i pulled the seam-ui jar out of the war and put it in the ear and all is work
well now.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996519#3996519
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996519
__
I does only appear to happen between portlet apps.
Each of my portlet apps declares its own loader in a jboss-app.xml in the
web-inf directory:
|
| portlet-app-one
|
| seam.jboss.org:loader=portlet-app-one
|
|
I will try moving this to the ear meta-inf
I deployed multiple non-portal applications using selectDate and was able to
currectly use the date selector on all applications.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996323#3996323
Reply to the post :
http://www.jboss.com/index.html?module=bb&op
i'm pretty sure I saw the same issue when running two of the seam sample apps
at the same time. for example, booking and jpa
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996317#3996317
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=postin
Are both applications in separate class loader repositories? Do the apps work
fine separately? I'm not sure what the classloader issues are with portal in
the mix, but I'll try with out portal example later if the issue isn't obvious.
View the original post :
http://www.jboss.com/index.html
