[
https://issues.jboss.org/browse/JBAS-9399?page=com.atlassian.jira.plugin....
]
Nathan Blomquist updated JBAS-9399:
-----------------------------------
Description:
URL.getContent() behaves differently within JBoss than it does in a normal JVM. In our
case, when a jar is used in a normal JVM, URL.getContent() returns an ImageProducer. When
the same jar is used from within JBoss, a VirtualFile is returned which then causes a
ClassCastException.
Note: This worked fine in JBoss 4.2.3.GA.
was:
URL.getContent() behaves differently within JBoss than it does in a normal JVM. In our
case, when a jar is used in a normal JVM, URL.getContent() returns an ImageProducer. When
the same jar is used from within JBoss, a VirtualFile is returned which then causes a
ClassCastException.
Note: This worked fine in JBoss 4.2.4.GA.
URL.getContent() returns VirtualFile instead of ImageProducer in
JBoss AS 6.0.0.FINAL
-------------------------------------------------------------------------------------
Key: JBAS-9399
URL:
https://issues.jboss.org/browse/JBAS-9399
Project: Legacy JBoss Application Server 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: VFS
Affects Versions: 6.0.0.Final
Environment: Windows XP
Reporter: Nathan Blomquist
URL.getContent() behaves differently within JBoss than it does in a normal JVM. In our
case, when a jar is used in a normal JVM, URL.getContent() returns an ImageProducer. When
the same jar is used from within JBoss, a VirtualFile is returned which then causes a
ClassCastException.
Note: This worked fine in JBoss 4.2.3.GA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira