Menu
▾
▴
springframework-developer — Spring Framework developers list
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
(55) |
Mar
(100) |
Apr
(203) |
May
(330) |
Jun
(190) |
Jul
(302) |
Aug
(323) |
Sep
(197) |
Oct
(245) |
Nov
(490) |
Dec
(330) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(194) |
Feb
(400) |
Mar
(416) |
Apr
(415) |
May
(359) |
Jun
(381) |
Jul
(491) |
Aug
(311) |
Sep
(291) |
Oct
(273) |
Nov
(355) |
Dec
(266) |
| 2005 |
Jan
(306) |
Feb
(303) |
Mar
(520) |
Apr
(346) |
May
(255) |
Jun
(221) |
Jul
(171) |
Aug
(247) |
Sep
(147) |
Oct
(125) |
Nov
(165) |
Dec
(65) |
| 2006 |
Jan
(90) |
Feb
(53) |
Mar
(121) |
Apr
(103) |
May
(113) |
Jun
(103) |
Jul
(104) |
Aug
(67) |
Sep
(78) |
Oct
(82) |
Nov
(78) |
Dec
(70) |
| 2007 |
Jan
(77) |
Feb
(76) |
Mar
(63) |
Apr
(30) |
May
(47) |
Jun
(41) |
Jul
(44) |
Aug
(44) |
Sep
(49) |
Oct
(33) |
Nov
(25) |
Dec
(21) |
| 2008 |
Jan
(45) |
Feb
(13) |
Mar
(15) |
Apr
(12) |
May
(9) |
Jun
(33) |
Jul
(30) |
Aug
(7) |
Sep
(20) |
Oct
(17) |
Nov
(20) |
Dec
(10) |
| 2009 |
Jan
(8) |
Feb
(5) |
Mar
(12) |
Apr
(17) |
May
(19) |
Jun
(97) |
Jul
(77) |
Aug
(33) |
Sep
(24) |
Oct
(41) |
Nov
(16) |
Dec
(32) |
| 2010 |
Jan
(24) |
Feb
(14) |
Mar
(50) |
Apr
(71) |
May
(70) |
Jun
(64) |
Jul
(45) |
Aug
(62) |
Sep
(32) |
Oct
(4) |
Nov
(12) |
Dec
(2) |
| 2011 |
Jan
(1) |
Feb
(3) |
Mar
(4) |
Apr
(3) |
May
(6) |
Jun
(1) |
Jul
(4) |
Aug
(3) |
Sep
(4) |
Oct
(6) |
Nov
(3) |
Dec
(3) |
| 2012 |
Jan
(4) |
Feb
(8) |
Mar
(6) |
Apr
(10) |
May
(2) |
Jun
(3) |
Jul
(11) |
Aug
(10) |
Sep
(4) |
Oct
|
Nov
(1) |
Dec
(1) |
| 2013 |
Jan
(4) |
Feb
(1) |
Mar
(9) |
Apr
(1) |
May
(8) |
Jun
(2) |
Jul
(5) |
Aug
(2) |
Sep
|
Oct
(3) |
Nov
(10) |
Dec
(8) |
| 2014 |
Jan
(3) |
Feb
(12) |
Mar
(9) |
Apr
(12) |
May
(2) |
Jun
|
Jul
(3) |
Aug
(1) |
Sep
(1) |
Oct
(4) |
Nov
|
Dec
(2) |
| 2015 |
Jan
(1) |
Feb
(3) |
Mar
(4) |
Apr
(9) |
May
(2) |
Jun
(2) |
Jul
|
Aug
(2) |
Sep
(7) |
Oct
(9) |
Nov
(7) |
Dec
(9) |
| 2016 |
Jan
(7) |
Feb
(5) |
Mar
(5) |
Apr
(5) |
May
(8) |
Jun
(4) |
Jul
(5) |
Aug
(4) |
Sep
(6) |
Oct
(7) |
Nov
(2) |
Dec
(3) |
| 2017 |
Jan
(7) |
Feb
(8) |
Mar
(7) |
Apr
(3) |
May
(4) |
Jun
(3) |
Jul
(5) |
Aug
(8) |
Sep
(4) |
Oct
(2) |
Nov
(3) |
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2019 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2021 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(2) |
Aug
(5) |
Sep
(2) |
Oct
|
Nov
|
Dec
(1) |
| 2026 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Erwin V. <erw...@er...> - 2005-03-11 11:46:18
|
I've brought the taglib documentation up-to-date. It's available in CVS (docs/taglib). Since this is not related to the 1.2 release, we can put it up on the website immediately! Can somebody do this please. Erwin Vervaet erw...@er... ----- Original Message ----- From: "Erwin Vervaet" <erw...@er...> To: <spr...@li...> Sent: Monday, January 24, 2005 7:30 PM Subject: Spring tag library docs > I'm not sure who is maintaining the Spring Tag Library docs you can find > at http://www.springframework.org/docs/taglib/index.html, but they are > somewhat 'lacking' :-) > > Maybe somebody can improve this with the 1.1.4 release still in the > pipeline. > > Erwin Vervaet |
|
From: Erwin V. <erw...@er...> - 2005-03-11 07:43:54
|
First try "method", and if that's not found try "action" to deal with backwards compatibility? Erwin Vervaet erw...@er... ----- Original Message ----- From: "Colin Sampaleanu" <col...@ex...> To: <spr...@li...> Sent: Thursday, March 10, 2005 11:18 PM Subject: Re: [Springframework-developer] Re: ParameterNameMethodNameResolver > Matt Raible wrote: > >> >> On Mar 10, 2005, at 3:04 PM, kat...@ho... wrote: >> >>> While on the topic, we should look at renaming the default parameter to >>> something other than 'action'. This clashes with the form's 'action' in >>> Javascript, and so is maybe not a good default. This would probably be >>> OK as part of a 1.2 release. >> >> >> +1, I'd recommend "method" or something. I've seen the same issue re: >> JavaScript, forms and button names. > > Hmm, > > I kind of like the idea, but this would probably break exsiting apps that > relied on the "action" default. They would not require a recompile, a > config change to set the property back to "action" would do, but I'm a bit > loath to break backwards compatibility in a .X release for something > that's not a true bug. Even now people can alway rename the param name. > > Anybody else have an opinion on this? > > 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 > > |
|
From: Seth L. <set...@gm...> - 2005-03-11 03:29:11
|
Aloha, I know there is a nice util method for BeanUtils.instantiateClass() that wraps the exception that might be thrown. I'm working on the RequiredDependencyCheckingPostProcessor, and I'm looking for a util method that handles getting the value from a field (/not/ a property) and wrapping the exception. It appears that BeanWrapper works with getters, which I'm trying to avoid. Is there such a thing? I've got it all working now, but wanted to clean it up and use what Spring already has (since I know it has a lot of nice util methods). Also, I can't find an exception under PropertyAccessException for FieldAccessException, or some cousin of IllegalAccessException in the BeansException hierarchy. It would be a useful thing to have, along with the util method to get a field value. Tips? Mahalo! 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> |
|
From: Dmitriy K. <dko...@ru...> - 2005-03-11 01:58:12
|
Done. Dmitriy. Seth Ladd wrote: >Hello, > >Can someone please add the new cglib-nodep-2.1.jar back into the >eclipse .classpath file? > >Mahalo! >Seth > >Index: .classpath >=================================================================== >RCS file: /cvsroot/springframework/spring/.classpath,v >retrieving revision 1.91 >diff -u -r1.91 .classpath >--- .classpath 6 Mar 2005 07:35:05 -0000 1.91 >+++ .classpath 11 Mar 2005 01:33:35 -0000 >@@ -95,7 +95,6 @@ > <classpathentry kind="lib" path="lib/itext/itext-1.1.4.jar"/> > <classpathentry kind="lib" path="lib/ibatis/ibatis-common-2.jar"/> > <classpathentry kind="lib" path="lib/jakarta-commons/commons-codec.jar"/> >- <classpathentry kind="lib" path="lib/cglib/cglib-nodep-2.1-dev.jar"/> > <classpathentry kind="lib" path="lib/ehcache/ehcache-1.1.jar"/> > <classpathentry kind="lib" path="lib/jasperreports/jasperreports-0.6.4.jar"/> > <classpathentry kind="lib" >path="lib/aspectwerkz/aspectwerkz-2.0.RC3-snapshot.jar"/> >@@ -103,5 +102,6 @@ > <classpathentry kind="lib" path="lib/j2ee/servlet-api.jar"/> > <classpathentry kind="lib" path="lib/j2ee/jsp-api.jar"/> > <classpathentry kind="lib" path="lib/c3p0/c3p0-0.8.5.jar"/> >+ <classpathentry kind="lib" path="lib/cglib/cglib-nodep-2.1.jar"/> > <classpathentry kind="output" path="target/other-classes"/> > </classpath> > > > > |
|
From: Seth L. <set...@gm...> - 2005-03-11 01:35:32
|
Hello, Can someone please add the new cglib-nodep-2.1.jar back into the eclipse .classpath file? Mahalo! Seth Index: .classpath =================================================================== RCS file: /cvsroot/springframework/spring/.classpath,v retrieving revision 1.91 diff -u -r1.91 .classpath --- .classpath 6 Mar 2005 07:35:05 -0000 1.91 +++ .classpath 11 Mar 2005 01:33:35 -0000 @@ -95,7 +95,6 @@ <classpathentry kind="lib" path="lib/itext/itext-1.1.4.jar"/> <classpathentry kind="lib" path="lib/ibatis/ibatis-common-2.jar"/> <classpathentry kind="lib" path="lib/jakarta-commons/commons-codec.jar"/> - <classpathentry kind="lib" path="lib/cglib/cglib-nodep-2.1-dev.jar"/> <classpathentry kind="lib" path="lib/ehcache/ehcache-1.1.jar"/> <classpathentry kind="lib" path="lib/jasperreports/jasperreports-0.6.4.jar"/> <classpathentry kind="lib" path="lib/aspectwerkz/aspectwerkz-2.0.RC3-snapshot.jar"/> @@ -103,5 +102,6 @@ <classpathentry kind="lib" path="lib/j2ee/servlet-api.jar"/> <classpathentry kind="lib" path="lib/j2ee/jsp-api.jar"/> <classpathentry kind="lib" path="lib/c3p0/c3p0-0.8.5.jar"/> + <classpathentry kind="lib" path="lib/cglib/cglib-nodep-2.1.jar"/> <classpathentry kind="output" path="target/other-classes"/> </classpath> -- <a href="http://www.picklematrix.net/foaf.rdf">Seth Ladd's FOAF</a> <a href="http://www.foaf-project.org/">What is FOAF?</a> |
|
From: Colin S. <col...@ex...> - 2005-03-10 23:50:47
|
Short of switching to separate source modules (hint hint :-) ), that's going to be pretty hard to do. We can compile with JDK 1.5, for lower target versions, but then if you don't specify a 1.5 target version, the annotations stuff would blow up. Juergen Hoeller wrote: > Thanks for the suggestion, Dan! I've prototypically added such an > AnnotationsSessionFactoryBean. > However, the Hibernate3 annotations jar is built with JDK 1.5, so we > can only build and ship this class if our build process switches to > JDK 1.5 required too. We might switch to building with JDK 1.5 anyway, > though, for our new transaction annotation feature that we'd like to > ship in Spring 1.2. > Juergen > > -----Original Message----- > *From:* spr...@li... > [mailto:spr...@li...]*On > Behalf Of *Washusen, Dan > *Sent:* Thursday, March 10, 2005 7:09 AM > *To:* spr...@li... > *Subject:* RE: [Springframework-developer] Hibernate 3 annotations > in 1.2 rc1 > > Incase anyone is interested; I’ve attached an implementation of > the bean definition I described below. > > Cheers, > > Dan > > ------------------------------------------------------------------------ > > *From:* spr...@li... > [mailto:spr...@li...] *On > Behalf Of *Washusen, Dan > *Sent:* Wednesday, 9 March 2005 12:29 PM > *To:* spr...@li... > *Subject:* [Springframework-developer] Hibernate 3 annotations in > 1.2 rc1 > > 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… > > 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. > > Pretty easy really… > > A provided extension of LocalSessionFactoryBean that had support > for annotated classes would be nice. The bean definition could > look something like: > > <bean id="sessionFactory" > class="org.springframework.orm.hibernate3.AnnotationsLocalSessionFactoryBean"> > > <property name="dataSource"> > > <ref local="dataSource"/> > > </property> > > <property name="mappingPackage"> > > <value>some.package</value> > > </property> > > <property name="annotatedClasses"> > > <list> > > <value>com.package.Foo</value> > > <value>com.package.Bar</value> > > </list> > > </property> > > </bean> > > Cheers, > > Dan > >www.sensis.com.au > >A leading Australian advertising, information > >and directories business. > > >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] > > >www.sensis.com.au > >A leading Australian advertising, information > >and directories business. > > >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] > > |
|
From: <al...@jt...> - 2005-03-10 23:41:16
|
<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 - =
build.221</td></tr><tr><td class=3D"header-data"><span class=
=3D"header-label">Date of build: </span>03/11/2005 00:16:44</td></tr><=
tr><td class=3D"header-data"><span class=3D"header-label">Time to build:&nb=
sp;</span>22 minutes 52 seconds</td></tr><tr><td class=3D"header-data"><spa=
n class=3D"header-label">Last changed: </span>03/10/2005 20:06:48</td>=
</tr><tr><td class=3D"header-data"><span class=3D"header-label">Last log en=
try: </span>properly clean up all JMX resources</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"> Errors/Warnings: (=
1389) </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"/># ----------------------------------------------------------------<b=
r class=3D"none"/>#<br class=3D"none"/># Spring Autobuilds - automatic app=
lication deployment and testing<br class=3D"none"/>#<br class=3D"none"/># =
target application: buildtest<br class=3D"none"/># target server: tomcat4<=
br class=3D"none"/>#<br class=3D"none"/># this output is recorded in the f=
ile:<br class=3D"none"/># ../../target/autobuilds/reports/buildtest_tomcat=
4_build_2005-03-11.log<br class=3D"none"/># ------------------------------=
----------------------------------<br class=3D"none"/>waiting 75 seconds fo=
r 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 fo=
und - Javascript disabled<br class=3D"none"/>## --------------------------=
--------------------------------------<br class=3D"none"/>## Stopping serv=
er 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 class=3D"none"/>#=
Spring Autobuilds - automatic application deployment and testing<br class=
=3D"none"/>#<br class=3D"none"/># target application: buildtest<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"/># ../../targe=
t/autobuilds/reports/buildtest_tomcat5_build_2005-03-11.log<br class=3D"non=
e"/># ----------------------------------------------------------------<br =
class=3D"none"/>waiting 75 seconds for server to warmup...<br class=3D"none=
"/># ----------------------------------------------------------------<br c=
lass=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"/>## Stopping server tomcat5<br class=3D"none"/>## ----=
------------------------------------------------------------<br class=3D"no=
ne"/>## ----------------------------------------------------------------<b=
r class=3D"none"/>## Starting server tomcat5<br class=3D"none"/>## ------=
----------------------------------------------------------<br class=3D"none=
"/># ----------------------------------------------------------------<br c=
lass=3D"none"/>#<br class=3D"none"/># Spring Autobuilds - automatic applic=
ation deployment and testing<br class=3D"none"/>#<br class=3D"none"/># tar=
get application: buildtest<br class=3D"none"/># target server: jetty4<br c=
lass=3D"none"/>#<br class=3D"none"/># this output is recorded in the file:=
<br class=3D"none"/># ../../target/autobuilds/reports/buildtest_jetty4_bui=
ld_2005-03-11.log<br class=3D"none"/># -----------------------------------=
-----------------------------<br class=3D"none"/>waiting 75 seconds for ser=
ver 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"/>## Stopping server je=
tty4<br class=3D"none"/>## -----------------------------------------------=
-----------------<br class=3D"none"/>## ----------------------------------=
------------------------------<br class=3D"none"/>## Starting server jetty=
4<br class=3D"none"/>## --------------------------------------------------=
--------------<br class=3D"none"/># --------------------------------------=
--------------------------<br class=3D"none"/>#<br class=3D"none"/># Sprin=
g Autobuilds - automatic application deployment and testing<br class=3D"non=
e"/>#<br class=3D"none"/># target application: jpetstore<br class=3D"none"=
/># target server: tomcat4<br class=3D"none"/>#<br class=3D"none"/># this=
output is recorded in the file:<br class=3D"none"/># ../../target/autobui=
lds/reports/jpetstore_tomcat4_build_2005-03-11.log<br class=3D"none"/># --=
--------------------------------------------------------------<br class=3D"=
none"/>waiting 75 seconds for server to warmup...<br class=3D"none"/># ---=
-------------------------------------------------------------<br class=3D"n=
one"/># 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 s=
erver tomcat4<br class=3D"none"/>## --------------------------------------=
--------------------------<br class=3D"none"/>## -------------------------=
---------------------------------------<br class=3D"none"/>## Starting ser=
ver tomcat4<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: tomcat5<br class=3D"none"/>#<br class=3D"none=
"/># this output is recorded in the file:<br class=3D"none"/># ../../targ=
et/autobuilds/reports/jpetstore_tomcat5_build_2005-03-11.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 tomcat5<br class=3D"none"/>## -------------------------=
---------------------------------------<br class=3D"none"/>## ------------=
----------------------------------------------------<br class=3D"none"/>## =
Starting server tomcat5<br class=3D"none"/>## ---------------------------=
-------------------------------------<br class=3D"none"/>/jteam/build2/chec=
kout/spring/spring/src/org/springframework/web/servlet/mvc/multiaction/Para=
meterMethodNameResolver.java:59: warning - Tag @see: can't find setMappings=
(String[]) in org.springframework.web.servlet.mvc.multiaction.ParameterMeth=
odNameResolver<br class=3D"none"/>/jteam/build2/checkout/spring/spring/src/=
org/springframework/jmx/export/assembler/InterfaceBasedMBeanInfoAssembler.j=
ava:153: warning - Tag @see: can't find isPublicInInterface(java.lang.refle=
ct.Method, String) in org.springframework.jmx.export.assembler.InterfaceBas=
edMBeanInfoAssembler<br class=3D"none"/>/jteam/build2/checkout/spring/sprin=
g/src/org/springframework/jmx/export/assembler/InterfaceBasedMBeanInfoAssem=
bler.java:125: warning - Tag @see: can't find isPublicInInterface(java.lang=
.reflect.Method, String) in org.springframework.jmx.export.assembler.Interf=
aceBasedMBeanInfoAssembler<br class=3D"none"/>/jteam/build2/checkout/spring=
/spring/src/org/springframework/jmx/export/assembler/InterfaceBasedMBeanInf=
oAssembler.java:139: warning - Tag @see: can't find isPublicInInterface(jav=
a.lang.reflect.Method, String) in org.springframework.jmx.export.assembler.=
InterfaceBasedMBeanInfoAssembler<br class=3D"none"/>/jteam/build2/checkout/=
spring/spring/src/org/springframework/jdbc/support/lob/OracleLobHandler.jav=
a:76: warning - Tag @see: reference not found: oracle.sql.BLOB<br class=3D"=
none"/>/jteam/build2/checkout/spring/spring/src/org/springframework/jdbc/su=
pport/lob/OracleLobHandler.java:76: warning - Tag @see: reference not found=
: oracle.sql.CLOB<br class=3D"none"/>/jteam/build2/checkout/spring/spring/s=
rc/org/springframework/jdbc/support/lob/OracleLobHandler.java:115: warning =
- Tag @see: reference not found: oracle.sql.BLOB#DURATION_SESSION<br class=
=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/springframework/jdb=
c/support/lob/OracleLobHandler.java:115: warning - Tag @see: reference not =
found: oracle.sql.BLOB#MODE_READWRITE<br class=3D"none"/>/jteam/build2/chec=
kout/spring/spring/src/org/springframework/jdbc/support/lob/OracleLobHandle=
r.java:115: warning - Tag @see: reference not found: oracle.sql.CLOB#DURATI=
ON_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.CLOB#MODE_READWRITE<br class=3D"none"/=
>/jteam/build2/checkout/spring/spring/src/org/springframework/jdbc/support/=
lob/OracleLobHandler.java:154: warning - Tag @see: reference not found: ora=
cle.jdbc.OracleConnection<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.BLOB#createTemporary<br=
class=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/springframewo=
rk/jdbc/support/lob/OracleLobHandler.java:164: warning - Tag @see: referenc=
e not found: oracle.sql.CLOB#createTemporary<br class=3D"none"/>/jteam/buil=
d2/checkout/spring/spring/src/org/springframework/jdbc/support/nativejdbc/J=
BossNativeJdbcExtractor.java:49: warning - Tag @see: reference not found: o=
rg.jboss.resource.adapter.jdbc.WrappedConnection#getUnderlyingConnection<br=
class=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/springframewo=
rk/jdbc/support/nativejdbc/JBossNativeJdbcExtractor.java:49: warning - Tag =
@see: reference not found: org.jboss.resource.adapter.jdbc.WrappedStatement=
#getUnderlyingStatement<br class=3D"none"/>/jteam/build2/checkout/spring/sp=
ring/src/org/springframework/jdbc/support/nativejdbc/JBossNativeJdbcExtract=
or.java:49: warning - Tag @see: reference not found: org.jboss.resource.ada=
pter.jdbc.WrappedResultSet#getUnderlyingResultSet<br class=3D"none"/>/jteam=
/build2/checkout/spring/spring/src/org/springframework/jdbc/support/nativej=
dbc/WebLogicNativeJdbcExtractor.java:45: warning - Tag @see: reference not =
found: weblogic.jdbc.extensions.WLConnection#getVendorConnection<br class=
=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/springframework/jdb=
c/support/nativejdbc/WebSphereNativeJdbcExtractor.java:49: warning - Tag @s=
ee: reference not found: com.ibm.ws.rsadapter.jdbc.WSJdbcConnection<br clas=
s=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/springframework/jd=
bc/support/nativejdbc/WebSphereNativeJdbcExtractor.java:49: warning - Tag @=
see: reference not found: com.ibm.ws.rsadapter.jdbc.WSJdbcUtil#getNativeCon=
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.ejs.cm.proxy.ConnectionPro=
xy#getPhysicalConnection<br class=3D"none"/>/jteam/build2/checkout/spring/s=
pring/src/org/springframework/orm/hibernate3/LocalSessionFactoryBean.java:3=
39: warning - Tag @see: reference not found: org.hibernate.UserType<br clas=
s=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/springframework/or=
m/hibernate3/SessionFactoryUtils.java:155: warning - Tag @see: reference no=
t found: org.hibernate.impl.SessionFactoryImpl<br class=3D"none"/>/jteam/bu=
ild2/checkout/spring/spring/src/org/springframework/orm/hibernate3/SessionF=
actoryUtils.java:155: warning - Tag @see: reference not found: org.hibernat=
e.jca.JCASessionFactoryImpl<br class=3D"none"/>/jteam/build2/checkout/sprin=
g/spring/src/org/springframework/orm/ibatis/SqlMapClientFactoryBean.java:19=
8: warning - Tag @see: reference not found: com.ibatis.sqlmap.engine.transa=
ction.jdbc.JdbcTransactionConfig<br class=3D"none"/>/jteam/build2/checkout/=
spring/spring/src/org/springframework/orm/ibatis/SqlMapClientFactoryBean.ja=
va:198: warning - Tag @see: reference not found: com.ibatis.sqlmap.engine.t=
ransaction.jta.JtaTransactionConfig<br class=3D"none"/>/jteam/build2/checko=
ut/spring/spring/src/org/springframework/orm/ibatis/SqlMapClientFactoryBean=
.java:226: warning - Tag @see: reference not found: com.ibatis.sqlmap.engin=
e.transaction.jdbc.JdbcTransactionConfig<br class=3D"none"/>/jteam/build2/c=
heckout/spring/spring/src/org/springframework/orm/ibatis/SqlMapClientFactor=
yBean.java:226: warning - Tag @see: reference not found: com.ibatis.sqlmap.=
engine.transaction.jta.JtaTransactionConfig<br class=3D"none"/>/jteam/build=
2/checkout/spring/spring/src/org/springframework/transaction/jta/WebLogicJt=
aTransactionManager.java:66: warning - Tag @see: reference not found: weblo=
gic.transaction.TransactionManager#forceResume<br class=3D"none"/>/jteam/bu=
ild2/checkout/spring/spring/src/org/springframework/transaction/jta/WebLogi=
cServerTransactionManagerFactoryBean.java:45: warning - Tag @see: reference=
not found: weblogic.transaction.TxHelper#getTransactionManager<br class=3D=
"none"/>/jteam/build2/checkout/spring/spring/src/org/springframework/transa=
ction/jta/WebSphereTransactionManagerFactoryBean.java:49: warning - Tag @se=
e: reference not found: com.ibm.ws.Transaction.TransactionManagerFactory#ge=
tTransactionManager<br class=3D"none"/>/jteam/build2/checkout/spring/spring=
/src/org/springframework/transaction/jta/WebSphereTransactionManagerFactory=
Bean.java:49: warning - Tag @see: reference not found: com.ibm.ejs.jts.jta.=
JTSXA#getTransactionManager<br class=3D"none"/>/jteam/build2/checkout/sprin=
g/spring/src/org/springframework/transaction/jta/WebSphereTransactionManage=
rFactoryBean.java:49: warning - Tag @see: reference not found: com.ibm.ejs.=
jts.jta.TransactionManagerFactory#getTransactionManager<br class=3D"none"/>=
/jteam/build2/checkout/spring/spring/src/org/springframework/util/ObjectUti=
ls.java:31: warning - Tag @see: reference not found: org.apache.commons.lan=
g.ObjectUtils<br class=3D"none"/>/jteam/build2/checkout/spring/spring/src/o=
rg/springframework/util/StringUtils.java:47: warning - Tag @see: reference =
not found: org.apache.commons.lang.StringUtils<br class=3D"none"/>/jteam/bu=
ild2/checkout/spring/spring/src/org/springframework/web/servlet/handler/met=
adata/PathMap.java:31: warning - @@org.apache.commons.attributes.Indexed() =
is an unknown tag.<br class=3D"none"/>/jteam/build2/checkout/spring/spring/=
src/org/springframework/web/servlet/mvc/multiaction/ParameterMethodNameReso=
lver.java:119: warning - Tag @link: can't find defaultMethodName in org.spr=
ingframework.web.servlet.mvc.multiaction.ParameterMethodNameResolver<br cla=
ss=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/springframework/w=
eb/servlet/mvc/multiaction/ParameterMethodNameResolver.java:100: warning - =
Tag @link: can't find logicalMappings in org.springframework.web.servlet.mv=
c.multiaction.ParameterMethodNameResolver<br class=3D"none"/>/jteam/build2/=
checkout/spring/spring/src/org/springframework/web/servlet/mvc/multiaction/=
ParameterMethodNameResolver.java:100: warning - Tag @link: can't find param=
Name in org.springframework.web.servlet.mvc.multiaction.ParameterMethodName=
Resolver<br class=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/sp=
ringframework/web/servlet/mvc/multiaction/ParameterMethodNameResolver.java:=
100: warning - Tag @link: can't find logicalMappings in org.springframework=
.web.servlet.mvc.multiaction.ParameterMethodNameResolver<br class=3D"none"/=
>/jteam/build2/checkout/spring/spring/src/org/springframework/web/servlet/m=
vc/multiaction/ParameterMethodNameResolver.java:100: warning - Tag @link: c=
an't find paramName in org.springframework.web.servlet.mvc.multiaction.Para=
meterMethodNameResolver<br class=3D"none"/>/jteam/build2/checkout/spring/sp=
ring/src/org/springframework/web/servlet/mvc/multiaction/ParameterMethodNam=
eResolver.java:100: warning - Tag @link: can't find logicalMappings in org.=
springframework.web.servlet.mvc.multiaction.ParameterMethodNameResolver<br =
class=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/springframewor=
k/web/servlet/mvc/multiaction/ParameterMethodNameResolver.java:100: warning=
- Tag @link: can't find paramName in org.springframework.web.servlet.mvc.m=
ultiaction.ParameterMethodNameResolver<br class=3D"none"/>/jteam/build2/che=
ckout/spring/spring/src/org/springframework/web/servlet/mvc/multiaction/Par=
ameterMethodNameResolver.java:100: warning - Tag @link: can't find logicalM=
appings in org.springframework.web.servlet.mvc.multiaction.ParameterMethodN=
ameResolver<br class=3D"none"/>/jteam/build2/checkout/spring/spring/src/org=
/springframework/web/servlet/mvc/multiaction/ParameterMethodNameResolver.ja=
va:100: warning - Tag @link: can't find paramName in org.springframework.we=
b.servlet.mvc.multiaction.ParameterMethodNameResolver<br class=3D"none"/>/j=
team/build2/checkout/spring/spring/src/org/springframework/web/servlet/mvc/=
multiaction/ParameterMethodNameResolver.java:100: warning - @param argument=
"an" is not a parameter name.<br class=3D"none"/>/jteam/build2/checkout/sp=
ring/spring/src/org/springframework/web/servlet/mvc/multiaction/ParameterMe=
thodNameResolver.java:119: warning - Tag @link: can't find defaultMethodNam=
e in org.springframework.web.servlet.mvc.multiaction.ParameterMethodNameRes=
olver<br class=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/sprin=
gframework/web/servlet/mvc/multiaction/ParameterMethodNameResolver.java:119=
: warning - Tag @link: can't find defaultMethodName in org.springframework.=
web.servlet.mvc.multiaction.ParameterMethodNameResolver<br class=3D"none"/>=
/jteam/build2/checkout/spring/spring/src/org/springframework/web/servlet/mv=
c/multiaction/ParameterMethodNameResolver.java:119: warning - Tag @link: ca=
n't find defaultMethodName in org.springframework.web.servlet.mvc.multiacti=
on.ParameterMethodNameResolver<br class=3D"none"/>Error on line 3 column 3 =
of file:/jteam/build2/checkout/spring/spring/docs/reference/src/webintegrat=
ion.xml:<br class=3D"none"/>Error reported by XML parser: name expected (fo=
und "<")<br class=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/spring/docs/reference/src/webintegration.xml:<br class=3D"n=
one"/>Error reported by XML parser: name expected (found "<")<br class=
=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/spri=
ng/docs/reference/src/webintegration.xml:<br class=3D"none"/>Error reported=
by XML parser: name expected (found "<")<br class=3D"none"/>Transformat=
ion failed: Run-time errors were reported<br class=3D"none"/>USAGE<br class=
=3D"none"/>Fop [options] [-fo|-xml] infile [-xsl file] [-awt|-pdf|-mif|-pcl=
|-ps|-txt|-at|-print] <outfile><br class=3D"none"/>[OPTIONS]<br class=
=3D"none"/>-d debug mode<br class=3D"none"/>-x dump confi=
guration settings<br class=3D"none"/>-q quiet mode<br class=3D"non=
e"/>-c cfg.xml use additional configuration file cfg.xml<br class=3D"none"=
/>-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 class=
=3D"none"/>-xml infile xml input file, must be used together with -xs=
l<br class=3D"none"/>-xsl stylesheet xslt stylesheet<br class=3D"none"/><=
br class=3D"none"/>[OUTPUT]<br class=3D"none"/>outfile input will=
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 outf=
ile input will be rendered as mif file (outfile req'd)<br class=3D"non=
e"/>-pcl outfile input will be rendered as pcl file (outfile req'd)<br=
class=3D"none"/>-ps outfile input will be rendered as PostScript fil=
e (outfile req'd)<br class=3D"none"/>-txt outfile input will be render=
ed 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 b=
e rendered as an svg slides file (outfile req'd)<br class=3D"none"/>-at out=
file representation of area tree as XML (outfile req'd)<br class=3D"n=
one"/>-print input file will be rendered and sent to the printer=
<br class=3D"none"/>see options with "-print help"<br class=3D"none"/>[Exam=
ples]<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"/>Fop=
-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"> Javadoc Errors/War=
nings: (48) </td></tr><tr><td><pre class=3D"compile-data=
">/jteam/build2/checkout/spring/spring/src/org/springframework/web/servlet/=
mvc/multiaction/ParameterMethodNameResolver.java:59: warning - Tag @see: ca=
n't find setMappings(String[]) in org.springframework.web.servlet.mvc.multi=
action.ParameterMethodNameResolver<br class=3D"none"/>/jteam/build2/checkou=
t/spring/spring/src/org/springframework/jmx/export/assembler/InterfaceBased=
MBeanInfoAssembler.java:153: warning - Tag @see: can't find isPublicInInter=
face(java.lang.reflect.Method, String) in org.springframework.jmx.export.as=
sembler.InterfaceBasedMBeanInfoAssembler<br class=3D"none"/>/jteam/build2/c=
heckout/spring/spring/src/org/springframework/jmx/export/assembler/Interfac=
eBasedMBeanInfoAssembler.java:125: warning - Tag @see: can't find isPublicI=
nInterface(java.lang.reflect.Method, String) in org.springframework.jmx.exp=
ort.assembler.InterfaceBasedMBeanInfoAssembler<br class=3D"none"/>/jteam/bu=
ild2/checkout/spring/spring/src/org/springframework/jmx/export/assembler/In=
terfaceBasedMBeanInfoAssembler.java:139: warning - Tag @see: can't find isP=
ublicInInterface(java.lang.reflect.Method, String) in org.springframework.j=
mx.export.assembler.InterfaceBasedMBeanInfoAssembler<br class=3D"none"/>/jt=
eam/build2/checkout/spring/spring/src/org/springframework/jdbc/support/lob/=
OracleLobHandler.java:76: warning - Tag @see: reference not found: oracle.s=
ql.BLOB<br class=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/spr=
ingframework/jdbc/support/lob/OracleLobHandler.java:76: warning - Tag @see:=
reference not found: oracle.sql.CLOB<br class=3D"none"/>/jteam/build2/chec=
kout/spring/spring/src/org/springframework/jdbc/support/lob/OracleLobHandle=
r.java:115: warning - Tag @see: reference not found: oracle.sql.BLOB#DURATI=
ON_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"none"/=
>/jteam/build2/checkout/spring/spring/src/org/springframework/jdbc/support/=
lob/OracleLobHandler.java:115: warning - Tag @see: reference not found: ora=
cle.sql.CLOB#DURATION_SESSION<br class=3D"none"/>/jteam/build2/checkout/spr=
ing/spring/src/org/springframework/jdbc/support/lob/OracleLobHandler.java:1=
15: warning - Tag @see: reference not found: oracle.sql.CLOB#MODE_READWRITE=
<br class=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/springfram=
ework/jdbc/support/lob/OracleLobHandler.java:154: warning - Tag @see: refer=
ence not found: oracle.jdbc.OracleConnection<br class=3D"none"/>/jteam/buil=
d2/checkout/spring/spring/src/org/springframework/jdbc/support/lob/OracleLo=
bHandler.java:164: warning - Tag @see: reference not found: oracle.sql.BLOB=
#createTemporary<br class=3D"none"/>/jteam/build2/checkout/spring/spring/sr=
c/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/s=
upport/nativejdbc/JBossNativeJdbcExtractor.java:49: warning - Tag @see: ref=
erence not found: org.jboss.resource.adapter.jdbc.WrappedConnection#getUnde=
rlyingConnection<br class=3D"none"/>/jteam/build2/checkout/spring/spring/sr=
c/org/springframework/jdbc/support/nativejdbc/JBossNativeJdbcExtractor.java=
:49: warning - Tag @see: reference not found: org.jboss.resource.adapter.jd=
bc.WrappedStatement#getUnderlyingStatement<br class=3D"none"/>/jteam/build2=
/checkout/spring/spring/src/org/springframework/jdbc/support/nativejdbc/JBo=
ssNativeJdbcExtractor.java:49: warning - Tag @see: reference not found: org=
.jboss.resource.adapter.jdbc.WrappedResultSet#getUnderlyingResultSet<br cla=
ss=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/springframework/j=
dbc/support/nativejdbc/WebLogicNativeJdbcExtractor.java:45: warning - Tag @=
see: reference not found: weblogic.jdbc.extensions.WLConnection#getVendorCo=
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.WSJdbcC=
onnection<br class=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/s=
pringframework/jdbc/support/nativejdbc/WebSphereNativeJdbcExtractor.java:49=
: warning - Tag @see: reference not found: com.ibm.ws.rsadapter.jdbc.WSJdbc=
Util#getNativeConnection<br class=3D"none"/>/jteam/build2/checkout/spring/s=
pring/src/org/springframework/jdbc/support/nativejdbc/WebSphereNativeJdbcEx=
tractor.java:49: warning - Tag @see: reference not found: com.ibm.ejs.cm.pr=
oxy.ConnectionProxy#getPhysicalConnection<br class=3D"none"/>/jteam/build2/=
checkout/spring/spring/src/org/springframework/orm/hibernate3/LocalSessionF=
actoryBean.java:339: warning - Tag @see: reference not found: org.hibernate=
.UserType<br class=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/s=
pringframework/orm/hibernate3/SessionFactoryUtils.java:155: warning - Tag @=
see: reference not found: org.hibernate.impl.SessionFactoryImpl<br class=3D=
"none"/>/jteam/build2/checkout/spring/spring/src/org/springframework/orm/hi=
bernate3/SessionFactoryUtils.java:155: warning - Tag @see: reference not fo=
und: org.hibernate.jca.JCASessionFactoryImpl<br class=3D"none"/>/jteam/buil=
d2/checkout/spring/spring/src/org/springframework/orm/ibatis/SqlMapClientFa=
ctoryBean.java:198: warning - Tag @see: reference not found: com.ibatis.sql=
map.engine.transaction.jdbc.JdbcTransactionConfig<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.jta.JtaTransactionConfig<br class=3D"none"/>/jt=
eam/build2/checkout/spring/spring/src/org/springframework/orm/ibatis/SqlMap=
ClientFactoryBean.java:226: warning - Tag @see: reference not found: com.ib=
atis.sqlmap.engine.transaction.jdbc.JdbcTransactionConfig<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.jta.JtaTransactionConfig<br class=3D"no=
ne"/>/jteam/build2/checkout/spring/spring/src/org/springframework/transacti=
on/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/transa=
ction/jta/WebLogicServerTransactionManagerFactoryBean.java:45: warning - Ta=
g @see: reference not found: weblogic.transaction.TxHelper#getTransactionMa=
nager<br class=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/sprin=
gframework/transaction/jta/WebSphereTransactionManagerFactoryBean.java:49: =
warning - Tag @see: reference not found: com.ibm.ws.Transaction.Transaction=
ManagerFactory#getTransactionManager<br class=3D"none"/>/jteam/build2/check=
out/spring/spring/src/org/springframework/transaction/jta/WebSphereTransact=
ionManagerFactoryBean.java:49: warning - Tag @see: reference not found: com=
.ibm.ejs.jts.jta.JTSXA#getTransactionManager<br class=3D"none"/>/jteam/buil=
d2/checkout/spring/spring/src/org/springframework/transaction/jta/WebSphere=
TransactionManagerFactoryBean.java:49: warning - Tag @see: reference not fo=
und: com.ibm.ejs.jts.jta.TransactionManagerFactory#getTransactionManager<br=
class=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/springframewo=
rk/util/ObjectUtils.java:31: warning - Tag @see: reference not found: org.a=
pache.commons.lang.ObjectUtils<br class=3D"none"/>/jteam/build2/checkout/sp=
ring/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/se=
rvlet/handler/metadata/PathMap.java:31: warning - @@org.apache.commons.attr=
ibutes.Indexed() is an unknown tag.<br class=3D"none"/>/jteam/build2/checko=
ut/spring/spring/src/org/springframework/web/servlet/mvc/multiaction/Parame=
terMethodNameResolver.java:119: warning - Tag @link: can't find defaultMeth=
odName in org.springframework.web.servlet.mvc.multiaction.ParameterMethodNa=
meResolver<br class=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/=
springframework/web/servlet/mvc/multiaction/ParameterMethodNameResolver.jav=
a:100: warning - Tag @link: can't find logicalMappings in org.springframewo=
rk.web.servlet.mvc.multiaction.ParameterMethodNameResolver<br class=3D"none=
"/>/jteam/build2/checkout/spring/spring/src/org/springframework/web/servlet=
/mvc/multiaction/ParameterMethodNameResolver.java:100: warning - Tag @link:=
can't find paramName in org.springframework.web.servlet.mvc.multiaction.Pa=
rameterMethodNameResolver<br class=3D"none"/>/jteam/build2/checkout/spring/=
spring/src/org/springframework/web/servlet/mvc/multiaction/ParameterMethodN=
ameResolver.java:100: warning - Tag @link: can't find logicalMappings in or=
g.springframework.web.servlet.mvc.multiaction.ParameterMethodNameResolver<b=
r class=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/springframew=
ork/web/servlet/mvc/multiaction/ParameterMethodNameResolver.java:100: warni=
ng - Tag @link: can't find paramName in org.springframework.web.servlet.mvc=
.multiaction.ParameterMethodNameResolver<br class=3D"none"/>/jteam/build2/c=
heckout/spring/spring/src/org/springframework/web/servlet/mvc/multiaction/P=
arameterMethodNameResolver.java:100: warning - Tag @link: can't find logica=
lMappings in org.springframework.web.servlet.mvc.multiaction.ParameterMetho=
dNameResolver<br class=3D"none"/>/jteam/build2/checkout/spring/spring/src/o=
rg/springframework/web/servlet/mvc/multiaction/ParameterMethodNameResolver.=
java:100: warning - Tag @link: can't find paramName in org.springframework.=
web.servlet.mvc.multiaction.ParameterMethodNameResolver<br class=3D"none"/>=
/jteam/build2/checkout/spring/spring/src/org/springframework/web/servlet/mv=
c/multiaction/ParameterMethodNameResolver.java:100: warning - Tag @link: ca=
n't find logicalMappings in org.springframework.web.servlet.mvc.multiaction=
.ParameterMethodNameResolver<br class=3D"none"/>/jteam/build2/checkout/spri=
ng/spring/src/org/springframework/web/servlet/mvc/multiaction/ParameterMeth=
odNameResolver.java:100: warning - Tag @link: can't find paramName in org.s=
pringframework.web.servlet.mvc.multiaction.ParameterMethodNameResolver<br c=
lass=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/springframework=
/web/servlet/mvc/multiaction/ParameterMethodNameResolver.java:100: warning =
- @param argument "an" is not a parameter name.<br class=3D"none"/>/jteam/b=
uild2/checkout/spring/spring/src/org/springframework/web/servlet/mvc/multia=
ction/ParameterMethodNameResolver.java:119: warning - Tag @link: can't find=
defaultMethodName in org.springframework.web.servlet.mvc.multiaction.Param=
eterMethodNameResolver<br class=3D"none"/>/jteam/build2/checkout/spring/spr=
ing/src/org/springframework/web/servlet/mvc/multiaction/ParameterMethodName=
Resolver.java:119: warning - Tag @link: can't find defaultMethodName in org=
.springframework.web.servlet.mvc.multiaction.ParameterMethodNameResolver<br=
class=3D"none"/>/jteam/build2/checkout/spring/spring/src/org/springframewo=
rk/web/servlet/mvc/multiaction/ParameterMethodNameResolver.java:119: warnin=
g - Tag @link: can't find defaultMethodName in org.springframework.web.serv=
let.mvc.multiaction.ParameterMethodNameResolver<br class=3D"none"/></pre></=
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"unittests-sectionheader"> =
Unit Tests: (2929) </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"> </td></tr><tr><td colspan=3D"4" cla=
ss=3D"unittests-sectionheader"> Unit Test Error De=
tails: (6) </td></tr><tr><td class=3D"unittests-data" c=
olspan=3D"2"> Test: testHelpPage</td></tr><tr><td class=
=3D"unittests-data" colspan=3D"2"> Class: 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: testPurchase</td></tr><tr><td class=3D"unittests-dat=
a" colspan=3D"2"> Class: 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: testSearch</td></tr><tr><td cl=
ass=3D"unittests-data" colspan=3D"2"> Class: 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: testHelpPage=
</td></tr><tr><td class=3D"unittests-data" colspan=3D"2"> Cl=
ass: 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: testPurchase</td></tr><tr><td=
class=3D"unittests-data" colspan=3D"2"> Class: 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: testSea=
rch</td></tr><tr><td class=3D"unittests-data" colspan=3D"2"> =
Class: 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"> </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"> =
Modifications since last build: =
(26) </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">test/org/springframework/jmx/=
AbstractJmxTests.java</td><td class=3D"modifications-data">properly clean u=
p all JMX resources</td></tr><tr class=3D"modifications-oddrow"><td class=
=3D"modifications-data">modified</td><td class=3D"modifications-data">jhoel=
ler</td><td class=3D"modifications-data">test/org/springframework/jmx/suppo=
rt/ConnectorServerFactoryBeanTests.java</td><td class=3D"modifications-data=
">properly clean up all JMX resources</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/jmx/support/ConnectorServerFactoryBean.java</td><td class=3D"modific=
ations-data">properly clean up all JMX resources</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/beans/factory/config/PropertyOverrideConfigurer.java</td=
><td class=3D"modifications-data">do not log invalid keys at WARN level in =
case of "ignoreInvalidKeys" (only at DEBUG)</td></tr><tr class=3D"modificat=
ions-evenrow"><td class=3D"modifications-data">modified</td><td class=3D"mo=
difications-data">jhoeller</td><td class=3D"modifications-data">lib/readme.=
txt</td><td class=3D"modifications-data">updated to CGLIB 2.1 final</td></t=
r><tr class=3D"modifications-oddrow"><td class=3D"modifications-data">delet=
ed</td><td class=3D"modifications-data">jhoeller</td><td class=3D"modificat=
ions-data">lib/cglib/cglib-nodep-2.1-dev.jar</td><td class=3D"modifications=
-data">updated to CGLIB 2.1 final</td></tr><tr class=3D"modifications-evenr=
ow"><td class=3D"modifications-data">added</td><td class=3D"modifications-d=
ata">jhoeller</td><td class=3D"modifications-data">lib/cglib/cglib-nodep-2.=
1.jar</td><td class=3D"modifications-data">updated to CGLIB 2.1 final</td><=
/tr><tr class=3D"modifications-oddrow"><td class=3D"modifications-data">mod=
ified</td><td class=3D"modifications-data">jhoeller</td><td class=3D"modifi=
cations-data">sandbox/src/org/springframework/jms/JmsConnectionFactoryBean.=
java</td><td class=3D"modifications-data">support Connection creation witho=
ut user credentials</td></tr><tr class=3D"modifications-evenrow"><td class=
=3D"modifications-data">modified</td><td class=3D"modifications-data">colin=
s</td><td class=3D"modifications-data">changelog.txt</td><td class=3D"modif=
ications-data">Enhance ParameterMethodNameResolver to also allow resolving =
method names based purely on the existence of a parameter (value ignored). =
Added unit test.</td></tr><tr class=3D"modifications-oddrow"><td class=3D"m=
odifications-data">modified</td><td class=3D"modifications-data">colins</td=
><td class=3D"modifications-data">src/org/springframework/web/servlet/mvc/m=
ultiaction/ParameterMethodNameResolver.java</td><td class=3D"modifications-=
data">Enhance ParameterMethodNameResolver to also allow resolving method na=
mes based purely on the existence of a parameter (value ignored). Added uni=
t test.</td></tr><tr class=3D"modifications-evenrow"><td class=3D"modificat=
ions-data">deleted</td><td class=3D"modifications-data">colins</td><td clas=
s=3D"modifications-data">src/org/springframework/web/servlet/mvc/multiactio=
n/ParameterNameMethodNameResolver.java</td><td class=3D"modifications-data"=
>Enhance ParameterMethodNameResolver to also allow resolving method names b=
ased purely on the existence of a parameter (value ignored). Added unit tes=
t.</td></tr><tr class=3D"modifications-oddrow"><td class=3D"modifications-d=
ata">modified</td><td class=3D"modifications-data">colins</td><td class=3D"=
modifications-data">changelog.txt</td><td class=3D"modifications-data">add =
ParameterNameMethodNameResolver</td></tr><tr class=3D"modifications-evenrow=
"><td class=3D"modifications-data">added</td><td class=3D"modifications-dat=
a">colins</td><td class=3D"modifications-data">src/org/springframework/web/=
servlet/mvc/multiaction/ParameterNameMethodNameResolver.java</td><td class=
=3D"modifications-data">add ParameterNameMethodNameResolver</td></tr><tr cl=
ass=3D"modifications-oddrow"><td class=3D"modifications-data">modified</td>=
<td class=3D"modifications-data">aarendsen</td><td class=3D"modifications-d=
ata">changelog.txt</td><td class=3D"modifications-data">* Addition of Bindi=
nggErrorProcessorSupport and default implementiations for PropertyAccessExc=
eptions and RequiredFieldErrors</td></tr><tr class=3D"modifications-evenrow=
"><td class=3D"modifications-data">modified</td><td class=3D"modifications-=
data">colins</td><td class=3D"modifications-data">src/org/springframework/c=
ontext/access/ContextSingletonBeanFactoryLocator.java</td><td class=3D"modi=
fications-data">SPR-719: try to work around SingletonBeanFactoryLocator rec=
ursion problem</td></tr><tr class=3D"modifications-oddrow"><td class=3D"mod=
ifications-data">modified</td><td class=3D"modifications-data">colins</td><=
td class=3D"modifications-data">src/org/springframework/beans/factory/acces=
s/SingletonBeanFactoryLocator.java</td><td class=3D"modifications-data">SPR=
-719: try to work around SingletonBeanFactoryLocator recursion problem</td>=
</tr><tr class=3D"modifications-evenrow"><td class=3D"modifications-data">a=
dded</td><td class=3D"modifications-data">aarendsen</td><td class=3D"modifi=
cations-data">src/org/springframework/validation/DefaultRequiredFieldErrorP=
rocessor.java</td><td class=3D"modifications-data">* Addition of BindinggEr=
rorProcessorSupport and default implementiations for PropertyAccessExceptio=
ns and RequiredFieldErrors</td></tr><tr class=3D"modifications-oddrow"><td =
class=3D"modifications-data">added</td><td class=3D"modifications-data">aar=
endsen</td><td class=3D"modifications-data">src/org/springframework/validat=
ion/PropertyAccessExceptionProcessor.java</td><td class=3D"modifications-da=
ta">* Addition of BindinggErrorProcessorSupport and default implementiation=
s for PropertyAccessExceptions and RequiredFieldErrors</td></tr><tr class=
=3D"modifications-evenrow"><td class=3D"modifications-data">added</td><td c=
lass=3D"modifications-data">aarendsen</td><td class=3D"modifications-data">=
src/org/springframework/validation/RequiredFieldErrorProcessor.java</td><td=
class=3D"modifications-data">* Addition of BindinggErrorProcessorSupport a=
nd default implementiations for PropertyAccessExceptions and RequiredFieldE=
rrors</td></tr><tr class=3D"modifications-oddrow"><td class=3D"modification=
s-data">modified</td><td class=3D"modifications-data">aarendsen</td><td cla=
ss=3D"modifications-data">src/org/springframework/validation/DataBinder.jav=
a</td><td class=3D"modifications-data">* Addition of BindinggErrorProcessor=
Support and default implementiations for PropertyAccessExceptions and Requi=
redFieldErrors</td></tr><tr class=3D"modifications-evenrow"><td class=3D"mo=
difications-data">added</td><td class=3D"modifications-data">aarendsen</td>=
<td class=3D"modifications-data">src/org/springframework/validation/Default=
PropertyAccessExceptionProcessor.java</td><td class=3D"modifications-data">=
* Addition of BindinggErrorProcessorSupport and default implementiations fo=
r PropertyAccessExceptions and RequiredFieldErrors</td></tr><tr class=3D"mo=
difications-oddrow"><td class=3D"modifications-data">modified</td><td class=
=3D"modifications-data">aarendsen</td><td class=3D"modifications-data">chan=
gelog.txt</td><td class=3D"modifications-data">* Fixed SPR-752, debug loggi=
ng for session attributes in form controller</td></tr><tr class=3D"modifica=
tions-evenrow"><td class=3D"modifications-data">modified</td><td class=3D"m=
odifications-data">aarendsen</td><td class=3D"modifications-data">src/org/s=
pringframework/web/servlet/mvc/AbstractWizardFormController.java</td><td cl=
ass=3D"modifications-data">* Fixed SPR-752, debug logging for session attri=
butes in form controller</td></tr><tr class=3D"modifications-oddrow"><td cl=
ass=3D"modifications-data">modified</td><td class=3D"modifications-data">aa=
rendsen</td><td class=3D"modifications-data">src/org/springframework/web/se=
rvlet/mvc/AbstractFormController.java</td><td class=3D"modifications-data">=
* Fixed SPR-752, debug logging for session attributes in form controller</t=
d></tr><tr class=3D"modifications-evenrow"><td class=3D"modifications-data"=
>modified</td><td class=3D"modifications-data">jhoeller</td><td class=3D"mo=
difications-data">src/org/springframework/transaction/interceptor/Attribute=
sTransactionAttributeSource.java</td><td class=3D"modifications-data">polis=
hing</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">src/org/springframework/metadata/Attributes.java</t=
d><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"> =
Deployments by this build: (17) </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><tr><td class=3D"distributables-data">Building war: /jteam/build2/ch=
eckout/spring/spring/autobuilds/apps/buildtest/dist/buildtest.war</td></tr>=
<tr class=3D"distributables-oddrow"><td class=3D"distributables-data">Build...
[truncated message content] |
|
From: Juergen H. <ju...@in...> - 2005-03-10 23:32:07
|
Thanks for the suggestion, Dan! I've prototypically added such an
AnnotationsSessionFactoryBean.
However, the Hibernate3 annotations jar is built with JDK 1.5, so we can
only build and ship this class if our build process switches to JDK 1.5
required too. We might switch to building with JDK 1.5 anyway, though, for
our new transaction annotation feature that we'd like to ship in Spring 1.2.
Juergen
-----Original Message-----
From: spr...@li...
[mailto:spr...@li...]On Behalf Of
Washusen, Dan
Sent: Thursday, March 10, 2005 7:09 AM
To: spr...@li...
Subject: RE: [Springframework-developer] Hibernate 3 annotations in 1.2
rc1
Incase anyone is interested; I've attached an implementation of the bean
definition I described below.
Cheers,
Dan
----------------------------------------------------------------------------
--
From: spr...@li...
[mailto:spr...@li...] On Behalf Of
Washusen, Dan
Sent: Wednesday, 9 March 2005 12:29 PM
To: spr...@li...
Subject: [Springframework-developer] Hibernate 3 annotations in 1.2 rc1
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.
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.
Pretty easy really.
A provided extension of LocalSessionFactoryBean that had support for
annotated classes would be nice. The bean definition could look something
like:
<bean id="sessionFactory"
class="org.springframework.orm.hibernate3.AnnotationsLocalSessionFactoryBean
">
<property name="dataSource">
<ref local="dataSource"/>
</property>
<property name="mappingPackage">
<value>some.package</value>
</property>
<property name="annotatedClasses">
<list>
<value>com.package.Foo</value>
<value>com.package.Bar</value>
</list>
</property>
</bean>
Cheers,
Dan
www.sensis.com.au
A leading Australian advertising, information
and directories business.
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]
www.sensis.com.au
A leading Australian advertising, information
and directories business.
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]
|
|
From: Colin S. <col...@ex...> - 2005-03-10 22:18:31
|
Matt Raible wrote: > > On Mar 10, 2005, at 3:04 PM, kat...@ho... wrote: > >> While on the topic, we should look at renaming the default parameter >> to something other than 'action'. This clashes with the form's >> 'action' in Javascript, and so is maybe not a good default. This >> would probably be OK as part of a 1.2 release. > > > +1, I'd recommend "method" or something. I've seen the same issue re: > JavaScript, forms and button names. Hmm, I kind of like the idea, but this would probably break exsiting apps that relied on the "action" default. They would not require a recompile, a config change to set the property back to "action" would do, but I'm a bit loath to break backwards compatibility in a .X release for something that's not a true bug. Even now people can alway rename the param name. Anybody else have an opinion on this? Colin |
|
From: Matt R. <li...@ra...> - 2005-03-10 22:10:29
|
On Mar 10, 2005, at 3:04 PM, kat...@ho... wrote: > While on the topic, we should look at renaming the default parameter > to something other than 'action'. This clashes with the form's > 'action' in Javascript, and so is maybe not a good default. This would > probably be OK as part of a 1.2 release. +1, I'd recommend "method" or something. I've seen the same issue re: JavaScript, forms and button names. |
|
From: Rod J. <ro...@in...> - 2005-03-10 22:10:06
|
> The main problem is where to get the transaction name from. I'm inclined to > extend our TransactionDefinition with a "getName" or "getDescription" > method, allowing to pass such a name in. TransactionInterceptor could > automatically specify class name plus method name there. Makes sense on any platform. |
|
From: Juergen H. <ju...@in...> - 2005-03-10 22:07:11
|
Good suggestion - dummy "user" and "password" properties added :-) Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...]On Behalf Of Seth Ladd Sent: Thursday, March 10, 2005 10:44 PM To: spr...@li... Subject: [Springframework-developer] Small Suggestion for JavaDocs on JotmFactoryBean Aloha, I'd like to suggest a small addition to the JotmFactoryBean's javadocs. The example given does not specify where to place the username and password properties. From my experience, they must be specified on the StandardXAPoolDataSource, instead of the StandardXADataSource. Let's place a dummy username and password in the example StandardXAPoolDataSource to help out future users. It would have saved me some time. :) 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> ------------------------------------------------------- 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 |
|
From: <kat...@ho...> - 2005-03-10 22:07:08
|
While on the topic, we should look at renaming the default parameter to something other than 'action'. This clashes with the form's 'action' in Javascript, and so is maybe not a good default. This would probably be OK as part of a 1.2 release. Colin Sampaleanu wrote: > Erwin, > > Actually I wrote the original support for handling image buttons for > flows, check out RequestParamNameToRequestAttributeFilter, which is > still in the sandbox... It's just a filter that maps param names to > name/value Request Attribute pairs, which the flow code would also > recognize. Of course the present approach is better. > > I agree about just combining the new code in > ParameterMethodNameResolver. I can't think of any real disadvantage, > although once in a while somebody might have to rename the default > 'action' parameter recognition to something else, if there's already an > unrelated 'action' paramter. I'll go ahead and do this. > > It probably does make sense to try to leverage the > 'searchForRequestParameter' code. Then image button support would come > in too. The only real disadvantage I can think of is that in the case > where you are using only the simple action=xxxx format, and want to rely > on the default method being hit (i.e. no match), then in that case > you're actually going to be expending extra cycles looping through all > request parameters to check for the 'logicalName_value = xyz' format as > well. This is really only a concern for the default method (other > methods would match the simpel parameter directly), so I don't know how > big a deal this is, but I guess it could be configurable actually as to > whether it supports the extended matching. > > Colin > > Erwin Vervaet wrote: > >> 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 |
|
From: Seth L. <set...@gm...> - 2005-03-10 21:44:14
|
Aloha, I'd like to suggest a small addition to the JotmFactoryBean's javadocs. The example given does not specify where to place the username and password properties. From my experience, they must be specified on the StandardXAPoolDataSource, instead of the StandardXADataSource. Let's place a dummy username and password in the example StandardXAPoolDataSource to help out future users. It would have saved me some time. :) 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> |
|
From: Abel P. <abl...@pa...> - 2005-03-10 21:33:21
|
Ben wrote: >So by 'JMS stuff' I take it you mean the org.springframework.jms >package? like the JmsTemplate, picture a JavaSpaceTemplate. >Have you been compiling any core support classes for general >Jini operations, e.g. service discovery/lookup, configuration >management, etc.? Nothing generic enough for use outside the scope of a JavaSpace. What I'm building now is more of a proof of concept, but eventually I plan to provide a set of general Jini usage support classes. >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. That would be ideal. - Abel -----Original Message----- From: spr...@li... [mailto:spr...@li...]On Behalf Of Ben Piper Sent: Wednesday, March 09, 2005 9:27 PM To: spr...@li... Subject: RE: [Springframework-developer] Spring remoting with Jini? 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. >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. 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. ------------------------------------------------------- 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_id396&op=ick _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Colin S. <col...@ex...> - 2005-03-10 21:15:21
|
I've added createBinder() and initBinder() methods to MultiActionController, similar to what exists already in BaseCommandController. Right now there's no easy way to add custom property editors to a MultiActionController. Note that there's still no way to set a custom MessageCodeResolver strategy such as available in BaseCommandController, to apply to the binder. That arguably should be added as well. Arguably, the whole MultiAction/MethodNameResolver concept needs to make its way into the BaseCommandController and subclasses in some fashion. When creating forms with multiple actions I've needed something similar, and handled dispatching by hand. I think what would perhaps work is to allow the properties to be set, but not to actually use them by default. That is, a subclass of BaseCommandController would have to manually invoke something like MultiActionController's invokeNamedMethod. For example, an AbstractFormController subclass would still override processFormSubmission or showForm as normal, but then as needed would be able to invoke something like invokeNamedMethod in those methods... Or it could manually get a resolved method, and use it as a command name, etc. Colin |
|
From: Dmitriy K. <dko...@ru...> - 2005-03-10 20:48:28
|
+1. I see it as a useful feature (to be able to identify TXs by name) for Weblogic users. Dmitriy. Juergen Hoeller wrote: >There's an interesting suggestion (by Bart Strubbe) regarding WebLogic's >transaction monitor: > >http://forum.springframework.org/viewtopic.php?t=3981 > >Essentially, WebLogic's transaction monitor seems to use "transaction names" >for monitoring and logging purposes. WebLogic's EJB container automatically >leverages this facility. The API to set such a transaction name is >WebLogic-specific; we could add support for it to our >WebLogicJtaTransactionManager. > >The main problem is where to get the transaction name from. I'm inclined to >extend our TransactionDefinition with a "getName" or "getDescription" >method, allowing to pass such a name in. TransactionInterceptor could >automatically specify class name plus method name there. > >Thoughts? > >Juergen > > > >------------------------------------------------------- >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 > > |
|
From: Colin S. <col...@ex...> - 2005-03-10 20:24:45
|
Unfortunately it's not that simple. I don't have the file to delete. It's something in the attic presumably (I get the infamous: cvs update: nothing known about test/org/springframework/web/servlet/mvc/multiaction/ParameterMethodNameResolverTests.java error when I do an update), and I can't see the Attic or any other part of the actual CVS filessytem, at SF. So there's nothing to delete, and I can't check in a new file by that name. Colin Erwin Vervaet wrote: > Making it configurable would be good. Keith actually mentioned he > noticed degraded performance with the extensive search, although that > seems unlikely unless you have a very large amount of request > parameters :-) > > > Erwin Vervaet > erw...@er... > ----- Original Message ----- From: "Colin Sampaleanu" <col...@ex...> > To: <spr...@li...> > Sent: Thursday, March 10, 2005 3:51 PM > Subject: Re: [Springframework-developer] ParameterNameMethodNameResolver > > >> Erwin, >> >> Actually I wrote the original support for handling image buttons for >> flows, check out RequestParamNameToRequestAttributeFilter, which is >> still in the sandbox... It's just a filter that maps param names to >> name/value Request Attribute pairs, which the flow code would also >> recognize. Of course the present approach is better. >> >> I agree about just combining the new code in >> ParameterMethodNameResolver. I can't think of any real disadvantage, >> although once in a while somebody might have to rename the default >> 'action' parameter recognition to something else, if there's already >> an unrelated 'action' paramter. I'll go ahead and do this. >> >> It probably does make sense to try to leverage the >> 'searchForRequestParameter' code. Then image button support would >> come in too. The only real disadvantage I can think of is that in the >> case where you are using only the simple action=xxxx format, and want >> to rely on the default method being hit (i.e. no match), then in that >> case you're actually going to be expending extra cycles looping >> through all request parameters to check for the 'logicalName_value = >> xyz' format as well. This is really only a concern for the default >> method (other methods would match the simpel parameter directly), so >> I don't know how big a deal this is, but I guess it could be >> configurable actually as to whether it supports the extended matching. >> >> Colin >> >> Erwin Vervaet wrote: >> >>> 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 >> >> > > > > ------------------------------------------------------- > 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 |
|
From: Erwin V. <erw...@er...> - 2005-03-10 20:10:21
|
To fix the CVS case-sensitive delete: first commit the delete of the file, then commit the renamed version (do both commits seperately). Erwin Vervaet erw...@er... ----- Original Message ----- From: "Colin Sampaleanu" <col...@ex...> To: <spr...@li...> Sent: Thursday, March 10, 2005 7:25 PM Subject: Re: [Springframework-developer] ParameterNameMethodNameResolver > I've moved the new code into ParameterMethodNameResolver, and killed > ParameterNameMethodNameResolver. Unfortunately I had to name the new test > class (there were no tests for the existing ParameterMethodNameResolver) > as ParameterMethodNameResolverTest and not our standard > ParameterMethodNameResolverTests, as the latter had some sort of conflict > based on there apparently already being some sort of deleted file in CVS > with the same name but differering only in case. > > I did not go ahead and try to use the 'searchForRequestParameter' code. Do > we all agree that it makes sense to pull that code from the sandbox, and > move it into WebUtils, and then use it here? Doing so would allow the > method resolver to also work with image buttons. > > Colin > > Colin Sampaleanu wrote: > >> Erwin, >> >> Actually I wrote the original support for handling image buttons for >> flows, check out RequestParamNameToRequestAttributeFilter, which is still >> in the sandbox... It's just a filter that maps param names to name/value >> Request Attribute pairs, which the flow code would also recognize. Of >> course the present approach is better. >> >> I agree about just combining the new code in ParameterMethodNameResolver. >> I can't think of any real disadvantage, although once in a while somebody >> might have to rename the default 'action' parameter recognition to >> something else, if there's already an unrelated 'action' paramter. I'll >> go ahead and do this. >> >> It probably does make sense to try to leverage the >> 'searchForRequestParameter' code. Then image button support would come in >> too. The only real disadvantage I can think of is that in the case where >> you are using only the simple action=xxxx format, and want to rely on the >> default method being hit (i.e. no match), then in that case you're >> actually going to be expending extra cycles looping through all request >> parameters to check for the 'logicalName_value = xyz' format as well. >> This is really only a concern for the default method (other methods would >> match the simpel parameter directly), so I don't know how big a deal this >> is, but I guess it could be configurable actually as to whether it >> supports the extended matching. >> >> Colin >> >> Erwin Vervaet wrote: >> >>> 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 > > |
|
From: Erwin V. <erw...@er...> - 2005-03-10 20:07:49
|
Making it configurable would be good. Keith actually mentioned he noticed degraded performance with the extensive search, although that seems unlikely unless you have a very large amount of request parameters :-) Erwin Vervaet erw...@er... ----- Original Message ----- From: "Colin Sampaleanu" <col...@ex...> To: <spr...@li...> Sent: Thursday, March 10, 2005 3:51 PM Subject: Re: [Springframework-developer] ParameterNameMethodNameResolver > Erwin, > > Actually I wrote the original support for handling image buttons for > flows, check out RequestParamNameToRequestAttributeFilter, which is still > in the sandbox... It's just a filter that maps param names to name/value > Request Attribute pairs, which the flow code would also recognize. Of > course the present approach is better. > > I agree about just combining the new code in ParameterMethodNameResolver. > I can't think of any real disadvantage, although once in a while somebody > might have to rename the default 'action' parameter recognition to > something else, if there's already an unrelated 'action' paramter. I'll go > ahead and do this. > > It probably does make sense to try to leverage the > 'searchForRequestParameter' code. Then image button support would come in > too. The only real disadvantage I can think of is that in the case where > you are using only the simple action=xxxx format, and want to rely on the > default method being hit (i.e. no match), then in that case you're > actually going to be expending extra cycles looping through all request > parameters to check for the 'logicalName_value = xyz' format as well. This > is really only a concern for the default method (other methods would match > the simpel parameter directly), so I don't know how big a deal this is, > but I guess it could be configurable actually as to whether it supports > the extended matching. > > Colin > > Erwin Vervaet wrote: > >> 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 > > |
|
From: Juergen H. <ju...@in...> - 2005-03-10 20:00:52
|
There's an interesting suggestion (by Bart Strubbe) regarding WebLogic's transaction monitor: http://forum.springframework.org/viewtopic.php?t=3981 Essentially, WebLogic's transaction monitor seems to use "transaction names" for monitoring and logging purposes. WebLogic's EJB container automatically leverages this facility. The API to set such a transaction name is WebLogic-specific; we could add support for it to our WebLogicJtaTransactionManager. The main problem is where to get the transaction name from. I'm inclined to extend our TransactionDefinition with a "getName" or "getDescription" method, allowing to pass such a name in. TransactionInterceptor could automatically specify class name plus method name there. Thoughts? Juergen |
|
From: Colin S. <col...@ex...> - 2005-03-10 18:31:50
|
Note btw that I've change the logic of the code a bit. There is the old ability to declare a paramter (default is 'action') whose value is the method name. Then you can declare a simple list (as a String array) of parameter names, which are treated such that (on a first match basis) if a parameter exists, that is the method name. Then there is also an optional logicalMappings Properties property that can be set, which can be used to treat the method name as logical name, and map it to the 'real' name. This allows the person configuring the controller to completely decouple the method name from that specified by the JSP page (or other browser based code sending in the request). Colin Sampaleanu wrote: > I've moved the new code into ParameterMethodNameResolver, and killed > ParameterNameMethodNameResolver. Unfortunately I had to name the new > test class (there were no tests for the existing > ParameterMethodNameResolver) as ParameterMethodNameResolverTest and > not our standard ParameterMethodNameResolverTests, as the latter had > some sort of conflict based on there apparently already being some > sort of deleted file in CVS with the same name but differering only in > case. > > I did not go ahead and try to use the 'searchForRequestParameter' > code. Do we all agree that it makes sense to pull that code from the > sandbox, and move it into WebUtils, and then use it here? Doing so > would allow the method resolver to also work with image buttons. > > Colin > > Colin Sampaleanu wrote: > >> Erwin, >> >> Actually I wrote the original support for handling image buttons for >> flows, check out RequestParamNameToRequestAttributeFilter, which is >> still in the sandbox... It's just a filter that maps param names to >> name/value Request Attribute pairs, which the flow code would also >> recognize. Of course the present approach is better. >> >> I agree about just combining the new code in >> ParameterMethodNameResolver. I can't think of any real disadvantage, >> although once in a while somebody might have to rename the default >> 'action' parameter recognition to something else, if there's already >> an unrelated 'action' paramter. I'll go ahead and do this. >> >> It probably does make sense to try to leverage the >> 'searchForRequestParameter' code. Then image button support would >> come in too. The only real disadvantage I can think of is that in the >> case where you are using only the simple action=xxxx format, and want >> to rely on the default method being hit (i.e. no match), then in that >> case you're actually going to be expending extra cycles looping >> through all request parameters to check for the 'logicalName_value = >> xyz' format as well. This is really only a concern for the default >> method (other methods would match the simpel parameter directly), so >> I don't know how big a deal this is, but I guess it could be >> configurable actually as to whether it supports the extended matching. >> >> Colin >> >> Erwin Vervaet wrote: >> >>> 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 >>> >>> > > |
|
From: Colin S. <col...@ex...> - 2005-03-10 18:26:08
|
I've moved the new code into ParameterMethodNameResolver, and killed ParameterNameMethodNameResolver. Unfortunately I had to name the new test class (there were no tests for the existing ParameterMethodNameResolver) as ParameterMethodNameResolverTest and not our standard ParameterMethodNameResolverTests, as the latter had some sort of conflict based on there apparently already being some sort of deleted file in CVS with the same name but differering only in case. I did not go ahead and try to use the 'searchForRequestParameter' code. Do we all agree that it makes sense to pull that code from the sandbox, and move it into WebUtils, and then use it here? Doing so would allow the method resolver to also work with image buttons. Colin Colin Sampaleanu wrote: > Erwin, > > Actually I wrote the original support for handling image buttons for > flows, check out RequestParamNameToRequestAttributeFilter, which is > still in the sandbox... It's just a filter that maps param names to > name/value Request Attribute pairs, which the flow code would also > recognize. Of course the present approach is better. > > I agree about just combining the new code in > ParameterMethodNameResolver. I can't think of any real disadvantage, > although once in a while somebody might have to rename the default > 'action' parameter recognition to something else, if there's already > an unrelated 'action' paramter. I'll go ahead and do this. > > It probably does make sense to try to leverage the > 'searchForRequestParameter' code. Then image button support would come > in too. The only real disadvantage I can think of is that in the case > where you are using only the simple action=xxxx format, and want to > rely on the default method being hit (i.e. no match), then in that > case you're actually going to be expending extra cycles looping > through all request parameters to check for the 'logicalName_value = > xyz' format as well. This is really only a concern for the default > method (other methods would match the simpel parameter directly), so I > don't know how big a deal this is, but I guess it could be > configurable actually as to whether it supports the extended matching. > > Colin > > Erwin Vervaet wrote: > >> 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 >> |
|
From: Seth L. <set...@gm...> - 2005-03-10 18:18:58
|
On Thu, 10 Mar 2005 09:00:17 +0100, Steven Devijver <ste...@gm...> wrote: > 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. Two things: Jini is not asynchronous by nature. In fact, it's neither. Jini supports remote Events (asynchronous) and regular RPC synchronous semantics. It depends on how you implement your service. Jini's standard remote proxies work almost identically like standard RMI proxies. So it's a nature fit with Spring's existing remoting support, and remote client support. Also, check out the JMS sandbox. There is some code in there to treat JMS just like a Spring remote exportable service. I haven't played with the code yet, but it sounds like what you're looking for. I actually think Jini integration would be a great addition for Spring. Spring hides all the complexity of exporting services, and consuming services. Spring uses interfaces a lot, and so does Jini. Spring's ApplicationContext has Events, and so does Jini. If I can remove yet another config line and use Jini's automated lookup and service registration, all the better! :) 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> |
|
From: Colin S. <col...@ex...> - 2005-03-10 14:51:17
|
Erwin, Actually I wrote the original support for handling image buttons for flows, check out RequestParamNameToRequestAttributeFilter, which is still in the sandbox... It's just a filter that maps param names to name/value Request Attribute pairs, which the flow code would also recognize. Of course the present approach is better. I agree about just combining the new code in ParameterMethodNameResolver. I can't think of any real disadvantage, although once in a while somebody might have to rename the default 'action' parameter recognition to something else, if there's already an unrelated 'action' paramter. I'll go ahead and do this. It probably does make sense to try to leverage the 'searchForRequestParameter' code. Then image button support would come in too. The only real disadvantage I can think of is that in the case where you are using only the simple action=xxxx format, and want to rely on the default method being hit (i.e. no match), then in that case you're actually going to be expending extra cycles looping through all request parameters to check for the 'logicalName_value = xyz' format as well. This is really only a concern for the default method (other methods would match the simpel parameter directly), so I don't know how big a deal this is, but I guess it could be configurable actually as to whether it supports the extended matching. Colin Erwin Vervaet wrote: > 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 > |
1239 messages has been excluded from this view by a project administrator.
