springframework-developer — Spring Framework developers list

Re: [Springframework-developer] spring webflow in progress pr3 features - seeking feedback

[Erwin V. <erw...@er...>]

Feedback ahead:

1. I'm not so sure about this feature. It seems kind of unelegant - =
something like your second example seems more complex than adding an =
additional action state right in front of the view state. Do you see =
many usecases for it, besides view setup logic? If that is the only real =
usecase, I guess direct support for setup logic in the view state is a =
better fit. Or maybe have like "named entry actions" to a view state, =
with normal transitions. Something like:

<view-state id=3D"displaySearchCriteria" view=3D"searchCriteria">
    <action name=3D"setup" bean=3D"phoneBookActions" =
method=3D"setupSearchCriteriaForm"/>

    <!-- action transitions -->
    <transition on=3D"setup.error" to=3D"myErrorState"/>

    <!-- view transitions -->
    <transition on=3D"submit" to=3D"doSearch"/>
</view-state>

2. I like this. How about letting the type converter be specified (it =
implies the output type so no need to specify that in that case):

<property name=3D"..." value=3D"..." =
converter=3D"com.mycompany.MyFullyQualifiedTypeConverter"/>

3. I really like this. Just one remark: why the "name" parameter? =
Wouldn't it be better to do:

<input source=3D"myValueName" target=3D"abc"/>
<input source=3D"${my.value.path}" target=3D"abc"/>

That way the source-type and target-type have a very consistent name. =
Still, this doesn't "read" as nicely as <input name=3D"a" as=3D"b"/>.

4. I like the idea as an alternative to the current FlowFactoryBean, but =
how is the FlowLocator going to get hold of the FlowLoader? Using a =
typed lookup in the context?

Erwin Vervaet
erw...@er...
  ----- Original Message -----=20
  From: Keith Donald=20
  To: spr...@li...=20
  Sent: Wednesday, May 18, 2005 3:16 AM
  Subject: [Springframework-developer] spring webflow in progress pr3 =
features - seeking feedback


  SWF PR3 is expected to add some significant new features.  Some of =
these are still in progress, but we want to get them out now for =
feedback. want to make sure these are right.

  =20

  Here they are:

  =20

    1.. view state "display criteria" - EXPERIMENTAL=20
  =20

  We are experimenting with display TransitionCriteria associatable with =
a ViewState, to be tested after the state is entered but before a view =
descriptor is returned for resolution and rendering.  This allows you to =
execute arbitrary view pre-render logic before the view is displayed, =
reducing the need for an explicit action state to execute such logic.  =
In addition, if the display criteria test fails, a transition to another =
state (like an error state) may be executed.

  =20

  This is realized in its simplest form in the DTD as follows:

  =20

  <view-state id=3D"displaySearchCriteria" view=3D"searchCriteria">

      <display-criteria if-false=3D"myErrorState">

          <action bean=3D"phonebookActions" =
method=3D"setupSearchCriteriaForm"/>

            </display-criteria>

  </view-state>

  =20

        It could get as involved as:

  =20

  <view-state id=3D"displaySearchCriteria" view=3D"searchCriteria">

      <display-criteria if-false=3D"myErrorState">

      <action-criteria true=3D"customTrueEventId" =
false=3D"customFalseEventId">

                    <action bean=3D"phonebookActions" =
method=3D"setupSearchCriteriaForm"/>

                    <action bean=3D"phonebookActions" =
method=3D"setupSearchCriteriaFormSecondActionMethod"/>

      </action-criteria>

            </display-criteria>

  </view-state>

  =20

    2.. annotated objects: flows, states, transitions, actions - NEARLY =
DONE=20
  =20

  All definition objects (instances of Flow, State, Transition, Action) =
can now be qualified (aka annotated) with properties - metadata.  This =
should open the door for all kinds of stuff from role-based state =
security checks to dynamic state decision logic based on transitional =
context.  We're also adding full support for from-string property type =
conversion (with type aliasing) using the new data binding =
infrastructure.

  =20

  This is realized in the xml definition as follows:

  =20

  <flow || state || action || transition>

       <property name=3D"foo" value=3D"12345" type=3D"int"/>

       <property name=3D"bar" value=3D"some_custom_type" =
type=3D"myCustomTypeAlias"/>

       <property name=3D"foo2" value=3D"some_other_custom_type" =
type=3D"com.mycompany.MyFullyQualifiedType"/>=20

  </.>

  =20

  This relies on a converter installed to convert from string to the =
target type, with optional type aliasing to reduce typing.

  =20

    3.. attribute mapping from xml flow definition - NEARLY DONE=20
  =20

  It's now possible to specify input/output mappings for subflows =
directly from within the xml definition, reducing the need to =
instantiate a custom attribute mapper instance.

  =20

  This realized in multiple ways as follows:

  =20

  <subflow-state id=3D"enterPassengerInformation" flow=3D"passenger">=20

        <attribute-mapper>=20

           <input name=3D"someInputAttributeName"/>

           <input name=3D"someOtherInputAttributeName" =
as=3D"someAdaptedInputAttributeName"/>=20

           <input value=3D"${requestScope.someAttribute}" =
source-type=3D"string" as=3D"someAdaptedInputAttributeName" =
target-type=3D"int"/>=20

           <output name=3D"someOutputAttributeName"/>=20

           <output name=3D"someOutputAttributeName" =
as=3D"someAdaptedOutputAttributeName"/>

                    .

        </attribute-mapper>=20

  </subflow-state>

  =20

  =20

    4.. flow loaders - EXPERIMENTAL=20
  =20

  There's really no benefit I see to have Flows exported in the web =
application context.  A FlowAssembler could easily accept a group of =
flow builder classnames and/or references to XML flow definition =
resources and produce fully-configured Flow instances locatable by a =
FlowLocator.  This would eliminate the need to define a FlowFactoryBean =
per Flow definition: you could define all the flows of your app in a =
single bean definition, e.g:

  =20

  <bean id=3D"flowLoader" =
class=3D"org.springframework.web.flow.config.FlowLoader"/>

      <property name=3D"locations">

          <list>

               <value>classpath:myflow.xml</value>

               <value>classpath:flows/*.xml</value>

          </list>

      <property name=3D"classes">

          <list>

               <value>com.mycompany.MyFlowBuilder</value>

          </list>

      </property>

  </bean>

  =20

  What do you think?  Note the data binding stuff is completely =
independent of webflow and really belongs as an enhancement to the core =
in future Spring releases.

  =20

  Keith=20

[Springframework-developer] RE: spring webflow in progress pr3 features - seeking feedback

[Keith D. <ke...@in...>]

A few additional comments:

 

On #1 below we could have simple view setup action support as follows:

 

<view-state id="displaySearchCriteria" view="searchCriteria">

<action bean="phonebookActions" method="setupSearchCriteriaForm"/>

</view-state>

 

That would of course assume there was only a 'success' action result
possibility, which seems appropriate for most setup actions (e.g to populate
reference data drop downs)  If you need to handle error cases, then you'd
need to use the display-criteria elemtn with a if-false attribute.

 

One other feature I forgot to mention is the new ViewDescriptorCreator
strategy, allowing full dynamic control over the selection of a view and all
supporting model data when a view state is rendered.  This is a powerful
thing, for use like:

 

   <view-state id="myViewState" view="myStaticView"/> 
   <view-state id="myViewState"
view-creator="samples.MyCustomViewDescriptorCreator"/> 
   <view-state id="myViewState"
redirect="myRedirectView?foo=${flowScope.foo}"/>

 

The first definition uses a SimpleViewDescriptorCreator that simply selects
the same view each time.  The second definition selects a custom
ViewDescriptorCreator implementation (the most flexible).  The third
leverages a RedirectViewDescriptorCreator capable of resolving redirect
parameters from the flow request context using something like OGNL
expressions.

 

Keith

 

  _____  

From: Keith Donald [mailto:ke...@in...] 
Sent: Tuesday, May 17, 2005 9:17 PM
To: 'spr...@li...'
Subject: spring webflow in progress pr3 features - seeking feedback

 

SWF PR3 is expected to add some significant new features.  Some of these are
still in progress, but we want to get them out now for feedback. want to
make sure these are right.

 

Here they are:

 

1.	view state "display criteria" - EXPERIMENTAL

 

We are experimenting with display TransitionCriteria associatable with a
ViewState, to be tested after the state is entered but before a view
descriptor is returned for resolution and rendering.  This allows you to
execute arbitrary view pre-render logic before the view is displayed,
reducing the need for an explicit action state to execute such logic.  In
addition, if the display criteria test fails, a transition to another state
(like an error state) may be executed.

 

This is realized in its simplest form in the DTD as follows:

 

<view-state id="displaySearchCriteria" view="searchCriteria">

    <display-criteria if-false="myErrorState">

        <action bean="phonebookActions" method="setupSearchCriteriaForm"/>

          </display-criteria>

</view-state>

 

      It could get as involved as:

 

<view-state id="displaySearchCriteria" view="searchCriteria">

    <display-criteria if-false="myErrorState">

    <action-criteria true="customTrueEventId" false="customFalseEventId">

                  <action bean="phonebookActions"
method="setupSearchCriteriaForm"/>

                  <action bean="phonebookActions"
method="setupSearchCriteriaFormSecondActionMethod"/>

    </action-criteria>

          </display-criteria>

</view-state>

 

2.	annotated objects: flows, states, transitions, actions - NEARLY DONE

 

All definition objects (instances of Flow, State, Transition, Action) can
now be qualified (aka annotated) with properties - metadata.  This should
open the door for all kinds of stuff from role-based state security checks
to dynamic state decision logic based on transitional context.  We're also
adding full support for from-string property type conversion (with type
aliasing) using the new data binding infrastructure.

 

This is realized in the xml definition as follows:

 

<flow || state || action || transition>

     <property name="foo" value="12345" type="int"/>

     <property name="bar" value="some_custom_type"
type="myCustomTypeAlias"/>

     <property name="foo2" value="some_other_custom_type"
type="com.mycompany.MyFullyQualifiedType"/> 

</.>

 

This relies on a converter installed to convert from string to the target
type, with optional type aliasing to reduce typing.

 

3.	attribute mapping from xml flow definition - NEARLY DONE

 

It's now possible to specify input/output mappings for subflows directly
from within the xml definition, reducing the need to instantiate a custom
attribute mapper instance.

 

This realized in multiple ways as follows:

 

<subflow-state id="enterPassengerInformation" flow="passenger"> 

      <attribute-mapper> 

         <input name="someInputAttributeName"/>

         <input name="someOtherInputAttributeName"
as="someAdaptedInputAttributeName"/> 

         <input value="${requestScope.someAttribute}" source-type="string"
as="someAdaptedInputAttributeName" target-type="int"/> 

         <output name="someOutputAttributeName"/> 

         <output name="someOutputAttributeName"
as="someAdaptedOutputAttributeName"/>

                  .

      </attribute-mapper> 

</subflow-state>

 

 

4.	flow loaders - EXPERIMENTAL

 

There's really no benefit I see to have Flows exported in the web
application context.  A FlowAssembler could easily accept a group of flow
builder classnames and/or references to XML flow definition resources and
produce fully-configured Flow instances locatable by a FlowLocator.  This
would eliminate the need to define a FlowFactoryBean per Flow definition:
you could define all the flows of your app in a single bean definition, e.g:

 

<bean id="flowLoader"
class="org.springframework.web.flow.config.FlowLoader"/>

    <property name="locations">

        <list>

             <value>classpath:myflow.xml</value>

             <value>classpath:flows/*.xml</value>

        </list>

    <property name="classes">

        <list>

             <value>com.mycompany.MyFlowBuilder</value>

        </list>

    </property>

</bean>

 

What do you think?  Note the data binding stuff is completely independent of
webflow and really belongs as an enhancement to the core in future Spring
releases.

 

Keith 

[Springframework-developer] spring webflow in progress pr3 features - seeking feedback

[Keith D. <ke...@in...>]

SWF PR3 is expected to add some significant new features.  Some of these are
still in progress, but we want to get them out now for feedback. want to
make sure these are right.

 

Here they are:

 

1.	view state "display criteria" - EXPERIMENTAL

 

We are experimenting with display TransitionCriteria associatable with a
ViewState, to be tested after the state is entered but before a view
descriptor is returned for resolution and rendering.  This allows you to
execute arbitrary view pre-render logic before the view is displayed,
reducing the need for an explicit action state to execute such logic.  In
addition, if the display criteria test fails, a transition to another state
(like an error state) may be executed.

 

This is realized in its simplest form in the DTD as follows:

 

<view-state id="displaySearchCriteria" view="searchCriteria">

    <display-criteria if-false="myErrorState">

        <action bean="phonebookActions" method="setupSearchCriteriaForm"/>

          </display-criteria>

</view-state>

 

      It could get as involved as:

 

<view-state id="displaySearchCriteria" view="searchCriteria">

    <display-criteria if-false="myErrorState">

    <action-criteria true="customTrueEventId" false="customFalseEventId">

                  <action bean="phonebookActions"
method="setupSearchCriteriaForm"/>

                  <action bean="phonebookActions"
method="setupSearchCriteriaFormSecondActionMethod"/>

    </action-criteria>

          </display-criteria>

</view-state>

 

2.	annotated objects: flows, states, transitions, actions - NEARLY DONE

 

All definition objects (instances of Flow, State, Transition, Action) can
now be qualified (aka annotated) with properties - metadata.  This should
open the door for all kinds of stuff from role-based state security checks
to dynamic state decision logic based on transitional context.  We're also
adding full support for from-string property type conversion (with type
aliasing) using the new data binding infrastructure.

 

This is realized in the xml definition as follows:

 

<flow || state || action || transition>

     <property name="foo" value="12345" type="int"/>

     <property name="bar" value="some_custom_type"
type="myCustomTypeAlias"/>

     <property name="foo2" value="some_other_custom_type"
type="com.mycompany.MyFullyQualifiedType"/> 

</.>

 

This relies on a converter installed to convert from string to the target
type, with optional type aliasing to reduce typing.

 

3.	attribute mapping from xml flow definition - NEARLY DONE

 

It's now possible to specify input/output mappings for subflows directly
from within the xml definition, reducing the need to instantiate a custom
attribute mapper instance.

 

This realized in multiple ways as follows:

 

<subflow-state id="enterPassengerInformation" flow="passenger"> 

      <attribute-mapper> 

         <input name="someInputAttributeName"/>

         <input name="someOtherInputAttributeName"
as="someAdaptedInputAttributeName"/> 

         <input value="${requestScope.someAttribute}" source-type="string"
as="someAdaptedInputAttributeName" target-type="int"/> 

         <output name="someOutputAttributeName"/> 

         <output name="someOutputAttributeName"
as="someAdaptedOutputAttributeName"/>

                  .

      </attribute-mapper> 

</subflow-state>

 

 

4.	flow loaders - EXPERIMENTAL

 

There's really no benefit I see to have Flows exported in the web
application context.  A FlowAssembler could easily accept a group of flow
builder classnames and/or references to XML flow definition resources and
produce fully-configured Flow instances locatable by a FlowLocator.  This
would eliminate the need to define a FlowFactoryBean per Flow definition:
you could define all the flows of your app in a single bean definition, e.g:

 

<bean id="flowLoader"
class="org.springframework.web.flow.config.FlowLoader"/>

    <property name="locations">

        <list>

             <value>classpath:myflow.xml</value>

             <value>classpath:flows/*.xml</value>

        </list>

    <property name="classes">

        <list>

             <value>com.mycompany.MyFlowBuilder</value>

        </list>

    </property>

</bean>

 

What do you think?  Note the data binding stuff is completely independent of
webflow and really belongs as an enhancement to the core in future Spring
releases.

 

Keith 

[Springframework-developer] FAILED BUILD: sparc-solaris2 (last 30 lines included)

[Darren D. <da...@sh...>]

1116373860
FAILED
    [junit] Testcase: testWebApplicationObjectSupport took 0,004 sec
    [junit] Testcase: testWebApplicationObjectSupportWithWrongContext took 0,002 sec
    [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0,249 sec
    [junit] Testsuite: org.springframework.web.filter.DelegatingFilterProxyTests
    [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0,249 sec

    [junit] Testcase: testDelegatingFilterProxy took 0,216 sec
    [junit] Testcase: testDelegatingFilterProxyWithFilterName took 0,004 sec
    [junit] Testcase: testDelegatingFilterProxyWithLazyContextStartup took 0,003 sec
    [junit] Testcase: testDelegatingFilterProxyWithTargetFilterLifecycle took 0,003 sec
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,029 sec
    [junit] Testsuite: org.springframework.web.jsf.DelegatingVariableResolverTests
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,029 sec

    [junit] Testcase: testDelegatingVariableResolver took 0,008 sec
    [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 1,173 sec
    [junit] Testsuite: org.springframework.web.multipart.commons.CommonsMultipartResolverTests
    [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 1,173 sec

    [junit] Testcase: testWithApplicationContext took 0,567 sec
    [junit] Testcase: testWithServletContextAndFilter took 0,327 sec
    [junit] Testcase: testWithServletContextAndFilterWithCustomBeanName took 0,259 sec
    [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0,479 sec
    [junit] Testsuite: org.springframework.web.multipart.cos.CosMultipartResolverTests
    [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0,479 sec

    [junit] Testcase: testWithApplicationContext took 0,017 sec
    [junit] Testcase: testWithServletContext took 0 sec
    [junit] Testcase: testMultipartResolution took 0,323 sec
    [junit] Testcase: testWithPhysicalFile took 0,115 sec

This is an automated mail from one of the SF Compile Farm machines.  
The machine name noted in the subject encountered a failure building
or running the Spring test suite.  The last few lines of the output
were included for info.

NB: No further mail will be sent from this machine until a
manual reset occurs on the cf-shell machine, although builds will
continue as scheduled.

See http://springframework.sourceforge.net/test/ for further
information.

[Springframework-developer] Paranoider Deutschenmoerder kommt in Psychiatrie

[<lm...@do...>]

Lese selbst:
http://brandenburg.rz.fhtw-berlin.de/poetschke.html

[Springframework-developer] FAILED BUILD: ppc-osx2 (last 30 lines included)

[Darren D. <da...@sh...>]

1116365809
FAILED

This is an automated mail from one of the SF Compile Farm machines.  
The machine name noted in the subject encountered a failure building
or running the Spring test suite.  The last few lines of the output
were included for info.

NB: No further mail will be sent from this machine until a
manual reset occurs on the cf-shell machine, although builds will
continue as scheduled.

See http://springframework.sourceforge.net/test/ for further
information.

RE: [Springframework-developer] Support for state/controller chaining in Portlets? (not quite webflow)

[Boyce, K. G. <Kei...@bc...>]

I created a portlet app with webflow. I read that back button
functionality is fixed but I have't tested it yet.=0D

-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf
Of Tim Kettering
Sent: Tuesday, May 17, 2005 4:00 PM
To: spr...@li...
Subject: [Springframework-developer] Support for state/controller
chaining in Portlets? (not quite webflow)


Hi everyone,

I'm just throwing this out here to see what other people have to say.  I
can see from the list that there are a few developers actively working
on portal solutions using Spring MVC.  We are starting on our first
project using this as well, and one of the issues I'm trying to figure
out now is the matter of maintaining state in a portlet. =0D

In a typical CRUD example, if we have a portlet to display, edit and
maange information about a certain object, like a Book. We'd have view,
edit and delete functionality for example.=0D

In a typical non-portlet webapp, we could easily split those up across
different servlets for fine-grained areas of responsibility. =0D

But it's not as simple with portlets, because there are limitations on
what can be done, and essentially, all requests would need to go thru a
single portlet configuration. =0D

So, it no longer become sufficient to configure a simple portlet
controller for a portlet.  There needs to be a way to maintain state and
to delegate the request/response process to different types of
controllers depending on the state.  Like a View page would need to go
thru a derivation of BaseCommandController, an Edit page would go thru
SimpleFormController.=0D

And not to mention adding yet another dimension when considering portlet
modes as well!

This article at IBM Developerworks pretty much covers the same issue I
am bringing up:

http://www-106.ibm.com/developerworks/websphere/library/techarticles/031
2_ha
nis/hanis1.html

I did look at Spring's WebFlow a few days ago to see if it could address
our issue, but in the Webflow FAQ, it pretty much states that WebFlow
should not be used in cases where the user will be using back-button, or
indeterminate actions not within a strict flow. =0D

So that kinda leaves me back at square one.  After some discussion with
my co-worker, I would imagine that this is a common problem for any
Spring portlet developer creating more than just simple portlet
functionality.  And that as Spring portlet support matures, this will be
a more common issue for everyone.  Hence this email to the list. =0D

I'm now wondering how some of you have addressed this problem, and
whether there is a need for Spring's portlet support, to be in Spring
1.3 to include some way to configure and facilitate a state process,
maybe even based on WebFlow's state machine - although I have only given
WebFlow's state functionality a brief look.

Thanks in advance,

-tim



-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be
the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=3D7412&alloc_id=3D16344&op=3Dclick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer


This message is a PRIVATE communication.
If you are not the intended recipient, please do not read, copy,
or use it, and do not disclose it to others. Please notify the
sender of the delivery error by replying to this message, and then
delete it from your system. Thank you.

[Springframework-developer] Support for state/controller chaining in Portlets? (not quite webflow)

[Tim K. <tim...@vi...>]

Hi everyone,

I'm just throwing this out here to see what other people have to say.  I can
see from the list that there are a few developers actively working on portal
solutions using Spring MVC.  We are starting on our first project using this
as well, and one of the issues I'm trying to figure out now is the matter of
maintaining state in a portlet.  

In a typical CRUD example, if we have a portlet to display, edit and maange
information about a certain object, like a Book. We'd have view, edit and
delete functionality for example. 

In a typical non-portlet webapp, we could easily split those up across
different servlets for fine-grained areas of responsibility.  

But it's not as simple with portlets, because there are limitations on what
can be done, and essentially, all requests would need to go thru a single
portlet configuration.  

So, it no longer become sufficient to configure a simple portlet controller
for a portlet.  There needs to be a way to maintain state and to delegate
the request/response process to different types of controllers depending on
the state.  Like a View page would need to go thru a derivation of
BaseCommandController, an Edit page would go thru SimpleFormController. 

And not to mention adding yet another dimension when considering portlet
modes as well!

This article at IBM Developerworks pretty much covers the same issue I am
bringing up:

http://www-106.ibm.com/developerworks/websphere/library/techarticles/0312_ha
nis/hanis1.html

I did look at Spring's WebFlow a few days ago to see if it could address our
issue, but in the Webflow FAQ, it pretty much states that WebFlow should not
be used in cases where the user will be using back-button, or indeterminate
actions not within a strict flow.  

So that kinda leaves me back at square one.  After some discussion with my
co-worker, I would imagine that this is a common problem for any Spring
portlet developer creating more than just simple portlet functionality.  And
that as Spring portlet support matures, this will be a more common issue for
everyone.  Hence this email to the list.  

I'm now wondering how some of you have addressed this problem, and whether
there is a need for Spring's portlet support, to be in Spring 1.3 to include
some way to configure and facilitate a state process, maybe even based on
WebFlow's state machine - although I have only given WebFlow's state
functionality a brief look.

Thanks in advance,

-tim

[Springframework-developer] **Message you sent blocked by our bulk email filter**

[MAILER-DAEMON <>]

WW91ciBtZXNzYWdlIHRvOiBhc3VkZWxsQGRjYS5uZXQKd2FzIGJsb2NrZWQg
Ynkgb3VyIFNwYW0gRmlyZXdhbGwuIFRoZSBlbWFpbCB5b3Ugc2VudCB3aXRo
IHRoZSBmb2xsb3dpbmcgc3ViamVjdCBoYXMgTk9UIEJFRU4gREVMSVZFUkVE
OgoKU3ViamVjdDogRHUgd2lyc3QgYXVzc3Bpb25pZXJ0IC4uLi4hCgo=

[Springframework-developer] FAILED BUILD: ppc-osx2 (last 30 lines included)

[Darren D. <da...@sh...>]

1116310511
FAILED
Buildfile: build.xml

clean:

compileattr:
[attribute-compiler] Generated attribute information for 1 classes. Ignored 0 classes.

buildmain:
    [mkdir] Created dir: /home/users/d/da/davison/checkouts/spring/target/ppc-osx2/classes
    [mkdir] Created dir: /home/users/d/da/davison/checkouts/spring/target/ppc-osx2/classes/META-INF
    [javac] Compiling 1048 source files to /home/users/d/da/davison/checkouts/spring/target/ppc-osx2/classes

This is an automated mail from one of the SF Compile Farm machines.  
The machine name noted in the subject encountered a failure building
or running the Spring test suite.  The last few lines of the output
were included for info.

NB: No further mail will be sent from this machine until a
manual reset occurs on the cf-shell machine, although builds will
continue as scheduled.

See http://springframework.sourceforge.net/test/ for further
information.

Re: [Springframework-developer] timezone on www.springframework.org

[Thomas V. de V. <tho...@gm...>]

A small additional point on i18n. Currently I am getting a couple of links=
=20
in French (due to my locale) but that doesn't make much sense since the sit=
e=20
is in english.

Thomas

On 5/16/05, Colin Sampaleanu <col...@ex...> wrote:
>=20
> Erwin Vervaet wrote:
>=20
> > What is up with the timezone indication on the new site? On my
> > machines it always says for news items with a start & end date:
> >
> > Timezone: -14400
> >
> > I haven't calculated whether or not that is correct.... :)
> >
> > Erwin Vervaet
> > erw...@er...
>=20
> I don't know why it prints that as the timezone. In the configuration
> for the site it's set as -0400.
>=20
> --
> Colin Sampaleanu
> Interface21 Principal Consultant
> Spring Training, Consulting and Support - "From the Source"
> http://www.springframework.com
>=20
>=20
> -------------------------------------------------------
> This SF.Net <http://SF.Net> email is sponsored by Oracle Space Sweepstake=
s
> Want to be the first software developer in space?
> Enter now for the Oracle Space Sweepstakes!
> http://ads.osdn.com/?ad_id=3D7393&alloc_id=3D16281&op=3Dclick
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>

[Springframework-developer] Race condition with transaction synchronization?

[Dave B. <dba...@on...>]

Hello,

I posted this on the forums, but costin and Rod suggested that I post it 
here.

I'm using Spring Framework 1.1.5 with Hibernate on WebLogic Server 6.1. 
I'm testing timeout scenarios, and I've run into an issue I need some 
help with. I'm slowly eliminating EJB's from my application, but I do 
have some legacy EJB code to deal with. In my scenario, my servlet is 
calling a SLSB, which in turn calls spring-managed transactional 
services. These transaction service join the CMT transaction created by 
the EJB container. I have:

Code:

1) A servlet calls SLSB with CMT.
2) The SLSB calls SessionFactoryUtils.getSession(sessionFactory, true)
-- This binds the hibernate session to the current thread
3) The SLSB calls a spring-managed transactional service
-- This bean uses the bound session as expected
4) The SLSB calls another spring-managed transactional service
-- This bean uses the bound session as expected
5) The SLSB exits
-- The TransactionSynchronizationManager unbinds the bound session as 
expected


So the non-timeout scenario functions as expected. Now I introduce a 
timeout (by causing blocking in by database) prior to (3). With the 
timeout scenario, I encounter one of two results:

Code:

A) A spring HibernateJdbcException wrapping a weblogic TimedOutException 
as expected.
B) An IllegalStateException Already value 
[org.springframework.orm.hibernate.SessionHolder@6f2304] for key 
[net.sf.hibernate.impl.SessionFactoryImpl@655ad0] bound to thread 
[ExecuteThread: '29' for queue: 'default']


Whether I get (A) or (B) is seemingly random. I've created a diagnostic 
version of SessionFactoryUtils to see what is happening in more detail.
In scenario (B), it looks like WebLogic's transaction manager is 
grabbing another thread from the pool and is invoking spring's 
JtaSessionSynchronization.afterCompletion() which is resulting in 
doClose() being called. I've added a dumpStack() in doClose(), and here 
is what I see. The line numbers will be a little off because of my 
diagnostic code:

Code:

java.lang.Exception: Stack trace
        at java.lang.Thread.dumpStack(Thread.java:992)
        at 
org.springframework.orm.hibernate.SessionFactoryUtils.doClose(SessionFactoryUtils.java:738)
        at 
org.springframework.orm.hibernate.SessionFactoryUtils.closeSessionOrRegisterDeferredClose(SessionFactoryUtils.java:726)
        at 
org.springframework.orm.hibernate.SessionFactoryUtils.access$300(SessionFactoryUtils.java:89)
        at 
org.springframework.orm.hibernate.SessionFactoryUtils$SpringSessionSynchronization.beforeCompletion(SessionFactoryUtils.java:867)
        at 
org.springframework.orm.hibernate.SessionFactoryUtils$JtaSessionSynchronization.afterCompletion(SessionFactoryUtils.java:978)
        at 
weblogic.transaction.internal.ServerSCInfo.callAfterCompletions(ServerSCInfo.java:464)
        at 
weblogic.transaction.internal.ServerTransactionImpl.callAfterCompletions(ServerTransactionImpl.java:2139)
        at 
weblogic.transaction.internal.ServerTransactionImpl.setRolledBack(ServerTransactionImpl.java:2090)
        at 
weblogic.transaction.internal.ServerTransactionImpl.globalRetryRollback(ServerTransactionImpl.java:2188)DEBUG 
18:19:23,000 [ExecuteThread: '34' for queue: 'default'] [edemo_acme] 
(Transacti
        at 
weblogic.transaction.internal.ServerTransactionImpl.globalRollback(ServerTransactionImpl.java:2080)
        at 
weblogic.transaction.internal.TransactionImpl$1.execute(TransactionImpl.java:1617)
        at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:159)
        at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:140)


Meanwhile, the original timeout thread, who is in the middle of calling 
getSession(), and hasn't yet encountered the weblogic TimedOutException,
tries to bind the session holder to the thread, and fails:

Code:

ERROR 18:19:23,046 [ExecuteThread: '34' for queue: 'default'] 
[edemo_acme] (TransactionAspectSupport.java:264) - Application exception 
overridden by rollback exception
java.lang.IllegalStateException: Already value 
[org.springframework.orm.hibernate.SessionHolder@747db9] for key 
[net.sf.hibernate.impl.SessionFactoryImpl@606e55] bound to thread 
[ExecuteThread: '34' for queue: 'default']
        at 
org.springframework.transaction.support.TransactionSynchronizationManager.bindResource(TransactionSynchronizationManager.java:147)
        at 
org.springframework.orm.hibernate.SessionFactoryUtils.getSession(SessionFactoryUtils.java:346)
        at 
org.springframework.orm.hibernate.SessionFactoryUtils.getSession(SessionFactoryUtils.java:266)
        at 
org.springframework.orm.hibernate.SessionFactoryUtils.getSession(SessionFactoryUtils.java:223)
        at 
org.springframework.orm.hibernate.HibernateInterceptor.invoke(HibernateInterceptor.java:149)
        at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:144)
        at 
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:174)
        at $Proxy93.findContract(Unknown Source)
        at 
mycode.ContractServiceImpl.findContract(ContractServiceImpl.java:59)
        ...


It's not clear to me who the culprit is here, not being that familiar 
with JTA and Spring. Perhaps the beforeCompletion() called by the 
weblogic transaction manager is not cleaning up properly? Any ideas?

Thanks for your help,
Dave

Re: [Springframework-developer] New www.springframework.org site is live!

[<tho...@tr...>]

I copied Darren's "hack" to give the nightly build download page the more
uniform look as well.

Thomas


> Darren Davison wrote:
>
>>On Fri, May 6, 2005 16:53, Colin Sampaleanu said:
>>
>>
>>>Darren Davison wrote:
>>>
>>>
>>>
>>>>On Fri, May 6, 2005 7:32, Erwin Vervaet said:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>* If you click "Development > Continuous Build" you go to a somewhat
>>>>> messed
>>>>>up page that has the old look & feel.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>the continuous build page is on the SF project web servers as I never
>>>> had SSH
>>>>(or FTP) access to the springframework.org site.  Materials from the
>>>> compile
>>>>farm are transferred from there to my home server then up to the web
>>>> server.
>>>>
>>>>I can either replicate the new look and feel on the project web space
>>>> at SF
>>>>or
>>>>transfer the material up to the new servers if preferred.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>You certainly _can_ get ssh access into the new host, although that
>>>doesn't get it into the CMS anyway. So if it stays as static HTML
>>>content, I'm not so sure it necessarilly adds much value to push the
>>>stuff to the new host. The builds are on SF anyway, and keeping the data
>>>there means there's means the page can probably be updated more easily,
>>>and there's reduced bandwidth usage on the new host as people will
>>>access the data from SF instead...
>>>
>>>
>>
>>finally got round to updated the L&F for the continuous build page:
>>http://springframework.sourceforge.net/test/
>>
>>May get out of sync if the navigation changes on the main site but the
>> CSS and
>>images are referenced from there directly.
>>
>>
> Cool! If we are worried about getting out of sync, I think one option
> would be to just keep on using the CSS and images, but have a minimal
> menu only with a link to the real site; that way it would be clear to
> people that they are on another site.
>
> Colin
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by Oracle Space Sweepstakes
> Want to be the first software developer in space?
> Enter now for the Oracle Space Sweepstakes!
> http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>

Re: [Springframework-developer] New www.springframework.org site is live!

[Colin S. <col...@ex...>]

Darren Davison wrote:

>On Fri, May 6, 2005 16:53, Colin Sampaleanu said:
>  
>
>>Darren Davison wrote:
>>
>>    
>>
>>>On Fri, May 6, 2005 7:32, Erwin Vervaet said:
>>>
>>>
>>>
>>>      
>>>
>>>>* If you click "Development > Continuous Build" you go to a somewhat messed
>>>>up page that has the old look & feel.
>>>>
>>>>
>>>>        
>>>>
>>>the continuous build page is on the SF project web servers as I never had SSH
>>>(or FTP) access to the springframework.org site.  Materials from the compile
>>>farm are transferred from there to my home server then up to the web server.
>>>
>>>I can either replicate the new look and feel on the project web space at SF
>>>or
>>>transfer the material up to the new servers if preferred.
>>>
>>>
>>>
>>>      
>>>
>>You certainly _can_ get ssh access into the new host, although that
>>doesn't get it into the CMS anyway. So if it stays as static HTML
>>content, I'm not so sure it necessarilly adds much value to push the
>>stuff to the new host. The builds are on SF anyway, and keeping the data
>>there means there's means the page can probably be updated more easily,
>>and there's reduced bandwidth usage on the new host as people will
>>access the data from SF instead...
>>    
>>
>
>finally got round to updated the L&F for the continuous build page:
>http://springframework.sourceforge.net/test/
>
>May get out of sync if the navigation changes on the main site but the CSS and
>images are referenced from there directly.
>  
>
Cool! If we are worried about getting out of sync, I think one option 
would be to just keep on using the CSS and images, but have a minimal 
menu only with a link to the real site; that way it would be clear to 
people that they are on another site.

Colin

Re: [Springframework-developer] New www.springframework.org site is live!

[Darren D. <da...@da...>]

On Fri, May 6, 2005 16:53, Colin Sampaleanu said:
> Darren Davison wrote:
>
>>On Fri, May 6, 2005 7:32, Erwin Vervaet said:
>>
>>
>>
>>>* If you click "Development > Continuous Build" you go to a somewhat m=
essed
>>>up page that has the old look & feel.
>>>
>>>
>>
>>the continuous build page is on the SF project web servers as I never h=
ad SSH
>>(or FTP) access to the springframework.org site.  Materials from the co=
mpile
>>farm are transferred from there to my home server then up to the web se=
rver.
>>
>>I can either replicate the new look and feel on the project web space a=
t SF
>> or
>>transfer the material up to the new servers if preferred.
>>
>>
>>
> You certainly _can_ get ssh access into the new host, although that
> doesn't get it into the CMS anyway. So if it stays as static HTML
> content, I'm not so sure it necessarilly adds much value to push the
> stuff to the new host. The builds are on SF anyway, and keeping the dat=
a
> there means there's means the page can probably be updated more easily,
> and there's reduced bandwidth usage on the new host as people will
> access the data from SF instead...

finally got round to updated the L&F for the continuous build page:
http://springframework.sourceforge.net/test/

May get out of sync if the navigation changes on the main site but the CS=
S and
images are referenced from there directly.

Regards,


--=20
Darren Davison
Public Key: 0xDD356B0D

Re: [Springframework-developer] timezone on www.springframework.org

[Colin S. <col...@ex...>]

Erwin Vervaet wrote:

> What is up with the timezone indication on the new site? On my 
> machines it always says for news items with a start & end date:
>
> Timezone: -14400
>
> I haven't calculated whether or not that is correct.... :)
>
> Erwin Vervaet
> erw...@er...

I don't know why it prints that as the timezone. In the configuration 
for the site it's set as -0400.

-- 
Colin Sampaleanu
Interface21 Principal Consultant
Spring Training, Consulting and Support - "From the Source"
http://www.springframework.com

[Springframework-developer] spring build.263 Build Successful

[<al...@in...>]

View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20050516001612Lbuild.263

[Springframework-developer] timezone on www.springframework.org

[Erwin V. <erw...@er...>]

What is up with the timezone indication on the new site? On my machines it 
always says for news items with a start & end date:

Timezone: -14400

I haven't calculated whether or not that is correct.... :)

Erwin Vervaet
erw...@er... 

[Springframework-developer] Multi-Kulturell = Multi-Kriminell

[<Pau...@kp...>]

Lese selbst:
http://www.npd.de/npd_info/meldungen/2005/m0105-19.html

[Springframework-developer] spring build.262 Build Successful

[<al...@in...>]

View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20050514001612Lbuild.262

[Springframework-developer] Spring Framework 1.2 final released

[Juergen H. <ju...@in...>]

Dear Spring community,

I'm pleased to announce that Spring 1.2 final has just been released. The
major new features since 1.2 RC2 are:

* TopLink support (for both TopLink 9.0.4 and 10.1.3)
* JDO 2.0 support (tested against JPOX 1.1 beta 3)
* Hibernate 3.0.3 support (aggressive release of Connections)

The overall major new features of Spring 1.2 are:

* finer-grained distribution jar files
* simplified XML bean definitions
* JMX support
* JDK 1.5 transaction annotation
* support for WebLogic JTA extensions
* JDBC RowSet support
* JCA CCI support
* JDO2 support
* Hibernate3 support
* TopLink support

Thanks to Oracle for donating the original TopLink support prototype, and in
particular to Jim Clark from Oracle - for all his help in getting the
TopLink support into its final shape!

For details on new features, deprecations and bug fixes, please see the
change log.

FYI, we have a 1.2.1 release scheduled for June, featuring minor
enhancements that did not make 1.2 final. See our JIRA road map for details.

Cheers,

Juergen

-----
Juergen Hoeller
Interface21 - Spring Services from the Source
http://www.springframework.com

Re: [Springframework-developer] Nightly snapshot available again

[Juergen H. <ju...@in...>]

Yippie :-) Thanks, Alef!

Juergen


-----Original Message-----
From: spr...@li...
[mailto:spr...@li...]On Behalf
Of Alef Arendsen
Sent: Friday, May 13, 2005 3:15 PM
To: spr...@li...
Subject: [Springframework-developer] Nightly snapshot available again


Okay, the nightly snapshot has been fixed. it's fixed, the upload should
has been done to the old springframework.org site and is linked from the
new download page.

Rgds,
Alef




> -----Original Message-----
> From: spr...@li...
> [mailto:spr...@li...]
>  On Behalf Of al...@in...
> Sent: Friday, May 13, 2005 3:05 PM
> To: spr...@li...
> Subject: [Springframework-developer] spring build.261 Build Fixed
>
> View results here ->
> http://opensource.jteam.nl/build/buildresults/spring?log=log20
> 050513144501Lbuild.261
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by Oracle Space Sweepstakes
> Want to be the first software developer in space?
> Enter now for the Oracle Space Sweepstakes!
> http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_ids93&alloc_id281&op=ick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

[Springframework-developer] Nightly snapshot available again

[Alef A. <al...@jt...>]

Okay, the nightly snapshot has been fixed. it's fixed, the upload should
has been done to the old springframework.org site and is linked from the
new download page.

Rgds,
Alef


=20

> -----Original Message-----
> From: spr...@li...=20
> [mailto:spr...@li...]
>  On Behalf Of al...@in...
> Sent: Friday, May 13, 2005 3:05 PM
> To: spr...@li...
> Subject: [Springframework-developer] spring build.261 Build Fixed
>=20
> View results here ->=20
> http://opensource.jteam.nl/build/buildresults/spring?log=3Dlog20
> 050513144501Lbuild.261
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by Oracle Space Sweepstakes=20
> Want to be the first software developer in space?
> Enter now for the Oracle Space Sweepstakes!
> http://ads.osdn.com/?ad_id=3D7393&alloc_id=3D16281&op=3Dclick
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>=20
>=20

[Springframework-developer] spring build.261 Build Fixed

[<al...@in...>]

View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20050513144501Lbuild.261

RE: [Springframework-developer] spring Build Failed

[Alef A. <al...@in...>]

Sorry guys, I have been terribly busy this week. I'll redirect the FTP
upload to oldwww.springframework.org for now and coordinate with Colin later
on.

Again, apologies!

Alef
 

> -----Original Message-----
> From: spr...@li... 
> [mailto:spr...@li...]
>  On Behalf Of Colin Sampaleanu
> Sent: Thursday, May 12, 2005 4:38 AM
> To: spr...@li...
> Subject: Re: [Springframework-developer] spring Build Failed
> 
> It's not as simple as 'someone'. Only Alef can do the work on 
> the build side, since it's running at JTeam. And on our end, 
> I'm generally the only person who's been touching our host 
> (although Alef knows Linux of course so could get in there), 
> and I'm onsite at a client all this week and can't coordinate 
> with Alef during the day.
> 
> I think the easiest thing is for Alef to point the uploads 
> towards oldwww.springframework.org, which still points to the 
> old site, and we can easilly adjust the link from the new 
> website to point to the upload dir on the old one.
> 
> Then this weekend or any time after, when I am back, I can 
> coordinate with Alef to get the stuff going into the new site.
> 
> Colin
> 
> Juergen Hoeller wrote:
> 
> >Could someone *please* fix the FTP upload? It's really a 
> pain that we 
> >haven't had a proper nightly build for a week now!
> >
> >I don't feel particularly confident about releasing 1.2 
> final without 
> >an up-to-date nightly build having preceded it...
> >
> >Juergen
> >
> >
> >-----Original Message-----
> >From: spr...@li...
> >[mailto:spr...@li...
> ]On Behalf 
> >Of al...@in...
> >Sent: Wednesday, May 11, 2005 12:32 AM
> >To: spr...@li...
> >Subject: [Springframework-developer] spring Build Failed
> >Importance: High
> >
> >
> >View results here ->
> >http://opensource.jteam.nl/build/buildresults/spring?log=log2
> 0050511001
> >708
> >
> >
> >-------------------------------------------------------
> >This SF.Net email is sponsored by Oracle Space Sweepstakes 
> Want to be 
> >the first software developer in space?
> >Enter now for the Oracle Space Sweepstakes!
> >http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
> >_______________________________________________
> >Springframework-developer mailing list
> >Spr...@li...
> >https://lists.sourceforge.net/lists/listinfo/springframework-
> developer
> >
> >
> >
> >-------------------------------------------------------
> >This SF.Net email is sponsored by Oracle Space Sweepstakes 
> Want to be 
> >the first software developer in space?
> >Enter now for the Oracle Space Sweepstakes!
> >http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
> >_______________________________________________
> >Springframework-developer mailing list
> >Spr...@li...
> >https://lists.sourceforge.net/lists/listinfo/springframework-
> developer
> >  
> >
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by Oracle Space Sweepstakes 
> Want to be the first software developer in space?
> Enter now for the Oracle Space Sweepstakes!
> http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
> 
>