springframework-developer — Spring Framework developers list

Re: [Springframework-developer] Final preparations for 1.1 RC1

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

On Sat, 24 Jul 2004 15:12:53 +0200, j=FCrgen h=F6ller [werk3AT]
<jue...@we...> wrote:
> Darren,
>=20
> Oops, I forgot to discuss that one: The reason why I removed the htmlEsca=
pe property from the "springBind" macro is to be able to participate in a R=
equestContext-level default, e.g. set via springMacroRequestContext.setDefa=
ultHtmlEscape(true). Note that the createBindStatus invocation on RequestCo=
ntext uses the defaultHtmlEscape flag then.
>=20
> I've just adapted the RequestContext implementation a bit further to also=
 be able to participate in a ServletContext-level default, just like our JS=
P tags can, i.e. a "defaultHtmlEscape" context-param in web.xml. JSP tags a=
nd Velocity/FreeMarker macros can then even share such an application-wide =
default. I'll commit this promptly.
>=20

Would it be appropriate to add a application-wide config param called
'usingDtd' with values such as 'XHTML1.0Strict" or "HTML4.01".  This
would help tags that do omit HTML to omit  the proper markup.  This
would be useful for the convenience form macros.

Thanks,
Seth

Re: [Springframework-developer] Final preparations for 1.1 RC1

[<jue...@we...>]

Actually, the same issue occurs with FreeMarker too: We specify =
"escape=3Dfalse" there, so do not participate in any default. This needs =
to be addressed: We should allow to work with the defaultHtmlEscape =
value here too.
=20
While we could introduce a further "escape" value for "use default", =
offering a special method signature for it, it's probably clearer two =
offer two FreeMarker macros: "spring:bind" which never takes an "escape" =
parameter (i.e. always uses the default), and "spring:bindEscaped" which =
takes a required "escape" parameter. This would be analogous to Velocity =
again then.
=20
However, there's still the naming issue: "bind" uses the default HTML =
escape setting. But how to the name the version that takes an explicit =
HTML escape parameter? Is there a better name than "bindEscaped"?
=20
This is easier with JSP tags, where there can be a true tag-internal =
default if the "setHtmlEscape" method was not called... As far as I can =
see, even FreeMarker just allows for an explicitly specified default in =
the macro definition: It cannot seamlessly invoke either =
RequestContext.createBindStatus(path) respectively =
RequestContext.createBindStatus(path, htmlEscape), in our concrete case.
=20
Juergen
=20

________________________________

Von: spr...@li... im Auftrag =
von j=FCrgen h=F6ller [werk3AT]
Gesendet: Sa 24.07.2004 15:12
An: spr...@li...
Betreff: Re: [Springframework-developer] Final preparations for 1.1 RC1



Darren,

Oops, I forgot to discuss that one: The reason why I removed the =
htmlEscape property from the "springBind" macro is to be able to =
participate in a RequestContext-level default, e.g. set via =
springMacroRequestContext.setDefaultHtmlEscape(true). Note that the =
createBindStatus invocation on RequestContext uses the defaultHtmlEscape =
flag then.

I've just adapted the RequestContext implementation a bit further to =
also be able to participate in a ServletContext-level default, just like =
our JSP tags can, i.e. a "defaultHtmlEscape" context-param in web.xml. =
JSP tags and Velocity/FreeMarker macros can then even share such an =
application-wide default. I'll commit this promptly.

Actually, the "springBindEscaped" macro should rather take an explicit =
htmlEscape parameter, to be able to override defaultHtmlEscape=3Dtrue to =
false for a specific macro. Hmm, what name could we use for this? =
"springBindWithExplicitEscape" is clearly too long... "springBind" with =
overloaded signature is not possible in Velocity... maybe still =
"springBindEscaped", but just with an explicit parameter?


Matt,

Note that the "springMacroRequestContext" is not really meant to be =
accessed directly; it is mainly meant to be used by Spring-provided =
macros. If you want to use a RequestContext in your own expressions, =
always specify the "requestContextAttribute" accordingly. We should =
highlight that in the docs.


Juergen


________________________________

Von: spr...@li... im Auftrag =
von Darren Davison
Gesendet: Sa 24.07.2004 10:18
An: spr...@li...
Betreff: Re: [Springframework-developer] Final preparations for 1.1 RC1



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 24 July 2004 01:09, Matt Raible wrote:
> I tried this out today and it works well.  The only thing I saw that
> might cause confusion for users is there are 2 macros for Velocity
> (#springBind and #springBindEscaped) - whereas FreeMarker has one w/ =
an
> "escape" parameter.  I imagine that folks using FreeMarker might be
> migrating from Velocity, so making the macros consistent might be
> helpful.  Who knows - just a thought.

FreeMarker has a default value of false for the 2nd param so you only =
need
supply it to override it.  Velocity can't do that.

The other options for Velocity are:

 * always supply the second parameter in every call to springBind

 * use a globally scoped, well-known variable defined in user templates.


I prefer personally to always require the additional parameter.  It's =
more
consistent with FM and won't cause user templates to break if they =
migrate
them to FM using the automatic conversion tool they have available.

What do you think?


> I would make sure and document that the name =
"springMacroRequestContext"
> can be overridden by specifying a "requestContextAttribute" property.
> It's much easier to write $rc.getMessage() than
> $springMacroRequestContext.getMessage(). ;-)

I will, thanks.

- --
Darren Davison
Public Key: http://www.davison.uk.net/pages/key.htm
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBAhtIKLMLAN01aw0RAisgAKCfjnl6dzgkdQ91o9lUrUvtd9RGWQCfRJNq
cn71Z/8ovFjaDLQRxtBwTfo=3D
=3Dlvg2
-----END PGP SIGNATURE-----


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idG21&alloc_id=10040&op=3Dick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer




-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idG21&alloc_id=10040&op=3Dick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] Serialization of AOP proxies

[Rod J. <rod...@in...>]

Rob

Please commit.

Cheers
Rod

----- Original Message -----
From: "Rob Harrop" <ro...@ca...>
To: <spr...@li...>
Sent: Saturday, July 24, 2004 3:03 PM
Subject: RE: [Springframework-developer] Serialization of AOP proxies


> To add to this:
>
> Cglib proxies are also now serializable provided that the TargetSource and
> Advisors are serializable.
>
> Haven't committed this yet, waiting for 1.1 RC1 to go out. If you are
> desperate to see then I will post in JIRA or something.
>
> Rob
>
> -----Original Message-----
> From: spr...@li...
> [mailto:spr...@li...] On Behalf
Of
> Rod Johnson
> Sent: 23 July 2004 19:29
> To: spr...@li...
> Subject: [Springframework-developer] Serialization of AOP proxies
>
> AOP users,
>
> I've just committed a feature that has been requested several times:
> serializability of AOP proxies.
>
> AOP proxies are now serializable if they're:
>
> - JDK dynamic proxies
> - all Advisors (meaning Pointcut + Advice) are serializable
> - TargetSource is serializable (normally only the target matters)
>
> I've made some framework classes Serializable such as Pointcut.TRUE and
> DefaultPointcutAdvisor, but the onus is on the developer to mark as
> serializable an Advice/Pointcut that may be serialized.
>
> This will be released in 1.1 RC1.
>
> We will also consider serializability for CGLIB proxies.
>
> Rgds
> Rod
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer

RE: [Springframework-developer] Serialization of AOP proxies

[Rob H. <ro...@ca...>]

Further update:

After discussion with Rod decided to commit the Cglib proxy change in time
for 1.1 RC1

Rob

-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf Of
Rod Johnson
Sent: 23 July 2004 19:29
To: spr...@li...
Subject: [Springframework-developer] Serialization of AOP proxies

AOP users,

I've just committed a feature that has been requested several times:
serializability of AOP proxies.

AOP proxies are now serializable if they're:

- JDK dynamic proxies
- all Advisors (meaning Pointcut + Advice) are serializable
- TargetSource is serializable (normally only the target matters)

I've made some framework classes Serializable such as Pointcut.TRUE and
DefaultPointcutAdvisor, but the onus is on the developer to mark as
serializable an Advice/Pointcut that may be serialized.

This will be released in 1.1 RC1.

We will also consider serializability for CGLIB proxies.

Rgds
Rod




-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

RE: [Springframework-developer] Serialization of AOP proxies

[Rob H. <ro...@ca...>]

To add to this:

Cglib proxies are also now serializable provided that the TargetSource and
Advisors are serializable.

Haven't committed this yet, waiting for 1.1 RC1 to go out. If you are
desperate to see then I will post in JIRA or something.

Rob

-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf Of
Rod Johnson
Sent: 23 July 2004 19:29
To: spr...@li...
Subject: [Springframework-developer] Serialization of AOP proxies

AOP users,

I've just committed a feature that has been requested several times:
serializability of AOP proxies.

AOP proxies are now serializable if they're:

- JDK dynamic proxies
- all Advisors (meaning Pointcut + Advice) are serializable
- TargetSource is serializable (normally only the target matters)

I've made some framework classes Serializable such as Pointcut.TRUE and
DefaultPointcutAdvisor, but the onus is on the developer to mark as
serializable an Advice/Pointcut that may be serialized.

This will be released in 1.1 RC1.

We will also consider serializability for CGLIB proxies.

Rgds
Rod




-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] Final preparations for 1.1 RC1

[<jue...@we...>]

Darren,
=20
Oops, I forgot to discuss that one: The reason why I removed the =
htmlEscape property from the "springBind" macro is to be able to =
participate in a RequestContext-level default, e.g. set via =
springMacroRequestContext.setDefaultHtmlEscape(true). Note that the =
createBindStatus invocation on RequestContext uses the defaultHtmlEscape =
flag then.
=20
I've just adapted the RequestContext implementation a bit further to =
also be able to participate in a ServletContext-level default, just like =
our JSP tags can, i.e. a "defaultHtmlEscape" context-param in web.xml. =
JSP tags and Velocity/FreeMarker macros can then even share such an =
application-wide default. I'll commit this promptly.
=20
Actually, the "springBindEscaped" macro should rather take an explicit =
htmlEscape parameter, to be able to override defaultHtmlEscape=3Dtrue to =
false for a specific macro. Hmm, what name could we use for this? =
"springBindWithExplicitEscape" is clearly too long... "springBind" with =
overloaded signature is not possible in Velocity... maybe still =
"springBindEscaped", but just with an explicit parameter?
=20
=20
Matt,
=20
Note that the "springMacroRequestContext" is not really meant to be =
accessed directly; it is mainly meant to be used by Spring-provided =
macros. If you want to use a RequestContext in your own expressions, =
always specify the "requestContextAttribute" accordingly. We should =
highlight that in the docs.
=20
=20
Juergen
=20

________________________________

Von: spr...@li... im Auftrag =
von Darren Davison
Gesendet: Sa 24.07.2004 10:18
An: spr...@li...
Betreff: Re: [Springframework-developer] Final preparations for 1.1 RC1



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 24 July 2004 01:09, Matt Raible wrote:
> I tried this out today and it works well.  The only thing I saw that
> might cause confusion for users is there are 2 macros for Velocity
> (#springBind and #springBindEscaped) - whereas FreeMarker has one w/ =
an
> "escape" parameter.  I imagine that folks using FreeMarker might be
> migrating from Velocity, so making the macros consistent might be
> helpful.  Who knows - just a thought.

FreeMarker has a default value of false for the 2nd param so you only =
need
supply it to override it.  Velocity can't do that.

The other options for Velocity are:

 * always supply the second parameter in every call to springBind

 * use a globally scoped, well-known variable defined in user templates.


I prefer personally to always require the additional parameter.  It's =
more
consistent with FM and won't cause user templates to break if they =
migrate
them to FM using the automatic conversion tool they have available.

What do you think?


> I would make sure and document that the name =
"springMacroRequestContext"
> can be overridden by specifying a "requestContextAttribute" property.
> It's much easier to write $rc.getMessage() than
> $springMacroRequestContext.getMessage(). ;-)

I will, thanks.

- --
Darren Davison
Public Key: http://www.davison.uk.net/pages/key.htm
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBAhtIKLMLAN01aw0RAisgAKCfjnl6dzgkdQ91o9lUrUvtd9RGWQCfRJNq
cn71Z/8ovFjaDLQRxtBwTfo=3D
=3Dlvg2
-----END PGP SIGNATURE-----


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idG21&alloc_id=10040&op=3Dick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

[Springframework-developer] simple compile typo in sandbox src

[jbetancourt <jbe...@co...>]

org.springframework.metadata.ant.MetadataCompilerAdapter




Index: MetadataCompilerAdapter.java
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
RCS file: =
/cvsroot/springframework/spring/sandbox/src/org/springframework/metadata/=
ant/MetadataCompilerAdapter.java,v
retrieving revision 1.1
diff -u -r1.1 MetadataCompilerAdapter.java
--- MetadataCompilerAdapter.java 22 Nov 2003 09:05:47 -0000 1.1
+++ MetadataCompilerAdapter.java 24 Jul 2004 10:22:33 -0000
@@ -47,7 +47,7 @@
         originalAdapter.setJavac(_javac);
         boolean javacOK =3D originalAdapter.execute();
=20
-        if (javacOK =3D false) {
+        if (javacOK =3D=3D false) {
             return false;
         } else {
=20

Re: [Springframework-developer] Final preparations for 1.1 RC1

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

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 24 July 2004 01:09, Matt Raible wrote:
> I tried this out today and it works well.  The only thing I saw that
> might cause confusion for users is there are 2 macros for Velocity
> (#springBind and #springBindEscaped) - whereas FreeMarker has one w/ an
> "escape" parameter.  I imagine that folks using FreeMarker might be
> migrating from Velocity, so making the macros consistent might be
> helpful.  Who knows - just a thought.

=46reeMarker has a default value of false for the 2nd param so you only nee=
d=20
supply it to override it.  Velocity can't do that.

The other options for Velocity are:

 * always supply the second parameter in every call to springBind

 * use a globally scoped, well-known variable defined in user templates.


I prefer personally to always require the additional parameter.  It's more=
=20
consistent with FM and won't cause user templates to break if they migrate=
=20
them to FM using the automatic conversion tool they have available.

What do you think?


> I would make sure and document that the name "springMacroRequestContext"
> can be overridden by specifying a "requestContextAttribute" property.
> It's much easier to write $rc.getMessage() than
> $springMacroRequestContext.getMessage(). ;-)

I will, thanks.

=2D --=20
Darren Davison
Public Key: http://www.davison.uk.net/pages/key.htm
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBAhtIKLMLAN01aw0RAisgAKCfjnl6dzgkdQ91o9lUrUvtd9RGWQCfRJNq
cn71Z/8ovFjaDLQRxtBwTfo=3D
=3Dlvg2
=2D----END PGP SIGNATURE-----

Re: [Springframework-developer] Final preparations for 1.1 RC1

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

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 24 July 2004 01:13, Matt Raible wrote:

> FYI...
>
> This doesn't work:
>
> <#import "spring.ftl" as spring />

hmm.. it works ok for me.

> But this does:
>
> <#import "/spring.ftl" as spring />
>
> Just thought it should be documented.

=2D --=20
Darren Davison
Public Key: http://www.davison.uk.net/pages/key.htm
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBAhmMKLMLAN01aw0RAuNlAKCJkf8+pnwIP4Bt31VwninHric7jgCeIA7v
w/4rPbU0TC06WZLKkIzVczw=3D
=3DWfZk
=2D----END PGP SIGNATURE-----

RE: [Springframework-developer] Final preparations for 1.1 RC1

[Matt R. <li...@ra...>]

>  
> * FreeMarkerConfigurer always registers an additional 
> ClassTemplateLoader now, being able to load macros from the 
> web.servlet.view.freemarker package. This means that a 
> FreeMarker template can simply import "spring.ftl" now, 
> rather than the lengthy 
> "org/springframework/web/servlet/view/freemarker/spring.ftl".

FYI...

This doesn't work:

<#import "spring.ftl" as spring />

But this does:

<#import "/spring.ftl" as spring />

Just thought it should be documented.

Matt

RE: [Springframework-developer] Final preparations for 1.1 RC1

[Matt R. <li...@ra...>]

I tried this out today and it works well.  The only thing I saw that
might cause confusion for users is there are 2 macros for Velocity
(#springBind and #springBindEscaped) - whereas FreeMarker has one w/ an
"escape" parameter.  I imagine that folks using FreeMarker might be
migrating from Velocity, so making the macros consistent might be
helpful.  Who knows - just a thought.

I would make sure and document that the name "springMacroRequestContext"
can be overridden by specifying a "requestContextAttribute" property.
It's much easier to write $rc.getMessage() than
$springMacroRequestContext.getMessage(). ;-)

Matt


> -----Original Message-----
> From: spr...@li...=20
> [mailto:spr...@li...]
>  On Behalf Of j=FCrgen h=F6ller [werk3AT]
> Sent: Friday, July 23, 2004 12:30 AM
> To: spr...@li...
> Subject: Re: [Springframework-developer] Final preparations=20
> for 1.1 RC1
>=20
>=20
> After giving it some more thought, I've just replaced the=20
> Velocity/FreeMarkerFormView subclasses with a=20
> "exposeSpringMacroHelpers" property in AbstractTemplateView,=20
> inherited by VelocityView and FreeMarkerView. This triggers=20
> the exposure of a RequestContext instance under the name=20
> "springMacroRequestContext", as expected by the macros in=20
> spring.vm and spring.ftl now.
> =20
> There's a new AbstractTemplateViewResolver that provided=20
> "exposeRequestAttributes", "exposeSessionAttributes" and=20
> "exposeSpringMacroHelpers" for all views. I've also added a=20
> FreeMarkerViewResolver as convenience subclass, as recently=20
> suggested by Matt Raible.
> =20
> I've used the term "Spring macros" rather than "form macros"=20
> or "bind macros", to allow for adding further default macros=20
> that do not necessarily focus on binding data for forms.
> =20
> If there aren't any objections, I'm about to commit these=20
> changes, as I believe they are worth it. Darren, what do you=20
> think? Do you maybe have the chance to adapt the docs accordingly?
> =20
> Juergen
> =20
>=20
> ________________________________
>=20
> Von: spr...@li... im=20
> Auftrag von j=FCrgen h=F6ller [werk3AT]
> Gesendet: Do 22.07.2004 17:44
> An: spr...@li...
> Betreff: Re: [Springframework-developer] Final preparations=20
> for 1.1 RC1
>=20
>=20
>=20
> Darren,
>=20
> I've just moved BindStatus and reworked the configuration=20
> part a bit. I've also removed BindStatusHelper and moved its=20
> createBindStatus methods to the RequestContext class itself.=20
> VelocityFormView and FreeMarkerFormView simply expose a=20
> RequestContext instance under the name=20
> "bindStatusRequestContext" now, accessed by the macros in=20
> spring.vm respectively spring.ftl.
>=20
> Regarding template loading, I've refined this a bit too:
>=20
> * FreeMarkerConfigurer always registers an additional=20
> ClassTemplateLoader now, being able to load macros from the=20
> web.servlet.view.freemarker package. This means that a=20
> FreeMarker template can simply import "spring.ftl" now,=20
> rather than the lengthy=20
> "org/springframework/web/servlet/view/freemarker/spring.ftl".
>=20
> * VelocityConfigurer always registers an additional=20
> ClasspathResourceLoader with the name "springFormMacro", plus=20
> the library "spring.vm" in the web.servlet.view.velocity=20
> package. Previously, the SpringResourceLoader was in=20
> potential conflict with a SpringResourceLoader from=20
> VelocityEngineFactory of the same name. Now, this should work=20
> with any kind and any number of primary resource loaders, as=20
> long as none is called "springFormMacro".
>=20
> What I'm still wondering is whether we need the subclasses=20
> VelocityFormView and FreeMarkerFormView at all: They just=20
> expose a RequestContext instance under a special name now. We=20
> could easily move that logic into VelocityView respectively=20
> FreeMarkerView itself, driven by a "enableBindMacros" flag.
>=20
> If the "enableBindMacros" flag existed on=20
> VelocityViewResolver and FreeMarkerViewResolver (to be=20
> created) too, it could be easily driven for all views. And=20
> there wouldn't be a need to override the viewClass property=20
> in that case. I'd prefer this over using view subclasses, as=20
> far as I can see.
>=20
> What do you think?
>=20
> Juergen
>=20
>=20
> ________________________________
>=20
> Von: spr...@li... im=20
> Auftrag von Darren Davison
> Gesendet: Mo 19.07.2004 12:33
> An: spr...@li...
> Betreff: Re: [Springframework-developer] Final preparations=20
> for 1.1 RC1
>=20
>=20
>=20
>=20
>=20
> > - I'd like to move BindStatus and the new BindStatusHelper=20
> class from=20
> > servlet.tags to servlet.support. JSPs using the BindTag=20
> should still=20
> > work, provided that they get freshly compiled. Any=20
> objections to this?
>=20
> I meant to raise this when I generalised the behaviour of=20
> them but it slipped my mind.  They should be moved to a=20
> non-tag specific package now.
>=20
> > - I'd like to refine resource loading in VelocityFormView and
> > FreeMarkerFormView: This is not entirely clean when combined with=20
> > custom resource paths yet, from a superficial glance.
>=20
> VelocityConfigurer (and respective FreeMarkerConfigurer)=20
> ensure a SpringResourceLoader is available for use, possibly=20
> in addition to any other resource loading strategy in the=20
> case of FreeMarker.  Does this not cover requirements?  I'm a=20
> little unclear on what's missing here..
>=20
> > Finally, regarding form simplification macros, i.e.=20
> Struts-style HTML=20
> > input tag wrappers: Do we already have something here, for=20
> either JSP=20
> > 2.0, Velocity or FreeMarker?
>=20
> not from my side - personal events have overtaken me a little=20
> recently. I'd intended contacting Seth again to catch up on=20
> this and ensure a consistent approach for the three=20
> technologies.  My feeling is that it should be fairly quick=20
> to add given the basic framework code is OK for resource=20
> loading, but I've not really looked closely at it yet.
>=20
> Regards,
> --
> Darren Davison
> Public Key: http://www.davison.uk.net/pages/key.htm
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.=20
http://ads.osdn.com/?ad_idG21&alloc_id=10040&op=3Dick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer




-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idG21&alloc_id=10040&op=3Dick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer




-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idG21&alloc_id=10040&op=CCk
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

[Springframework-developer] spring build.61 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:#FF0000; }.checkstyle-oddrow { bac=
kground-color:#CCCCCC }.checkstyle-data { font-family:arial,helvetica,sans-=
serif; font-size:8pt; color:#000000; }.checkstyle-sectionheader { backgroun=
d-color:#000066; font-family:arial,helvetica,sans-serif; font-size:10pt; co=
lor:#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.61</td></tr><tr><td class=3D"header-data"><span class=
=3D"header-label">Date of build:&nbsp;</span>07/24/2004 00:15:53</td></tr><=
tr><td class=3D"header-data"><span class=3D"header-label">Time to build:&nb=
sp;</span>13 minutes 21 seconds</td></tr><tr><td class=3D"header-data"><spa=
n class=3D"header-label">Last changed:&nbsp;</span>07/23/2004 16:29:07</td>=
</tr><tr><td class=3D"header-data"><span class=3D"header-label">Last log en=
try:&nbsp;</span>reorganized JMS support packages, moved unfinished stuff b=
ack to sandbox</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"/><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: (=
6)                    </td></tr><tr><td><pre class=3D"compile-error-data">N=
ote: Some input files use or override a deprecated API.<br class=3D"none"/>=
Note: Recompile with -deprecation for details.Note: /jteam/build/checkout/s=
pring/spring/mock/org/springframework/mock/web/MockHttpSession.java uses or=
 overrides a deprecated API.<br class=3D"none"/>Note: Recompile with -depre=
cation for details.<br class=3D"none"/>Note: Some input files use or overri=
de a deprecated API.<br class=3D"none"/>Note: Recompile with -deprecation f=
or 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: (1470)                </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">testHomePage</td><td width=
=3D"40%" class=3D"unittests-data">org.springframework.apptests.buildtest.Al=
lTests</td></tr></table></td></tr><tr></tr><tr><td colspan=3D"2">&nbsp;</td=
></tr><tr><td colspan=3D"4" class=3D"unittests-sectionheader">             =
       &nbsp;Unit Test Error Details:&nbsp;(1)                </td></tr><tr=
><td class=3D"unittests-data" colspan=3D"2">                Test:&nbsp;test=
HomePage</td></tr><tr><td class=3D"unittests-data" colspan=3D"2">          =
      Class:&nbsp;org.springframework.apptests.buildtest.AllTests</td></tr>=
<tr><td class=3D"unittests-data" colspan=3D"2">                Type: junit.=
framework.AssertionFailedError</td></tr><tr><td class=3D"unittests-data" co=
lspan=3D"2">                Message: Exception while testing URL http://loc=
alhost:13084/buildtest:java.io.IOException</td></tr><tr><td class=3D"unitte=
sts-error" colspan=3D"2"><pre>junit.framework.AssertionFailedError: Excepti=
on while testing URL http://localhost:13084/buildtest:java.io.IOException<b=
r>=09at org.springframework.apptests.buildtest.AllTests.testHomePage(Unknow=
n Source)<br>=09at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Meth=
od)<br>=09at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess=
orImpl.java:39)<br>=09at sun.reflect.DelegatingMethodAccessorImpl.invoke(De=
legatingMethodAccessorImpl.java:25)<br></pre></td></tr><tr><td colspan=3D"2=
">&nbsp;</td></tr></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"modifications-sectionheader">   =
                 &nbsp;Modifications since last build:&nbsp;               =
     (61)                </td></tr><tr class=3D"modifications-evenrow"><td =
class=3D"modifications-data">added</td><td class=3D"modifications-data">jho=
eller</td><td class=3D"modifications-data">sandbox/src/org/springframework/=
jms/DefaultJmsAdmin.java</td><td class=3D"modifications-data">reorganized J=
MS support packages, moved unfinished stuff back to sandbox</td></tr><tr cl=
ass=3D"modifications-oddrow"><td class=3D"modifications-data">added</td><td=
 class=3D"modifications-data">jhoeller</td><td class=3D"modifications-data"=
>sandbox/src/org/springframework/jms/DestinationInfo.java</td><td class=3D"=
modifications-data">reorganized JMS support packages, moved unfinished stuf=
f back to sandbox</td></tr><tr class=3D"modifications-evenrow"><td class=3D=
"modifications-data">added</td><td class=3D"modifications-data">jhoeller</t=
d><td class=3D"modifications-data">sandbox/src/org/springframework/jms/JmsA=
dmin.java</td><td class=3D"modifications-data">reorganized JMS support pack=
ages, moved unfinished stuff back to sandbox</td></tr><tr class=3D"modifica=
tions-oddrow"><td class=3D"modifications-data">modified</td><td class=3D"mo=
difications-data">jhoeller</td><td class=3D"modifications-data">sandbox/src=
/org/springframework/jms/JmsConnectionFactoryBean.java</td><td class=3D"mod=
ifications-data">reorganized JMS support packages, moved unfinished stuff b=
ack to sandbox</td></tr><tr class=3D"modifications-evenrow"><td class=3D"mo=
difications-data">added</td><td class=3D"modifications-data">jhoeller</td><=
td class=3D"modifications-data">sandbox/src/org/springframework/jms/JmsCons=
umerFactoryBean.java</td><td class=3D"modifications-data">reorganized JMS s=
upport packages, moved unfinished stuff back to sandbox</td></tr><tr class=
=3D"modifications-oddrow"><td class=3D"modifications-data">modified</td><td=
 class=3D"modifications-data">jhoeller</td><td class=3D"modifications-data"=
>sandbox/src/org/springframework/jms/JmsProducerFactoryBean.java</td><td cl=
ass=3D"modifications-data">reorganized JMS support packages, moved unfinish=
ed stuff back to sandbox</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">sandbox/src/org/springframewor=
k/jms/JmsSessionFactoryBean.java</td><td class=3D"modifications-data">reorg=
anized JMS support packages, moved unfinished stuff back to sandbox</td></t=
r><tr class=3D"modifications-oddrow"><td class=3D"modifications-data">added=
</td><td class=3D"modifications-data">jhoeller</td><td class=3D"modificatio=
ns-data">sandbox/src/org/springframework/jms/MapMessageConverter.java</td><=
td class=3D"modifications-data">reorganized JMS support packages, moved unf=
inished stuff back to sandbox</td></tr><tr class=3D"modifications-evenrow">=
<td class=3D"modifications-data">added</td><td class=3D"modifications-data"=
>jhoeller</td><td class=3D"modifications-data">sandbox/src/org/springframew=
ork/jms/QueueInfo.java</td><td class=3D"modifications-data">reorganized JMS=
 support packages, moved unfinished stuff back to sandbox</td></tr><tr clas=
s=3D"modifications-oddrow"><td class=3D"modifications-data">added</td><td c=
lass=3D"modifications-data">jhoeller</td><td class=3D"modifications-data">s=
andbox/src/org/springframework/jms/TopicInfo.java</td><td class=3D"modifica=
tions-data">reorganized JMS support packages, moved unfinished stuff back t=
o sandbox</td></tr><tr class=3D"modifications-evenrow"><td class=3D"modific=
ations-data">added</td><td class=3D"modifications-data">jhoeller</td><td cl=
ass=3D"modifications-data">sandbox/test/org/springframework/jms/MapMessageC=
onverterTests.java</td><td class=3D"modifications-data">reorganized JMS sup=
port packages, moved unfinished stuff back to sandbox</td></tr><tr class=3D=
"modifications-oddrow"><td class=3D"modifications-data">added</td><td class=
=3D"modifications-data">jhoeller</td><td class=3D"modifications-data">sandb=
ox/test/org/springframework/jms/SimpleTestBean.java</td><td class=3D"modifi=
cations-data">reorganized JMS support packages, moved unfinished stuff back=
 to sandbox</td></tr><tr class=3D"modifications-evenrow"><td class=3D"modif=
ications-data">modified</td><td class=3D"modifications-data">jhoeller</td><=
td class=3D"modifications-data">src/org/springframework/web/servlet/ModelAn=
dView.java</td><td class=3D"modifications-data">use optimal HashMap capacit=
y</td></tr><tr class=3D"modifications-oddrow"><td class=3D"modifications-da=
ta">modified</td><td class=3D"modifications-data">jhoeller</td><td class=3D=
"modifications-data">src/org/springframework/beans/factory/support/DefaultL=
istableBeanFactory.java</td><td class=3D"modifications-data">polishing</td>=
</tr><tr class=3D"modifications-evenrow"><td class=3D"modifications-data">m=
odified</td><td class=3D"modifications-data">jhoeller</td><td class=3D"modi=
fications-data">src/org/springframework/beans/support/MutableSortDefinition=
.java</td><td class=3D"modifications-data">polishing</td></tr><tr class=3D"=
modifications-oddrow"><td class=3D"modifications-data">modified</td><td cla=
ss=3D"modifications-data">jhoeller</td><td class=3D"modifications-data">src=
/org/springframework/core/io/support/ResourcePatternResolver.java</td><td c=
lass=3D"modifications-data">polishing</td></tr><tr class=3D"modifications-e=
venrow"><td class=3D"modifications-data">modified</td><td class=3D"modifica=
tions-data">jhoeller</td><td class=3D"modifications-data">src/org/springfra=
mework/jdbc/support/JdbcAccessor.java</td><td class=3D"modifications-data">=
turned abstract</td></tr><tr class=3D"modifications-oddrow"><td class=3D"mo=
difications-data">modified</td><td class=3D"modifications-data">jhoeller</t=
d><td class=3D"modifications-data">src/org/springframework/orm/jdo/JdoAcces=
sor.java</td><td class=3D"modifications-data">turned abstract</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">/build.xml</td><td class=3D"modifications-data">applied -source 1.3 =
wherever necessary to allow building with JDK 1.5</td></tr><tr class=3D"mod=
ifications-oddrow"><td class=3D"modifications-data">modified</td><td class=
=3D"modifications-data">jhoeller</td><td class=3D"modifications-data">src/o=
rg/springframework/jndi/AbstractJndiLocator.java</td><td class=3D"modificat=
ions-data">factored out JndiLocatorSupport from AbstractJndiLocator</td></t=
r><tr class=3D"modifications-evenrow"><td class=3D"modifications-data">adde=
d</td><td class=3D"modifications-data">jhoeller</td><td class=3D"modificati=
ons-data">src/org/springframework/jndi/JndiLocatorSupport.java</td><td clas=
s=3D"modifications-data">factored out JndiLocatorSupport from AbstractJndiL=
ocator</td></tr><tr class=3D"modifications-oddrow"><td class=3D"modificatio=
ns-data">deleted</td><td class=3D"modifications-data">jhoeller</td><td clas=
s=3D"modifications-data">test/org/springframework/jdbc/datasource/DataSourc=
eUtilsTests.java</td><td class=3D"modifications-data">removed close-suppres=
sing connection proxy tests</td></tr><tr class=3D"modifications-evenrow"><t=
d class=3D"modifications-data">modified</td><td class=3D"modifications-data=
">jhoeller</td><td class=3D"modifications-data">/build.xml</td><td class=3D=
"modifications-data">copy spring.vm and spring.ftl to dist directory</td></=
tr><tr class=3D"modifications-oddrow"><td class=3D"modifications-data">modi=
fied</td><td class=3D"modifications-data">jhoeller</td><td class=3D"modific=
ations-data">src/org/springframework/web/servlet/view/document/AbstractPdfV=
iew.java</td><td class=3D"modifications-data">polishing</td></tr><tr class=
=3D"modifications-evenrow"><td class=3D"modifications-data">modified</td><t=
d class=3D"modifications-data">jhoeller</td><td class=3D"modifications-data=
">src/org/springframework/ui/velocity/SpringResourceLoader.java</td><td cla=
ss=3D"modifications-data">polishing</td></tr><tr class=3D"modifications-odd=
row"><td class=3D"modifications-data">modified</td><td class=3D"modificatio=
ns-data">jhoeller</td><td class=3D"modifications-data">src/org/springframew=
ork/web/servlet/view/UrlBasedViewResolver.java</td><td class=3D"modificatio=
ns-data">polishing</td></tr><tr class=3D"modifications-evenrow"><td class=
=3D"modifications-data">modified</td><td class=3D"modifications-data">jhoel=
ler</td><td class=3D"modifications-data">src/org/springframework/ui/freemar=
ker/FreeMarkerConfigurationFactory.java</td><td class=3D"modifications-data=
">polishing</td></tr><tr class=3D"modifications-oddrow"><td class=3D"modifi=
cations-data">modified</td><td class=3D"modifications-data">jhoeller</td><t=
d class=3D"modifications-data">src/org/springframework/ui/freemarker/Spring=
TemplateLoader.java</td><td class=3D"modifications-data">polishing</td></tr=
><tr class=3D"modifications-evenrow"><td class=3D"modifications-data">modif=
ied</td><td class=3D"modifications-data">jhoeller</td><td class=3D"modifica=
tions-data">src/org/springframework/aop/framework/AdvisedSupport.java</td><=
td class=3D"modifications-data">polishing</td></tr><tr class=3D"modificatio=
ns-oddrow"><td class=3D"modifications-data">modified</td><td class=3D"modif=
ications-data">jhoeller</td><td class=3D"modifications-data">src/org/spring=
framework/aop/framework/ProxyFactory.java</td><td class=3D"modifications-da=
ta">polishing</td></tr><tr class=3D"modifications-evenrow"><td class=3D"mod=
ifications-data">modified</td><td class=3D"modifications-data">johnsonr</td=
><td class=3D"modifications-data">src/org/springframework/aop/framework/Adv=
ised.java</td><td class=3D"modifications-data">Added setTargetSource() meth=
od to Advised interface</td></tr><tr class=3D"modifications-oddrow"><td cla=
ss=3D"modifications-data">modified</td><td class=3D"modifications-data">joh=
nsonr</td><td class=3D"modifications-data">test/org/springframework/aop/fra=
mework/AbstractAopProxyTests.java</td><td class=3D"modifications-data">Adde=
d setTargetSource() method to Advised interface</td></tr><tr class=3D"modif=
ications-evenrow"><td class=3D"modifications-data">modified</td><td class=
=3D"modifications-data">jhoeller</td><td class=3D"modifications-data">src/o=
rg/springframework/web/servlet/view/document/AbstractExcelView.java</td><td=
 class=3D"modifications-data">adapted localization to conform to ResourceBu=
ndle conventions, load via ApplicationContext rather than ServletContext</t=
d></tr><tr class=3D"modifications-oddrow"><td class=3D"modifications-data">=
modified</td><td class=3D"modifications-data">jhoeller</td><td class=3D"mod=
ifications-data">src/org/springframework/web/servlet/view/freemarker/FreeMa=
rkerConfigurer.java</td><td class=3D"modifications-data">removed Velocity/F=
reeMarkerFormView in favor of "exposeSpringBindHelpers" property in Abstrac=
tTemplateView, reworked Velocity/FreeMarker initializitation of Spring macr=
os</td></tr><tr class=3D"modifications-evenrow"><td class=3D"modifications-=
data">deleted</td><td class=3D"modifications-data">jhoeller</td><td class=
=3D"modifications-data">src/org/springframework/web/servlet/view/freemarker=
/FreeMarkerFormView.java</td><td class=3D"modifications-data">removed Veloc=
ity/FreeMarkerFormView in favor of "exposeSpringBindHelpers" property in Ab=
stractTemplateView, reworked Velocity/FreeMarker initializitation of Spring=
 macros</td></tr><tr class=3D"modifications-oddrow"><td class=3D"modificati=
ons-data">modified</td><td class=3D"modifications-data">jhoeller</td><td cl=
ass=3D"modifications-data">src/org/springframework/web/servlet/view/freemar=
ker/FreeMarkerView.java</td><td class=3D"modifications-data">removed Veloci=
ty/FreeMarkerFormView in favor of "exposeSpringBindHelpers" property in Abs=
tractTemplateView, reworked Velocity/FreeMarker initializitation of Spring =
macros</td></tr><tr class=3D"modifications-evenrow"><td class=3D"modificati=
ons-data">added</td><td class=3D"modifications-data">jhoeller</td><td class=
=3D"modifications-data">src/org/springframework/web/servlet/view/freemarker=
/FreeMarkerViewResolver.java</td><td class=3D"modifications-data">removed V=
elocity/FreeMarkerFormView in favor of "exposeSpringBindHelpers" property i=
n AbstractTemplateView, reworked Velocity/FreeMarker initializitation of Sp=
ring macros</td></tr><tr class=3D"modifications-oddrow"><td class=3D"modifi=
cations-data">modified</td><td class=3D"modifications-data">jhoeller</td><t=
d class=3D"modifications-data">src/org/springframework/web/servlet/view/fre=
emarker/spring.ftl</td><td class=3D"modifications-data">removed Velocity/Fr=
eeMarkerFormView in favor of "exposeSpringBindHelpers" property in Abstract=
TemplateView, reworked Velocity/FreeMarker initializitation of Spring macro=
s</td></tr><tr class=3D"modifications-evenrow"><td class=3D"modifications-d=
ata">deleted</td><td class=3D"modifications-data">jhoeller</td><td class=3D=
"modifications-data">test/org/springframework/web/servlet/view/velocity/Vel=
ocityFormViewTests.java</td><td class=3D"modifications-data">removed Veloci=
ty/FreeMarkerFormView in favor of "exposeSpringBindHelpers" property in Abs=
tractTemplateView, reworked Velocity/FreeMarker initializitation of Spring =
macros</td></tr><tr class=3D"modifications-oddrow"><td class=3D"modificatio=
ns-data">added</td><td class=3D"modifications-data">jhoeller</td><td class=
=3D"modifications-data">test/org/springframework/web/servlet/view/velocity/=
VelocityMacroTests.java</td><td class=3D"modifications-data">removed Veloci=
ty/FreeMarkerFormView in favor of "exposeSpringBindHelpers" property in Abs=
tractTemplateView, reworked Velocity/FreeMarker initializitation of Spring =
macros</td></tr><tr class=3D"modifications-evenrow"><td class=3D"modificati=
ons-data">modified</td><td class=3D"modifications-data">jhoeller</td><td cl=
ass=3D"modifications-data">src/org/springframework/web/servlet/view/velocit=
y/VelocityConfigurer.java</td><td class=3D"modifications-data">removed Velo=
city/FreeMarkerFormView in favor of "exposeSpringBindHelpers" property in A=
bstractTemplateView, reworked Velocity/FreeMarker initializitation of Sprin=
g macros</td></tr><tr class=3D"modifications-oddrow"><td class=3D"modificat=
ions-data">deleted</td><td class=3D"modifications-data">jhoeller</td><td cl=
ass=3D"modifications-data">src/org/springframework/web/servlet/view/velocit=
y/VelocityFormView.java</td><td class=3D"modifications-data">removed Veloci=
ty/FreeMarkerFormView in favor of "exposeSpringBindHelpers" property in Abs=
tractTemplateView, reworked Velocity/FreeMarker initializitation of Spring =
macros</td></tr><tr class=3D"modifications-evenrow"><td class=3D"modificati=
ons-data">modified</td><td class=3D"modifications-data">jhoeller</td><td cl=
ass=3D"modifications-data">src/org/springframework/web/servlet/view/velocit=
y/VelocityView.java</td><td class=3D"modifications-data">removed Velocity/F=
reeMarkerFormView in favor of "exposeSpringBindHelpers" property in Abstrac=
tTemplateView, reworked Velocity/FreeMarker initializitation of Spring macr=
os</td></tr><tr class=3D"modifications-oddrow"><td class=3D"modifications-d=
ata">modified</td><td class=3D"modifications-data">jhoeller</td><td class=
=3D"modifications-data">src/org/springframework/web/servlet/view/velocity/V=
elocityViewResolver.java</td><td class=3D"modifications-data">removed Veloc=
ity/FreeMarkerFormView in favor of "exposeSpringBindHelpers" property in Ab=
stractTemplateView, reworked Velocity/FreeMarker initializitation of Spring=
 macros</td></tr><tr class=3D"modifications-evenrow"><td class=3D"modificat=
ions-data">modified</td><td class=3D"modifications-data">jhoeller</td><td c=
lass=3D"modifications-data">src/org/springframework/web/servlet/view/veloci=
ty/spring.vm</td><td class=3D"modifications-data">removed Velocity/FreeMark=
erFormView in favor of "exposeSpringBindHelpers" property in AbstractTempla=
teView, reworked Velocity/FreeMarker initializitation of Spring macros</td>=
</tr><tr class=3D"modifications-oddrow"><td class=3D"modifications-data">mo=
dified</td><td class=3D"modifications-data">jhoeller</td><td class=3D"modif=
ications-data">src/org/springframework/web/servlet/view/AbstractTemplateVie=
w.java</td><td class=3D"modifications-data">removed Velocity/FreeMarkerForm=
View in favor of "exposeSpringBindHelpers" property in AbstractTemplateView=
, reworked Velocity/FreeMarker initializitation of Spring macros</td></tr><=
tr class=3D"modifications-evenrow"><td class=3D"modifications-data">added</=
td><td class=3D"modifications-data">jhoeller</td><td class=3D"modifications=
-data">src/org/springframework/web/servlet/view/AbstractTemplateViewResolve=
r.java</td><td class=3D"modifications-data">removed Velocity/FreeMarkerForm=
View in favor of "exposeSpringBindHelpers" property in AbstractTemplateView=
, reworked Velocity/FreeMarker initializitation of Spring macros</td></tr><=
tr class=3D"modifications-oddrow"><td class=3D"modifications-data">modified=
</td><td class=3D"modifications-data">jhoeller</td><td class=3D"modificatio=
ns-data">docs/taglib/tag/BindTag.html</td><td class=3D"modifications-data">=
made BindStatus class more generic, moving it to support package, keeping a=
 deprecated subclass in tags package</td></tr><tr class=3D"modifications-ev=
enrow"><td class=3D"modifications-data">added</td><td class=3D"modification=
s-data">jhoeller</td><td class=3D"modifications-data">src/org/springframewo=
rk/web/servlet/support/BindStatus.java</td><td class=3D"modifications-data"=
>made BindStatus class more generic, moving it to support package, keeping =
a deprecated subclass in tags package</td></tr><tr class=3D"modifications-o=
ddrow"><td class=3D"modifications-data">modified</td><td class=3D"modificat=
ions-data">jhoeller</td><td class=3D"modifications-data">src/org/springfram=
ework/web/servlet/support/RequestContext.java</td><td class=3D"modification=
s-data">made BindStatus class more generic, moving it to support package, k=
eeping a deprecated subclass in tags package</td></tr><tr class=3D"modifica=
tions-evenrow"><td class=3D"modifications-data">modified</td><td class=3D"m=
odifications-data">jhoeller</td><td class=3D"modifications-data">src/org/sp=
ringframework/web/servlet/tags/BindStatus.java</td><td class=3D"modificatio=
ns-data">made BindStatus class more generic, moving it to support package, =
keeping a deprecated subclass in tags package</td></tr><tr class=3D"modific=
ations-oddrow"><td class=3D"modifications-data">deleted</td><td class=3D"mo=
difications-data">jhoeller</td><td class=3D"modifications-data">src/org/spr=
ingframework/web/servlet/tags/BindStatusHelper.java</td><td class=3D"modifi=
cations-data">made BindStatus class more generic, moving it to support pack=
age, keeping a deprecated subclass in tags package</td></tr><tr class=3D"mo=
difications-evenrow"><td class=3D"modifications-data">modified</td><td clas=
s=3D"modifications-data">jhoeller</td><td class=3D"modifications-data">src/=
org/springframework/web/servlet/tags/BindTag.java</td><td class=3D"modifica=
tions-data">made BindStatus class more generic, moving it to support packag=
e, keeping a deprecated subclass in tags package</td></tr><tr class=3D"modi=
fications-oddrow"><td class=3D"modifications-data">modified</td><td class=
=3D"modifications-data">jhoeller</td><td class=3D"modifications-data">src/o=
rg/springframework/web/servlet/tags/spring.tld</td><td class=3D"modificatio=
ns-data">made BindStatus class more generic, moving it to support package, =
keeping a deprecated subclass in tags package</td></tr><tr class=3D"modific=
ations-evenrow"><td class=3D"modifications-data">modified</td><td class=3D"=
modifications-data">jhoeller</td><td class=3D"modifications-data">test/org/=
springframework/web/servlet/tags/BindTestSuite.java</td><td class=3D"modifi=
cations-data">made BindStatus class more generic, moving it to support pack=
age, keeping a deprecated subclass in tags package</td></tr><tr class=3D"mo=
difications-oddrow"><td class=3D"modifications-data">modified</td><td class=
=3D"modifications-data">jhoeller</td><td class=3D"modifications-data">src/o=
rg/springframework/web/context/support/StaticWebApplicationContext.java</td=
><td class=3D"modifications-data">use ServletContextResource even for mock =
ServletContext</td></tr><tr class=3D"modifications-evenrow"><td class=3D"mo=
difications-data">modified</td><td class=3D"modifications-data">jhoeller</t=
d><td class=3D"modifications-data">test/org/springframework/web/servlet/vie=
w/ResourceBundleViewResolverTestSuite.java</td><td class=3D"modifications-d=
ata">use ServletContextResource even for mock ServletContext</td></tr><tr c=
lass=3D"modifications-oddrow"><td class=3D"modifications-data">modified</td=
><td class=3D"modifications-data">jhoeller</td><td class=3D"modifications-d=
ata">test/org/springframework/web/servlet/view/ViewResolverTestSuite.java</=
td><td class=3D"modifications-data">use ServletContextResource even for moc=
k ServletContext</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">mock/org/springframework/mock/web/Mock=
ServletContext.java</td><td class=3D"modifications-data">use ServletContext=
Resource even for mock ServletContext</td></tr><tr class=3D"modifications-o=
ddrow"><td class=3D"modifications-data">modified</td><td class=3D"modificat=
ions-data">trisberg</td><td class=3D"modifications-data">test/org/springfra=
mework/jdbc/support/SQLErrorCodesFactoryTests.java</td><td class=3D"modific=
ations-data">added additional wildcard tests</td></tr><tr class=3D"modifica=
tions-evenrow"><td class=3D"modifications-data">modified</td><td class=3D"m=
odifications-data">trisberg</td><td class=3D"modifications-data">test/org/s=
pringframework/jdbc/support/wildcard-error-codes.xml</td><td class=3D"modif=
ications-data">added additional wildcard tests</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;(8)                    </td><=
/tr><tr><td class=3D"distributables-data">Building jar: /jteam/build/checko=
ut/spring/spring/dist/spring.jar</td></tr><tr class=3D"distributables-oddro=
w"><td class=3D"distributables-data">Building war: /jteam/build/checkout/sp=
ring/spring/autobuilds/apps/buildtest/dist/buildtest.war</td></tr><tr><td c=
lass=3D"distributables-data">Building war: /jteam/build/checkout/spring/spr=
ing/autobuilds/apps/buildtest/dist/buildtest.war</td></tr><tr class=3D"dist=
ributables-oddrow"><td class=3D"distributables-data">Building war: /jteam/b=
uild/checkout/spring/spring/autobuilds/apps/buildtest/dist/buildtest.war</t=
d></tr><tr><td class=3D"distributables-data">Building jar: /jteam/build/che=
ckout/spring/spring/autobuilds/apps/jpetstore/war/WEB-INF/lib/jpetstore.jar=
</td></tr><tr class=3D"distributables-oddrow"><td class=3D"distributables-d=
ata">Building war: /jteam/build/checkout/spring/spring/autobuilds/apps/jpet=
store/dist/jpetstore.war</td></tr><tr><td class=3D"distributables-data">Bui=
lding jar: /jteam/build/checkout/spring/spring/autobuilds/apps/jpetstore/wa=
r/WEB-INF/lib/jpetstore.jar</td></tr><tr class=3D"distributables-oddrow"><t=
d class=3D"distributables-data">Building war: /jteam/build/checkout/spring/=
spring/autobuilds/apps/jpetstore/dist/jpetstore.war</td></tr></table>
</body></html>

Re: [Springframework-developer] Tests (groovy!)

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

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 23 July 2004 16:59, Rod Johnson wrote:
> Darren
>
> I'd definitely like to continue to explore the use of Groovy. Juergen has
> a good point re the imminent 1.1 releases, but beyond that I think this
> is definitely important and likely to be beneficial. I would be surpised
> if we don't find other uses of Groovy in 1.2...

I agree.  I'm still pretty confident it would be a useful option as a bean=
=20
definition syntax.  There's also the possibilty of using it where=20
expression languages might otherwise be used and it has some interesting=20
SQL and Markup constructs that could find a home in various project and=20
application tasks.

D.

=2D --=20
Darren Davison
Public Key: http://www.davison.uk.net/pages/key.htm
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBAWjOKLMLAN01aw0RAsC5AJ9w4cO5PVn5GxcPU45VgIDOpgWmAACfZMm3
J/jb3I1fDjhFvAMebcUf2vU=3D
=3DDyJ7
=2D----END PGP SIGNATURE-----

Re: [Springframework-developer] Tests (groovy!)

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

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 23 July 2004 18:38, Alef Arendsen wrote:
> I agree with not having Groovy dependent tests in the distribution before
> 1.1 final. However I don't think it's much of a problem to keep the
> Groovy tests in the test directory since they can be excluded using the
> .groovy file extension, can't they?

correct.  In fact they don't even need to be explicitly excluded since java=
c=20
and junit will simply ignore them unless someone previously opted to=20
compile them with groovyc.

> So keep the groovy-build.xml around for the time being and move it over
> to the build.xml file after 1.1?

as I mentioned before, I'm happy to go along with wherever the interest=20
is :)

=2D --=20
Darren Davison
Public Key: http://www.davison.uk.net/pages/key.htm
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBAWf+KLMLAN01aw0RAp6LAJ95eQYGTapY7i4f2ARTd2hlJqDUYACgi1bK
EPRprZE2il/9uuo2zw5k4fM=3D
=3DeGlX
=2D----END PGP SIGNATURE-----

[Springframework-developer] Serialization of AOP proxies

[Rod J. <rod...@in...>]

AOP users,

I've just committed a feature that has been requested several times:
serializability of AOP proxies.

AOP proxies are now serializable if they're:

- JDK dynamic proxies
- all Advisors (meaning Pointcut + Advice) are serializable
- TargetSource is serializable (normally only the target matters)

I've made some framework classes Serializable such as Pointcut.TRUE and
DefaultPointcutAdvisor, but the onus is on the developer to mark as
serializable an Advice/Pointcut that may be serialized.

This will be released in 1.1 RC1.

We will also consider serializability for CGLIB proxies.

Rgds
Rod

[Springframework-developer] RE: Spring 1.1 Release Plan

[prakasam k. <k_p...@ya...>]

Hi

I am wondering if there is any release plan for
version 1.1 and I'd like to know the tentative (FCS)
final release date.

Prakash


	
		
__________________________________
Do you Yahoo!?
Vote for the stars of Yahoo!'s next ad campaign!
http://advision.webevents.yahoo.com/yahoo/votelifeengine/

Re: [Springframework-developer] Re: Is it possible to publish nightly builds?

[Dmitriy K. <dko...@ru...>]

Actually it should be all about the options we give to our users: it 
wouldn't bother some folks to manually build CVS snapshots while some 
would definitely prefer just to "grab" the latest jars from nightly 
build. I would vote for publishing the nightly builds.

Regards,
Dmitriy.


Vinay Aggarwal wrote:

>
> Thanks Jérôme for the patch.
>
> I think I have proved my point, build did not 'just work' after 
> everybody swore it would. There were problems in build, problems in my 
> environment not to mention I needed to install CVS client and proper 
> JDK version. This patch is not the last problem, I can already foresee 
> a couple of more issues. On the other hand, I have yet to hear a 
> reason why not just publish nightly build. Expecting me, as a user, to 
> go through all this pain without proper reasoning does not make me a 
> (happy) user.
>
> I also understand, I am outvoted here. I will pass for now.
>
> Regards
> Vinay
>
>
> Jérôme BERNARD wrote:
>
>> I wrote a patch a few days ago in order to solve this problem.
>> See http://opensource.atlassian.com/projects/spring/browse/SPR-228
>>
>> Regards,
>> Jérôme.
>>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer

[Springframework-developer] Re: Is it possible to publish nightly builds?

[Vinay A. <vin...@ya...>]

Thanks Jérôme for the patch.

I think I have proved my point, build did not 'just work' after 
everybody swore it would. There were problems in build, problems in my 
environment not to mention I needed to install CVS client and proper JDK 
version. This patch is not the last problem, I can already foresee a 
couple of more issues. On the other hand, I have yet to hear a reason 
why not just publish nightly build. Expecting me, as a user, to go 
through all this pain without proper reasoning does not make me a 
(happy) user.

I also understand, I am outvoted here. I will pass for now.

Regards
Vinay


Jérôme BERNARD wrote:
> I wrote a patch a few days ago in order to solve this problem.
> See http://opensource.atlassian.com/projects/spring/browse/SPR-228
> 
> Regards,
> Jérôme.
> 

Re: [Springframework-developer] Re: Is it possible to publish nightly builds?

[<jer...@xt...>]

BTW, why not publishing CruiseControl artifacts somewhere on the web, so=20
that users could have the JARs of the lastest successful build ?

J=E9r=F4me.

j=FCrgen h=F6ller [werk3AT] wrote:

>Just applied the patch. Should be visible in public CVS in a couple of h=
ours.
>
>I generally recommend to build with Sun JDK 1.4.2, though.
>
>Juergen
>
>
>-----Original Message-----
>From: spr...@li...
>[mailto:spr...@li...]On Behalf
>Of J=E9r=F4me BERNARD
>Sent: Friday, July 23, 2004 12:32 PM
>To: spr...@li...; Vinay Aggarwal
>Cc: spr...@li...
>Subject: Re: [Springframework-developer] Re: Is it possible to publish
>nightly builds?
>
>
>I wrote a patch a few days ago in order to solve this problem.
>See http://opensource.atlassian.com/projects/spring/browse/SPR-228
>
>Regards,
>J=E9r=F4me.
>
>
>Selon Vinay Aggarwal <vin...@ya...>:
>
> =20
>
>>You guys convinced me to give it one more try. I downloaded the whole
>>project and tried to compile it. The build did infact fail. Anyway,
>>thanks for your help and encouragement, but I am not going to spend any
>>more time on it.
>>
>>Regards
>>Vinay
>>
>>P.S.: In case you are interested, the error is enclosed.
>>
>>C:\software\workspace\spring>\software\apache-ant-1.6.1\bin\ant alljars
>>Buildfile: build.xml
>>
>>compileattr:
>>[attribute-compiler] Generated attribute information for 1 classes.
>>Ignored 0 classes.
>>
>>build:
>>     [mkdir] Created dir:
>>C:\software\workspace\spring\target\classes\META-INF
>>     [javac] Compiling 1 source file to
>>C:\software\workspace\spring\target\classes
>>     [javac] javac: source release 1.4 requires target release 1.4
>>
>>BUILD FAILED
>>C:\software\workspace\spring\build.xml:119: Compile failed; see the
>>compiler error output for details.
>>
>>Total time: 10 seconds
>>C:\software\workspace\spring>
>>
>>
>>
>>
>>
>>Rob Harrop wrote:
>>
>>   =20
>>
>>>Vinay,
>>>
>>>I have to 'third' what is being said here. You are most unlikely to ha=
ve
>>>     =20
>>>
>>any
>>   =20
>>
>>>issues with classpath/3rd party libs since Ant takes care of the class=
path
>>>and a check out from Spring CVS will include everything you need.
>>>
>>>If you are still having trouble getting a build post your error here a=
nd I
>>>will decode it for you and find out what is wrong.
>>>
>>>Rob
>>>
>>>-----Original Message-----
>>>From: spr...@li...
>>>[mailto:spr...@li...] On Beha=
lf Of
>>>j=FCrgen h=F6ller [werk3AT]
>>>Sent: 23 July 2004 09:09
>>>To: spr...@li...
>>>Subject: Re: [Springframework-developer] Re: Is it possible to publish
>>>nightly builds?
>>>
>>>Vinay,
>>>
>>>While I certainly understand the desire for nightly builds (we actuall=
y do
>>>them, we just don't publish them yet), I'd still like to second Matt t=
hat
>>>Spring is surprisingly easy to build from CVS.
>>>
>>>You'll get all third-party libraries from our CVS, and a prepared buil=
d
>>>script that auto-detects all those. So basically, all you need to do i=
s
>>>install JDK 1.4.2 and invoke our build.xml in the root of the "spring"
>>>module. We even ship a matching Ant version. And for Windows, there's =
a
>>>build.bat that just requires JAVA_HOME to be set and uses the included=
 Ant
>>>to perform the build.
>>>
>>>Essentially, it's the same as when you download one of our
>>>"-with-dependencies" distributions. Those zips include everything you =
need
>>>to build Spring yourself, just like above. If you fetch a CVS snapshot=
,
>>>     =20
>>>
>>it's
>>   =20
>>
>>>the same build file and same directory structure, just with newer cont=
ents.
>>>
>>>Juergen
>>>
>>>     =20
>>>
>>
>>-------------------------------------------------------
>>This SF.Net email is sponsored by BEA Weblogic Workshop
>>FREE Java Enterprise J2EE developer tools!
>>Get your free copy of BEA WebLogic Workshop 8.1 today.
>>http://ads.osdn.com/?ad_id=3D4721&alloc_id=3D10040&op=3Dclick
>>_______________________________________________
>>Springframework-developer mailing list
>>Spr...@li...
>>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>
>>   =20
>>
>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by BEA Weblogic Workshop
>FREE Java Enterprise J2EE developer tools!
>Get your free copy of BEA WebLogic Workshop 8.1 today.
>http://ads.osdn.com/?ad_idG21&alloc_id=10040&op=3Dick
>_______________________________________________
>Springframework-developer mailing list
>Spr...@li...
>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by BEA Weblogic Workshop
>FREE Java Enterprise J2EE developer tools!
>Get your free copy of BEA WebLogic Workshop 8.1 today.
>http://ads.osdn.com/?ad_idG21&alloc_id=10040&op=3Dclick
>_______________________________________________
>Springframework-developer mailing list
>Spr...@li...
>https://lists.sourceforge.net/lists/listinfo/springframework-developer
> =20
>

RE: [Springframework-developer] Tests (groovy!)

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

I agree with not having Groovy dependent tests in the distribution =
before 1.1 final. However I don't think it's much of a problem to keep =
the Groovy tests in the test directory since they can be excluded using =
the .groovy file extension, can't they?
=20
So keep the groovy-build.xml around for the time being and move it over =
to the build.xml file after 1.1?
=20
Alef
=20
=20

________________________________

Van: spr...@li... namens =
j=FCrgen h=F6ller [werk3AT]
Verzonden: vr 23-7-2004 16:01
Aan: spr...@li...
Onderwerp: Re: [Springframework-developer] Tests (groovy!)



Sounds plausible! Still, for the time being, I'd prefer if our release =
distributions don't have to include Groovy: i.e., our framework test =
suite does not depend on groovy.jar. If we want to use Groovy for core =
frameworks tests, let's do this after Spring 1.1 final (or at least, =
after 1.1 RC1).

Of course, groovy.jar can reside in our CVS lib directory; we just =
wouldn't include in the release zip. However, Groovy-dependent tests =
should preferably not reside in the "test" directory for the time being, =
but rather in some separate directory that doesn't get included in =
release zips.

My main concern is to get 1.1 RC1 and 1.1 final out the door as soon as =
possible, and to avoid anything that could potentially cause =
complications. As we ship our tests, dependencies, and build scripts, =
they should be considered in feature freeze mode too.

Other opinions on this?

Juergen


-----Original Message-----
From: spr...@li...
[mailto:spr...@li...]On Behalf
Of Darren Davison
Sent: Thursday, July 22, 2004 2:34 PM
To: spr...@li...
Subject: Re: [Springframework-developer] Tests (groovy!)



> Darren,
>
> Are you modifying Spring's standard build process here? Will this make
> Spring's standard build depend on Groovy? I feel that this is not too
> appropriate given that we are about to release 1.1 RC1 within the next
> couple of days.

No it won't affect the build or make it depend on groovy.  What I've =
done
for now is to take a copy of build.xml (called groovy-build.xml) and =
added
the groovyc taskdef and task to the buildtests target in there while
experimenting with it.  In fact those are the only 2 changes required to
the build to enable the whole process - it's pretty seamless.  Nor have =
I
modified any of the existing test classes, rather I've duplicated two =
test
classes, so in the tree for those 2 files only, a corresponding
*Tests.groovy file exists alongside the *Tests.java file.

If you build with build.xml, nothing unusual happens - any .groovy files
in the tree are simply ignored by javac and junit.  If you specify
-buildfile groovy-build.xml then the groovyc task will compile *.groovy
files to standard *.class files just as the javac task handles *.java
files.  The two languages can be mixed and matched seamlessly as the
bytecode is standard.

Once people have had a look at it, if it's something we want to use as =
an
option then we'd modify the main build.xml as described - but that can =
be
whenever.  Of course at that point, any new tests written in groovy
*would* have a dependency on groovy.jar but this is no more onerous than
depending on any other jar.  See below..

> I certainly don't object to doing tests with Groovy, but remember that =
we
> ship our build file and all libraries that we depend on in the
> "-with-dependencies" download, so that people can build Spring =
themselves
> respectively run the test suite themselves. For 1.1, they should be =
able
> to do this without Groovy, IMO.

that's no problem, they can do that.  The only dependencies when running
tests written with groovy are: groovy.jar, which will be in /lib/groovy
(it also contains the groovyc ant task) and asm.jar which we already
depend on anyway.  The junit side of things is completely unmodified =
since
any tests written in groovy extend GroovyTest which in turn extends
junit.framework.TestCase somewhere along the line.

There's no requirement to install any of the groovy binaries or other =
bits
and pieces you can download from them, even when writing and running
groovy based unit tests - it's all pure java and all invoked via ant.

If you're still not comfortable with it and want to hold off committing
for a while, that's no problem at all.  The _only_ impact it will have =
is
adding a couple of hundred KB to the size of the release zip in =
practice,
since it will just be "another jar file" and won't be implicated in
anything the users want to do with the tests.

> Sorry if I misunderstand something here...

not at all - just let me know if you'd still prefer me to hold off?

Best wishes,
--
Darren Davison
Public Key: http://www.davison.uk.net/pages/key.htm




-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idG21&alloc_id=10040&op=3Dick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idG21&alloc_id=10040&op=3Dick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

[Springframework-developer] FactoryBeans, BeanFactoryPostProcessors and finding beans by type

[David H. <dh...@ob...>]

Have=20just=20come=20across=20an=20interesting=20and=20quite=20subtle=20go=
tcha=20that=20is=20probably=20worth=20sharing.
=20
If=20a=20BeanPostProcessor=20attempts=20to=20locate=20collaborators=20by=20=
type=20in=20the=20ListableBeanFactory=20,=20and=20follows=20the=20standard=
=20method=20of=20preventing=20circular=20references=20using=20ControlFlow,=
=20then=20it=20will=20fail=20to=20process=20dependencies=20of=20non-lazy=20=
FactoryBeans.
=20
I'll=20elaborate=20on=20that=20mouthful=20of=20a=20sentence=20with=20an=20=
example.=20We=20use=20a=20BeanPostProcessor=20to=20auto-register=20JMX=20m=
anageable=20beans,=20which=20does=20the=20following=20in=20postProcessAfte=
rInitialization:
*=09Checks=20that=20we=20are=20not=20in=20a=20circular=20dependency=20usin=
g=20the=20ControlFlow=20method,=20as=20in=20AbstractAdvisorAutoProxyCreato=
r.shouldSkip
*=09If=20this=20test=20succeeds,=20it=20locates=20a=20number=20of=20collab=
orating=20handlers=20by=20type=20that=20define=20different=20strategies=20=
for=20registering=20MBeans=20(ie=20registering=20standard=20MBeans,=20or=20=
POJOs=20with=20attributes).=20=20
*=09The=20found=20handlers=20are=20then=20applied=20to=20the=20bean=20bein=
g=20processed
=20
This=20seems=20to=20be=20a=20perfectly=20sane=20and=20valid=20series=20of=20=
calls.=20In=20fact,=20the=20only=20real=20difference=20between=20this=20an=
d=20DefaultAdvisorAutoProxyCreator=20is=20that=20collaborators=20are=20loc=
ated=20by=20type=20and=20not=20by=20name,=20which=20is=20not=20unreasonabl=
e.=20However,=20an=20issue=20occurs=20when=20a=20bean=20you=20expect=20to=20=
be=20post-processed=20is=20itself=20a=20dependency=20of=20a=20FactoryBean=20=
that=20is=20not=20lazily=20instantiated.=20All=20FactoryBeans=20are=20auto=
matically=20instantiated=20when=20we=20locate=20beans=20by=20type,=20to=20=
determine=20what=20type=20of=20object=20they=20return.=20However,=20this=20=
in=20turn=20instantiates=20all=20of=20the=20FactoryBean's=20dependencies=20=
-=20one=20of=20which=20is=20a=20bean=20we=20expect=20to=20be=20handled=20b=
y=20our=20BeanPostProcessor,=20which=20does=20not=20process=20it=20since=20=
we=20are=20already=20in=20a=20call=20stack=20protected=20by=20ControlFlow.=
=20The=20result=20is=20that=20some=20beans=20are=20registered=20with=20our=
=20JMX=20server,=20and=20some=20aren't=20-=20and=20the=20ones=20that=20are=
n't=20are=20those=20that=20happen=20to=20be=20dependencies=20of=20non-lazy=
=20FactoryBeans.=20
=20
All=20of=20the=20above=20is=20exactly=20the=20behaviour=20you=20would=20ex=
pect=20if=20you=20were=20paying=20really=20close=20attention=20-=20except=20=
I=20wasn't=20and=20it=20surprised=20the=20hell=20out=20of=20me.=20If=20the=
=20TODO=20in=20AbstractAdvisorAutoProxyCreator=20is=20to=20be=20believed=20=
(in=20the=201.0.2=20source),=20the=20ControlFlow=20check=20is=20likely=20t=
o=20end=20up=20in=20a=20base=20class=20for=20broader=20re-use.=20Thus,=20i=
s=20it=20worth=20explicitly=20documenting=20(assuming=20that=20it=20isn't=20=
already)=20that=20ListableBeanFactory.getBeansOfType=20can=20cause=20probl=
ems=20like=20this=20with=20FactoryBeans=20and=20should=20be=20used=20with=20=
care?
=20
Dave=20Hewitt
------------------
Systems=20Engineer
OBJECTIVITY
Tel:=20024=207642=200000
Fax:=20024=207642=200001
Email:=20d...@ob...=20<mailto:dh...@ob...>=20=

www.objectivity.co.uk=20<http://www.objectivity.co.uk/>=20
=20

________________________________________________________________________
This=20e-mail=20has=20been=20scanned=20for=20all=20viruses=20by=20Star=20I=
nternet.=20The
service=20is=20powered=20by=20MessageLabs.=20For=20more=20information=20on=
=20a=20proactive
anti-virus=20service=20working=20around=20the=20clock,=20around=20the=20gl=
obe,=20visit:
http://www.star.net.uk
________________________________________________________________________

Re: [Springframework-developer] Tests (groovy!)

[Rod J. <rod...@in...>]

Darren

I'd definitely like to continue to explore the use of Groovy. Juergen has a
good point re the imminent 1.1 releases, but beyond that I think this is
definitely important and likely to be beneficial. I would be surpised if we
don't find other uses of Groovy in 1.2...

R

----- Original Message -----
From: "Darren Davison" <da...@da...>
To: <spr...@li...>
Sent: Friday, July 23, 2004 4:16 PM
Subject: Re: [Springframework-developer] Tests (groovy!)



> Sounds plausible! Still, for the time being, I'd prefer if our release
> distributions don't have to include Groovy: i.e., our framework test suite
> does not depend on groovy.jar. If we want to use Groovy for core
> frameworks tests, let's do this after Spring 1.1 final (or at least, after
> 1.1 RC1).
>
> Of course, groovy.jar can reside in our CVS lib directory; we just
> wouldn't include in the release zip. However, Groovy-dependent tests
> should preferably not reside in the "test" directory for the time being,
> but rather in some separate directory that doesn't get included in release
> zips.
>
> My main concern is to get 1.1 RC1 and 1.1 final out the door as soon as
> possible, and to avoid anything that could potentially cause
> complications. As we ship our tests, dependencies, and build scripts, they
> should be considered in feature freeze mode too.

sounds fine to me.  No-one's in any *need* of this after all - it was just
a way to make tests potentially easier to write and therefore more likely
that people *would* write them.  Given immature IDE integration and the
additional learning curve, there's not even any guarantee that writing
code in Groovy is going to be quicker than writing the equivalent, more
verbose Java :)

I'm happy to drop it altogether if there's not enough interest - at least
we know it's simple to integrate should we choose to look at it again in
the future.

I still might look at the possibility of using Groovy (or other BSF
script) as a bean definition language.  This has cropped up on the lists
before.

Cheers!

--
Darren Davison
Public Key: http://www.davison.uk.net/pages/key.htm




-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idG21&alloc_id040&op=ick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] Tests (groovy!)

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

> Sounds plausible! Still, for the time being, I'd prefer if our release
> distributions don't have to include Groovy: i.e., our framework test su=
ite
> does not depend on groovy.jar. If we want to use Groovy for core
> frameworks tests, let's do this after Spring 1.1 final (or at least, af=
ter
> 1.1 RC1).
>
> Of course, groovy.jar can reside in our CVS lib directory; we just
> wouldn't include in the release zip. However, Groovy-dependent tests
> should preferably not reside in the "test" directory for the time being=
,
> but rather in some separate directory that doesn't get included in rele=
ase
> zips.
>
> My main concern is to get 1.1 RC1 and 1.1 final out the door as soon as
> possible, and to avoid anything that could potentially cause
> complications. As we ship our tests, dependencies, and build scripts, t=
hey
> should be considered in feature freeze mode too.

sounds fine to me.  No-one's in any *need* of this after all - it was jus=
t
a way to make tests potentially easier to write and therefore more likely
that people *would* write them.  Given immature IDE integration and the
additional learning curve, there's not even any guarantee that writing
code in Groovy is going to be quicker than writing the equivalent, more
verbose Java :)

I'm happy to drop it altogether if there's not enough interest - at least
we know it's simple to integrate should we choose to look at it again in
the future.

I still might look at the possibility of using Groovy (or other BSF
script) as a bean definition language.  This has cropped up on the lists
before.

Cheers!

--=20
Darren Davison
Public Key: http://www.davison.uk.net/pages/key.htm

RE: [Springframework-developer] Velocity, XSLT integration

[Stefan D S. <ste...@us...>]

So tiles will be the nly way to do this? If you get a working model and I=
 be happy to give it a test.


Friday, July 23, 2004 9:28 AM
To: <spr...@li...>
cc: =

From: "Rob Harrop" <ro...@ca...>
Subject: RE: [Springframework-developer] Velocity, XSLT integration


I=92m guessing that we would have to add support for both Velocity and XS=
LT under Tiles. That way you could use Tiles to perform the layout and th=
en use Velocity views for one tile and XSLT for another.
 =

I am going to finish some JMX stuff up today and then take a look at this=
 Velocity integration over the weekend, because I need it for a project. =
If I have time I will look at XSLT as well.

Rob
 =




From: spr...@li... [mailto:sprin=
gfr...@li...] On Behalf Of Stefan D S=
ookraj
Sent: 23 July 2004 12:51
To: spr...@li...
Subject: [Springframework-developer] Velocity, XSLT integration
 =

On the subject of view integration, how would I integrate Velocity and XS=
LT views? I have my left nav bar done in velocity and do not want to redu=
ndanly redo the logic for XSLT. How can I use Velocity for the left nav, =
header and footer and XSLT for the main content area? Is this possible an=
d is there an example? Thank you.
 =

 =

 =

 =

 =

 =

Friday, July 23, 2004 6:09 AM
To: <spr...@li...>
cc: =

From: "Alef Arendsen" <al...@jt...>
Subject: RE: [Springframework-developer] Velocity, Tiles and Spring
I had a short email chat with Pavl Muller on this... He's sent me his cod=
e for integration tiles with velocity (TilesVelocityView and even views m=
ixing velocity and jsp in different Tiles I believe). I'll forward it to =
you. Didn't have the time to look at it yet...
 =

alef
 =

 =




From: spr...@li... [mailto:sprin=
gfr...@li...] On Behalf Of Rob Harrop=

Sent: Friday, July 23, 2004 11:15 AM
To: spr...@li...
Subject: [Springframework-developer] Velocity, Tiles and Spring
All,
 =

I have a quick question  what is the best way of using Velocity as the co=
mponent views for a Tiles-based view in Spring?
 =

Rob=

Re: [Springframework-developer] Tests (groovy!)

[<jue...@we...>]

Sounds plausible! Still, for the time being, I'd prefer if our release =
distributions don't have to include Groovy: i.e., our framework test =
suite does not depend on groovy.jar. If we want to use Groovy for core =
frameworks tests, let's do this after Spring 1.1 final (or at least, =
after 1.1 RC1).

Of course, groovy.jar can reside in our CVS lib directory; we just =
wouldn't include in the release zip. However, Groovy-dependent tests =
should preferably not reside in the "test" directory for the time being, =
but rather in some separate directory that doesn't get included in =
release zips.

My main concern is to get 1.1 RC1 and 1.1 final out the door as soon as =
possible, and to avoid anything that could potentially cause =
complications. As we ship our tests, dependencies, and build scripts, =
they should be considered in feature freeze mode too.

Other opinions on this?

Juergen


-----Original Message-----
From: spr...@li...
[mailto:spr...@li...]On Behalf
Of Darren Davison
Sent: Thursday, July 22, 2004 2:34 PM
To: spr...@li...
Subject: Re: [Springframework-developer] Tests (groovy!)



> Darren,
>
> Are you modifying Spring's standard build process here? Will this make
> Spring's standard build depend on Groovy? I feel that this is not too
> appropriate given that we are about to release 1.1 RC1 within the next
> couple of days.

No it won't affect the build or make it depend on groovy.  What I've =
done
for now is to take a copy of build.xml (called groovy-build.xml) and =
added
the groovyc taskdef and task to the buildtests target in there while
experimenting with it.  In fact those are the only 2 changes required to
the build to enable the whole process - it's pretty seamless.  Nor have =
I
modified any of the existing test classes, rather I've duplicated two =
test
classes, so in the tree for those 2 files only, a corresponding
*Tests.groovy file exists alongside the *Tests.java file.

If you build with build.xml, nothing unusual happens - any .groovy files
in the tree are simply ignored by javac and junit.  If you specify
-buildfile groovy-build.xml then the groovyc task will compile *.groovy
files to standard *.class files just as the javac task handles *.java
files.  The two languages can be mixed and matched seamlessly as the
bytecode is standard.

Once people have had a look at it, if it's something we want to use as =
an
option then we'd modify the main build.xml as described - but that can =
be
whenever.  Of course at that point, any new tests written in groovy
*would* have a dependency on groovy.jar but this is no more onerous than
depending on any other jar.  See below..

> I certainly don't object to doing tests with Groovy, but remember that =
we
> ship our build file and all libraries that we depend on in the
> "-with-dependencies" download, so that people can build Spring =
themselves
> respectively run the test suite themselves. For 1.1, they should be =
able
> to do this without Groovy, IMO.

that's no problem, they can do that.  The only dependencies when running
tests written with groovy are: groovy.jar, which will be in /lib/groovy
(it also contains the groovyc ant task) and asm.jar which we already
depend on anyway.  The junit side of things is completely unmodified =
since
any tests written in groovy extend GroovyTest which in turn extends
junit.framework.TestCase somewhere along the line.

There's no requirement to install any of the groovy binaries or other =
bits
and pieces you can download from them, even when writing and running
groovy based unit tests - it's all pure java and all invoked via ant.

If you're still not comfortable with it and want to hold off committing
for a while, that's no problem at all.  The _only_ impact it will have =
is
adding a couple of hundred KB to the size of the release zip in =
practice,
since it will just be "another jar file" and won't be implicated in
anything the users want to do with the tests.

> Sorry if I misunderstand something here...

not at all - just let me know if you'd still prefer me to hold off?

Best wishes,
--=20
Darren Davison
Public Key: http://www.davison.uk.net/pages/key.htm




-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idG21&alloc_id=10040&op=3Dick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer