Re: SSL : setting up truststore (and keystore?)

2009-06-24 Thread asheikh
Hi, I have a strange problem with using SSL server. I have a war application which has a jar that connects to a SSL web service. System.setProperty(javax.net.ssl.keyStore, url.getPath()); System.setProperty(jjavax.net.ssl.keyStoreType, jks);

Re: SSL : setting up truststore (and keystore?)

2009-06-24 Thread asheikh
and Consulting http://www.sosnoski.com - http://www.sosnoski.co.nz Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117 asheikh wrote: Hi, I have a strange problem with using SSL server. I have a war application which has a jar that connects to a SSL web service

Re: SSL : setting up truststore (and keystore?)

2009-06-24 Thread asheikh
-0576 - Wellington, NZ +64-4-298-6117 asheikh wrote: Dennis, Thanks for the code and suggestions. The app server should have some way of configuring SSL support, and even though that configuration is going to be intended more for inbound connections it might also have settings for outbound

Re: How to use Rampart as Axis2 client from ejb (JBoss) ?

2009-06-21 Thread asheikh
Andreas, Thanks a lot, I have added in the repository/modules/modules.list with the following code, and everything is fine, thanks again My problem was that I have never included modules.list in the repository. Asad On Sun, Jun 21, 2009 at 7:42 AM, asheikh asad.a.she...@gmail.com wrote

Re: How to use Rampart as Axis2 client from ejb (JBoss) ?

2009-06-20 Thread asheikh
Hi The solution of using the following configuration context works(default context and re-naming mar to jar or copying modules to lib directory) in a stand alone application, but not in a ear deployment . I have spring configuration that creates a bean, and in the construction of the bean I

Re: How to use Rampart as Axis2 client from ejb (JBoss) ?

2009-06-20 Thread asheikh
Andreas, Thanks for the replay but I have already done that but it didn't work either URL url = this.getClass().getClassLoader().getResource( repository); ConfigurationContext ctxs = ConfigurationContextFactory .createConfigurationContextFromURIs(null, url.getPath()) the above code is

Header contains body and body contains header as well

2009-06-15 Thread asheikh
Hi I have generated a stub from a wsdl and run a test, but my problem is the server is not returning a response. I have tcpmonitor and I saw the header includes the body and body also includes the header. There is another web service deployed and when I generated a stub for that service

Re: Header contains body and body contains header as well

2009-06-15 Thread asheikh
Hi, After adding the following line to the stub, the problem is solved and I was able to get a response from the server _serviceClient.getOptions().setProperty(HTTPConstants.CHUNKED, false); On Mon, Jun 15, 2009 at 4:07 PM, asheikh asad.a.she...@gmail.com wrote: Hi I have generated a stub

Re: Parser has already reached end of the document. No siblings found

2009-01-26 Thread asheikh
, Andreas On Wed, Jan 21, 2009 at 11:03, asheikh asad.a.she...@gmail.com wrote: Hi Andreas, did this show anything that I am doing, thanks for your help On Wed, Jan 21, 2009 at 7:34 AM, asheikh asad.a.she...@gmail.com wrote: Andreas, I couldn't respond earlier than

Axis2 1.4.1 and Apache Rampart 1.4 Release (JDK1.4 )

2009-01-25 Thread asheikh
Hi I am using axis 1.4 with JDK1.4 and I am trying to use Rampart 1.4, but it seems Rampart is not compatible with JDK 1.4. Isn't Rampart 1.4 be compatible since axis2 1.4 is also JDK1.4 compatible http://www.mail-archive.com/axis-user@ws.apache.org/msg40420.html I have just migrated my

Re: WS_Security with Axis2 using ServiceClient and OperationClient

2009-01-25 Thread asheikh
Hi, is Rampart compatible with JDK1.4, or I can only use with JDK1.5(which I can't at this time with Weblogic 8.1) Thanks On Sun, Jan 25, 2009 at 5:32 PM, Sameera Jayasoma sameera.madus...@gmail.com wrote: Hi, You can achieve WS-Security with Apache Axis2 by using Rampart. Rampart is an

Re: Parser has already reached end of the document. No siblings found

2009-01-21 Thread asheikh
Hi Andreas, did this show anything that I am doing, thanks for your help On Wed, Jan 21, 2009 at 7:34 AM, asheikh asad.a.she...@gmail.com wrote: Andreas, I couldn't respond earlier than this, It is a soap request, soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope

Re: Parser has already reached end of the document. No siblings found

2009-01-20 Thread asheikh
msgContext.getEnvelope(); Thanks On Tue, Jan 20, 2009 at 12:16 PM, Andreas Veithen andreas.veit...@gmail.com wrote: Could be somehow related to WSCOMMONS-372. Can you test this with Axiom 1.2.8? Andreas On Tue, Jan 20, 2009 at 08:56, asheikh asad.a.she...@gmail.com wrote: Hi, I have also

Re: Parser has already reached end of the document. No siblings found

2009-01-20 Thread asheikh
well with a fully built tree, but not if it is only partially built. This could be a bug in Axiom. Do you have a stacktrace of the exception? Andreas On Tue, Jan 20, 2009 at 11:26, asheikh asad.a.she...@gmail.com wrote: Andreas, Thanks for your input, but it is still the same... Just

Re: Parser has already reached end of the document. No siblings found

2009-01-20 Thread asheikh
#check? Andreas On Tue, Jan 20, 2009 at 12:11, asheikh asad.a.she...@gmail.com wrote: Thanks a lot Andreas, Please see the stactrace below: Start- Stactrace: org.apache.axiom.om.OMException: Parser has already reached end of the document. No siblings found

Re: Parser has already reached end of the document. No siblings found

2009-01-20 Thread asheikh
(), RAIRequest.class, getEnvelopeNamespaces(msgContext .getEnvelope())); try { if(doCheckMM) mmc.check(msgContext); On Tue, Jan 20, 2009 at 2:36 PM, asheikh

Re: Parser has already reached end of the document. No siblings found

2009-01-20 Thread asheikh
PM, Andreas Veithen andreas.veit...@gmail.comwrote: Can you also post a sample request that triggers this issue? In particular is it a SOAP or plain XML request? Andreas On Tue, Jan 20, 2009 at 12:40, asheikh asad.a.she...@gmail.com wrote: Andreas, Below is the code that calls check

Parser has already reached end of the document. No siblings found

2009-01-19 Thread asheikh
Hi, I have migrated my services from axis2. 1.3 to axis2 1.4, and I am getting the following error whenever I invoke any service. Please advice, Thanks in advance *This code does't work: * public void invokeBusinessLogic( org.apache.axis2.context.MessageContext msgContext,

Re: Parser has already reached end of the document. No siblings found

2009-01-19 Thread asheikh
, Jan 20, 2009 at 8:47 AM, asheikh asad.a.she...@gmail.com wrote: Hi, I have migrated my services from axis2. 1.3 to axis2 1.4, and I am getting the following error whenever I invoke any service. Please advice, Thanks in advance *This code does't work: * public void invokeBusinessLogic

Re: ADB maxlength

2009-01-07 Thread asheikh
Thanks Amila, I will... On Wed, Jan 7, 2009 at 9:58 AM, Amila Suriarachchi amilasuriarach...@gmail.com wrote: On Thu, May 22, 2008 at 1:22 AM, sultanat asultanud...@yahoo.com wrote: For the following schema, the axis2 1.4 ADB doesnt check for max length, it is only checking for the

Re: ADB maxlength

2009-01-06 Thread asheikh
Hi I have similar problem, can anyone, please, put some light why axis2 1.3/1.4 doesn't check xsd:maxLength, In my case, the client application can set the field value either in Arabic or English which has different character length. Thanks in advance On Wed, May 21, 2008 at 10:52 PM,

Re: following tags were not closed: soapenv:Envelope...

2008-12-11 Thread asheikh
Hello, Could any one please give me some guidance of how to handle this? Thanks in advance On Thu, Dec 11, 2008 at 9:08 AM, asheikh [EMAIL PROTECTED] wrote: Hi, I have a service that receives that from another system and sometimes my service generates the following message. How can I

following tags were not closed: soapenv:Envelope...

2008-12-10 Thread asheikh
Hi, I have a service that receives that from another system and sometimes my service generates the following message. How can I make sure the response/SOAP message (Axis 1.3) from my service is not malformed... *Error Messsage: * org.apache.axiom.om.OMException:

Re: WSDL2JAVA created uncompilable Stub

2008-12-02 Thread asheikh
Hi I am having same issue, any idea how to solve this. I am using Eclipse Platform Version: 3.3.1.1, and my axis2 runtime is axis2-1.4 I have also noticed that in service.xml says !-- This file was auto-generated from WSDL -- !-- by the Apache Axis2 version: 1.3 Built on : Aug 10, 2007

Failed to load from file, META-INF/ServiceData.xml

2008-06-12 Thread asheikh
Hi Can someone please guide me what this error means. My service was running ok for sometime, and I don't know what I have changed. I am suddenly getting the exception below, Thanks 2008-06-12 09:37:32,533 [DEBUG] File does not exist in the Service Repository! File=META-INF/ServiceData.xml

Re: Failed to load from file, META-INF/ServiceData.xml

2008-06-12 Thread asheikh
Hi Deepal, The error occurs even from version service. For example, executing the following URL will generate the error. Note: The service is running ok http://localhost:7001/Webservice/services/Version?wsdl Thanks On Thu, Jun 12, 2008 at 10:04 AM, Deepal jayasinghe [EMAIL PROTECTED] wrote:

Fwd: Failed to load from file, META-INF/ServiceData.xml

2008-06-12 Thread asheikh
Hi Deepal, Sorry! if I have sent multiple emails, I have been receiving mail delivery errors The error occurs even from version service. For example, executing the following URL will generate the error. Where can I find ServiceData.xml file? Note: The service is running ok

Re: Unparseable date: Cannot receive DateTime field contain

2008-05-25 Thread asheikh
and and not Axis2-1.3. On Mon, May 19, 2008 at 10:55 AM, asheikh [EMAIL PROTECTED] wrote: Hey Joern, Thanks for the response. The code below works fine for me as well. I don't understand why the mistake is because of my code. My code runs fine with Axis2-1.4 and Axis2-1.3 in another

Re: Unparseable date: Cannot receive DateTime field contain

2008-05-19 Thread asheikh
Hey Joern, Thanks for the response. The code below works fine for me as well. I don't understand why the mistake is because of my code. My code runs fine with Axis2-1.4 and Axis2-1.3 in another machine. The NumberFormat Exception is thrown by

Unparseable date: Cannot receive DateTime field contain

2008-05-18 Thread asheikh
Hi Running the following code in two machines with latest release axis2-1.3 (axis2-1.4 is fine) generates the exception below , while other machines are fine. org.apache.axis2.databinding.utils.ConverterUtil.*convertToDateTime* Please, can someone put some light on why the following code would