[appfuse-user] Quick Question About Spring & Hibernate

[Doug Pham]

You may have ran across this along the way.  Each time I used the DAO to make a 
call, the session seems to get closed.  If I used the OpenViewFilter, the 
session is open, but it's in a READ-ONLY mode.  I know I am not posting any 
code here, but has anyone ran across this and have a correct way of setting 
this?

Thanks,
Doug

   
-
Be a better friend, newshound, and know-it-all with Yahoo! Mobile.  Try it now.

Re: [appfuse-user] Quick Question About Spring & Hibernate

[Michael Courcy]

Open session in view is meant to be read-only.

When the call to the manager return  (inside the controller) the 
transaction is commited  and the transactionManager change its flushMode 
temporaly to reset it just after to never  (Aka read only),  thus when 
the control is passed to rendering  the transaction is back in  read 
only mode.


This is taken from the javadoc of OSVF :

* NOTE: This filter will by default not flush the 
Hibernate Session,
* with the flush mode set to FlushMode.NEVER. It assumes 
to be used
* in combination with service layer transactions that care for the 
flushing: The

* active transaction manager will temporarily change the flush mode to
* FlushMode.AUTO during a read-write transaction, with the 
flush
* mode reset to FlushMode.NEVER at the end of each 
transaction.

* If you intend to use this filter without transactions, consider changing
* the default flush mode (through the "flushMode" property).

Cheers

Doug Pham a écrit :
You may have ran across this along the way.  Each time I used the DAO 
to make a call, the session seems to get closed.  If I used the 
OpenViewFilter, the session is open, but it's in a READ-ONLY mode.  I 
know I am not posting any code here, but has anyone ran across this 
and have a correct way of setting this?


Thanks,
Doug


Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try 
it now. 
 




--
Michael Courcy
http://courcy.blogspot.com
http://courcy-en.blogspot.com



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [appfuse-user] AspectJ 1.6 issues, when is appfuse 2.02 coming out?

[mschipperheyn]

Darn, tried that. And..no spring archetype snapshot. Hmm, perhaps we
should try to agree on a release date for 2.0.2. How about tomorrow?

Cheers,

Marc


dusty wrote:
> 
> svn update
> mvn install
> if you were any kind of man at all..
> -D
> 
> 
> 
> - Original Message 
> From: mschipperheyn <[EMAIL PROTECTED]>
> To: users@appfuse.dev.java.net
> Sent: Thursday, May 8, 2008 1:37:46 AM
> Subject: Re: [appfuse-user] AspectJ 1.6 issues, when is appfuse 2.02
> coming out?
> 
> 
> This is Java. A bit of blood is all par for the game :-)
> 
> Cheers,
> 
> Marc
> 
> 
> 
> Mike Horwitz wrote:
>> 
>> There is a SNAPSHOT release in the AppFuse repository. If you want to use
>> the bleeding edge, you can depend on AppFuse 2.0.2-SNAPSHOT.
>> 
>> Mike
>> 
>> 2008/5/7 mschipperheyn <[EMAIL PROTECTED]>:
>> 
>>>
>>> Seems to work for the compilation, but doesn't update the dependencies
>>> in
>>> Eclipse web module. Even if I add the dependency to the main pom.xml.
>>> That
>>> always worked before getting stuff loaded to Eclipse.
>>>
>>> Anyway, with regards to delivery, I would be a strong proponent of
>>> nightly
>>> development snapshots. It would allow us to use the material when it
>>> contains all the stuff we need to work.
>>>
>>> Cheers,
>>>
>>> Marc
>>>
>>>
>>> mraible wrote:
>>> >
>>> > You need to override the aspectj-maven-plugins dependency versions to
>>> fix
>>> > this:
>>> >
>>> >            
>>> >                org.codehaus.mojo
>>> >                aspectj-maven-plugin
>>> >                1.0
>>> >                
>>> >                    1.5
>>> >                    true
>>> >                    1.5
>>> >                    true
>>> >                    
>>> >                        
>>> >                            org.springframework
>>> >                            spring-aspects
>>> >                        
>>> >                    
>>> >                
>>> >                
>>> >                    
>>> >                        
>>> >                            compile
>>> >                        
>>> >                    
>>> >                
>>> >                
>>> >                    
>>> >                        org.aspectj
>>> >                        aspectjrt
>>> >                        1.6.0
>>> >                    
>>> >                    
>>> >                        org.aspectj
>>> >                        aspectjtools
>>> >                        1.6.0
>>> >                    
>>> >                
>>> >            
>>> >
>>> > 2.0.2 is pretty much done - I'm just working on a "copy-templates"
>>> > mojo (for overridding CRUD) and writing up documentation.
>>> > Unfortunately, I have a day job and I'm staying across the street from
>>> > JavaOne, so it's difficult to free up time to get the release out.
>>> >
>>> > Matt
>>> >
>>> > On Tue, May 6, 2008 at 3:54 AM, mschipperheyn
>>> <[EMAIL PROTECTED]>
>>> > wrote:
>>> >>
>>> >>  Hi,
>>> >>
>>> >>  I've been massaging my project configuration to add support for new
>>> >> versions
>>> >>  of Spring etc for a while now. Now, it seems I have run into a snag
>>> >>  upgrading to Spring 2.5.4, I get the following error trying to run
>>> mvn
>>> >> and
>>> >>  following that, this one from Tomcat withing Eclipse
>>> >>
>>> >>  [WARNING] bad version number found in C:\Documents and
>>> >>  Settings\marc\.m2\reposit
>>> >>  ory\org\aspectj\aspectjrt\1.6.0\aspectjrt-1.6.0.jar expected 1.5.4
>>> found
>>> >>  1.6.0
>>> >>
>>> >>
>>> >>  org.springframework.beans.factory.BeanCreationException: Error
>>> creating
>>> >> bean
>>> >>  with name
>>> >> 'org.springframework.context.config.internalBeanConfigurerAspect':
>>> >>  Instantiation of bean failed; nested exception is
>>> >>  org.springframework.beans.factory.BeanDefinitionStoreException:
>>> Factory
>>> >>  method [public static
>>> >>
>>> 
org.springframework.beans.factory.aspectj.AnnotationBeanConfigurerAspect
>>> >>
>>> >>
>>> org.springframework.beans.factory.aspectj.AnnotationBeanConfigurerAspect.aspectOf()]
>>> >>  threw exception; nested exception is
>>> >>  org.aspectj.lang.NoAspectBoundException: Exception while
>>> initializing
>>> >>
>>> >>
>>> org_springframework_beans_factory_aspectj_AnnotationBeanConfigurerAspect:
>>> >>  java.lang.InstantiationError:
>>> >>  org.springframework.beans.factory.wiring.BeanConfigurerSupport
>>> >>
>>> >>  Caused by:
>>> >> org.springframework.beans.factory.BeanDefinitionStoreException:
>>> >>  Factory method [public static
>>> >>
>>> 
org.springframework.beans.factory.aspectj.AnnotationBeanConfigurerAspect
>>> >>
>>> >>
>>> org.springframework.beans.factory.aspectj.AnnotationBeanConfigurerAspect.aspectOf()]
>>> >>  threw exception; nested exception is
>>> >>  org.aspectj.lang.NoAspectBoundException: Exception while
>>> initializing
>>> >>
>>> >>
>>> org_springframework_beans_factory_aspectj_AnnotationBeanConfigurerAspect:
>>> >>  java.lang.InstantiationError:
>>> >>  org.springframework.beans.factory.wiring.BeanConfigu

Re: [appfuse-user] Quick Question About Spring & Hibernate

[Doug Pham]

Michael,
 If I commented out the filter, after getting the object, the session is 
closed and the next line of code in the action causes a lazyInstantiation 
error.  I just can't believe it closed after one usage even within the same 
action which is still using the same manager.

Cheers,
Doug

Michael Courcy <[EMAIL PROTECTED]> wrote: Open session in view is meant to be 
read-only.
 
When the call to the manager return  (inside the controller) the 
transaction is commited  and the transactionManager change its flushMode 
temporaly to reset it just after to never  (Aka read only),  thus when 
the control is passed to rendering  the transaction is back in  read 
only mode.

This is taken from the javadoc of OSVF :

 * NOTE: This filter will by default not flush the 
Hibernate Session,
 * with the flush mode set to FlushMode.NEVER. It assumes 
to be used
 * in combination with service layer transactions that care for the 
flushing: The
 * active transaction manager will temporarily change the flush mode to
 * FlushMode.AUTO during a read-write transaction, with the 
flush
 * mode reset to FlushMode.NEVER at the end of each 
transaction.
 * If you intend to use this filter without transactions, consider changing
 * the default flush mode (through the "flushMode" property).

Cheers

Doug Pham a écrit :
> You may have ran across this along the way.  Each time I used the DAO 
> to make a call, the session seems to get closed.  If I used the 
> OpenViewFilter, the session is open, but it's in a READ-ONLY mode.  I 
> know I am not posting any code here, but has anyone ran across this 
> and have a correct way of setting this?
>
> Thanks,
> Doug
>
> 
> Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try 
> it now. 
>  



-- 
Michael Courcy
http://courcy.blogspot.com
http://courcy-en.blogspot.com



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




   
-
Be a better friend, newshound, and know-it-all with Yahoo! Mobile.  Try it now.

Re: [appfuse-user] AspectJ 1.6 issues, when is appfuse 2.02 coming out?

[Michael Horwitz]

Seems to be there?
http://static.appfuse.org/repository/org/appfuse/archetypes/appfuse-basic-spring/2.0.2-SNAPSHOT/
*

*Mike*
*
2008/5/10 mschipperheyn <[EMAIL PROTECTED]>:

>
> Darn, tried that. And..no spring archetype snapshot. Hmm, perhaps we
> should try to agree on a release date for 2.0.2. How about tomorrow?
>
> Cheers,
>
> Marc
>
>
> dusty wrote:
> >
> > svn update
> > mvn install
> > if you were any kind of man at all..
> > -D
> >
> >
> >
> > - Original Message 
> > From: mschipperheyn <[EMAIL PROTECTED]>
> > To: users@appfuse.dev.java.net
> > Sent: Thursday, May 8, 2008 1:37:46 AM
> > Subject: Re: [appfuse-user] AspectJ 1.6 issues, when is appfuse 2.02
> > coming out?
> >
> >
> > This is Java. A bit of blood is all par for the game :-)
> >
> > Cheers,
> >
> > Marc
> >
> >
> >
> > Mike Horwitz wrote:
> >>
> >> There is a SNAPSHOT release in the AppFuse repository. If you want to
> use
> >> the bleeding edge, you can depend on AppFuse 2.0.2-SNAPSHOT.
> >>
> >> Mike
> >>
> >> 2008/5/7 mschipperheyn <[EMAIL PROTECTED]>:
> >>
> >>>
> >>> Seems to work for the compilation, but doesn't update the dependencies
> >>> in
> >>> Eclipse web module. Even if I add the dependency to the main pom.xml.
> >>> That
> >>> always worked before getting stuff loaded to Eclipse.
> >>>
> >>> Anyway, with regards to delivery, I would be a strong proponent of
> >>> nightly
> >>> development snapshots. It would allow us to use the material when it
> >>> contains all the stuff we need to work.
> >>>
> >>> Cheers,
> >>>
> >>> Marc
> >>>
> >>>
> >>> mraible wrote:
> >>> >
> >>> > You need to override the aspectj-maven-plugins dependency versions to
> >>> fix
> >>> > this:
> >>> >
> >>> >
> >>> >org.codehaus.mojo
> >>> >aspectj-maven-plugin
> >>> >1.0
> >>> >
> >>> >1.5
> >>> >true
> >>> >1.5
> >>> >true
> >>> >
> >>> >
> >>> >org.springframework
> >>> >spring-aspects
> >>> >
> >>> >
> >>> >
> >>> >
> >>> >
> >>> >
> >>> >compile
> >>> >
> >>> >
> >>> >
> >>> >
> >>> >
> >>> >org.aspectj
> >>> >aspectjrt
> >>> >1.6.0
> >>> >
> >>> >
> >>> >org.aspectj
> >>> >aspectjtools
> >>> >1.6.0
> >>> >
> >>> >
> >>> >
> >>> >
> >>> > 2.0.2 is pretty much done - I'm just working on a "copy-templates"
> >>> > mojo (for overridding CRUD) and writing up documentation.
> >>> > Unfortunately, I have a day job and I'm staying across the street
> from
> >>> > JavaOne, so it's difficult to free up time to get the release out.
> >>> >
> >>> > Matt
> >>> >
> >>> > On Tue, May 6, 2008 at 3:54 AM, mschipperheyn
> >>> <[EMAIL PROTECTED]>
> >>> > wrote:
> >>> >>
> >>> >>  Hi,
> >>> >>
> >>> >>  I've been massaging my project configuration to add support for new
> >>> >> versions
> >>> >>  of Spring etc for a while now. Now, it seems I have run into a snag
> >>> >>  upgrading to Spring 2.5.4, I get the following error trying to run
> >>> mvn
> >>> >> and
> >>> >>  following that, this one from Tomcat withing Eclipse
> >>> >>
> >>> >>  [WARNING] bad version number found in C:\Documents and
> >>> >>  Settings\marc\.m2\reposit
> >>> >>  ory\org\aspectj\aspectjrt\1.6.0\aspectjrt-1.6.0.jar expected 1.5.4
> >>> found
> >>> >>  1.6.0
> >>> >>
> >>> >>
> >>> >>  org.springframework.beans.factory.BeanCreationException: Error
> >>> creating
> >>> >> bean
> >>> >>  with name
> >>> >> 'org.springframework.context.config.internalBeanConfigurerAspect':
> >>> >>  Instantiation of bean failed; nested exception is
> >>> >>  org.springframework.beans.factory.BeanDefinitionStoreException:
> >>> Factory
> >>> >>  method [public static
> >>> >>
> >>>
> org.springframework.beans.factory.aspectj.AnnotationBeanConfigurerAspect
> >>> >>
> >>> >>
> >>>
> org.springframework.beans.factory.aspectj.AnnotationBeanConfigurerAspect.aspectOf()]
> >>> >>  threw exception; nested exception is
> >>> >>  org.aspectj.lang.NoAspectBoundException: Exception while
> >>> initializing
> >>> >>
> >>> >>
> >>>
> org_springframework_beans_factory_aspectj_AnnotationBeanConfigurerAspect:
> >>> >>  java.lang.InstantiationError:
> >>> >>  org.springframework.beans.factory.wiring.BeanConfigurerSupport
> >>> >>
> >>> >>  Caused by:
> >>> >> org.springframework.beans.factory.BeanDefinitionStoreException:
> >>> >>  Factory method [public static
> >>> >>
> >>>
> org.springf

[appfuse-user] DisplayTag, Struts2, OGNL & You

[Dustin Pearce]

So, we have discussed this topic in the past, but I wanted to bring it  
up again because I am still not sure why.


When I use Appfuse 2.x and Struts2, I can just name my displayTag  
table to a getter on my Action and somehow that collection (on the  
OGNL value stack) finds its way to displayTag.   My memory of working  
with Webwork is always having to do a  in order to move the  
OGNL variable into page or request scope for DisplayTag to grab it.  I  
don't remember when I stopped having to do that  call, but  
now with Struts 2.1.x, I have to make the  call again for  
displayTag to see the collection.


Does anyone know how DisplayTag can see the collection without a  
 in the current Struts2 basic build of Appfuse (Struts  
2.0.11.1, Appfuse 2.0.1)?


-Dusty

That means you Rob   ;-)


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [appfuse-user] DisplayTag, Struts2, OGNL & Yo

[Matt Raible]

This might be related to the following:

http://struts.apache.org/2.x/docs/s2-001.html

In other words, I believe they stopped processing JSP EL expressions
${} in Struts tags.

Matt

On Sat, May 10, 2008 at 8:05 PM, Dustin Pearce <[EMAIL PROTECTED]> wrote:
> So, we have discussed this topic in the past, but I wanted to bring it up
> again because I am still not sure why.
>
> When I use Appfuse 2.x and Struts2, I can just name my displayTag table to a
> getter on my Action and somehow that collection (on the OGNL value stack)
> finds its way to displayTag.   My memory of working with Webwork is always
> having to do a  in order to move the OGNL variable into page or
> request scope for DisplayTag to grab it.  I don't remember when I stopped
> having to do that  call, but now with Struts 2.1.x, I have to make
> the  call again for displayTag to see the collection.
>
> Does anyone know how DisplayTag can see the collection without a 
> in the current Struts2 basic build of Appfuse (Struts 2.0.11.1, Appfuse
> 2.0.1)?
>
> -Dusty
>
> That means you Rob   ;-)
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[appfuse-user] java.lang.ClassCastException: org.codehaus.xfire.aegis.type.basic.CalendarType error accessing UserService.wsdl

[narups]

Hello All, 

I am trying to access the existing UserService in appfuse web application.
but i get the class cast exception.
does anyone had this issue. But when i run the sample service tutorial from
appfuse i had no problem.

java.lang.ClassCastException:
org.codehaus.xfire.aegis.type.basic.CalendarType
at
org.codehaus.xfire.aegis.type.basic.BeanType.getSuperType(BeanType.java:731)
at
org.codehaus.xfire.aegis.type.basic.BeanType.writeSchema(BeanType.java:461)
at
org.codehaus.xfire.wsdl.AbstractWSDL.addDependency(AbstractWSDL.java:230)
at
org.codehaus.xfire.wsdl.AbstractWSDL.addDependency(AbstractWSDL.java:239)
at
org.codehaus.xfire.wsdl.AbstractWSDL.addDependency(AbstractWSDL.java:239)
at
org.codehaus.xfire.wsdl.AbstractWSDL.addDependency(AbstractWSDL.java:239)
at
org.codehaus.xfire.wsdl.AbstractWSDL.addDependency(AbstractWSDL.java:239)
at
org.codehaus.xfire.wsdl.AbstractWSDL.addDependency(AbstractWSDL.java:239)
at
org.codehaus.xfire.wsdl.AbstractWSDL.addDependency(AbstractWSDL.java:239)
at
org.codehaus.xfire.wsdl11.builder.WSDLBuilder.writeParametersSchema(WSDLBuilder.java:638)
at
org.codehaus.xfire.wsdl11.builder.WSDLBuilder.createDocumentType(WSDLBuilder.java:612)
at
org.codehaus.xfire.wsdl11.builder.WSDLBuilder.createWrappedOutputParts(WSDLBuilder.java:594)
at
org.codehaus.xfire.wsdl11.builder.WSDLBuilder.createOutputMessage(WSDLBuilder.java:337)
at
org.codehaus.xfire.wsdl11.builder.WSDLBuilder.createAbstractInterface(WSDLBuilder.java:243)
at
org.codehaus.xfire.wsdl11.builder.WSDLBuilder.write(WSDLBuilder.java:161)
at
org.codehaus.xfire.wsdl11.builder.WSDLBuilderAdapter.write(WSDLBuilderAdapter.java:40)
at org.codehaus.xfire.DefaultXFire.generateWSDL(DefaultXFire.java:104)
at
org.codehaus.xfire.transport.http.XFireServletController.generateWSDL(XFireServletController.java:380)
at
org.codehaus.xfire.transport.http.XFireServletController.doService(XFireServletController.java:125)
at
org.codehaus.xfire.transport.http.XFireServlet.doGet(XFireServlet.java:107)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at 
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:447)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1050)
at
com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118)
at
com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1041)
at
org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:350)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1041)
at
org.appfuse.webapp.filter.LocaleFilter.doFilterInternal(LocaleFilter.java:64)
at
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:75)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1041)
at
com.opensymphony.clickstream.ClickstreamFilter.doFilter(ClickstreamFilter.java:42)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1041)
at
org.springframework.orm.hibernate3.support.OpenSessionInViewFilter.doFilterInternal(OpenSessionInViewFilter.java:198)
at
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:75)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1041)
at
org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:264)
at
org.acegisecurity.intercept.web.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:107)
at
org.acegisecurity.intercept.web.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:72)
at
org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274)
at
org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:110)
at
org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274)
at
org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
at
org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274)
at
org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
at
org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274)
at
org.acegisecurity.wrapper.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.ja

Re: [appfuse-user] DisplayTag, Struts2, OGNL & Yo

[Dustin Pearce]

Yeah, I read that, but in the scenario with Appfuse there are no  
struts tags.  The  is not necessary to make displayTag see  
the collection in the current version of Appfuse/Struts and I can't  
figure out how.  DisplayTag is going to look in the request scope for  
the variable "list" for going to put that variable on the value stack.


Some possabilities:
* Struts pre-2.1 has a filter that makes the value stack values  
available via the request scope as well for JSTL style code -- I  
vaguely remember something like that in the Webwork days -- and that  
is no longer there
* DisplayTag is able to somehow reach out past the request scope and  
look in Struts' value stack for the List.  And with the new version of  
Struts, that code is broken???


I see your point on how its related, but that security warning is more  
about the use of struts tags rather than OGNL value stack objects in  
3rd party JSP tag libs.


-D


On May 10, 2008, at 7:16 PM, Matt Raible wrote:


This might be related to the following:

http://struts.apache.org/2.x/docs/s2-001.html

In other words, I believe they stopped processing JSP EL expressions
${} in Struts tags.

Matt

On Sat, May 10, 2008 at 8:05 PM, Dustin Pearce <[EMAIL PROTECTED] 
> wrote:
So, we have discussed this topic in the past, but I wanted to bring  
it up

again because I am still not sure why.

When I use Appfuse 2.x and Struts2, I can just name my displayTag  
table to a
getter on my Action and somehow that collection (on the OGNL value  
stack)
finds its way to displayTag.   My memory of working with Webwork is  
always
having to do a  in order to move the OGNL variable into  
page or
request scope for DisplayTag to grab it.  I don't remember when I  
stopped
having to do that  call, but now with Struts 2.1.x, I have  
to make

the  call again for displayTag to see the collection.

Does anyone know how DisplayTag can see the collection without a  

in the current Struts2 basic build of Appfuse (Struts 2.0.11.1,  
Appfuse

2.0.1)?

-Dusty

That means you Rob   ;-)


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]