springframework-developer — Spring Framework developers list

Re: [Springframework-developer] Minor bug in reference documentation

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

Thanks for spotting this - fixed!

Juergen


-----Original Message-----
From: spr...@li...
[mailto:spr...@li...]On Behalf
Of Jan Zuchhold
Sent: Wednesday, March 09, 2005 6:34 PM
To: spr...@li...
Subject: [Springframework-developer] Minor bug in reference
documentation


Hello,

there's a minor bug in the reference documentation
(http://www.springframework.org/docs/reference/remoting.html).

In section "17.2.2. Linking in the service at the client" the second sample
should be

<bean class="example.SimpleObject">
 <property name="accountService"><ref bean="accountService"/></property>
</bean>
[...]

instead of

<bean class="example.SimpleObject">
 <property name="accountService"><ref bean="accountService"/></bean>
</bean>
[...]


Jan


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] ParameterNameMethodNameResolver

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

I agree with Erwin that combining both approaches into
ParameterMethodNameResolver would be nice. Any objection to this, Colin?

Juergen


-----Original Message-----
From: spr...@li...
[mailto:spr...@li...]On Behalf
Of Erwin Vervaet
Sent: Thursday, March 10, 2005 8:48 AM
To: spr...@li...
Subject: Re: [Springframework-developer] ParameterNameMethodNameResolver


Colin,

Good idea, but I think it would be better to integrate both systems in the
ParameterMethodNameResolver:
1) first try the action=methodname syntax
2) if nothing found, try action:methodName=foobar syntax

Combining the two in 1 MethodNameResolver gives you to opportunity to mix
and match the 2 techniques in the view. By having 2 resolvers you're forced
to use one technique or the other.

In the web flow system we originally also had these 2 systems in seperate
"ParameterExtractors", but we abandoned this in favour of a more powerfull
approach that supports both systems (and actually a third: image buttons).
Check the following method in the sanbox source tree:

org.springframework.web.flow.support.HttpFlowExecutionManager.searchForReque
stParameter(HttpServletRequest
request, String logicalName, String delimiter)

Maybe it would be good to use that. We could move the method into the main
source tree and put it on the WebUtils class.

What do you think?

Erwin Vervaet
----- Original Message -----
From: "Colin Sampaleanu" <col...@ex...>
To: <spr...@li...>
Sent: Thursday, March 10, 2005 4:55 AM
Subject: [Springframework-developer] ParameterNameMethodNameResolver


> I've added a new resolver for the MultiActionController,
> ParameterNameMethodNameResolver. Unlike ParameterMethodNameResolver, which
> looks for a parameter like
>   action=methodname
> where action stays constant, and the value is the method name,
> ParameterNameMethodNameResolver uses the very existene of a parameter name
> as an indication to map to a specific method. So feeding it the String
> mapping array
>   "hello:goodbye", "validate", "colin:nina"
> for example would map to the 'goodbye' method if there was a param
> 'hello', to the 'validate' method if there was a parameter named
> 'validate', and to 'nina' if there is a parameter named 'colin'. The
> request parameter value is simply ignored, and the first match wins.
>
> This is useful when you have a bunch of submit buttons on a page, and need
> to be able to tell them apart. The value attribute of a submit button is
> also the display text, which is often localized, so it's not a great
> mechanism to have the same button name and use the value to tell the
> buttons apart. However, the name itself can be set different for each
> button, and then this resolver can map based on that.
>
> Colin
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] Spring remoting with Jini?

[Steven D. <ste...@gm...>]

Just for my understanding, are you talking about Jini integration for
Spring or remoting for Spring?

Currently there is no remoting support for JMS since - like Jini -
this is an asynchronous service. Calling a remote method and receiving
a result or exception asynchronously for me lies somewhere between
undoable and very difficult.

Steven

On Thu, 10 Mar 2005 16:27:08 +1300, Ben Piper <Ben...@pe...> wrote:
> Seth said:
>=20
> >As an avid Jini fan (and past user) I can say it should be a great
> >match, and quite easy to do.  I'd be glad to help if you need it.
> >I've often thought about combining Spring and Jini, so I'm glad you
> >brought it up. :)
>=20
> It's nice to know that others have also considered this.  Perhaps I can
> get your thoughts on what I've contemplated thus far:
>=20
> The current implementations of remoting seem to follow a common model of
> intercepting method invocations at the client end and turning them into
> remote service calls.  To follow this model with Jini implies that you
> load a Jini Configuration at some initialisation point, discover the
> service, grab the service proxy, then invoke the intercepted
> MethodInvocation on it.  I'm a little shaky on the Spring stuff... but I
> guess you'd have a JiniProxyFactoryBean to do some initialisation in
> afterPropertiesSet (I imagine you'd set up a LookupCache for the service
> interface in question?).
>=20
> On the remote end, I'm even more uncertain.  I like to think of Jini in
> terms of Rio (a sub-project that makes Jini more accessible to those of
> us in the enterprise application space), as I came upon the two
> simultaneously.  So, you would have a Cybernode 'container' (which is
> itself a service) that can export services as provisioned to it by a
> Provision Monitor.  The question in my mind is where Spring comes into
> the picture.  I see no reason why one couldn't have a JiniRemoteExporter
> of sorts... such that when Spring initialises the bean, the service
> interface is exported... however in the case of Rio, it's actually when
> a service is provisioned to a Cybernode that it's exported.
>=20
> So, within a Cybernode container (or any JVM), I may want to load a
> Spring ApplicationContext, but I might not necessarily want that to
> drive the exporting of services... and that's certainly configurable
> (but you probably wouldn't want to be providing a service within the
> Cybernode container without the Cybernode service itself knowing that
> it's exported it).
>=20
> The context in which I'm looking at this is that a couple of colleagues
> are piloting a fully Spring managed architecture for a web application,
> from MVC to integration with Hibernate, transaction management and all
> that.  What we're just starting to look at now is physically (or
> logically) breaking up the web and application tiers with remoting, for
> which Jini seems an excellent middleware fit, particularly given other
> requirements that we have.
>=20
> I'd be very keen to receive any comments and ideas that you might have.
>=20
>=20
> Abel said:
>=20
> >Ben I'm currently working on JavaSpaces and Spring integration (as a
> side >project) nothing related to remote invocations though.  What I'm
> doing is >putting together something that resembles the JMS stuff in
> Spring but for >JavaSpaces.  The goal is to make the Jini related stuff
> transparent from >the user.
>=20
> So by 'JMS stuff' I take it you mean the org.springframework.jms
> package? Have you been compiling any core support classes for general
> Jini operations, e.g. service discovery/lookup, configuration
> management, etc.? It'd be great to have a common integration point with
> Spring for the core Jini stuff, and use that as a platform for
> JavaSpaces, remoting, and whatever else.  At the moment I'm trying to
> write some fairly case-specific Jini remoting stuff to prove to myself
> that I'm not barking up the wrong tree, but I'm not yet comfortable
> enough with Jini and Spring to be sure what the best way forward is.  I
> have a good application for it though, so I hope to make some progress.
> I'm also interested in JavaSpaces integration for areas outside of
> remote service invocation, although it's not something I'm focusing on
> right now.
>=20
>=20
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_ide95&alloc_id=14396&opclick
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>=20
>

Re: [Springframework-developer] ParameterNameMethodNameResolver

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

Colin,

Good idea, but I think it would be better to integrate both systems in the 
ParameterMethodNameResolver:
1) first try the action=methodname syntax
2) if nothing found, try action:methodName=foobar syntax

Combining the two in 1 MethodNameResolver gives you to opportunity to mix 
and match the 2 techniques in the view. By having 2 resolvers you're forced 
to use one technique or the other.

In the web flow system we originally also had these 2 systems in seperate 
"ParameterExtractors", but we abandoned this in favour of a more powerfull 
approach that supports both systems (and actually a third: image buttons).
Check the following method in the sanbox source tree:

org.springframework.web.flow.support.HttpFlowExecutionManager.searchForRequestParameter(HttpServletRequest 
request, String logicalName, String delimiter)

Maybe it would be good to use that. We could move the method into the main 
source tree and put it on the WebUtils class.

What do you think?

Erwin Vervaet
----- Original Message ----- 
From: "Colin Sampaleanu" <col...@ex...>
To: <spr...@li...>
Sent: Thursday, March 10, 2005 4:55 AM
Subject: [Springframework-developer] ParameterNameMethodNameResolver


> I've added a new resolver for the MultiActionController, 
> ParameterNameMethodNameResolver. Unlike ParameterMethodNameResolver, which 
> looks for a parameter like
>   action=methodname
> where action stays constant, and the value is the method name, 
> ParameterNameMethodNameResolver uses the very existene of a parameter name 
> as an indication to map to a specific method. So feeding it the String 
> mapping array
>   "hello:goodbye", "validate", "colin:nina"
> for example would map to the 'goodbye' method if there was a param 
> 'hello', to the 'validate' method if there was a parameter named 
> 'validate', and to 'nina' if there is a parameter named 'colin'. The 
> request parameter value is simply ignored, and the first match wins.
>
> This is useful when you have a bunch of submit buttons on a page, and need 
> to be able to tell them apart. The value attribute of a submit button is 
> also the display text, which is often localized, so it's not a great 
> mechanism to have the same button name and use the value to tell the 
> buttons apart. However, the name itself can be set different for each 
> button, and then this resolver can map based on that.
>
> Colin
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
> 

[Springframework-developer] ParameterNameMethodNameResolver

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

I've added a new resolver for the MultiActionController, 
ParameterNameMethodNameResolver. Unlike ParameterMethodNameResolver, 
which looks for a parameter like
   action=methodname
where action stays constant, and the value is the method name, 
ParameterNameMethodNameResolver uses the very existene of a parameter 
name as an indication to map to a specific method. So feeding it the 
String mapping array
   "hello:goodbye", "validate", "colin:nina"
for example would map to the 'goodbye' method if there was a param 
'hello', to the 'validate' method if there was a parameter named 
'validate', and to 'nina' if there is a parameter named 'colin'. The 
request parameter value is simply ignored, and the first match wins.

This is useful when you have a bunch of submit buttons on a page, and 
need to be able to tell them apart. The value attribute of a submit 
button is also the display text, which is often localized, so it's not a 
great mechanism to have the same button name and use the value to tell 
the buttons apart. However, the name itself can be set different for 
each button, and then this resolver can map based on that.

Colin

RE: [Springframework-developer] Spring remoting with Jini?

[Ben P. <Ben...@pe...>]

Seth said:

>As an avid Jini fan (and past user) I can say it should be a great
>match, and quite easy to do.  I'd be glad to help if you need it.=20
>I've often thought about combining Spring and Jini, so I'm glad you
>brought it up. :)

It's nice to know that others have also considered this.  Perhaps I can
get your thoughts on what I've contemplated thus far:

The current implementations of remoting seem to follow a common model of
intercepting method invocations at the client end and turning them into
remote service calls.  To follow this model with Jini implies that you
load a Jini Configuration at some initialisation point, discover the
service, grab the service proxy, then invoke the intercepted
MethodInvocation on it.  I'm a little shaky on the Spring stuff... but I
guess you'd have a JiniProxyFactoryBean to do some initialisation in
afterPropertiesSet (I imagine you'd set up a LookupCache for the service
interface in question?).

On the remote end, I'm even more uncertain.  I like to think of Jini in
terms of Rio (a sub-project that makes Jini more accessible to those of
us in the enterprise application space), as I came upon the two
simultaneously.  So, you would have a Cybernode 'container' (which is
itself a service) that can export services as provisioned to it by a
Provision Monitor.  The question in my mind is where Spring comes into
the picture.  I see no reason why one couldn't have a JiniRemoteExporter
of sorts... such that when Spring initialises the bean, the service
interface is exported... however in the case of Rio, it's actually when
a service is provisioned to a Cybernode that it's exported. =20

So, within a Cybernode container (or any JVM), I may want to load a
Spring ApplicationContext, but I might not necessarily want that to
drive the exporting of services... and that's certainly configurable
(but you probably wouldn't want to be providing a service within the
Cybernode container without the Cybernode service itself knowing that
it's exported it).

The context in which I'm looking at this is that a couple of colleagues
are piloting a fully Spring managed architecture for a web application,
from MVC to integration with Hibernate, transaction management and all
that.  What we're just starting to look at now is physically (or
logically) breaking up the web and application tiers with remoting, for
which Jini seems an excellent middleware fit, particularly given other
requirements that we have.

I'd be very keen to receive any comments and ideas that you might have.


Abel said:

>Ben I'm currently working on JavaSpaces and Spring integration (as a
side >project) nothing related to remote invocations though.  What I'm
doing is >putting together something that resembles the JMS stuff in
Spring but for >JavaSpaces.  The goal is to make the Jini related stuff
transparent from >the user.

So by 'JMS stuff' I take it you mean the org.springframework.jms
package? Have you been compiling any core support classes for general
Jini operations, e.g. service discovery/lookup, configuration
management, etc.? It'd be great to have a common integration point with
Spring for the core Jini stuff, and use that as a platform for
JavaSpaces, remoting, and whatever else.  At the moment I'm trying to
write some fairly case-specific Jini remoting stuff to prove to myself
that I'm not barking up the wrong tree, but I'm not yet comfortable
enough with Jini and Spring to be sure what the best way forward is.  I
have a good application for it though, so I hope to make some progress.
I'm also interested in JavaSpaces integration for areas outside of
remote service invocation, although it's not something I'm focusing on
right now.   =20

[Springframework-developer] spring Build Failed

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

<html><head>
<style>
.white { color:#FFFFFF }.index { background-color:#FFFFFF }.index-passed { =
color:#004400 }.index-failed { color:#FF0000; font-weight:bold }.index-head=
er { font-weight:bold }.link { font-family:arial,helvetica,sans-serif; font=
-size:10pt; color:#FFFFFF; text-decoration:none; }.tab-table { margin: 0em =
0em 0.5em 0em; }.tabs { font-family:arial,helvetica,sans-serif; font-size:8=
pt; color:#000000; font-weight:bold; padding: 0em 2em; background-color:#EE=
EEEE; }.tabs-link { color:#000000; text-decoration:none; }.tabs-link:visite=
d { color:#000000; text-decoration:none; }.tabs-selected { font-family:aria=
l,helvetica,sans-serif; font-size:8pt; color:#000000; font-weight:bold; pad=
ding: 0em 2em; }.tabs-selected { border: inset; }.header-title { font-famil=
y:arial,helvetica,sans-serif; font-size:12pt; color:#000000; font-weight:bo=
ld; }.header-label { font-weight:bold; }.header-data { font-family:arial,he=
lvetica,sans-serif; font-size:10pt; color:#000000; }.modifications-data { f=
ont-family:arial,helvetica,sans-serif; font-size:8pt; color:#000000; }.modi=
fications-sectionheader { background-color:#000066; font-family:arial,helve=
tica,sans-serif; font-size:10pt; color:#FFFFFF; }.modifications-oddrow { ba=
ckground-color:#CCCCCC }.modifications-evenrow { background-color:#FFFFCC }=
.changelists-oddrow { background-color:#CCCCCC }.changelists-evenrow { back=
ground-color:#FFFFCC }.changelists-file-spacer { background-color:#FFFFFF }=
.changelists-file-evenrow { background-color:#EEEEEE }.changelists-file-odd=
row { background-color:#FFFFEE }.changelists-file-header { background-color=
:#666666; font-family:arial,helvetica,sans-serif; font-size:8pt; color:#FFF=
FFF; }.compile-data { font-family:arial,helvetica,sans-serif; font-size:8pt=
; color:#000000; }.compile-error-data { font-family:arial,helvetica,sans-se=
rif; font-size:8pt; color:#FF0000; }.compile-warn-data { font-family:arial,=
helvetica,sans-serif; font-size:8pt; color:#CC9900; }.compile-sectionheader=
 { background-color:#000066; font-family:arial,helvetica,sans-serif; font-s=
ize:10pt; color:#FFFFFF; }.distributables-data { font-family:arial,helvetic=
a,sans-serif; font-size:8pt; color:#000000; }.distributables-sectionheader =
{ background-color:#000066; font-family:arial,helvetica,sans-serif; font-si=
ze:10pt; color:#FFFFFF; }.distributables-oddrow { background-color:#CCCCCC =
}.unittests-sectionheader { background-color:#000066; font-family:arial,hel=
vetica,sans-serif; font-size:10pt; color:#FFFFFF; }.unittests-oddrow { back=
ground-color:#CCCCCC }.unittests-data { font-family:arial,helvetica,sans-se=
rif; font-size:8pt; color:#000000; }.unittests-error { font-family:arial,he=
lvetica,sans-serif; font-size:8pt; color:#901090; }.unittests-failure { fon=
t-family:arial,helvetica,sans-serif; font-size:8pt; color:#FF0000; }.checks=
tyle-oddrow { background-color:#CCCCCC }.checkstyle-data { font-family:aria=
l,helvetica,sans-serif; font-size:8pt; color:#000000; }.checkstyle-sectionh=
eader { background-color:#000066; font-family:arial,helvetica,sans-serif; f=
ont-size:10pt; color:#FFFFFF; }
</style>
</head><body>
<p>
<table width=3D"98%" border=3D"0" cellspacing=3D"0" cellpadding=3D"2" align=
=3D"center"><tr><td class=3D"header-title">BUILD FAILED</td></tr><tr><td cl=
ass=3D"header-data"><span class=3D"header-label">Ant Error Message:&nbsp;</=
span>/jteam/build2/checkout/spring/spring/build.xml:482: Tests failed</td><=
/tr><tr><td class=3D"header-data"><span class=3D"header-label">Date of buil=
d:&nbsp;</span>03/10/2005 00:16:02</td></tr><tr><td class=3D"header-data"><=
span class=3D"header-label">Time to build:&nbsp;</span>1 minute 58 seconds<=
/td></tr><tr><td class=3D"header-data"><span class=3D"header-label">Last ch=
anged:&nbsp;</span>03/09/2005 00:18:53</td></tr><tr><td class=3D"header-dat=
a"><span class=3D"header-label">Last log entry:&nbsp;</span>polishing</td><=
/tr></table><p>
<p>
<p>
<table xmlns=3D"http://www.w3.org/TR/html4/strict.dtd" width=3D"98%" border=
=3D"0" cellspacing=3D"0" cellpadding=3D"2" align=3D"center"><tr><td class=
=3D"compile-sectionheader">                        &nbsp;Errors/Warnings: (=
1270)                    </td></tr><tr><td><pre class=3D"compile-data">Note=
: Some input files use or override a deprecated API.<br class=3D"none"/>Not=
e: Recompile with -deprecation for details.<br class=3D"none"/>Note: /jteam=
/build2/checkout/spring/spring/mock/org/springframework/mock/web/MockHttpSe=
ssion.java uses or overrides a deprecated API.<br class=3D"none"/>Note: Rec=
ompile with -deprecation for details.<br class=3D"none"/>Note: Some input f=
iles use or override a deprecated API.<br class=3D"none"/>Note: Recompile w=
ith -deprecation for details.<br class=3D"none"/></pre></td></tr></table><p=
>
<p>
<table width=3D"98%" border=3D"0" cellspacing=3D"0" cellpadding=3D"2" align=
=3D"center"><tr><td colspan=3D"4" class=3D"unittests-sectionheader">       =
            &nbsp;Unit Tests: (1554)                </td></tr><tr><td><tabl=
e width=3D"98%" border=3D"0" cellspacing=3D"0" cellpadding=3D"2" align=3D"c=
enter"><tr><td class=3D"unittests-data">                error            </=
td><td width=3D"40%" class=3D"unittests-data">testStartupWithSuppliedServer=
</td><td width=3D"40%" class=3D"unittests-data">org.springframework.jmx.sup=
port.ConnectorServerFactoryBeanTests</td></tr></table></td></tr><tr></tr><t=
r><td colspan=3D"2">&nbsp;</td></tr><tr><td colspan=3D"4" class=3D"unittest=
s-sectionheader">                    &nbsp;Unit Test Error Details:&nbsp;(1=
)                </td></tr><tr><td class=3D"unittests-data" colspan=3D"2"> =
               Test:&nbsp;testStartupWithSuppliedServer</td></tr><tr><td cl=
ass=3D"unittests-data" colspan=3D"2">                Class:&nbsp;org.spring=
framework.jmx.support.ConnectorServerFactoryBeanTests</td></tr><tr><td clas=
s=3D"unittests-data" colspan=3D"2">                    Type: java.net.BindE=
xception</td></tr><tr><td class=3D"unittests-data" colspan=3D"2">          =
      Message: Address already in use</td></tr><tr><td class=3D"unittests-e=
rror" colspan=3D"2"><PRE>java.net.BindException: Address already in use<br>=
=09at java.net.PlainSocketImpl.socketBind(Native Method)<br>=09at java.net.=
PlainSocketImpl.bind(PlainSocketImpl.java:331)<br>=09at java.net.ServerSock=
et.bind(ServerSocket.java:318)<br>=09at sun.reflect.NativeMethodAccessorImp=
l.invoke0(Native Method)<br>=09at sun.reflect.NativeMethodAccessorImpl.invo=
ke(NativeMethodAccessorImpl.java:39)<br>=09at sun.reflect.DelegatingMethodA=
ccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)<br>=09at com.sun.j=
mx.remote.socket.SocketConnectionServer.start(SocketConnectionServer.java:1=
28)<br>=09at com.sun.jmx.remote.generic.SynchroMessageConnectionServerImpl.=
start(SynchroMessageConnectionServerImpl.java:39)<br>=09at javax.management=
.remote.generic.GenericConnectorServer.start(GenericConnectorServer.java:23=
5)<br>=09at org.springframework.jmx.support.ConnectorServerFactoryBean.star=
t(ConnectorServerFactoryBean.java:207)<br>=09at org.springframework.jmx.sup=
port.ConnectorServerFactoryBeanTests.testStartupWithSuppliedServer(Connecto=
rServerFactoryBeanTests.java:50)<br>=09at sun.reflect.NativeMethodAccessorI=
mpl.invoke0(Native Method)<br>=09at sun.reflect.NativeMethodAccessorImpl.in=
voke(NativeMethodAccessorImpl.java:39)<br>=09at sun.reflect.DelegatingMetho=
dAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)</PRE></td></tr><=
tr><td colspan=3D"2">&nbsp;</td></tr></table><p>
<table width=3D"98%" border=3D"0" cellspacing=3D"1" cellpadding=3D"2" align=
=3D"center"><tr><td colspan=3D"6" class=3D"modifications-sectionheader">   =
                 &nbsp;Modifications since last build:&nbsp;               =
     (2)                </td></tr><tr class=3D"modifications-evenrow"><td c=
lass=3D"modifications-data">modified</td><td class=3D"modifications-data">j=
hoeller</td><td class=3D"modifications-data">src/org/springframework/transa=
ction/interceptor/AttributesTransactionAttributeSource.java</td><td class=
=3D"modifications-data">polishing</td></tr><tr class=3D"modifications-oddro=
w"><td class=3D"modifications-data">modified</td><td class=3D"modifications=
-data">jhoeller</td><td class=3D"modifications-data">src/org/springframewor=
k/metadata/Attributes.java</td><td class=3D"modifications-data">polishing</=
td></tr></table><p>
<table width=3D"98%" border=3D"0" cellspacing=3D"0" cellpadding=3D"2" align=
=3D"center"><tr><td class=3D"distributables-sectionheader">                =
        &nbsp;Deployments by this build:&nbsp;(10)                    </td>=
</tr><tr><td class=3D"distributables-data">Building jar: /jteam/build2/chec=
kout/spring/spring/dist/spring-core.jar</td></tr><tr class=3D"distributable=
s-oddrow"><td class=3D"distributables-data">Building jar: /jteam/build2/che=
ckout/spring/spring/dist/spring-aop.jar</td></tr><tr><td class=3D"distribut=
ables-data">Building jar: /jteam/build2/checkout/spring/spring/dist/spring-=
dao.jar</td></tr><tr class=3D"distributables-oddrow"><td class=3D"distribut=
ables-data">Building jar: /jteam/build2/checkout/spring/spring/dist/spring-=
context.jar</td></tr><tr><td class=3D"distributables-data">Building jar: /j=
team/build2/checkout/spring/spring/dist/spring-web.jar</td></tr><tr class=
=3D"distributables-oddrow"><td class=3D"distributables-data">Building jar: =
/jteam/build2/checkout/spring/spring/dist/spring-webmvc.jar</td></tr><tr><t=
d class=3D"distributables-data">Building jar: /jteam/build2/checkout/spring=
/spring/dist/spring-remoting.jar</td></tr><tr class=3D"distributables-oddro=
w"><td class=3D"distributables-data">Building jar: /jteam/build2/checkout/s=
pring/spring/dist/spring-orm.jar</td></tr><tr><td class=3D"distributables-d=
ata">Building jar: /jteam/build2/checkout/spring/spring/dist/spring.jar</td=
></tr><tr class=3D"distributables-oddrow"><td class=3D"distributables-data"=
>Building jar: /jteam/build2/checkout/spring/spring/dist/spring-mock.jar</t=
d></tr></table>
</body></html>

[Springframework-developer] Minor bug in reference documentation

[Jan Z. <Ja...@zu...>]

Hello,

there's a minor bug in the reference documentation 
(http://www.springframework.org/docs/reference/remoting.html).

In section "17.2.2. Linking in the service at the client" the second sample 
should be

<bean class="example.SimpleObject">
 <property name="accountService"><ref bean="accountService"/></property>
</bean>
[...]

instead of

<bean class="example.SimpleObject">
 <property name="accountService"><ref bean="accountService"/></bean>
</bean>
[...]


Jan

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

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

1110385665
FAILED

    [junit] Testcase: testNaming took 0,007 sec
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,029 sec
    [junit] Testsuite: org.springframework.jmx.export.naming.PropertiesNamingStrategyTests
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,029 sec

    [junit] Testcase: testNaming took 0 sec
    [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 0,197 sec
    [junit] Testsuite: org.springframework.jmx.support.ConnectorServerFactoryBeanTests
    [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 0,197 sec

    [junit] Testcase: testStartupWithLocatedServer took 0,083 sec
    [junit] Testcase: testStartupWithSuppliedServer took 0,067 sec
    [junit] 	Caused an ERROR
    [junit] Address already in use
    [junit] java.net.BindException: Address already in use
    [junit] 	at java.net.PlainSocketImpl.socketBind(Native Method)
    [junit] 	at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:321)
    [junit] 	at java.net.ServerSocket.bind(ServerSocket.java:308)
    [junit] 	at sun.reflect.GeneratedMethodAccessor139.invoke(Unknown Source)
    [junit] 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [junit] 	at com.sun.jmx.remote.socket.SocketConnectionServer.start(SocketConnectionServer.java:128)
    [junit] 	at com.sun.jmx.remote.generic.SynchroMessageConnectionServerImpl.start(SynchroMessageConnectionServerImpl.java:39)
    [junit] 	at javax.management.remote.generic.GenericConnectorServer.start(GenericConnectorServer.java:235)
    [junit] 	at org.springframework.jmx.support.ConnectorServerFactoryBean.start(ConnectorServerFactoryBean.java:207)
    [junit] 	at org.springframework.jmx.support.ConnectorServerFactoryBeanTests.testStartupWithSuppliedServer(ConnectorServerFactoryBeanTests.java:50)
    [junit] 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [junit] 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [junit] 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)


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] FAILED BUILD: x86-solaris1 (last 30 lines included)

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

1110381970
FAILED
    [junit] Testcase: testNaming took 0,008 sec
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,021 sec
    [junit] Testsuite: org.springframework.jmx.export.naming.PropertiesNamingStrategyTests
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,021 sec

    [junit] Testcase: testNaming took 0,001 sec
    [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 0,717 sec
    [junit] Testsuite: org.springframework.jmx.support.ConnectorServerFactoryBeanTests
    [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 0,717 sec

    [junit] Testcase: testStartupWithLocatedServer took 0,615 sec
    [junit] Testcase: testStartupWithSuppliedServer took 0,057 sec
    [junit] 	Caused an ERROR
    [junit] Address already in use
    [junit] java.net.BindException: Address already in use
    [junit] 	at java.net.PlainSocketImpl.socketBind(Native Method)
    [junit] 	at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:331)
    [junit] 	at java.net.ServerSocket.bind(ServerSocket.java:318)
    [junit] 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [junit] 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [junit] 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [junit] 	at com.sun.jmx.remote.socket.SocketConnectionServer.start(SocketConnectionServer.java:128)
    [junit] 	at com.sun.jmx.remote.generic.SynchroMessageConnectionServerImpl.start(SynchroMessageConnectionServerImpl.java:39)
    [junit] 	at javax.management.remote.generic.GenericConnectorServer.start(GenericConnectorServer.java:235)
    [junit] 	at org.springframework.jmx.support.ConnectorServerFactoryBean.start(ConnectorServerFactoryBean.java:207)
    [junit] 	at org.springframework.jmx.support.ConnectorServerFactoryBeanTests.testStartupWithSuppliedServer(ConnectorServerFactoryBeanTests.java:50)
    [junit] 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [junit] 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [junit] 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)


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] Spring remoting with Jini?

[Seth L. <set...@gm...>]

> I'm just curious as to whether anyone has considered building support into
> Spring's remoting framework for remote service invocation via Jini? 
> 
>   
> 
> The reason I ask is that I'm hoping to integrate the two for some prototype
> work, and am apprehensive about striking out on my own when others may have
> gone or are currently going down this path.  I'm fairly new to both Jini and
> Spring.  Are there any Jini experts/followers in the Spring developer
> community who'd care to comment? 

Ben,

As an avid Jini fan (and past user) I can say it should be a great
match, and quite easy to do.  I'd be glad to help if you need it. 
I've often thought about combining Spring and Jini, so I'm glad you
brought it up. :)

Seth

-- 
<a href="http://www.picklematrix.net/foaf.rdf">Seth Ladd's FOAF</a>
<a href="http://www.foaf-project.org/">What is FOAF?</a>

RE: [Springframework-developer] Spring remoting with Jini?

[Abel P. <abl...@pa...>]

Ben wrote:
>I'm just curious as to whether anyone has considered building support into
Spring's remoting framework for remote service invocation via Jini?



Ben I'm currently working on JavaSpaces and Spring integration (as a side
project) nothing related to remote invocations though.  What I'm doing is
putting together something that resembles the JMS stuff in Spring but for
JavaSpaces.  The goal is to make the Jini related stuff transparent from the
user.



- Abel

  -----Original Message-----
  From: spr...@li...
[mailto:spr...@li...]On Behalf Of
Ben Piper
  Sent: Tuesday, March 08, 2005 8:58 PM
  To: spr...@li...
  Subject: [Springframework-developer] Spring remoting with Jini?


  Hi all,



  I'm just curious as to whether anyone has considered building support into
Spring's remoting framework for remote service invocation via Jini?



  The reason I ask is that I'm hoping to integrate the two for some
prototype work, and am apprehensive about striking out on my own when others
may have gone or are currently going down this path.  I'm fairly new to both
Jini and Spring.  Are there any Jini experts/followers in the Spring
developer community who'd care to comment?



  Ben

[Springframework-developer] Spring remoting with Jini?

[Ben P. <Ben...@pe...>]

Hi all,

=20

I'm just curious as to whether anyone has considered building support
into Spring's remoting framework for remote service invocation via Jini?


=20

The reason I ask is that I'm hoping to integrate the two for some
prototype work, and am apprehensive about striking out on my own when
others may have gone or are currently going down this path.  I'm fairly
new to both Jini and Spring.  Are there any Jini experts/followers in
the Spring developer community who'd care to comment?

=20

Ben

[Springframework-developer] Re: Portlet Form Controllers

[John L. <jl...@ar...>]

I agree that it could go either way.  The reasons I might be supportive 
of making it part of core Spring are that the number of classes is 
relatively small (around 30 at this point), and that it is all pretty 
tightly coupled with the web servlet framework.  But I could go either 
way with it.

I would be happy to volunteer to be a dedicated developer for the 
portlet framework.  We are going to be using it extensively for the next 
few years so we have a big vested interest in making it work well.

I'd love to go ahead and commit the new controller hierarchy into the 
sandbox.  What would it take to get approved to do that?  Juergen, my 
SourceForge user ID is 'johnalewis' if that is all you need.

Thanks!
John

Juergen Hoeller wrote:
> We don't need to vote right now; we're just gathering opinions :-)
> 
> The decision will also depend on the final size of the Portlet support. If
> it turns out to be too small for a separate subproject, including it in the
> core distribution might be the only feasible way to go.
> 
> Juergen
> 
> 
> -----Original Message-----
> From: spr...@li...
> [mailto:spr...@li...]On Behalf
> Of Ken Krebs
> Sent: Friday, March 04, 2005 11:47 PM
> To: spr...@li...
> Subject: Re: [Springframework-developer] Portlet Form Controllers
> 
> 
> +1 for subproject status.
> It makes sense to me to let them evolve in a more loosely coupled way,
> especially as Juergen points out given the small target audience for
> portlets.
> 
> Juergen Hoeller wrote:
> 
> 
>>As I said, a subproject is just under consideration. The alternative is to
>>release the portlet support as part of the core Spring 1.3 distribution.
> 
> The
> 
>>rationale of factoring out subprojects is to let the core concentrate on
> 
> its
> 
>>current scope and not introduce completely new areas of functionality. A
>>secondary goal is to limit the size of spring.jar.
>>
>>The current core web support and web MVC framework is used by the portlet
>>support underneath, for example to render views (at least that was the case
>>last year). So Spring Portlet depends on Spring core web (even core web
>>MVC), but not the other way round: a case for core web MVC staying part of
>>the core distribution, but Portlet support (optionally) becoming a separate
>>subproject.
>>
>>Note that Spring's core web support is of interest to many people: not only
>>to web application people, but also to rich client developers accessing
>>HTTP-based remote services (running in a Servlet container). Portlet
> 
> support
> 
>>is more specific and has a narrower target audience.
>>
>>A further advantage of a separate subproject is that it can evolve more
>>easily. Specific sample applications, tutorials, tools etc can be added
>>without having to worry about scope or size of the core Spring
> 
> distribution.
> 
>>Anyway, this has not been decided yet and does not have to be decided right
>>now. It's gonna become an important topic after the Spring 1.2 release,
>>though.
>>
>>Juergen
>>
>>
>>
>>-----Original Message-----
>>From: spr...@li...
>>[mailto:spr...@li...]On Behalf
>>Of Jean-Pol Landrain
>>Sent: Friday, March 04, 2005 7:29 PM
>>To: spr...@li...
>>Subject: Re: [Springframework-developer] Portlet Form Controllers
>>
>>
>>I quite agree with Rob. Except, of course, if you plan to create a
>>subproject for Spring MVC too. This would allow a Spring "à la carte".
>>This would keep the framework light, but would perhaps be a bit confusing
> 
> to
> 
>>the users. Perhaps a "plugin" functionnality would be nice if the number of
>>projects grows : you would have a core Spring and be able to plug in, for
>>example by using a dedicated XML file, the other sub-projects you want to
>>use. That's just an idea.
>>
>>Cheers,
>>Jean-Pol.
>>
>>----- Original Message -----
>>From: "Rob Butler" <cro...@ya...>
>>To: <spr...@li...>
>>Sent: Friday, March 04, 2005 7:01 PM
>>Subject: Re: [Springframework-developer] Portlet Form Controllers
>>
>>
>>
>>
>>
>>>Why would you have a separate sub-project for the
>>>portlet support in Spring?  That would be like having
>>>a separate sub-project for the web MVC stuff, and a
>>>separate sub-project for the DAO related stuff, and
>>>another one for AOP, etc.
>>>
>>>Later
>>>Rob
>>>--- Juergen Hoeller <ju...@in...> wrote:
>>>
>>>
>>>
>>>
>>>>Sounds like good stuff :-)
>>>>
>>>>On this occasion: Let's discuss the road to an
>>>>official release of the
>>>>Portlet support. We consider releasing the Portlet
>>>>support as an official
>>>>subproject, i.e. as a separate distribution and with
>>>>a separate CVS module
>>>>(or even separate CVS repository). The association
>>>>would be similar to the
>>>>just-announced Spring subproject status of Acegi
>>>>Security, and the already
>>>>established status of Spring RCP.
>>>>
>>>>Very importantly, the portlet subproject needs a
>>>>dedicated developer team.
>>>>Any volunteers? :-)
>>>>
>>>>Juergen
>>>>
>>>>
>>>>-----Original Message-----
>>>>From:
>>>>
>>>>
>>>>
>>>
>>>spr...@li...
>>>
>>>
>>>[mailto:spr...@li...]On
>>>
>>>
>>>
>>>>Behalf
>>>>Of John Lewis
>>>>Sent: Thursday, March 03, 2005 6:53 PM
>>>>To: spr...@li...
>>>>Subject: [Springframework-developer] Portlet Form
>>>>Controllers
>>>>
>>>>
>>>>We've been working on porting a fairly complex
>>>>enterprise application
>>>
>>>>from the Spring Servlet MVC framework to the Spring
>>>
>>>>Portlet MVC
>>>>framework.  As Nick Lothian and Rainer Schmitz
>>>>discovered, the Form
>>>>Controller hierarchy is difficult to port over from
>>>>the Servlet area to
>>>>the Portlet area because of the two-phase nature of
>>>>portlet requests.
>>>>Since we were porting a large number of existing
>>>>controllers descended
>>>
>>>>from AbstractController, AbstractFormController, or
>>>
>>>>SimpleFormController, it was critical to that all
>>>>the former
>>>>functionality of these parent be present and that
>>>>our logic work the
>>>>same as before.
>>>>
>>>>Nick Lothian's version of
>>>>SimplePortletFormController gave us a good
>>>>starting point and helped us understand a lot of the
>>>>issues with portlet
>>>>development in general and with Spring portlets in
>>>>particular.  However,
>>>>a lot of our controllers manage database content, so
>>>>we needed proper
>>>>separation between the action and render phase of
>>>>the request, which
>>>>this controller did not give us.
>>>>
>>>>Rainer Schmitz's work went much further and provided
>>>>the traditional
>>>>hierarchy of controllers and further demonstrated
>>>>the issues with
>>>>separating out the two phases of the portlet
>>>>request.  However, these
>>>>still did not give us the complete control that we
>>>>needed.  We
>>>>especially needed a version of SimpleFormController
>>>>that could handle
>>>>the separation of the action logic from the render
>>>>logic.
>>>>
>>>>Over the past few months we have developed a new set
>>>>of the
>>>>AbstractController, BaseCommandController,
>>>>AbstractFormController, and
>>>>SimpleFormController classes that we think
>>>>rigorously address all the
>>>>issues with portlet development and that have
>>>>allowed us to port over
>>>>existing servlet controllers with relative ease.
>>>>
>>>>We've included a portlet version of
>>>>WebContentGenerator to give the
>>>>controller classes their proper ancestry and provide
>>>>control over things
>>>>like content caching and access to the web
>>>>application context and to
>>>>centralized logging.
>>>>
>>>>We've also create a new set of the binding classes
>>>>(PortletRequestDataBinder,
>>>>PortletRequestParameterPropertyValues and
>>>>PortletRequestBindingException) that support special
>>>>field markers,
>>>>correct problems with form elements such as radio
>>>>buttons and
>>>>checkboxes, and handle redisplay of invalid submits
>>>>of non-string
>>>>parameters properly.
>>>>
>>>>All of the classes are fully documented, including
>>>>workflow descriptions
>>>>in the controllers that cover the special nature of
>>>>portlet development.
>>>>
>>>>Our hope is that these classes can handle the needs
>>>>of everyone working
>>>>with form controllers in Spring portlets and that
>>>>these can be merged
>>>>into the sandbox source code.
>>>>
>>>>The classes are posted in a zip file on the Spring
>>>>Portlet Wiki page at:
>>>>
>>>>
>>>>
>>>
>>>http://opensource.atlassian.com/confluence/spring/display/JSR168/
>>>
>>>
>>>
>>>>The link to the file is (sorry for the long link):
>>>>
>>>>
>>>>
>>
>>http://opensource.atlassian.com/confluence/spring/download/attachments/10/s
> 
> p
> 
>>
>>>>ring-portlet-controllers.zip
>>>>
>>>>Please send me any questions or comments you may
>>>>have about these
>>>>classes.  We are eager to support their adoption in
>>>>the Spring Portlet
>>>>community.
>>>>
>>>>John Lewis
>>>>jl...@ar...

[Springframework-developer] Hibernate 3 annotations in 1.2 rc1

[Washusen, D. <Dan...@se...>]

Hey guys,

I've bean mucking around with Hibernate 3 (with annotations) support in
nightly build.  All is going well but I thought I would offer some
feedback...

=0D

1.	I had to extend the
org.springframework.orm.hibernate3.LocalSessionFactoryBean class and
override the newConfiguration() method to return an instance of
org.hibernate.cfg.AnnotationConfiguration.
2.	I then moved the list of mappings (from hibernate2) specified by
mappingResources into the hibernate.cfg.xml file (using the format
specified by the Hibernate annotations page) and specified the location
using the configLocation property.

=0D

Pretty easy really...

=0D

A provided extension of LocalSessionFactoryBean that had support for
annotated classes would be nice.  The bean definition could look
something like:

<bean id=3D"sessionFactory"
class=3D"org.springframework.orm.hibernate3.AnnotationsLocalSessionFactory
Bean">

        <property name=3D"dataSource">

            <ref local=3D"dataSource"/>

        </property>

        <property name=3D"mappingPackage">

            <value>some.package</value>

        </property>

        <property name=3D"annotatedClasses">

            <list>

                <value>com.package.Foo</value>

                <value>com.package.Bar</value>

            </list>

        </property>

    </bean>

=0D

Cheers,

Dan



www.sensis.com.au

A leading Australian advertising, information=0D
and directories business.=0D

www.yellowpages.com.au
www.whitepages.com.au
www.citysearch.com.au
www.whereis.com.au
www.telstra.com.au
www.tradingpost.com.au

This email and any attachments are intended only for the use of the=
 recipient and may be confidential and/or legally privileged.
Sensis Pty Ltd disclaims liability for any errors, omissions, viruses, loss=
 and/or damage arising from using, opening or transmitting this email.
If you are not the intended recipient you must not use, interfere with,=
 disclose, copy or retain this email and you should notify the sender=
 immediately by return email or by contacting Sensis Pty Ltd by telephone=
 on [+61 3 8653 5000]

[Springframework-developer] spring build.220 Build Successful

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

<html><head>
<style>
.white { color:#FFFFFF }.index { background-color:#FFFFFF }.index-passed { =
color:#004400 }.index-failed { color:#FF0000; font-weight:bold }.index-head=
er { font-weight:bold }.link { font-family:arial,helvetica,sans-serif; font=
-size:10pt; color:#FFFFFF; text-decoration:none; }.tab-table { margin: 0em =
0em 0.5em 0em; }.tabs { font-family:arial,helvetica,sans-serif; font-size:8=
pt; color:#000000; font-weight:bold; padding: 0em 2em; background-color:#EE=
EEEE; }.tabs-link { color:#000000; text-decoration:none; }.tabs-link:visite=
d { color:#000000; text-decoration:none; }.tabs-selected { font-family:aria=
l,helvetica,sans-serif; font-size:8pt; color:#000000; font-weight:bold; pad=
ding: 0em 2em; }.tabs-selected { border: inset; }.header-title { font-famil=
y:arial,helvetica,sans-serif; font-size:12pt; color:#000000; font-weight:bo=
ld; }.header-label { font-weight:bold; }.header-data { font-family:arial,he=
lvetica,sans-serif; font-size:10pt; color:#000000; }.modifications-data { f=
ont-family:arial,helvetica,sans-serif; font-size:8pt; color:#000000; }.modi=
fications-sectionheader { background-color:#000066; font-family:arial,helve=
tica,sans-serif; font-size:10pt; color:#FFFFFF; }.modifications-oddrow { ba=
ckground-color:#CCCCCC }.modifications-evenrow { background-color:#FFFFCC }=
.changelists-oddrow { background-color:#CCCCCC }.changelists-evenrow { back=
ground-color:#FFFFCC }.changelists-file-spacer { background-color:#FFFFFF }=
.changelists-file-evenrow { background-color:#EEEEEE }.changelists-file-odd=
row { background-color:#FFFFEE }.changelists-file-header { background-color=
:#666666; font-family:arial,helvetica,sans-serif; font-size:8pt; color:#FFF=
FFF; }.compile-data { font-family:arial,helvetica,sans-serif; font-size:8pt=
; color:#000000; }.compile-error-data { font-family:arial,helvetica,sans-se=
rif; font-size:8pt; color:#FF0000; }.compile-warn-data { font-family:arial,=
helvetica,sans-serif; font-size:8pt; color:#CC9900; }.compile-sectionheader=
 { background-color:#000066; font-family:arial,helvetica,sans-serif; font-s=
ize:10pt; color:#FFFFFF; }.distributables-data { font-family:arial,helvetic=
a,sans-serif; font-size:8pt; color:#000000; }.distributables-sectionheader =
{ background-color:#000066; font-family:arial,helvetica,sans-serif; font-si=
ze:10pt; color:#FFFFFF; }.distributables-oddrow { background-color:#CCCCCC =
}.unittests-sectionheader { background-color:#000066; font-family:arial,hel=
vetica,sans-serif; font-size:10pt; color:#FFFFFF; }.unittests-oddrow { back=
ground-color:#CCCCCC }.unittests-data { font-family:arial,helvetica,sans-se=
rif; font-size:8pt; color:#000000; }.unittests-error { font-family:arial,he=
lvetica,sans-serif; font-size:8pt; color:#901090; }.unittests-failure { fon=
t-family:arial,helvetica,sans-serif; font-size:8pt; color:#FF0000; }.checks=
tyle-oddrow { background-color:#CCCCCC }.checkstyle-data { font-family:aria=
l,helvetica,sans-serif; font-size:8pt; color:#000000; }.checkstyle-sectionh=
eader { background-color:#000066; font-family:arial,helvetica,sans-serif; f=
ont-size:10pt; color:#FFFFFF; }
</style>
</head><body>
<p>
<table width=3D"98%" border=3D"0" cellspacing=3D"0" cellpadding=3D"2" align=
=3D"center"><tr><td class=3D"header-title">BUILD COMPLETE&nbsp;-&nbsp;     =
               build.220</td></tr><tr><td class=3D"header-data"><span class=
=3D"header-label">Date of build:&nbsp;</span>03/09/2005 00:15:48</td></tr><=
tr><td class=3D"header-data"><span class=3D"header-label">Time to build:&nb=
sp;</span>23 minutes 2 seconds</td></tr><tr><td class=3D"header-data"><span=
 class=3D"header-label">Last changed:&nbsp;</span>03/08/2005 19:20:29</td><=
/tr><tr><td class=3D"header-data"><span class=3D"header-label">Last log ent=
ry:&nbsp;</span>removed unnecessary imports</td></tr></table><p>
<p>
<p>
<table xmlns=3D"http://www.w3.org/TR/html4/strict.dtd" width=3D"98%" border=
=3D"0" cellspacing=3D"0" cellpadding=3D"2" align=3D"center"><tr><td class=
=3D"compile-sectionheader">                        &nbsp;Errors/Warnings: (=
1372)                    </td></tr><tr><td><pre class=3D"compile-error-data=
">Test org.springframework.apptests.jpetstore.AllTests FAILEDTest org.sprin=
gframework.apptests.jpetstore.AllTests FAILED<br class=3D"none"/>Java Resul=
t: 2<br class=3D"none"/>Java Result: 2<br class=3D"none"/>Java Result: 2<br=
 class=3D"none"/>Java Result: 1<br class=3D"none"/></pre></td></tr><tr><td>=
<pre class=3D"compile-data">Note: Some input files use or override a deprec=
ated API.<br class=3D"none"/>Note: Recompile with -deprecation for details.=
<br class=3D"none"/>Note: /jteam/build2/checkout/spring/spring/mock/org/spr=
ingframework/mock/web/MockHttpSession.java uses or overrides a deprecated A=
PI.<br class=3D"none"/>Note: Recompile with -deprecation for details.<br cl=
ass=3D"none"/>Note: Some input files use or override a deprecated API.<br c=
lass=3D"none"/>Note: Recompile with -deprecation for details.<br class=3D"n=
one"/>09.03.2005 00:22:12 java.util.prefs.FileSystemPreferences syncWorld<b=
r class=3D"none"/>WARNUNG: Couldn't flush system prefs: java.util.prefs.Bac=
kingStoreException: java.io.FileNotFoundException: /etc/.java/.systemPrefs/=
prefs.tmp (Permission denied)<br class=3D"none"/>09.03.2005 00:22:42 java.u=
til.prefs.FileSystemPreferences syncWorld<br class=3D"none"/>WARNUNG: Could=
n't flush system prefs: java.util.prefs.BackingStoreException: java.io.File=
NotFoundException: /etc/.java/.systemPrefs/prefs.tmp (Permission denied)<br=
 class=3D"none"/>#  -------------------------------------------------------=
---------<br class=3D"none"/>#<br class=3D"none"/>#  Spring Autobuilds - au=
tomatic application deployment and testing<br class=3D"none"/>#<br class=3D=
"none"/>#  target application: buildtest<br class=3D"none"/>#  target serve=
r: tomcat4<br class=3D"none"/>#<br class=3D"none"/>#  this output is record=
ed in the file:<br class=3D"none"/>#  ../../target/autobuilds/reports/build=
test_tomcat4_build_2005-03-09.log<br class=3D"none"/>#  -------------------=
---------------------------------------------<br class=3D"none"/>waiting 75=
 seconds for server to warmup...<br class=3D"none"/>#  --------------------=
--------------------------------------------<br class=3D"none"/>#  Starting=
 unit tests for buildtest<br class=3D"none"/>#  ---------------------------=
-------------------------------------<br class=3D"none"/>Rhino classes (js.=
jar) not found - Javascript disabled<br class=3D"none"/>##  ---------------=
-------------------------------------------------<br class=3D"none"/>##  St=
opping server tomcat4<br class=3D"none"/>##  ------------------------------=
----------------------------------<br class=3D"none"/>##  -----------------=
-----------------------------------------------<br class=3D"none"/>##  Star=
ting server tomcat4<br class=3D"none"/>##  --------------------------------=
--------------------------------<br class=3D"none"/>#  --------------------=
--------------------------------------------<br class=3D"none"/>#<br class=
=3D"none"/>#  Spring Autobuilds - automatic application deployment and test=
ing<br class=3D"none"/>#<br class=3D"none"/>#  target application: buildtes=
t<br class=3D"none"/>#  target server: tomcat5<br class=3D"none"/>#<br clas=
s=3D"none"/>#  this output is recorded in the file:<br class=3D"none"/>#  .=
./../target/autobuilds/reports/buildtest_tomcat5_build_2005-03-09.log<br cl=
ass=3D"none"/>#  ----------------------------------------------------------=
------<br class=3D"none"/>waiting 75 seconds for server to warmup...<br cla=
ss=3D"none"/>#  -----------------------------------------------------------=
-----<br class=3D"none"/>#  Starting unit tests for buildtest<br class=3D"n=
one"/>#  ----------------------------------------------------------------<b=
r class=3D"none"/>Rhino classes (js.jar) not found - Javascript disabled<br=
 class=3D"none"/>##  ------------------------------------------------------=
----------<br class=3D"none"/>##  Stopping server tomcat5<br class=3D"none"=
/>##  ----------------------------------------------------------------<br c=
lass=3D"none"/>##  --------------------------------------------------------=
--------<br class=3D"none"/>##  Starting server tomcat5<br class=3D"none"/>=
##  ----------------------------------------------------------------<br cla=
ss=3D"none"/>#  -----------------------------------------------------------=
-----<br class=3D"none"/>#<br class=3D"none"/>#  Spring Autobuilds - automa=
tic application deployment and testing<br class=3D"none"/>#<br class=3D"non=
e"/>#  target application: buildtest<br class=3D"none"/>#  target server: j=
etty4<br class=3D"none"/>#<br class=3D"none"/>#  this output is recorded in=
 the file:<br class=3D"none"/>#  ../../target/autobuilds/reports/buildtest_=
jetty4_build_2005-03-09.log<br class=3D"none"/>#  -------------------------=
---------------------------------------<br class=3D"none"/>waiting 75 secon=
ds for server to warmup...<br class=3D"none"/>#  --------------------------=
--------------------------------------<br class=3D"none"/>#  Starting unit =
tests for buildtest<br class=3D"none"/>#  ---------------------------------=
-------------------------------<br class=3D"none"/>Rhino classes (js.jar) n=
ot found - Javascript disabled<br class=3D"none"/>##  ---------------------=
-------------------------------------------<br class=3D"none"/>##  Stopping=
 server jetty4<br class=3D"none"/>##  -------------------------------------=
---------------------------<br class=3D"none"/>##  ------------------------=
----------------------------------------<br class=3D"none"/>##  Starting se=
rver jetty4<br class=3D"none"/>##  ----------------------------------------=
------------------------<br class=3D"none"/>#  ----------------------------=
------------------------------------<br class=3D"none"/>#<br class=3D"none"=
/>#  Spring Autobuilds - automatic application deployment and testing<br cl=
ass=3D"none"/>#<br class=3D"none"/>#  target application: jpetstore<br clas=
s=3D"none"/>#  target server: tomcat4<br class=3D"none"/>#<br class=3D"none=
"/>#  this output is recorded in the file:<br class=3D"none"/>#  ../../targ=
et/autobuilds/reports/jpetstore_tomcat4_build_2005-03-09.log<br class=3D"no=
ne"/>#  ----------------------------------------------------------------<br=
 class=3D"none"/>waiting 75 seconds for server to warmup...<br class=3D"non=
e"/>#  ----------------------------------------------------------------<br =
class=3D"none"/>#  Starting unit tests for jpetstore<br class=3D"none"/>#  =
----------------------------------------------------------------<br class=
=3D"none"/>#  -------------------------------------------------------------=
---<br class=3D"none"/>#  Stopping HSQLDB<br class=3D"none"/>#  -----------=
-----------------------------------------------------<br class=3D"none"/># =
 ----------------------------------------------------------------<br class=
=3D"none"/>#  Starting HSQLDB<br class=3D"none"/>#  -----------------------=
-----------------------------------------<br class=3D"none"/>##  ----------=
------------------------------------------------------<br class=3D"none"/>#=
#  Stopping server tomcat4<br class=3D"none"/>##  -------------------------=
---------------------------------------<br class=3D"none"/>##  ------------=
----------------------------------------------------<br class=3D"none"/>## =
 Starting server tomcat4<br class=3D"none"/>##  ---------------------------=
-------------------------------------<br class=3D"none"/>#  ---------------=
-------------------------------------------------<br class=3D"none"/>#<br c=
lass=3D"none"/>#  Spring Autobuilds - automatic application deployment and =
testing<br class=3D"none"/>#<br class=3D"none"/>#  target application: jpet=
store<br class=3D"none"/>#  target server: tomcat5<br class=3D"none"/>#<br =
class=3D"none"/>#  this output is recorded in the file:<br class=3D"none"/>=
#  ../../target/autobuilds/reports/jpetstore_tomcat5_build_2005-03-09.log<b=
r class=3D"none"/>#  ------------------------------------------------------=
----------<br class=3D"none"/>waiting 75 seconds for server to warmup...<br=
 class=3D"none"/>#  -------------------------------------------------------=
---------<br class=3D"none"/>#  Starting unit tests for jpetstore<br class=
=3D"none"/>#  -------------------------------------------------------------=
---<br class=3D"none"/>#  -------------------------------------------------=
---------------<br class=3D"none"/>#  Starting HSQLDB<br class=3D"none"/># =
 ----------------------------------------------------------------<br class=
=3D"none"/>#  -------------------------------------------------------------=
---<br class=3D"none"/>#  Stopping HSQLDB<br class=3D"none"/>#  -----------=
-----------------------------------------------------<br class=3D"none"/>##=
  ----------------------------------------------------------------<br class=
=3D"none"/>##  Stopping server tomcat5<br class=3D"none"/>##  -------------=
---------------------------------------------------<br class=3D"none"/>##  =
----------------------------------------------------------------<br class=
=3D"none"/>##  Starting server tomcat5<br class=3D"none"/>##  -------------=
---------------------------------------------------<br class=3D"none"/>/jte=
am/build2/checkout/spring/spring/src/org/springframework/jdbc/support/lob/O=
racleLobHandler.java:76: warning - Tag @see: reference not found: oracle.sq=
l.BLOB<br class=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/spri=
ngframework/jdbc/support/lob/OracleLobHandler.java:76: warning - Tag @see: =
reference not found: oracle.sql.CLOB<br class=3D"none"/>/jteam/build2/check=
out/spring/spring/src/org/springframework/jdbc/support/lob/OracleLobHandler=
.java:115: warning - Tag @see: reference not found: oracle.sql.BLOB#DURATIO=
N_SESSION<br class=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/s=
pringframework/jdbc/support/lob/OracleLobHandler.java:115: warning - Tag @s=
ee: reference not found: oracle.sql.BLOB#MODE_READWRITE<br class=3D"none"/>=
/jteam/build2/checkout/spring/spring/src/org/springframework/jdbc/support/l=
ob/OracleLobHandler.java:115: warning - Tag @see: reference not found: orac=
le.sql.CLOB#DURATION_SESSION<br class=3D"none"/>/jteam/build2/checkout/spri=
ng/spring/src/org/springframework/jdbc/support/lob/OracleLobHandler.java:11=
5: warning - Tag @see: reference not found: oracle.sql.CLOB#MODE_READWRITE<=
br class=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/springframe=
work/jdbc/support/lob/OracleLobHandler.java:154: warning - Tag @see: refere=
nce not found: oracle.jdbc.OracleConnection<br class=3D"none"/>/jteam/build=
2/checkout/spring/spring/src/org/springframework/jdbc/support/lob/OracleLob=
Handler.java:164: warning - Tag @see: reference not found: oracle.sql.BLOB#=
createTemporary<br class=3D"none"/>/jteam/build2/checkout/spring/spring/src=
/org/springframework/jdbc/support/lob/OracleLobHandler.java:164: warning - =
Tag @see: reference not found: oracle.sql.CLOB#createTemporary<br class=3D"=
none"/>/jteam/build2/checkout/spring/spring/src/org/springframework/jdbc/su=
pport/nativejdbc/JBossNativeJdbcExtractor.java:49: warning - Tag @see: refe=
rence not found: org.jboss.resource.adapter.jdbc.WrappedConnection#getUnder=
lyingConnection<br class=3D"none"/>/jteam/build2/checkout/spring/spring/src=
/org/springframework/jdbc/support/nativejdbc/JBossNativeJdbcExtractor.java:=
49: warning - Tag @see: reference not found: org.jboss.resource.adapter.jdb=
c.WrappedStatement#getUnderlyingStatement<br class=3D"none"/>/jteam/build2/=
checkout/spring/spring/src/org/springframework/jdbc/support/nativejdbc/JBos=
sNativeJdbcExtractor.java:49: warning - Tag @see: reference not found: org.=
jboss.resource.adapter.jdbc.WrappedResultSet#getUnderlyingResultSet<br clas=
s=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/springframework/jd=
bc/support/nativejdbc/WebLogicNativeJdbcExtractor.java:45: warning - Tag @s=
ee: reference not found: weblogic.jdbc.extensions.WLConnection#getVendorCon=
nection<br class=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/spr=
ingframework/jdbc/support/nativejdbc/WebSphereNativeJdbcExtractor.java:49: =
warning - Tag @see: reference not found: com.ibm.ws.rsadapter.jdbc.WSJdbcCo=
nnection<br class=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/sp=
ringframework/jdbc/support/nativejdbc/WebSphereNativeJdbcExtractor.java:49:=
 warning - Tag @see: reference not found: com.ibm.ws.rsadapter.jdbc.WSJdbcU=
til#getNativeConnection<br class=3D"none"/>/jteam/build2/checkout/spring/sp=
ring/src/org/springframework/jdbc/support/nativejdbc/WebSphereNativeJdbcExt=
ractor.java:49: warning - Tag @see: reference not found: com.ibm.ejs.cm.pro=
xy.ConnectionProxy#getPhysicalConnection<br class=3D"none"/>/jteam/build2/c=
heckout/spring/spring/src/org/springframework/orm/hibernate3/LocalSessionFa=
ctoryBean.java:339: warning - Tag @see: reference not found: org.hibernate.=
UserType<br class=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/sp=
ringframework/orm/hibernate3/SessionFactoryUtils.java:155: warning - Tag @s=
ee: reference not found: org.hibernate.impl.SessionFactoryImpl<br class=3D"=
none"/>/jteam/build2/checkout/spring/spring/src/org/springframework/orm/hib=
ernate3/SessionFactoryUtils.java:155: warning - Tag @see: reference not fou=
nd: org.hibernate.jca.JCASessionFactoryImpl<br class=3D"none"/>/jteam/build=
2/checkout/spring/spring/src/org/springframework/orm/ibatis/SqlMapClientFac=
toryBean.java:198: warning - Tag @see: reference not found: com.ibatis.sqlm=
ap.engine.transaction.jdbc.JdbcTransactionConfig<br class=3D"none"/>/jteam/=
build2/checkout/spring/spring/src/org/springframework/orm/ibatis/SqlMapClie=
ntFactoryBean.java:198: warning - Tag @see: reference not found: com.ibatis=
.sqlmap.engine.transaction.jta.JtaTransactionConfig<br class=3D"none"/>/jte=
am/build2/checkout/spring/spring/src/org/springframework/orm/ibatis/SqlMapC=
lientFactoryBean.java:226: warning - Tag @see: reference not found: com.iba=
tis.sqlmap.engine.transaction.jdbc.JdbcTransactionConfig<br class=3D"none"/=
>/jteam/build2/checkout/spring/spring/src/org/springframework/orm/ibatis/Sq=
lMapClientFactoryBean.java:226: warning - Tag @see: reference not found: co=
m.ibatis.sqlmap.engine.transaction.jta.JtaTransactionConfig<br class=3D"non=
e"/>/jteam/build2/checkout/spring/spring/src/org/springframework/transactio=
n/jta/WebLogicJtaTransactionManager.java:66: warning - Tag @see: reference =
not found: weblogic.transaction.TransactionManager#forceResume<br class=3D"=
none"/>/jteam/build2/checkout/spring/spring/src/org/springframework/transac=
tion/jta/WebLogicServerTransactionManagerFactoryBean.java:45: warning - Tag=
 @see: reference not found: weblogic.transaction.TxHelper#getTransactionMan=
ager<br class=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/spring=
framework/transaction/jta/WebSphereTransactionManagerFactoryBean.java:49: w=
arning - Tag @see: reference not found: com.ibm.ws.Transaction.TransactionM=
anagerFactory#getTransactionManager<br class=3D"none"/>/jteam/build2/checko=
ut/spring/spring/src/org/springframework/transaction/jta/WebSphereTransacti=
onManagerFactoryBean.java:49: warning - Tag @see: reference not found: com.=
ibm.ejs.jts.jta.JTSXA#getTransactionManager<br class=3D"none"/>/jteam/build=
2/checkout/spring/spring/src/org/springframework/transaction/jta/WebSphereT=
ransactionManagerFactoryBean.java:49: warning - Tag @see: reference not fou=
nd: com.ibm.ejs.jts.jta.TransactionManagerFactory#getTransactionManager<br =
class=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/springframewor=
k/util/ObjectUtils.java:31: warning - Tag @see: reference not found: org.ap=
ache.commons.lang.ObjectUtils<br class=3D"none"/>/jteam/build2/checkout/spr=
ing/spring/src/org/springframework/util/StringUtils.java:47: warning - Tag =
@see: reference not found: org.apache.commons.lang.StringUtils<br class=3D"=
none"/>/jteam/build2/checkout/spring/spring/src/org/springframework/web/ser=
vlet/handler/metadata/PathMap.java:31: warning - @@org.apache.commons.attri=
butes.Indexed() is an unknown tag.<br class=3D"none"/>Error on line 3 colum=
n 3 of file:/jteam/build2/checkout/spring/spring/docs/reference/src/webinte=
gration.xml:<br class=3D"none"/>Error reported by XML parser: name expected=
 (found "&lt;")<br class=3D"none"/>Transformation failed: Run-time errors w=
ere reported<br class=3D"none"/>Error on line 3 column 3 of file:/jteam/bui=
ld2/checkout/spring/spring/docs/reference/src/webintegration.xml:<br class=
=3D"none"/>Error reported by XML parser: name expected (found "&lt;")<br cl=
ass=3D"none"/>Transformation failed: Run-time errors were reported<br class=
=3D"none"/>Error on line 3 column 3 of file:/jteam/build2/checkout/spring/s=
pring/docs/reference/src/webintegration.xml:<br class=3D"none"/>Error repor=
ted by XML parser: name expected (found "&lt;")<br class=3D"none"/>Transfor=
mation failed: Run-time errors were reported<br class=3D"none"/>USAGE<br cl=
ass=3D"none"/>Fop [options] [-fo|-xml] infile [-xsl file] [-awt|-pdf|-mif|-=
pcl|-ps|-txt|-at|-print] &lt;outfile&gt;<br class=3D"none"/>[OPTIONS]<br cl=
ass=3D"none"/>-d          debug mode<br class=3D"none"/>-x          dump co=
nfiguration settings<br class=3D"none"/>-q          quiet mode<br class=3D"=
none"/>-c cfg.xml  use additional configuration file cfg.xml<br class=3D"no=
ne"/>-l lang     the language to use for user information<br class=3D"none"=
/>-s          for area tree XML, down to block areas only<br class=3D"none"=
/>[INPUT]<br class=3D"none"/>infile            xsl:fo input file (the same =
as the next)<br class=3D"none"/>-fo  infile       xsl:fo input file<br clas=
s=3D"none"/>-xml infile       xml input file, must be used together with -x=
sl<br class=3D"none"/>-xsl stylesheet   xslt stylesheet<br class=3D"none"/>=
<br class=3D"none"/>[OUTPUT]<br class=3D"none"/>outfile           input wil=
l be rendered as pdf file into outfile<br class=3D"none"/>-pdf outfile     =
 input will be rendered as pdf file (outfile req'd)<br class=3D"none"/>-awt=
              input will be displayed on screen<br class=3D"none"/>-mif out=
file      input will be rendered as mif file (outfile req'd)<br class=3D"no=
ne"/>-pcl outfile      input will be rendered as pcl file (outfile req'd)<b=
r class=3D"none"/>-ps outfile       input will be rendered as PostScript fi=
le (outfile req'd)<br class=3D"none"/>-txt outfile      input will be rende=
red as text file (outfile req'd)<br class=3D"none"/>-txt.encoding encoding =
 use the encoding for the output file.<br class=3D"none"/>the encoding must=
 be a valid java encoding.<br class=3D"none"/>-svg outfile      input will =
be rendered as an svg slides file (outfile req'd)<br class=3D"none"/>-at ou=
tfile       representation of area tree as XML (outfile req'd)<br class=3D"=
none"/>-print            input file will be rendered and sent to the printe=
r<br class=3D"none"/>see options with "-print help"<br class=3D"none"/>[Exa=
mples]<br class=3D"none"/>Fop foo.fo foo.pdf<br class=3D"none"/>Fop -fo foo=
.fo -pdf foo.pdf (does the same as the previous line)<br class=3D"none"/>Fo=
p -xsl foo.xsl -xml foo.xml -pdf foo.pdf<br class=3D"none"/>Fop foo.fo -mif=
 foo.mif<br class=3D"none"/>Fop foo.fo -print or Fop -print foo.fo<br class=
=3D"none"/>Fop foo.fo -awt<br class=3D"none"/></pre></td></tr></table><p>
<table xmlns=3D"http://www.w3.org/TR/html4/strict.dtd" width=3D"98%" border=
=3D"0" cellspacing=3D"0" cellpadding=3D"2" align=3D"center"><tr><td class=
=3D"compile-sectionheader">                        &nbsp;Javadoc Errors/War=
nings: (31)                    </td></tr><tr><td><pre class=3D"compile-data=
">/jteam/build2/checkout/spring/spring/src/org/springframework/jdbc/support=
/lob/OracleLobHandler.java:76: warning - Tag @see: reference not found: ora=
cle.sql.BLOB<br class=3D"none"/>/jteam/build2/checkout/spring/spring/src/or=
g/springframework/jdbc/support/lob/OracleLobHandler.java:76: warning - Tag =
@see: reference not found: oracle.sql.CLOB<br class=3D"none"/>/jteam/build2=
/checkout/spring/spring/src/org/springframework/jdbc/support/lob/OracleLobH=
andler.java:115: warning - Tag @see: reference not found: oracle.sql.BLOB#D=
URATION_SESSION<br class=3D"none"/>/jteam/build2/checkout/spring/spring/src=
/org/springframework/jdbc/support/lob/OracleLobHandler.java:115: warning - =
Tag @see: reference not found: oracle.sql.BLOB#MODE_READWRITE<br class=3D"n=
one"/>/jteam/build2/checkout/spring/spring/src/org/springframework/jdbc/sup=
port/lob/OracleLobHandler.java:115: warning - Tag @see: reference not found=
: oracle.sql.CLOB#DURATION_SESSION<br class=3D"none"/>/jteam/build2/checkou=
t/spring/spring/src/org/springframework/jdbc/support/lob/OracleLobHandler.j=
ava:115: warning - Tag @see: reference not found: oracle.sql.CLOB#MODE_READ=
WRITE<br class=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/sprin=
gframework/jdbc/support/lob/OracleLobHandler.java:154: warning - Tag @see: =
reference not found: oracle.jdbc.OracleConnection<br class=3D"none"/>/jteam=
/build2/checkout/spring/spring/src/org/springframework/jdbc/support/lob/Ora=
cleLobHandler.java:164: warning - Tag @see: reference not found: oracle.sql=
.BLOB#createTemporary<br class=3D"none"/>/jteam/build2/checkout/spring/spri=
ng/src/org/springframework/jdbc/support/lob/OracleLobHandler.java:164: warn=
ing - Tag @see: reference not found: oracle.sql.CLOB#createTemporary<br cla=
ss=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/springframework/j=
dbc/support/nativejdbc/JBossNativeJdbcExtractor.java:49: warning - Tag @see=
: reference not found: org.jboss.resource.adapter.jdbc.WrappedConnection#ge=
tUnderlyingConnection<br class=3D"none"/>/jteam/build2/checkout/spring/spri=
ng/src/org/springframework/jdbc/support/nativejdbc/JBossNativeJdbcExtractor=
.java:49: warning - Tag @see: reference not found: org.jboss.resource.adapt=
er.jdbc.WrappedStatement#getUnderlyingStatement<br class=3D"none"/>/jteam/b=
uild2/checkout/spring/spring/src/org/springframework/jdbc/support/nativejdb=
c/JBossNativeJdbcExtractor.java:49: warning - Tag @see: reference not found=
: org.jboss.resource.adapter.jdbc.WrappedResultSet#getUnderlyingResultSet<b=
r class=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/springframew=
ork/jdbc/support/nativejdbc/WebLogicNativeJdbcExtractor.java:45: warning - =
Tag @see: reference not found: weblogic.jdbc.extensions.WLConnection#getVen=
dorConnection<br class=3D"none"/>/jteam/build2/checkout/spring/spring/src/o=
rg/springframework/jdbc/support/nativejdbc/WebSphereNativeJdbcExtractor.jav=
a:49: warning - Tag @see: reference not found: com.ibm.ws.rsadapter.jdbc.WS=
JdbcConnection<br class=3D"none"/>/jteam/build2/checkout/spring/spring/src/=
org/springframework/jdbc/support/nativejdbc/WebSphereNativeJdbcExtractor.ja=
va:49: warning - Tag @see: reference not found: com.ibm.ws.rsadapter.jdbc.W=
SJdbcUtil#getNativeConnection<br class=3D"none"/>/jteam/build2/checkout/spr=
ing/spring/src/org/springframework/jdbc/support/nativejdbc/WebSphereNativeJ=
dbcExtractor.java:49: warning - Tag @see: reference not found: com.ibm.ejs.=
cm.proxy.ConnectionProxy#getPhysicalConnection<br class=3D"none"/>/jteam/bu=
ild2/checkout/spring/spring/src/org/springframework/orm/hibernate3/LocalSes=
sionFactoryBean.java:339: warning - Tag @see: reference not found: org.hibe=
rnate.UserType<br class=3D"none"/>/jteam/build2/checkout/spring/spring/src/=
org/springframework/orm/hibernate3/SessionFactoryUtils.java:155: warning - =
Tag @see: reference not found: org.hibernate.impl.SessionFactoryImpl<br cla=
ss=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/springframework/o=
rm/hibernate3/SessionFactoryUtils.java:155: warning - Tag @see: reference n=
ot found: org.hibernate.jca.JCASessionFactoryImpl<br class=3D"none"/>/jteam=
/build2/checkout/spring/spring/src/org/springframework/orm/ibatis/SqlMapCli=
entFactoryBean.java:198: warning - Tag @see: reference not found: com.ibati=
s.sqlmap.engine.transaction.jdbc.JdbcTransactionConfig<br class=3D"none"/>/=
jteam/build2/checkout/spring/spring/src/org/springframework/orm/ibatis/SqlM=
apClientFactoryBean.java:198: warning - Tag @see: reference not found: com.=
ibatis.sqlmap.engine.transaction.jta.JtaTransactionConfig<br class=3D"none"=
/>/jteam/build2/checkout/spring/spring/src/org/springframework/orm/ibatis/S=
qlMapClientFactoryBean.java:226: warning - Tag @see: reference not found: c=
om.ibatis.sqlmap.engine.transaction.jdbc.JdbcTransactionConfig<br class=3D"=
none"/>/jteam/build2/checkout/spring/spring/src/org/springframework/orm/iba=
tis/SqlMapClientFactoryBean.java:226: warning - Tag @see: reference not fou=
nd: com.ibatis.sqlmap.engine.transaction.jta.JtaTransactionConfig<br class=
=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/springframework/tra=
nsaction/jta/WebLogicJtaTransactionManager.java:66: warning - Tag @see: ref=
erence not found: weblogic.transaction.TransactionManager#forceResume<br cl=
ass=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/springframework/=
transaction/jta/WebLogicServerTransactionManagerFactoryBean.java:45: warnin=
g - Tag @see: reference not found: weblogic.transaction.TxHelper#getTransac=
tionManager<br class=3D"none"/>/jteam/build2/checkout/spring/spring/src/org=
/springframework/transaction/jta/WebSphereTransactionManagerFactoryBean.jav=
a:49: warning - Tag @see: reference not found: com.ibm.ws.Transaction.Trans=
actionManagerFactory#getTransactionManager<br class=3D"none"/>/jteam/build2=
/checkout/spring/spring/src/org/springframework/transaction/jta/WebSphereTr=
ansactionManagerFactoryBean.java:49: warning - Tag @see: reference not foun=
d: com.ibm.ejs.jts.jta.JTSXA#getTransactionManager<br class=3D"none"/>/jtea=
m/build2/checkout/spring/spring/src/org/springframework/transaction/jta/Web=
SphereTransactionManagerFactoryBean.java:49: warning - Tag @see: reference =
not found: com.ibm.ejs.jts.jta.TransactionManagerFactory#getTransactionMana=
ger<br class=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/springf=
ramework/util/ObjectUtils.java:31: warning - Tag @see: reference not found:=
 org.apache.commons.lang.ObjectUtils<br class=3D"none"/>/jteam/build2/check=
out/spring/spring/src/org/springframework/util/StringUtils.java:47: warning=
 - Tag @see: reference not found: org.apache.commons.lang.StringUtils<br cl=
ass=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/springframework/=
web/servlet/handler/metadata/PathMap.java:31: warning - @@org.apache.common=
s.attributes.Indexed() is an unknown tag.<br class=3D"none"/></pre></td></t=
r></table><p>
<table width=3D"98%" border=3D"0" cellspacing=3D"0" cellpadding=3D"2" align=
=3D"center"><tr><td colspan=3D"4" class=3D"unittests-sectionheader">       =
            &nbsp;Unit Tests: (2769)                </td></tr><tr><td><tabl=
e width=3D"98%" border=3D"0" cellspacing=3D"0" cellpadding=3D"2" align=3D"c=
enter"><tr><td class=3D"unittests-data">                failure            =
</td><td width=3D"40%" class=3D"unittests-data">testHelpPage</td><td width=
=3D"40%" class=3D"unittests-data">org.springframework.apptests.jpetstore.Al=
lTests</td></tr><tr class=3D"unittests-oddrow"><td class=3D"unittests-data"=
>                failure            </td><td width=3D"40%" class=3D"unittes=
ts-data">testPurchase</td><td width=3D"40%" class=3D"unittests-data">org.sp=
ringframework.apptests.jpetstore.AllTests</td></tr><tr><td class=3D"unittes=
ts-data">                failure            </td><td width=3D"40%" class=3D=
"unittests-data">testSearch</td><td width=3D"40%" class=3D"unittests-data">=
org.springframework.apptests.jpetstore.AllTests</td></tr><tr class=3D"unitt=
ests-oddrow"><td class=3D"unittests-data">                failure          =
  </td><td width=3D"40%" class=3D"unittests-data">testHelpPage</td><td widt=
h=3D"40%" class=3D"unittests-data">org.springframework.apptests.jpetstore.A=
llTests</td></tr><tr><td class=3D"unittests-data">                failure  =
          </td><td width=3D"40%" class=3D"unittests-data">testPurchase</td>=
<td width=3D"40%" class=3D"unittests-data">org.springframework.apptests.jpe=
tstore.AllTests</td></tr><tr class=3D"unittests-oddrow"><td class=3D"unitte=
sts-data">                failure            </td><td width=3D"40%" class=
=3D"unittests-data">testSearch</td><td width=3D"40%" class=3D"unittests-dat=
a">org.springframework.apptests.jpetstore.AllTests</td></tr></table></td></=
tr><tr></tr><tr><td colspan=3D"2">&nbsp;</td></tr><tr><td colspan=3D"4" cla=
ss=3D"unittests-sectionheader">                    &nbsp;Unit Test Error De=
tails:&nbsp;(6)                </td></tr><tr><td class=3D"unittests-data" c=
olspan=3D"2">                Test:&nbsp;testHelpPage</td></tr><tr><td class=
=3D"unittests-data" colspan=3D"2">                Class:&nbsp;org.springfra=
mework.apptests.jpetstore.AllTests</td></tr><tr><td class=3D"unittests-data=
" colspan=3D"2">                Type: junit.framework.AssertionFailedError<=
/td></tr><tr><td class=3D"unittests-data" colspan=3D"2">                Mes=
sage: Exception: com.meterware.httpunit.HttpInternalErrorException: Error o=
n HTTP request: 500 Internal Error [http://localhost:13084/jpetstore/shop/h=
elp.do?param=3Dfreemarker]</td></tr><tr><td class=3D"unittests-failure" col=
span=3D"2"><pre>junit.framework.AssertionFailedError: Exception: com.meterw=
are.httpunit.HttpInternalErrorException: Error on HTTP request: 500 Interna=
l Error [http://localhost:13084/jpetstore/shop/help.do?param=3Dfreemarker]<=
br>=09at org.springframework.apptests.jpetstore.AllTests.testHelpPage(Unkno=
wn Source)<br>=09at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Met=
hod)<br>=09at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces=
sorImpl.java:39)<br>=09at sun.reflect.DelegatingMethodAccessorImpl.invoke(D=
elegatingMethodAccessorImpl.java:25)<br>=09at java.lang.Thread.run(Thread.j=
ava:534)</pre></td></tr><tr><td class=3D"unittests-data" colspan=3D"2">    =
            Test:&nbsp;testPurchase</td></tr><tr><td class=3D"unittests-dat=
a" colspan=3D"2">                Class:&nbsp;org.springframework.apptests.j=
petstore.AllTests</td></tr><tr><td class=3D"unittests-data" colspan=3D"2"> =
               Type: junit.framework.AssertionFailedError</td></tr><tr><td =
class=3D"unittests-data" colspan=3D"2">                Message: Exception: =
com.meterware.httpunit.HttpInternalErrorException: Error on HTTP request: 5=
00 Internal Error [http://localhost:13084/jpetstore/shop/index.do]</td></tr=
><tr><td class=3D"unittests-failure" colspan=3D"2"><pre>junit.framework.Ass=
ertionFailedError: Exception: com.meterware.httpunit.HttpInternalErrorExcep=
tion: Error on HTTP request: 500 Internal Error [http://localhost:13084/jpe=
tstore/shop/index.do]<br>=09at org.springframework.apptests.jpetstore.AllTe=
sts.testPurchase(Unknown Source)<br>=09at sun.reflect.NativeMethodAccessorI=
mpl.invoke0(Native Method)<br>=09at sun.reflect.NativeMethodAccessorImpl.in=
voke(NativeMethodAccessorImpl.java:39)<br>=09at sun.reflect.DelegatingMetho=
dAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)<br>=09at java.la=
ng.Thread.run(Thread.java:534)</pre></td></tr><tr><td class=3D"unittests-da=
ta" colspan=3D"2">                Test:&nbsp;testSearch</td></tr><tr><td cl=
ass=3D"unittests-data" colspan=3D"2">                Class:&nbsp;org.spring=
framework.apptests.jpetstore.AllTests</td></tr><tr><td class=3D"unittests-d=
ata" colspan=3D"2">                Type: junit.framework.AssertionFailedErr=
or</td></tr><tr><td class=3D"unittests-data" colspan=3D"2">                =
Message: Exception: com.meterware.httpunit.HttpInternalErrorException: Erro=
r on HTTP request: 500 Internal Error [http://localhost:13084/jpetstore/sho=
p/index.do]</td></tr><tr><td class=3D"unittests-failure" colspan=3D"2"><pre=
>junit.framework.AssertionFailedError: Exception: com.meterware.httpunit.Ht=
tpInternalErrorException: Error on HTTP request: 500 Internal Error [http:/=
/localhost:13084/jpetstore/shop/index.do]<br>=09at org.springframework.appt=
ests.jpetstore.AllTests.testSearch(Unknown Source)<br>=09at sun.reflect.Nat=
iveMethodAccessorImpl.invoke0(Native Method)<br>=09at sun.reflect.NativeMet=
hodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)<br>=09at sun.refle=
ct.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25=
)<br>=09at java.lang.Thread.run(Thread.java:534)</pre></td></tr><tr><td cla=
ss=3D"unittests-data" colspan=3D"2">                Test:&nbsp;testHelpPage=
</td></tr><tr><td class=3D"unittests-data" colspan=3D"2">                Cl=
ass:&nbsp;org.springframework.apptests.jpetstore.AllTests</td></tr><tr><td =
class=3D"unittests-data" colspan=3D"2">                Type: junit.framewor=
k.AssertionFailedError</td></tr><tr><td class=3D"unittests-data" colspan=3D=
"2">                Message: Exception: com.meterware.httpunit.HttpInternal=
ErrorException: Error on HTTP request: 500 Internal Error [http://localhost=
:13084/jpetstore/shop/help.do?param=3Dfreemarker]</td></tr><tr><td class=3D=
"unittests-failure" colspan=3D"2"><pre>junit.framework.AssertionFailedError=
: Exception: com.meterware.httpunit.HttpInternalErrorException: Error on HT=
TP request: 500 Internal Error [http://localhost:13084/jpetstore/shop/help.=
do?param=3Dfreemarker]<br>=09at org.springframework.apptests.jpetstore.AllT=
ests.testHelpPage(Unknown Source)<br>=09at sun.reflect.NativeMethodAccessor=
Impl.invoke0(Native Method)<br>=09at sun.reflect.NativeMethodAccessorImpl.i=
nvoke(NativeMethodAccessorImpl.java:39)<br>=09at sun.reflect.DelegatingMeth=
odAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)<br>=09at java.l=
ang.Thread.run(Thread.java:534)</pre></td></tr><tr><td class=3D"unittests-d=
ata" colspan=3D"2">                Test:&nbsp;testPurchase</td></tr><tr><td=
 class=3D"unittests-data" colspan=3D"2">                Class:&nbsp;org.spr=
ingframework.apptests.jpetstore.AllTests</td></tr><tr><td class=3D"unittest=
s-data" colspan=3D"2">                Type: junit.framework.AssertionFailed=
Error</td></tr><tr><td class=3D"unittests-data" colspan=3D"2">             =
   Message: Exception: com.meterware.httpunit.HttpInternalErrorException: E=
rror on HTTP request: 500 Internal Error [http://localhost:13084/jpetstore/=
shop/index.do]</td></tr><tr><td class=3D"unittests-failure" colspan=3D"2"><=
pre>junit.framework.AssertionFailedError: Exception: com.meterware.httpunit=
.HttpInternalErrorException: Error on HTTP request: 500 Internal Error [htt=
p://localhost:13084/jpetstore/shop/index.do]<br>=09at org.springframework.a=
pptests.jpetstore.AllTests.testPurchase(Unknown Source)<br>=09at sun.reflec=
t.NativeMethodAccessorImpl.invoke0(Native Method)<br>=09at sun.reflect.Nati=
veMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)<br>=09at sun.=
reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja=
va:25)<br>=09at java.lang.Thread.run(Thread.java:534)</pre></td></tr><tr><t=
d class=3D"unittests-data" colspan=3D"2">                Test:&nbsp;testSea=
rch</td></tr><tr><td class=3D"unittests-data" colspan=3D"2">               =
 Class:&nbsp;org.springframework.apptests.jpetstore.AllTests</td></tr><tr><=
td class=3D"unittests-data" colspan=3D"2">                Type: junit.frame=
work.AssertionFailedError</td></tr><tr><td class=3D"unittests-data" colspan=
=3D"2">                Message: Exception: com.meterware.httpunit.HttpInter=
nalErrorException: Error on HTTP request: 500 Internal Error [http://localh=
ost:13084/jpetstore/shop/index.do]</td></tr><tr><td class=3D"unittests-fail=
ure" colspan=3D"2"><pre>junit.framework.AssertionFailedError: Exception: co=
m.meterware.httpunit.HttpInternalErrorException: Error on HTTP request: 500=
 Internal Error [http://localhost:13084/jpetstore/shop/index.do]<br>=09at o=
rg.springframework.apptests.jpetstore.AllTests.testSearch(Unknown Source)<b=
r>=09at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)<br>=09a=
t sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java=
:39)<br>=09at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet=
hodAccessorImpl.java:25)<br>=09at java.lang.Thread.run(Thread.java:534)</pr=
e></td></tr><tr><td colspan=3D"2">&nbsp;</td></tr></table><p>
<table width=3D"98%" border=3D"0" cellspacing=3D"1" cellpadding=3D"2" align=
=3D"center"><tr><td colspan=3D"6" class=3D"modifications-sectionheader">   =
                 &nbsp;Modifications since last build:&nbsp;               =
     (3)                </td></tr><tr class=3D"modifications-evenrow"><td c=
lass=3D"modifications-data">modified</td><td class=3D"modifications-data">j=
hoeller</td><td class=3D"modifications-data">src/org/springframework/aop/fr=
amework/Advised.java</td><td class=3D"modifications-data">removed unnecessa=
ry imports</td></tr><tr class=3D"modifications-oddrow"><td class=3D"modific=
ations-data">modified</td><td class=3D"modifications-data">jhoeller</td><td=
 class=3D"modifications-data">src/org/springframework/aop/framework/Advised=
Support.java</td><td class=3D"modifications-data">removed unnecessary impor=
ts</td></tr><tr class=3D"modifications-evenrow"><td class=3D"modifications-=
data">modified</td><td class=3D"modifications-data">jhoeller</td><td class=
=3D"modifications-data">src/org/springframework/beans/factory/xml/XmlBeanFa=
ctory.java</td><td class=3D"modifications-data">removed unnecessary imports=
</td></tr></table><p>
<table width=3D"98%" border=3D"0" cellspacing=3D"0" cellpadding=3D"2" align=
=3D"center"><tr><td class=3D"distributables-sectionheader">                =
        &nbsp;Deployments by this build:&nbsp;(16)                    </td>=
</tr><tr><td class=3D"distributables-data">Building jar: /jteam/build2/chec=
kout/spring/spring/dist/spring-core.jar</td></tr><tr class=3D"distributable=
s-oddrow"><td class=3D"distributables-data">Building jar: /jteam/build2/che=
ckout/spring/spring/dist/spring-aop.jar</td></tr><tr><td class=3D"distribut=
ables-data">Building jar: /jteam/build2/checkout/spring/spring/dist/spring-=
context.jar</td></tr><tr class=3D"distributables-oddrow"><td class=3D"distr=
ibutables-data">Building jar: /jteam/build2/checkout/spring/spring/dist/spr=
ing-dao.jar</td></tr><tr><td class=3D"distributables-data">Building jar: /j=
team/build2/checkout/spring/spring/dist/spring-orm.jar</td></tr><tr class=
=3D"distributables-oddrow"><td class=3D"distributables-data">Building jar: =
/jteam/build2/checkout/spring/spring/dist/spring-web.jar</td></tr><tr><td c=
lass=3D"distributables-data">Building jar: /jteam/build2/checkout/spring/sp=
ring/dist/spring-webmvc.jar</td></tr><tr class=3D"distributables-oddrow"><t=
d class=3D"distributables-data">Building jar: /jteam/build2/checkout/spring=
/spring/dist/spring.jar</td></tr><tr><td class=3D"distributables-data">Buil=
ding jar: /jteam/build2/checkout/spring/spring/dist/spring-mock.jar</td></t=
r><tr class=3D"distributables-oddrow"><td class=3D"distributables-data">Bui=
lding war: /jteam/build2/checkout/spring/spring/autobuilds/apps/buildtest/d=
ist/buildtest.war</td></tr><tr><td class=3D"distributables-data">Building w=
ar: /jteam/build2/checkout/spring/spring/autobuilds/apps/buildtest/dist/bui=
ldtest.war</td></tr><tr class=3D"distributables-oddrow"><td class=3D"distri=
butables-data">Building war: /jteam/build2/checkout/spring/spring/autobuild=
s/apps/buildtest/dist/buildtest.war</td></tr><tr><td class=3D"distributable=
s-data">Building jar: /jteam/build2/checkout/spring/spring/autobuilds/apps/=
jpetstore/war/WEB-INF/lib/jpetstore.jar</td></tr><tr class=3D"distributable=
s-oddrow"><td class=3D"distributables-data">Building war: /jteam/build2/che=
ckout/spring/spring/autobuilds/apps/jpetstore/dist/jpetstore.war</td></tr><=
tr><td class=3D"distributables-data">Building jar: /jteam/build2/checkout/s=
pring/spring/autobuilds/apps/jpetstore/war/WEB-INF/lib/jpetstore.jar</td></=
tr><tr class=3D"distributables-oddrow"><td class=3D"distributables-data">Bu=
ilding war: /jteam/build2/checkout/spring/spring/autobuilds/apps/jpetstore/=
dist/jpetstore.war</td></tr></table>
</body></html>

RE: [Springframework-developer] Portlet Form Controllers

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

Related to this portlet stuff, will John Lewis' contribution be finding =
its
way in the sandbox cvs anytime soon?

-tim


-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf =
Of
William G. Thompson, Jr.
Sent: Tuesday, March 08, 2005 1:12 PM
To: spr...@li...
Subject: Re: [Springframework-developer] Portlet Form Controllers

I'm also in favor of a subproject that can move ahead with independent=20
release dates.  We already have Portlets in production based on the=20
sandbox support for Portlet API.  We are interested in seeing this move=20
out to a GA release.

Bill


Tim Kettering wrote:
>=20
> I am also in favor of the option that allows the portlet subproject to
move
> ahead as quickly as it can.  We are working on a portlet project here =
at
my
> company and we've decided to settle on Spring's MVC, and am more than
> willing to contribute any improvements that may come along to the =
Portlet
> subproject as well. =20
>=20
> -tim
>=20
> -----Original Message-----
> From: spr...@li...
> [mailto:spr...@li...] On =
Behalf
Of
> Juergen Hoeller
> Sent: Friday, March 04, 2005 5:54 PM
> To: spr...@li...
> Subject: Re: [Springframework-developer] Portlet Form Controllers
>=20
> We don't need to vote right now; we're just gathering opinions :-)
>=20
> The decision will also depend on the final size of the Portlet =
support. If
> it turns out to be too small for a separate subproject, including it =
in
the
> core distribution might be the only feasible way to go.
>=20
> Juergen
>=20
>=20
> -----Original Message-----
> From: spr...@li...
> [mailto:spr...@li...]On =
Behalf
> Of Ken Krebs
> Sent: Friday, March 04, 2005 11:47 PM
> To: spr...@li...
> Subject: Re: [Springframework-developer] Portlet Form Controllers
>=20
>=20
> +1 for subproject status.
> It makes sense to me to let them evolve in a more loosely coupled way,
> especially as Juergen points out given the small target audience for
> portlets.
>=20
> Juergen Hoeller wrote:
>=20
>=20
>>As I said, a subproject is just under consideration. The alternative =
is to
>>release the portlet support as part of the core Spring 1.3 =
distribution.
>=20
> The
>=20
>>rationale of factoring out subprojects is to let the core concentrate =
on
>=20
> its
>=20
>>current scope and not introduce completely new areas of functionality. =
A
>>secondary goal is to limit the size of spring.jar.
>>
>>The current core web support and web MVC framework is used by the =
portlet
>>support underneath, for example to render views (at least that was the
case
>>last year). So Spring Portlet depends on Spring core web (even core =
web
>>MVC), but not the other way round: a case for core web MVC staying =
part of
>>the core distribution, but Portlet support (optionally) becoming a
separate
>>subproject.
>>
>>Note that Spring's core web support is of interest to many people: not
only
>>to web application people, but also to rich client developers =
accessing
>>HTTP-based remote services (running in a Servlet container). Portlet
>=20
> support
>=20
>>is more specific and has a narrower target audience.
>>
>>A further advantage of a separate subproject is that it can evolve =
more
>>easily. Specific sample applications, tutorials, tools etc can be =
added
>>without having to worry about scope or size of the core Spring
>=20
> distribution.
>=20
>>Anyway, this has not been decided yet and does not have to be decided
right
>>now. It's gonna become an important topic after the Spring 1.2 =
release,
>>though.
>>
>>Juergen
>>
>>
>>
>>-----Original Message-----
>>From: spr...@li...
>>[mailto:spr...@li...]On =
Behalf
>>Of Jean-Pol Landrain
>>Sent: Friday, March 04, 2005 7:29 PM
>>To: spr...@li...
>>Subject: Re: [Springframework-developer] Portlet Form Controllers
>>
>>
>>I quite agree with Rob. Except, of course, if you plan to create a
>>subproject for Spring MVC too. This would allow a Spring "=E0 la =
carte".
>>This would keep the framework light, but would perhaps be a bit =
confusing
>=20
> to
>=20
>>the users. Perhaps a "plugin" functionnality would be nice if the =
number
of
>>projects grows : you would have a core Spring and be able to plug in, =
for
>>example by using a dedicated XML file, the other sub-projects you want =
to
>>use. That's just an idea.
>>
>>Cheers,
>>Jean-Pol.
>>
>>----- Original Message -----
>>From: "Rob Butler" <cro...@ya...>
>>To: <spr...@li...>
>>Sent: Friday, March 04, 2005 7:01 PM
>>Subject: Re: [Springframework-developer] Portlet Form Controllers
>>
>>
>>
>>
>>
>>>Why would you have a separate sub-project for the
>>>portlet support in Spring?  That would be like having
>>>a separate sub-project for the web MVC stuff, and a
>>>separate sub-project for the DAO related stuff, and
>>>another one for AOP, etc.
>>>
>>>Later
>>>Rob
>>>--- Juergen Hoeller <ju...@in...> wrote:
>>>
>>>
>>>
>>>
>>>>Sounds like good stuff :-)
>>>>
>>>>On this occasion: Let's discuss the road to an
>>>>official release of the
>>>>Portlet support. We consider releasing the Portlet
>>>>support as an official
>>>>subproject, i.e. as a separate distribution and with
>>>>a separate CVS module
>>>>(or even separate CVS repository). The association
>>>>would be similar to the
>>>>just-announced Spring subproject status of Acegi
>>>>Security, and the already
>>>>established status of Spring RCP.
>>>>
>>>>Very importantly, the portlet subproject needs a
>>>>dedicated developer team.
>>>>Any volunteers? :-)
>>>>
>>>>Juergen
>>>>
>>>>
>>>>-----Original Message-----
>>>>From:
>>>>
>>>>
>>>>
>>>
>>>spr...@li...
>>>
>>>
>>>[mailto:spr...@li...]On
>>>
>>>
>>>
>>>>Behalf
>>>>Of John Lewis
>>>>Sent: Thursday, March 03, 2005 6:53 PM
>>>>To: spr...@li...
>>>>Subject: [Springframework-developer] Portlet Form
>>>>Controllers
>>>>
>>>>
>>>>We've been working on porting a fairly complex
>>>>enterprise application
>>>
>>>>from the Spring Servlet MVC framework to the Spring
>>>
>>>>Portlet MVC
>>>>framework.  As Nick Lothian and Rainer Schmitz
>>>>discovered, the Form
>>>>Controller hierarchy is difficult to port over from
>>>>the Servlet area to
>>>>the Portlet area because of the two-phase nature of
>>>>portlet requests.
>>>>Since we were porting a large number of existing
>>>>controllers descended
>>>
>>>>from AbstractController, AbstractFormController, or
>>>
>>>>SimpleFormController, it was critical to that all
>>>>the former
>>>>functionality of these parent be present and that
>>>>our logic work the
>>>>same as before.
>>>>
>>>>Nick Lothian's version of
>>>>SimplePortletFormController gave us a good
>>>>starting point and helped us understand a lot of the
>>>>issues with portlet
>>>>development in general and with Spring portlets in
>>>>particular.  However,
>>>>a lot of our controllers manage database content, so
>>>>we needed proper
>>>>separation between the action and render phase of
>>>>the request, which
>>>>this controller did not give us.
>>>>
>>>>Rainer Schmitz's work went much further and provided
>>>>the traditional
>>>>hierarchy of controllers and further demonstrated
>>>>the issues with
>>>>separating out the two phases of the portlet
>>>>request.  However, these
>>>>still did not give us the complete control that we
>>>>needed.  We
>>>>especially needed a version of SimpleFormController
>>>>that could handle
>>>>the separation of the action logic from the render
>>>>logic.
>>>>
>>>>Over the past few months we have developed a new set
>>>>of the
>>>>AbstractController, BaseCommandController,
>>>>AbstractFormController, and
>>>>SimpleFormController classes that we think
>>>>rigorously address all the
>>>>issues with portlet development and that have
>>>>allowed us to port over
>>>>existing servlet controllers with relative ease.
>>>>
>>>>We've included a portlet version of
>>>>WebContentGenerator to give the
>>>>controller classes their proper ancestry and provide
>>>>control over things
>>>>like content caching and access to the web
>>>>application context and to
>>>>centralized logging.
>>>>
>>>>We've also create a new set of the binding classes
>>>>(PortletRequestDataBinder,
>>>>PortletRequestParameterPropertyValues and
>>>>PortletRequestBindingException) that support special
>>>>field markers,
>>>>correct problems with form elements such as radio
>>>>buttons and
>>>>checkboxes, and handle redisplay of invalid submits
>>>>of non-string
>>>>parameters properly.
>>>>
>>>>All of the classes are fully documented, including
>>>>workflow descriptions
>>>>in the controllers that cover the special nature of
>>>>portlet development.
>>>>
>>>>Our hope is that these classes can handle the needs
>>>>of everyone working
>>>>with form controllers in Spring portlets and that
>>>>these can be merged
>>>>into the sandbox source code.
>>>>
>>>>The classes are posted in a zip file on the Spring
>>>>Portlet Wiki page at:
>>>>
>>>>
>>>>
>>>
>>>http://opensource.atlassian.com/confluence/spring/display/JSR168/
>>>
>>>
>>>
>>>>The link to the file is (sorry for the long link):
>>>>
>>>>
>>>>
>>
>>http://opensource.atlassian.com/confluence/spring/download/attachments/=
10/
s
>=20
> p
>=20
>>
>>>>ring-portlet-controllers.zip
>>>>
>>>>Please send me any questions or comments you may
>>>>have about these
>>>>classes.  We are eager to support their adoption in
>>>>the Spring Portlet
>>>>community.
>>>>
>>>>John Lewis
>>>>jl...@ar...
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] Portlet Form Controllers

[William G. T. Jr. <wg...@ru...>]

I'm also in favor of a subproject that can move ahead with independent 
release dates.  We already have Portlets in production based on the 
sandbox support for Portlet API.  We are interested in seeing this move 
out to a GA release.

Bill


Tim Kettering wrote:
> 
> I am also in favor of the option that allows the portlet subproject to move
> ahead as quickly as it can.  We are working on a portlet project here at my
> company and we've decided to settle on Spring's MVC, and am more than
> willing to contribute any improvements that may come along to the Portlet
> subproject as well.  
> 
> -tim
> 
> -----Original Message-----
> From: spr...@li...
> [mailto:spr...@li...] On Behalf Of
> Juergen Hoeller
> Sent: Friday, March 04, 2005 5:54 PM
> To: spr...@li...
> Subject: Re: [Springframework-developer] Portlet Form Controllers
> 
> We don't need to vote right now; we're just gathering opinions :-)
> 
> The decision will also depend on the final size of the Portlet support. If
> it turns out to be too small for a separate subproject, including it in the
> core distribution might be the only feasible way to go.
> 
> Juergen
> 
> 
> -----Original Message-----
> From: spr...@li...
> [mailto:spr...@li...]On Behalf
> Of Ken Krebs
> Sent: Friday, March 04, 2005 11:47 PM
> To: spr...@li...
> Subject: Re: [Springframework-developer] Portlet Form Controllers
> 
> 
> +1 for subproject status.
> It makes sense to me to let them evolve in a more loosely coupled way,
> especially as Juergen points out given the small target audience for
> portlets.
> 
> Juergen Hoeller wrote:
> 
> 
>>As I said, a subproject is just under consideration. The alternative is to
>>release the portlet support as part of the core Spring 1.3 distribution.
> 
> The
> 
>>rationale of factoring out subprojects is to let the core concentrate on
> 
> its
> 
>>current scope and not introduce completely new areas of functionality. A
>>secondary goal is to limit the size of spring.jar.
>>
>>The current core web support and web MVC framework is used by the portlet
>>support underneath, for example to render views (at least that was the case
>>last year). So Spring Portlet depends on Spring core web (even core web
>>MVC), but not the other way round: a case for core web MVC staying part of
>>the core distribution, but Portlet support (optionally) becoming a separate
>>subproject.
>>
>>Note that Spring's core web support is of interest to many people: not only
>>to web application people, but also to rich client developers accessing
>>HTTP-based remote services (running in a Servlet container). Portlet
> 
> support
> 
>>is more specific and has a narrower target audience.
>>
>>A further advantage of a separate subproject is that it can evolve more
>>easily. Specific sample applications, tutorials, tools etc can be added
>>without having to worry about scope or size of the core Spring
> 
> distribution.
> 
>>Anyway, this has not been decided yet and does not have to be decided right
>>now. It's gonna become an important topic after the Spring 1.2 release,
>>though.
>>
>>Juergen
>>
>>
>>
>>-----Original Message-----
>>From: spr...@li...
>>[mailto:spr...@li...]On Behalf
>>Of Jean-Pol Landrain
>>Sent: Friday, March 04, 2005 7:29 PM
>>To: spr...@li...
>>Subject: Re: [Springframework-developer] Portlet Form Controllers
>>
>>
>>I quite agree with Rob. Except, of course, if you plan to create a
>>subproject for Spring MVC too. This would allow a Spring "à la carte".
>>This would keep the framework light, but would perhaps be a bit confusing
> 
> to
> 
>>the users. Perhaps a "plugin" functionnality would be nice if the number of
>>projects grows : you would have a core Spring and be able to plug in, for
>>example by using a dedicated XML file, the other sub-projects you want to
>>use. That's just an idea.
>>
>>Cheers,
>>Jean-Pol.
>>
>>----- Original Message -----
>>From: "Rob Butler" <cro...@ya...>
>>To: <spr...@li...>
>>Sent: Friday, March 04, 2005 7:01 PM
>>Subject: Re: [Springframework-developer] Portlet Form Controllers
>>
>>
>>
>>
>>
>>>Why would you have a separate sub-project for the
>>>portlet support in Spring?  That would be like having
>>>a separate sub-project for the web MVC stuff, and a
>>>separate sub-project for the DAO related stuff, and
>>>another one for AOP, etc.
>>>
>>>Later
>>>Rob
>>>--- Juergen Hoeller <ju...@in...> wrote:
>>>
>>>
>>>
>>>
>>>>Sounds like good stuff :-)
>>>>
>>>>On this occasion: Let's discuss the road to an
>>>>official release of the
>>>>Portlet support. We consider releasing the Portlet
>>>>support as an official
>>>>subproject, i.e. as a separate distribution and with
>>>>a separate CVS module
>>>>(or even separate CVS repository). The association
>>>>would be similar to the
>>>>just-announced Spring subproject status of Acegi
>>>>Security, and the already
>>>>established status of Spring RCP.
>>>>
>>>>Very importantly, the portlet subproject needs a
>>>>dedicated developer team.
>>>>Any volunteers? :-)
>>>>
>>>>Juergen
>>>>
>>>>
>>>>-----Original Message-----
>>>>From:
>>>>
>>>>
>>>>
>>>
>>>spr...@li...
>>>
>>>
>>>[mailto:spr...@li...]On
>>>
>>>
>>>
>>>>Behalf
>>>>Of John Lewis
>>>>Sent: Thursday, March 03, 2005 6:53 PM
>>>>To: spr...@li...
>>>>Subject: [Springframework-developer] Portlet Form
>>>>Controllers
>>>>
>>>>
>>>>We've been working on porting a fairly complex
>>>>enterprise application
>>>
>>>>from the Spring Servlet MVC framework to the Spring
>>>
>>>>Portlet MVC
>>>>framework.  As Nick Lothian and Rainer Schmitz
>>>>discovered, the Form
>>>>Controller hierarchy is difficult to port over from
>>>>the Servlet area to
>>>>the Portlet area because of the two-phase nature of
>>>>portlet requests.
>>>>Since we were porting a large number of existing
>>>>controllers descended
>>>
>>>>from AbstractController, AbstractFormController, or
>>>
>>>>SimpleFormController, it was critical to that all
>>>>the former
>>>>functionality of these parent be present and that
>>>>our logic work the
>>>>same as before.
>>>>
>>>>Nick Lothian's version of
>>>>SimplePortletFormController gave us a good
>>>>starting point and helped us understand a lot of the
>>>>issues with portlet
>>>>development in general and with Spring portlets in
>>>>particular.  However,
>>>>a lot of our controllers manage database content, so
>>>>we needed proper
>>>>separation between the action and render phase of
>>>>the request, which
>>>>this controller did not give us.
>>>>
>>>>Rainer Schmitz's work went much further and provided
>>>>the traditional
>>>>hierarchy of controllers and further demonstrated
>>>>the issues with
>>>>separating out the two phases of the portlet
>>>>request.  However, these
>>>>still did not give us the complete control that we
>>>>needed.  We
>>>>especially needed a version of SimpleFormController
>>>>that could handle
>>>>the separation of the action logic from the render
>>>>logic.
>>>>
>>>>Over the past few months we have developed a new set
>>>>of the
>>>>AbstractController, BaseCommandController,
>>>>AbstractFormController, and
>>>>SimpleFormController classes that we think
>>>>rigorously address all the
>>>>issues with portlet development and that have
>>>>allowed us to port over
>>>>existing servlet controllers with relative ease.
>>>>
>>>>We've included a portlet version of
>>>>WebContentGenerator to give the
>>>>controller classes their proper ancestry and provide
>>>>control over things
>>>>like content caching and access to the web
>>>>application context and to
>>>>centralized logging.
>>>>
>>>>We've also create a new set of the binding classes
>>>>(PortletRequestDataBinder,
>>>>PortletRequestParameterPropertyValues and
>>>>PortletRequestBindingException) that support special
>>>>field markers,
>>>>correct problems with form elements such as radio
>>>>buttons and
>>>>checkboxes, and handle redisplay of invalid submits
>>>>of non-string
>>>>parameters properly.
>>>>
>>>>All of the classes are fully documented, including
>>>>workflow descriptions
>>>>in the controllers that cover the special nature of
>>>>portlet development.
>>>>
>>>>Our hope is that these classes can handle the needs
>>>>of everyone working
>>>>with form controllers in Spring portlets and that
>>>>these can be merged
>>>>into the sandbox source code.
>>>>
>>>>The classes are posted in a zip file on the Spring
>>>>Portlet Wiki page at:
>>>>
>>>>
>>>>
>>>
>>>http://opensource.atlassian.com/confluence/spring/display/JSR168/
>>>
>>>
>>>
>>>>The link to the file is (sorry for the long link):
>>>>
>>>>
>>>>
>>
>>http://opensource.atlassian.com/confluence/spring/download/attachments/10/s
> 
> p
> 
>>
>>>>ring-portlet-controllers.zip
>>>>
>>>>Please send me any questions or comments you may
>>>>have about these
>>>>classes.  We are eager to support their adoption in
>>>>the Spring Portlet
>>>>community.
>>>>
>>>>John Lewis
>>>>jl...@ar...
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>

RE: [Springframework-developer] Portlet Form Controllers

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

I am also in favor of the option that allows the portlet subproject to =
move
ahead as quickly as it can.  We are working on a portlet project here at =
my
company and we've decided to settle on Spring's MVC, and am more than
willing to contribute any improvements that may come along to the =
Portlet
subproject as well. =20

-tim

-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf =
Of
Juergen Hoeller
Sent: Friday, March 04, 2005 5:54 PM
To: spr...@li...
Subject: Re: [Springframework-developer] Portlet Form Controllers

We don't need to vote right now; we're just gathering opinions :-)

The decision will also depend on the final size of the Portlet support. =
If
it turns out to be too small for a separate subproject, including it in =
the
core distribution might be the only feasible way to go.

Juergen


-----Original Message-----
From: spr...@li...
[mailto:spr...@li...]On Behalf
Of Ken Krebs
Sent: Friday, March 04, 2005 11:47 PM
To: spr...@li...
Subject: Re: [Springframework-developer] Portlet Form Controllers


+1 for subproject status.
It makes sense to me to let them evolve in a more loosely coupled way,
especially as Juergen points out given the small target audience for
portlets.

Juergen Hoeller wrote:

>As I said, a subproject is just under consideration. The alternative is =
to
>release the portlet support as part of the core Spring 1.3 =
distribution.
The
>rationale of factoring out subprojects is to let the core concentrate =
on
its
>current scope and not introduce completely new areas of functionality. =
A
>secondary goal is to limit the size of spring.jar.
>
>The current core web support and web MVC framework is used by the =
portlet
>support underneath, for example to render views (at least that was the =
case
>last year). So Spring Portlet depends on Spring core web (even core web
>MVC), but not the other way round: a case for core web MVC staying part =
of
>the core distribution, but Portlet support (optionally) becoming a =
separate
>subproject.
>
>Note that Spring's core web support is of interest to many people: not =
only
>to web application people, but also to rich client developers accessing
>HTTP-based remote services (running in a Servlet container). Portlet
support
>is more specific and has a narrower target audience.
>
>A further advantage of a separate subproject is that it can evolve more
>easily. Specific sample applications, tutorials, tools etc can be added
>without having to worry about scope or size of the core Spring
distribution.
>
>Anyway, this has not been decided yet and does not have to be decided =
right
>now. It's gonna become an important topic after the Spring 1.2 release,
>though.
>
>Juergen
>
>
>
>-----Original Message-----
>From: spr...@li...
>[mailto:spr...@li...]On Behalf
>Of Jean-Pol Landrain
>Sent: Friday, March 04, 2005 7:29 PM
>To: spr...@li...
>Subject: Re: [Springframework-developer] Portlet Form Controllers
>
>
>I quite agree with Rob. Except, of course, if you plan to create a
>subproject for Spring MVC too. This would allow a Spring "=E0 la =
carte".
>This would keep the framework light, but would perhaps be a bit =
confusing
to
>the users. Perhaps a "plugin" functionnality would be nice if the =
number of
>projects grows : you would have a core Spring and be able to plug in, =
for
>example by using a dedicated XML file, the other sub-projects you want =
to
>use. That's just an idea.
>
>Cheers,
>Jean-Pol.
>
>----- Original Message -----
>From: "Rob Butler" <cro...@ya...>
>To: <spr...@li...>
>Sent: Friday, March 04, 2005 7:01 PM
>Subject: Re: [Springframework-developer] Portlet Form Controllers
>
>
>
>
>>Why would you have a separate sub-project for the
>>portlet support in Spring?  That would be like having
>>a separate sub-project for the web MVC stuff, and a
>>separate sub-project for the DAO related stuff, and
>>another one for AOP, etc.
>>
>>Later
>>Rob
>>--- Juergen Hoeller <ju...@in...> wrote:
>>
>>
>>
>>>Sounds like good stuff :-)
>>>
>>>On this occasion: Let's discuss the road to an
>>>official release of the
>>>Portlet support. We consider releasing the Portlet
>>>support as an official
>>>subproject, i.e. as a separate distribution and with
>>>a separate CVS module
>>>(or even separate CVS repository). The association
>>>would be similar to the
>>>just-announced Spring subproject status of Acegi
>>>Security, and the already
>>>established status of Spring RCP.
>>>
>>>Very importantly, the portlet subproject needs a
>>>dedicated developer team.
>>>Any volunteers? :-)
>>>
>>>Juergen
>>>
>>>
>>>-----Original Message-----
>>>From:
>>>
>>>
>>>
>>spr...@li...
>>
>>
>>[mailto:spr...@li...]On
>>
>>
>>>Behalf
>>>Of John Lewis
>>>Sent: Thursday, March 03, 2005 6:53 PM
>>>To: spr...@li...
>>>Subject: [Springframework-developer] Portlet Form
>>>Controllers
>>>
>>>
>>>We've been working on porting a fairly complex
>>>enterprise application
>>>from the Spring Servlet MVC framework to the Spring
>>>Portlet MVC
>>>framework.  As Nick Lothian and Rainer Schmitz
>>>discovered, the Form
>>>Controller hierarchy is difficult to port over from
>>>the Servlet area to
>>>the Portlet area because of the two-phase nature of
>>>portlet requests.
>>>Since we were porting a large number of existing
>>>controllers descended
>>>from AbstractController, AbstractFormController, or
>>>SimpleFormController, it was critical to that all
>>>the former
>>>functionality of these parent be present and that
>>>our logic work the
>>>same as before.
>>>
>>>Nick Lothian's version of
>>>SimplePortletFormController gave us a good
>>>starting point and helped us understand a lot of the
>>>issues with portlet
>>>development in general and with Spring portlets in
>>>particular.  However,
>>>a lot of our controllers manage database content, so
>>>we needed proper
>>>separation between the action and render phase of
>>>the request, which
>>>this controller did not give us.
>>>
>>>Rainer Schmitz's work went much further and provided
>>>the traditional
>>>hierarchy of controllers and further demonstrated
>>>the issues with
>>>separating out the two phases of the portlet
>>>request.  However, these
>>>still did not give us the complete control that we
>>>needed.  We
>>>especially needed a version of SimpleFormController
>>>that could handle
>>>the separation of the action logic from the render
>>>logic.
>>>
>>>Over the past few months we have developed a new set
>>>of the
>>>AbstractController, BaseCommandController,
>>>AbstractFormController, and
>>>SimpleFormController classes that we think
>>>rigorously address all the
>>>issues with portlet development and that have
>>>allowed us to port over
>>>existing servlet controllers with relative ease.
>>>
>>>We've included a portlet version of
>>>WebContentGenerator to give the
>>>controller classes their proper ancestry and provide
>>>control over things
>>>like content caching and access to the web
>>>application context and to
>>>centralized logging.
>>>
>>>We've also create a new set of the binding classes
>>>(PortletRequestDataBinder,
>>>PortletRequestParameterPropertyValues and
>>>PortletRequestBindingException) that support special
>>>field markers,
>>>correct problems with form elements such as radio
>>>buttons and
>>>checkboxes, and handle redisplay of invalid submits
>>>of non-string
>>>parameters properly.
>>>
>>>All of the classes are fully documented, including
>>>workflow descriptions
>>>in the controllers that cover the special nature of
>>>portlet development.
>>>
>>>Our hope is that these classes can handle the needs
>>>of everyone working
>>>with form controllers in Spring portlets and that
>>>these can be merged
>>>into the sandbox source code.
>>>
>>>The classes are posted in a zip file on the Spring
>>>Portlet Wiki page at:
>>>
>>>
>>>
>>http://opensource.atlassian.com/confluence/spring/display/JSR168/
>>
>>
>>>The link to the file is (sorry for the long link):
>>>
>>>
>>>
>http://opensource.atlassian.com/confluence/spring/download/attachments/1=
0/s
p
>
>
>>>ring-portlet-controllers.zip
>>>
>>>Please send me any questions or comments you may
>>>have about these
>>>classes.  We are eager to support their adoption in
>>>the Spring Portlet
>>>community.
>>>
>>>John Lewis
>>>jl...@ar...
>>>
>>>
>>>
>>>
>>>
>>>




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id=14396&op=3Dick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

[Springframework-developer] Nucleus

[James E. <jam...@gm...>]

I'm on a project now that is using ATG Dynamo.  While I don't like
Dynamo so much, I do think there IoC container, Nucleus, while very
simple, is pretty nice.  I especially like the way it handles
namespacing.  I was just wondering if the list had any experience with
it/opinions on it?  It has been around since 1997 and handles
constructor-based and setter-based injection.  I still prefer
Spring...but I do think that Nucleus has some ideas worth looking at.

In a nutshell, the container is provided a list of folders to use a
its search path.  The folders contain .properties files that hold the
bean definitions (one file per bean).  The location of the file in the
folder + the file name (minus .properties) becomes the bean's fully
qualified name.  For example, if you have /com/foo/Test.properties,
then the container has a bean whose id is /com/foo/Test and the bean
is defined by the properties in the file.  There is a special $class
property that identifies the class to instantiate, then the other
properties are injected into the bean.  You can refer to other beans
in the container too:
dataSource=/com/foo/DataSource
If a bean definition is located in multiple folders in the search
path, the files are combined in memory...where properties defined
later will overwrite those defined earlier in the path.
There is also a lifecycle the beans can participate in, but they
require the use of Marker Interfaces.

Pretty much the entire Server is built on top of Nucleus.  There is an
admin console that you can use to browse the container at runtime and
modify the values (configured and live) for the beans (even the beans
for webapps).  I keep seeing it as a cross between JNDI, IoC
container, and JMX...at least conceptually.  It sounds a bit in the
same vein as what is happening with Geronimo (at least from the very
little I've heard).

Again, just wondering what other people thought. I'd never heard of it
before 2 weeks ago even thought its been around for 8 years.  I guess
that should be expected since it is proprietary and specific to ATG. 
I really think it would have served ATG better to open source Nucleus
and Repository (their ORM framework...similar to hibernate).  As it
stands there is a huge learning curve for developers coming
in...having it out there would have reduced that some...if people
picked it up and liked it that is ;).
If interested, you can read the details at
http://www.atg.com/repositories/ContentCatalogRepository_en/manuals/ATG7.0/dynprog/index.html
Chapter 2.


James

[Springframework-developer] Re: Spring supports JDO2 ?

[Jack T. <hi...@gm...>]

And really sorry for it. Five mins later, I got the answer. there is
no sun's jdo2.jar and jpox-...jar contains some RI. Finally, I remove
jdo.jar from WEB-INF/lib, everything works

/Jack


On Tue, 8 Mar 2005 17:15:19 +0800, Jack Tang <hi...@gm...> wrote:
> Hi Spring guys
> 
> Does spring support JDO2? I have gooogled, it said yes. And I followed
> the tutorial <http://www.jpox.org/docs/1_1/tutorials/springframework.html>.
> Some exceptions here:
> 
> ERROR  - Context initialization failed
> org.springframework.beans.factory.BeanCreationException: Error creating bean wit
> h name 'jdoPMF' defined in ServletContext resource [/WEB-INF/applicationContext-
> dao.xml]: Initialization of bean failed; nested exception is javax.jdo.JDOFatalU
> serException: JDO 2.0 capabilities cannot be accessed! Please make sure that you
> do not have a JDO 1.0 jar in front of the JDO 2 classes in your CLASSPATH.
> javax.jdo.JDOFatalUserException: JDO 2.0 capabilities cannot be accessed! Please
> make sure that you do not have a JDO 1.0 jar in front of the JDO 2 classes in y
> our CLASSPATH.
>        at org.jpox.AbstractPersistenceManagerFactory.<init>(AbstractPersistence
> ManagerFactory.java:113)
>        at org.jpox.PersistenceManagerFactoryImpl.<init>(PersistenceManagerFacto
> ryImpl.java:437)
>        at org.jpox.PersistenceManagerFactoryImpl.getPersistenceManagerFactory(P
> ersistenceManagerFactoryImpl.java:80)
>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
> 
> My spring version is 1.1.5, with jpox version 1.1.0-beta-1, and
> jdo.jar I copyed it from Spring's lib.
> So, any suggestions on how to make Spring and JDO2 harmonic?
> Thanks
> 
> /Jack
>

[Springframework-developer] Spring supports JDO2 ?

[Jack T. <hi...@gm...>]

Hi Spring guys

Does spring support JDO2? I have gooogled, it said yes. And I followed
the tutorial <http://www.jpox.org/docs/1_1/tutorials/springframework.html>.
Some exceptions here:

ERROR  - Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean wit
h name 'jdoPMF' defined in ServletContext resource [/WEB-INF/applicationContext-
dao.xml]: Initialization of bean failed; nested exception is javax.jdo.JDOFatalU
serException: JDO 2.0 capabilities cannot be accessed! Please make sure that you
 do not have a JDO 1.0 jar in front of the JDO 2 classes in your CLASSPATH.
javax.jdo.JDOFatalUserException: JDO 2.0 capabilities cannot be accessed! Please
 make sure that you do not have a JDO 1.0 jar in front of the JDO 2 classes in y
our CLASSPATH.
        at org.jpox.AbstractPersistenceManagerFactory.<init>(AbstractPersistence
ManagerFactory.java:113)
        at org.jpox.PersistenceManagerFactoryImpl.<init>(PersistenceManagerFacto
ryImpl.java:437)
        at org.jpox.PersistenceManagerFactoryImpl.getPersistenceManagerFactory(P
ersistenceManagerFactoryImpl.java:80)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)

My spring version is 1.1.5, with jpox version 1.1.0-beta-1, and
jdo.jar I copyed it from Spring's lib.
So, any suggestions on how to make Spring and JDO2 harmonic?
Thanks

/Jack

Re: [Springframework-developer] cleanup of src/ tree, removing eclipse warnings

[Seth L. <set...@gm...>]

On Mon, 7 Mar 2005 21:21:36 +0100, Juergen Hoeller
<ju...@in...> wrote:
> Thanks, Seth. I've cleaned up the imports - those emerged when I removed
> deprecated methods for 1.2 RC1; I didn't perform an "optimize imports" step
> afterwards...
> 
> Regarding "perform" vs "execute" on a Tiles component controller in
> TilesView: I guess it's better to call "perform" there for the time being,
> to stay backwards compatible with Struts 1.1 (IIRC, "perform" was deprecated
> as recently as Struts 1.2).

OK, sounds good.

Thanks!
Seth


-- 
<a href="http://www.picklematrix.net/foaf.rdf">Seth Ladd's FOAF</a>
<a href="http://www.foaf-project.org/">What is FOAF?</a>

Re: [Springframework-developer] cleanup of src/ tree, removing eclipse warnings

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

Thanks, Seth. I've cleaned up the imports - those emerged when I removed
deprecated methods for 1.2 RC1; I didn't perform an "optimize imports" step
afterwards...

Regarding "perform" vs "execute" on a Tiles component controller in
TilesView: I guess it's better to call "perform" there for the time being,
to stay backwards compatible with Struts 1.1 (IIRC, "perform" was deprecated
as recently as Struts 1.2).

Juergen


-----Original Message-----
From: spr...@li...
[mailto:spr...@li...]On Behalf
Of Seth Ladd
Sent: Monday, March 07, 2005 9:05 PM
To: spr...@li...
Subject: [Springframework-developer] cleanup of src/ tree, removing
eclipse warnings


Hello,

Here's a small patch that cleans up unused import statements and fixes
one deprecated method.  Only four files were touched.  This patch was
made against the HEAD.

Hope it helps,
Seth

--
<a href="http://www.picklematrix.net/foaf.rdf">Seth Ladd's FOAF</a>
<a href="http://www.foaf-project.org/">What is FOAF?</a>

[Springframework-developer] cleanup of src/ tree, removing eclipse warnings

[Seth L. <set...@gm...>]

Hello,

Here's a small patch that cleans up unused import statements and fixes
one deprecated method.  Only four files were touched.  This patch was
made against the HEAD.

Hope it helps,
Seth

-- 
<a href="http://www.picklematrix.net/foaf.rdf">Seth Ladd's FOAF</a>
<a href="http://www.foaf-project.org/">What is FOAF?</a>