Good morning, Martin -

First, I have been using the same blessed Rampart modules all along.  Now, to 
the real issue - I did as you suggested, i.e., deployed Tomcat 7, Axis2 1.6.2 
with the rampart modules from 
http://axis.apache.org/axis2/java/rampart/download.html. (I also added the 
Rampart jars to webapps/axis2/WEB-INF/lib).
Tomcat started fine but, as I mentioned, I'm operating in a very tightly 
controlled environment. The browser proxy setting did not allow me to connect 
to http://localhost:8080 and I'm not authorized to change proxy setting. The 
upshot, I can't verify the rampart module using the admin tool.

Now, I'd like to test this deployment but, I am not running a web application 
but a standalone client and I initialize the configuration context from the 
repository

ConfigurationContext ctx = 
ConfigurationContextFactory.createConfigurationContextFromFileSystem("c:/stage/axis2-1.6.2/repository",
 null);

How can I use the modules installed in Tomcat for my non-web client?

TIA,

-a

________________________________
From: aaron.stro...@rsa.com
To: java-user@axis.apache.org
Date: Mon, 13 Aug 2012 17:25:23 -0400
Subject: RE: 
ConfigurationContextFactory.createConfigurationContextFromFileSystem yields 
IllegalArgumentException
Hello, Martin -

Thank you for the suggestion. I know, this is my problem, but my target 
environment is very restricted one and it's windows XP sp3. I've used 
downloaded rampart modules on my winsdows 7 and they seem to work fine.  I 
can't build natively on the target machine, where I cannot install any build 
tools, but I did so on my windows 7 machine. It appears to be an issue related 
to the target platform.

I did follow the instructions you referenced. As I mentioned, I don't seem to 
have the same issue on my development machine (unfortunately, no access to the 
web service from it).

Thanks again,

-a

From: Martin Gainty [mailto:mgai...@hotmail.com]
Sent: Monday, 13 August, 2012 14:27
To: java-user@axis.apache.org
Subject: RE: 
ConfigurationContextFactory.createConfigurationContextFromFileSystem yields 
IllegalArgumentException

Good Afternoon Aaron

MG>it appears you dont have a valid rampart*.mar for your axis2 environment to 
use so it would be best to follow the instructions for build and deploy rampart 
at
MG>http://axis.apache.org/axis2/java/rampart/developer-guide.html
MG>Once you have valid rampart and rahas mar to deploy copy both mars to 
axis2/WEB-INF/modules
MG>then use the admin tool to view the rampart*mar and rahas*.mar
MG>then follow the instructions for incorporating rahas and rampart modules 
available at
http://wso2.org/library/3190#Step_3._Engaging_Rampart_and_setting_authentication_information

MG>Issues regarding Microsoft Dot Net clients contacting Axis2 Servlet are 
explained at
http://webservices20.blogspot.com/2010/01/axis2-wcf-interoperability.html

HTH
Martin

________________________________
From: aaron.stro...@rsa.com
To: java-user@axis.apache.org
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:aaron.stro...@rsa.com]
Sent: Monday, 13 August, 2012 11:05
To: java-user@axis.apache.org
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

Reply via email to