Borland application as Axis Web Services client

2007-12-13 Thread axel.theisen
Hi

We are trying to make our old c++ application, developed in Borland C++
5.02, use some services from a Java Web Service server. The server is
using (Java)Axis 1.2.1, so we were told the best was to use Axis at the
client side as well. We have downloaded Axis 1.6. and installed it. We
then used the wsdl2ws tool to create stubs from the wsdl supplied from
the server. We then want to use the service by taking all the stub files
into Borland and compile them with our application.

That's where we ran into trouble as we got he following error message
from the compiler: 
- Cannot convert 'char *' to 'char * *'

The code it was complaining about was in one of the stub cpp-files(arrow
marked):
int
Axis_DeSerialize_TestWebServiceData_TestWebServiceSubData(TestWebService
Data_TestWebServiceSubData* param,  IWrapperSoapDeSerializer*
pIWSDZ)
{
-  xsd__string* p_testString =
(pIWSDZ-getElementAsString(testString,0));
param-testString = *p_testString;
delete p_testString;
TestWebServiceData_TestWebServiceSubData_Array * array0 = new
TestWebServiceData_TestWebServiceSubData_Array();.
.
.


What can be the cause of this error, and how do we fix it?
Could the different Axis versions be the cause of the problem? Or the
fact that it is a Java server and a C++ client?
Is the old Borland version the problem?

We have tried to get rid of the problem by changing to:
-  xsd__string p_testString =
(pIWSDZ-getElementAsString(testString,0));
-  param-testString = p_testString;

which resolves the pointer error, but we then got the following error
message:

Error:  memory.h(185,1):Cannot convert 'const
std::basic_stringchar,std::string_char_traitschar,std::allocatorchar
 *' to 'void *'
Error:  memory.h(185,1):Type mismatch in parameter 1 in call to
'operator delete(void *)'

As newcomers we would be very glad if anyone could help.

Regards
Axel Theisen
Invenia


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



SV: Borland application as Axis Web Services client

2007-12-13 Thread axel.theisen
Thank you, we found a newer version on SVN (axis-c-1.6-Win32-trace-bin) from  
24-Aug-2006 16:05. Is this the right one?

We have now used this version creating stubs and compiling. We first had to 
change an include from cctype to ctype, but then we got the same error as 
last time:
Error:  memory.h(185,1):Cannot convert 'const 
std::basic_stringchar,std::string_char_traitschar,std::allocatorchar *' 
to 'void *'
Error:  memory.h(185,1):Type mismatch in parameter 1 in call to 'operator 
delete(void *)'

Axel Theisen


-Opprinnelig melding-
Fra: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] På vegne av Nadir Amra
Sendt: 13. desember 2007 12:40
Til: Apache AXIS C User List
Kopi: axis-c-user@ws.apache.org
Emne: Re: Borland application as Axis Web Services client

I would try building the code from SVN, there are many fixes that are not in 1.6

Nadir K. Amra


[EMAIL PROTECTED] wrote on 12/13/2007 05:03:24 AM:

 Hi
 
 We are trying to make our old c++ application, developed in Borland 
 C++ 5.02, use some services from a Java Web Service server. The server 
 is using (Java)Axis 1.2.1, so we were told the best was to use Axis at 
 the client side as well. We have downloaded Axis 1.6. and installed 
 it. We then used the wsdl2ws tool to create stubs from the wsdl 
 supplied from the server. We then want to use the service by taking 
 all the stub files into Borland and compile them with our application.
 
 That's where we ran into trouble as we got he following error message 
 from the compiler:
 - Cannot convert 'char *' to 'char * *'
 
 The code it was complaining about was in one of the stub 
 cpp-files(arrow
 marked):
 int
 Axis_DeSerialize_TestWebServiceData_TestWebServiceSubData(TestWebService
 Data_TestWebServiceSubData* param,IWrapperSoapDeSerializer*
 pIWSDZ)
 {
 -   xsd__string* p_testString =
 (pIWSDZ-getElementAsString(testString,0));
param-testString = *p_testString;
delete p_testString;
TestWebServiceData_TestWebServiceSubData_Array * array0 = new 
 TestWebServiceData_TestWebServiceSubData_Array();.
 .
 .
 
 
 What can be the cause of this error, and how do we fix it?
 Could the different Axis versions be the cause of the problem? Or the 
 fact that it is a Java server and a C++ client?
 Is the old Borland version the problem?
 
 We have tried to get rid of the problem by changing to:
 -   xsd__string p_testString =
 (pIWSDZ-getElementAsString(testString,0));
 -   param-testString = p_testString;
 
 which resolves the pointer error, but we then got the following error
 message:
 
 Error:  memory.h(185,1):Cannot convert 'const 
 std::basic_stringchar,std::string_char_traitschar,std::allocatorch
 ar
  *' to 'void *'
 Error:  memory.h(185,1):Type mismatch in parameter 1 in call to 
 'operator delete(void *)'
 
 As newcomers we would be very glad if anyone could help.
 
 Regards
 Axel Theisen
 Invenia
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: SV: Borland application as Axis Web Services client

2007-12-13 Thread Nadir Amra
No, there is currently no nightly-binary...you have to build it yourself. 
What you have is very old.

Nadir K. Amra


[EMAIL PROTECTED] wrote on 12/13/2007 08:13:13 AM:

 Thank you, we found a newer version on SVN (axis-c-1.6-Win32-trace-
 bin) from  24-Aug-2006 16:05. Is this the right one?
 
 We have now used this version creating stubs and compiling. We first
 had to change an include from cctype to ctype, but then we got 
 the same error as last time:
 Error:  memory.h(185,1):Cannot convert 'const std::
 basic_stringchar,std::string_char_traitschar,std::
 allocatorchar *' to 'void *'
 Error:  memory.h(185,1):Type mismatch in parameter 1 in call to 
 'operator delete(void *)'
 
 Axel Theisen
 
 
 -Opprinnelig melding-
 Fra: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED]
 org] På vegne av Nadir Amra
 Sendt: 13. desember 2007 12:40
 Til: Apache AXIS C User List
 Kopi: axis-c-user@ws.apache.org
 Emne: Re: Borland application as Axis Web Services client
 
 I would try building the code from SVN, there are many fixes that 
 are not in 1.6
 
 Nadir K. Amra
 
 
 [EMAIL PROTECTED] wrote on 12/13/2007 05:03:24 AM:
 
  Hi
  
  We are trying to make our old c++ application, developed in Borland 
  C++ 5.02, use some services from a Java Web Service server. The server 

  is using (Java)Axis 1.2.1, so we were told the best was to use Axis at 

  the client side as well. We have downloaded Axis 1.6. and installed 
  it. We then used the wsdl2ws tool to create stubs from the wsdl 
  supplied from the server. We then want to use the service by taking 
  all the stub files into Borland and compile them with our application.
  
  That's where we ran into trouble as we got he following error message 
  from the compiler:
  - Cannot convert 'char *' to 'char * *'
  
  The code it was complaining about was in one of the stub 
  cpp-files(arrow
  marked):
  int
  
Axis_DeSerialize_TestWebServiceData_TestWebServiceSubData(TestWebService
  Data_TestWebServiceSubData* param,IWrapperSoapDeSerializer*
  pIWSDZ)
  {
  -   xsd__string* p_testString =
  (pIWSDZ-getElementAsString(testString,0));
 param-testString = *p_testString;
 delete p_testString;
 TestWebServiceData_TestWebServiceSubData_Array * array0 = new 
  TestWebServiceData_TestWebServiceSubData_Array();.
  .
  .
  
  
  What can be the cause of this error, and how do we fix it?
  Could the different Axis versions be the cause of the problem? Or the 
  fact that it is a Java server and a C++ client?
  Is the old Borland version the problem?
  
  We have tried to get rid of the problem by changing to:
  -   xsd__string p_testString =
  (pIWSDZ-getElementAsString(testString,0));
  -   param-testString = p_testString;
  
  which resolves the pointer error, but we then got the following error
  message:
  
  Error:  memory.h(185,1):Cannot convert 'const 
  std::basic_stringchar,std::string_char_traitschar,std::allocatorch
  ar
   *' to 'void *'
  Error:  memory.h(185,1):Type mismatch in parameter 1 in call to 
  'operator delete(void *)'
  
  As newcomers we would be very glad if anyone could help.
  
  Regards
  Axel Theisen
  Invenia
  
  
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
  
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: what is libxslt for?

2007-12-13 Thread Samisa Abeysinghe

cara wrote:
I think that was a mistake in the documentation. It was removed for 
Jira issue AXIS2C-765.


Yes that is correct. We had a code generation module written in C, that 
required libxslt, but due to lack of maintenance, we removed that 
module. We should have removed libxml dependency along with that.


Samisa...



On 12/13/07, *Michael Mole*  [EMAIL PROTECTED] 
mailto:[EMAIL PROTECTED] wrote:



I was looking at the installation instructions for Axis2/C the
other day and noticed that it now requires a library called
libxslt.  However, I haven't had any problems using Axis2/C
without it.  Can someone tell me what it is for?

Thanks,
Mike

Michael J Molé
Software Engineer
IBM Software Group - Rational
(781)676-2710




No virus found in this incoming message.
Checked by AVG Free Edition. 
Version: 7.5.503 / Virus Database: 269.17.1/1182 - Release Date: 12/12/2007 11:29 AM
  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Generating SOAP request from WSDL's schema

2007-12-13 Thread Antonio Manuel Muñiz Martín
You can use soapUI (www.soapui.org). SoapUI is an java application, use it
and you will see how it works. Is exactly what do you want. You can checkout
the source code and use it as API for dinamic message construction.

I had the same issue some time ago.

But, you can use Axis2 client side, data binding abstracts you of SOAP
message creation.

Bye.

2007/12/12, Eric Nygma [EMAIL PROTECTED]:

 Hi,

 I have a requirement in which I have to programatically read a
 webservice's WSDL, and construct the SOAP request to consume the service.
 Reading the WSDL can be accomplished with WSDL4J. But I  am having
 problems constructing the request message from the schema.

 Is there some API which can do this for me. JAXB is not an option, because
 it involves an intermediate step of generating class files from the schema,
 and then class files are subsequently used my Marshallers. Rather,I am
 looking for an API which ideally is fed an xsd and generates the
 OMElement/DOM corresponsding to it, which can then be put inside a soap
 envelope and dispatched.

 Thanks very much in advance.

 Regards
 Eric.



Removing SOAP 1.2 and HTTP for POJO services

2007-12-13 Thread Hoda, Nadeem [USA]
 
 
In a simple POJO service with no WSDL file (only relying on the
ServiceClass in services.xml), how do you disable/get rid of SOAP 1.2
and HTTP bindings and ports if you only want the SOAP 1.1 port and
binding?
 
Is there a simple config/options/parameter for this?
 
Thanks, 
 
Nadeem


Re: Fault in parsing web service

2007-12-13 Thread Mr Smith
On Dec 13, 2007 2:25 AM, jfirman [EMAIL PROTECTED] wrote:

 Hi Mr Smith,

 I'm having exactly the same problem -- were you able to modify the wsdl file
 to fix this problem?

Yes, I modified a line in the wsdl file from
fault name=Fault/
to
soap:fault name=Fault/

-- 
mack /

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Sending SOAP Requests through an HTTP Proxy ... continued

2007-12-13 Thread Udo Butschinek
Hello alltogether,

I am having a special problem. 

I am trying to send SOAP requests through an HTTP Proxy. For this purpose I set 
the http.proxyHost and http.proxyPort systemvariables by 
System.setProperty(). This basically works very fine. 

Now my application (SOAP-Client) has to switch between using a proxy for 
sending SOAP requests to a server on the internet and sending the same data to 
a server in the intranet. In the latter case no proxy is used. 

The problem is, that the Axis-Call-Class caches the data somewhere, so that 
always the first settings are used, so a switch is not possible. 

This has been documented and mentioned by other users before:

http://marc.info/?l=axis-userm=113698996700314w=2

See solution seems to be here:

http://wiki.apache.org/ws/FrontPage/Axis/AxisProxy

There it sais:

[QUOTE]
If you need the ability to reset proxy settings during runtime, i.e. without 
stopping/starting the JVM (e.g. after the proxy settings dialog of your 
application was edited and confirmed by a user), it is sufficient to add a 
public static method to TransportClientPropertiesFactory, that is just clearing 
its TransportClientProperties-cache. If it is possible to override the default 
TransportClientPropertiesFactory, by providing your custom factory

-Dorg.apache.axis.components.net.TransportClientPropertiesFactory=your.package.YourTCPropsFactory
this would be the preferable approach.
[/QUOTE]

To my somehow dull mind this means that I write a class MyTCPropsFactory. 
Register a System variable with key 
org.apache.axis.components.net.TransportClientPropertiesFactory where the 
value is MyTCPropsFactory. 
My factory has a static method called whatever (? say: clearCache()).  

Now the question: 

1. What exactly has to be done in the public static method
2. How does Axis know which method to call and when is it called?

After hours of googling I could not find any concrete example of code where it 
is shown how to clear the cache. 
I could not see another way than asking the apache-list directly.

Any help would highly be appreciated. 

Yours desperately,
Udo Butschinek

__

Udo Butschinek, M.A.
Projektmanagement, Kommunikation

E-Mail[EMAIL PROTECTED]
Internet  www.zimmer19.de

T+49 (0) 211.  93 88 54 84
F+49 (0) 211.  93 88 54 81

zimmer19 GbR
Hendrik Becker
Udo Butschinek
Nadja Iven
Markus Wendland

Zimmerstr. 19

D-40215 Düsseldorf
USt-IdNr.: DE814746933



Re: Axis 1.3 and Attachments for Large Docs

2007-12-13 Thread [EMAIL PROTECTED]

Hi Aoife,
I have a similar kind of requirement and i want to know whether you have got
any solution for this. There is harldy any document regarding attachments
and Soap Over JMS. If you did find a solution, can you pls share the same
with me...


Aoife Kavanagh (Ext. 987) wrote:
 
 Hi,
 
 I'm currently looking to see if sending large PDFs as an attachment using
 Axis 1.3 over JMS will reduce the memory spikes that we are currently
 seeing
 on some sites.
 
 If this did work we would be sending SOAP messages over JMS but for
 prototyping purposes I'm working with Tomcat 5.5.12
 However, I'm getting a bit confused over how exactly to send/receive
 attachments.  The Axis 1.3 samples directory contains what I believe are
 two
 samples - attachments and swa.  I'm assuming that swa is
 SoapWithAttachments
 in which case I'm not quite sure what the example in the attachments
 directory is.  It seems that the service method called in the attachments
 code explicitly passes a DataHandler object as a parameter to the service
 call whereas this is not the case for the swa example.  
 
 I also have been looking at Fear of Attachments from
 http://www.mail-archive.com/[EMAIL PROTECTED]/msg08732/Fear_of_Attach
 ments.pdf which I thought would be helpful but the code samples seem to
 assume use of some generated files from WSDL which I wouldn't have, in
 particular the section of client code where the attachment (DataHandler)
 is
 added.In a way similar to this code though I want to be just tag the
 attachment on to the service request message.
 
 I apologise in advance if I'm missing something obvious but if if I could
 just get clear explanation of differences between ways of sending
 attachments indicated by the attachments example and the swa example that
 would be great.  
 
 Alternatively, if anybody knows that this approach won't solve our problem
 then could you let me know with reasoning.  Upgrading to Axis 2 is not an
 option at the moment so please don't suggest.
 
 Thanks,
 Aoife
 
 
 __
 The information contained in this e-mail is confidential, may be
 privileged and is intended 
 only for the user of the recipient named above. If you are not the
 intended recipient or a 
 representative of the intended recipient, you have received this e-mail in
 error and must 
 not copy, use or disclose the contents of this e-mail to anybody else.  
 
 If you have received this e-mail in error, please notify the sender
 immediately by return 
 e-mail and permanently delete the copy you received.  This e-mail has been
 swept for 
 computer viruses. However, you should carry out your own virus checks. 
 Registered in Ireland, No. 205721.  http://www.FINEOS.com
 __
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Axis-1.3-and-Attachments-for-Large-Docs-tp643p14317155.html
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: [Axis2] Unable to deserialize OMElement

2007-12-13 Thread Lositski Vadim
Hello,

I've done additional research on this topic, and it seems that the problem is 
in the size of the response XML envelope.
When I am trying to print out the resulted OMElement:

result.serializeAndConsume(System.out);

Only first 4000 characters are printed and then  following exception is thrown: 
java.lang.RuntimeException: [was class java.io.IOException] Attempted read on 
closed stream

Stange is that when the operation returns XML which length is less than 4000 
characters everything works fine.
Also when I use this operation in async mode, everything is also fine, response 
size irrespectively.

Do you know about this limitation?

Thanks in advance,
Vadim

-Original Message-
From: Lositski Vadim
Sent: Wednesday, December 12, 2007 5:19 PM
To: axis-user@ws.apache.org
Subject: [Axis2] Unable to deserialize OMElement

Hi everybody,

I am sending a request to the service which combines its response from various 
sources, then creates an OMElement and sends it back. The databinding and 
deserialization is made with Castor and Stax APIs basically as it is described 
in the databinding example from Axis2 distribution.

When I am trying to create an object from an OMElement received from the service

StAXSource staxSource = new StAXSource(result.getXMLStreamReader());
Unmarshaller unmarshaller = new Unmarshaller(TargetClass.class);
UnmarshalHandler unmarshalHandler = unmarshaller.createHandler();
try {
ContentHandler contentHandler = (ContentHandler) 
Unmarshaller.getContentHandler(unmarshalHandler);
TransformerFactory.newInstance().newTransformer().transform(staxSource, new 
SAXResult(contentHandler));
}
catch (Exception ex) {
ex.printStackTrace();
}
TargetClass response = (TargetClass) unmarshalHandler.getObject();

I receive a NullPointerException exception:

java.lang.NullPointerException
at javanet.staxutils.StAXSource$1.parse(StAXSource.java:196)
at javanet.staxutils.StAXSource$1.parse(StAXSource.java:181)
at 
org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:484)
at 
com.profitsoftware.webservices.central.CentralWebServiceTester.main(CentralWebServiceTester.java:85)

The object is serialized, but partially some data fields are null

I have also tried to just print out the OMElement, but received:

Exception in thread main java.lang.StackOverflowError
at 
org.apache.axiom.om.impl.llom.OMNodeImpl.setComplete(OMNodeImpl.java:174)
at 
org.apache.axiom.om.impl.llom.OMNodeImpl.setComplete(OMNodeImpl.java:174)
at 
org.apache.axiom.om.impl.llom.OMNodeImpl.setComplete(OMNodeImpl.java:174)

When I use OMElement.toStringWithConsume() I have the following exception:

java.lang.RuntimeException: [was class java.io.IOException] Attempted read on 
closed stream.
at 
com.ctc.wstx.util.ExceptionUtil.throwRuntimeException(ExceptionUtil.java:18)
at com.ctc.wstx.sr.StreamScanner.throwLazyError(StreamScanner.java:706)
at 
com.ctc.wstx.sr.BasicStreamReader.safeFinishToken(BasicStreamReader.java:3655)
at com.ctc.wstx.sr.BasicStreamReader.getText(BasicStreamReader.java:809)
at 
org.apache.axiom.om.impl.llom.OMStAXWrapper.getText(OMStAXWrapper.java:364)
at 
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeText(StreamingOMSerializer.java:339)
at 
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeNode(StreamingOMSerializer.java:79)
at 
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serialize(StreamingOMSerializer.java:57)
at 
org.apache.axiom.om.impl.util.OMSerializerUtil.serializeByPullStream(OMSerializerUtil.java:525)
at 
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:795)
at 
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:814)
at 
org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(OMNodeImpl.java:358)
at 
org.apache.axiom.om.impl.llom.OMElementImpl.toStringWithConsume(OMElementImpl.java:904)
at 
com.profitsoftware.webservices.central.CentralWebServiceTester.main(CentralWebServiceTester.java:79)
Caused by: java.io.IOException: Attempted read on closed stream.
at 
org.apache.commons.httpclient.AutoCloseInputStream.isReadAllowed(AutoCloseInputStream.java:165)
at 
org.apache.commons.httpclient.AutoCloseInputStream.read(AutoCloseInputStream.java:106)
at java.io.FilterInputStream.read(FilterInputStream.java:111)
at java.io.PushbackInputStream.read(PushbackInputStream.java:161)
at java.io.FilterInputStream.read(FilterInputStream.java:90)
at com.ctc.wstx.io.UTF8Reader.loadMore(UTF8Reader.java:362)
at com.ctc.wstx.io.UTF8Reader.read(UTF8Reader.java:110)
at com.ctc.wstx.io.MergedReader.read(MergedReader.java:101)
at com.ctc.wstx.io.ReaderSource.readInto(ReaderSource.java:84)
at 

Re: Sending SOAP Requests through an HTTP Proxy ... continued

2007-12-13 Thread Antonio Manuel Muñiz Martín
You can configure proxy dinamically for each client independently using:

ProxyProperties proxyProperties = new ProxyProperties();
proxyProperties.setDomain(102.12.12.12);
proxyProperties.setProxyPort(80);
proxyProperties.setUserName(user);
proxyProperties.setPassWord(pass);

stub._getServiceClient().getOptions().setProperty(
HTTPConstants.PROXY, proxyProperties);

Bye.

2007/12/13, Udo Butschinek [EMAIL PROTECTED]:

  Hello alltogether,

 I am having a special problem.

 I am trying to send SOAP requests through an HTTP Proxy. For this purpose
 I set the http.proxyHost and http.proxyPort systemvariables by
 System.setProperty(). This basically works very fine.

 Now my application (SOAP-Client) has to switch between using a proxy for
 sending SOAP requests to a server on the internet and sending the same data
 to a server in the intranet. In the latter case no proxy is used.

 The problem is, that the Axis-Call-Class caches the data somewhere, so
 that always the first settings are used, so a switch is not possible.

 This has been documented and mentioned by other users before:

 http://marc.info/?l=axis-userm=113698996700314w=2

 See solution seems to be here:

 http://wiki.apache.org/ws/FrontPage/Axis/AxisProxy

 There it sais:

 [QUOTE]
 If you need the ability to reset proxy settings during runtime, i.e.
 without stopping/starting the JVM (e.g. after the proxy settings dialog of
 your application was edited and confirmed by a user), it is sufficient to
 add a public static method to TransportClientPropertiesFactory, that is just
 clearing its TransportClientProperties-cache. If it is possible to override
 the default TransportClientPropertiesFactory, by providing your custom
 factory

 -
 Dorg.apache.axis.components.net.TransportClientPropertiesFactory=your.package.YourTCPropsFactory
 this would be the preferable approach.
 [/QUOTE]

 To my somehow dull mind this means that I write a class MyTCPropsFactory.
 Register a System variable with key 
 org.apache.axis.components.net.TransportClientPropertiesFactory where the
 value is MyTCPropsFactory.
 My factory has a static method called whatever (? say: clearCache()).

 Now the question:

 1. What exactly has to be done in the public static method
 2. How does Axis know which method to call and when is it called?

 After hours of googling I could not find any concrete example of code
 where it is shown how to clear the cache.
 I could not see another way than asking the apache-list directly.

 Any help would highly be appreciated.

 Yours desperately,
 Udo Butschinek

 __

 Udo Butschinek, M.A.
 Projektmanagement, Kommunikation

 E-Mail[EMAIL PROTECTED]
 Internet  www.zimmer19.de

 T+49 (0) 211.  93 88 54 84
 F+49 (0) 211.  93 88 54 81

 zimmer19 GbR
 Hendrik Becker
 Udo Butschinek
 Nadja Iven
 Markus Wendland

 Zimmerstr. 19

 D-40215 Düsseldorf
 USt-IdNr.: DE814746933




Re: Fault in parsing web service

2007-12-13 Thread jfirman

Thanks!

-John

Mr Smith wrote:
 
 On Dec 13, 2007 2:25 AM, jfirman [EMAIL PROTECTED] wrote:

 Hi Mr Smith,

 I'm having exactly the same problem -- were you able to modify the wsdl
 file
 to fix this problem?
 
 Yes, I modified a line in the wsdl file from
 fault name=Fault/
 to
 soap:fault name=Fault/
 
 -- 
 mack /
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Fault-in-parsing-web-service-tp14251801p14320887.html
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



axis2 https Unexpected EOF in prolog

2007-12-13 Thread Marco Rossi
Hi,
i have to test a webservices build with axis2 (tomcat6, linux red hat).
We have a reverse proxy to expose this service to the client (via SSL); so
if i create a test client with axis2 (same library, same version) and use
the internal endpoint (http://myserver/myService) all works fine.
But il I try to test the same come with the reverse proxy endpoint
https://myproxy/myService i get the following

org.apache.axis2.AxisFault: com.ctc.wstx.exc.WstxEOFException: Unexpected
EOF in prolog
 at [row,col {unknown-source}]: [1,0]

Any idea?

Thanks,
Marco


Axis validate SOAP Messages

2007-12-13 Thread Antonio Manuel Muñiz Martín
Hi.

Axis2 validate SOAP messages?
I write in wsdl

...
xs:sequence
xs:element minOccurs=1 name=appl
nillable=true type=xs:string /
...

I send to service a message without appl element, in service code I do:

 String appl = operation.getOperationRequest().getAppl();

and this statement return null, that´s ok, but this element can not be null
as WSDL says (minOccurs = 1). Is this correct?. Must throws axis an
Exception?

Thanks.


Can't Package Axis2 In EAR with Maven2

2007-12-13 Thread devnulled

Unfortunately this is kind of an obtuse question, but I’m hoping someone out
there has ran into this problem before.

I’m currently trying to repackage some existing projects into an EAR for
JBoss (converting from a WAR) because I have some EJB session beans I need
to deploy.  A couple of the sub-projects in the main project I’m trying to
deploy as an EAR contain Axis2 stub clients which use Rampart for
WS-Security.   The .mar’s for WS-Security support are put into a resources
folder under one of the projects, and said project is a dependency of the
only other project using Axis2.

Let me know if I’m leaving-out any details here.. I didn’t actually develop
these stubs, I just tend to be the person who manages our build process.

Whenever I try to include these projects into an EAR using the Maven2 EAR
plugin, I get this error:

[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] Failed to initialize ear modules

Embedded error: Unknown artifact type[mar]
[INFO]

[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to initialize
ear modules
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to
initialize ear modules
at
org.apache.maven.plugin.ear.AbstractEarMojo.execute(AbstractEarMojo.java:210)
at
org.apache.maven.plugin.ear.GenerateApplicationXmlMojo.execute(GenerateApplicationXmlMojo.java:96)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
... 16 more
Caused by: org.apache.maven.plugin.ear.UnknownArtifactTypeException: Unknown
artifact type[mar]
at
org.apache.maven.plugin.ear.util.ArtifactTypeMappingService.getStandardType(ArtifactTypeMappingService.java:159)
at
org.apache.maven.plugin.ear.EarModuleFactory.newEarModule(EarModuleFactory.java:65)
at
org.apache.maven.plugin.ear.AbstractEarMojo.execute(AbstractEarMojo.java:203)
... 19 more

If I comment out references to the two projects containing Axis2 artifacts,
I can build the ear just fine.

Here are the entries in the pom file for Axis2 1.3 we’re using:
dependency
groupIdorg.apache.axis2/groupId
artifactIdaxis2-kernel/artifactId
version1.3/version
/dependency
dependency
groupIdorg.apache.axis2/groupId
artifactIdaxis2-adb/artifactId
version1.3/version
/dependency
dependency
groupIdorg.apache.ws.commons.axiom/groupId
artifactIdaxiom-api/artifactId
version1.2.5/version
/dependency
dependency
groupIdorg.apache.ws.commons.axiom/groupId
artifactIdaxiom-dom/artifactId
version1.2.5/version
/dependency
dependency
groupIdorg.apache.ws.commons.axiom/groupId
artifactIdaxiom-impl/artifactId
version1.2.5/version
/dependency
dependency
groupIdwsdl4j/groupId
artifactIdwsdl4j/artifactId
version1.6.1/version
/dependency
dependency
groupIdorg.apache.ws.commons.schema/groupId

Re: Removing SOAP 1.2 and HTTP for POJO services

2007-12-13 Thread Nadir Amra
Nadeem

You will need to get the latest code (a nightly build) to use these, but 
in axis2.xml config file, you can do the following:

!-- Following parameter will completely disable REST handling in 
Axis2--
parameter name=disableREST locked=truetrue/parameter
 
!-- Following parameter will suppress generation of SOAP 1.2 bindings 
in auto-generated WSDL files --
parameter name=disableSOAP12 locked=truetrue/parameter

This will disable it for all services...there currently no way to 
selectively do this on a per service basis.  There is a JIRA for this 
enhancement.

Nadir K. Amra


Hoda, Nadeem [USA] [EMAIL PROTECTED] wrote on 12/13/2007 05:17:49 
AM:

 
 
 In a simple POJO service with no WSDL file (only relying on the 
 ServiceClass in services.xml), how do you disable/get rid of SOAP 1.
 2 and HTTP bindings and ports if you only want the SOAP 1.1 port and 
binding?
 
 Is there a simple config/options/parameter for this?
 
 Thanks, 
 
 Nadeem

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: [Axis2] trimming down the xml in axis2 1.3

2007-12-13 Thread samir shaikh
Raghu,

I see in the archives that you ran into the same
problem as this. Did wsdl2java with -sp work for you?

Samir

--- Raghu Upadhyayula [EMAIL PROTECTED]
wrote:

 Samir,
 
   WSDL2Java can also be used to generate serverside
 code. Check
 WSDL2Java options, to create serverside code you
 need to specify the
 options -ss -sd -ssi (check the description for
 these options in
 WSDL2Java)
 
 You can use -sp option with WSDL2Java when you
 generate the serverside
 code in which case the namespace is suppressed on
 the serverside.
 
 Thanks
 Raghu
 
 -Original Message-
 From: samir shaikh [mailto:[EMAIL PROTECTED] 
 Sent: Wednesday, December 12, 2007 5:31 PM
 To: axis-user@ws.apache.org
 Subject: Re: [Axis2] trimming down the xml in axis2
 1.3
 
 Martin,
 
 You mean using QName in the client code?
 
 I'm trying to tune my server to not send back
 excessive xml. I cannot change the xml I send back
 to
 my clients. the extra ns: is causing me trouble
 after upgrading from axis2 1.1.1 to axis2 1.3 e.g.
 ns:fieldName0/ns:fieldName. My clients expect
 fieldName0/fieldName.
 
 Samir
 
 --- Martin Gainty [EMAIL PROTECTED] wrote:
 
  you can always use null..e.g.
   QName paramQName = new QName(, paramName);
  
  M--
  - Original Message -
  From: samir shaikh [EMAIL PROTECTED]
  To: axis-user@ws.apache.org
  Sent: Wednesday, December 12, 2007 7:20 PM
  Subject: RE: [Axis2] trimming down the xml in
 axis2
  1.3
  
  
   Raghu,
  
   Thanks for your help. I tried that out but I
 want
  to
   suppress it on the server. I think WSDL2Java is
  for
   generating a client, right?
  
   I'm hoping to find some configuration in
  services.xml
   or axis2.xml... any idea?
  
   Samir
  
  
   --- Raghu Upadhyayula
 [EMAIL PROTECTED]
   wrote:
  
Samir,
   
Try WSDL2Java with -sp option to suppress the
namespace prefix.
   
Thanks
Raghu
   
-Original Message-
From: samir shaikh
 [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 12, 2007 2:20 PM
To: axis-user@ws.apache.org
Subject: [Axis2] trimming down the xml in
 axis2
  1.3
   
Hi,
   
I'm trying to trim down the xml exchanged when
  using
a
axis2 client and server. Is there a way I can
configure the serializer to not prefix
 namespace
with
every element e.g.
  ns:errorCode0/ns:errorCode
can
just be errorCode0errorCode. Also not send
  back
the additional headers and field types with
 each
call.
I was able to do that in Axis1.3 with the wsdd
  file.
Can someone point me to where that is done in
  Axis2.
   
Thanks a lot.
   
Samir
   
   
   
   
  
 



Be a better friend, newshound, and
know-it-all with Yahoo! Mobile.  Try it now.
   
  
 

http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
   
   
   
   
  
 

-
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
   
   
   
  
 

-
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
   
   
  
  
  
  
 


 
  
   Be a better friend, newshound, and
   know-it-all with Yahoo! Mobile.  Try it now.
 

http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
  
  
  
 

-
   To unsubscribe, e-mail:
  [EMAIL PROTECTED]
   For additional commands, e-mail:
  [EMAIL PROTECTED]
  
  
  
  
 

-
  To unsubscribe, e-mail:
  [EMAIL PROTECTED]
  For additional commands, e-mail:
  [EMAIL PROTECTED]
  
  
 
 
 
  


 
 Be a better friend, newshound, and 
 know-it-all with Yahoo! Mobile.  Try it now.

http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
 
 
 

-
 To unsubscribe, e-mail:
 [EMAIL PROTECTED]
 
=== message truncated ===



  

Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: [Axis2] trimming down the xml in axis2 1.3

2007-12-13 Thread Raghu Upadhyayula
Samir,

Yes, it worked for me.

I used the WSDL2Java with -sp option to generate the server code.

What data binding are you using?

If you are using ADB, then you have to replace all the request 
response classes.

Thanks
Raghu
-Original Message-
From: samir shaikh [mailto:[EMAIL PROTECTED] 
Sent: Thursday, December 13, 2007 10:50 AM
To: axis-user@ws.apache.org
Subject: RE: [Axis2] trimming down the xml in axis2 1.3

Raghu,

I see in the archives that you ran into the same
problem as this. Did wsdl2java with -sp work for you?

Samir

--- Raghu Upadhyayula [EMAIL PROTECTED]
wrote:

 Samir,
 
   WSDL2Java can also be used to generate serverside
 code. Check
 WSDL2Java options, to create serverside code you
 need to specify the
 options -ss -sd -ssi (check the description for
 these options in
 WSDL2Java)
 
 You can use -sp option with WSDL2Java when you
 generate the serverside
 code in which case the namespace is suppressed on
 the serverside.
 
 Thanks
 Raghu
 
 -Original Message-
 From: samir shaikh [mailto:[EMAIL PROTECTED] 
 Sent: Wednesday, December 12, 2007 5:31 PM
 To: axis-user@ws.apache.org
 Subject: Re: [Axis2] trimming down the xml in axis2
 1.3
 
 Martin,
 
 You mean using QName in the client code?
 
 I'm trying to tune my server to not send back
 excessive xml. I cannot change the xml I send back
 to
 my clients. the extra ns: is causing me trouble
 after upgrading from axis2 1.1.1 to axis2 1.3 e.g.
 ns:fieldName0/ns:fieldName. My clients expect
 fieldName0/fieldName.
 
 Samir
 
 --- Martin Gainty [EMAIL PROTECTED] wrote:
 
  you can always use null..e.g.
   QName paramQName = new QName(, paramName);
  
  M--
  - Original Message -
  From: samir shaikh [EMAIL PROTECTED]
  To: axis-user@ws.apache.org
  Sent: Wednesday, December 12, 2007 7:20 PM
  Subject: RE: [Axis2] trimming down the xml in
 axis2
  1.3
  
  
   Raghu,
  
   Thanks for your help. I tried that out but I
 want
  to
   suppress it on the server. I think WSDL2Java is
  for
   generating a client, right?
  
   I'm hoping to find some configuration in
  services.xml
   or axis2.xml... any idea?
  
   Samir
  
  
   --- Raghu Upadhyayula
 [EMAIL PROTECTED]
   wrote:
  
Samir,
   
Try WSDL2Java with -sp option to suppress the
namespace prefix.
   
Thanks
Raghu
   
-Original Message-
From: samir shaikh
 [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 12, 2007 2:20 PM
To: axis-user@ws.apache.org
Subject: [Axis2] trimming down the xml in
 axis2
  1.3
   
Hi,
   
I'm trying to trim down the xml exchanged when
  using
a
axis2 client and server. Is there a way I can
configure the serializer to not prefix
 namespace
with
every element e.g.
  ns:errorCode0/ns:errorCode
can
just be errorCode0errorCode. Also not send
  back
the additional headers and field types with
 each
call.
I was able to do that in Axis1.3 with the wsdd
  file.
Can someone point me to where that is done in
  Axis2.
   
Thanks a lot.
   
Samir
   
   
   
   
  
 



Be a better friend, newshound, and
know-it-all with Yahoo! Mobile.  Try it now.
   
  
 

http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
   
   
   
   
  
 

-
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
   
   
   
  
 

-
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
   
   
  
  
  
  
 


 
  
   Be a better friend, newshound, and
   know-it-all with Yahoo! Mobile.  Try it now.
 

http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
  
  
  
 

-
   To unsubscribe, e-mail:
  [EMAIL PROTECTED]
   For additional commands, e-mail:
  [EMAIL PROTECTED]
  
  
  
  
 

-
  To unsubscribe, e-mail:
  [EMAIL PROTECTED]
  For additional commands, e-mail:
  [EMAIL PROTECTED]
  
  
 
 
 
  


 
 Be a better friend, newshound, and 
 know-it-all with Yahoo! Mobile.  Try it now.

http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
 
 
 

-
 To unsubscribe, e-mail:
 [EMAIL PROTECTED]
 
=== message truncated ===



 


Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 



RE: [Axis2] trimming down the xml in axis2 1.3

2007-12-13 Thread samir shaikh
Raghu,

I use the default databinding i.e. ADB. I typically
build a service and expose it and let Axis2 generate
my wsdl for me. This is actually working back.

I'll try it and let you know...

Thanks a lot!

Samir

--- Raghu Upadhyayula [EMAIL PROTECTED]
wrote:

 Samir,
 
 Yes, it worked for me.
 
 I used the WSDL2Java with -sp option to generate the
 server code.
 
 What data binding are you using?
 
 If you are using ADB, then you have to replace all
 the request 
 response classes.
 
 Thanks
 Raghu
 -Original Message-
 From: samir shaikh [mailto:[EMAIL PROTECTED] 
 Sent: Thursday, December 13, 2007 10:50 AM
 To: axis-user@ws.apache.org
 Subject: RE: [Axis2] trimming down the xml in axis2
 1.3
 
 Raghu,
 
 I see in the archives that you ran into the same
 problem as this. Did wsdl2java with -sp work for
 you?
 
 Samir
 
 --- Raghu Upadhyayula [EMAIL PROTECTED]
 wrote:
 
  Samir,
  
  WSDL2Java can also be used to generate serverside
  code. Check
  WSDL2Java options, to create serverside code you
  need to specify the
  options -ss -sd -ssi (check the description for
  these options in
  WSDL2Java)
  
  You can use -sp option with WSDL2Java when you
  generate the serverside
  code in which case the namespace is suppressed on
  the serverside.
  
  Thanks
  Raghu
  
  -Original Message-
  From: samir shaikh [mailto:[EMAIL PROTECTED] 
  Sent: Wednesday, December 12, 2007 5:31 PM
  To: axis-user@ws.apache.org
  Subject: Re: [Axis2] trimming down the xml in
 axis2
  1.3
  
  Martin,
  
  You mean using QName in the client code?
  
  I'm trying to tune my server to not send back
  excessive xml. I cannot change the xml I send back
  to
  my clients. the extra ns: is causing me trouble
  after upgrading from axis2 1.1.1 to axis2 1.3 e.g.
  ns:fieldName0/ns:fieldName. My clients expect
  fieldName0/fieldName.
  
  Samir
  
  --- Martin Gainty [EMAIL PROTECTED] wrote:
  
   you can always use null..e.g.
QName paramQName = new QName(, paramName);
   
   M--
   - Original Message -
   From: samir shaikh [EMAIL PROTECTED]
   To: axis-user@ws.apache.org
   Sent: Wednesday, December 12, 2007 7:20 PM
   Subject: RE: [Axis2] trimming down the xml in
  axis2
   1.3
   
   
Raghu,
   
Thanks for your help. I tried that out but I
  want
   to
suppress it on the server. I think WSDL2Java
 is
   for
generating a client, right?
   
I'm hoping to find some configuration in
   services.xml
or axis2.xml... any idea?
   
Samir
   
   
--- Raghu Upadhyayula
  [EMAIL PROTECTED]
wrote:
   
 Samir,

 Try WSDL2Java with -sp option to suppress
 the
 namespace prefix.

 Thanks
 Raghu

 -Original Message-
 From: samir shaikh
  [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, December 12, 2007 2:20 PM
 To: axis-user@ws.apache.org
 Subject: [Axis2] trimming down the xml in
  axis2
   1.3

 Hi,

 I'm trying to trim down the xml exchanged
 when
   using
 a
 axis2 client and server. Is there a way I
 can
 configure the serializer to not prefix
  namespace
 with
 every element e.g.
   ns:errorCode0/ns:errorCode
 can
 just be errorCode0errorCode. Also not
 send
   back
 the additional headers and field types with
  each
 call.
 I was able to do that in Axis1.3 with the
 wsdd
   file.
 Can someone point me to where that is done
 in
   Axis2.

 Thanks a lot.

 Samir




   
  
 


 
 Be a better friend, newshound, and
 know-it-all with Yahoo! Mobile.  Try it now.

   
  
 

http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ




   
  
 

-
 To unsubscribe, e-mail:
 [EMAIL PROTECTED]
 For additional commands, e-mail:
 [EMAIL PROTECTED]



   
  
 

-
 To unsubscribe, e-mail:
 [EMAIL PROTECTED]
 For additional commands, e-mail:
 [EMAIL PROTECTED]


   
   
   
 
=== message truncated ===



  

Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: axis2 https Unexpected EOF in prolog

2007-12-13 Thread Murali Krishnan
Not very sure if this will help, but you can try this in your client code:
Set this property as one of the options for the ServiceClient...

options.setProperty(org.apache.axis2.transport.http.HTTPConstants.CHUNKED, 
Boolean.FALSE);

Murali

- Original Message 
From: Marco Rossi [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Thursday, December 13, 2007 12:36:58 PM
Subject: axis2 https Unexpected EOF in prolog


Hi,
i have to test a webservices build with axis2 (tomcat6, linux red hat).
We have a reverse proxy to expose this service to the client (via SSL); so if i 
create a test client with axis2 (same library, same version) and use the 
internal endpoint (
http://myserver/myService) all works fine.
But il I try to test the same come with the reverse proxy endpoint 
https://myproxy/myService
 i get the following

org.apache.axis2.AxisFault: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF 
in prolog
 at [row,col {unknown-source}]: [1,0]

Any idea?

Thanks,
Marco







  

Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  
http://tools.search.yahoo.com/newsearch/category.php?category=shopping

Re: Can't Package Axis2 In EAR with Maven2

2007-12-13 Thread sumedha
Brandon,
This looks like mar plug-in is not being recognized inside your build
environment.
1. Leave out two projects having dependencies to Axis2.
2. Create a dummy project which just uses Axis2 MAR plug-in.
3. See if you can get EAR build run with this dummy project included as a
sub module.

/sumedha

 [INFO]
 
 [ERROR] BUILD ERROR
 [INFO]
 
 [INFO] Failed to initialize ear modules

 Embedded error: Unknown artifact type[mar]
 [INFO]
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Can't Package Axis2 In EAR with Maven2

2007-12-13 Thread devnulled

Sumedha,

Thanks for the response.   I just created a simple mock project and added
the maven-mar plugin, a couple of logging deps, and an empty mock class,
added it as a dependency to the main project, and commented-out references
to the two projects which have Axis2 dependencies.   It worked just fine and
built the full EAR.. here is a snippet of my pom.xml where I added the
plugin in the mock project:

build
plugins
  plugin
artifactIdmaven-ejb-plugin/artifactId
configuration
  ejbVersion3.0/ejbVersion
  archive
manifest
  addClasspathtrue/addClasspath
/manifest
  /archive
/configuration
  /plugin
  plugin
groupIdorg.apache.axis2/groupId
artifactIdaxis2-mar-maven-plugin/artifactId
version1.3/version
extensionstrue/extensions
configuration
  includeDependenciesfalse/includeDependencies
/configuration
  /plugin
/plugins
  /build


As far as I can tell this plugin gets resolved correctly? On a sidenote, I'm
using more than just the default Maven repo so I do have all of the rampart
deps, including the mar files in a resources folder).  So it looks like that
is not the problem?

Thanks,

- Brandon


sumedha rubasinghe wrote:
 
 Brandon,
 This looks like mar plug-in is not being recognized inside your build
 environment.
 1. Leave out two projects having dependencies to Axis2.
 2. Create a dummy project which just uses Axis2 MAR plug-in.
 3. See if you can get EAR build run with this dummy project included as a
 sub module.
 
 /sumedha
 
 [INFO]
 
 [ERROR] BUILD ERROR
 [INFO]
 
 [INFO] Failed to initialize ear modules

 Embedded error: Unknown artifact type[mar]
 [INFO]
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Can%27t-Package-Axis2-In-EAR-with-Maven2-tp14321321p14324846.html
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Can't Package Axis2 In EAR with Maven2

2007-12-13 Thread devnulled

I just /finally/ came across the fix for this particular problem.   I haven't
verified that everything still works because I have more EAR deployment work
and testing to do, but this particular problem went away by making all of
the Rampart dependencies as scopeprovided/scope.

After talking to a co-worker about how I fixed the problem, it totally made
sense given that we really only depend on Rampart at runtime.I probably
would have realized it much sooner had I written the code myself and having
an understanding about how Rampart actually works.

Thanks to all those who replied!

- Brandon


devnulled wrote:
 
 Sumedha,
 
 Thanks for the response.   I just created a simple mock project and added
 the maven-mar plugin, a couple of logging deps, and an empty mock class,
 added it as a dependency to the main project, and commented-out references
 to the two projects which have Axis2 dependencies.   It worked just fine
 and built the full EAR.. here is a snippet of my pom.xml where I added the
 plugin in the mock project:
 
 build
 plugins
   plugin
 artifactIdmaven-ejb-plugin/artifactId
 configuration
   ejbVersion3.0/ejbVersion
   archive
 manifest
   addClasspathtrue/addClasspath
 /manifest
   /archive
 /configuration
   /plugin
   plugin
 groupIdorg.apache.axis2/groupId
 artifactIdaxis2-mar-maven-plugin/artifactId
 version1.3/version
 extensionstrue/extensions
 configuration
   includeDependenciesfalse/includeDependencies
 /configuration
   /plugin
 /plugins
   /build
 
 
 As far as I can tell this plugin gets resolved correctly? On a sidenote,
 I'm using more than just the default Maven repo so I do have all of the
 rampart deps, including the mar files in a resources folder).  So it looks
 like that is not the problem?
 
 Thanks,
 
 - Brandon
 
 
 sumedha rubasinghe wrote:
 
 Brandon,
 This looks like mar plug-in is not being recognized inside your build
 environment.
 1. Leave out two projects having dependencies to Axis2.
 2. Create a dummy project which just uses Axis2 MAR plug-in.
 3. See if you can get EAR build run with this dummy project included as a
 sub module.
 
 /sumedha
 
 [INFO]
 
 [ERROR] BUILD ERROR
 [INFO]
 
 [INFO] Failed to initialize ear modules

 Embedded error: Unknown artifact type[mar]
 [INFO]
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Can%27t-Package-Axis2-In-EAR-with-Maven2-tp14321321p14326782.html
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



debugging a 400 Bad Request fault

2007-12-13 Thread Marc Esher
Greetings all. I've got a small project using  Axis 1.4. I just hit a
problem where I'm getting a 400 Bad Request error in a simple invocation.
The thing has worked fine for months, invoking the requests on multiple
servers, but when invoking the service on one particular server I get the
bad request fault. invoking the service outside of my program, on this
troublesome server, works fine (i.e. executing the wsdl directly in a
browser, for example).

Any tips on starting to debug this thing? I think what I need first is to
see what URL axis is actually trying to hit, but I can't seem to get at it,
as I don't know the API that well and my initial attempts at finding the
data i need have been unsuccessful.

I'm using old-school call.invoke() style invocation on this one.

thanks a lot.

marc


Setting up Axis in an Apache/Tomcat Environment

2007-12-13 Thread Jeremiah Weeden
Hello -

I am a newbie with Axis and am wondering if anyone has tried setting it up
on a server/workstation where tomcat and apache are both running. We have a
situation at work where we will be doing this and I'm wondering how
different the installation is compared to a pure tomcat installation (I have
already done a pure tomcat installation).  I know that files need to be in
different directories and potentially configuration files need to be
modified so I was just curious about how much different the installation
process would be.

Thanks!

-- 
Jeremiah


Re: Can't Package Axis2 In EAR with Maven2

2007-12-13 Thread Martin Gainty
DevNull that is a very unusual name

I found this link helpful to setup your dev environment
http://ws.apache.org/rampart/developer-guide.html

applicable bits are to
svn http://svn.apache.org/repos/asf/webservices/rampart/trunk/java/

this sets up a development folder called java which has a working
build.xml..!!!

there are 2 properties to setup assuming your username starts as DevNull
${username}=DevNull
dir.mvn2.repo=C:/Documents and
Settings/${username}/.m2/repositoryversion.xmlsec=1.4.0

so an example would be
${dir.mvn2.repo}/org/apache/santuario/xmlsec/${version.xmlsec}/xmlsec-${vers
ion.xmlsec}.jar

cd /java
ant
when all is said and done you have the version specific mar located in /dist
folder

HTH/
Martin--
- Original Message -
From: devnulled [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Thursday, December 13, 2007 6:14 PM
Subject: Re: Can't Package Axis2 In EAR with Maven2



 I just /finally/ came across the fix for this particular problem.   I
haven't
 verified that everything still works because I have more EAR deployment
work
 and testing to do, but this particular problem went away by making all of
 the Rampart dependencies as scopeprovided/scope.

 After talking to a co-worker about how I fixed the problem, it totally
made
 sense given that we really only depend on Rampart at runtime.I
probably
 would have realized it much sooner had I written the code myself and
having
 an understanding about how Rampart actually works.

 Thanks to all those who replied!

 - Brandon


 devnulled wrote:
 
  Sumedha,
 
  Thanks for the response.   I just created a simple mock project and
added
  the maven-mar plugin, a couple of logging deps, and an empty mock class,
  added it as a dependency to the main project, and commented-out
references
  to the two projects which have Axis2 dependencies.   It worked just fine
  and built the full EAR.. here is a snippet of my pom.xml where I added
the
  plugin in the mock project:
 
  build
  plugins
plugin
  artifactIdmaven-ejb-plugin/artifactId
  configuration
ejbVersion3.0/ejbVersion
archive
  manifest
addClasspathtrue/addClasspath
  /manifest
/archive
  /configuration
/plugin
plugin
  groupIdorg.apache.axis2/groupId
  artifactIdaxis2-mar-maven-plugin/artifactId
  version1.3/version
  extensionstrue/extensions
  configuration
includeDependenciesfalse/includeDependencies
  /configuration
/plugin
  /plugins
/build
 
 
  As far as I can tell this plugin gets resolved correctly? On a sidenote,
  I'm using more than just the default Maven repo so I do have all of the
  rampart deps, including the mar files in a resources folder).  So it
looks
  like that is not the problem?
 
  Thanks,
 
  - Brandon
 
 
  sumedha rubasinghe wrote:
 
  Brandon,
  This looks like mar plug-in is not being recognized inside your build
  environment.
  1. Leave out two projects having dependencies to Axis2.
  2. Create a dummy project which just uses Axis2 MAR plug-in.
  3. See if you can get EAR build run with this dummy project included as
a
  sub module.
 
  /sumedha
 
  [INFO]

 
  [ERROR] BUILD ERROR
  [INFO]

 
  [INFO] Failed to initialize ear modules
 
  Embedded error: Unknown artifact type[mar]
  [INFO]

 
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
 

 --
 View this message in context:
http://www.nabble.com/Can%27t-Package-Axis2-In-EAR-with-Maven2-tp14321321p14
326782.html
 Sent from the Axis - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[AXIS 2] SSL Error :Unconnected sockets not implemented

2007-12-13 Thread Srikanth Muthyala

Hello All, 

I am implementing Https to connect to service on tomcat. It works fine with 
Http. I made changes to tomcat to accept https port 8443. When I am using 
client stub I am setting  below properties. 
System. setProperty ( javax.net.ssl.keyStoreType , JKS ); 
System. setProperty ( javax.net.ssl.keyStorePassword , kspass ); 
System. setProperty ( javax.net.ssl.trustStorePassword , kspass ); 

When service invoked I get java .net.SocketException : Unconnected sockets not 
implemented 
When I googled I found page 
http://wiki.petals.objectweb.org/xwiki/bin/view/Components.Binding/Axis2BCUserguide
 saying this is a known bug. 

Has anybody got a workaround for this??? Any solutions?? 

Regards, 

Srikanth 

Re: [AXIS 2] SSL Error :Unconnected sockets not implemented

2007-12-13 Thread Martin Gainty
is trustStore set to the store location e.g.
  System.setProperty(javax.net.ssl.trustStore, 
${AXIS_HOME}/src/java/modules/integration/test-resources/rampart/store.jks);

is EPR should be set to SSL connection?
options.setTo(new 
EndpointReference(https://www-lk.wso2.com:8443/axis2/services/UTSAMLHoK;));

M-
  - Original Message - 
  From: Srikanth Muthyala 
  To: axis-user@ws.apache.org 
  Sent: Thursday, December 13, 2007 9:12 PM
  Subject: [AXIS 2] SSL Error :Unconnected sockets not implemented


  Hello All,

  I am implementing Https to connect to service on tomcat. It works fine with 
Http. I made changes to tomcat to accept https port 8443. When I am using 
client stub I am setting  below properties. 
  System.setProperty(javax.net.ssl.keyStoreType, JKS);
  System.setProperty(javax.net.ssl.keyStorePassword, kspass);
  System.setProperty(javax.net.ssl.trustStorePassword, kspass);

  When service invoked I get java.net.SocketException: Unconnected sockets not 
implemented
  When I googled I found page 
http://wiki.petals.objectweb.org/xwiki/bin/view/Components.Binding/Axis2BCUserguide
 saying this is a known bug.

  Has anybody got a workaround for this??? Any solutions?? 

  Regards,

  Srikanth 

Re: Setting up Axis in an Apache/Tomcat Environment

2007-12-13 Thread Charitha Kankanamge

Hi Jeremiah,
Are you referring to Axis2 or Axis1? If it is Axis2, please have a look 
at http://ws.apache.org/axis2/1_3/installationguide.html#servlet_container


regards
Charitha

Jeremiah Weeden wrote:


Hello -

I am a newbie with Axis and am wondering if anyone has tried setting 
it up on a server/workstation where tomcat and apache are both 
running. We have a situation at work where we will be doing this and 
I'm wondering how different the installation is compared to a pure 
tomcat installation (I have already done a pure tomcat installation).  
I know that files need to be in different directories and potentially 
configuration files need to be modified so I was just curious about 
how much different the installation process would be.


Thanks!

--
Jeremiah 




--
Charitha Kankanamge
WSO2 inc.
Flower Road, Colombo 07
+94 714268070





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[Axis2] 1.3 with MTOM - AxisFault: Connection reset in HTTPSender.sendViaPost

2007-12-13 Thread Pantvaidya, Vishwajit
Hello,

I have deployed my webservice using Axis2 1.3 (with the axiom jars patched for 
https://issues.apache.org/jira/browse/AXIS2-3196). This service receives calls 
from a .NET client and then makes calls to a .NET webservice (.NET 2.0 WSE 
3.0). After every few calls (about 10 or so), I get the Connection reset 
exception (stack trace copied at the end of this post) while trying to call the 
.NET service.


 1.  I tried disabling chunking as suggested at 
http://wso2.org/forum/thread/1878 - but then I get the error Transport error: 
403 Error: Access Forbidden at 
org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:298) 
at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:192)
 2.  My problem seems to be same as the one at 
https://issues.apache.org/jira/browse/AXIS2-1473 - which basically says that 
connection keeps on dropping because of the 100 continue messages from IIS. I 
cannot apply the IIS patch - so I was thinking I can use the http method param 
http.protocol.expect-continue so that the apache http client does not reset 
connection upon the 100 msgs from IIS.

Is this the right and only solution? If yes - can anyone suggest a good way to 
do this - I was thinking of configuring axis2.xml to use my custom class 
instead of axis2 CommonsHTTPSender and setting this param there.


Thanks,

Vish.


org.apache.axis2.AxisFault: Connection reset
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417)
at 
org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:195)
at 
org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77)
at 
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:327)
at 
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:206)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:396)
at 
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374)
at 
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
at 
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
at 
com.selectica.ws.pdfwordclient.wsdlgen.CPMPDFToWordStub.DownloadChunk(CPMPDFToWordStub.java:796)
at 
com.selectica.ws.ecm.ECMServiceSoapImpl.downloadChunk(ECMServiceSoapImpl.java:837)
at 
com.selectica.ws.ecm.wsdlgen.ECMServiceSoapMessageReceiverInOut.invokeBusinessLogic(ECMServiceSoapMessageReceiverInOut.java:358)
at 
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at 
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:96)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:145)
at 
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
at 
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:120)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at 
com.determine.servletfilter.CryptLinksFilter.doFilter(CryptLinksFilter.java:80)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at 
com.determine.servletfilter.ExceptionCatcherFilter.doFilter(ExceptionCatcherFilter.java:72)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at 

Re: [Axis2] Unable to deserialize OMElement

2007-12-13 Thread Ramesh Gurunathan
I got a similar issue some time ago, then I found out that cleanup  
call on the stub closed the connection and is the cause of this error.  
Don't call cleanup untill you read the XML completely.



On Dec 13, 2007, at 7:00 AM, Lositski Vadim [EMAIL PROTECTED] 
 wrote:



Hello,

I've done additional research on this topic, and it seems that the  
problem is in the size of the response XML envelope.

When I am trying to print out the resulted OMElement:

result.serializeAndConsume(System.out);

Only first 4000 characters are printed and then  following exception  
is thrown: java.lang.RuntimeException: [was class  
java.io.IOException] Attempted read on closed stream


Stange is that when the operation returns XML which length is less  
than 4000 characters everything works fine.
Also when I use this operation in async mode, everything is also  
fine, response size irrespectively.


Do you know about this limitation?

Thanks in advance,
Vadim

-Original Message-
From: Lositski Vadim
Sent: Wednesday, December 12, 2007 5:19 PM
To: axis-user@ws.apache.org
Subject: [Axis2] Unable to deserialize OMElement

Hi everybody,

I am sending a request to the service which combines its response  
from various sources, then creates an OMElement and sends it back.  
The databinding and deserialization is made with Castor and Stax  
APIs basically as it is described in the databinding example from  
Axis2 distribution.


When I am trying to create an object from an OMElement received from  
the service


StAXSource staxSource = new StAXSource(result.getXMLStreamReader());
Unmarshaller unmarshaller = new Unmarshaller(TargetClass.class);
UnmarshalHandler unmarshalHandler = unmarshaller.createHandler();
try {
   ContentHandler contentHandler = (ContentHandler)  
Unmarshaller.getContentHandler(unmarshalHandler);
   TransformerFactory.newInstance().newTransformer().transform 
(staxSource, new SAXResult(contentHandler));

}
catch (Exception ex) {
   ex.printStackTrace();
}
TargetClass response = (TargetClass) unmarshalHandler.getObject();

I receive a NullPointerException exception:

java.lang.NullPointerException
at javanet.staxutils.StAXSource$1.parse(StAXSource.java:196)
at javanet.staxutils.StAXSource$1.parse(StAXSource.java:181)
at org.apache.xalan.transformer.TransformerIdentityImpl.transform 
(TransformerIdentityImpl.java:484)
at  
com.profitsoftware.webservices.central.CentralWebServiceTester.main 
(CentralWebServiceTester.java:85)


The object is serialized, but partially some data fields are null

I have also tried to just print out the OMElement, but received:

Exception in thread main java.lang.StackOverflowError
   at org.apache.axiom.om.impl.llom.OMNodeImpl.setComplete 
(OMNodeImpl.java:174)
   at org.apache.axiom.om.impl.llom.OMNodeImpl.setComplete 
(OMNodeImpl.java:174)
   at org.apache.axiom.om.impl.llom.OMNodeImpl.setComplete 
(OMNodeImpl.java:174)


When I use OMElement.toStringWithConsume() I have the following  
exception:


java.lang.RuntimeException: [was class java.io.IOException]  
Attempted read on closed stream.
   at com.ctc.wstx.util.ExceptionUtil.throwRuntimeException 
(ExceptionUtil.java:18)
   at com.ctc.wstx.sr.StreamScanner.throwLazyError 
(StreamScanner.java:706)
   at com.ctc.wstx.sr.BasicStreamReader.safeFinishToken 
(BasicStreamReader.java:3655)
   at com.ctc.wstx.sr.BasicStreamReader.getText 
(BasicStreamReader.java:809)
   at org.apache.axiom.om.impl.llom.OMStAXWrapper.getText 
(OMStAXWrapper.java:364)
   at  
org. 
apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeText 
(StreamingOMSerializer.java:339)
   at  
org. 
apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeNode 
(StreamingOMSerializer.java:79)
   at  
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serialize 
(StreamingOMSerializer.java:57)
   at  
org.apache.axiom.om.impl.util.OMSerializerUtil.serializeByPullStream 
(OMSerializerUtil.java:525)
   at  
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize 
(OMElementImpl.java:795)
   at  
org. 
apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume 
(OMElementImpl.java:814)
   at  
org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume 
(OMNodeImpl.java:358)
   at  
org.apache.axiom.om.impl.llom.OMElementImpl.toStringWithConsume 
(OMElementImpl.java:904)
   at  
com.profitsoftware.webservices.central.CentralWebServiceTester.main 
(CentralWebServiceTester.java:79)

Caused by: java.io.IOException: Attempted read on closed stream.
   at  
org.apache.commons.httpclient.AutoCloseInputStream.isReadAllowed 
(AutoCloseInputStream.java:165)
   at org.apache.commons.httpclient.AutoCloseInputStream.read 
(AutoCloseInputStream.java:106)

   at java.io.FilterInputStream.read(FilterInputStream.java:111)
   at java.io.PushbackInputStream.read(PushbackInputStream.java: 
161)

   at java.io.FilterInputStream.read(FilterInputStream.java:90)
  

Re: [AXIS 2] SSL Error :Unconnected sockets not implemented

2007-12-13 Thread Srikanth Muthyala

Martin, 

thanks its working now. The issue was as I am testing I am using same file 
keystore and trust store (selfsigned) for client and server. For keystore as we 
know if file name/path not specified it looks up in the user's home directory. 
I thought same should be for truststore. But when I explicitly provided 
javax.net.ssl.trustStore with absolute path of SAME file it worked. I am not 
sure why it failed before. 

Regards, 

Srikanth  



- Original Message - 
From: Martin Gainty [EMAIL PROTECTED] 
To: axis-user@ws.apache.org 
Sent: Friday, 14 December 2007 01:54:00 PM (GMT+1000) Australia/Sydney 
Subject: Re: [AXIS 2] SSL Error :Unconnected sockets not implemented 

 

is trustStore set to the store location e.g. 
  System.setProperty(javax.net.ssl.trustStore, 
${AXIS_HOME}/src/java/modules/integration/test-resources/rampart/store.jks); 

is EPR should be set to SSL connection? 
    options.setTo(new EndpointReference( 
https://www-lk.wso2.com:8443/axis2/services/UTSAMLHoK )); 

M- 


- Original Message - 
From: Srikanth Muthyala 
To: axis-user@ws.apache.org 
Sent: Thursday, December 13, 2007 9:12 PM 
Subject: [AXIS 2] SSL Error :Unconnected sockets not implemented 


Hello All, 

I am implementing Https to connect to service on tomcat. It works fine with 
Http. I made changes to tomcat to accept https port 8443. When I am using 
client stub I am setting  below properties. 
System. setProperty ( javax.net.ssl.keyStoreType , JKS ); 
System. setProperty ( javax.net.ssl.keyStorePassword , kspass ); 
System. setProperty ( javax.net.ssl.trustStorePassword , kspass ); 

When service invoked I get java .net.SocketException : Unconnected sockets not 
implemented 
When I googled I found page 
http://wiki.petals.objectweb.org/xwiki/bin/view/Components.Binding/Axis2BCUserguide
 saying this is a known bug. 

Has anybody got a workaround for this??? Any solutions?? 

Regards, 

Srikanth 

Re: Setting up Axis in an Apache/Tomcat Environment

2007-12-13 Thread Jeremiah Weeden
We're actually using axis1. Is that going to make a big difference?

- Jeremiah

On Dec 13, 2007 7:39 PM, Charitha Kankanamge [EMAIL PROTECTED] wrote:

 Hi Jeremiah,
 Are you referring to Axis2 or Axis1? If it is Axis2, please have a look
 at http://ws.apache.org/axis2/1_3/installationguide.html#servlet_container

 regards
 Charitha

 Jeremiah Weeden wrote:

  Hello -
 
  I am a newbie with Axis and am wondering if anyone has tried setting
  it up on a server/workstation where tomcat and apache are both
  running. We have a situation at work where we will be doing this and
  I'm wondering how different the installation is compared to a pure
  tomcat installation (I have already done a pure tomcat installation).
  I know that files need to be in different directories and potentially
  configuration files need to be modified so I was just curious about
  how much different the installation process would be.
 
  Thanks!
 
  --
  Jeremiah



 --
 Charitha Kankanamge
 WSO2 inc.
 Flower Road, Colombo 07
 +94 714268070





 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




-- 
Jeremiah


Re: Setting up Axis in an Apache/Tomcat Environment

2007-12-13 Thread Charitha Kankanamge
Though i'm not sure about Axis1, 
http://ws.apache.org/axis/java/install.html#Step2SettingUpTheLibraries 
will help you a bit. Someone familiar with Axis1 may provide more 
explanation.


regards
Charitha

Jeremiah Weeden wrote:


We're actually using axis1. Is that going to make a big difference?

- Jeremiah

On Dec 13, 2007 7:39 PM, Charitha Kankanamge [EMAIL PROTECTED] 
mailto:[EMAIL PROTECTED] wrote:


Hi Jeremiah,
Are you referring to Axis2 or Axis1? If it is Axis2, please have a
look
at
http://ws.apache.org/axis2/1_3/installationguide.html#servlet_container

regards
Charitha

Jeremiah Weeden wrote:

 Hello -

 I am a newbie with Axis and am wondering if anyone has tried setting
 it up on a server/workstation where tomcat and apache are both
 running. We have a situation at work where we will be doing this and
 I'm wondering how different the installation is compared to a pure
 tomcat installation (I have already done a pure tomcat
installation).
 I know that files need to be in different directories and
potentially
 configuration files need to be modified so I was just curious about
 how much different the installation process would be.

 Thanks!

 --
 Jeremiah



--
Charitha Kankanamge
WSO2 inc.
Flower Road, Colombo 07
+94 714268070





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]




--
Jeremiah 




--
Charitha Kankanamge
WSO2 inc.
Flower Road, Colombo 07
+94 714268070

A bug in the hand is better than one as yet undetected



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Setting up Axis in an Apache/Tomcat Environment

2007-12-13 Thread samir shaikh
Hi,

I did this several years ago, but I'll give it a shot
at explaining how it was done as far as I can
remember.

The process for axis1 is similar to just setting up a
web application and wiring it into the web server just
like a servlet. The web.xml will contain references to
AxisServlet. This servlet will initialize the web
service environment. There is a java tool called
AdminClient which takes service definition in the form
of a wsdd file. This tool deploys the service on the
server.

HTH.

Samir


--- Charitha Kankanamge [EMAIL PROTECTED] wrote:

 Though i'm not sure about Axis1, 

http://ws.apache.org/axis/java/install.html#Step2SettingUpTheLibraries
 
 will help you a bit. Someone familiar with Axis1 may
 provide more 
 explanation.
 
 regards
 Charitha
 
 Jeremiah Weeden wrote:
 
  We're actually using axis1. Is that going to make
 a big difference?
 
  - Jeremiah
 
  On Dec 13, 2007 7:39 PM, Charitha Kankanamge
 [EMAIL PROTECTED] 
  mailto:[EMAIL PROTECTED] wrote:
 
  Hi Jeremiah,
  Are you referring to Axis2 or Axis1? If it is
 Axis2, please have a
  look
  at
 

http://ws.apache.org/axis2/1_3/installationguide.html#servlet_container
 
  regards
  Charitha
 
  Jeremiah Weeden wrote:
 
   Hello -
  
   I am a newbie with Axis and am wondering if
 anyone has tried setting
   it up on a server/workstation where tomcat
 and apache are both
   running. We have a situation at work where
 we will be doing this and
   I'm wondering how different the installation
 is compared to a pure
   tomcat installation (I have already done a
 pure tomcat
  installation).
   I know that files need to be in different
 directories and
  potentially
   configuration files need to be modified so I
 was just curious about
   how much different the installation process
 would be.
  
   Thanks!
  
   --
   Jeremiah
 
 
 
  --
  Charitha Kankanamge
  WSO2 inc.
  Flower Road, Colombo 07
  +94 714268070
 
 
 
 
 
 

-
  To unsubscribe, e-mail:
 [EMAIL PROTECTED]
  mailto:[EMAIL PROTECTED]
  For additional commands, e-mail:
 [EMAIL PROTECTED]
  mailto:[EMAIL PROTECTED]
 
 
 
 
  -- 
  Jeremiah 
 
 
 
 -- 
 Charitha Kankanamge
 WSO2 inc.
 Flower Road, Colombo 07
 +94 714268070
 
 A bug in the hand is better than one as yet
 undetected
 
 
 

-
 To unsubscribe, e-mail:
 [EMAIL PROTECTED]
 For additional commands, e-mail:
 [EMAIL PROTECTED]
 
 



  

Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  
http://tools.search.yahoo.com/newsearch/category.php?category=shopping

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]