[shrinkwrap-issues] [JBoss JIRA] (SHRINKWRAP-315) NPE in ContainerBase.addAsLibrary
[
https://issues.jboss.org/browse/SHRINKWRAP-315?page=com.atlassian.jira.pl...
]
Michal Matloka commented on SHRINKWRAP-315:
-------------------------------------------
I've tried tests presented by Tommy and I've run XercesUsageInWebServiceTestCase
from jboss-as, but changed with invalid library path - every case returns properly
IllegalArgumentException
{noformat}
Caused by: java.lang.IllegalArgumentException: xerces/xercesImplxx.jar doesn't exist
or can't be accessed
at org.jboss.shrinkwrap.impl.base.Validate.notNull(Validate.java:43)
at
org.jboss.shrinkwrap.impl.base.container.ContainerBase.fileFromResource(ContainerBase.java:1689)
at
org.jboss.shrinkwrap.impl.base.container.ContainerBase.addAsLibrary(ContainerBase.java:1517)
at
org.jboss.shrinkwrap.impl.base.container.ContainerBase.addAsLibrary(ContainerBase.java:1463)
at
org.jboss.as.test.integration.xerces.ws.unit.XercesUsageInWebServiceTestCase.createWebServiceDeployment(XercesUsageInWebServiceTestCase.java:78)
... 63 more
{noformat}
NPE in ContainerBase.addAsLibrary
---------------------------------
Key: SHRINKWRAP-315
URL: https://issues.jboss.org/browse/SHRINKWRAP-315
Project: ShrinkWrap
Issue Type: Bug
Affects Versions: 1.0.0-beta-2
Reporter: Andrew Rubinger
Assignee: Michal Matloka
Using code:
{code}war.addAsLibrary("xerces/xercesImpl.jar",
"xercesImpl.jar");{code}
..if the resourceName doesn't exist, results in:
{code}Caused by: java.lang.NullPointerException
at
org.jboss.shrinkwrap.impl.base.container.ContainerBase.addAsLibrary(ContainerBase.java:1353)
at
org.jboss.shrinkwrap.impl.base.container.ContainerBase.addAsLibrary(ContainerBase.java:1338)
at
org.jboss.shrinkwrap.impl.base.container.ContainerBase.addAsLibrary(ContainerBase.java:1289)
at
org.jboss.as.test.spec.xerces.ws.XercesUsageInWebServiceTestCase.createWebServiceDeployment(XercesUsageInWebServiceTestCase.java:74)
... 59 more{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira