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: <jue...@we...> - 2004-12-09 12:41:43
|
I'm surprised ;-) =20 I'll commit the overloaded "getMessage" methods on RequestContext in a = second. =20 Juergen =20 ________________________________ Von: spr...@li... im Auftrag = von Darren Davison Gesendet: Do 09.12.2004 13:36 An: spr...@li... Betreff: Re: [Springframework-developer] MessageSource - methods to take = 'args' as List On Thu, December 9, 2004 12:18, j=FCrgen h=F6ller [werk3AT] said: > Does Velocity automatically detect the > correct overloaded version of the "getMessage" method, that is, the = one with > the List argument rather than the one with the array argument? indeed it does :) -- Darren Davison Public Key: #DD356B0D ------------------------------------------------------- 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://productguide.itmanagersjournal.com/ _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Darren D. <da...@da...> - 2004-12-09 12:36:28
|
On Thu, December 9, 2004 12:18, j=FCrgen h=F6ller [werk3AT] said: > Does Velocity automatically detect the > correct overloaded version of the "getMessage" method, that is, the one= with > the List argument rather than the one with the array argument? indeed it does :) --=20 Darren Davison Public Key: #DD356B0D |
|
From: <jue...@we...> - 2004-12-09 12:16:08
|
I guess it would be sufficient to add such convenience methods with a =
List argument to the RequestContext class. Does Velocity automatically =
detect the correct overloaded version of the "getMessage" method, that =
is, the one with the List argument rather than the one with the array =
argument?
=20
Juergen
=20
________________________________
Von: spr...@li... im Auftrag =
von Darren Davison
Gesendet: Do 09.12.2004 12:35
An: spr...@li...
Betreff: [Springframework-developer] MessageSource - methods to take =
'args' as List
Is there any possibility to add methods to MessageSource types that =
accept a
List of args in place of the Object[] ? They could just defer to the =
existing
methods in default implementations..
public final String getMessage(String code, List args, String =
defaultMessage,
Locale locale) {
return getMessage(code, args.toArray(), defaultMessage, locale);
}
public final String getMessage(String code, List args, Locale locale) {
return getMessage(code, args.toArray(), locale);
}
The use case is that I can't create an Object[] from Velocity templates, =
but I
can create an ArrayList..
$rc.getMessage("msg.code", ["Param1", "Param2"], "default message")
^^^^^^^^^^^^^^^^^^^^
Velocity creates ArrayList here ..^
--
Darren Davison
Public Key: #DD356B0D
-------------------------------------------------------
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://productguide.itmanagersjournal.com/
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer
|
|
From: Darren D. <da...@da...> - 2004-12-09 11:35:56
|
Is there any possibility to add methods to MessageSource types that accep=
t a
List of args in place of the Object[] ? They could just defer to the exi=
sting
methods in default implementations..
public final String getMessage(String code, List args, String defaultMess=
age,
Locale locale) {
return getMessage(code, args.toArray(), defaultMessage, locale);
}
public final String getMessage(String code, List args, Locale locale) {
return getMessage(code, args.toArray(), locale);
}
The use case is that I can't create an Object[] from Velocity templates, =
but I
can create an ArrayList..
$rc.getMessage("msg.code", ["Param1", "Param2"], "default message")
^^^^^^^^^^^^^^^^^^^^
Velocity creates ArrayList here ..^
--=20
Darren Davison
Public Key: #DD356B0D
|
|
From: <jue...@we...> - 2004-12-09 10:24:18
|
Actually, there seems to be a pretty straightforward solution: I've = added a check whether there is a SessionHolder bound to the current = thread, only invoking "unbindResource" if found. Else, the SessionHolder = is simply left bound to the thread: It's empty anyway, as the = synchronization code will have removed and closed the transactional = Session. The next data access operation on that thread will simply reuse = the same SessionHolder, adding a new Hibernate Session to it. =20 I've attached a refined version of SessionFactoryUtils.java to the JIRA = issue. Juergen =20 ________________________________ Von: spr...@li... im Auftrag = von j=FCrgen h=F6ller [werk3AT] Gesendet: Do 09.12.2004 10:45 An: spr...@li... Betreff: [Springframework-developer] Spring JTA synchronization in a = remote transaction propagation scenario Does someone have experience with using Spring's JTA synchronization, in = particular the Hibernate Session synchronization, in a remote = transaction propagation scenario? That is, one server starts and ends = the transaction but the actual data access happens on other servers that = participate in the transaction. The problem is that the synchronization callbacks get executed on each = server, but in a different thread than the one that performed the data = access (triggered by JTA commit, which sends a remote call to each = participating server to execute the synchronizations). So Spring's = synchronization implementation can't find the thread-bound Hibernate = Session anymore, which leads to an IllegalStateException. Have a look at the corresponding JIRA issue: http://opensource.atlassian.com/projects/spring/browse/SPR-532 Any input is greatly appreciated! 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://productguide.itmanagersjournal.com/ _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: <jue...@we...> - 2004-12-09 09:41:39
|
Does someone have experience with using Spring's JTA synchronization, in = particular the Hibernate Session synchronization, in a remote = transaction propagation scenario? That is, one server starts and ends = the transaction but the actual data access happens on other servers that = participate in the transaction. The problem is that the synchronization callbacks get executed on each = server, but in a different thread than the one that performed the data = access (triggered by JTA commit, which sends a remote call to each = participating server to execute the synchronizations). So Spring's = synchronization implementation can't find the thread-bound Hibernate = Session anymore, which leads to an IllegalStateException. Have a look at the corresponding JIRA issue: http://opensource.atlassian.com/projects/spring/browse/SPR-532 Any input is greatly appreciated! =20 Juergen |
|
From: Nick L. <nic...@es...> - 2004-12-09 04:51:28
|
Portlet support (in the sandbox) has been fairly stable for the past couple of months. I've been finding it works well and I think a few other people have used it successfully, too. What would be involved in moving it out of the sandbox (Post 1.1.3)? I'm happy to help with updating docs/build files, etc. Nick Lothian |
|
From: <al...@jt...> - 2004-12-08 23:41:34
|
<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.167</td></tr><tr><td class=3D"header-data"><span class=
=3D"header-label">Date of build: </span>12/09/2004 00:16:50</td></tr><=
tr><td class=3D"header-data"><span class=3D"header-label">Time to build:&nb=
sp;</span>22 minutes 23 seconds</td></tr><tr><td class=3D"header-data"><spa=
n class=3D"header-label">Last changed: </span>12/08/2004 18:22:13</td>=
</tr><tr><td class=3D"header-data"><span class=3D"header-label">Last log en=
try: </span>polishing</td></tr></table><p>
<p>
<p>
<table xmlns=3D"http://www.w3.org/TR/html4/strict.dtd" width=3D"98%" border=
=3D"0" cellspacing=3D"0" cellpadding=3D"2" align=3D"center"><tr><td class=
=3D"compile-sectionheader"> Errors/Warnings: (=
6) </td></tr><tr><td><pre class=3D"compile-data">Note: S=
ome input files use or override a deprecated API.<br class=3D"none"/>Note: =
Recompile with -deprecation for details.<br class=3D"none"/>Note: /jteam/bu=
ild2/checkout/spring/spring/mock/org/springframework/mock/web/MockHttpSessi=
on.java uses or overrides a deprecated API.<br class=3D"none"/>Note: Recomp=
ile with -deprecation for details.<br class=3D"none"/>Note: Some input file=
s use or override a deprecated API.<br class=3D"none"/>Note: Recompile with=
-deprecation for details.<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: (26) </td></tr><tr><td><pre class=3D"compile-data=
">/jteam/build2/checkout/spring/spring/src/org/springframework/jdbc/support=
/lob/OracleLobHandler.java:76: warning - Tag @see: reference not found: ora=
cle.sql.BLOB<br/>/jteam/build2/checkout/spring/spring/src/org/springframewo=
rk/jdbc/support/lob/OracleLobHandler.java:76: warning - Tag @see: reference=
not found: oracle.sql.CLOB<br/>/jteam/build2/checkout/spring/spring/src/or=
g/springframework/jdbc/support/lob/OracleLobHandler.java:115: warning - Tag=
@see: reference not found: oracle.sql.BLOB#DURATION_SESSION<br/>/jteam/bui=
ld2/checkout/spring/spring/src/org/springframework/jdbc/support/lob/OracleL=
obHandler.java:115: warning - Tag @see: reference not found: oracle.sql.BLO=
B#MODE_READWRITE<br/>/jteam/build2/checkout/spring/spring/src/org/springfra=
mework/jdbc/support/lob/OracleLobHandler.java:115: warning - Tag @see: refe=
rence not found: oracle.sql.CLOB#DURATION_SESSION<br/>/jteam/build2/checkou=
t/spring/spring/src/org/springframework/jdbc/support/lob/OracleLobHandler.j=
ava:115: warning - Tag @see: reference not found: oracle.sql.CLOB#MODE_READ=
WRITE<br/>/jteam/build2/checkout/spring/spring/src/org/springframework/jdbc=
/support/lob/OracleLobHandler.java:154: warning - Tag @see: reference not f=
ound: oracle.jdbc.OracleConnection<br/>/jteam/build2/checkout/spring/spring=
/src/org/springframework/jdbc/support/lob/OracleLobHandler.java:164: warnin=
g - Tag @see: reference not found: oracle.sql.BLOB#createTemporary<br/>/jte=
am/build2/checkout/spring/spring/src/org/springframework/jdbc/support/lob/O=
racleLobHandler.java:164: warning - Tag @see: reference not found: oracle.s=
ql.CLOB#createTemporary<br/>/jteam/build2/checkout/spring/spring/src/org/sp=
ringframework/jdbc/support/nativejdbc/JBossNativeJdbcExtractor.java:49: war=
ning - Tag @see: reference not found: org.jboss.resource.adapter.jdbc.Wrapp=
edConnection#getUnderlyingConnection<br/>/jteam/build2/checkout/spring/spri=
ng/src/org/springframework/jdbc/support/nativejdbc/JBossNativeJdbcExtractor=
.java:49: warning - Tag @see: reference not found: org.jboss.resource.adapt=
er.jdbc.WrappedStatement#getUnderlyingStatement<br/>/jteam/build2/checkout/=
spring/spring/src/org/springframework/jdbc/support/nativejdbc/JBossNativeJd=
bcExtractor.java:49: warning - Tag @see: reference not found: org.jboss.res=
ource.adapter.jdbc.WrappedResultSet#getUnderlyingResultSet<br/>/jteam/build=
2/checkout/spring/spring/src/org/springframework/jdbc/support/nativejdbc/We=
bLogicNativeJdbcExtractor.java:45: warning - Tag @see: reference not found:=
weblogic.jdbc.extensions.WLConnection#getVendorConnection<br/>/jteam/build=
2/checkout/spring/spring/src/org/springframework/jdbc/support/nativejdbc/We=
bSphereNativeJdbcExtractor.java:34: warning - Tag @see: reference not found=
: com.ibm.ws.rsadapter.jdbc.WSJdbcConnection<br/>/jteam/build2/checkout/spr=
ing/spring/src/org/springframework/jdbc/support/nativejdbc/WebSphereNativeJ=
dbcExtractor.java:34: warning - Tag @see: reference not found: com.ibm.ws.r=
sadapter.jdbc.WSJdbcUtil#getNativeConnection<br/>/jteam/build2/checkout/spr=
ing/spring/src/org/springframework/jdbc/support/nativejdbc/WebSphereNativeJ=
dbcExtractor.java:34: warning - Tag @see: reference not found: com.ibm.ejs.=
cm.proxy.ConnectionProxy#getPhysicalConnection<br/>/jteam/build2/checkout/s=
pring/spring/src/org/springframework/orm/ibatis/SqlMapClientFactoryBean.jav=
a:170: warning - Tag @see: reference not found: com.ibatis.sqlmap.engine.tr=
ansaction.jdbc.JdbcTransactionConfig<br/>/jteam/build2/checkout/spring/spri=
ng/src/org/springframework/orm/ibatis/SqlMapClientFactoryBean.java:170: war=
ning - Tag @see: reference not found: com.ibatis.sqlmap.engine.transaction.=
jta.JtaTransactionConfig<br/>/jteam/build2/checkout/spring/spring/src/org/s=
pringframework/orm/ibatis/SqlMapClientFactoryBean.java:198: warning - Tag @=
see: reference not found: com.ibatis.sqlmap.engine.transaction.jdbc.JdbcTra=
nsactionConfig<br/>/jteam/build2/checkout/spring/spring/src/org/springframe=
work/orm/ibatis/SqlMapClientFactoryBean.java:198: warning - Tag @see: refer=
ence not found: com.ibatis.sqlmap.engine.transaction.jta.JtaTransactionConf=
ig<br/>/jteam/build2/checkout/spring/spring/src/org/springframework/transac=
tion/jta/WebLogicJtaTransactionManager.java:67: warning - Tag @see: referen=
ce not found: weblogic.transaction.TransactionManager#forceResume<br/>/jtea=
m/build2/checkout/spring/spring/src/org/springframework/transaction/jta/Web=
LogicServerTransactionManagerFactoryBean.java:45: warning - Tag @see: refer=
ence not found: weblogic.transaction.TxHelper#getTransactionManager<br/>/jt=
eam/build2/checkout/spring/spring/src/org/springframework/transaction/jta/W=
ebSphereTransactionManagerFactoryBean.java:47: warning - Tag @see: referenc=
e not found: com.ibm.ws.Transaction.TransactionManagerFactory#getTransactio=
nManager<br/>/jteam/build2/checkout/spring/spring/src/org/springframework/t=
ransaction/jta/WebSphereTransactionManagerFactoryBean.java:47: warning - Ta=
g @see: reference not found: com.ibm.ejs.jts.jta.JTSXA#getTransactionManage=
r<br/>/jteam/build2/checkout/spring/spring/src/org/springframework/transact=
ion/jta/WebSphereTransactionManagerFactoryBean.java:47: warning - Tag @see:=
reference not found: com.ibm.ejs.jts.jta.TransactionManagerFactory#getTran=
sactionManager<br/>/jteam/build2/checkout/spring/spring/src/org/springframe=
work/web/servlet/handler/metadata/PathMap.java:31: warning - @@org.apache.c=
ommons.attributes.Indexed() is an unknown tag.<br/></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: (2073) </td></tr><tr><td class=
=3D"unittests-data" colspan=3D"2"> All Tests Pas=
sed </td></tr><tr><td><table width=3D"98%" border=3D=
"0" cellspacing=3D"0" cellpadding=3D"2" align=3D"center"></table></td></tr>=
<tr></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: =
(46) </td></tr><tr class=3D"modifications-evenrow"><td =
class=3D"modifications-data">modified</td><td class=3D"modifications-data">=
jhoeller</td><td class=3D"modifications-data">src/org/springframework/aop/f=
ramework/adapter/AfterReturningAdviceInterceptor.java</td><td class=3D"modi=
fications-data">polishing</td></tr><tr class=3D"modifications-oddrow"><td c=
lass=3D"modifications-data">modified</td><td class=3D"modifications-data">j=
hoeller</td><td class=3D"modifications-data">src/org/springframework/aop/Me=
thodBeforeAdvice.java</td><td class=3D"modifications-data">polishing</td></=
tr><tr class=3D"modifications-evenrow"><td class=3D"modifications-data">mod=
ified</td><td class=3D"modifications-data">jhoeller</td><td class=3D"modifi=
cations-data">src/org/springframework/validation/ValidationUtils.java</td><=
td class=3D"modifications-data">improved javadoc</td></tr><tr class=3D"modi=
fications-oddrow"><td class=3D"modifications-data">modified</td><td class=
=3D"modifications-data">jhoeller</td><td class=3D"modifications-data">src/o=
rg/springframework/web/servlet/mvc/Controller.java</td><td class=3D"modific=
ations-data">improved javadoc</td></tr><tr class=3D"modifications-evenrow">=
<td class=3D"modifications-data">modified</td><td class=3D"modifications-da=
ta">jhoeller</td><td class=3D"modifications-data">src/org/springframework/a=
op/AfterReturningAdvice.java</td><td class=3D"modifications-data">improved =
javadoc</td></tr><tr class=3D"modifications-oddrow"><td class=3D"modificati=
ons-data">modified</td><td class=3D"modifications-data">jhoeller</td><td cl=
ass=3D"modifications-data">src/org/springframework/aop/framework/AdvisedSup=
portListener.java</td><td class=3D"modifications-data">improved javadoc</td=
></tr><tr class=3D"modifications-evenrow"><td class=3D"modifications-data">=
modified</td><td class=3D"modifications-data">jhoeller</td><td class=3D"mod=
ifications-data">src/org/springframework/aop/support/DefaultIntroductionAdv=
isor.java</td><td class=3D"modifications-data">added serialVersionUID from =
Spring 1.1</td></tr><tr class=3D"modifications-oddrow"><td class=3D"modific=
ations-data">modified</td><td class=3D"modifications-data">robharrop</td><t=
d class=3D"modifications-data">changelog.txt</td><td class=3D"modifications=
-data">Updated changelog</td></tr><tr class=3D"modifications-evenrow"><td c=
lass=3D"modifications-data">modified</td><td class=3D"modifications-data">j=
hoeller</td><td class=3D"modifications-data">src/org/springframework/web/se=
rvlet/FrameworkServlet.java</td><td class=3D"modifications-data">refined st=
artup logging, use StringUtils' "tokenizeToStringArray(str,delim)"</td></tr=
><tr class=3D"modifications-oddrow"><td class=3D"modifications-data">modifi=
ed</td><td class=3D"modifications-data">jhoeller</td><td class=3D"modificat=
ions-data">src/org/springframework/web/struts/ContextLoaderPlugIn.java</td>=
<td class=3D"modifications-data">refined startup logging, use StringUtils' =
"tokenizeToStringArray(str,delim)"</td></tr><tr class=3D"modifications-even=
row"><td class=3D"modifications-data">modified</td><td class=3D"modificatio=
ns-data">jhoeller</td><td class=3D"modifications-data">src/org/springframew=
ork/web/context/ContextLoader.java</td><td class=3D"modifications-data">ref=
ined startup logging, use StringUtils' "tokenizeToStringArray(str,delim)"</=
td></tr><tr class=3D"modifications-oddrow"><td class=3D"modifications-data"=
>modified</td><td class=3D"modifications-data">jhoeller</td><td class=3D"mo=
difications-data">src/org/springframework/beans/factory/access/JndiBeanFact=
oryLocator.java</td><td class=3D"modifications-data">added "tokenizeToStrin=
gArray(str,delim)" method to StringUtils</td></tr><tr class=3D"modification=
s-evenrow"><td class=3D"modifications-data">modified</td><td class=3D"modif=
ications-data">jhoeller</td><td class=3D"modifications-data">src/org/spring=
framework/util/StringUtils.java</td><td class=3D"modifications-data">added =
"tokenizeToStringArray(str,delim)" method to StringUtils</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/web/servlet/ResourceServlet.java</td><td class=3D"=
modifications-data">added "tokenizeToStringArray(str,delim)" method to Stri=
ngUtils</td></tr><tr class=3D"modifications-evenrow"><td class=3D"modificat=
ions-data">modified</td><td class=3D"modifications-data">jhoeller</td><td c=
lass=3D"modifications-data">src/org/springframework/beans/factory/xml/Defau=
ltXmlBeanDefinitionParser.java</td><td class=3D"modifications-data">added "=
tokenizeToStringArray(str,delim)" method to StringUtils</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/beans/factory/ListableBeanFactory.java</td><td cla=
ss=3D"modifications-data">improved javadoc</td></tr><tr class=3D"modificati=
ons-evenrow"><td class=3D"modifications-data">modified</td><td class=3D"mod=
ifications-data">jhoeller</td><td class=3D"modifications-data">src/org/spri=
ngframework/beans/factory/BeanFactoryUtils.java</td><td class=3D"modificati=
ons-data">improved javadoc</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/beans=
/factory/config/BeanDefinition.java</td><td class=3D"modifications-data">im=
proved javadoc</td></tr><tr class=3D"modifications-evenrow"><td class=3D"mo=
difications-data">modified</td><td class=3D"modifications-data">jhoeller</t=
d><td class=3D"modifications-data">src/org/springframework/beans/factory/su=
pport/AbstractBeanFactory.java</td><td class=3D"modifications-data">moved m=
anagement of ignored dependency types from AbstractBeanFactory down to Abst=
ractAutowireCapableBeanFactory</td></tr><tr class=3D"modifications-oddrow">=
<td class=3D"modifications-data">modified</td><td class=3D"modifications-da=
ta">jhoeller</td><td class=3D"modifications-data">src/org/springframework/b=
eans/factory/support/AbstractAutowireCapableBeanFactory.java</td><td class=
=3D"modifications-data">moved management of ignored dependency types from A=
bstractBeanFactory down to AbstractAutowireCapableBeanFactory</td></tr><tr =
class=3D"modifications-evenrow"><td class=3D"modifications-data">modified</=
td><td class=3D"modifications-data">jhoeller</td><td class=3D"modifications=
-data">src/org/springframework/beans/factory/config/ConfigurableBeanFactory=
.java</td><td class=3D"modifications-data">moved "ignoreDependencyType" met=
hod from ConfigurableBeanFactory interface down to ConfigurableListableBean=
Factory</td></tr><tr class=3D"modifications-oddrow"><td class=3D"modificati=
ons-data">modified</td><td class=3D"modifications-data">jhoeller</td><td cl=
ass=3D"modifications-data">src/org/springframework/beans/factory/config/Con=
figurableListableBeanFactory.java</td><td class=3D"modifications-data">move=
d "ignoreDependencyType" method from ConfigurableBeanFactory interface down=
to ConfigurableListableBeanFactory</td></tr><tr class=3D"modifications-eve=
nrow"><td class=3D"modifications-data">modified</td><td class=3D"modificati=
ons-data">robharrop</td><td class=3D"modifications-data">test/org/springfra=
mework/aop/framework/CglibProxyTests.java</td><td class=3D"modifications-da=
ta">Tests for fix SPR-529</td></tr><tr class=3D"modifications-oddrow"><td c=
lass=3D"modifications-data">modified</td><td class=3D"modifications-data">j=
hoeller</td><td class=3D"modifications-data">src/org/springframework/aop/fr=
amework/ReflectiveMethodInvocation.java</td><td class=3D"modifications-data=
">introduced ProxyMethodInvocation interface</td></tr><tr class=3D"modifica=
tions-evenrow"><td class=3D"modifications-data">modified</td><td class=3D"m=
odifications-data">jhoeller</td><td class=3D"modifications-data">src/org/sp=
ringframework/aop/support/DelegatingIntroductionInterceptor.java</td><td cl=
ass=3D"modifications-data">introduced ProxyMethodInvocation interface</td><=
/tr><tr class=3D"modifications-oddrow"><td class=3D"modifications-data">add=
ed</td><td class=3D"modifications-data">jhoeller</td><td class=3D"modificat=
ions-data">src/org/springframework/aop/ProxyMethodInvocation.java</td><td c=
lass=3D"modifications-data">introduced ProxyMethodInvocation interface</td>=
</tr><tr class=3D"modifications-evenrow"><td class=3D"modifications-data">m=
odified</td><td class=3D"modifications-data">robharrop</td><td class=3D"mod=
ifications-data">src/org/springframework/aop/framework/Cglib2AopProxy.java<=
/td><td class=3D"modifications-data">Fixed SPR-529</td></tr><tr class=3D"mo=
difications-oddrow"><td class=3D"modifications-data">modified</td><td class=
=3D"modifications-data">robharrop</td><td class=3D"modifications-data">src/=
org/springframework/beans/BeanUtils.java</td><td class=3D"modifications-dat=
a">Added lazy initialization support to Spring JMX. Refactored the internal=
s so assemblers are no longer dependent on having the bean instance availab=
le. Added getPropertyDescriptors() to BeanUtils to support JMX operations a=
nd modified Cglib2AopProxy to allow for target sources with no target.</td>=
</tr><tr class=3D"modifications-evenrow"><td class=3D"modifications-data">m=
odified</td><td class=3D"modifications-data">robharrop</td><td class=3D"mod=
ifications-data">test/org/springframework/beans/BeanUtilsTests.java</td><td=
class=3D"modifications-data">Added lazy initialization support to Spring J=
MX. Refactored the internals so assemblers are no longer dependent on havin=
g the bean instance available. Added getPropertyDescriptors() to BeanUtils =
to support JMX operations and modified Cglib2AopProxy to allow for target s=
ources with no target.</td></tr><tr class=3D"modifications-oddrow"><td clas=
s=3D"modifications-data">modified</td><td class=3D"modifications-data">robh=
arrop</td><td class=3D"modifications-data">sandbox/test/org/springframework=
/jmx/AbstractAutodetectTest.java</td><td class=3D"modifications-data">Added=
lazy initialization support to Spring JMX. Refactored the internals so ass=
emblers are no longer dependent on having the bean instance available. Adde=
d getPropertyDescriptors() to BeanUtils to support JMX operations and modif=
ied Cglib2AopProxy to allow for target sources with no target.</td></tr><tr=
class=3D"modifications-evenrow"><td class=3D"modifications-data">modified<=
/td><td class=3D"modifications-data">robharrop</td><td class=3D"modificatio=
ns-data">sandbox/test/org/springframework/jmx/AbstractJmxAssemblerTests.jav=
a</td><td class=3D"modifications-data">Added lazy initialization support to=
Spring JMX. Refactored the internals so assemblers are no longer dependent=
on having the bean instance available. Added getPropertyDescriptors() to B=
eanUtils to support JMX operations and modified Cglib2AopProxy to allow for=
target sources with no target.</td></tr><tr class=3D"modifications-oddrow"=
><td class=3D"modifications-data">modified</td><td class=3D"modifications-d=
ata">robharrop</td><td class=3D"modifications-data">sandbox/test/org/spring=
framework/jmx/AbstractProxyTests.java</td><td class=3D"modifications-data">=
Added lazy initialization support to Spring JMX. Refactored the internals s=
o assemblers are no longer dependent on having the bean instance available.=
Added getPropertyDescriptors() to BeanUtils to support JMX operations and =
modified Cglib2AopProxy to allow for target sources with no target.</td></t=
r><tr class=3D"modifications-evenrow"><td class=3D"modifications-data">adde=
d</td><td class=3D"modifications-data">robharrop</td><td class=3D"modificat=
ions-data">sandbox/test/org/springframework/jmx/ExceptionOnInitBean.java</t=
d><td class=3D"modifications-data">Added lazy initialization support to Spr=
ing JMX. Refactored the internals so assemblers are no longer dependent on =
having the bean instance available. Added getPropertyDescriptors() to BeanU=
tils to support JMX operations and modified Cglib2AopProxy to allow for tar=
get sources with no target.</td></tr><tr class=3D"modifications-oddrow"><td=
class=3D"modifications-data">added</td><td class=3D"modifications-data">ro=
bharrop</td><td class=3D"modifications-data">sandbox/test/org/springframewo=
rk/jmx/JmxMBeanAdapterTests.java</td><td class=3D"modifications-data">Added=
lazy initialization support to Spring JMX. Refactored the internals so ass=
emblers are no longer dependent on having the bean instance available. Adde=
d getPropertyDescriptors() to BeanUtils to support JMX operations and modif=
ied Cglib2AopProxy to allow for target sources with no target.</td></tr><tr=
class=3D"modifications-evenrow"><td class=3D"modifications-data">deleted</=
td><td class=3D"modifications-data">robharrop</td><td class=3D"modification=
s-data">sandbox/test/org/springframework/jmx/JmxMBeanAdaptorTests.java</td>=
<td class=3D"modifications-data">Added lazy initialization support to Sprin=
g JMX. Refactored the internals so assemblers are no longer dependent on ha=
ving the bean instance available. Added getPropertyDescriptors() to BeanUti=
ls to support JMX operations and modified Cglib2AopProxy to allow for targe=
t sources with no target.</td></tr><tr class=3D"modifications-oddrow"><td c=
lass=3D"modifications-data">added</td><td class=3D"modifications-data">robh=
arrop</td><td class=3D"modifications-data">sandbox/test/org/springframework=
/jmx/LazyInitTests.java</td><td class=3D"modifications-data">Added lazy ini=
tialization support to Spring JMX. Refactored the internals so assemblers a=
re no longer dependent on having the bean instance available. Added getProp=
ertyDescriptors() to BeanUtils to support JMX operations and modified Cglib=
2AopProxy to allow for target sources with no target.</td></tr><tr class=3D=
"modifications-evenrow"><td class=3D"modifications-data">added</td><td clas=
s=3D"modifications-data">robharrop</td><td class=3D"modifications-data">san=
dbox/test/org/springframework/jmx/lazyInit.xml</td><td class=3D"modificatio=
ns-data">Added lazy initialization support to Spring JMX. Refactored the in=
ternals so assemblers are no longer dependent on having the bean instance a=
vailable. Added getPropertyDescriptors() to BeanUtils to support JMX operat=
ions and modified Cglib2AopProxy to allow for target sources with no target=
.</td></tr><tr class=3D"modifications-oddrow"><td class=3D"modifications-da=
ta">modified</td><td class=3D"modifications-data">robharrop</td><td class=
=3D"modifications-data">src/org/springframework/aop/framework/Cglib2AopProx=
y.java</td><td class=3D"modifications-data">Added lazy initialization suppo=
rt to Spring JMX. Refactored the internals so assemblers are no longer depe=
ndent on having the bean instance available. Added getPropertyDescriptors()=
to BeanUtils to support JMX operations and modified Cglib2AopProxy to allo=
w for target sources with no target.</td></tr><tr class=3D"modifications-ev=
enrow"><td class=3D"modifications-data">modified</td><td class=3D"modificat=
ions-data">robharrop</td><td class=3D"modifications-data">sandbox/src/org/s=
pringframework/jmx/JmxMBeanAdapter.java</td><td class=3D"modifications-data=
">Added lazy initialization support to Spring JMX. Refactored the internals=
so assemblers are no longer dependent on having the bean instance availabl=
e. Added getPropertyDescriptors() to BeanUtils to support JMX operations an=
d modified Cglib2AopProxy to allow for target sources with no target.</td><=
/tr><tr class=3D"modifications-oddrow"><td class=3D"modifications-data">mod=
ified</td><td class=3D"modifications-data">robharrop</td><td class=3D"modif=
ications-data">sandbox/src/org/springframework/jmx/assemblers/AbstractModel=
MBeanInfoAssembler.java</td><td class=3D"modifications-data">Added lazy ini=
tialization support to Spring JMX. Refactored the internals so assemblers a=
re no longer dependent on having the bean instance available. Added getProp=
ertyDescriptors() to BeanUtils to support JMX operations and modified Cglib=
2AopProxy to allow for target sources with no target.</td></tr><tr class=3D=
"modifications-evenrow"><td class=3D"modifications-data">modified</td><td c=
lass=3D"modifications-data">robharrop</td><td class=3D"modifications-data">=
sandbox/src/org/springframework/jmx/assemblers/AbstractReflectionBasedModel=
MBeanInfoAssembler.java</td><td class=3D"modifications-data">Added lazy ini=
tialization support to Spring JMX. Refactored the internals so assemblers a=
re no longer dependent on having the bean instance available. Added getProp=
ertyDescriptors() to BeanUtils to support JMX operations and modified Cglib=
2AopProxy to allow for target sources with no target.</td></tr><tr class=3D=
"modifications-oddrow"><td class=3D"modifications-data">modified</td><td cl=
ass=3D"modifications-data">robharrop</td><td class=3D"modifications-data">s=
andbox/src/org/springframework/jmx/assemblers/ModelMBeanInfoAssembler.java<=
/td><td class=3D"modifications-data">Added lazy initialization support to S=
pring JMX. Refactored the internals so assemblers are no longer dependent o=
n having the bean instance available. Added getPropertyDescriptors() to Bea=
nUtils to support JMX operations and modified Cglib2AopProxy to allow for t=
arget sources with no target.</td></tr><tr class=3D"modifications-evenrow">=
<td class=3D"modifications-data">modified</td><td class=3D"modifications-da=
ta">robharrop</td><td class=3D"modifications-data">sandbox/src/org/springfr=
amework/jmx/assemblers/reflection/ReflectiveModelMBeanInfoAssembler.java</t=
d><td class=3D"modifications-data">Added lazy initialization support to Spr=
ing JMX. Refactored the internals so assemblers are no longer dependent on =
having the bean instance available. Added getPropertyDescriptors() to BeanU=
tils to support JMX operations and modified Cglib2AopProxy to allow for tar=
get sources with no target.</td></tr><tr class=3D"modifications-oddrow"><td=
class=3D"modifications-data">modified</td><td class=3D"modifications-data"=
>robharrop</td><td class=3D"modifications-data">sandbox/src/org/springframe=
work/jmx/assemblers/metadata/MetadataModelMBeanInfoAssembler.java</td><td c=
lass=3D"modifications-data">Added lazy initialization support to Spring JMX=
. Refactored the internals so assemblers are no longer dependent on having =
the bean instance available. Added getPropertyDescriptors() to BeanUtils to=
support JMX operations and modified Cglib2AopProxy to allow for target sou=
rces with no target.</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">src/org/springframework/beans/factor=
y/xml/spring-beans.dtd</td><td class=3D"modifications-data">mention that au=
towire by name will not be an error if there is no match</td></tr><tr class=
=3D"modifications-oddrow"><td class=3D"modifications-data">modified</td><td=
class=3D"modifications-data">colins</td><td class=3D"modifications-data">d=
ocs/reference/src/dtd.xml</td><td class=3D"modifications-data">mention that=
autowire by name will not be an error if there is no match</td></tr></tabl=
e><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: (16) </td>=
</tr><tr><td class=3D"distributables-data">Building jar: /jteam/build2/chec=
kout/spring/spring/dist/spring-core.jar</td></tr><tr class=3D"distributable=
s-oddrow"><td class=3D"distributables-data">Building jar: /jteam/build2/che=
ckout/spring/spring/dist/spring-aop.jar</td></tr><tr><td class=3D"distribut=
ables-data">Building jar: /jteam/build2/checkout/spring/spring/dist/spring-=
context.jar</td></tr><tr class=3D"distributables-oddrow"><td class=3D"distr=
ibutables-data">Building jar: /jteam/build2/checkout/spring/spring/dist/spr=
ing-dao.jar</td></tr><tr><td class=3D"distributables-data">Building jar: /j=
team/build2/checkout/spring/spring/dist/spring-orm.jar</td></tr><tr class=
=3D"distributables-oddrow"><td class=3D"distributables-data">Building jar: =
/jteam/build2/checkout/spring/spring/dist/spring-web.jar</td></tr><tr><td c=
lass=3D"distributables-data">Building jar: /jteam/build2/checkout/spring/sp=
ring/dist/spring-webmvc.jar</td></tr><tr class=3D"distributables-oddrow"><t=
d class=3D"distributables-data">Building jar: /jteam/build2/checkout/spring=
/spring/dist/spring.jar</td></tr><tr><td class=3D"distributables-data">Buil=
ding jar: /jteam/build2/checkout/spring/spring/dist/spring-mock.jar</td></t=
r><tr class=3D"distributables-oddrow"><td class=3D"distributables-data">Bui=
lding war: /jteam/build2/checkout/spring/spring/autobuilds/apps/buildtest/d=
ist/buildtest.war</td></tr><tr><td class=3D"distributables-data">Building w=
ar: /jteam/build2/checkout/spring/spring/autobuilds/apps/buildtest/dist/bui=
ldtest.war</td></tr><tr class=3D"distributables-oddrow"><td class=3D"distri=
butables-data">Building war: /jteam/build2/checkout/spring/spring/autobuild=
s/apps/buildtest/dist/buildtest.war</td></tr><tr><td class=3D"distributable=
s-data">Building jar: /jteam/build2/checkout/spring/spring/autobuilds/apps/=
jpetstore/war/WEB-INF/lib/jpetstore.jar</td></tr><tr class=3D"distributable=
s-oddrow"><td class=3D"distributables-data">Building war: /jteam/build2/che=
ckout/spring/spring/autobuilds/apps/jpetstore/dist/jpetstore.war</td></tr><=
tr><td class=3D"distributables-data">Building jar: /jteam/build2/checkout/s=
pring/spring/autobuilds/apps/jpetstore/war/WEB-INF/lib/jpetstore.jar</td></=
tr><tr class=3D"distributables-oddrow"><td class=3D"distributables-data">Bu=
ilding war: /jteam/build2/checkout/spring/spring/autobuilds/apps/jpetstore/=
dist/jpetstore.war</td></tr></table>
</body></html> |
|
From: Colin S. <col...@ex...> - 2004-12-08 23:12:31
|
The other thing that I need to find 10 min for is to document the import element. That's probably the most important of the outstanding documentation tasks. jürgen höller [werk3AT] wrote: >Well, we absolutely need to release 1.1.3 this week, JDK 1.3 compatibility being the main reason. And it looks like there's enough minor stuff left (and new reports expected for the coming weeks) to justify 1.1.4... We can still decide against it, but on the other hand 1.2 final is still a while away. > >Juergen > > >________________________________ > >Von: spr...@li... im Auftrag von Colin Sampaleanu >Gesendet: Mi 08.12.2004 23:30 >An: spr...@li... >Betreff: Re: [Springframework-developer] Preparing for 1.1.3 > > > >I'll see. All this does is add implementations for the two template >methods in the class, and the ejbtest sample does use those methods >already, and runs in JBoss. So it is not a big deal to test. > >Until today, I didn't know we were really planning 1.1.4, so I guess >it's not as important to get this in there now, if 1.1.4 is still coming. > > >jürgen höller [werk3AT] wrote: > > > >>Colin, >> >>I wouldn't mind deferring this to 1.1.4, in particular if there's not enough time to test the final implementation in a target environment. So if it doesn't get completely ready till tomorrow, please commit it after the actual 1.1.3 release. >> >>Juergen >> >> >>________________________________ >> >>Von: spr...@li... im Auftrag von Colin Sampaleanu >>Gesendet: Mi 08.12.2004 21:17 >>An: spr...@li... >>Betreff: Re: [Springframework-developer] Preparing for 1.1.3 >> >> >> >>I think tonight I should do SPR-358: >> http://opensource.atlassian.com/projects/spring/browse/SPR-358 >>there's been no more discussion on it. It's essentially zero risk, since >>it just moves existing working code used in the ejbtest integration test >>sample, into ContextLoader... >> >>Colin >> >> >>jürgen höller [werk3AT] wrote: >> >>>From my side, we're ready for the 1.1.3 release. All issues in JIRA that are still marked for 1.1.3 should be deferred to 1.1.4, unless they can be solved immediately. I'd like to do the actual release tomorrow. >> >> >> >> >>>It seems that a 1.1.4 release will be necessary to get all sorts of minor things in; probably in early January. Next stop after 1.1.4 will be 1.2 RC1 then - end of January or early February. >>> >>>Thoughts? >>> >>>Juergen >>> >>> >>>________________________________ >>> >>>Von: spr...@li... im Auftrag von jürgen höller [werk3AT] >>>Gesendet: Mo 06.12.2004 01:19 >>>An: spr...@li... >>>Betreff: [Springframework-developer] Preparing for 1.1.3 >>> >>> >>> >>>Hi everybody, >>> >>>I've committed a bunch of stuff for 1.1.3, mainly addressing recent JIRA issues but also refining HTTP invoker internals etc. Anyone who has some time left, please give a current snapshot a try and check whether everything works for you! >>> >>>I'd like to do the actual 1.1.3 release as early as this Wednesday, unless there are major obstacles. Fixing the JDK 1.3 incompatibilities that slipped into 1.1.2 is an important factor here, but also getting a couple of other things out early. >>> >>>This means that remaining issues that are not of critical importance should be deferred, either till 1.2 RC1 or till 1.1.4 (the need for such a further 1.1.x point needs to be discussed). Minor issues can also be fixed tomorrow or on Tuesday, of course. >>> >>>There are also a couple of documentation issues in JIRA. They are not critical for 1.1.3, but it would be good to address them as early as possible. >>> >>>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://productguide.itmanagersjournal.com/ >>>_______________________________________________ >>>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://productguide.itmanagersjournal.com/ >>>_______________________________________________ >>>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://productguide.itmanagersjournal.com/ >>_______________________________________________ >>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://productguide.itmanagersjournal.com/ >>_______________________________________________ >>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://productguide.itmanagersjournal.com/ >_______________________________________________ >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://productguide.itmanagersjournal.com/ >_______________________________________________ >Springframework-developer mailing list >Spr...@li... >https://lists.sourceforge.net/lists/listinfo/springframework-developer > > |
|
From: <jue...@we...> - 2004-12-08 23:02:26
|
Well, we absolutely need to release 1.1.3 this week, JDK 1.3 = compatibility being the main reason. And it looks like there's enough = minor stuff left (and new reports expected for the coming weeks) to = justify 1.1.4... We can still decide against it, but on the other hand = 1.2 final is still a while away. =20 Juergen =20 ________________________________ Von: spr...@li... im Auftrag = von Colin Sampaleanu Gesendet: Mi 08.12.2004 23:30 An: spr...@li... Betreff: Re: [Springframework-developer] Preparing for 1.1.3 I'll see. All this does is add implementations for the two template methods in the class, and the ejbtest sample does use those methods already, and runs in JBoss. So it is not a big deal to test. Until today, I didn't know we were really planning 1.1.4, so I guess it's not as important to get this in there now, if 1.1.4 is still = coming. j=FCrgen h=F6ller [werk3AT] wrote: >Colin, > >I wouldn't mind deferring this to 1.1.4, in particular if there's not = enough time to test the final implementation in a target environment. So = if it doesn't get completely ready till tomorrow, please commit it after = the actual 1.1.3 release. > >Juergen > > >________________________________ > >Von: spr...@li... im Auftrag = von Colin Sampaleanu >Gesendet: Mi 08.12.2004 21:17 >An: spr...@li... >Betreff: Re: [Springframework-developer] Preparing for 1.1.3 > > > >I think tonight I should do SPR-358: > http://opensource.atlassian.com/projects/spring/browse/SPR-358 >there's been no more discussion on it. It's essentially zero risk, = since >it just moves existing working code used in the ejbtest integration = test >sample, into ContextLoader... > >Colin > > >j=FCrgen h=F6ller [werk3AT] wrote: > >>From my side, we're ready for the 1.1.3 release. All issues in JIRA = that are still marked for 1.1.3 should be deferred to 1.1.4, unless they = can be solved immediately. I'd like to do the actual release tomorrow. >=20 > >>It seems that a 1.1.4 release will be necessary to get all sorts of = minor things in; probably in early January. Next stop after 1.1.4 will = be 1.2 RC1 then - end of January or early February. >> >>Thoughts? >> >>Juergen >> >> >>________________________________ >> >>Von: spr...@li... im Auftrag = von j=FCrgen h=F6ller [werk3AT] >>Gesendet: Mo 06.12.2004 01:19 >>An: spr...@li... >>Betreff: [Springframework-developer] Preparing for 1.1.3 >> >> >> >>Hi everybody, >> >>I've committed a bunch of stuff for 1.1.3, mainly addressing recent = JIRA issues but also refining HTTP invoker internals etc. Anyone who has = some time left, please give a current snapshot a try and check whether = everything works for you! >> >>I'd like to do the actual 1.1.3 release as early as this Wednesday, = unless there are major obstacles. Fixing the JDK 1.3 incompatibilities = that slipped into 1.1.2 is an important factor here, but also getting a = couple of other things out early. >> >>This means that remaining issues that are not of critical importance = should be deferred, either till 1.2 RC1 or till 1.1.4 (the need for such = a further 1.1.x point needs to be discussed). Minor issues can also be = fixed tomorrow or on Tuesday, of course. >> >>There are also a couple of documentation issues in JIRA. They are not = critical for 1.1.3, but it would be good to address them as early as = possible. >> >>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://productguide.itmanagersjournal.com/ >>_______________________________________________ >>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://productguide.itmanagersjournal.com/ >>_______________________________________________ >>Springframework-developer mailing list >>Spr...@li... >>https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >> >> =20 >> > > > >------------------------------------------------------- >SF email is sponsored by - The IT Product Guide >Read honest & candid reviews on hundreds of IT Products from real = users. >Discover which products truly live up to the hype. Start reading now. >http://productguide.itmanagersjournal.com/ >_______________________________________________ >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://productguide.itmanagersjournal.com/ >_______________________________________________ >Springframework-developer mailing list >Spr...@li... >https://lists.sourceforge.net/lists/listinfo/springframework-developer >=20 > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Colin S. <col...@ex...> - 2004-12-08 22:31:17
|
I'll see. All this does is add implementations for the two template methods in the class, and the ejbtest sample does use those methods already, and runs in JBoss. So it is not a big deal to test. Until today, I didn't know we were really planning 1.1.4, so I guess it's not as important to get this in there now, if 1.1.4 is still coming. jürgen höller [werk3AT] wrote: >Colin, > >I wouldn't mind deferring this to 1.1.4, in particular if there's not enough time to test the final implementation in a target environment. So if it doesn't get completely ready till tomorrow, please commit it after the actual 1.1.3 release. > >Juergen > > >________________________________ > >Von: spr...@li... im Auftrag von Colin Sampaleanu >Gesendet: Mi 08.12.2004 21:17 >An: spr...@li... >Betreff: Re: [Springframework-developer] Preparing for 1.1.3 > > > >I think tonight I should do SPR-358: > http://opensource.atlassian.com/projects/spring/browse/SPR-358 >there's been no more discussion on it. It's essentially zero risk, since >it just moves existing working code used in the ejbtest integration test >sample, into ContextLoader... > >Colin > > >jürgen höller [werk3AT] wrote: > >>From my side, we're ready for the 1.1.3 release. All issues in JIRA that are still marked for 1.1.3 should be deferred to 1.1.4, unless they can be solved immediately. I'd like to do the actual release tomorrow. > > >>It seems that a 1.1.4 release will be necessary to get all sorts of minor things in; probably in early January. Next stop after 1.1.4 will be 1.2 RC1 then - end of January or early February. >> >>Thoughts? >> >>Juergen >> >> >>________________________________ >> >>Von: spr...@li... im Auftrag von jürgen höller [werk3AT] >>Gesendet: Mo 06.12.2004 01:19 >>An: spr...@li... >>Betreff: [Springframework-developer] Preparing for 1.1.3 >> >> >> >>Hi everybody, >> >>I've committed a bunch of stuff for 1.1.3, mainly addressing recent JIRA issues but also refining HTTP invoker internals etc. Anyone who has some time left, please give a current snapshot a try and check whether everything works for you! >> >>I'd like to do the actual 1.1.3 release as early as this Wednesday, unless there are major obstacles. Fixing the JDK 1.3 incompatibilities that slipped into 1.1.2 is an important factor here, but also getting a couple of other things out early. >> >>This means that remaining issues that are not of critical importance should be deferred, either till 1.2 RC1 or till 1.1.4 (the need for such a further 1.1.x point needs to be discussed). Minor issues can also be fixed tomorrow or on Tuesday, of course. >> >>There are also a couple of documentation issues in JIRA. They are not critical for 1.1.3, but it would be good to address them as early as possible. >> >>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://productguide.itmanagersjournal.com/ >>_______________________________________________ >>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://productguide.itmanagersjournal.com/ >>_______________________________________________ >>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://productguide.itmanagersjournal.com/ >_______________________________________________ >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://productguide.itmanagersjournal.com/ >_______________________________________________ >Springframework-developer mailing list >Spr...@li... >https://lists.sourceforge.net/lists/listinfo/springframework-developer > > |
|
From: <jue...@we...> - 2004-12-08 22:24:54
|
Colin, =20 I wouldn't mind deferring this to 1.1.4, in particular if there's not = enough time to test the final implementation in a target environment. So = if it doesn't get completely ready till tomorrow, please commit it after = the actual 1.1.3 release. =20 Juergen =20 ________________________________ Von: spr...@li... im Auftrag = von Colin Sampaleanu Gesendet: Mi 08.12.2004 21:17 An: spr...@li... Betreff: Re: [Springframework-developer] Preparing for 1.1.3 I think tonight I should do SPR-358: http://opensource.atlassian.com/projects/spring/browse/SPR-358 there's been no more discussion on it. It's essentially zero risk, since it just moves existing working code used in the ejbtest integration test sample, into ContextLoader... Colin j=FCrgen h=F6ller [werk3AT] wrote: >From my side, we're ready for the 1.1.3 release. All issues in JIRA = that are still marked for 1.1.3 should be deferred to 1.1.4, unless they = can be solved immediately. I'd like to do the actual release tomorrow. > >It seems that a 1.1.4 release will be necessary to get all sorts of = minor things in; probably in early January. Next stop after 1.1.4 will = be 1.2 RC1 then - end of January or early February. > >Thoughts? > >Juergen > > >________________________________ > >Von: spr...@li... im Auftrag = von j=FCrgen h=F6ller [werk3AT] >Gesendet: Mo 06.12.2004 01:19 >An: spr...@li... >Betreff: [Springframework-developer] Preparing for 1.1.3 > > > >Hi everybody, > >I've committed a bunch of stuff for 1.1.3, mainly addressing recent = JIRA issues but also refining HTTP invoker internals etc. Anyone who has = some time left, please give a current snapshot a try and check whether = everything works for you! > >I'd like to do the actual 1.1.3 release as early as this Wednesday, = unless there are major obstacles. Fixing the JDK 1.3 incompatibilities = that slipped into 1.1.2 is an important factor here, but also getting a = couple of other things out early. > >This means that remaining issues that are not of critical importance = should be deferred, either till 1.2 RC1 or till 1.1.4 (the need for such = a further 1.1.x point needs to be discussed). Minor issues can also be = fixed tomorrow or on Tuesday, of course. > >There are also a couple of documentation issues in JIRA. They are not = critical for 1.1.3, but it would be good to address them as early as = possible. > >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://productguide.itmanagersjournal.com/ >_______________________________________________ >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://productguide.itmanagersjournal.com/ >_______________________________________________ >Springframework-developer mailing list >Spr...@li... >https://lists.sourceforge.net/lists/listinfo/springframework-developer >=20 > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Dmitriy K. <dko...@ru...> - 2004-12-08 21:44:21
|
It's already committed in CVS. Probably has not propagated to the public instance... katentim @hotmail.com wrote: > RCS file: /cvsroot/springframework/spring/.classpath,v > retrieving revision 1.80 > diff -u -r1.80 .classpath > --- .classpath 7 Dec 2004 21:06:36 -0000 1.80 > +++ .classpath 8 Dec 2004 21:32:37 -0000 > @@ -94,5 +94,6 @@ > <classpathentry kind="lib" path="lib/jamon/JAMon.jar"/> > <classpathentry kind="lib" path="lib/log4j/log4j-1.2.9.jar"/> > <classpathentry kind="lib" path="lib/struts/struts.jar"/> > + <classpathentry kind="lib" > path="lib/velocity/velocity-tools-view-1.1.jar"/> > <classpathentry kind="output" path="target/other-classes"/> > </classpath> > > > > > ------------------------------------------------------- > 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://productguide.itmanagersjournal.com/ > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: katentim @hotmail.c. <kat...@ho...> - 2004-12-08 21:39:07
|
RCS file: /cvsroot/springframework/spring/.classpath,v retrieving revision 1.80 diff -u -r1.80 .classpath --- .classpath 7 Dec 2004 21:06:36 -0000 1.80 +++ .classpath 8 Dec 2004 21:32:37 -0000 @@ -94,5 +94,6 @@ <classpathentry kind="lib" path="lib/jamon/JAMon.jar"/> <classpathentry kind="lib" path="lib/log4j/log4j-1.2.9.jar"/> <classpathentry kind="lib" path="lib/struts/struts.jar"/> + <classpathentry kind="lib" path="lib/velocity/velocity-tools-view-1.1.jar"/> <classpathentry kind="output" path="target/other-classes"/> </classpath> |
|
From: <jue...@we...> - 2004-12-08 21:20:11
|
It's already committed to the main branch, so will be in 1.1.3 :-) =20 Thanks for the suggestion! =20 Juergen =20 ________________________________ Von: spr...@li... im Auftrag = von Rob Butler Gesendet: Mi 08.12.2004 22:08 An: spr...@li... Betreff: Re: [Springframework-developer] Re: [Springframework-user] = Velocity Tools and Spring MVC GREAT! Will this make it into 1.1.3? Thanks j=FCrgen, your efforts are greatly appreciated. Rob --- j=FCrgen h=F6ller [werk3AT] <jue...@we...> wrote: > OK, I'll add an "attributes" property of type > java.util.Properties and an "attributesMap" property > of type java.util.Map to UrlBasedViewResolver. The > first can be populated via <value> or <props>; the > latter is meant to be populated via <map> but also > allows specifying direct entries like <property > name=3D"attributesMap[key1]"><value>myValue</value></property>. >=20 > "attributesCSV" doesn't make too much sense on a > ViewResolver, as it's really just meant for view > definitions in properties file (read by > ResourceBundleViewResolver). For this reason, I'm > not keen on introducing it on UrlBasedViewResolver. >=20 > Juergen >=20 > > ________________________________ > > Von: > spr...@li... im > Auftrag von Rob Butler > Gesendet: Di 07.12.2004 20:44 > An: spr...@li... > Betreff: Re: [Springframework-user] Velocity Tools > and Spring MVC > > > > Actually, things may not be as clear as I thought. > > > > I understand your argument of allowing > > > Spring-managed placeholders; that's why I > pointed > > > out the "attributes" support. AbstractView's > > > "attributes" and "attributesCSV" are indeed just > > > suitable for String values, but "attributesMap" > > > allows any Object as value: You could define > inner > > > beans of type java.lang.Integer or the like > there, > > > to get values of specific types. The problem of > > > getting special types for map values is not > > > restricted to VelocityView; it's the same for > any > > > other type of Spring-defined bean, so needs a > > > generic solution. > > Ok, I agree with everything above. But here's the > problem. I can add an attribute to a view, but if I > have 30 views in my application, and I want the same > property exposed to all 30 views, I then must define > 30 view beans in my spring config (yuck!). There is > currently no way to set attributes in a view > resolver > so that the attributes are added to all views > created > by that resolver. > > Can you add a setAttributes(Properties prop), > setAttributesMap(Map), and a > setAttributesCSV(String) > method to the > org.springframework.web.servlet.view.UrlBasedViewResolver > class? This would then allow you to add properties > to > the view resolver, so the properties are then > available in all views created by the resolver. > Since > this is a base view resolver, the functionality > would > be available to all other view technologies too, so > it > is a generic solution. > > Thanks. > Rob > > > =20 > __________________________________ > Do you Yahoo!? > Yahoo! Mail - 250MB free storage. Do more. Manage > less. > http://info.mail.yahoo.com/mail_250 > > > ------------------------------------------------------- > 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://productguide.itmanagersjournal.com/ > _______________________________________________ > Springframework-user mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-user > > > > > ------------------------------------------------------- > 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://productguide.itmanagersjournal.com/ > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > =20 __________________________________ Do you Yahoo!? All your favorites on one personal page - Try My Yahoo! http://my.yahoo.com ------------------------------------------------------- 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://productguide.itmanagersjournal.com/ _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Roberto C. <ro...@in...> - 2004-12-08 21:12:06
|
How can I help you spring people? Seems that there are many small things to do on Spring and I think I'm = getting confident enough with its source (at least for the mvc stuff). Just let me know. /Roberto |
|
From: Rob B. <cro...@ya...> - 2004-12-08 21:08:59
|
GREAT! Will this make it into 1.1.3? Thanks jürgen, your efforts are greatly appreciated. Rob --- jürgen höller [werk3AT] <jue...@we...> wrote: > OK, I'll add an "attributes" property of type > java.util.Properties and an "attributesMap" property > of type java.util.Map to UrlBasedViewResolver. The > first can be populated via <value> or <props>; the > latter is meant to be populated via <map> but also > allows specifying direct entries like <property > name="attributesMap[key1]"><value>myValue</value></property>. > > "attributesCSV" doesn't make too much sense on a > ViewResolver, as it's really just meant for view > definitions in properties file (read by > ResourceBundleViewResolver). For this reason, I'm > not keen on introducing it on UrlBasedViewResolver. > > Juergen > > > ________________________________ > > Von: > spr...@li... im > Auftrag von Rob Butler > Gesendet: Di 07.12.2004 20:44 > An: spr...@li... > Betreff: Re: [Springframework-user] Velocity Tools > and Spring MVC > > > > Actually, things may not be as clear as I thought. > > > > I understand your argument of allowing > > > Spring-managed placeholders; that's why I > pointed > > > out the "attributes" support. AbstractView's > > > "attributes" and "attributesCSV" are indeed just > > > suitable for String values, but "attributesMap" > > > allows any Object as value: You could define > inner > > > beans of type java.lang.Integer or the like > there, > > > to get values of specific types. The problem of > > > getting special types for map values is not > > > restricted to VelocityView; it's the same for > any > > > other type of Spring-defined bean, so needs a > > > generic solution. > > Ok, I agree with everything above. But here's the > problem. I can add an attribute to a view, but if I > have 30 views in my application, and I want the same > property exposed to all 30 views, I then must define > 30 view beans in my spring config (yuck!). There is > currently no way to set attributes in a view > resolver > so that the attributes are added to all views > created > by that resolver. > > Can you add a setAttributes(Properties prop), > setAttributesMap(Map), and a > setAttributesCSV(String) > method to the > org.springframework.web.servlet.view.UrlBasedViewResolver > class? This would then allow you to add properties > to > the view resolver, so the properties are then > available in all views created by the resolver. > Since > this is a base view resolver, the functionality > would > be available to all other view technologies too, so > it > is a generic solution. > > Thanks. > Rob > > > > __________________________________ > Do you Yahoo!? > Yahoo! Mail - 250MB free storage. Do more. Manage > less. > http://info.mail.yahoo.com/mail_250 > > > ------------------------------------------------------- > 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://productguide.itmanagersjournal.com/ > _______________________________________________ > Springframework-user mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-user > > > > > ------------------------------------------------------- > 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://productguide.itmanagersjournal.com/ > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > __________________________________ Do you Yahoo!? All your favorites on one personal page Try My Yahoo! http://my.yahoo.com |
|
From: <jue...@we...> - 2004-12-08 20:38:38
|
OK, I'll add an "attributes" property of type java.util.Properties and =
an "attributesMap" property of type java.util.Map to =
UrlBasedViewResolver. The first can be populated via <value> or <props>; =
the latter is meant to be populated via <map> but also allows specifying =
direct entries like <property =
name=3D"attributesMap[key1]"><value>myValue</value></property>.
=20
"attributesCSV" doesn't make too much sense on a ViewResolver, as it's =
really just meant for view definitions in properties file (read by =
ResourceBundleViewResolver). For this reason, I'm not keen on =
introducing it on UrlBasedViewResolver.
=20
Juergen
=20
________________________________
Von: spr...@li... im Auftrag von Rob =
Butler
Gesendet: Di 07.12.2004 20:44
An: spr...@li...
Betreff: Re: [Springframework-user] Velocity Tools and Spring MVC
Actually, things may not be as clear as I thought.
> > I understand your argument of allowing
> > Spring-managed placeholders; that's why I pointed
> > out the "attributes" support. AbstractView's
> > "attributes" and "attributesCSV" are indeed just
> > suitable for String values, but "attributesMap"
> > allows any Object as value: You could define inner
> > beans of type java.lang.Integer or the like there,
> > to get values of specific types. The problem of
> > getting special types for map values is not
> > restricted to VelocityView; it's the same for any
> > other type of Spring-defined bean, so needs a
> > generic solution.
Ok, I agree with everything above. But here's the
problem. I can add an attribute to a view, but if I
have 30 views in my application, and I want the same
property exposed to all 30 views, I then must define
30 view beans in my spring config (yuck!). There is
currently no way to set attributes in a view resolver
so that the attributes are added to all views created
by that resolver.
Can you add a setAttributes(Properties prop),
setAttributesMap(Map), and a setAttributesCSV(String)
method to the
org.springframework.web.servlet.view.UrlBasedViewResolver
class? This would then allow you to add properties to
the view resolver, so the properties are then
available in all views created by the resolver. Since
this is a base view resolver, the functionality would
be available to all other view technologies too, so it
is a generic solution.
Thanks.
Rob
=20
__________________________________
Do you Yahoo!?
Yahoo! Mail - 250MB free storage. Do more. Manage less.
http://info.mail.yahoo.com/mail_250
-------------------------------------------------------
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://productguide.itmanagersjournal.com/
_______________________________________________
Springframework-user mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-user
|
|
From: Colin S. <col...@ex...> - 2004-12-08 20:17:17
|
I think tonight I should do SPR-358: http://opensource.atlassian.com/projects/spring/browse/SPR-358 there's been no more discussion on it. It's essentially zero risk, since it just moves existing working code used in the ejbtest integration test sample, into ContextLoader... Colin jürgen höller [werk3AT] wrote: >From my side, we're ready for the 1.1.3 release. All issues in JIRA that are still marked for 1.1.3 should be deferred to 1.1.4, unless they can be solved immediately. I'd like to do the actual release tomorrow. > >It seems that a 1.1.4 release will be necessary to get all sorts of minor things in; probably in early January. Next stop after 1.1.4 will be 1.2 RC1 then - end of January or early February. > >Thoughts? > >Juergen > > >________________________________ > >Von: spr...@li... im Auftrag von jürgen höller [werk3AT] >Gesendet: Mo 06.12.2004 01:19 >An: spr...@li... >Betreff: [Springframework-developer] Preparing for 1.1.3 > > > >Hi everybody, > >I've committed a bunch of stuff for 1.1.3, mainly addressing recent JIRA issues but also refining HTTP invoker internals etc. Anyone who has some time left, please give a current snapshot a try and check whether everything works for you! > >I'd like to do the actual 1.1.3 release as early as this Wednesday, unless there are major obstacles. Fixing the JDK 1.3 incompatibilities that slipped into 1.1.2 is an important factor here, but also getting a couple of other things out early. > >This means that remaining issues that are not of critical importance should be deferred, either till 1.2 RC1 or till 1.1.4 (the need for such a further 1.1.x point needs to be discussed). Minor issues can also be fixed tomorrow or on Tuesday, of course. > >There are also a couple of documentation issues in JIRA. They are not critical for 1.1.3, but it would be good to address them as early as possible. > >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://productguide.itmanagersjournal.com/ >_______________________________________________ >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://productguide.itmanagersjournal.com/ >_______________________________________________ >Springframework-developer mailing list >Spr...@li... >https://lists.sourceforge.net/lists/listinfo/springframework-developer > > |
|
From: Rob B. <cro...@ya...> - 2004-12-08 19:44:50
|
jürgen, Please take a look at: http://article.gmane.org/gmane.comp.java.springframework.user/4708 I think it would be a useful addition, and if this could get out in 1.1.3 that would really help me. Thanks Rob --- jürgen höller [werk3AT] <jue...@we...> wrote: > From my side, we're ready for the 1.1.3 release. All > issues in JIRA that are still marked for 1.1.3 > should be deferred to 1.1.4, unless they can be > solved immediately. I'd like to do the actual > release tomorrow. > > It seems that a 1.1.4 release will be necessary to > get all sorts of minor things in; probably in early > January. Next stop after 1.1.4 will be 1.2 RC1 then > - end of January or early February. > > Thoughts? > > Juergen > > > ________________________________ > > Von: > spr...@li... > im Auftrag von jürgen höller [werk3AT] > Gesendet: Mo 06.12.2004 01:19 > An: spr...@li... > Betreff: [Springframework-developer] Preparing for > 1.1.3 > > > > Hi everybody, > > I've committed a bunch of stuff for 1.1.3, mainly > addressing recent JIRA issues but also refining HTTP > invoker internals etc. Anyone who has some time > left, please give a current snapshot a try and check > whether everything works for you! > > I'd like to do the actual 1.1.3 release as early as > this Wednesday, unless there are major obstacles. > Fixing the JDK 1.3 incompatibilities that slipped > into 1.1.2 is an important factor here, but also > getting a couple of other things out early. > > This means that remaining issues that are not of > critical importance should be deferred, either till > 1.2 RC1 or till 1.1.4 (the need for such a further > 1.1.x point needs to be discussed). Minor issues can > also be fixed tomorrow or on Tuesday, of course. > > There are also a couple of documentation issues in > JIRA. They are not critical for 1.1.3, but it would > be good to address them as early as possible. > > 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://productguide.itmanagersjournal.com/ > _______________________________________________ > 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://productguide.itmanagersjournal.com/ > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
|
From: Rob H. <ro...@ca...> - 2004-12-08 18:33:34
|
I added a few fixes for problems today, but I don't think I'll get anything else done in time. We still need to decide on a solution to the CGLIB/no arg constructor problem since I really want to get that fix in for 1.1.4. Rob jürgen höller [werk3AT] wrote: >>From my side, we're ready for the 1.1.3 release. All issues in JIRA that are still marked for 1.1.3 should be deferred to 1.1.4, unless they can be solved immediately. I'd like to do the actual release tomorrow. > >It seems that a 1.1.4 release will be necessary to get all sorts of minor things in; probably in early January. Next stop after 1.1.4 will be 1.2 RC1 then - end of January or early February. > >Thoughts? > >Juergen > > >________________________________ > >Von: spr...@li... im Auftrag von jürgen höller [werk3AT] >Gesendet: Mo 06.12.2004 01:19 >An: spr...@li... >Betreff: [Springframework-developer] Preparing for 1.1.3 > > > >Hi everybody, > >I've committed a bunch of stuff for 1.1.3, mainly addressing recent JIRA issues but also refining HTTP invoker internals etc. Anyone who has some time left, please give a current snapshot a try and check whether everything works for you! > >I'd like to do the actual 1.1.3 release as early as this Wednesday, unless there are major obstacles. Fixing the JDK 1.3 incompatibilities that slipped into 1.1.2 is an important factor here, but also getting a couple of other things out early. > >This means that remaining issues that are not of critical importance should be deferred, either till 1.2 RC1 or till 1.1.4 (the need for such a further 1.1.x point needs to be discussed). Minor issues can also be fixed tomorrow or on Tuesday, of course. > >There are also a couple of documentation issues in JIRA. They are not critical for 1.1.3, but it would be good to address them as early as possible. > >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://productguide.itmanagersjournal.com/ >_______________________________________________ >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://productguide.itmanagersjournal.com/ >_______________________________________________ >Springframework-developer mailing list >Spr...@li... >https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > |
|
From: Dmitriy K. <dko...@ru...> - 2004-12-08 18:16:56
|
The schedule looks good to me. Dmitriy. j=FCrgen h=F6ller [werk3AT] wrote: >From my side, we're ready for the 1.1.3 release. All issues in JIRA = that are still marked for 1.1.3 should be deferred to 1.1.4, unless t= hey can be solved immediately. I'd like to do the actual release tomo= rrow. >=20 >It seems that a 1.1.4 release will be necessary to get all sorts of = minor things in; probably in early January. Next stop after 1.1.4 wil= l be 1.2 RC1 then - end of January or early February. >=20 >Thoughts? >=20 >Juergen >=20 > >________________________________ > >Von: spr...@li... im Auftra= g von j=FCrgen h=F6ller [werk3AT] >Gesendet: Mo 06.12.2004 01:19 >An: spr...@li... >Betreff: [Springframework-developer] Preparing for 1.1.3 > > > >Hi everybody, > >I've committed a bunch of stuff for 1.1.3, mainly addressing recent = JIRA issues but also refining HTTP invoker internals etc. Anyone who = has some time left, please give a current snapshot a try and check wh= ether everything works for you! > >I'd like to do the actual 1.1.3 release as early as this Wednesday, = unless there are major obstacles. Fixing the JDK 1.3 incompatibilitie= s that slipped into 1.1.2 is an important factor here, but also getti= ng a couple of other things out early. > >This means that remaining issues that are not of critical importance= should be deferred, either till 1.2 RC1 or till 1.1.4 (the need for = such a further 1.1.x point needs to be discussed). Minor issues can a= lso be fixed tomorrow or on Tuesday, of course. > >There are also a couple of documentation issues in JIRA. They are no= t critical for 1.1.3, but it would be good to address them as early a= s possible. > >Juergen > > >------------------------------------------------------- >SF email is sponsored by - The IT Product Guide >Read honest & candid reviews on hundreds of IT Products from real us= ers. >Discover which products truly live up to the hype. Start reading now= . >http://productguide.itmanagersjournal.com/ >_______________________________________________ >Springframework-developer mailing list >Spr...@li... >https://lists.sourceforge.net/lists/listinfo/springframework-develop= er > > > > >------------------------------------------------------- >SF email is sponsored by - The IT Product Guide >Read honest & candid reviews on hundreds of IT Products from real us= ers. >Discover which products truly live up to the hype. Start reading now= .=20 >http://productguide.itmanagersjournal.com/ >_______________________________________________ >Springframework-developer mailing list >Spr...@li... >https://lists.sourceforge.net/lists/listinfo/springframework-develop= er > =20 > |
|
From: <jue...@we...> - 2004-12-08 18:07:51
|
From my side, we're ready for the 1.1.3 release. All issues in JIRA that = are still marked for 1.1.3 should be deferred to 1.1.4, unless they can = be solved immediately. I'd like to do the actual release tomorrow. =20 It seems that a 1.1.4 release will be necessary to get all sorts of = minor things in; probably in early January. Next stop after 1.1.4 will = be 1.2 RC1 then - end of January or early February. =20 Thoughts? =20 Juergen =20 ________________________________ Von: spr...@li... im Auftrag = von j=FCrgen h=F6ller [werk3AT] Gesendet: Mo 06.12.2004 01:19 An: spr...@li... Betreff: [Springframework-developer] Preparing for 1.1.3 Hi everybody, I've committed a bunch of stuff for 1.1.3, mainly addressing recent JIRA = issues but also refining HTTP invoker internals etc. Anyone who has some = time left, please give a current snapshot a try and check whether = everything works for you! I'd like to do the actual 1.1.3 release as early as this Wednesday, = unless there are major obstacles. Fixing the JDK 1.3 incompatibilities = that slipped into 1.1.2 is an important factor here, but also getting a = couple of other things out early. This means that remaining issues that are not of critical importance = should be deferred, either till 1.2 RC1 or till 1.1.4 (the need for such = a further 1.1.x point needs to be discussed). Minor issues can also be = fixed tomorrow or on Tuesday, of course. There are also a couple of documentation issues in JIRA. They are not = critical for 1.1.3, but it would be good to address them as early as = possible. 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://productguide.itmanagersjournal.com/ _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Rob H. <ro...@ca...> - 2004-12-08 16:32:34
|
Oops, yes. I have committed this now. Rob Dmitriy Kopylenko wrote: > Rob, > > I've just resynced with the latest CVS snapshot and the > "HtmlAdapterHostsTest" fails to compile because the > "org.springframework.jmx.adapters.ri.HtmlAdapterHost" is missing. > (this the sandbox). Did you forget to commit it? > > Regards, > Dmitriy. > > > ------------------------------------------------------- > 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://productguide.itmanagersjournal.com/ > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > |
|
From: Dmitriy K. <dko...@ru...> - 2004-12-08 16:09:05
|
Rob, I've just resynced with the latest CVS snapshot and the "HtmlAdapterHostsTest" fails to compile because the "org.springframework.jmx.adapters.ri.HtmlAdapterHost" is missing. (this the sandbox). Did you forget to commit it? Regards, Dmitriy. |
1239 messages has been excluded from this view by a project administrator.
