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: Dave B. <dba...@on...> - 2005-05-24 14:57:57
|
Hi Juergen, I've been testing with spring-framework-1.2.1-build.267-20050524.zip, and can't seem to recreate the problem, so it appears fixed. One thing that is bothering me, though, is that my scenario was a race condition. Basically, one of two things would happen on a timeout: 1) Tx rolls back and org.springframework.jdbc.UncategorizedSQLException(SQLException(TimeoutException) thrown by a call to hibernate session.flush() 2) Tx rolls back When using spring-framework-1.2.1-build.267-20050524, now, all I encounter is: 1) Tx rolls back and org.springframework.jdbc.UncategorizedSQLException(SQLException(TimeoutException) thrown by a call to hibernate session.flush() So it *appears* that with the fix, flush() is always called. This is fine with me, but is this what you would expect from your fix, or am I just getting lucky? Dave Dave Ballard wrote: > Hi Juergen , > > That's great. I will give it a try tomorrow. > > Dave > > Juergen Hoeller wrote: > >> Dave, >> >> I've already finished the reworking: AbstractPlatformTransactionManager >> discriminated between a "local" and a "global" rollback-only flag >> now, which >> was fortunately straightforward to do. >> >> "local" refers to a TransactionStatus.setRollbackOnly() call by the >> application, which leads to a silent rollback (usually, the >> application will >> throw an appropriate exception). >> >> "global" refers to the UserTransaction or resource holder being >> marked as >> rollback-only, which can only happen through the transaction >> coordinator. >> One example for this is a transaction timeout. >> >> There is one side effect, though: If you have an outer and an inner >> transaction and call TransactionStatus.setRollbackOnly() on the inner >> transaction without throwing an exception, you got a silent rollback >> of the >> outer transaction before. Now, the outer transaction will throw an >> UnexpectedRollbackException instead. >> >> I guess it's more appropriate to throw an UnexpectedRollbackException >> here >> in any case, to avoid surprises for callers of the outer transaction. >> Usually, the inner transaction will throw an exception anyway, so the >> outer >> transaction will simply rollback and propagate that exception. >> >> In total, I'm happy with the new semantics. Rollbacks will always >> lead to an >> exception, unless the local TransactionStatus object received a >> setRollbackOnly() call from the application. The slight change in >> semantics >> should not be an issue, as I do not expect any application to rely on >> such >> silent rollbacks of outer transactions. >> >> I'll commit this today; it should be available in the next nightly >> build. >> Please give this refined behavior a try and let me know how it works for >> you! >> >> Juergen >> >> >> -----Original Message----- >> From: spr...@li... >> [mailto:spr...@li...]On Behalf >> Of Dave Ballard >> Sent: Sunday, May 22, 2005 1:22 AM >> To: spr...@li... >> Subject: Re: [Springframework-developer] Spring 1.2 Spring JTA tx >> timeout, tx rolls back, but no exception thrown (another race condition) >> >> >> Hi Juergen, >> >> Thanks for checking into this. Does look a little ugly. Hopefully you'll >> find a way to tell the difference between the two different rollback >> situations (or to inquire if in fact a timeout has occurred). Currently >> this is a show-stopper for me. Although this type of timeout won't >> happen frequently, it will happen, and the consequences will be a little >> difficult to track down because of the lack of an exception. >> >> Thanks again for your help, >> Dave >> >> Juergen Hoeller wrote: >> >> >> >>> Good point - thanks for reporting this! JTA implementations seem to >>> mark >>> transaction as rollback-only when they have timed out, without further >>> indication. So unless you attempt an actual resource operation after >>> the >>> timeout, there is no guarantee than an exception gets thrown before >>> commit. >>> >>> If Spring discovers a rollback-only status, it assumes that the >>> application >>> has set the transaction to rollback-only and triggers a silent >>> rollback. >>> This will usually happen when TransactionStatus.setRollbackOnly() >>> has been >>> called, instead of configuring a rollback rule, with an >>> application-level >>> exception getting thrown. >>> >>> In the case of a JTA timeout, the rollback-only marker comes from >>> the JTA >>> subsystem, though. Spring effectively misinterprets that marker as >>> driven >>> >> >> by >> >> >>> the application, which leads to an inappropriate silent reaction. >>> I'll fix >>> that for Spring 1.2.1, although it's unfortunately not that trivial >>> for the >>> general case. >>> >>> Juergen >>> >>> >>> -----Original Message----- >>> From: spr...@li... >>> [mailto:spr...@li...]On Behalf >>> Of Dave Ballard >>> Sent: Friday, May 20, 2005 10:44 PM >>> To: spr...@li... >>> Subject: [Springframework-developer] Spring 1.2 Spring JTA tx timeout, >>> tx rolls back, but no exception thrown (another race condition) >>> >>> >>> Hi Juergen, >>> >>> Using unpatched Spring 1.2 on WebLogic 6.1. I've defined a >>> Spring-managed service bean, with the following transaction manager and >>> transaction interceptor beans: >>> >>> <bean id="MyTransactionManager" >>> class="org.springframework.transaction.jta.JtaTransactionManager"> >>> <property >>> name="transactionManagerName"><value>java:comp/UserTransaction</value></pro >>> >>> >> >> p >> >> >>> erty> >>> </bean> >>> >>> <bean id="MyTransactionInterceptor" >>> class="org.springframework.transaction.interceptor.TransactionInterceptor"> >>> >>> <property name="transactionManager"><ref >>> bean="MyTransactionManager"/></property> >>> <property name="transactionAttributeSource"> >>> <value> >>> PaymentService.commit=PROPAGATION_REQUIRED,-Exception >>> </value> >>> </property> >>> </bean> >>> >>> The transactional demarcation causes a commit when the method succeeds, >>> and causes a rollback when an exception is thrown (and throws the >>> exception), as expected. However, if I introduce a 40 second sleep in >>> the method, the transaction rolls back as expected, but sometimes no >>> exception is thrown. In the case where no exception is thrown, I can >>> see >>> in the Spring log: >>> >>> WARN 14:45:03,156 [ExecuteThread: '30' for queue: 'default'] >>> [edemo_acme] (EjbUtils.java:626) - START SLEEP 40: >>> PaymentServiceImpl.commit() 40 seconds...... >>> WARN 14:45:43,156 [ExecuteThread: '30' for queue: 'default'] >>> [edemo_acme] (EjbUtils.java:633) - DONE SLEEP 40: >>> PaymentServiceImpl.commit() 40 seconds...... >>> DEBUG 14:45:43,156 [ExecuteThread: '30' for queue: 'default'] >>> [edemo_acme] (TransactionAspectSupport.java:258) - Invoking commit for >>> transaction on PaymentService.commit >>> DEBUG 14:45:43,156 [ExecuteThread: '30' for queue: 'default'] >>> [edemo_acme] (AbstractPlatformTransactionManager.java:382) - >>> Transactional code has requested rollback >>> DEBUG 14:45:43,156 [ExecuteThread: '30' for queue: 'default'] >>> [edemo_acme] (AbstractPlatformTransactionManager.java:542) - Triggering >>> beforeCompletion synchronization >>> DEBUG 14:45:43,156 [ExecuteThread: '30' for queue: 'default'] >>> [edemo_acme] (TransactionSynchronizationManager.java:177) - Removed >>> value [org.springframework.orm.hibernate.SessionHolder@57f820] for key >>> [net.sf.hibernate.impl.SessionFactoryImpl@39569e] from thread >>> [ExecuteThread: '30' for queue: 'default'] >>> DEBUG 14:45:43,156 [ExecuteThread: '30' for queue: 'default'] >>> [edemo_acme] (SessionFactoryUtils.java:730) - Closing Hibernate Session >>> DEBUG 14:45:43,156 [ExecuteThread: '30' for queue: 'default'] >>> [edemo_acme] (AbstractPlatformTransactionManager.java:463) - Initiating >>> transaction rollback >>> DEBUG 14:45:43,156 [ExecuteThread: '30' for queue: 'default'] >>> [edemo_acme] (JtaTransactionManager.java:719) - Rolling back JTA >>> >> >> transaction >> >> >>> DEBUG 14:45:43,156 [ExecuteThread: '30' for queue: 'default'] >>> [edemo_acme] (AbstractPlatformTransactionManager.java:572) - Triggering >>> afterCompletion synchronization >>> DEBUG 14:45:43,156 [ExecuteThread: '30' for queue: 'default'] >>> [edemo_acme] (TransactionSynchronizationManager.java:252) - Clearing >>> transaction synchronization >>> INFO 14:45:43,171 [ExecuteThread: '30' for queue: 'default'] >>> [edemo_acme] (PaymentCommit.java:167) - PERFORMANCE END PaymentCommit >>> >>> This is an intermittent problem that occurs in both 1.1.5 and 1.2. I >>> run >>> the same test over and over, and while it always rolls back, it only >>> sometimes throws an exception. In the case where it does throw an >>> exception, the log is different: >>> >>> WARN 15:18:54,109 [ExecuteThread: '31' for queue: 'default'] >>> [edemo_acme] (EjbUtils.java:626) - START SLEEP 40: >>> PaymentServiceImpl.commit() 40 seconds...... >>> WARN 15:19:34,109 [ExecuteThread: '31' for queue: 'default'] >>> [edemo_acme] (EjbUtils.java:633) - DONE SLEEP 40: >>> PaymentServiceImpl.commit() 40 seconds...... >>> DEBUG 15:19:34,109 [ExecuteThread: '31' for queue: 'default'] >>> [edemo_acme] (TransactionAspectSupport.java:241) - Invoking commit for >>> transaction on method 'commit' in class [PaymentService] >>> DEBUG 15:19:34,109 [ExecuteThread: '31' for queue: 'default'] >>> [edemo_acme] (AbstractPlatformTransactionManager.java:523) - Triggering >>> beforeCommit synchronization >>> DEBUG 15:19:34,109 [ExecuteThread: '31' for queue: 'default'] >>> [edemo_acme] (SessionFactoryUtils.java:809) - Flushing Hibernate >>> session >>> on transaction synchronization >>> DEBUG 15:19:34,109 [ExecuteThread: '31' for queue: 'default'] >>> [edemo_acme] (SQLErrorCodeSQLExceptionTranslator.java:225) - Unable to >>> translate SQLException with errorCode '0', will now try the fallback >>> translator >>> DEBUG 15:19:34,109 [ExecuteThread: '31' for queue: 'default'] >>> [edemo_acme] (SQLStateSQLExceptionTranslator.java:74) - Translating >>> SQLException with SQLState 'null' and errorCode '0' and message [The >>> transaction is no longer active (status = Rolled back. >>> [Reason=weblogic.transaction.internal.TimedOutException: Transaction >>> timed out after 28 seconds >>> [snip] >>> >>> This appears to be another race condition. In the case where the >>> exception is thrown, the transaction has not yet been flagged as >>> rollback-only. The code proceeds to attempt a hibernate flush(), and >>> this causes a SQLException(TimedOutException) to be thrown. >>> >>> In the first case where no exception is thrown, the transaction has >>> already been flagged rollback-only, so the code never calls hibernate >>> flush, and simply returns w/o an exception after rolling back the tx. >>> >>> This is a pretty serious problem for my application because the calling >>> code has no idea that the transaction rolled back. >>> >>> Thanks, >>> Dave >>> >>> >>> >>> >>> >>> >>> ------------------------------------------------------- >>> This SF.Net email is sponsored by Oracle Space Sweepstakes >>> Want to be the first software developer in space? >>> Enter now for the Oracle Space Sweepstakes! >>> http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click >>> _______________________________________________ >>> Springframework-developer mailing list >>> Spr...@li... >>> https://lists.sourceforge.net/lists/listinfo/springframework-developer >>> >>> >>> >>> ------------------------------------------------------- >>> This SF.Net email is sponsored by Oracle Space Sweepstakes >>> Want to be the first software developer in space? >>> Enter now for the Oracle Space Sweepstakes! >>> http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click >>> _______________________________________________ >>> Springframework-developer mailing list >>> Spr...@li... >>> https://lists.sourceforge.net/lists/listinfo/springframework-developer >>> >>> >>> >>> >>> >> >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by Oracle Space Sweepstakes >> Want to be the first software developer in space? >> Enter now for the Oracle Space Sweepstakes! >> http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by Oracle Space Sweepstakes >> Want to be the first software developer in space? >> Enter now for the Oracle Space Sweepstakes! >> http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >> >> >> > > > ------------------------------------------------------- > This SF.Net email is sponsored by Oracle Space Sweepstakes > Want to be the first software developer in space? > Enter now for the Oracle Space Sweepstakes! > http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > |
|
From: Achmad A. R. <a.a...@gm...> - 2005-05-24 08:31:47
|
Sory, my mistake :) (Read The Fine Manual) On 5/24/05, Shinobu Kawai <shi...@gm...> wrote: >=20 > Hi Achmad, >=20 > > Hi guys, is there any idea how to integrate velocity-view-tool=20 > especially > > $import , into springMacroRequestContext ? >=20 > From Spring 1.2, you can use the VelocityToolboxView, which adds > toolbox support to the VelocityView. >=20 > http://static.springframework.org/spring/docs/1.2/api/org/springframework= /web/servlet/view/velocity/VelocityToolboxView.html >=20 > ## But there might be a way to inject tools from the > ApplicationContext. I'm still new to Spring. >=20 > Best regards, > -- Shinobu >=20 > -- > Shinobu Kawai <shi...@gm...> >=20 >=20 > ------------------------------------------------------- > This SF.Net <http://SF.Net> email is sponsored by Oracle Space Sweepstake= s > Want to be the first software developer in space? > Enter now for the Oracle Space Sweepstakes! > http://ads.osdn.com/?ad_idt12&alloc_id=16344&opclick > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |
|
From: Steven D. <ste...@gm...> - 2005-05-24 07:18:41
|
Regarding the WebFlow FAQ entry, this should not be a limitation for CRUD applications. For example, you should never call the remove action before you have displayed the related record which is by itself an example of a workflow. The same for detail screens, you should first pass through a table view or another detail screen. I'm not sure about the back button, maybe somebody from the WebFlow crew could comment on that. On 5/17/05, Tim Kettering <tim...@vi...> wrote: >=20 > Hi everyone, >=20 > I'm just throwing this out here to see what other people have to say. I = can > see from the list that there are a few developers actively working on por= tal > solutions using Spring MVC. We are starting on our first project using t= his > as well, and one of the issues I'm trying to figure out now is the matter= of > maintaining state in a portlet. >=20 > In a typical CRUD example, if we have a portlet to display, edit and maan= ge > information about a certain object, like a Book. We'd have view, edit and > delete functionality for example. >=20 > In a typical non-portlet webapp, we could easily split those up across > different servlets for fine-grained areas of responsibility. >=20 > But it's not as simple with portlets, because there are limitations on wh= at > can be done, and essentially, all requests would need to go thru a single > portlet configuration. >=20 > So, it no longer become sufficient to configure a simple portlet controll= er > for a portlet. There needs to be a way to maintain state and to delegate > the request/response process to different types of controllers depending = on > the state. Like a View page would need to go thru a derivation of > BaseCommandController, an Edit page would go thru SimpleFormController. >=20 > And not to mention adding yet another dimension when considering portlet > modes as well! >=20 > This article at IBM Developerworks pretty much covers the same issue I am > bringing up: >=20 > http://www-106.ibm.com/developerworks/websphere/library/techarticles/0312= _ha > nis/hanis1.html >=20 > I did look at Spring's WebFlow a few days ago to see if it could address = our > issue, but in the Webflow FAQ, it pretty much states that WebFlow should = not > be used in cases where the user will be using back-button, or indetermina= te > actions not within a strict flow. >=20 > So that kinda leaves me back at square one. After some discussion with m= y > co-worker, I would imagine that this is a common problem for any Spring > portlet developer creating more than just simple portlet functionality. = And > that as Spring portlet support matures, this will be a more common issue = for > everyone. Hence this email to the list. >=20 > I'm now wondering how some of you have addressed this problem, and whethe= r > there is a need for Spring's portlet support, to be in Spring 1.3 to incl= ude > some way to configure and facilitate a state process, maybe even based on > WebFlow's state machine - although I have only given WebFlow's state > functionality a brief look. >=20 > Thanks in advance, >=20 > -tim >=20 >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by Oracle Space Sweepstakes > Want to be the first software developer in space? > Enter now for the Oracle Space Sweepstakes! > http://ads.osdn.com/?ad_id=3D7412&alloc_id=3D16344&op=3Dclick > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer >=20 >=20 --=20 "If you want to be a different fish, you gotta jump out of the school." -- Captain Beefheart |
|
From: J.Enrique Ruiz-V. <er...@di...> - 2005-05-24 07:01:16
|
Hi Tim, It could take to long time to explain you how we work with portlets, but basically, we use View mode for read-only operations and Edit mode for write operations. Before using Spring Webflow we were using one Controller for each mode, in Edit mode we were using our porting of MultiActionController to manage each update action. Now with Spring Webflow we have one Controller for each portlet, one flow for each portlet mode and we have one SWF-Action for each read or write action. I hope this message can help you. >Hi everyone, > >I'm just throwing this out here to see what other people have to say. I can >see from the list that there are a few developers actively working on portal >solutions using Spring MVC. We are starting on our first project using this >as well, and one of the issues I'm trying to figure out now is the matter of >maintaining state in a portlet. > >In a typical CRUD example, if we have a portlet to display, edit and maange >information about a certain object, like a Book. We'd have view, edit and >delete functionality for example. > >In a typical non-portlet webapp, we could easily split those up across >different servlets for fine-grained areas of responsibility. > >But it's not as simple with portlets, because there are limitations on what >can be done, and essentially, all requests would need to go thru a single >portlet configuration. > >So, it no longer become sufficient to configure a simple portlet controller >for a portlet. There needs to be a way to maintain state and to delegate >the request/response process to different types of controllers depending on >the state. Like a View page would need to go thru a derivation of >BaseCommandController, an Edit page would go thru SimpleFormController. > >And not to mention adding yet another dimension when considering portlet >modes as well! > >This article at IBM Developerworks pretty much covers the same issue I am >bringing up: > >http://www-106.ibm.com/developerworks/websphere/library/techarticles/0312_ha >nis/hanis1.html > >I did look at Spring's WebFlow a few days ago to see if it could address our >issue, but in the Webflow FAQ, it pretty much states that WebFlow should not >be used in cases where the user will be using back-button, or indeterminate >actions not within a strict flow. > >So that kinda leaves me back at square one. After some discussion with my >co-worker, I would imagine that this is a common problem for any Spring >portlet developer creating more than just simple portlet functionality. And >that as Spring portlet support matures, this will be a more common issue for >everyone. Hence this email to the list. > >I'm now wondering how some of you have addressed this problem, and whether >there is a need for Spring's portlet support, to be in Spring 1.3 to include >some way to configure and facilitate a state process, maybe even based on >WebFlow's state machine - although I have only given WebFlow's state >functionality a brief look. > >Thanks in advance, > >-tim > > > >------------------------------------------------------- >This SF.Net email is sponsored by Oracle Space Sweepstakes >Want to be the first software developer in space? >Enter now for the Oracle Space Sweepstakes! >http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click >_______________________________________________ >Springframework-developer mailing list >Spr...@li... >https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > -- J.Enrique Ruiz-Valenciano CIO, DiSiD S.L.L. (http://www.disid.com) Phone: +34.655407965 Email: er...@di... |
|
From: Darren D. <da...@sh...> - 2005-05-24 04:34:26
|
1116909262
FAILED
[junit] ------------- Standard Output ---------------
[junit] StopWatch '': running time (millis) = 24381
[junit] [class org.springframework.aop.framework.OptimizedCglibProxyTests.testManyProxies: create 10000 proxies] took 24381=100%
[junit] ------------- ---------------- ---------------
[junit] Testcase: testDeclaredException took 0.24 sec
[junit] Testcase: testTargetCanGetInvocationEvenIfNoAdviceChain took 0 sec
[junit] Testcase: testExistingProxyChangesTarget took 0.005 sec
[junit] Testcase: testDynamicMethodPointcutThatAppliesStaticallyOnlyToSetters took 0.422 sec
[junit] Testcase: testStaticMethodPointcut took 0.397 sec
[junit] Testcase: testNullConfig took 0.011 sec
[junit] Testcase: testNoTarget took 0.001 sec
[junit] Testcase: testProtectedMethodInvocation took 0.012 sec
[junit] Testcase: testProxyCanBeClassNotInterface took 0.001 sec
[junit] Testcase: testCglibProxyingGivesMeaningfulExceptionIfAskedToProxyNonvisibleClass took 0.063 sec
[junit] Testcase: testMethodInvocationDuringConstructor took 0.36 sec
[junit] Testcase: testUnadvisedProxyCreationWithCallDuringConstructor took 0.002 sec
[junit] Testcase: testMultipleProxies took 0.561 sec
[junit] Testcase: testWithNoArgConstructor took 0.003 sec
[junit] Testcase: testProxyAProxy took 0.003 sec
[junit] Testcase: testExceptionHandling took 0.112 sec
[junit] Testcase: testWithDependencyChecking took 0.389 sec
[junit] Testcase: testNoInterceptorsAndNoTarget took 0.001 sec
[junit] Testcase: testValuesStick took 0.001 sec
[junit] Testcase: testManyProxies took 24.433 sec
[junit] FAILED
[junit] Proxy creation was too slow
[junit] junit.framework.AssertionFailedError: Proxy creation was too slow
[junit] at org.springframework.aop.framework.AbstractAopProxyTests.testManyProxies(AbstractAopProxyTests.java:147)
This is an automated mail from one of the SF Compile Farm machines.
The machine name noted in the subject encountered a failure building
or running the Spring test suite. The last few lines of the output
were included for info.
NB: No further mail will be sent from this machine until a
manual reset occurs on the cf-shell machine, although builds will
continue as scheduled.
See http://springframework.sourceforge.net/test/ for further
information.
|
|
From: <al...@in...> - 2005-05-23 22:30:26
|
View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20050524001621Lbuild.267 |
|
From: Scott B. <sco...@ru...> - 2005-05-23 20:10:20
|
Thanks that did the trick! Works beautifully :-D
-Scott
Erwin Vervaet wrote:
> This is caused because of the ViewResolver(s) you have registered with
> the DispatcherServlet. You don't seem to be using a
> UrlBasedViewResolver (e.g. InternalResourceViewResolver), which picks
> up on the redirect.
>
> Here's what's happening: I assume the value of the *service* string is
> "https:/<machinename>:8443/contacts-cas/j_acegi_cas_security_check".
> Since you are setting the redirect property of the view descriptor to
> true, the FlowController.toModelAndView() method will actually create
> a ModelAndView object with as a view name
> "redirect:https:/<machinename>:8443/contacts-cas/j_acegi_cas_security_check".
> This ModelAndView is passed back up to the DispatcherServlet which
> tries to resolve it using a ViewResolver, as usual in Spring MVC. If
> you have a UrlBasedViewResolver, it will recognize the "redirect:"
> prefix and construct an appropriate RedirectView to redirect to the
> specified URL.
>
> Erwin Vervaet
> erw...@er...
> ----- Original Message ----- From: "Scott Battaglia"
> <sco...@ru...>
> To: <spr...@li...>
> Sent: Monday, May 23, 2005 7:43 PM
> Subject: Re: [Springframework-developer] Spring Webflow PR3 and Redirects
>
>
>> Erwin,
>>
>> Thanks for the response.
>>
>> One more question for you: is it possible to redirect to a specific
>> url (rather than a view). I tried creating a custom view descriptor
>> creator that did the following:
>>
>> public class RedirectViewDescriptorCreator implements
>> ViewDescriptorCreator {
>>
>> public ViewDescriptor createViewDescriptor(RequestContext
>> requestContext) {
>> final String service = (String)
>> ContextUtils.getAttributeFromFlowScope(requestContext,
>> WebConstants.SERVICE);
>> final String ticket = (String)
>> ContextUtils.getAttributeFromFlowScope(requestContext,
>> WebConstants.TICKET);
>> final Map model = new HashMap();
>> model.put(WebConstants.TICKET, ticket);
>> ViewDescriptor descriptor = new ViewDescriptor(service, model);
>> descriptor.setRedirect(true);
>> return descriptor;
>> }
>> }
>>
>> However, I get a an error message: javax.servlet.ServletException:
>> Could not resolve view with name
>> 'redirect:https:/<machinename>:8443/contacts-cas/j_acegi_cas_security_check'
>> in servlet with name 'cas'
>>
>> Is there a proper way to handle redirects to URLs using Webflow?
>>
>> Thanks
>> -Scott
>>
>> Erwin Vervaet wrote:
>>
>>> Yes, that's a limitation of the current
>>> RedirectViewDescriptorCreator: it only evaluates expressions in the
>>> values of request attributes. That will certainly be made more
>>> generic with the next release.
>>>
>>> For now you could do something like this:
>>>
>>> <end-state id="redirect"
>>> view="class:com.my.CustomViewDescriptorCreator"/>
>>>
>>> and just implement a CustomViewDescriptorCreator for your case.
>>>
>>> Erwin Vervaet
>>> erw...@er...
>>> ----- Original Message ----- From: "Scott Battaglia"
>>> <sco...@ru...>
>>> To: <spr...@li...>
>>> Sent: Monday, May 23, 2005 4:41 PM
>>> Subject: [Springframework-developer] Spring Webflow PR3 and Redirects
>>>
>>>
>>>> I've just started using PR3 of Webflow (nice stuff!!) and I'm
>>>> trying to get the redirect views to work.
>>>>
>>>> It seems to be choking though on the following entry:
>>>> <end-state id="redirect"
>>>> view="redirect:${flowScope.service}?ticket=${flowScope.ticket}"/>
>>>>
>>>> Is the above a valid statement? It seems to not be evaluating the
>>>> flowScope.service.
>>>>
>>>> This is the error I get:
>>>> javax.servlet.ServletException: Could not resolve view with name
>>>> 'redirect:${flowScope.service}' in servlet with name 'cas'
>>>>
>>>> Thanks
>>>> -Scott
>>>>
>>>> --
>>>> Scott Battaglia
>>>> Application Developer, Architecture & Engineering Team
>>>> Enterprise Systems and Services, Rutgers University
>>>> v: 732.445.0097 | f: 732.445.5493 | sco...@ru...
>>>>
>>>>
>>>>
>>>> -------------------------------------------------------
>>>> This SF.Net email is sponsored by Oracle Space Sweepstakes
>>>> Want to be the first software developer in space?
>>>> Enter now for the Oracle Space Sweepstakes!
>>>> http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
>>>> _______________________________________________
>>>> Springframework-developer mailing list
>>>> Spr...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>>>
>>>>
>>>
>>>
>>>
>>> -------------------------------------------------------
>>> This SF.Net email is sponsored by Oracle Space Sweepstakes
>>> Want to be the first software developer in space?
>>> Enter now for the Oracle Space Sweepstakes!
>>> http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
>>> _______________________________________________
>>> Springframework-developer mailing list
>>> Spr...@li...
>>> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>
>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by Oracle Space Sweepstakes
>> Want to be the first software developer in space?
>> Enter now for the Oracle Space Sweepstakes!
>> http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
>> _______________________________________________
>> Springframework-developer mailing list
>> Spr...@li...
>> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>
>>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by Oracle Space Sweepstakes
> Want to be the first software developer in space?
> Enter now for the Oracle Space Sweepstakes!
> http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
|
|
From: Erwin V. <erw...@er...> - 2005-05-23 19:21:45
|
Regarding the first issue. So far we haven't really been focusing on = this kind of exception handling functionality, so I'm not sure it's = going to be in PR4. However, it is certainly a topic that's still on our = TODO list. The second issue (OSIV) is not related to SWF but should be resolved in = the Spring 1.3 timeframe since that's when Portlet support will be = included. Erwin Vervaet erw...@er... ----- Original Message -----=20 From: Boyce, Keith Garry=20 To: spr...@li...=20 Sent: Monday, May 23, 2005 9:09 PM Subject: RE: [Springframework-developer] Spring Web Flow PR3 Released So it would seem the following features aren't included in PR3: http://opensource.atlassian.com/projects/spring/browse/SPR-933 which = refers to session expiry and http://forum.springframework.org/viewtopic.php?t=3D4907&highlight=3D = which talks about OpenSessionInView interceptor for portlets... Am I right.. If so will those come in PR4? Thanks, Garry -------------------------------------------------------------------------= --- From: spr...@li... = [mailto:spr...@li...] On Behalf = Of Erwin Vervaet Sent: Monday, May 23, 2005 2:56 PM To: spr...@li... Subject: Re: [Springframework-developer] Spring Web Flow PR3 = Released Handling session timeouts? Are you talking about HTTP sessions? If = so, there is nothing in SWF related to this. Maybe you can take a look = at = javax.servlet.http.HttpSessionListener.sessionDestroyed(HttpSessionEvent = se). If you're talking about FlowSession and FlowExecution expiry, There = is not really anything like that available in SWF for the moment. = However, there is the = org.springframework.web.flow.support.ExpiredFlowCleanupFilter that will = cleanup FlowExecutions that have timed out (expired). Erwin Vervaet ----- Original Message -----=20 From: Boyce, Keith Garry=20 To: spr...@li...=20 Sent: Monday, May 23, 2005 6:43 PM Subject: RE: [Springframework-developer] Spring Web Flow PR3 = Released Is a method for handling session timeouts in this release? If so = can someone point me to the documentation? ------------------------------------------------------------------------ From: spr...@li... = [mailto:spr...@li...] On Behalf = Of Keith Donald Sent: Monday, May 23, 2005 1:46 AM To: spr...@li... Subject: [Springframework-developer] Spring Web Flow PR3 = Released Dear Spring Community, =20 I'm pleased to announce the release of Spring Web Flow Preview = 3. This is a major new release with a substantial number of new = features: both in terms of power and convenience. This release is = considered stable for development use. =20 To download, access: = http://sourceforge.net/project/showfiles.php?group_id=3D73357&package_id=3D= 148517 =20 Note: there are a few incompatible changes between PR2 and PR3. = For a listing and a porting guide, access the change log here: = http://opensource.atlassian.com/confluence/spring/display/WEBFLOW/Change+= Log =20 Contained within this release are a number of new and noteworthy = enhancements. Here are some of them: =20 View State Enhancements =20 - Each view state may now be configured with one or = more setup actions. This action is executed after the state is entered = but before control is returned to the client for response rendering. = This reduces (and in many cases eliminates) the need for setup action = states, making for more concise flow definitions. =20 - Each view state may now select the view to render and = all supporting model data in a fully dynamic, pluggable fashion using = the new ViewDescriptorCreator strategy. =20 - Powerful redirect expressions are now supported, with = full-support for resolving redirect parameters in a dynamic fashion from = the flow RequestContext. =20 Here is an example of these new features in action: =20 Setup actions =20 <view-state id=3D"displayCriteria" view=3D"criteriaView"> <setup bean=3D"searchFormAction" = method=3D"setupForm"/> <transition on=3D"submit" to=3D"executeQuery"> <action bean=3D"searchFormAction" = method=3D"bindAndValidate"/> </transition> </view-state> =20 Redirect expressions =20 <end-state id=3D"end" = view=3D"redirect:/myFlow.htm?input=3D${flowScope.input}"/> =20 Subflow Attribute Mapping Enhancements =20 - Subflow input and output mapping policies are now = fully configurable via a XML flow definition. =20 - Expressions may also be specified that resolve = subflow input attribute values in a dynamic fashion. =20 For example: =20 <attribute-mapper> <input value=3D"${sourceEvent.parameters.id}" = as=3D"id" type=3D"long"/> </attribute-mapper> =20 The expression language used is also pluggable - by default web = flow will try OGNL, if it's not found on the classpath it'll use = Spring's BeanWrapper. =20 Annotated Definition Objects =20 - In addition to action execution parameters, each core = definition object in the system--Flow, State, and Transition---can now = be annotated with arbitrary property metadata. Such properties are = specifiable in the webflow xml definition using the "property" element, = with full support for from-string type conversion with convenient type = aliasing. =20 For example: =20 <transition on=3D"submit" to=3D"executeQuery"> <property name=3D"submitPressed" value=3D"true" = type=3D"boolean"/> </transition> =20 In this case this 'submitPressed' boolean property would be made = available to this transition's target state after entering for = reasoning. =20 Enhanced Flow Execution Listener Callbacks =20 - Listeners responding to the lifecycle of an executing = flow now have more hooks to insert custom logic-notification now happens = when a flow is starting, started, paused, resumed, entering a new state, = entered a new state, or ended---with veto capability for proposed flow = state changes (to facilitate state precondition checks, for example). =20 --- =20 These are just some of the new features of this release. For a = full list of changes, see = http://opensource.atlassian.com/confluence/spring/display/WEBFLOW/Change+= Log =20 As always, we very much value your feedback. One or two more PR = releases to go and we'll be at 1.0 final! J =20 Cheers, =20 Keith Donald Erwin Vervaet =20 Interface21 - http://www.springframework.com This message is a PRIVATE communication. If you are not the intended recipient, please do not read, = copy, or use it, and do not disclose it to others. Please notify = the sender of the delivery error by replying to this message, = and then delete it from your system. Thank you. =20 This message is a PRIVATE communication. If you are not the intended recipient, please do not read, copy, or use it, and do not disclose it to others. Please notify the sender of the delivery error by replying to this message, and = then delete it from your system. Thank you. =20 |
|
From: Boyce, K. G. <Kei...@bc...> - 2005-05-23 19:11:39
|
So it would seem the following features aren't included in PR3: =0D http://opensource.atlassian.com/projects/spring/browse/SPR-933 which refers to session expiry =0D and =0D http://forum.springframework.org/viewtopic.php?t=3D4907&highlight=3D which talks about OpenSessionInView interceptor for portlets... =0D Am I right.. If so will those come in PR4? =0D Thanks, Garry _____ =0D From: spr...@li... [mailto:spr...@li...] On Behalf Of Erwin Vervaet Sent: Monday, May 23, 2005 2:56 PM To: spr...@li... Subject: Re: [Springframework-developer] Spring Web Flow PR3 Released =0D =0D Handling session timeouts? Are you talking about HTTP sessions? If so, there is nothing in SWF related to this. Maybe you can take a look at javax.servlet.http.HttpSessionListener.sessionDestroyed(HttpSessionEvent se). =0D If you're talking about FlowSession and FlowExecution expiry, There is not really anything like that available in SWF for the moment. However, there is the org.springframework.web.flow.support.ExpiredFlowCleanupFilter that will cleanup FlowExecutions that have timed out (expired). =0D Erwin Vervaet ----- Original Message -----=0D From: Boyce, Keith Garry <mailto:Kei...@bc...> =0D To: spr...@li...=0D Sent: Monday, May 23, 2005 6:43 PM Subject: RE: [Springframework-developer] Spring Web Flow PR3 Released Is a method for handling session timeouts in this release? If so can someone point me to the documentation? _____ =0D From: spr...@li... [mailto:spr...@li...] On Behalf Of Keith Donald Sent: Monday, May 23, 2005 1:46 AM To: spr...@li... Subject: [Springframework-developer] Spring Web Flow PR3 Released =0D =0D Dear Spring Community, =0D I'm pleased to announce the release of Spring Web Flow Preview 3. This is a major new release with a substantial number of new features: both in terms of power and convenience. This release is considered stable for development use. =0D To download, access: http://sourceforge.net/project/showfiles.php?group_id=3D73357&package_id= =3D1 48517 =0D Note: there are a few incompatible changes between PR2 and PR3. For a listing and a porting guide, access the change log here: http://opensource.atlassian.com/confluence/spring/display/WEBFLOW/Change +Log =0D Contained within this release are a number of new and noteworthy enhancements. Here are some of them: =0D View State Enhancements =0D - Each view state may now be configured with one or more setup actions. This action is executed after the state is entered but before control is returned to the client for response rendering. This reduces (and in many cases eliminates) the need for setup action states, making for more concise flow definitions. =0D - Each view state may now select the view to render and all supporting model data in a fully dynamic, pluggable fashion using the new ViewDescriptorCreator strategy. =0D - Powerful redirect expressions are now supported, with full-support for resolving redirect parameters in a dynamic fashion from the flow RequestContext. =0D Here is an example of these new features in action: =0D Setup actions =0D <view-state id=3D"displayCriteria" view=3D"criteriaView"> <setup bean=3D"searchFormAction" method=3D"setupForm"/> <transition on=3D"submit" to=3D"executeQuery"> <action bean=3D"searchFormAction" method=3D"bindAndValidate"/> </transition> </view-state> =0D Redirect expressions =0D <end-state id=3D"end" view=3D"redirect:/myFlow.htm?input=3D${flowScope.input}"/> =0D Subflow Attribute Mapping Enhancements =0D - Subflow input and output mapping policies are now fully configurable via a XML flow definition. =0D - Expressions may also be specified that resolve subflow input attribute values in a dynamic fashion. =0D For example: =0D <attribute-mapper> <input value=3D"${sourceEvent.parameters.id}" as=3D"id" type=3D"long"/> </attribute-mapper> =0D The expression language used is also pluggable - by default web flow will try OGNL, if it's not found on the classpath it'll use Spring's BeanWrapper. =0D Annotated Definition Objects =0D - In addition to action execution parameters, each core definition object in the system--Flow, State, and Transition---can now be annotated with arbitrary property metadata. Such properties are specifiable in the webflow xml definition using the "property" element, with full support for from-string type conversion with convenient type aliasing. =0D For example: =0D <transition on=3D"submit" to=3D"executeQuery"> <property name=3D"submitPressed" value=3D"true" type=3D"boolean"/> </transition> =0D In this case this 'submitPressed' boolean property would be made available to this transition's target state after entering for reasoning. =0D Enhanced Flow Execution Listener Callbacks =0D - Listeners responding to the lifecycle of an executing flow now have more hooks to insert custom logic-notification now happens when a flow is starting, started, paused, resumed, entering a new state, entered a new state, or ended---with veto capability for proposed flow state changes (to facilitate state precondition checks, for example). =0D --- =0D These are just some of the new features of this release. For a full list of changes, see http://opensource.atlassian.com/confluence/spring/display/WEBFLOW/Change +Log =0D As always, we very much value your feedback. One or two more PR releases to go and we'll be at 1.0 final! :-) =0D Cheers, =0D Keith Donald Erwin Vervaet =0D Interface21 - http://www.springframework.com <http://www.springframework.com/>=0D This message is a PRIVATE communication. If you are not the intended recipient, please do not read, copy, or use it, and do not disclose it to others. Please notify the sender of the delivery error by replying to this message, and then delete it from your system. Thank you. =0D This message is a PRIVATE communication. If you are not the intended recipient, please do not read, copy, or use it, and do not disclose it to others. Please notify the sender of the delivery error by replying to this message, and then delete it from your system. Thank you. |
|
From: Erwin V. <erw...@er...> - 2005-05-23 19:10:25
|
This is caused because of the ViewResolver(s) you have registered with the
DispatcherServlet. You don't seem to be using a UrlBasedViewResolver (e.g.
InternalResourceViewResolver), which picks up on the redirect.
Here's what's happening: I assume the value of the *service* string is
"https:/<machinename>:8443/contacts-cas/j_acegi_cas_security_check". Since
you are setting the redirect property of the view descriptor to true, the
FlowController.toModelAndView() method will actually create a ModelAndView
object with as a view name
"redirect:https:/<machinename>:8443/contacts-cas/j_acegi_cas_security_check".
This ModelAndView is passed back up to the DispatcherServlet which tries to
resolve it using a ViewResolver, as usual in Spring MVC. If you have a
UrlBasedViewResolver, it will recognize the "redirect:" prefix and construct
an appropriate RedirectView to redirect to the specified URL.
Erwin Vervaet
erw...@er...
----- Original Message -----
From: "Scott Battaglia" <sco...@ru...>
To: <spr...@li...>
Sent: Monday, May 23, 2005 7:43 PM
Subject: Re: [Springframework-developer] Spring Webflow PR3 and Redirects
> Erwin,
>
> Thanks for the response.
>
> One more question for you: is it possible to redirect to a specific url
> (rather than a view). I tried creating a custom view descriptor creator
> that did the following:
>
> public class RedirectViewDescriptorCreator implements
> ViewDescriptorCreator {
>
> public ViewDescriptor createViewDescriptor(RequestContext
> requestContext) {
> final String service = (String)
> ContextUtils.getAttributeFromFlowScope(requestContext,
> WebConstants.SERVICE);
> final String ticket = (String)
> ContextUtils.getAttributeFromFlowScope(requestContext,
> WebConstants.TICKET);
> final Map model = new HashMap();
> model.put(WebConstants.TICKET, ticket);
> ViewDescriptor descriptor = new ViewDescriptor(service, model);
> descriptor.setRedirect(true);
> return descriptor;
> }
> }
>
> However, I get a an error message: javax.servlet.ServletException: Could
> not resolve view with name
> 'redirect:https:/<machinename>:8443/contacts-cas/j_acegi_cas_security_check'
> in servlet with name 'cas'
>
> Is there a proper way to handle redirects to URLs using Webflow?
>
> Thanks
> -Scott
>
> Erwin Vervaet wrote:
>
>> Yes, that's a limitation of the current RedirectViewDescriptorCreator: it
>> only evaluates expressions in the values of request attributes. That will
>> certainly be made more generic with the next release.
>>
>> For now you could do something like this:
>>
>> <end-state id="redirect"
>> view="class:com.my.CustomViewDescriptorCreator"/>
>>
>> and just implement a CustomViewDescriptorCreator for your case.
>>
>> Erwin Vervaet
>> erw...@er...
>> ----- Original Message ----- From: "Scott Battaglia"
>> <sco...@ru...>
>> To: <spr...@li...>
>> Sent: Monday, May 23, 2005 4:41 PM
>> Subject: [Springframework-developer] Spring Webflow PR3 and Redirects
>>
>>
>>> I've just started using PR3 of Webflow (nice stuff!!) and I'm trying to
>>> get the redirect views to work.
>>>
>>> It seems to be choking though on the following entry:
>>> <end-state id="redirect"
>>> view="redirect:${flowScope.service}?ticket=${flowScope.ticket}"/>
>>>
>>> Is the above a valid statement? It seems to not be evaluating the
>>> flowScope.service.
>>>
>>> This is the error I get:
>>> javax.servlet.ServletException: Could not resolve view with name
>>> 'redirect:${flowScope.service}' in servlet with name 'cas'
>>>
>>> Thanks
>>> -Scott
>>>
>>> --
>>> Scott Battaglia
>>> Application Developer, Architecture & Engineering Team
>>> Enterprise Systems and Services, Rutgers University
>>> v: 732.445.0097 | f: 732.445.5493 | sco...@ru...
>>>
>>>
>>>
>>> -------------------------------------------------------
>>> This SF.Net email is sponsored by Oracle Space Sweepstakes
>>> Want to be the first software developer in space?
>>> Enter now for the Oracle Space Sweepstakes!
>>> http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
>>> _______________________________________________
>>> Springframework-developer mailing list
>>> Spr...@li...
>>> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>>
>>>
>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by Oracle Space Sweepstakes
>> Want to be the first software developer in space?
>> Enter now for the Oracle Space Sweepstakes!
>> http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
>> _______________________________________________
>> Springframework-developer mailing list
>> Spr...@li...
>> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by Oracle Space Sweepstakes
> Want to be the first software developer in space?
> Enter now for the Oracle Space Sweepstakes!
> http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
|
|
From: Erwin V. <erw...@er...> - 2005-05-23 18:53:14
|
Handling session timeouts? Are you talking about HTTP sessions? If so, =
there is nothing in SWF related to this. Maybe you can take a look at =
javax.servlet.http.HttpSessionListener.sessionDestroyed(HttpSessionEvent =
se).
If you're talking about FlowSession and FlowExecution expiry, There is =
not really anything like that available in SWF for the moment. However, =
there is the =
org.springframework.web.flow.support.ExpiredFlowCleanupFilter that will =
cleanup FlowExecutions that have timed out (expired).
Erwin Vervaet
----- Original Message -----=20
From: Boyce, Keith Garry=20
To: spr...@li...=20
Sent: Monday, May 23, 2005 6:43 PM
Subject: RE: [Springframework-developer] Spring Web Flow PR3 Released
Is a method for handling session timeouts in this release? If so can =
someone point me to the documentation?
-------------------------------------------------------------------------=
---
From: spr...@li... =
[mailto:spr...@li...] On Behalf =
Of Keith Donald
Sent: Monday, May 23, 2005 1:46 AM
To: spr...@li...
Subject: [Springframework-developer] Spring Web Flow PR3 Released
Dear Spring Community,
=20
I'm pleased to announce the release of Spring Web Flow Preview 3. =
This is a major new release with a substantial number of new features: =
both in terms of power and convenience. This release is considered =
stable for development use.
=20
To download, access: =
http://sourceforge.net/project/showfiles.php?group_id=3D73357&package_id=3D=
148517
=20
Note: there are a few incompatible changes between PR2 and PR3. For =
a listing and a porting guide, access the change log here: =
http://opensource.atlassian.com/confluence/spring/display/WEBFLOW/Change+=
Log
=20
Contained within this release are a number of new and noteworthy =
enhancements. Here are some of them:
=20
View State Enhancements
=20
- Each view state may now be configured with one or more =
setup actions. This action is executed after the state is entered but =
before control is returned to the client for response rendering. This =
reduces (and in many cases eliminates) the need for setup action states, =
making for more concise flow definitions.
=20
- Each view state may now select the view to render and all =
supporting model data in a fully dynamic, pluggable fashion using the =
new ViewDescriptorCreator strategy.
=20
- Powerful redirect expressions are now supported, with =
full-support for resolving redirect parameters in a dynamic fashion from =
the flow RequestContext.
=20
Here is an example of these new features in action:
=20
Setup actions
=20
<view-state id=3D"displayCriteria" view=3D"criteriaView">
<setup bean=3D"searchFormAction" method=3D"setupForm"/>
<transition on=3D"submit" to=3D"executeQuery">
<action bean=3D"searchFormAction" =
method=3D"bindAndValidate"/>
</transition>
</view-state>
=20
Redirect expressions
=20
<end-state id=3D"end" =
view=3D"redirect:/myFlow.htm?input=3D${flowScope.input}"/>
=20
Subflow Attribute Mapping Enhancements
=20
- Subflow input and output mapping policies are now fully =
configurable via a XML flow definition.
=20
- Expressions may also be specified that resolve subflow =
input attribute values in a dynamic fashion.
=20
For example:
=20
<attribute-mapper>
<input value=3D"${sourceEvent.parameters.id}" as=3D"id" =
type=3D"long"/>
</attribute-mapper>
=20
The expression language used is also pluggable - by default web flow =
will try OGNL, if it's not found on the classpath it'll use Spring's =
BeanWrapper.
=20
Annotated Definition Objects
=20
- In addition to action execution parameters, each core =
definition object in the system--Flow, State, and Transition---can now =
be annotated with arbitrary property metadata. Such properties are =
specifiable in the webflow xml definition using the "property" element, =
with full support for from-string type conversion with convenient type =
aliasing.
=20
For example:
=20
<transition on=3D"submit" to=3D"executeQuery">
<property name=3D"submitPressed" value=3D"true" =
type=3D"boolean"/>
</transition>
=20
In this case this 'submitPressed' boolean property would be made =
available to this transition's target state after entering for =
reasoning.
=20
Enhanced Flow Execution Listener Callbacks
=20
- Listeners responding to the lifecycle of an executing =
flow now have more hooks to insert custom logic-notification now happens =
when a flow is starting, started, paused, resumed, entering a new state, =
entered a new state, or ended---with veto capability for proposed flow =
state changes (to facilitate state precondition checks, for example).
=20
---
=20
These are just some of the new features of this release. For a full =
list of changes, see =
http://opensource.atlassian.com/confluence/spring/display/WEBFLOW/Change+=
Log
=20
As always, we very much value your feedback. One or two more PR =
releases to go and we'll be at 1.0 final! J
=20
Cheers,
=20
Keith Donald
Erwin Vervaet
=20
Interface21 - http://www.springframework.com
This message is a PRIVATE communication.
If you are not the intended recipient, please do not read, copy,
or use it, and do not disclose it to others. Please notify the
sender of the delivery error by replying to this message, and =
then
delete it from your system. Thank you.
=20
|
|
From: Shinobu K. <shi...@gm...> - 2005-05-23 17:59:00
|
Hi Achmad, > Hi guys, is there any idea how to integrate velocity-view-tool especially > $import , into springMacroRequestContext ?=20 From Spring 1.2, you can use the VelocityToolboxView, which adds toolbox support to the VelocityView. http://static.springframework.org/spring/docs/1.2/api/org/springframework= /web/servlet/view/velocity/VelocityToolboxView.html ## But there might be a way to inject tools from the ApplicationContext. I'm still new to Spring. Best regards, -- Shinobu -- Shinobu Kawai <shi...@gm...> |
|
From: Scott B. <sco...@ru...> - 2005-05-23 17:43:14
|
Erwin,
Thanks for the response.
One more question for you: is it possible to redirect to a specific url
(rather than a view). I tried creating a custom view descriptor creator
that did the following:
public class RedirectViewDescriptorCreator implements
ViewDescriptorCreator {
public ViewDescriptor createViewDescriptor(RequestContext
requestContext) {
final String service = (String)
ContextUtils.getAttributeFromFlowScope(requestContext,
WebConstants.SERVICE);
final String ticket = (String)
ContextUtils.getAttributeFromFlowScope(requestContext, WebConstants.TICKET);
final Map model = new HashMap();
model.put(WebConstants.TICKET, ticket);
ViewDescriptor descriptor = new ViewDescriptor(service, model);
descriptor.setRedirect(true);
return descriptor;
}
}
However, I get a an error message: javax.servlet.ServletException: Could
not resolve view with name
'redirect:https:/<machinename>:8443/contacts-cas/j_acegi_cas_security_check'
in servlet with name 'cas'
Is there a proper way to handle redirects to URLs using Webflow?
Thanks
-Scott
Erwin Vervaet wrote:
> Yes, that's a limitation of the current RedirectViewDescriptorCreator:
> it only evaluates expressions in the values of request attributes.
> That will certainly be made more generic with the next release.
>
> For now you could do something like this:
>
> <end-state id="redirect"
> view="class:com.my.CustomViewDescriptorCreator"/>
>
> and just implement a CustomViewDescriptorCreator for your case.
>
> Erwin Vervaet
> erw...@er...
> ----- Original Message ----- From: "Scott Battaglia"
> <sco...@ru...>
> To: <spr...@li...>
> Sent: Monday, May 23, 2005 4:41 PM
> Subject: [Springframework-developer] Spring Webflow PR3 and Redirects
>
>
>> I've just started using PR3 of Webflow (nice stuff!!) and I'm trying
>> to get the redirect views to work.
>>
>> It seems to be choking though on the following entry:
>> <end-state id="redirect"
>> view="redirect:${flowScope.service}?ticket=${flowScope.ticket}"/>
>>
>> Is the above a valid statement? It seems to not be evaluating the
>> flowScope.service.
>>
>> This is the error I get:
>> javax.servlet.ServletException: Could not resolve view with name
>> 'redirect:${flowScope.service}' in servlet with name 'cas'
>>
>> Thanks
>> -Scott
>>
>> --
>> Scott Battaglia
>> Application Developer, Architecture & Engineering Team
>> Enterprise Systems and Services, Rutgers University
>> v: 732.445.0097 | f: 732.445.5493 | sco...@ru...
>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by Oracle Space Sweepstakes
>> Want to be the first software developer in space?
>> Enter now for the Oracle Space Sweepstakes!
>> http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
>> _______________________________________________
>> Springframework-developer mailing list
>> Spr...@li...
>> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>
>>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by Oracle Space Sweepstakes
> Want to be the first software developer in space?
> Enter now for the Oracle Space Sweepstakes!
> http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
|
|
From: Darren D. <da...@sh...> - 2005-05-23 17:41:18
|
1116870074
FAILED
[attribute-compiler] /var/local/home/users/d/da/davison/checkouts/spring/test/org/springframework/aop/framework/AbstractAopProxyTests.java --> TrapTargetInterceptor qualified to org.springframework.aop.framework.TrapTargetInterceptor
[attribute-compiler] /var/local/home/users/d/da/davison/checkouts/spring/test/org/springframework/aop/framework/AbstractAopProxyTests.java --> AdvisedSupportListener qualified to org.springframework.aop.framework.AdvisedSupportListener
[attribute-compiler] /var/local/home/users/d/da/davison/checkouts/spring/test/org/springframework/aop/framework/AbstractAopProxyTests.java --> AdvisorChainFactory qualified to org.springframework.aop.framework.AdvisorChainFactory
[attribute-compiler] /var/local/home/users/d/da/davison/checkouts/spring/test/org/springframework/aop/framework/JdkDynamicProxyTests.java --> TrapTargetInterceptor qualified to org.springframework.aop.framework.TrapTargetInterceptor
[attribute-compiler] /var/local/home/users/d/da/davison/checkouts/spring/test/org/springframework/beans/factory/DummyFactory.java --> FactoryBean qualified to org.springframework.beans.factory.FactoryBean
[attribute-compiler] /var/local/home/users/d/da/davison/checkouts/spring/test/org/springframework/beans/factory/DummyFactory.java --> BeanNameAware qualified to org.springframework.beans.factory.BeanNameAware
[attribute-compiler] /var/local/home/users/d/da/davison/checkouts/spring/test/org/springframework/beans/factory/DummyFactory.java --> BeanFactoryAware qualified to org.springframework.beans.factory.BeanFactoryAware
[attribute-compiler] /var/local/home/users/d/da/davison/checkouts/spring/test/org/springframework/beans/factory/DummyFactory.java --> InitializingBean qualified to org.springframework.beans.factory.InitializingBean
[attribute-compiler] /var/local/home/users/d/da/davison/checkouts/spring/test/org/springframework/beans/factory/DummyFactory.java --> DisposableBean qualified to org.springframework.beans.factory.DisposableBean
[attribute-compiler] /var/local/home/users/d/da/davison/checkouts/spring/test/org/springframework/aop/framework/autoproxy/AutoProxyCreatorTests.java --> AbstractAutoProxyCreator qualified to org.springframework.aop.framework.autoproxy.AbstractAutoProxyCreator
[attribute-compiler] /var/local/home/users/d/da/davison/checkouts/spring/test/org/springframework/aop/support/AopUtilsTests.java --> StaticMethodMatcherPointcut qualified to org.springframework.aop.support.StaticMethodMatcherPointcut
[attribute-compiler] /var/local/home/users/d/da/davison/checkouts/spring/test/org/springframework/aop/support/AopUtilsTests.java --> DynamicMethodMatcherPointcut qualified to org.springframework.aop.support.DynamicMethodMatcherPointcut
[attribute-compiler] /var/local/home/users/d/da/davison/checkouts/spring/test/org/springframework/aop/support/AopUtilsTests.java --> DynamicMethodMatcherPointcutAdvisor qualified to org.springframework.aop.support.DynamicMethodMatcherPointcutAdvisor
[attribute-compiler] /var/local/home/users/d/da/davison/checkouts/spring/test/org/springframework/aop/support/ComposablePointcutTests.java --> StaticMethodMatcher qualified to org.springframework.aop.support.StaticMethodMatcher
[attribute-compiler] /var/local/home/users/d/da/davison/checkouts/spring/test/org/springframework/aop/support/DelegatingIntroductionInterceptorTests.java --> ITest qualified to org.springframework.aop.support.ITest
[attribute-compiler] /var/local/home/users/d/da/davison/checkouts/spring/test/org/springframework/aop/support/DelegatingIntroductionInterceptorTests.java --> DelegatingIntroductionInterceptor qualified to org.springframework.aop.support.DelegatingIntroductionInterceptor
[attribute-compiler] /var/local/home/users/d/da/davison/checkouts/spring/test/org/springframework/aop/support/MethodMatchersTests.java --> StaticMethodMatcher qualified to org.springframework.aop.support.StaticMethodMatcher
[attribute-compiler] /var/local/home/users/d/da/davison/checkouts/spring/test/org/springframework/aop/support/MethodMatchersTests.java --> DynamicMethodMatcher qualified to org.springframework.aop.support.DynamicMethodMatcher
[attribute-compiler] /var/local/home/users/d/da/davison/checkouts/spring/test/org/springframework/aop/support/PointcutsTests.java --> StaticMethodMatcherPointcut qualified to org.springframework.aop.support.StaticMethodMatcherPointcut
[attribute-compiler] /var/local/home/users/d/da/davison/checkouts/spring/test/org/springframework/aop/target/PrototypeBasedTargetSourceTests.java --> AbstractPrototypeBasedTargetSource qualified to org.springframework.aop.target.AbstractPrototypeBasedTargetSource
buildmaintests:
[mkdir] Created dir: /var/local/home/users/d/da/davison/checkouts/spring/target/x86-linux2/test-classes
[javac] Compiling 439 source files to /var/local/home/users/d/da/davison/checkouts/spring/target/x86-linux2/test-classes
[javac] /var/local/home/users/d/da/davison/checkouts/spring/test/org/springframework/web/util/ExpressionEvaluationUtilsTests.java:29: error while writing org.springframework.web.util.ExpressionEvaluationUtilsTests: /var/local/home/users/d/da/davison/checkouts/spring/target/x86-linux2/test-classes/org/springframework/web/util/ExpressionEvaluationUtilsTests.class (No such file or directory)
[javac] public class ExpressionEvaluationUtilsTests extends TestCase {
[javac] ^
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -deprecation for details.
[javac] 1 error
This is an automated mail from one of the SF Compile Farm machines.
The machine name noted in the subject encountered a failure building
or running the Spring test suite. The last few lines of the output
were included for info.
NB: No further mail will be sent from this machine until a
manual reset occurs on the cf-shell machine, although builds will
continue as scheduled.
See http://springframework.sourceforge.net/test/ for further
information.
|
|
From: Boyce, K. G. <Kei...@bc...> - 2005-05-23 16:45:05
|
Is a method for handling session timeouts in this release? If so can someone point me to the documentation? _____ =0D From: spr...@li... [mailto:spr...@li...] On Behalf Of Keith Donald Sent: Monday, May 23, 2005 1:46 AM To: spr...@li... Subject: [Springframework-developer] Spring Web Flow PR3 Released =0D =0D Dear Spring Community, =0D I'm pleased to announce the release of Spring Web Flow Preview 3. This is a major new release with a substantial number of new features: both in terms of power and convenience. This release is considered stable for development use. =0D To download, access: http://sourceforge.net/project/showfiles.php?group_id=3D73357&package_id= =3D1 48517 =0D Note: there are a few incompatible changes between PR2 and PR3. For a listing and a porting guide, access the change log here: http://opensource.atlassian.com/confluence/spring/display/WEBFLOW/Change +Log =0D Contained within this release are a number of new and noteworthy enhancements. Here are some of them: =0D View State Enhancements =0D - Each view state may now be configured with one or more setup actions. This action is executed after the state is entered but before control is returned to the client for response rendering. This reduces (and in many cases eliminates) the need for setup action states, making for more concise flow definitions. =0D - Each view state may now select the view to render and all supporting model data in a fully dynamic, pluggable fashion using the new ViewDescriptorCreator strategy. =0D - Powerful redirect expressions are now supported, with full-support for resolving redirect parameters in a dynamic fashion from the flow RequestContext. =0D Here is an example of these new features in action: =0D Setup actions =0D <view-state id=3D"displayCriteria" view=3D"criteriaView"> <setup bean=3D"searchFormAction" method=3D"setupForm"/> <transition on=3D"submit" to=3D"executeQuery"> <action bean=3D"searchFormAction" method=3D"bindAndValidate"/> </transition> </view-state> =0D Redirect expressions =0D <end-state id=3D"end" view=3D"redirect:/myFlow.htm?input=3D${flowScope.input}"/> =0D Subflow Attribute Mapping Enhancements =0D - Subflow input and output mapping policies are now fully configurable via a XML flow definition. =0D - Expressions may also be specified that resolve subflow input attribute values in a dynamic fashion. =0D For example: =0D <attribute-mapper> <input value=3D"${sourceEvent.parameters.id}" as=3D"id" type=3D"long"/> </attribute-mapper> =0D The expression language used is also pluggable - by default web flow will try OGNL, if it's not found on the classpath it'll use Spring's BeanWrapper. =0D Annotated Definition Objects =0D - In addition to action execution parameters, each core definition object in the system--Flow, State, and Transition---can now be annotated with arbitrary property metadata. Such properties are specifiable in the webflow xml definition using the "property" element, with full support for from-string type conversion with convenient type aliasing. =0D For example: =0D <transition on=3D"submit" to=3D"executeQuery"> <property name=3D"submitPressed" value=3D"true" type=3D"boolean"/> </transition> =0D In this case this 'submitPressed' boolean property would be made available to this transition's target state after entering for reasoning. =0D Enhanced Flow Execution Listener Callbacks =0D - Listeners responding to the lifecycle of an executing flow now have more hooks to insert custom logic-notification now happens when a flow is starting, started, paused, resumed, entering a new state, entered a new state, or ended---with veto capability for proposed flow state changes (to facilitate state precondition checks, for example). =0D --- =0D These are just some of the new features of this release. For a full list of changes, see http://opensource.atlassian.com/confluence/spring/display/WEBFLOW/Change +Log =0D As always, we very much value your feedback. One or two more PR releases to go and we'll be at 1.0 final! :-) =0D Cheers, =0D Keith Donald Erwin Vervaet =0D Interface21 - http://www.springframework.com <http://www.springframework.com/>=0D This message is a PRIVATE communication. If you are not the intended recipient, please do not read, copy, or use it, and do not disclose it to others. Please notify the sender of the delivery error by replying to this message, and then delete it from your system. Thank you. |
|
From: Boyce, K. G. <Kei...@bc...> - 2005-05-23 16:12:35
|
That fixed it... =0D Thanks, Garry _____ =0D From: spr...@li... [mailto:spr...@li...] On Behalf Of Juergen Hoeller Sent: Monday, May 23, 2005 11:59 AM To: spr...@li... Subject: Re: [Springframework-developer] Spring Web Flow PR3 Released =0D =0D Oops... looks like you've been caught by a recent change in the Portlet support, following a refinement in Spring core 1.2.1. Essentially, DispatcherPortlet is trying to use a new ConfigurableBeanFactory method which has been introduced in Spring 1.2.1. =0D I'm afraid you will have to wait for Spring 1.2.1 (scheduled for this Friday) to make Web Flow PR3 work in a Portlet environment, or use a recent nightly 1.2.1 snapshot in combination with Web Flow PR3. =0D Juergen =0D =0D -----Original Message----- From: spr...@li... [mailto:spr...@li...]On Behalf Of Boyce, Keith Garry Sent: Monday, May 23, 2005 5:25 PM To: spr...@li... Subject: RE: [Springframework-developer] Spring Web Flow PR3 Released =0D =0D Go following error after upgrade... Any ideas? =0D Encountered the following problem(s) while attempting to render portlet fragment: dp-22 Failed to load portlet org.springframework.web.portlet.DispatcherPortlet: java.lang.NoSuchMethodError: org.springframework.beans.factory.config.ConfigurableListableBeanFactory .ignoreDependencyInterface(Ljava/lang/Class;)V=0D This message is a PRIVATE communication. If you are not the intended recipient, please do not read, copy, or use it, and do not disclose it to others. Please notify the sender of the delivery error by replying to this message, and then delete it from your system. Thank you. =0D This message is a PRIVATE communication. If you are not the intended recipient, please do not read, copy, or use it, and do not disclose it to others. Please notify the sender of the delivery error by replying to this message, and then delete it from your system. Thank you. |
|
From: Juergen H. <ju...@in...> - 2005-05-23 15:59:41
|
Oops... looks like you've been caught by a recent change in the Portlet
support, following a refinement in Spring core 1.2.1. Essentially,
DispatcherPortlet is trying to use a new ConfigurableBeanFactory method
which has been introduced in Spring 1.2.1.
I'm afraid you will have to wait for Spring 1.2.1 (scheduled for this
Friday) to make Web Flow PR3 work in a Portlet environment, or use a recent
nightly 1.2.1 snapshot in combination with Web Flow PR3.
Juergen
-----Original Message-----
From: spr...@li...
[mailto:spr...@li...]On Behalf Of
Boyce, Keith Garry
Sent: Monday, May 23, 2005 5:25 PM
To: spr...@li...
Subject: RE: [Springframework-developer] Spring Web Flow PR3 Released
Go following error after upgrade... Any ideas?
Encountered the following problem(s) while attempting to render portlet
fragment: dp-22
Failed to load portlet org.springframework.web.portlet.DispatcherPortlet:
java.lang.NoSuchMethodError:
org.springframework.beans.factory.config.ConfigurableListableBeanFactory.ign
oreDependencyInterface(Ljava/lang/Class;)V
This message is a PRIVATE communication.
If you are not the intended recipient, please do not read, copy,
or use it, and do not disclose it to others. Please notify the
sender of the delivery error by replying to this message, and then
delete it from your system. Thank you.
|
|
From: Thomas R. <tho...@tr...> - 2005-05-23 15:38:14
|
NoSuchMethodError is usually caused by older jar files still accessible on the classpath. Search for any old spring.jar files. Thomas On May 23, 2005, at 11:25 AM, Boyce, Keith Garry wrote: > NoSuchMethodError |
|
From: Boyce, K. G. <Kei...@bc...> - 2005-05-23 15:27:04
|
Go following error after upgrade... Any ideas? =0D Encountered the following problem(s) while attempting to render portlet fragment: dp-22 Failed to load portlet org.springframework.web.portlet.DispatcherPortlet: java.lang.NoSuchMethodError: org.springframework.beans.factory.config.ConfigurableListableBeanFactory .ignoreDependencyInterface(Ljava/lang/Class;)V=0D This message is a PRIVATE communication. If you are not the intended recipient, please do not read, copy, or use it, and do not disclose it to others. Please notify the sender of the delivery error by replying to this message, and then delete it from your system. Thank you. |
|
From: Erwin V. <erw...@er...> - 2005-05-23 15:00:18
|
Yes, that's a limitation of the current RedirectViewDescriptorCreator: it
only evaluates expressions in the values of request attributes. That will
certainly be made more generic with the next release.
For now you could do something like this:
<end-state id="redirect" view="class:com.my.CustomViewDescriptorCreator"/>
and just implement a CustomViewDescriptorCreator for your case.
Erwin Vervaet
erw...@er...
----- Original Message -----
From: "Scott Battaglia" <sco...@ru...>
To: <spr...@li...>
Sent: Monday, May 23, 2005 4:41 PM
Subject: [Springframework-developer] Spring Webflow PR3 and Redirects
> I've just started using PR3 of Webflow (nice stuff!!) and I'm trying to
> get the redirect views to work.
>
> It seems to be choking though on the following entry:
> <end-state id="redirect"
> view="redirect:${flowScope.service}?ticket=${flowScope.ticket}"/>
>
> Is the above a valid statement? It seems to not be evaluating the
> flowScope.service.
>
> This is the error I get:
> javax.servlet.ServletException: Could not resolve view with name
> 'redirect:${flowScope.service}' in servlet with name 'cas'
>
> Thanks
> -Scott
>
> --
> Scott Battaglia
> Application Developer, Architecture & Engineering Team
> Enterprise Systems and Services, Rutgers University
> v: 732.445.0097 | f: 732.445.5493 | sco...@ru...
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by Oracle Space Sweepstakes
> Want to be the first software developer in space?
> Enter now for the Oracle Space Sweepstakes!
> http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
|
|
From: Scott B. <sco...@ru...> - 2005-05-23 14:41:30
|
I've just started using PR3 of Webflow (nice stuff!!) and I'm trying to
get the redirect views to work.
It seems to be choking though on the following entry:
<end-state id="redirect"
view="redirect:${flowScope.service}?ticket=${flowScope.ticket}"/>
Is the above a valid statement? It seems to not be evaluating the
flowScope.service.
This is the error I get:
javax.servlet.ServletException: Could not resolve view with name
'redirect:${flowScope.service}' in servlet with name 'cas'
Thanks
-Scott
--
Scott Battaglia
Application Developer, Architecture & Engineering Team
Enterprise Systems and Services, Rutgers University
v: 732.445.0097 | f: 732.445.5493 | sco...@ru...
|
|
From: Rob H. <rob...@in...> - 2005-05-23 14:29:15
|
Dear Spring community, I am pleased to announce that Spring Modules 0.2 has just been released. Downloads can be found at: http://springmodules.dev.java.net. This release includes: * Improved OSWorkflow integration with the OSWorkflowTemplate * Integration of Wanghy Cache under the new Spring Modules Cache banner * JDK 5.0 Annotations support for Cache * OSWorkflow sample application * Improved test coverage For a detailed list of features, see the changelog. The OSWorkflow support is considered to be reasonably stable although feedback about the API will be warmly welcomed. The overhaul to JSR-94 session handling had to be delayed to 0.3 because of time constraints and the need to get the Cache module out of the door. We are planning to release 0.3 within the next three weeks, hopefully with Spring 1.2.1 included. Notable features scheduled for 0.3 are Lucene support, our own validation language: Valang, JSR-94 session handling overhaul and improvements to Commons Validator support. The full roadmap can be found at: http://opensource.atlassian.com/projects/spring/secure/BrowseProject.jspa?id =10030&report=roadmap. We are still looking to recruit more developers to work on more modules, and any feedback on new or existing features will be much appreciated. Regards, Rob -- Rob Harrop Interface21 - Spring Services from the Source http://www.springframework.com |
|
From: Juergen H. <ju...@in...> - 2005-05-23 13:55:46
|
Actually, according to the CVS history of spring-beans.dtd, this has already been relaxed for Spring 1.1.4. Do you maybe have an old spring-beans.dtd around in your class path or IDE? The spring-beans.dtd as shipped in spring.jar should allow for arbitrary order of the sub elements there... You could also check the spring-beand.dtd file in the dist directory of your Spring distribution. Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...]On Behalf Of Tim Kettering Sent: Monday, May 23, 2005 3:47 PM To: spr...@li... Subject: RE: [Springframework-developer] order of lookup-method in bean declaration important? Well, apparently it isn't working for me under spring 1.2 (RC2). We haven't updated our project to 1.2 final yet. I will give that a try today, but here is the exception stack trace I'm getting (see below). ----- Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: Line 72 in XML document from resource [/WEB-INF/TopicPortlet-portlet.xml] of PortletContext is invalid; nested exception is org.xml.sax.SAXParseException: Element "bean" does not allow "property" here. at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefini tions(XmlBeanDefinitionReader.java:152) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadB eanDefinitions(AbstractBeanDefinitionReader.java:99) at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDe finitions(AbstractXmlApplicationContext.java:102) at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDe finitions(AbstractXmlApplicationContext.java:70) at org.springframework.context.support.AbstractRefreshableApplicationContext.re freshBeanFactory(AbstractRefreshableApplicationContext.java:87) at org.springframework.context.support.AbstractApplicationContext.refresh(Abstr actApplicationContext.java:262) at org.springframework.web.portlet.context.support.XmlPortletApplicationContext .refresh(XmlPortletApplicationContext.java:132) at org.springframework.web.portlet.FrameworkPortlet.createPortletApplicationCon text(FrameworkPortlet.java:315) at org.springframework.web.portlet.FrameworkPortlet.initPortletApplicationConte xt(FrameworkPortlet.java:260) at org.springframework.web.portlet.FrameworkPortlet.initPortletBean(FrameworkPo rtlet.java:230) at org.springframework.web.portlet.PortletBean.init(PortletBean.java:95) at javax.portlet.GenericPortlet.init(GenericPortlet.java:98) at org.apache.pluto.core.PortletServlet.init(PortletServlet.java:93) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:10 91) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:750) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher. java:641) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatch er.java:574) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher .java:499) at org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.j ava:120) ... 89 more Caused by: org.xml.sax.SAXParseException: Element "bean" does not allow "property" here. at org.apache.crimson.parser.Parser2.error(Parser2.java:3354) at org.apache.crimson.parser.ValidatingParser$ChildrenValidator.consume(Validat ingParser.java:349) at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1497) at org.apache.crimson.parser.Parser2.content(Parser2.java:1963) at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691) at org.apache.crimson.parser.Parser2.content(Parser2.java:1963) at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691) at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:667) at org.apache.crimson.parser.Parser2.parse(Parser2.java:337) at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448) at org.apache.crimson.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:1 85) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:76) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefini tions(XmlBeanDefinitionReader.java:145) ... 107 more -----Original Message----- From: spr...@li... [mailto:spr...@li...] On Behalf Of Juergen Hoeller Sent: Monday, May 23, 2005 9:30 AM To: spr...@li... Subject: Re: [Springframework-developer] order of lookup-method in bean declaration important? Ah yes, that has changed as of Spring 1.2. But that at least means that upgrading to Spring 1.2 should help :-) Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...]On Behalf Of Christopher Harris Sent: Monday, May 23, 2005 2:39 PM To: spr...@li... Subject: Re: [Springframework-developer] order of lookup-method in bean declaration important? Juergen, I get the same problem when using spring 1.1.2. It is caused by the definition of the bean element within the spring-bean.dtd within the spring-core.jar: <!ELEMENT bean ( description?, (constructor-arg | property)*, (lookup-method | replaced-method)* )> Looks as if the spring-bean.dtd has been changed within the 1.2. Hope that helps. Chris. From: "Juergen Hoeller" <ju...@in...> Reply-To: spr...@li... To: <spr...@li...> Subject: Re: [Springframework-developer] order of lookup-method in bean declaration important? Date: Mon, 23 May 2005 11:59:04 +0200 Tim, The order of <bean> sub elements should not matter, with the sole exception of <description> which needs to be first. What kind of error do you get when you place your <lookup-method> tag before your <property> tag? Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...]On Behalf Of Tim Kettering Sent: Thursday, May 19, 2005 11:21 PM To: spr...@li... Subject: [Springframework-developer] order of lookup-method in bean declaration important? Hi, I was looking into integrating lookup-method in my context, and I was using the reference found here: http://static.springframework.org/spring/docs/1.2/reference/beans.html#beans -factory-method-injection After much tussling around with some weird XML error, and looking at some other examples pasted in the forums, I moved the <lookup-method> tag to appear after the <property> tags, and it all worked after that. So I think the example in the reference is misleading, since it places the <lookup-method> tag before the <property> tag, which apparently does not work for me (in Spring 1.2). So, does the order matter? If so, the reference example should be updated and the text to clearly state in what order it should appear in the <bean> declaration. Thanks. -tim ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Tim K. <tim...@vi...> - 2005-05-23 13:46:31
|
Well, apparently it isn't working for me under spring 1.2 (RC2). We haven't updated our project to 1.2 final yet. I will give that a try today, but here is the exception stack trace I'm getting (see below). ----- Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: Line 72 in XML document from resource [/WEB-INF/TopicPortlet-portlet.xml] of PortletContext is invalid; nested exception is org.xml.sax.SAXParseException: Element "bean" does not allow "property" here. at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefini tions(XmlBeanDefinitionReader.java:152) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadB eanDefinitions(AbstractBeanDefinitionReader.java:99) at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDe finitions(AbstractXmlApplicationContext.java:102) at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDe finitions(AbstractXmlApplicationContext.java:70) at org.springframework.context.support.AbstractRefreshableApplicationContext.re freshBeanFactory(AbstractRefreshableApplicationContext.java:87) at org.springframework.context.support.AbstractApplicationContext.refresh(Abstr actApplicationContext.java:262) at org.springframework.web.portlet.context.support.XmlPortletApplicationContext .refresh(XmlPortletApplicationContext.java:132) at org.springframework.web.portlet.FrameworkPortlet.createPortletApplicationCon text(FrameworkPortlet.java:315) at org.springframework.web.portlet.FrameworkPortlet.initPortletApplicationConte xt(FrameworkPortlet.java:260) at org.springframework.web.portlet.FrameworkPortlet.initPortletBean(FrameworkPo rtlet.java:230) at org.springframework.web.portlet.PortletBean.init(PortletBean.java:95) at javax.portlet.GenericPortlet.init(GenericPortlet.java:98) at org.apache.pluto.core.PortletServlet.init(PortletServlet.java:93) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:10 91) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:750) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher. java:641) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatch er.java:574) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher .java:499) at org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.j ava:120) ... 89 more Caused by: org.xml.sax.SAXParseException: Element "bean" does not allow "property" here. at org.apache.crimson.parser.Parser2.error(Parser2.java:3354) at org.apache.crimson.parser.ValidatingParser$ChildrenValidator.consume(Validat ingParser.java:349) at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1497) at org.apache.crimson.parser.Parser2.content(Parser2.java:1963) at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691) at org.apache.crimson.parser.Parser2.content(Parser2.java:1963) at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691) at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:667) at org.apache.crimson.parser.Parser2.parse(Parser2.java:337) at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448) at org.apache.crimson.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:1 85) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:76) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefini tions(XmlBeanDefinitionReader.java:145) ... 107 more -----Original Message----- From: spr...@li... [mailto:spr...@li...] On Behalf Of Juergen Hoeller Sent: Monday, May 23, 2005 9:30 AM To: spr...@li... Subject: Re: [Springframework-developer] order of lookup-method in bean declaration important? Ah yes, that has changed as of Spring 1.2. But that at least means that upgrading to Spring 1.2 should help :-) Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...]On Behalf Of Christopher Harris Sent: Monday, May 23, 2005 2:39 PM To: spr...@li... Subject: Re: [Springframework-developer] order of lookup-method in bean declaration important? Juergen, I get the same problem when using spring 1.1.2. It is caused by the definition of the bean element within the spring-bean.dtd within the spring-core.jar: <!ELEMENT bean ( description?, (constructor-arg | property)*, (lookup-method | replaced-method)* )> Looks as if the spring-bean.dtd has been changed within the 1.2. Hope that helps. Chris. From: "Juergen Hoeller" <ju...@in...> Reply-To: spr...@li... To: <spr...@li...> Subject: Re: [Springframework-developer] order of lookup-method in bean declaration important? Date: Mon, 23 May 2005 11:59:04 +0200 Tim, The order of <bean> sub elements should not matter, with the sole exception of <description> which needs to be first. What kind of error do you get when you place your <lookup-method> tag before your <property> tag? Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...]On Behalf Of Tim Kettering Sent: Thursday, May 19, 2005 11:21 PM To: spr...@li... Subject: [Springframework-developer] order of lookup-method in bean declaration important? Hi, I was looking into integrating lookup-method in my context, and I was using the reference found here: http://static.springframework.org/spring/docs/1.2/reference/beans.html#beans -factory-method-injection After much tussling around with some weird XML error, and looking at some other examples pasted in the forums, I moved the <lookup-method> tag to appear after the <property> tags, and it all worked after that. So I think the example in the reference is misleading, since it places the <lookup-method> tag before the <property> tag, which apparently does not work for me (in Spring 1.2). So, does the order matter? If so, the reference example should be updated and the text to clearly state in what order it should appear in the <bean> declaration. Thanks. -tim ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Juergen H. <ju...@in...> - 2005-05-23 13:30:19
|
Ah yes, that has changed as of Spring 1.2. But that at least means that upgrading to Spring 1.2 should help :-) Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...]On Behalf Of Christopher Harris Sent: Monday, May 23, 2005 2:39 PM To: spr...@li... Subject: Re: [Springframework-developer] order of lookup-method in bean declaration important? Juergen, I get the same problem when using spring 1.1.2. It is caused by the definition of the bean element within the spring-bean.dtd within the spring-core.jar: <!ELEMENT bean ( description?, (constructor-arg | property)*, (lookup-method | replaced-method)* )> Looks as if the spring-bean.dtd has been changed within the 1.2. Hope that helps. Chris. From: "Juergen Hoeller" <ju...@in...> Reply-To: spr...@li... To: <spr...@li...> Subject: Re: [Springframework-developer] order of lookup-method in bean declaration important? Date: Mon, 23 May 2005 11:59:04 +0200 Tim, The order of <bean> sub elements should not matter, with the sole exception of <description> which needs to be first. What kind of error do you get when you place your <lookup-method> tag before your <property> tag? Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...]On Behalf Of Tim Kettering Sent: Thursday, May 19, 2005 11:21 PM To: spr...@li... Subject: [Springframework-developer] order of lookup-method in bean declaration important? Hi, I was looking into integrating lookup-method in my context, and I was using the reference found here: http://static.springframework.org/spring/docs/1.2/reference/beans.html#beans -factory-method-injection After much tussling around with some weird XML error, and looking at some other examples pasted in the forums, I moved the <lookup-method> tag to appear after the <property> tags, and it all worked after that. So I think the example in the reference is misleading, since it places the <lookup-method> tag before the <property> tag, which apparently does not work for me (in Spring 1.2). So, does the order matter? If so, the reference example should be updated and the text to clearly state in what order it should appear in the <bean> declaration. Thanks. -tim ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
1239 messages has been excluded from this view by a project administrator.
