Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Message-ID: <3938241.1177094055367.JavaMail.jira@brutus>
Date: Fri, 20 Apr 2007 11:34:15 -0700 (PDT)
From: "Davanum Srinivas (JIRA)" <jira@apache.org>
To: axis-dev@ws.apache.org
Subject: [jira] Resolved: (AXIS2-2484) IllegalArgumentException: Null
 InputStream is not a valid argument when loading axis client from
 URLClassLoader
In-Reply-To: <31933577.1175863652248.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/AXIS2-2484?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

Davanum Srinivas resolved AXIS2-2484.
-------------------------------------

    Resolution: Fixed

> IllegalArgumentException: Null InputStream is not a valid argument when l=
oading axis client from URLClassLoader
> -------------------------------------------------------------------------=
--------------------------------------
>
>                 Key: AXIS2-2484
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2484
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: kernel
>    Affects Versions: 1.1.1
>         Environment: Sun JDK 1.4.2, Axis 1.1.1, Windows 2000, ADB data bi=
nding
>            Reporter: Jacques Desmazieres
>
> I have a application with a plugin feature. I have implemented an Axis 2 =
service and generated both service and client using java2wsdl and wsdl2java=
.
> When invoking the service using the generated client, loaded in the class=
path, everything is ok.=20
> But when I load the client in an URLClassloader, with all the Axis2 libra=
ries specified in the url[] parameter, I have the following message:
> java.lang.IllegalArgumentException: Null InputStream is not a valid argum=
ent
> =09at com.ctc.wstx.stax.WstxInputFactory.createSR(WstxInputFactory.java:6=
02)
> =09at com.ctc.wstx.stax.WstxInputFactory.createXMLStreamReader(WstxInputF=
actory.java:305)
> =09at org.apache.axiom.om.util.StAXUtils.createXMLStreamReader(StAXUtils.=
java:129)
> =09at org.apache.axis2.deployment.DescriptionBuilder.buildOM(DescriptionB=
uilder.java:86)
> =09at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisCo=
nfigBuilder.java:58)
> =09at org.apache.axis2.deployment.DeploymentEngine.populateAxisConfigurat=
ion(DeploymentEngine.java:690)
> =09at org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfigura=
tion(FileSystemConfigurator.java:109)
> After some investigation, it appears that the exception is raised beacaus=
e the FileSystemConfigurator class cannot find the default axis2.xml config=
uration file.
> I have found that the issue comes from the loading of the default axis2.x=
ml config file in the  org.apache.axis2.deployment.getAxisConfiguration() m=
ethod line 106:
> ClassLoader cl =3D Thread.currentThread().getContextClassLoader();
> In my case, the classloader retrieved is the one of the calling applicati=
on (not the plugin's classloader) and so the axis2 (and mainly axis2-kernel=
-1.1.1.jar) is not found.
> Why retrieving the context classloader ? Is there a reason for that ? Can=
 I fix that with a proper configuration ? Deploying the axis2 kernel jar at=
 application level is not an option.
> If you replace the source code line by the following fixes the problem:
> ClassLoader cl =3D getClass().getClassLoader();
> As we retrieve the service client's classloader, Axis is able to find the=
 default configuration file.
> Jacques Desmazi=C3=A8res

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org