-
1. Could this be a classpath problem?
redsea Oct 10, 2006 11:39 PM (in response to redsea)My application bundles the sun jsf jars in my apps lib folder.
jboss has the myfaces jars in its standard classpath.
When my project is deployed can you tell me where my apps jars are placed in the classpath?
If my jars are after the jboss jars then my app will link with the wrong jars.
Can someone help me out here and explain how the classpath is formed by jboss when an application is deployed?
Thanks. -
2. Re: Please fix this bug!
jaikiran Oct 11, 2006 1:46 AM (in response to redsea)Can someone help me out here and explain how the classpath is formed by jboss when an application is deployed?
Have a look at:
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossClassLoadingUseCases
http://wiki.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration -
3. Re: Please fix this bug!
ssilvert Oct 11, 2006 8:42 AM (in response to redsea)You are bundling the JSF implementation with your WAR. This is causing a conflict with the implementation that ships with JBoss.
Starting with JBoss AS 4.0.3, we bundle a JSF implementation with the app server. For the 4.x series the implementation is MyFaces. For 5.x, the implementation is the Glassfish/CDDL JSF 1.2 implementation.
See http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossFaces
You can either remove the JSF implementation from your WAR or you can disable the one that ships with JBoss. See the section on "Using the JSF Reference Implementation" on this page:
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossWithIntegratedMyFaces -
4. Re: Please fix this bug!
redsea Oct 11, 2006 8:46 AM (in response to redsea)Thanks for those two links. They are very informative and helpful.
-
5. Re: Please fix this bug!
redsea Oct 11, 2006 8:50 AM (in response to redsea)Yes stan I am bundling the jsf libraries with my app. I understand now that I should rely on the jsf that comes with the jboss server.
Thansk for your reply I do appreciate it. -
6. stan...
redsea Oct 11, 2006 9:01 AM (in response to redsea)I read the two links you provided. I understand that I dont have to include jsf llibraries when deploying to a jboss server. But how would I have known this...
add the following to web.xml:
<listener-class>org.apache.myfaces.webapp.StartupServletContextListener</listener-class>
Thats getting a little to obscure in my opinion. How does one stay on top of all these esoteric things? I would never have known about the additions to the web.xml file if you hadnt told me. -
7. Some friendly advice
redsea Oct 11, 2006 2:09 PM (in response to redsea)In the past few weeks I have been evaluating application servers. Within a minutes time I can start tomcat, sun app server or jboss server. One of the qualities that I am looking for in a serve is a "write once drop anywhere" kind of quality. By this I mean, if I write a web app(let say) using netbeans and follow the j2ee standards, then I should be able to drop that app in any app server and EXPECT it to run.
Now, I have spent more time on jboss because I like some of its design features. However, the more I get into it the more I am beginning to think that jboss has the wrong "philosophy" for us.
Please read this link http://jira.jboss.com/jira/browse/JBAS-2593
The originator of that report had the right idea. It should be as easy as dropping a war file into the deploy directory. However, looking at the two responses I realize that jboss has the wrong focus. If the focus was on their clients that report would not be a dont fix.
Theres a lot I like about jboss, but I want to focus on standards, and not on jboss proprietary enhancements.