[jboss-dev-forums] [Design of JBoss/Tomcat Integration] - Re: java2ClassLoadingCompliance in AS5?

[adrian@jboss.org]

"david.lloyd at jboss.com" wrote : In the new AS5/MC classloader methodology, wouldn't the proper fix be to exclude the builtin JSF classes from deployments that specify this parameter?  Like, using classloading metadata somehow...  maybe bunding the JSF RI as a "module" and implicitly adding a "depends" thing into any web deployment that does NOT specify the WAR_BUNDLES_JSF_JAR context param.
  | 
  | I guess it might be tricky since it's implemented as a context-param rather than, say, a top-level metadata thinger in jboss-web.xml.  But I bet it's still doable this way... where does the WAR deployer live these days?  Has it been POJO-ized?

Yes, the "real fix" would be to do like seam-int does and include the JSF classes
in the war's classpath if it wants jsf.

There's no problem with reading the WebMetaData in a DESCRIBE deployer
for this purpose (including modifying it to include the jsf integration).

This would also avoid having the jsf implementation inside JBossWeb and visible to
everything (it would also fix which classloader gets used when it wants to do xml
parsing).

You could even choose which version of the jsf classes you want to use.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4192229#4192229

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4192229