It appears to me that the modules are loaded successfully, otherwise Axis would
have let me know. How can I find out what is was attempting to load when it
choked?
Aug 13, 2012 2:08:27 PM org.apache.axis2.deployment.ModuleDeployer deploy
INFO: Deploying module: addressing-1.6.2 - file:/C:/Documents and
Settings/astroma/My
Documents/AxisClient/axis2-1.6.2/repository/modules/addressing-1.6.2.mar
Aug 13, 2012 2:08:27 PM org.apache.axis2.deployment.ModuleDeployer deploy
INFO: Deploying module: metadataExchange-1.6.2 - file:/C:/Documents and
Settings/astroma/My
Documents/AxisClient/axis2-1.6.2/repository/modules/mex1.6.2.mar
Aug 13, 2012 2:08:27 PM org.apache.axis2.deployment.ModuleDeployer deploy
INFO: Deploying module: mtompolicy-1.6.2 - file:/C:/Documents and
Settings/astroma/My
Documents/AxisClient/axis2-1.6.2/repository/modules/mtompolicy-1.6.2.mar
Aug 13, 2012 2:08:27 PM org.apache.axis2.deployment.ModuleDeployer deploy
INFO: Deploying module: ping-1.6.2 - file:/C:/Documents and Settings/astroma/My
Documents/AxisClient/axis2-1.6.2/repository/modules/ping-1.6.2.mar
Aug 13, 2012 2:08:28 PM org.apache.axis2.deployment.ModuleDeployer deploy
INFO: Deploying module: rahas-1.6.2 - file:/C:/Documents and
Settings/astroma/My
Documents/AxisClient/axis2-1.6.2/repository/modules/rahas-1.6.2.mar
Aug 13, 2012 2:08:28 PM org.apache.axis2.deployment.ModuleDeployer deploy
INFO: Deploying module: rampart-1.6.2 - file:/C:/Documents and
Settings/astroma/My
Documents/AxisClient/axis2-1.6.2/repository/modules/rampart-1.6.2.mar
Aug 13, 2012 2:08:28 PM org.apache.axis2.deployment.ModuleDeployer deploy
INFO: Deploying module: script-1.6.2 - file:/C:/Documents and
Settings/astroma/My
Documents/AxisClient/axis2-1.6.2/repository/modules/scripting-1.6.2.mar
Aug 13, 2012 2:08:28 PM org.apache.axis2.deployment.ModuleDeployer deploy
INFO: Deploying module: soapmonitor-1.6.2 - file:/C:/Documents and
Settings/astroma/My
Documents/AxisClient/axis2-1.6.2/repository/modules/soapmonitor-1.6.2.mar
Exception in thread "main" java.lang.IllegalArgumentException: InputStream
cannot be null
at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
at
org.opensaml.xml.parse.BasicParserPool$DocumentBuilderProxy.parse(BasicParserPool.java:671)
at
org.opensaml.xml.parse.BasicParserPool.parse(BasicParserPool.java:215)
at org.opensaml.xml.XMLConfigurator.load(XMLConfigurator.java:141)
at
org.opensaml.DefaultBootstrap.initializeXMLTooling(DefaultBootstrap.java:199)
at
org.apache.rahas.RampartSAMLBootstrap.bootstrap(RampartSAMLBootstrap.java:79)
at org.apache.rahas.Rahas.init(Rahas.java:41)
at
org.apache.axis2.context.ConfigurationContextFactory.initModules(ConfigurationContextFactory.java:252)
at
org.apache.axis2.context.ConfigurationContextFactory.init(ConfigurationContextFactory.java:230)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:93)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:210)
at com.rsa.pso.common.ws.hcm.axis.Client.<init>(Client.java:66)
at com.rsa.pso.common.ws.hcm.axis.Client.main(Client.java:93)
From: Martin Gainty [mailto:[email protected]]
Sent: Monday, 13 August, 2012 12:59
To: [email protected]; Stromas, Aaron
Subject: RE:
ConfigurationContextFactory.createConfigurationContextFromFileSystem yields
IllegalArgumentException
Aaron
If the InputStream is null this means your module.xml is either incorrectly
configured and or classes missing when you package your rampart*.mar
can we take a look at the META-INF\module.xml..my copy for 1.4 is:
<module name="rampart" class="org.apache.rampart.Rampart">
<Description>This module provides the WS-Security and WS-SecureConversation
functionalities for Axis2, based on Apache WSS4J, Apache XML-Security
and Apache Rahas implementations.
</Description>
<InFlow>
<handler name="PolicyBasedSecurityInHandler"
class="org.apache.rampart.handler.RampartReceiver">
<order phase="Security" phaseFirst="true"/>
</handler>
<handler name="SecurityInHandler"
class="org.apache.rampart.handler.WSDoAllReceiver">
<order phase="Security"/>
</handler>
<handler name="PostDispatchVerificationHandler"
class="org.apache.rampart.handler.PostDispatchVerificationHandler">
<order phase="Dispatch" phaseLast="true"/>
</handler>
</InFlow>
<OutFlow>
<handler name="SecurityOutHandler"
class="org.apache.rampart.handler.WSDoAllSender">
<order phase="Security"/>
</handler>
<handler name="PolicyBasedSecurityOutHandler"
class="org.apache.rampart.handler.RampartSender">
<order phase="Security" phaseLast="true"/>
</handler>
</OutFlow>
<OutFaultFlow>
<handler name="PolicyBasedSecurityOutHandler"
class="org.apache.rampart.handler.RampartSender">
<order phase="Security" phaseLast="true"/>
</handler>
</OutFaultFlow>
<InFaultFlow>
<handler name="PolicyBasedSecurityInHandler"
class="org.apache.rampart.handler.RampartReceiver">
<order phase="Security" phaseFirst="true"/>
</handler>
</InFaultFlow>
<supported-policy-namespaces
namespaces="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"/>
<local-policy-assertions>
<rampart:RampartConfig
xmlns:rampart="http://ws.apache.org/rampart/policy"; />
</local-policy-assertions>
</module>
Martin Gainty
______________________________________________
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung.
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est
interdite. Ce message sert à l'information seulement et n'aura pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
________________________________
From: [email protected]
To: [email protected]
Date: Mon, 13 Aug 2012 12:47:33 -0400
Subject: RE:
ConfigurationContextFactory.createConfigurationContextFromFileSystem yields
IllegalArgumentException
I thought that the error I was getting was due to the second parameter being
null, so I created an axis2.xml and passes it as the second parameter. To my
surprise, I'm still getting the same error. And if I use null for both
parameters, I get the "Unable to engage module: rampart" when I try to load it.
My client follows the article
http://wso2.org/library/3190#Step_3._Engaging_Rampart_and_setting_authentication_information.
Any suggestions, please?
INFO: Deploying module: soapmonitor-1.6.2 - file:/C:/Documents and
Settings/astroma/My
Documents/AxisClient/axis2-1.6.2/repository/modules/soapmonitor-1.6.2.mar
Exception in thread "main" java.lang.IllegalArgumentException: InputStream
cannot be null
at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
at
org.opensaml.xml.parse.BasicParserPool$DocumentBuilderProxy.parse(BasicParserPool.java:671)
at
org.opensaml.xml.parse.BasicParserPool.parse(BasicParserPool.java:215)
at org.opensaml.xml.XMLConfigurator.load(XMLConfigurator.java:141)
at
org.opensaml.DefaultBootstrap.initializeXMLTooling(DefaultBootstrap.java:199)
at
org.apache.rahas.RampartSAMLBootstrap.bootstrap(RampartSAMLBootstrap.java:79)
at org.apache.rahas.Rahas.init(Rahas.java:41)
at
org.apache.axis2.context.ConfigurationContextFactory.initModules(ConfigurationContextFactory.java:252)
at
org.apache.axis2.context.ConfigurationContextFactory.init(ConfigurationContextFactory.java:230)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:93)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:210)
at com.rsa.pso.common.ws.hcm.axis.Client.<init>(Client.java:66)
at com.rsa.pso.common.ws.hcm.axis.Client.main(Client.java:93)
From: Stromas, Aaron [mailto:[email protected]]
Sent: Monday, 13 August, 2012 11:05
To: [email protected]
Subject: ConfigurationContextFactory.createConfigurationContextFromFileSystem
yields IllegalArgumentException
Hello,
I'm using Axis2 1.6.2 with Rampart 1.6.2. My client attempts to create the
ConfigurationContext by calling
File repoPath = new File("axis2-1.6.1/repository")
ConfigurationContextFactory.createConfigurationContextFromFileSystem(repoPath.getAbsolutePath(),
null);
And I'm getting the IllegalArgumentException: Input cannot be null
Why is that? According to what I read, "AxisConfiguration will be created using
default axis2.xml and services and modules will be created and loaded from the
repository". BTW, modules are in ./ axis2-1.6.1/repository/modules.
TIA,
-a
