Re: ClassLoading problem

[Marco Mistroni]

hello,

  sorry can't help here.... it's been 2 days that i am trying to deploy my JSF app into jboss 4.0.2 and still got a nasty exception when jboss tries to scan some tld for myfaces..

 

java.util.zip.ZipException: too many length or distance symbols
 at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:140)
 at java.util.zip.ZipInputStream.read(ZipInputStream.java:139)
 at java.util.jar.JarInputStream.read (JarInputStream.java:171)
 at java.io.BufferedInputStream.read1(BufferedInputStream.java:254)
 at java.io.BufferedInputStream.read(BufferedInputStream.java:313)
 at java.util.jar.JarInputStream.getBytes(JarInputStream.java :88)
 at java.util.jar.JarInputStream.<init>(JarInputStream.java:65)
 at java.util.jar.JarInputStream.<init>(JarInputStream.java:43)
 at org.jboss.web.tomcat.tc5.jasper.TagLibCache.scanJar(TagLibCache.java :310)
 at org.jboss.web.tomcat.tc5.jasper.TagLibCache.processTldsInFileSystem(TagLibCache.java:263)
 at org.jboss.web.tomcat.tc5.jasper.TagLibCache.processTldsInFileSystem(TagLibCache.java:256)
 at org.jboss.web.tomcat.tc5.jasper.TagLibCache.init (TagLibCache.java:100)
 at org.jboss.web.tomcat.tc5.jasper.TagLibCache.getLocation(TagLibCache.java:88)
 at org.apache.jasper.JspCompilationContext.getTldLocation(JspCompilationContext.java:519)
 at org.apache.jasper.compiler.Parser.parseTaglibDirective (Parser.java:417)
 at org.apache.jasper.compiler.Parser.parseDirective(Parser.java:483)

 

have you ever seen that? i am going to post another msg to the list to see if someone has find something similar..

 

thanks and regars

 marco

 

 

On 11/17/05, [EMAIL PROTECTED] <[EMAIL PROTECTED] > wrote:

Hi

I use JBoss4.0.2 and as I said, I have the acegi-security and spring.jar under common/lib directory to achieve single signon related functional requirements.

 

Balaji Saranathan

Wipro Technologies

-----------------------------------------------------

ESN:  6  877 8715

Tel :   91 80 2852 0408 * 82333

Fax :  91 80 5138 1761

Cell :  91 98868 61757

 

---

From: Marco Mistroni [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 17, 2005 3:12 PM

To: MyFaces Discussion
Subject: Re: ClassLoading problem

 

Hello,

  where are you deploying to? i deployed on jboss 3.2.5..

all my classes are in my webapp, including spring,acegi & jsf-spring

 

regards

 marco
 

On 11/17/05, [EMAIL PROTECTED] <[EMAIL PROTECTED] > wrote:

Hi,

 

I guess I have some more problems here. We use acegi-security(depends on spring.jar) and depend on container level contexts for addressing certain security requirements. Therefore spring.jar is loaded from the common/lib directory. Now bundling myfaces along with my app seems to lead to some classloader problems integrating with spring beans :-(

 

The curious part is that I had the same working with SUN RI jar files in the common/lib directory. When I moved to MyFaces, I thought it would be as easy to replace the jar files and make changes to the taglib imports. Seems like I need to do more homework on this classloading issue.

 

Balaji Saranathan

Wipro Technologies

-----------------------------------------------------

ESN:  6  877 8715

Tel :   91 80 2852 0408 * 82333

Fax :  91 80 5138 1761

Cell :  91 98868 61757

 

---

From: Wayne Fay [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 16, 2005 9:42 PM
To: MyFaces Discussion
Subject: Re: ClassLoading problem

 

Be sure to shut down jboss, then delete the various jars including anything in tmp/work, then restart and redeploy your app including the Myfaces jars...

 

Wayne

 

On 11/16/05, Marco Mistroni < [EMAIL PROTECTED] > wrote:

hello

 agree... got same error.... package your spring/myfaces/webapp files in your app and don't trust jboss....

more than that, delete your tmp/work directory to make sure...

once i struggled a day to find out where my app faces file were clashing......and found out that in tmp/work directory

i had old copies...

 

regards

 marco

 

On 11/16/05, Wayne Fay < [EMAIL PROTECTED] > wrote:

From the stack trace, I think your application is failing to find one of your Managed Beans specified in faces-config.xml. buildManagedBean is calling ClassUtils to find and instantiate the bean, but JBoss just can't find it, so it bombs out. I could easily be wrong, but that's what it looks like to me.

 

 at org.apache.myfaces.util.ClassUtils.classForName(ClassUtils.java:138)
 at org.apache.myfaces.util.ClassUtils.simpleClassForName(ClassUtils.java:157)
 at org.apache.myfaces.util.ClassUtils.newInstance (ClassUtils.java:265)
 at org.apache.myfaces.config.ManagedBeanBuilder.buildManagedBean(ManagedBeanBuilder.java:49)
 

 

Also I generally suggest that you not use the JBoss MyFaces jar files and instead bundle each application with its own jars -- shared libs are great until you need NB 20051115 MyFaces for your app, and another person with a different application on your JBoss server says that anything after 1.1.1 breaks his app, now what do you do?

 

 

Wayne

 

On 11/16/05, [EMAIL PROTECTED] <[EMAIL PROTECTED] > wrote:

Hi,

 

I get such error in my application. MyFaces jar files are present under <Jboss>/server/default/lib directory whereas my beans are packaged in the web application. I suspect that to be the error, but jsut wanted to make sure , it is. Does anyone have any suggestion?

 

2005-11-16 20:08:54,015 ERROR [ClassUtils] Class com.nortel.ems.mgmt.linux.webInterface.UserManagementHandler not found
java.lang.ClassNotFoundException: No ClassLoaders found for: com.nortel.ems.mgmt.linux.webInterface.UserManagementHandler
 at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:198)
 at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java :475)

 at org.jboss.mx.loading.RepositoryClassLoader.loadClass (RepositoryClassLoaderjava:377)

 at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
 at java.lang.ClassLoader.loadClassInternal(ClassLoader.java :319)
 at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName (Class.java:242)
 at org.apache.myfaces.util.ClassUtils.classForName(ClassUtils.java:138)
 at org.apache.myfaces.util.ClassUtils.simpleClassForName (ClassUtils.java:157)
 at org.apache.myfaces.util.ClassUtils.newInstance (ClassUtils.java:265)
 at org.apache.myfaces.config.ManagedBeanBuilder.buildManagedBean(ManagedBeanBuilder.java:49)
 at org.apache.myfaces.el.VariableResolverImpl.resolveVariable (VariableResolverImpl.java:311)
 at org.springframework.web.jsf.DelegatingVariableResolver.resolveVariable(DelegatingVariableResolver.java:103)
 at org.springframework.web.jsf.DelegatingVariableResolver.resolveVariable (DelegatingVariableResolver.java :103)
 at org.apache.myfaces.el.ValueBindingImpl$ELVariableResolver.resolveVariable(ValueBindingImpl.java:571)
 at org.apache.commons.el.NamedValue.evaluate(NamedValue.java:124)
 at org.apache.commons.el.ComplexValue.evaluate (ComplexValue.java:140)
 at org.apache.myfaces.el.ValueBindingImpl.getValue(ValueBindingImpl.java

 

Thanks

Balaji Saranathan

Wipro Technologies

-----------------------------------------------------

ESN:  6  877 8715

Tel :   91 80 2852 0408 * 82333

Fax :  91 80 5138 1761

Cell :  91 98868 61757

 

Confidentiality Notice The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or [EMAIL PROTECTED] immediately and destroy all copies of this message and any attachments.

Confidentiality Notice The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or [EMAIL PROTECTED] immediately and destroy all copies of this message and any attachments.

Confidentiality Notice The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or [EMAIL PROTECTED] immediately and destroy all copies of this message and any attachments.