RE: ConfigurationContextFactory.createConfigurationContextFromFileSystem yields IllegalArgumentException

Martin Gainty <[email protected]>
Newsgroups gmane.text.xml.axis.user
Message-ID <[email protected]>
Good Morning Aaron

Can you download the latest Rampart Binaries from
http://axis.apache.org/axis2/java/rampart/download.html

These are the blessed binaries so you should not never see any errors or any NULL InputStream from any of Rampart*.mar
Please Download and install to webapps/axis2/WEB-INF/modules

Then you can use the admin tool to view the rampart module
and once you verified the rampart*mar module is valid
engage the rampart*.mar module to your Axis2 webapp

Please keep me apprised if you see any errors.

Thanks,
Martin Gainty 
______________________________________________ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
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 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:[email protected]] 
Sent: Monday, 13 August, 2012 14:27
To: [email protected]
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: [email protected]
To: [email protected]
Date: Mon, 13 Aug 2012 12:47:33 -0400
Subject: RE: ConfigurationContextFactory.createConfigurationContextFromFileSystem yields IllegalArgumentExceptionI 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.marException 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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.