[jboss-jira] [JBoss JIRA] Commented: (JBAS-5614) Cannot access <service-ref> in nested jar

[Ales Justin (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBAS-5614?page=comments#action_12417103 ] 
            
Ales Justin commented on JBAS-5614:
-----------------------------------

I have a fix already for this vfszip bug.
But as discussed in forum post, I still don't think you should depend on vfs serialization.
You should reconstruct if possible, since when we do in-memory handling, 
you might serialize something that is not available to the client, but due to in-memory it will still 
be seen as if it was present/available.
Consider permissions here as well; e.g. server is able to read, client cannot.

> Cannot access <service-ref> in nested jar
> -----------------------------------------
>
>                 Key: JBAS-5614
>                 URL: http://jira.jboss.com/jira/browse/JBAS-5614
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Ales Justin
>             Fix For: JBossAS-5.0.0.CR1
>
>
> org.jboss:jboss-vfs:jar:2.0.0.Beta15 might cause this issue
> [INFO] \- org.jboss.ws:jbossws-jboss501:jar:3.0.2-SNAPSHOT:compile
> [INFO]    +- org.jboss:jboss-vfs:jar:2.0.0.Beta15:compile
> [INFO]    |  \- org.jboss:jboss-common-core:jar:2.2.5.GA:compile
> [INFO]    +- org.jboss:jboss-reflect:jar:2.0.0.Beta12:compile
> [INFO]    |  \- jboss:jboss-common-logging-spi:jar:2.0.4.GA:compile
> [INFO]    +- org.jboss:jbossxb:jar:2.0.0.CR9:compile
> [INFO]    |  +- apache-xerces:xercesImpl:jar:2.9.1:compile
> [INFO]    |  +- wutka-dtdparser:dtdparser121:jar:1.2.1:compile
> [INFO]    |  \- javax.activation:activation:jar:1.1:compile
> [INFO]    +- org.jboss.metadata:jboss-metadata:jar:1.0.0.Beta18:compile
> [INFO]    |  +- org.jboss.ejb3:jboss-ejb3-ext-api:jar:0.3:compile
> [INFO]    |  +- org.jboss.javaee:jboss-ejb-api:jar:3.0.0.CR1:compile
> [INFO]    |  |  \- jboss.jbossws:jboss-jaxrpc:jar:1.0.4.GA:compile
> [INFO]    |  +- org.jboss.javaee:jboss-jms-api:jar:1.1.0.CR1:compile
> [INFO]    |  +- org.jboss.javaee:jboss-persistence-api:jar:3.0.0.CR1:compile
> [INFO]    |  +- org.jboss.javaee:jboss-transaction-api:jar:1.0.1.CR1:compile
> [INFO]    |  \- org.jboss:jboss-mdr:jar:2.0.0.Beta15:compile
> [INFO]    +- org.jboss.microcontainer:jboss-dependency:jar:2.0.0.Beta15:compile
> [INFO]    \- org.jboss.microcontainer:jboss-kernel:jar:2.0.0.Beta11:compile (version managed from 2.0.0.Beta15)
> http://jbws.dyndns.org:8280/hudson/view/Native%20Tests/job/Native-Core-AS-5.0.1/81/testReport/org.jboss.test.ws.jaxrpc.jbws1121/JBWS1121TestCase/testCall/
> Caused by: java.lang.RuntimeException: File not found: /usr/share/java/workspace/jbossws-hudson-3.0.2-SNAPSHOT/hudson-home/jobs/Native-Core-AS-5.0.1/workspace/stack-native/modules/testsuite/native-tests/target/test-libs/jaxrpc-jbws1121.ear/jaxrpc-jbws1121-client.jar
> 	at org.jboss.virtual.plugins.context.zip.ZipFileWrapper.<init>(ZipFileWrapper.java:87)
> 	at org.jboss.virtual.plugins.context.zip.ZipEntryContext.init(ZipEntryContext.java:210)
> 	at org.jboss.virtual.plugins.context.zip.ZipEntryContext.<init>(ZipEntryContext.java:138)
> 	at org.jboss.virtual.plugins.context.zip.ZipEntryContext.<init>(ZipEntryContext.java:123)
> 	at org.jboss.virtual.plugins.context.zip.ZipEntryContextFactory.getVFS(ZipEntryContextFactory.java:100)
> 	at org.jboss.virtual.plugins.context.zip.ZipEntryContextFactory.getVFS(ZipEntryContextFactory.java:60)
> 	at org.jboss.virtual.plugins.context.AbstractVirtualFileHandler.readObject(AbstractVirtualFileHandler.java:580)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:946)
> 	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1809)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
> 	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
> 	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
> 	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
> 	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
> 	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
> 	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
> 	at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
> 	at org.jboss.ws.core.jaxrpc.client.ServiceObjectFactoryJAXRPC.getObjectInstance(ServiceObjectFactoryJAXRPC.java:118)
> 	at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira