Re: undefined 'scandir' and 'alphsort'

[ramesh Gopal]

These function are available only from SOL 10 onwards.

You will probably need to write an equivalent of those functions



  Your Mail works best with the New Yahoo Optimized IE8. Get it NOW! 
http://downloads.yahoo.com/in/internetexplorer/

Re: Client API problem

[Amir Mousavizadegan]

For your first question, it seems to me you are losing a socket connection 
or timeout on the connection to server, check your network. For your  second 
problem, it  may be  is related to  drop of socket from first question.

thx
Amir
- Original Message - 
From: Fan, Jan-fon jan-fon@intel.com

To: Apache AXIS C User List axis-c-user@ws.apache.org
Sent: Thursday, February 18, 2010 10:39 PM
Subject: Client API problem


Hi,
I am using AXIS2C client api in my application to access web services which 
is developed with .NET.

The way that I send my request is as below:

   /* Send request */
   ret_node = axis2_svc_client_send_receive(svc_client, env, payload);

   if (ret_node)
   {
   axis2_char_t *om_str = NULL;
   om_str = axiom_node_to_string(ret_node, env);
   if (om_str)
   printf(\nReceived OM : %s\n, om_str);
   printf(\nclient invoke SUCCESSFUL!\n);

   AXIS2_FREE(env-allocator, om_str);
   ret_node = NULL;
   }
   else
   {
   AXIS2_LOG_ERROR(env-log, AXIS2_LOG_SI,
   Stub invoke FAILED: Error code:  %d :: %s,
   env-error-error_number,
   AXIS2_ERROR_GET_MESSAGE(env-error));
   printf(client invoke FAILED!\n);
   }

I have 2 questions:
1. I send my requests in a loop. Inside the loop, I keep sending about 30 
requests to the same web service. Sometime one or more requests would print 
out client  invoke FAILED. What could be the reason that causes this 
problem?


2. Sometime when I print out the result from server, it only contain partial 
information.



Really appreciate your help!

Jan-fon

Re: Axis2-1.5.1 and user exceptions

[Mauro Molinari]

Il 17/02/2010 3.53, glopezm ha scritto:

Any thoughts/experiences with a similar issues with axis2?


I use contract-first approach. My user exceptions extend Exception and 
have a field called faultMessage with getter getFaultMessage and setter 
setFaultMessage. The constructor prepares the faultMessage and sets it 
via setFaultMessage. The faultMessage is an object of a class generated 
by WSDL2Code from an XMLSchema type that describes my fault message, so 
that it implements ADBBean.


In this way, when my code raises my user defined exception, Axis2 
recognizes the existence of the fault message and attaches it correctly 
to the fault returned to the client code.


This is the result of my trial-and-errors researches of some years ago 
with Axis2 1.3 and it is working with Axis2 1.5 too. I think that you 
may find something else in this mailing list archive by me on this subject.


--
Mauro Molinari
Software Designer  Developer
E-mail: mauro.molin...@cardinis.com

Re: Axis2-1.5.1 and user exceptions

[Li Ma]

I have been puzzled by this issue for long time. Seams like at this point,
using contract-first approach is the only solution for now.

But it will still be very very helpful if something can be done so
code-first approach can work too. Axis1 definitely worked. I can imagine
lots of people are using code-first approach because of its simplicity.

Thanks!

Li

On Fri, Feb 19, 2010 at 6:42 AM, Mauro Molinari mauro.molin...@cardinis.com
 wrote:

 Il 17/02/2010 3.53, glopezm ha scritto:

  Any thoughts/experiences with a similar issues with axis2?


 I use contract-first approach. My user exceptions extend Exception and have
 a field called faultMessage with getter getFaultMessage and setter
 setFaultMessage. The constructor prepares the faultMessage and sets it via
 setFaultMessage. The faultMessage is an object of a class generated by
 WSDL2Code from an XMLSchema type that describes my fault message, so that it
 implements ADBBean.

 In this way, when my code raises my user defined exception, Axis2
 recognizes the existence of the fault message and attaches it correctly to
 the fault returned to the client code.

 This is the result of my trial-and-errors researches of some years ago with
 Axis2 1.3 and it is working with Axis2 1.5 too. I think that you may find
 something else in this mailing list archive by me on this subject.

 --
 Mauro Molinari
 Software Designer  Developer
 E-mail: mauro.molin...@cardinis.com




-- 
Li Ma
lim...@gmail.com

RE: Axis2-1.5.1 and user exceptions

[Martin Gainty]

Hello Li

the biggest problem with a contract is you are bound to fixed record

doc-literal-encoded has been around for 7 years and has been deployed numerous 
times on numerous production sites
Here is a good whitepaper to read on the advantages of doc-literal over RPC
http://www.ibm.com/developerworks/webservices/library/ws-whichwsdl/

also DOC-LITERAL (with encoding) is clearly the best choice for complex 
structures over any RPC based implementation

ALSO rpc is using a remote procedure call to call the function with the 
parameters leaving a HUGE security hole 
in your webservice with the open port you are using to the RPC method

AXIS2 is heavily favoring doc-literal over RPC for above stated reasons 

when you state ..it definitely worked under axis1 ..are you stating you must 
specify RPC over doc-literal?
Is the use of RPC a stated  business requirement?

Martin Gainty 
__ 
please do not modify or disrupt this transmission. Thank You




Date: Fri, 19 Feb 2010 09:15:03 -0500
Subject: Re: Axis2-1.5.1 and user exceptions
From: lim...@gmail.com
To: axis-user@ws.apache.org

I have been puzzled by this issue for long time. Seams like at this point, 
using contract-first approach is the only solution for now.
But it will still be very very helpful if something can be done so code-first 
approach can work too. Axis1 definitely worked. I can imagine lots of people 
are using code-first approach because of its simplicity.

Thanks!
Li

On Fri, Feb 19, 2010 at 6:42 AM, Mauro Molinari mauro.molin...@cardinis.com 
wrote:

Il 17/02/2010 3.53, glopezm ha scritto:


Any thoughts/experiences with a similar issues with axis2?




I use contract-first approach. My user exceptions extend Exception and have a 
field called faultMessage with getter getFaultMessage and setter 
setFaultMessage. The constructor prepares the faultMessage and sets it via 
setFaultMessage. The faultMessage is an object of a class generated by 
WSDL2Code from an XMLSchema type that describes my fault message, so that it 
implements ADBBean.




In this way, when my code raises my user defined exception, Axis2 recognizes 
the existence of the fault message and attaches it correctly to the fault 
returned to the client code.



This is the result of my trial-and-errors researches of some years ago with 
Axis2 1.3 and it is working with Axis2 1.5 too. I think that you may find 
something else in this mailing list archive by me on this subject.




-- 

Mauro Molinari

Software Designer  Developer

E-mail: mauro.molin...@cardinis.com



-- 
Li Ma
lim...@gmail.com


  
_
Your E-mail and More On-the-Go. Get Windows Live Hotmail Free.
http://clk.atdmt.com/GBL/go/201469229/direct/01/

Re: Sandesha2 1.5 Release Candidate

[David Parsons1]

Hi Amila,

Definitely.  I was planning on getting to this asap.  I will try to get to 
it today and put the vote out.

Regards,

Dave

Dave Parsons
Web Services Development
INTERNAL:  David Parsons1/UK/i...@ibmgb :: DE3F20 :: 246930
EXTERNAL:  parso...@uk.ibm.com :: (01962) 816930
Mail Point 211, IBM Hursley Park, Winchester. SO21 2JN




From:
Amila Suriarachchi amilasuriarach...@gmail.com
To:
David Parsons1/UK/i...@ibmgb
Cc:
axis-user@ws.apache.org, sandesha-...@ws.apache.org, 
axis-...@ws.apache.org, gene...@ws.apache.org
Date:
18/02/2010 04:55
Subject:
Re: Sandesha2 1.5 Release Candidate



since rampart 1.5 has been released shall we do the sandesha release?

thanks,
Amila.

On Tue, Oct 6, 2009 at 9:07 PM, David Parsons1 parso...@uk.ibm.com 
wrote:

Hi, 

I have created a Sandesha2 1.5 release candidate here: 

http://people.apache.org/~parsonsd/sandesha-1.5/RC1/dist/ 

and the M2 repository can be found here: 

http://people.apache.org/~parsonsd/sandesha-1.5/RC1/m2_repo/ 

This release candidate is using the Rampart 1.5 release candidate which 
can be found: 

 http://people.apache.org/~nandana/rampart-1.5/RC1/dist/ 

and the M2 repository for this can be found here: 

   http://people.apache.org/~nandana/rampart-1.5/RC1/m2_repo/ 


I will leave this available for a short period of time.  If no one finds 
any issues I'll request a vote on whether to submit it as a release of 
Sandesha2.  The Rampart 1.5 release is going to have to be cut before I 
can officially cut the Sandesha2 release so does anyone know how close 
this is to being done? 

Regards, 

Dave 

Dave Parsons
Web Services Development
INTERNAL:  David Parsons1/UK/i...@ibmgb :: DE3F20 :: 246930
EXTERNAL:  parso...@uk.ibm.com :: (01962) 816930
Mail Point 211, IBM Hursley Park, Winchester. SO21 2JN





Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU 












Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU 









-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/







Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Re: Can't get Axis handlers to work

[Joe Ammann]

On Thursday 18 February 2010 16:15:03 Joe Ammann wrote:
 And - my problem - the handler.invoke() is never called.
 
 Any hints what I'm doing wrong?

Ok, https://issues.apache.org/jira/browse/AXIS2-3588 was extremly helpful :-)

Of course, I also got the XML tags case wrong :-/ Now it works

-- 
CU, Joe

Re: How to create a SSL client to support https

[Ashok P]

Hi Dumindu,

As per your suggestions if client won't need any authentication, only
SERVER_CERT is required. I am not sure why SERVER_CERT also required. Here
server certificate may expire and so on.

Is it easy to make changes in src\core\transport\http\sender\ssl\ssl_utils.c
for SSL_VERIFY_NONE?? I don't want any type of validation for client.

Thanks in Advance. 

Thanks,
Ashok


Dumindu Pallewela wrote:
 
 Hi Kelvin,
 
 If you didn't know this already:
 You do *not* have to set ssl parameters *both* in axis2.xml and in your 
 client code. We have given the user the option to choose which he prefers.
 
 Please further comments inline.
 
 Regards,
 Dumindu.
 
 In short, I configure axis2.xml as:
 
 transportSender name=https class=axis2_http_sender
 parameter name=PROTOCOL locked=falseHTTP/1.1/parameter
 /transportSender
 !--parameter 
 name=SERVER_CERTE:/Project/VS8/Axis2_prototype/debug/TrustList.pem/parameter--
 !--parameter 
 name=KEY_FILEE:\Project\VS8\Axis2_prototype\debug\TrustList.pem/parameter
 parameter name=SSL_PASSPHRASEpassphrase/parameter--
 
 !-- -- tag in XML makes whatever it encloses a comment. Thus, in the 
 above, SERVER_CERT parameter is not set. Only the client key's pass 
 phrase, which you don't need, is set from the above configuration.
 
 Since you have mentioned that you don't need client authentication, 
 please remove the last two lines, so that you don't have unnecessary
 stuff:
 
 transportSender name=https class=axis2_http_sender
  parameter name=PROTOCOL locked=falseHTTP/1.1/parameter
 /transportSender
 parameter 
 name=SERVER_CERTE:/Project/VS8/Axis2_prototype/debug/TrustList.pem/parameter
 
 Then run your axis client making sure that the AXIS2C_HOME is set to the 
 directory where the now edited axis2.xml resides.
 
 Also your epr should start with https://
 
 If this doesn't work, there is no point in trying setting these 
 parameters in client code.
 
 And I create TrustList.pem file following the manual of Axis2/C:
 
 For testing purposes, you can use the server's certificate instead of 
 the CA certificate. You can obtain this by running the command |openssl 
 s_client -connect servername:port| and copying the portion of the 
 output bounded by and including:
 
 -BEGIN CERTIFICATE-
 -END CERTIFICATE-
 
 Get the content of this file is:
 
 -BEGIN
  CERTIFICATE-
 MIIB7TCCAVagAwIBAgIEPygs+DANBgkqhkiG9w0BAQQFADA7MQswCQYDVQQGEwJV
 UzEMMAoGA1UEChMDSUJNMQwwCgYDVQQLEwNTV0cxEDAOBgNVBAMTB2pzZXJ2ZXIw
 HhcNMDMwNzMwMjAzOTIwWhcNMjExMDEzMjAzOTIwWjA7MQswCQYDVQQGEwJVUzEM
 MAoGA1UEChMDSUJNMQwwCgYDVQQLEwNTV0cxEDAOBgNVBAMTB2pzZXJ2ZXIwgZ8w
 DQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAIQhMysAHrupK8YLnu54xipwbYfJw1ac
 xMSNQPphN2ZQEznGNp1E8tONwN4RJ4nCW/5mQRFkErOUJW3ZQKP/gwK37HwKz1+V
 OVOlQ9fitArsnEZTeqzdmBLa+vx7B7bZ8bIRPzI0CeWgQiYZZjSCsZz8JcQZxLM6
 ob9mKE28VeZvAgMBAAEwDQYJKoZIhvcNAQEEBQADgYEAEPCRwEUBxz6+9A5/AoPB
 LiYInrowLfY+w3xJyDCie+GneLnirL+1HXRBbNOJYQTCpzN00Cgq2M/LU6tUeeZQ
 3gwidiqFUculi2Z+8wd60q8vy6qdJ1kvg9atwMdQV2LFf7TPNccmULD9/LV9h3AV
 oBbsFukZAroF0ZvO+/4vrIk=
 -END CERTIFICATE-

 
 This is fine.
 
 My colleague once tried to
  send soap message created by gsoap,
 although the message itself is wrong. But he still get some error
 message back and in the console of the server, there are some error
 messages like I mentioned before.
 
 can you send those error messages? even if that is not axis2 we may be 
 able to get an idea about what's going wrong.
 
 -
 To unsubscribe, e-mail: axis-c-user-unsubscr...@ws.apache.org
 For additional commands, e-mail: axis-c-user-h...@ws.apache.org
 
 
 

-- 
View this message in context: 
http://old.nabble.com/How-to-create-a-SSL-client-to-support-https-tp11441745p27621164.html
Sent from the Axis - C++ - User mailing list archive at Nabble.com.

Re: Sandesha2 1.5 Release Candidate

[Amila Suriarachchi]

since rampart 1.5 has been released shall we do the sandesha release?

thanks,
Amila.

On Tue, Oct 6, 2009 at 9:07 PM, David Parsons1 parso...@uk.ibm.com wrote:


 Hi,

 I have created a Sandesha2 1.5 release candidate here:

 
 http://people.apache.org/~parsonsd/sandesha-1.5/RC1/dist/http://people.apache.org/%7Eparsonsd/sandesha-1.5/RC1/dist/

 and the M2 repository can be found here:

 
 http://people.apache.org/~parsonsd/sandesha-1.5/RC1/m2_repo/http://people.apache.org/%7Eparsonsd/sandesha-1.5/RC1/m2_repo/

 This release candidate is using the Rampart 1.5 release candidate which can
 be found:

  
 *http://people.apache.org/~nandana/rampart-1.5/RC1/dist/*http://people.apache.org/%7Enandana/rampart-1.5/RC1/dist/

 and the M2 repository for this can be found here:
 *

 **http://people.apache.org/~nandana/rampart-1.5/RC1/m2_repo/*http://people.apache.org/%7Enandana/rampart-1.5/RC1/m2_repo/


 I will leave this available for a short period of time.  If no one finds
 any issues I'll request a vote on whether to submit it as a release of
 Sandesha2.  The Rampart 1.5 release is going to have to be cut before I can
 officially cut the Sandesha2 release so does anyone know how close this is
 to being done?

 Regards,

 Dave

 Dave Parsons
 Web Services Development
 INTERNAL:  David Parsons1/UK/i...@ibmgb :: DE3F20 :: 246930
 EXTERNAL:  parso...@uk.ibm.com :: (01962) 816930
 Mail Point 211, IBM Hursley Park, Winchester. SO21 2JN



  --

 *
 *

 *Unless stated otherwise above:
 IBM United Kingdom Limited - Registered in England and Wales with number
 741598.
 Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
 *










  --

 *
 *

 *Unless stated otherwise above:
 IBM United Kingdom Limited - Registered in England and Wales with number
 741598.
 Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
 *









-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Re: Receive WSSecurityException (The signature verification failed)

[Hans-Bernhard Friedrich]

)
 at org.apache.catalina.core.StandardPipeline
$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594)
 at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:433)
 at org.apache.catalina.core.ContainerBase.invoke
(ContainerBase.java:955)
 at org.apache.catalina.core.StandardContext.invoke
(StandardContext.java:2460)
 at org.apache.catalina.core.StandardHostValve.invoke
(StandardHostValve.java:133)
 at org.apache.catalina.core.StandardPipeline
$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
 at org.apache.catalina.valves.ErrorDispatcherValve.invoke
(ErrorDispatcherValve.java:119)
 at org.apache.catalina.core.StandardPipeline
$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594)
 at org.apache.catalina.valves.ErrorReportValve.invoke
(ErrorReportValve.java:117)
 at org.apache.catalina.core.StandardPipeline
$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594)
 at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:433)
 at org.apache.catalina.core.ContainerBase.invoke
(ContainerBase.java:955)
 at org.apache.catalina.core.StandardEngineValve.invoke
(StandardEngineValve.java:127)
 at org.apache.catalina.core.StandardPipeline
$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
 at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:433)
 at org.apache.catalina.core.ContainerBase.invoke
(ContainerBase.java:955)
 at org.apache.coyote.tomcat4.CoyoteAdapter.service
(CoyoteAdapter.java:157)
 at org.apache.jk.server.JkCoyoteHandler.invoke
(JkCoyoteHandler.java:200)
 at org.apache.jk.common.HandlerRequest.invoke
(HandlerRequest.java:283)
 at org.apache.jk.common.ChannelSocket.invoke
(ChannelSocket.java:773)
 at org.apache.jk.common.ChannelSocket.processConnection
(ChannelSocket.java:703)
 at org.apache.jk.common.ChannelSocket$SocketConnection.runIt
(ChannelSocket.java:895)
 at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run
(ThreadPool.java:689)
 at java.lang.Thread.run(Thread.java:619)]


Greetings
Hans


 From:
 
 Nandana Mihindukulasooriya nandana@gmail.com
 
 To:
 
 axis-user@ws.apache.org
 
 Date:
 
 15.02.2010 23:52
 
 Subject:
 
 Re: Receive WSSecurityException (The signature verification failed)
 
 Hans,
  Can you post the stacktrace too. Might be helpful to figure out
 what exactly is happening. 
 
 regards,
 Nandana 

 On Mon, Feb 15, 2010 at 7:17 PM, Hans-Bernhard Friedrich 
 h.friedr...@levigo.de wrote:
 Hi, 
 
 I work on a webservice client and I always receive the same error 
 when I try to make a request to our clients webservice. 
 
 org.apache.ws.security.WSSecurityException (The signature 
 verification failed) 
 
 - Our client's webservice is axis-based, more I don't know 
 
 - I use rampart 1.3 and Axis2 1.4.1, EclipseEE 
 - I generated the customers WSDLs with axis2 1.4.1 in EclipseEE 
 - I received certificates of our customer and imported them to a 
keystore 
 - I set up the the security using outflow configuration. I know it's
 deprecated but it seemed easier to me than using a policy.xml. 
 - I also set up a client using a policy.xml signing the body but 
 reveice the same error. I will change to policy in the next step. 
 
 - I read all I could find on the web and in mailinglists but nothing 
helped: 
 - XML is UTF-B 
 - JVM argument language=EN didn't help 
 - Mixing different Axis2 and rampart versions didn't help 
 - Changing xmlsec1.4.0. jar to  1.4.1 or 1.4.2 didn't help 
 - The certs are have not expired 
 - Eclipse' Workspace encoding is UTF-8 
 
 Question: 
 - Does the exception really mean the SOAP-Envelope has been changed 
 after is was singed? Are there any other reasons this exception 
 could be thrown? 
 
 - What is about the Pretty Printing of the XML issue I've found on
 the mailing list. This this really solved in axis2 1.4.1? 
 - Is there a way to set up namespace optimation and pretty printing 
 manually in axis2 like in axis 1? 
 - Could somethig else be wrong with the certificates? 
 
 The thing is when I use the a modified sample using a policy.xml I 
 get the same Exception 
 
 - Is there anything I could tell our client to changed what could help 
me? 
 
 What did I do special: 
 - Wrote a little handler to avoid mustunderstand-Problem in the 
 response: I Set all headers in the response to processed. The error 
 also occurs if I don't engage my handler 
 
 Here is my Security setup using outflowConfiguration: 
 
 ...options.setProperty(WSSHandlerConstants.OUTFLOW_SECURITY, 
 getOutflowConfiguration()); 
 ... 
 private  Parameter getOutflowConfiguration() { 
 OutflowConfiguration ofc = new OutflowConfiguration(); 
 ofc.setActionItems(Timestamp Signature

Re: where is SVN repo http.// svn.apache.org / asf / webservices / axis2 / java / trunk NOW

[Katherine Sanders]

Hi Josef,

Axis2 has been moved to its own top level project instead of being 
underneath the webservices project.  The code for it has been moved to:  
http://svn.apache.org/repos/asf/axis/axis2/java/core/trunk/.  The other 
projects that depend on axis2 such as sandesha and rampart have also been 
moved under http://svn.apache.org/repos/asf/axis/axis2/java/, and the c 
versions of the projects can be found under 
http://svn.apache.org/repos/asf/axis/axis2/c/.

Thanks,
Katherine



Katherine Sanders
 MP 127, IBM UK Ltd

Software Engineer
 Hursley Park, Winchester, Hampshire SO21 2JN
WebSphere ESB Foundation Technologies
 United Kingdom
IBM Software Group, Application and Integration Middleware Software
 

Phone:
+44 (0) 1962 815758
 

Tie-Line:
245758
 

e-mail:
katherine_sand...@uk.ibm.com
 





From:
Stadelmann Josef josef.stadelm...@axa-winterthur.ch
To:
axis-user@ws.apache.org
Date:
16/02/2010 09:21
Subject:
where is SVN repo http.// svn.apache.org / asf / webservices / axis2 / 
java / trunk NOW



Hi all,
Can someone from the TEAM tell me where all this SVN repos or subdirs 
where moved by ?gmcdonald? on Saturday 13. February 2010-02-16 
this was the root http://svn.apache.org/repos/asf/webservices
I need to update from 
http://svn.apache.org/repos/asf/webservices/axis2/trunk and fail now
I can?t findy anything now for this and other components like rampart, 
sandesha, savan, ?..
Are you breaking our checkout, download, but most important 
svn-update-system?
Would someone from the team then please explain to all members of this 
forum/list where all the stuff has gone.
Moving axis svn, part of TLP move INFRA-2441
Where can I update my 
http://svn/apache/org/asf/webservices/axis2/trunk/java NOW
Josef.Stadelmann
@axa-winterthur.ch







Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU





image/gif

RE: Axis2-1.5.1 and user exceptions

[glopezm]

I've continued doing some research about these issues and I've also found out
that there's another related issue in
http://issues.apache.org/jira/browse/AXIS2-3412. It is now clear for me that
custom exceptions are not working the way it should (at least for those like
me using the code first approach) and that throwing an AxisFault is the
solution/workaround to get the chance to generate the detail part manually
as I shown in my previous message. Even though in order to get the generated
client side code to work or handle the exceptions appropriately I had to do
some subtle changes regarding namespace uri within the stub while parsing
the response... 

Any thoughts/experiences with a similar issues with axis2?


glopezm wrote:
 
 Thanks for your response Michael!!!
 
 That may be useful and I was not aware of that setting however I was
 trying to get axis2 to work pretty much the same way it was doing it in
 previous versions. Let me explain. Axis1 whenever you expose an operation
 as a web service (bottom up) it generates the wsdl:fault within the wsdl
 and also places the information within the detail tag so it could be
 mapped to whatever language you are working with in the other end. Now
 this is not working this way. If you expose the same operation through
 axis2 the exception would be present within the generated wsdl but no
 information regarding the exception is placed within the soap fault's
 detail tag so nobody will be able to deserialize anything. 
 
 The good news is that while I was waiting for someone to come up with an
 idea/clue about this issue I found out a way to create and set the tag by
 declaring those methods/operations throwing AxisFault. 
 
 This is not exactly what I was expecting and it is not my idea of a good
 solution however I can get it to work. 
 
 The code for the operation in case anyone else raise the same issue is the
 following:
 
   public void sayHello(String str) throws AxisFault {
   //First get the message context
   MessageContext messageContext =
 MessageContext.getCurrentMessageContext();
 
   //Create the soap factory
   SOAPFactory soapFactory = null;
   if (messageContext.isSOAP11()) {
   soapFactory = OMAbstractFactory.getSOAP11Factory();
   } else {
   soapFactory = OMAbstractFactory.getSOAP12Factory();
   }
 
   //Create the detail with an error code and message
   SOAPFaultDetail soapFaultDetail = 
 soapFactory.createSOAPFaultDetail();
   QName qName = new QName(http://test;, fault, ns);
   OMElement detail = soapFactory.createOMElement(qName, 
 soapFaultDetail);
   
   qName = new QName(null, code, ns);
   OMElement code = soapFactory.createOMElement(qName, null);
   code.setText(ERR-1234);
   detail.addChild(code);
   
   qName = new QName(null, message, ns);
   OMElement message = soapFactory.createOMElement(qName, null);
   message.setText(A readable message);
   detail.addChild(message);
 
   //Finally create the axis fault and populate it
   AxisFault af = new AxisFault(CustomException: The message);
   af.setDetail(detail);
   af.setFaultCode(new QName(null, Receiver.userException, 
 soapenv));
   
   throw af;
   }
 
 I'd say that all this stuff should be done by axis2 itself whenever a
 service operation throws a (checked) exception and this was the way it was
 working and it is currently working axis1.
 
 Please send me your comments if you have a better solution/idea.
 
 Thanks again for your response!
 
 
 
 Doughty, Michael wrote:
 
 In the axis2.xml file on the server/service side, you should see this
 line:
 
 parameter name=sendStacktraceDetailsWithFaultsfalse/parameter
 
 Set that parameter to true.
 
 Additionally, you might want to change this parameter as well:
 
 parameter name=DrillDownToRootCauseForFaultReasonfalse/parameter
 
 Setting that to true should force more stack trace detail to be sent
 along with it, including the details of the root cause exception.
 
 -Original Message-
 From: glopezm [mailto:gmlopez.mackin...@gmail.com] 
 Sent: Monday, February 15, 2010 8:32 PM
 To: axis-user@ws.apache.org
 Subject: Axis2-1.5.1 and user exceptions
 
 
 Hi, 
 I'm using axis2 v1.5.1 as it is stated in the subject of this message and
 I've found that user exceptions are not being reported as they used to be
 with axis1. If one declare an operation throwing an exception, whenever
 the
 exception is thrown the detail part of the soap fault element used to be
 populated by axis1 with all exception data. However it is not working (at
 least in this way) anymore. The soapenv:Detail / tag is empty. There is
 a
 bug that was filed almost two years ago
 

Re: using faults w/ wsdl2c

[Selvaratnam Uthaiyashankar]

On Sat, Feb 13, 2010 at 12:07 AM, Sam Carleton scarle...@gmail.com wrote:
 Shankar,

 Thank you.  I was wondering:

 It is my understanding that when folks on this mailing list refer to
 axis2, they mean axis2/java not axis2/c.  Is this a correct statement?


Yes, generally when someone mentions Axis2, they mean Axis2/Java. But
in this mailing list, some users use Axis2 to mean Axis2/C. We
normally interpret what is meant by Axis2, by using the context of the
discussion

Regards,
Shankar



 Sam

 On Fri, Feb 12, 2010 at 2:23 AM, Selvaratnam Uthaiyashankar
 uthaiyashan...@gmail.com wrote:
 Hi Sam,

 You can take the checkout from
 https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/

 Regards,
 Shankar

 On Fri, Feb 12, 2010 at 9:30 AM, Sam Carleton scarle...@gmail.com wrote:
 Ok, I am trying to figure out to use faults with Axis2/C.  There was a
 thread back in December that said there is some new features in the latest
 axis2 WSDL2C generator code.  Is my understanding that on this mailing list
 when folks refer to axis2, they mean axis2/java not axis2/c, correct?
 At this time are there binaries for the latest axis2 WSDL2C generator code
 or does one still need to go to the nightly build to get it?
 It looks to me like the nightly build can be found in the following SVN
 repository:
 http://svn.apache.org/viewvc/webservices/axis2/trunk/java/
 When I try to use TortoiseSVN 1.6.1 to check out the code, I get the
 following error:
 Repository moved permanently to '/viewvc/webservices/axis2/trunk/java/';
 please relocate
 Any thoughts on what the problem is?
 Sam
 On Tue, Dec 15, 2009 at 3:32 PM, Dimuthu Gamage dimut...@gmail.com wrote:


 On Sat, Dec 5, 2009 at 5:56 AM, Samisa Abeysinghe sam...@wso2.com wrote:


 On Fri, Dec 4, 2009 at 11:09 PM, Sam Carleton scarle...@gmail.com
 wrote:

 Dimuthu,
 Where EXACTLY does one find the latest WSDL2C code?  Is it in an build
 or is it in the Axis2/Java SVN repository?

 Hi,

 In fact right now we are not maintaining an Axis2 nightly build. So you
 have to do your own build of Axis2/Java to get the latest WSDL2C code.

 Thanks
 Dimuthu


 Axis2 svn.
 Samisa...


 Sam

 On Thu, Dec 3, 2009 at 10:57 PM, Dimuthu Gamage dimut...@gmail.com
 wrote:

 Hi,

 If you use the latest axis2 WSDL2C generator code, you don't need to
 create soap fault message manually as the generated code provide lot of
 support in generating fault message.

 Please have a look at this for the improved API,
 http://www.dimuthu.org/blog/2009/02/09/code-generate-custom-soap-faults-for-axis2c/


 Thanks
 Dimuthu


 On Wed, Nov 18, 2009 at 3:49 AM, Doug Price doug.pr...@presagis.com
 wrote:

 While I see that this approach allows the creation of user-defined
 fault types, is it possible to also use it to specify the standard
 SOAP-ENV:Fault?  I see a struct named axiom_soap_fault_t in the
 distribution, but I can't seem to return it from the
 axis2_svc_skel_*_on_fault() function because it requires a pointer to 
 the
 SOAP body to create one.  Is there some other way to return a standard 
 SOAP
 fault from a service?


 --
 Doug Price
 Research Director | Presagis

 T. +1 972 943.2433  F. +1 469 467.4564  C. +1 469 867.8399

 DISCLAIMER: This e-mail message is for the sole use of the intended
 recipient(s) and may contain confidential and/or proprietary 
 information. Do
 not read, copy, or disseminate this message unless you are the 
 addressee.
 Any unauthorized review, use, disclosure or distribution is strictly
 prohibited. If you have received this message in error, please contact 
 the
 sender by reply e-mail and delete the original and any copies from your
 system.

 -Original Message-

 From: Amir Mousavizadegan [mailto:amir.mousavizade...@cox.net]
 Sent: Tuesday, November 17, 2009 10:29 AM
 To: Apache AXIS C User List
 Subject: Re: using faults w/ wsdl2c

 I did not write the sample codes  nor the document,  however  in order
 to
 get it working, you have to change the body of the generated  code, or
 create a replacement function as I did.
 thx
 Amir
 - Original Message -
 From: Doug Price doug.pr...@presagis.com
 To: Apache AXIS C User List axis-c-user@ws.apache.org
 Sent: Tuesday, November 17, 2009 11:05 AM
 Subject: RE: using faults w/ wsdl2c


 Just what I was looking for.  Thanks so much.

 A quick follow up question on the code though.  Is there a reason that
 axis2_svc_skel_Division_on_fault() doesn't use the adv_divFault api to
 create the fault?


 --
 Doug Price
 Research Director | Presagis

 T. +1 972 943.2433  F. +1 469 467.4564  C. +1 469 867.8399

 DISCLAIMER: This e-mail message is for the sole use of the intended
 recipient(s) and may contain confidential and/or proprietary
 information. Do
 not read, copy, or disseminate this message unless you are the
 addressee.
 Any unauthorized review, use, disclosure or distribution is strictly
 prohibited. If you have received this message in error, please contact
 the
 sender by reply e-mail and delete

RE: Interoperability of Axis2

[Sandeep Khurana]

I tried the reverse way. Generated the java server side classes from the 
generated WSDL (from the POJO deployed webservice) and then deployed the WS 
(using this new generated code). Now I was able to get the custom object as a 
parameter in the web method.

But I am still not getting why the reverse with a POJO did not work?
Has anyone faces this issue before?
-Sandeep

From: Sandeep Khurana [mailto:sandeep_khur...@persistent.co.in]
Sent: Friday, February 12, 2010 11:21 AM
To: axis-user@ws.apache.org
Subject: RE: Interoperability of Axis2

Any pointer on this issue will be helpful...
-Sandeep

From: Sandeep Khurana [mailto:sandeep_khur...@persistent.co.in]
Sent: Thursday, February 11, 2010 6:52 PM
To: axis-user@ws.apache.org
Subject: RE: Interoperability of Axis2

I have checked the request and response messages.
wsdl:message name=getMethodRequest /
wsdl:message name=getMethodResponse
They are present in the WSDL file. Actually I am able to get String Objects but 
not this Custom Objects.
Any pointers will be helpful?

-Sandeep


From: Amila Suriarachchi [mailto:amilasuriarach...@gmail.com]
Sent: Thursday, February 11, 2010 10:34 AM
To: axis-user@ws.apache.org
Subject: Re: Interoperability of Axis2


On Wed, Feb 10, 2010 at 9:31 PM, Sandeep Khurana 
sandeep_khur...@persistent.co.inmailto:sandeep_khur...@persistent.co.in 
wrote:
Hi,
I have created a simple webservice using the POJO class in eclipse. One of the 
web had a custom class as a parameter.
The issue that I faced was when I created the C++ client using gSoap client. 
The Webservice was not able to receive the custom class object and it was null

Is this a known issue or I need to do some more settings?

check the wsdl you get with the deployed service with the request and response 
messages.

thanks,
Amila.

-sandeep

DISCLAIMER == This e-mail may contain privileged and confidential 
information which is the property of Persistent Systems Ltd. It is intended 
only for the use of the individual or entity to which it is addressed. If you 
are not the intended recipient, you are not authorized to read, retain, copy, 
print, distribute or use this message. If you have received this communication 
in error, please notify the sender and delete all copies of this message. 
Persistent Systems Ltd. does not accept any liability for virus infected mails.



--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

DISCLAIMER == This e-mail may contain privileged and confidential 
information which is the property of Persistent Systems Ltd. It is intended 
only for the use of the individual or entity to which it is addressed. If you 
are not the intended recipient, you are not authorized to read, retain, copy, 
print, distribute or use this message. If you have received this communication 
in error, please notify the sender and delete all copies of this message. 
Persistent Systems Ltd. does not accept any liability for virus infected mails.

DISCLAIMER == This e-mail may contain privileged and confidential 
information which is the property of Persistent Systems Ltd. It is intended 
only for the use of the individual or entity to which it is addressed. If you 
are not the intended recipient, you are not authorized to read, retain, copy, 
print, distribute or use this message. If you have received this communication 
in error, please notify the sender and delete all copies of this message. 
Persistent Systems Ltd. does not accept any liability for virus infected mails.

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

RE: Please help on Axis2 Exception handling

[Sandeep Khurana]

Actually, I also faced a similar problem while throwing a RemoteException from 
POJO.
Couldn't get a solution for that. Does anybody have a guide for exception 
handling or the best practices for this?

-Sandeep

From: Li Ma [mailto:lim...@gmail.com]
Sent: Monday, February 15, 2010 7:34 PM
To: axis-user@ws.apache.org
Subject: Please help on Axis2 Exception handling

Dear All,

I ran into a very weird problem with Axis2 exception handling, which puzzled me 
for long time. Any help from you Axis2 expert will be greately appreciated!

This is what I did:

1. Get my service POJO ready. All method throws a customized MyException which 
is derived from java.lang.Exception
2. Use Axis2 java2wsdl to convert this POJO to WSDL,. I can see the wsdl:fault 
part of each service call has been created successfully with name as MyException
3. Then use wsdl2java to generate client side API with ADB binding. Suddenly 
Axis2 creates a bunch of exception related classes, such as:
MyExceptionException
MyExceptionE
xsd/MyException

The methods will throw MyExceptionException, which contains MyExceptionE, which 
contains xsd/MyException. The xsd/MyException has all properties I defined at 
server side. Method also throw AxisFault.

When I run the client code and throw MyException on server, at client side, I 
could only catch AxisFault exception which reason string as return of 
MyException.getMessage() defined on server. I could never catch MyException nor 
MyExceptionException at client side. This is the bigest issue that troubled me. 
If Axis2 has to wrap everything in AxisFault at client side, fine, but whey 
wsdl2java still throws MyExceptionException in generated code and never throw 
it?

Thanks a lot!

Li

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

RE: Please help on Axis2 Exception handling

[Martin Gainty]

the client needs to disable setExceptionToBeThrownOnSOAPFault
ServiceClient.setExceptionToBeThrownOnSOAPFault

now the client is free to handle any exception..

you will need to configure the client method to throw your exception which you 
can do at the phase level
ConfigurationContext ctx=UtilServer.getConfigurationContext();
List phases_list=ctx.getAxisConfiguration().getInFlowPhases();
Phase phaseOne=(Phase) phases_list.get(0); //acquire the first phase
phaseOne.addHandler(new FaultHandler());

Notice that the FaultHandler code has these 3 line which you can tweak to 
override the 
FaultHandler 
invoke(MsgContext msgContext)
.
org.apache.axiom.soap.SOAPFactory fac=msgContext.isSOAP11()? 
OMAbstractFactory.getSOAP11Factory() : OMAbstractFactory().getSOAP12Factory();

org.apache.axiom.soap.SOAPFaultCode 
PlaceNewLocalNameHere=fac.createSOAPFaultCode();
//override the value with whatever you need here assuming the new FaultCode 
overrides SOAPFaultCode 
msgContext.setProperty(SOAP12Constants.SOAP_FAULT_CODE_LOCAL_NAME,PlaceNewLocalNameHere);

org.apache.axiom.soap.SOAPReasonName 
PlaceNewReasonHere=fac.createSOAPFaultReason();
///override the reason with whatever you need here assuming the new ReasonName 
overrides SOAPReasonName
msgContext.setProperty(SOAP12Constants.SOAP_FAULT_REASON_NAME,PlaceNewReasonHere);

org.apache.axiom.soap.SOAPFaultDetail 
PlaceNewDetailHere=fac.createSOAPFaultDetail();
//override the PlaceNewDetailHere with whatever you need here assuming new 
SOAPFaultDetail overrides SOAPFaultDetail
msgContext.setProperty(SOAP12Constants.SOAP_FAULT_DETAIL_LOCAL_NAME,PlaceNewDetailHere);

throw new FaultThatOverridesAxisFault(FaultThatOverridesAxisFaultException has 
occured);

Greetings ,
Martin Gainty
USCitizen(contractor)

Please do not alter or disrupt this transmission. Thank You

Date: Mon, 15 Feb 2010 09:04:08 -0500
Subject: Please help on Axis2 Exception handling
From: lim...@gmail.com
To: axis-user@ws.apache.org

Dear All,
I ran into a very weird problem with Axis2 exception handling, which puzzled me 
for long time. Any help from you Axis2 expert will be greately appreciated!
This is what I did:

1. Get my service POJO ready. All method throws a customized MyException which 
is derived from java.lang.Exception2. Use Axis2 java2wsdl to convert this POJO 
to WSDL,. I can see the wsdl:fault part of each service call has been created 
successfully with name as MyException
3. Then use wsdl2java to generate client side API with ADB binding. Suddenly 
Axis2 creates a bunch of exception related classes, such 
as:MyExceptionExceptionMyExceptionExsd/MyException

The methods will throw MyExceptionException, which contains MyExceptionE, which 
contains xsd/MyException. The xsd/MyException has all properties I defined at 
server side. Method also throw AxisFault.

When I run the client code and throw MyException on server, at client side, I 
could only catch AxisFault exception which reason string as return of 
MyException.getMessage() defined on server. I could never catch MyException nor 
MyExceptionException at client side. This is the bigest issue that troubled me. 
If Axis2 has to wrap everything in AxisFault at client side, fine, but whey 
wsdl2java still throws MyExceptionException in generated code and never throw 
it?

Thanks a lot!
Li
  
_
Hotmail: Trusted email with powerful SPAM protection.
http://clk.atdmt.com/GBL/go/201469227/direct/01/

Re: Receive WSSecurityException (The signature verification failed)

[Nandana Mihindukulasooriya]

Hans,
 Can you post the stacktrace too. Might be helpful to figure out what
exactly is happening.

regards,
Nandana

On Mon, Feb 15, 2010 at 7:17 PM, Hans-Bernhard Friedrich 
h.friedr...@levigo.de wrote:

 Hi,

 I work on a webservice client and I always receive the same error when I
 try to make a request to our clients webservice.

 org.apache.ws.security.WSSecurityException (The signature verification
 failed)

 - Our client's webservice is axis-based, more I don't know

 - I use rampart 1.3 and Axis2 1.4.1, EclipseEE
 - I generated the customers WSDLs with axis2 1.4.1 in EclipseEE
 - I received certificates of our customer and imported them to a keystore
 - I set up the the security using outflow configuration. I know it's
 deprecated but it seemed easier to me than using a policy.xml.
 - I also set up a client using a policy.xml signing the body but reveice
 the same error. I will change to policy in the next step.

 - I read all I could find on the web and in mailinglists but nothing
 helped:
 - XML is UTF-B
 - JVM argument language=EN didn't help
 - Mixing different Axis2 and rampart versions didn't help
 - Changing xmlsec1.4.0. jar to  1.4.1 or 1.4.2 didn't help
 - The certs are have not expired
 - Eclipse' Workspace encoding is UTF-8

 Question:
 - Does the exception really mean the SOAP-Envelope has been changed after
 is was singed? Are there any other reasons this exception could be thrown?

 - What is about the Pretty Printing of the XML issue I've found on the
 mailing list. This this really solved in axis2 1.4.1?
 - Is there a way to set up namespace optimation and pretty printing
 manually in axis2 like in axis 1?
 - Could somethig else be wrong with the certificates?

 The thing is when I use the a modified sample using a policy.xml I get the
 same Exception

 - Is there anything I could tell our client to changed what could help me?

 What did I do special:
 - Wrote a little handler to avoid mustunderstand-Problem in the response:
 I Set all headers in the response to processed. The error also occurs if I
 don't engage my handler

 Here is my Security setup using outflowConfiguration:

 ...options.setProperty(WSSHandlerConstants.*OUTFLOW_SECURITY*,
 getOutflowConfiguration());
 ...
 *private*  Parameter getOutflowConfiguration() {
 *OutflowConfiguration* ofc = *new** OutflowConfiguration()*;
 *ofc.setActionItems(**Timestamp Signature**)*;
 *ofc.setSignatureParts(**{Element}{**
 http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd
 *http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd
 *}Timestamp**)*;
 *ofc.setUser(**fcms-aci**)*;
 *ofc.setPasswordCallbackClass(**de.aci.handler.PWCBHandler**)*;
 *ofc.setSignaturePropRefId(**cyrpto_props**)*;
 *ofc.setSignatureKeyIdentifier(WSSHandlerConstants.**
 X509_KEY_IDENTIFIER**)*;
 *return* *ofc.getProperty()*;
 }



 The *PWCBHandler* is the same as in all Samples. I just changed the alias
 and the password

 I set the properties programmatically, because they should change
 dynamically later:

 Properties prop1 = getProps();
 serviceclient.getOptions.options.setProperty(cyrpto_props, prop1);
 ...
 *private* Properties getProps() {
 Properties prop1 =  *new* Properties();
 prop1.setProperty(org.apache.ws.security.crypto.provider,
 org.apache.ws.security.components.crypto.Merlin);
 prop1.setProperty(
 org.apache.ws.security.crypto.merlin.keystore.type, jks);
 prop1.setProperty(
 org.apache.ws.security.crypto.merlin.keystore.password, L7uZJX1JUZ9l@
 +W2);
 prop1.setProperty(
 org.apache.ws.security.crypto.merlin.file, fcms.keystore);
 *return* prop1;
   }



 Does anybody has an idea what I do wrong?

 Thank you so very much in advance for any ideas

 Greetings
 Hans

RE: Axis2-1.5.1 and user exceptions

[Doughty, Michael]

In the axis2.xml file on the server/service side, you should see this line:

parameter name=sendStacktraceDetailsWithFaultsfalse/parameter

Set that parameter to true.

Additionally, you might want to change this parameter as well:

parameter name=DrillDownToRootCauseForFaultReasonfalse/parameter

Setting that to true should force more stack trace detail to be sent along 
with it, including the details of the root cause exception.

-Original Message-
From: glopezm [mailto:gmlopez.mackin...@gmail.com] 
Sent: Monday, February 15, 2010 8:32 PM
To: axis-user@ws.apache.org
Subject: Axis2-1.5.1 and user exceptions


Hi, 
I'm using axis2 v1.5.1 as it is stated in the subject of this message and
I've found that user exceptions are not being reported as they used to be
with axis1. If one declare an operation throwing an exception, whenever the
exception is thrown the detail part of the soap fault element used to be
populated by axis1 with all exception data. However it is not working (at
least in this way) anymore. The soapenv:Detail / tag is empty. There is a
bug that was filed almost two years ago
(https://issues.apache.org/jira/browse/AXIS2-3443) which explains the
situation very clearly but it has not even been assigned yet!

Now I'm wondering whether someone is aware of a workaround to overcome this
issue since it does not happen that the bug will be corrected anytime soon
:-(.

Thanks in advance for your help!
-- 
View this message in context: 
http://old.nabble.com/Axis2-1.5.1-and-user-exceptions-tp27602949p27602949.html
Sent from the Axis - User mailing list archive at Nabble.com.

RE: Axis2-1.5.1 and user exceptions

[glopezm]

Thanks for your response Michael!!!

That may be useful and I was not aware of that setting however I was trying
to get axis2 to work pretty much the same way it was doing it in previous
versions. Let me explain. Axis1 whenever you expose an operation as a web
service (bottom up) it generates the wsdl:fault within the wsdl and also
places the information within the detail tag so it could be mapped to
whatever language you are working with in the other end. Now this is not
working this way. If you expose the same operation through axis2 the
exception would be present within the generated wsdl but no information
regarding the exception is placed within the soap fault's detail tag so
nobody will be able to deserialize anything. 

The good news is that while I was waiting for someone to come up with an
idea/clue about this issue I found out a way to create and set the tag by
declaring those methods/operations throwing AxisFault. 

This is not exactly what I was expecting and it is not my idea of a good
solution however I can get it to work. 

The code for the operation in case anyone else raise the same issue is the
following:

public void sayHello(String str) throws AxisFault {
//First get the message context
MessageContext messageContext =
MessageContext.getCurrentMessageContext();

//Create the soap factory
SOAPFactory soapFactory = null;
if (messageContext.isSOAP11()) {
soapFactory = OMAbstractFactory.getSOAP11Factory();
} else {
soapFactory = OMAbstractFactory.getSOAP12Factory();
}

//Create the detail with an error code and message
SOAPFaultDetail soapFaultDetail = 
soapFactory.createSOAPFaultDetail();
QName qName = new QName(http://test;, fault, ns);
OMElement detail = soapFactory.createOMElement(qName, 
soapFaultDetail);

qName = new QName(null, code, ns);
OMElement code = soapFactory.createOMElement(qName, null);
code.setText(ERR-1234);
detail.addChild(code);

qName = new QName(null, message, ns);
OMElement message = soapFactory.createOMElement(qName, null);
message.setText(A readable message);
detail.addChild(message);

//Finally create the axis fault and populate it
AxisFault af = new AxisFault(CustomException: The message);
af.setDetail(detail);
af.setFaultCode(new QName(null, Receiver.userException, 
soapenv));

throw af;
}

I'd say that all this stuff should be done by axis2 itself whenever a
service operation throws a (checked) exception and this was the way it was
working and it is currently working axis1.

Please send me your comments if you have a better solution/idea.

Thanks again for your response!



Doughty, Michael wrote:
 
 In the axis2.xml file on the server/service side, you should see this
 line:
 
 parameter name=sendStacktraceDetailsWithFaultsfalse/parameter
 
 Set that parameter to true.
 
 Additionally, you might want to change this parameter as well:
 
 parameter name=DrillDownToRootCauseForFaultReasonfalse/parameter
 
 Setting that to true should force more stack trace detail to be sent
 along with it, including the details of the root cause exception.
 
 -Original Message-
 From: glopezm [mailto:gmlopez.mackin...@gmail.com] 
 Sent: Monday, February 15, 2010 8:32 PM
 To: axis-user@ws.apache.org
 Subject: Axis2-1.5.1 and user exceptions
 
 
 Hi, 
 I'm using axis2 v1.5.1 as it is stated in the subject of this message and
 I've found that user exceptions are not being reported as they used to be
 with axis1. If one declare an operation throwing an exception, whenever
 the
 exception is thrown the detail part of the soap fault element used to be
 populated by axis1 with all exception data. However it is not working (at
 least in this way) anymore. The soapenv:Detail / tag is empty. There is
 a
 bug that was filed almost two years ago
 (https://issues.apache.org/jira/browse/AXIS2-3443) which explains the
 situation very clearly but it has not even been assigned yet!
 
 Now I'm wondering whether someone is aware of a workaround to overcome
 this
 issue since it does not happen that the bug will be corrected anytime soon
 :-(.
 
 Thanks in advance for your help!
 -- 
 View this message in context:
 http://old.nabble.com/Axis2-1.5.1-and-user-exceptions-tp27602949p27602949.html
 Sent from the Axis - User mailing list archive at Nabble.com.
 
 
 

-- 
View this message in context: 
http://old.nabble.com/Axis2-1.5.1-and-user-exceptions-tp27602949p27603868.html
Sent from the Axis - User mailing list archive at Nabble.com.

RE: Initializing Web Service (Server) before first request received

[Oded Onn]

First, thank you Deepal, Michael, Charles and Kouki for your help.
Second, after playing with different options, I ended up with a very
easy solution.

1. The business logic class implements the interface
org.apache.axis2.engine.ServiceLifeCycle

2. Add the class attribute to your service in the services.xml file and
point it to the ServiceLifeCycle implementing class:
service name=myService class=implementingServiceLifeCycleClass

3. Implement the two methods:
public void startUp(ConfigurationContext configctx, AxisService service)

{ static initialization, resource handling... }

public void shutDown(ConfigurationContext configctx, AxisService
service) 
{...}

Both are being called when the service is deployed and stopped,
irrespectively of the service scope, and so static initialization can
easily be called from startUp(). In my case specifically, I do not use
hot-update to the service and so I am not sure if it behaves differently
in that case.

Cheers,
Oded



-Original Message-
From: Charles Galpin [mailto:cgal...@lhsw.com] 
Sent: Wednesday, February 10, 2010 14:23
To: axis-user@ws.apache.org
Subject: Re: Initializing Web Service (Server) before first request
received

I'm not sure I ever fully understood this, even after reading the docs
on the service lifecycle a few times. What I found was that the methods
did not fire the same way during hot deployment as they do on startup so
don't get fooled by that. The best I came up with was use application
scope, restart tomcat whenever I needed to apply a change, and the init
method was the best place to put any one time setup code.

hth
charles

On Feb 10, 2010, at 5:23 AM, Doughty, Michael wrote:

 In your services.xml file, add 'scope= application' to the service
element, as follows:
 
 service name=***your service name*** scope= application
 
 The service will then be deployable in application mode.
 
 Now a question to Deepal... will this actually load the implementation
class immediately on deployment and thus cause all static initialization
in the class to take place?
 
 I know that application mode will cause Axis2 to treat the
implementation class as a singleton and reuse the same instance for each
service call, but I was still under the impression that it would require
that first service call to be made still.  If the class is loaded on
deployment or the singleton is constructed prior to the first service
call, then that is definitely good news.
 
 -Original Message-
 From: Oded Onn [mailto:oded@mobixell.com] 
 Sent: Wednesday, February 10, 2010 3:21 AM
 To: axis-user@ws.apache.org
 Subject: RE: Initializing Web Service (Server) before first request
received
 
 Deepal,
 Can you please elaborate a bit more. I am not sure I quite understand
 what you mean.
 Thanks,
 Oded
 
 -Original Message-
 From: Deepal Jayasinghe [mailto:dee...@opensource.lk] 
 Sent: Wednesday, February 10, 2010 00:58
 To: axis-user@ws.apache.org
 Subject: Re: Initializing Web Service (Server) before first request
 received
 
 Deploy there service in Application scope.
 
 Thanks,
 Deepal
 
 Hi all,
 
 
 
 I am deploying an AXIS2 web service (server side).
 
 
 
 My problem: The skeleton class (the one that performs all the
business
 logic) is read for the first time only when the first request is
 received by the server. It means that the first response takes a
 really long time (up to 20 seconds on a weak machine) since there are
 a lot of initialization I have to perform (static init).
 
 
 
 Solution: I am assuming I can write some sort of a main class that
 will try to call the skeleton class. This is not only ugly but also
 prone to all sorts of errors. Is there a proper way to init my
service
 class? I would expect some mechanism to be used, such as utilizing
the
 servlet init of the axis servlet.
 
 
 
 Anyone? Thanks!
 
 Oded
 
 
 -- 
 Thank you!
 
 
 http://blogs.deepal.org
 http://deepal.org
 

RE: Strange issue with Axis2 setting improper default namespaces in responses

[Doughty, Michael]

So I tested an existing client written using Axis2 1.4.1 and Rampart 1.4 
against the Web service today written using Axis2 1.5.1 and Rampart 1.5.  With 
encryption and signature turned off things went fine, but when encryption and 
signature were turned on, the client sent a proper request that was understood 
by the server, but the response sent by the server caused the client to error 
out with Expecting one of {classList}.

This is almost certainly due to the fact that classList is supposed to have 
the empty default Namespace, but Axis2 1.5.1 and Rampart 1.5 are changing that 
namespace to the parent namespace of 
http://atrium.bmc.com/2009/01/classes/types; on encrypting and signing the 
body.

I am relatively sure this isn't correct behavior, but I am unable to get the 
Axis2 1.5.1/Rampart 1.5 combo to work differently.  Is this a known issue with 
Rampart?  Has anyone run into this before?  Is there any way to work around the 
issue and make the responses preserve the proper default namespaces?

From: Doughty, Michael [mailto:michael_doug...@bmc.com]
Sent: Sunday, February 14, 2010 12:57 AM
To: axis-user@ws.apache.org
Subject: Strange issue with Axis2 setting improper default namespaces in 
responses

We've been porting our Web services from another provider to Axis2.  Both 
support XML bean bindings, and we used them in our original implementation, so 
that has made the porting easier than it would have been otherwise.

However, I've run into an odd issue that I haven't caught up to now using the 
testing tool we use during dev.  The old tool is properly setting the default 
namespace to child elements to empty, which allows the responses to be properly 
handled by the clients.  However, the Axis2 services seem to be setting the 
default namespace in each case to the parent namespace.  This causes validation 
of the responses against the WSDL and the schemas to be incorrect.

So then I decided to see what happens in the Axis2-based responses when I turn 
security off and just accept a UsernameToken without encryption or signature.  
Turns out the response is just fine when I do that, as this snippet shows:

  ListClassesOutput
xmlns=http://atrium.bmc.com/2009/01/classes/types;
   classList
xmlns=
list
 namespaceNameBMC.CORE/namespaceName
 classNameBMC_Mainframe/className
/list
list
 namespaceNameBMC.CORE/namespaceName
 classNameBMC_Printer/className
/list
   /classList
   status
xmlns=/
   extensions xmlns=
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:nil=true/
  /ListClassesOutput

However, the minute I turn the Signature and Encryption components on in the 
Rampart configuration, I get the bad behavior again, as shown here:

ListClassesOutput xmlns=http://atrium.bmc.com/2009/01/classes/types; 
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; 
xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
 xmlns:xenc=http://www.w3.org/2001/04/xmlenc#;
  classList xmlns=http://atrium.bmc.com/2009/01/classes/types; 
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; 
xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
 xmlns:xenc=http://www.w3.org/2001/04/xmlenc#;
list xmlns=http://atrium.bmc.com/2009/01/classes/types; 
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; 
xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
 xmlns:xenc=http://www.w3.org/2001/04/xmlenc#;
 namespaceName xmlns=http://atrium.bmc.com/2009/01/classes/types; 
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; 
xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
 xmlns:xenc=http://www.w3.org/2001/04/xmlenc#;BMC.CORE/namespaceName'
 className xmlns=http://atrium.bmc.com/2009/01/classes/types; 
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; 
xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
 xmlns:xenc=http://www.w3.org/2001/04/xmlenc#;BMC_Mainframe/className
   /list
   list xmlns=http://atrium.bmc.com/2009/01/classes/types; 
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; 
xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
 xmlns:xenc=http://www.w3.org/2001/04/xmlenc#;
 namespaceName xmlns=http://atrium.bmc.com/2009/01/classes/types; 
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; 
xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
 xmlns:xenc=http://www.w3.org/2001/04/xmlenc#;BMC.CORE/namespaceName
 className xmlns=http://atrium.bmc.com/2009/01/classes/types; 
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; 
xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
 xmlns:xenc=http://www.w3.org/2001/04/xmlenc#;BMC_Printer/className
/list
  /classList
  status 

Re: Parameter ordering in SOAP Requests

[Amila Suriarachchi]

On Thu, Feb 11, 2010 at 9:02 PM, Larry Gilliam lgill...@innovim.com wrote:

 Hello,

  Is there any way to enable users to pass SOAP and/or REST parameters in
 any order? I can't quite understand why the order (as per the WSDL) is
 necessary since the input is name/value pairs.

  If there is a way to accept input in any order, please advise how. If not,
 a brief explanation why would be great.

 Thanks for any info you can provide.


The bottom line is you need to send your request message according to the
way it is specified in the wsdl schema. If the schema specified it as a
sequence (which is most of the case) parameters has to send in an order.

Actually there is no concept of parameter order here. Only thing is the
request message must match in the way it is described in wsdl file.

this[1] may help you as well.

thanks,
Amila.

[1] http://wso2.org/library/2873


 -Larry




-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Re: How java.lang.Object is handled in Axis2 1.4.1?

[Chinmoy Chakraborty]

Hello All,

I am using using Axis2 1.4.1. I found if I have argument of a service of
type *java.lang.Object*, Axis2 internally converts it into *
javax.activation.DataHandler*. So Axis2 does support java.lang.Object as
argument of a service method?

Could any one please give me pointer on this?

Chinmoy

RE: xsi:type

[Rahul Rulz]

Hi Martin,
I have been trying to get this working for months but was not successful . I 
would like to know if it can be done..Please reply.
Thanks,Raghav. 

--- On Fri, 2/12/10, Rahul Rulz ragul...@yahoo.com wrote:

From: Rahul Rulz ragul...@yahoo.com
Subject: RE: xsi:type
To: axis-user@ws.apache.org
Date: Friday, February 12, 2010, 8:43 AM

Hi Martin,
Thanks for your reply.. basically I want to include the XSi:type in the 
responses made from my server..
This is the response I am getting from my server presently : 
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; 
xmlns:xsd=http://www.w3.org/2001/XMLSchema; 
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;   /soapenv:Header   
soapenv:Body      ns4:PBSNR xmlns:ns4=bp:ProfileManagementService         
PBSNRT            SNs               SLSLINKED/SLS  
             SN12Ea345/SN               SNStatusACTIVE/SNStatus         
      STMDN/ST            /SNs            SNs               
SLSINITIAL/SLS               SN12Ea345/SN               
SNStatusACTIVE/SNStatus               STMDN/ST            /SNs        
    user      
         ns7:userSegment xmlns:ns7=http://user.prof.services.bp.com/        
       usernameem...@bp.com/username            /user         /PBSNRT   
   /ns4:PBSNR   /soapenv:Body/soapenv:Envelope
But I want to include the types in the message and it would look as
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; 
xmlns:xsd=http://www.w3.org/2001/XMLSchema; 
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;   /soapenv:Header   
soapenv:Body      ns4:PBSNR
 xmlns:ns4=bp:ProfileManagementService         PBSNRT            SNs     
          SLSLINKED/SLS               SN 
xsi:type=ns1:ServiceTypeEnum12/SN               SNStatus 
xsi:type=xsd:stringACTIVE/SNStatus               ST 
xsi:type=xsd:stringMDN/ST            /SNs            SNs               
SLSINITIAL/SLS               SN
 xsi:type=ns1:ServiceTypeEnum12/SN               
SNStatusACTIVE/SNStatus               ST xsi:type=xsd:stringMDN/ST    
        /SNs            user               ns7:userSegment 
xmlns:ns7=http://user.prof.services.bp.com/               
usernameem...@bp.com/username            /user         /PBSNRT      
/ns4:PBSNR   /soapenv:Body/soapenv:Envelope
Please note that I have
 developed the service from the scratch without the WSDL.. 
It would be great if you can guide me.
Many Thanks,Raghav.

--- On Fri, 2/12/10, Martin Gainty mgai...@hotmail.com wrote:

From: Martin Gainty mgai...@hotmail.com
Subject: RE: xsi:type
To: axis-user@ws.apache.org
Date: Friday, February 12, 2010, 7:39 AM





 
we would need to see the schema instance namespace declaration such as
schema xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance...

Martin Gainty 
__ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie
 de ceci est interdite. Ce message sert à l'information seulement et n'aura pas 
n'importe quel effet légalement obligatoire. Étant donné que les email peuvent 
facilement être sujets à la manipulation, nous ne pouvons accepter aucune 
responsabilité pour le contenu fourni.




Date: Thu, 11 Feb 2010 16:38:58 -0800
From: ragul...@yahoo.com
Subject: Re: xsi:type
To: axis-user@ws.apache.org

Hi Users,
can anyone help me out please...
Thanks,Raghav.

 

--- On Thu, 2/11/10, Rahul Rulz
 ragul...@yahoo.com wrote:

From: Rahul Rulz ragul...@yahoo.com
Subject: xsi:type
To: axis-user@ws.apache.org
Date: Thursday, February 11, 2010, 11:03 AM

Hi All,
I am looking to include xsi:type in the responses from my server for a ling 
time :( .. Have not done it till now..Could anyone pl. help me as to do it..I 
have created a service from
 scratch(not from WSDL generated java code) which uses message receivers and 
send the responses. I am using axis2 1.5.1
Thanks for your help.
Regards,Raghav.

 


  
  
Hotmail: Trusted email with powerful SPAM protection. Sign up now. 





  


  

Re: using faults w/ wsdl2c

[Sam Carleton]

Shankar,

Thank you.  I was wondering:

It is my understanding that when folks on this mailing list refer to
axis2, they mean axis2/java not axis2/c.  Is this a correct statement?

Sam

On Fri, Feb 12, 2010 at 2:23 AM, Selvaratnam Uthaiyashankar
uthaiyashan...@gmail.com wrote:
 Hi Sam,

 You can take the checkout from
 https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/

 Regards,
 Shankar

 On Fri, Feb 12, 2010 at 9:30 AM, Sam Carleton scarle...@gmail.com wrote:
 Ok, I am trying to figure out to use faults with Axis2/C.  There was a
 thread back in December that said there is some new features in the latest
 axis2 WSDL2C generator code.  Is my understanding that on this mailing list
 when folks refer to axis2, they mean axis2/java not axis2/c, correct?
 At this time are there binaries for the latest axis2 WSDL2C generator code
 or does one still need to go to the nightly build to get it?
 It looks to me like the nightly build can be found in the following SVN
 repository:
 http://svn.apache.org/viewvc/webservices/axis2/trunk/java/
 When I try to use TortoiseSVN 1.6.1 to check out the code, I get the
 following error:
 Repository moved permanently to '/viewvc/webservices/axis2/trunk/java/';
 please relocate
 Any thoughts on what the problem is?
 Sam
 On Tue, Dec 15, 2009 at 3:32 PM, Dimuthu Gamage dimut...@gmail.com wrote:


 On Sat, Dec 5, 2009 at 5:56 AM, Samisa Abeysinghe sam...@wso2.com wrote:


 On Fri, Dec 4, 2009 at 11:09 PM, Sam Carleton scarle...@gmail.com
 wrote:

 Dimuthu,
 Where EXACTLY does one find the latest WSDL2C code?  Is it in an build
 or is it in the Axis2/Java SVN repository?

 Hi,

 In fact right now we are not maintaining an Axis2 nightly build. So you
 have to do your own build of Axis2/Java to get the latest WSDL2C code.

 Thanks
 Dimuthu


 Axis2 svn.
 Samisa...


 Sam

 On Thu, Dec 3, 2009 at 10:57 PM, Dimuthu Gamage dimut...@gmail.com
 wrote:

 Hi,

 If you use the latest axis2 WSDL2C generator code, you don't need to
 create soap fault message manually as the generated code provide lot of
 support in generating fault message.

 Please have a look at this for the improved API,
 http://www.dimuthu.org/blog/2009/02/09/code-generate-custom-soap-faults-for-axis2c/


 Thanks
 Dimuthu


 On Wed, Nov 18, 2009 at 3:49 AM, Doug Price doug.pr...@presagis.com
 wrote:

 While I see that this approach allows the creation of user-defined
 fault types, is it possible to also use it to specify the standard
 SOAP-ENV:Fault?  I see a struct named axiom_soap_fault_t in the
 distribution, but I can't seem to return it from the
 axis2_svc_skel_*_on_fault() function because it requires a pointer to 
 the
 SOAP body to create one.  Is there some other way to return a standard 
 SOAP
 fault from a service?


 --
 Doug Price
 Research Director | Presagis

 T. +1 972 943.2433  F. +1 469 467.4564  C. +1 469 867.8399

 DISCLAIMER: This e-mail message is for the sole use of the intended
 recipient(s) and may contain confidential and/or proprietary 
 information. Do
 not read, copy, or disseminate this message unless you are the 
 addressee.
 Any unauthorized review, use, disclosure or distribution is strictly
 prohibited. If you have received this message in error, please contact 
 the
 sender by reply e-mail and delete the original and any copies from your
 system.

 -Original Message-

 From: Amir Mousavizadegan [mailto:amir.mousavizade...@cox.net]
 Sent: Tuesday, November 17, 2009 10:29 AM
 To: Apache AXIS C User List
 Subject: Re: using faults w/ wsdl2c

 I did not write the sample codes  nor the document,  however  in order
 to
 get it working, you have to change the body of the generated  code, or
 create a replacement function as I did.
 thx
 Amir
 - Original Message -
 From: Doug Price doug.pr...@presagis.com
 To: Apache AXIS C User List axis-c-user@ws.apache.org
 Sent: Tuesday, November 17, 2009 11:05 AM
 Subject: RE: using faults w/ wsdl2c


 Just what I was looking for.  Thanks so much.

 A quick follow up question on the code though.  Is there a reason that
 axis2_svc_skel_Division_on_fault() doesn't use the adv_divFault api to
 create the fault?


 --
 Doug Price
 Research Director | Presagis

 T. +1 972 943.2433  F. +1 469 467.4564  C. +1 469 867.8399

 DISCLAIMER: This e-mail message is for the sole use of the intended
 recipient(s) and may contain confidential and/or proprietary
 information. Do
 not read, copy, or disseminate this message unless you are the
 addressee.
 Any unauthorized review, use, disclosure or distribution is strictly
 prohibited. If you have received this message in error, please contact
 the
 sender by reply e-mail and delete the original and any copies from
 your
 system.

 -Original Message-

 From: Amir Mousavizadegan [mailto:amir.mousavizade...@cox.net]
 Sent: Tuesday, November 17, 2009 7:52 AM
 To: Apache AXIS C User List
 Subject: Re: using faults w/ wsdl2c

 Please see attached document
 - Original Message -
 From

RE : Need suggestions on Axis/c client stub

[Olivier Mengué]

De: Nadir Amra
Axis-C++ client-side is not broken or buggy.  It is perfectly functional 
and in some cases much easier to use than axis2/C.
 
So why Axis2/C was created? I'm insterested in the history of the project.
Is it because C support is not complete. in Axis C++ ?
(according to http://ws.apache.org/axis/cpp/index.html#Known_issues )

Olivier.

RE : Need suggestions on Axis/c client stub

[Nadir Amra]

Actually, C support is as complete as the C++ support.  But only on client 
side, and only for doc/literal.


From an old post when I asked the question long ago:

AxisC++ is a very good, solid, 2nd generation Web Services stack written 
in C++. It supports being a client to UDDI, and certainly it would be 
possible to support WS-Sec under it. However standards like RM and 
WS-Addressing are hard to support. 

If you look at the iterations of development, the first iteration (e.g. 
ApacheSOAP) was just about getting the job done simply. The next iteration 
added better parsing and more flexible handler models, which successfully 
supports WSSecurity and simple extensions to SOAP. 

However, the big change has been WS-Addressing, which has made WS much 
more asynchronous and message based. Unfortunately a lot of WS stacks 
including Axis/Java 1.x and Axis/C++ 1.x were built with a very RPC-like 
model. 

Axis2 C is the start of the move of Axis in C/C++ to the Axis2 model. When 
we wrote Axis2/Java we started again. In building Axis2/C we also started 
again. 
===

So basically Axis2/C and Axis2/Java were created to support more of the 
standards and improve on what was learned in prior implementations.

Nadir Amra


Olivier Mengué omen...@oxymel.com wrote on 02/11/2010 03:57:55 AM:

 [image removed] 
 
 RE : Need suggestions on Axis/c client stub
 
 Olivier Mengué 
 
 to:
 
 Apache AXIS C User List, Apache AXIS C User List
 
 02/11/2010 04:02 AM
 
 Cc:
 
 Apache AXIS C User List
 
 Please respond to Apache AXIS C User List
 
 
 

 De: Nadir Amra
 Axis-C++ client-side is not broken or buggy.  It is perfectly 
functional
 and in some cases much easier to use than axis2/C.
 
 So why Axis2/C was created? I'm insterested in the history of the 
project.
 Is it because C support is not complete. in Axis C++ ?
 (according to http://ws.apache.org/axis/cpp/index.html#Known_issues )
 
 Olivier. 

Re: using faults w/ wsdl2c

[Sam Carleton]

Ok, I am trying to figure out to use faults with Axis2/C.  There was a
thread back in December that said there is some new features in the latest
axis2 WSDL2C generator code.  Is my understanding that on this mailing list
when folks refer to axis2, they mean axis2/java not axis2/c, correct?

At this time are there binaries for the latest axis2 WSDL2C generator code
or does one still need to go to the nightly build to get it?

It looks to me like the nightly build can be found in the following SVN
repository:

http://svn.apache.org/viewvc/webservices/axis2/trunk/java/

When I try to use TortoiseSVN 1.6.1 to check out the code, I get the
following error:

Repository moved permanently to '/viewvc/webservices/axis2/trunk/java/';
please relocate

Any thoughts on what the problem is?

Sam

On Tue, Dec 15, 2009 at 3:32 PM, Dimuthu Gamage dimut...@gmail.com wrote:



 On Sat, Dec 5, 2009 at 5:56 AM, Samisa Abeysinghe sam...@wso2.com wrote:



 On Fri, Dec 4, 2009 at 11:09 PM, Sam Carleton scarle...@gmail.comwrote:

 Dimuthu,

 Where EXACTLY does one find the latest WSDL2C code?  Is it in an build or
 is it in the Axis2/Java SVN repository?


 Hi,

 In fact right now we are not maintaining an Axis2 nightly build. So you
 have to do your own build of Axis2/Java to get the latest WSDL2C code.

 Thanks
 Dimuthu


 Axis2 svn.

 Samisa...



 Sam


  On Thu, Dec 3, 2009 at 10:57 PM, Dimuthu Gamage dimut...@gmail.comwrote:

 Hi,

 If you use the latest axis2 WSDL2C generator code, you don't need to
 create soap fault message manually as the generated code provide lot of
 support in generating fault message.

 Please have a look at this for the improved API,
 http://www.dimuthu.org/blog/2009/02/09/code-generate-custom-soap-faults-for-axis2c/


 Thanks
 Dimuthu



 On Wed, Nov 18, 2009 at 3:49 AM, Doug Price doug.pr...@presagis.comwrote:

 While I see that this approach allows the creation of user-defined
 fault types, is it possible to also use it to specify the standard
 SOAP-ENV:Fault?  I see a struct named axiom_soap_fault_t in the
 distribution, but I can't seem to return it from the
 axis2_svc_skel_*_on_fault() function because it requires a pointer to the
 SOAP body to create one.  Is there some other way to return a standard 
 SOAP
 fault from a service?


 --
 Doug Price
 Research Director | Presagis

 T. +1 972 943.2433  F. +1 469 467.4564  C. +1 469 867.8399

 DISCLAIMER: This e-mail message is for the sole use of the intended
 recipient(s) and may contain confidential and/or proprietary information. 
 Do
 not read, copy, or disseminate this message unless you are the addressee.
 Any unauthorized review, use, disclosure or distribution is strictly
 prohibited. If you have received this message in error, please contact the
 sender by reply e-mail and delete the original and any copies from your
 system.

 -Original Message-

 From: Amir Mousavizadegan [mailto:amir.mousavizade...@cox.net]
 Sent: Tuesday, November 17, 2009 10:29 AM
 To: Apache AXIS C User List
 Subject: Re: using faults w/ wsdl2c

 I did not write the sample codes  nor the document,  however  in order
 to
 get it working, you have to change the body of the generated  code, or
 create a replacement function as I did.
 thx
 Amir
 - Original Message -
 From: Doug Price doug.pr...@presagis.com
 To: Apache AXIS C User List axis-c-user@ws.apache.org
 Sent: Tuesday, November 17, 2009 11:05 AM
 Subject: RE: using faults w/ wsdl2c


 Just what I was looking for.  Thanks so much.

 A quick follow up question on the code though.  Is there a reason that
 axis2_svc_skel_Division_on_fault() doesn't use the adv_divFault api to
 create the fault?


 --
 Doug Price
 Research Director | Presagis

 T. +1 972 943.2433  F. +1 469 467.4564  C. +1 469 867.8399

 DISCLAIMER: This e-mail message is for the sole use of the intended
 recipient(s) and may contain confidential and/or proprietary
 information. Do
 not read, copy, or disseminate this message unless you are the
 addressee.
 Any unauthorized review, use, disclosure or distribution is strictly
 prohibited. If you have received this message in error, please contact
 the
 sender by reply e-mail and delete the original and any copies from your
 system.

 -Original Message-

 From: Amir Mousavizadegan [mailto:amir.mousavizade...@cox.net]
 Sent: Tuesday, November 17, 2009 7:52 AM
 To: Apache AXIS C User List
 Subject: Re: using faults w/ wsdl2c

 Please see attached document
 - Original Message -
 From: Doug Price doug.pr...@presagis.com
 To: axis-c-user@ws.apache.org
 Sent: Monday, November 16, 2009 4:47 PM
 Subject: using faults w/ wsdl2c


 I created a simple web service w/ Axis2c using wsdl2c on a WSDL file I
 created in Eclipse.  The default functionality of this works fine.
  However,
 now I'd like to incorporate faults into my SOAP messages.  I created a
 fault
 type in my WSDL and wsdl2c creates the wrappers for the fault message,
 but
 the service skeleton and client stubs files

Re: using faults w/ wsdl2c

[Selvaratnam Uthaiyashankar]

Hi Sam,

You can take the checkout from
https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/

Regards,
Shankar

On Fri, Feb 12, 2010 at 9:30 AM, Sam Carleton scarle...@gmail.com wrote:
 Ok, I am trying to figure out to use faults with Axis2/C.  There was a
 thread back in December that said there is some new features in the latest
 axis2 WSDL2C generator code.  Is my understanding that on this mailing list
 when folks refer to axis2, they mean axis2/java not axis2/c, correct?
 At this time are there binaries for the latest axis2 WSDL2C generator code
 or does one still need to go to the nightly build to get it?
 It looks to me like the nightly build can be found in the following SVN
 repository:
 http://svn.apache.org/viewvc/webservices/axis2/trunk/java/
 When I try to use TortoiseSVN 1.6.1 to check out the code, I get the
 following error:
 Repository moved permanently to '/viewvc/webservices/axis2/trunk/java/';
 please relocate
 Any thoughts on what the problem is?
 Sam
 On Tue, Dec 15, 2009 at 3:32 PM, Dimuthu Gamage dimut...@gmail.com wrote:


 On Sat, Dec 5, 2009 at 5:56 AM, Samisa Abeysinghe sam...@wso2.com wrote:


 On Fri, Dec 4, 2009 at 11:09 PM, Sam Carleton scarle...@gmail.com
 wrote:

 Dimuthu,
 Where EXACTLY does one find the latest WSDL2C code?  Is it in an build
 or is it in the Axis2/Java SVN repository?

 Hi,

 In fact right now we are not maintaining an Axis2 nightly build. So you
 have to do your own build of Axis2/Java to get the latest WSDL2C code.

 Thanks
 Dimuthu


 Axis2 svn.
 Samisa...


 Sam

 On Thu, Dec 3, 2009 at 10:57 PM, Dimuthu Gamage dimut...@gmail.com
 wrote:

 Hi,

 If you use the latest axis2 WSDL2C generator code, you don't need to
 create soap fault message manually as the generated code provide lot of
 support in generating fault message.

 Please have a look at this for the improved API,
 http://www.dimuthu.org/blog/2009/02/09/code-generate-custom-soap-faults-for-axis2c/


 Thanks
 Dimuthu


 On Wed, Nov 18, 2009 at 3:49 AM, Doug Price doug.pr...@presagis.com
 wrote:

 While I see that this approach allows the creation of user-defined
 fault types, is it possible to also use it to specify the standard
 SOAP-ENV:Fault?  I see a struct named axiom_soap_fault_t in the
 distribution, but I can't seem to return it from the
 axis2_svc_skel_*_on_fault() function because it requires a pointer to the
 SOAP body to create one.  Is there some other way to return a standard 
 SOAP
 fault from a service?


 --
 Doug Price
 Research Director | Presagis

 T. +1 972 943.2433  F. +1 469 467.4564  C. +1 469 867.8399

 DISCLAIMER: This e-mail message is for the sole use of the intended
 recipient(s) and may contain confidential and/or proprietary 
 information. Do
 not read, copy, or disseminate this message unless you are the addressee.
 Any unauthorized review, use, disclosure or distribution is strictly
 prohibited. If you have received this message in error, please contact 
 the
 sender by reply e-mail and delete the original and any copies from your
 system.

 -Original Message-

 From: Amir Mousavizadegan [mailto:amir.mousavizade...@cox.net]
 Sent: Tuesday, November 17, 2009 10:29 AM
 To: Apache AXIS C User List
 Subject: Re: using faults w/ wsdl2c

 I did not write the sample codes  nor the document,  however  in order
 to
 get it working, you have to change the body of the generated  code, or
 create a replacement function as I did.
 thx
 Amir
 - Original Message -
 From: Doug Price doug.pr...@presagis.com
 To: Apache AXIS C User List axis-c-user@ws.apache.org
 Sent: Tuesday, November 17, 2009 11:05 AM
 Subject: RE: using faults w/ wsdl2c


 Just what I was looking for.  Thanks so much.

 A quick follow up question on the code though.  Is there a reason that
 axis2_svc_skel_Division_on_fault() doesn't use the adv_divFault api to
 create the fault?


 --
 Doug Price
 Research Director | Presagis

 T. +1 972 943.2433  F. +1 469 467.4564  C. +1 469 867.8399

 DISCLAIMER: This e-mail message is for the sole use of the intended
 recipient(s) and may contain confidential and/or proprietary
 information. Do
 not read, copy, or disseminate this message unless you are the
 addressee.
 Any unauthorized review, use, disclosure or distribution is strictly
 prohibited. If you have received this message in error, please contact
 the
 sender by reply e-mail and delete the original and any copies from
 your
 system.

 -Original Message-

 From: Amir Mousavizadegan [mailto:amir.mousavizade...@cox.net]
 Sent: Tuesday, November 17, 2009 7:52 AM
 To: Apache AXIS C User List
 Subject: Re: using faults w/ wsdl2c

 Please see attached document
 - Original Message -
 From: Doug Price doug.pr...@presagis.com
 To: axis-c-user@ws.apache.org
 Sent: Monday, November 16, 2009 4:47 PM
 Subject: using faults w/ wsdl2c


 I created a simple web service w/ Axis2c using wsdl2c on a WSDL file I
 created in Eclipse.  The default functionality of this works fine

RE: Interoperability of Axis2

[Sandeep Khurana]

I have checked the request and response messages.
wsdl:message name=getMethodRequest /
wsdl:message name=getMethodResponse
They are present in the WSDL file. Actually I am able to get String Objects but 
not this Custom Objects.
Any pointers will be helpful?

-Sandeep


From: Amila Suriarachchi [mailto:amilasuriarach...@gmail.com]
Sent: Thursday, February 11, 2010 10:34 AM
To: axis-user@ws.apache.org
Subject: Re: Interoperability of Axis2


On Wed, Feb 10, 2010 at 9:31 PM, Sandeep Khurana 
sandeep_khur...@persistent.co.inmailto:sandeep_khur...@persistent.co.in 
wrote:
Hi,
I have created a simple webservice using the POJO class in eclipse. One of the 
web had a custom class as a parameter.
The issue that I faced was when I created the C++ client using gSoap client. 
The Webservice was not able to receive the custom class object and it was null

Is this a known issue or I need to do some more settings?

check the wsdl you get with the deployed service with the request and response 
messages.

thanks,
Amila.

-sandeep

DISCLAIMER == This e-mail may contain privileged and confidential 
information which is the property of Persistent Systems Ltd. It is intended 
only for the use of the individual or entity to which it is addressed. If you 
are not the intended recipient, you are not authorized to read, retain, copy, 
print, distribute or use this message. If you have received this communication 
in error, please notify the sender and delete all copies of this message. 
Persistent Systems Ltd. does not accept any liability for virus infected mails.



--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

Re: xsi:type

[Rahul Rulz]

Hi Users,
can anyone help me out please...
Thanks,Raghav.

 

--- On Thu, 2/11/10, Rahul Rulz ragul...@yahoo.com wrote:

From: Rahul Rulz ragul...@yahoo.com
Subject: xsi:type
To: axis-user@ws.apache.org
Date: Thursday, February 11, 2010, 11:03 AM

Hi All,
I am looking to include xsi:type in the responses from my server for a ling 
time :( .. Have not done it till now..Could anyone pl. help me as to do it..I 
have created a service from scratch(not from WSDL generated java code) which 
uses message receivers and send the responses. I am using axis2 1.5.1
Thanks for your help.
Regards,Raghav.

 


  


  

RE: xsi:type

[Martin Gainty]

we would need to see the schema instance namespace declaration such as
schema xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance...

Martin Gainty 
__ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est 
interdite. Ce message sert à l'information seulement et n'aura pas n'importe 
quel effet légalement obligatoire. Étant donné que les email peuvent facilement 
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité 
pour le contenu fourni.




Date: Thu, 11 Feb 2010 16:38:58 -0800
From: ragul...@yahoo.com
Subject: Re: xsi:type
To: axis-user@ws.apache.org

Hi Users,
can anyone help me out please...
Thanks,Raghav.

 

--- On Thu, 2/11/10, Rahul Rulz ragul...@yahoo.com wrote:

From: Rahul Rulz ragul...@yahoo.com
Subject: xsi:type
To: axis-user@ws.apache.org
Date: Thursday, February 11, 2010, 11:03 AM

Hi All,
I am looking to include xsi:type in the responses from my server for a ling 
time :( .. Have not done it till now..Could anyone pl. help me as to do it..I 
have created a service from
 scratch(not from WSDL generated java code) which uses message receivers and 
send the responses. I am using axis2 1.5.1
Thanks for your help.
Regards,Raghav.

 


  
  
_
Hotmail: Trusted email with powerful SPAM protection.
http://clk.atdmt.com/GBL/go/201469227/direct/01/

RE: com.ctc.wstx.exc.WstxEOFException

[Colin Sharples [DATACOM]]

No, I'm pretty sure this is a problem in the generated client. When I
used tcpmon, I couldn't get the error at all. I don't get the error when
calling the web service from SoapUI, nor from the Eclipse Web Services
Test explorer.

 

I wrote a standalone Java program using the generated client stub to
call the web service 10 times. It fails every second call, i.e. 5 out of
the 10 calls fail, every time I run the program.

 

I'm pretty sure I didn't specify broken=true when I generated the
client:

 

taskdef name=wsdl2java
classname=org.apache.axis2.tool.ant.AntCodegenTask

classpath

fileset dir=${axis2-lib} includes=*.jar/

/classpath

/taskdef

target name=gen-wsdl-client-sch

wsdl2java wsdlfilename=ScheduleService.wsdl
packagename=nz.co.datacom.foo databindingname=jibx synconly=true
serverside=false generateservicexml=false unwrap=false
targetsourcefolderlocation=../Client/src overwrite=true

parameter name=bindingfile value=binding.xml/

/wsdl2java

/target

 

I'm just using the client stub generated by wsdl2java unchanged.

 

From: Amila Suriarachchi [mailto:amilasuriarach...@gmail.com] 
Sent: Thursday, 11 February 2010 6:11 p.m.
To: axis-user@ws.apache.org
Subject: Re: com.ctc.wstx.exc.WstxEOFException

 

 

On Thu, Feb 11, 2010 at 2:26 AM, Colin Sharples [DATACOM]
colin.sharp...@datacom.co.nz wrote:

I have an Axis2 web service that was working fine, but in the last
couple of days has started misbehaving. Every now and then, the client
gets a com.ctc.wstx.exc.WstxEOFException when calling
OperationClient.execute().  The exception detail says: Unexpected EOF
in prolog at [row,col {unknown-source}]: [1,0]

 

The stack trace showed the fault occurred in
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(),
just after AxisEngine.receive().

 

I put some debugging into my service class, and it is clear that the
incoming request never gets into the service, which suggests that it is
the request from the client that is faulty. 


I think it gets this exception when it try to parse the response. see
the response message. You can use tcpmon[1] for that.

thanks,
Amila.

[1] http://ws.apache.org/commons/tcpmon/download.cgi 

 

Does anyone have any idea what might be causing this?

 

Colin Sharples

 

Solutions Architect | Datacom Systems  Integration

Email: colin.sharp...@datacom.co.nz | Mob: +64-27-457-6628

 




-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

RE: com.ctc.wstx.exc.WstxEOFException

[Martin Gainty]

can you publish the wsdl and the accompanying xsds?

Martin Gainty 
__ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
 
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est 
interdite. Ce message sert à l'information seulement et n'aura pas n'importe 
quel effet légalement obligatoire. Étant donné que les email peuvent facilement 
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité 
pour le contenu fourni.




Subject: RE: com.ctc.wstx.exc.WstxEOFException
Date: Fri, 12 Feb 2010 15:47:49 +1300
From: colin.sharp...@datacom.co.nz
To: axis-user@ws.apache.org
















No, I’m pretty sure this is a problem in the generated
client. When I used tcpmon, I couldn’t get the error at all. I don’t
get the error when calling the web service from SoapUI, nor from the Eclipse
Web Services Test explorer.

 

I wrote a standalone Java program using the generated client
stub to call the web service 10 times. It fails every second call, i.e. 5 out
of the 10 calls fail, every time I run the program.

 

I’m pretty sure I didn’t specify broken=”true”
when I generated the client:

 

taskdef name=wsdl2java 
classname=org.apache.axis2.tool.ant.AntCodegenTask

   
classpath

   
fileset dir=${axis2-lib} includes=*.jar/

   
/classpath

/taskdef

target name=gen-wsdl-client-sch

   
wsdl2java wsdlfilename=ScheduleService.wsdl packagename=nz.co.datacom.foo 
databindingname=jibx synconly=true serverside=false 
generateservicexml=false unwrap=false 
targetsourcefolderlocation=../Client/src overwrite=true

   
parameter name=bindingfile value=binding.xml/

   
/wsdl2java

/target

 

I’m just using the client stub generated by wsdl2java unchanged.

 



From: Amila Suriarachchi
[mailto:amilasuriarach...@gmail.com] 

Sent: Thursday, 11 February 2010 6:11 p.m.

To: axis-user@ws.apache.org

Subject: Re: com.ctc.wstx.exc.WstxEOFException



 

 



On Thu, Feb 11, 2010 at 2:26 AM, Colin Sharples [DATACOM]
colin.sharp...@datacom.co.nz
wrote:





I
have an Axis2 web service that was working fine, but in the last couple of days
has started misbehaving. Every now and then, the client gets a 
com.ctc.wstx.exc.WstxEOFException
when calling OperationClient.execute().  The exception detail
says: “Unexpected EOF in prolog at [row,col {unknown-source}]: [1,0]”

 

The
stack trace showed the fault occurred in 
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(),
just after AxisEngine.receive().

 

I
put some debugging into my service class, and it is clear that the incoming
request never gets into the service, which suggests that it is the request from
the client that is faulty. 









I think it gets this exception when it try to parse the response. see the
response message. You can use tcpmon[1] for that.



thanks,

Amila.



[1] http://ws.apache.org/commons/tcpmon/download.cgi










 

Does
anyone have any idea what might be causing this?

 

Colin
Sharples

 

Solutions
Architect | Datacom Systems  Integration

Email:
colin.sharp...@datacom.co.nz
| Mob: +64-27-457-6628

 














-- 

Amila Suriarachchi

WSO2 Inc.

blog: http://amilachinthaka.blogspot.com/

  
_
Hotmail: Powerful Free email with security by Microsoft.
http://clk.atdmt.com/GBL/go/201469230/direct/01/

RE: xsi:type

[Rahul Rulz]

Hi Martin,
Thanks for your reply.. basically I want to include the XSi:type in the 
responses made from my server..
This is the response I am getting from my server presently : 
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; 
xmlns:xsd=http://www.w3.org/2001/XMLSchema; 
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;   /soapenv:Header   
soapenv:Body      ns4:PBSNR xmlns:ns4=bp:ProfileManagementService         
PBSNRT            SNs               SLSLINKED/SLS               
SN12Ea345/SN               SNStatusACTIVE/SNStatus               
STMDN/ST            /SNs            SNs               
SLSINITIAL/SLS               SN12Ea345/SN               
SNStatusACTIVE/SNStatus               STMDN/ST            /SNs        
    user               ns7:userSegment 
xmlns:ns7=http://user.prof.services.bp.com/               
usernameem...@bp.com/username            /user         /PBSNRT      
/ns4:PBSNR  
 /soapenv:Body/soapenv:Envelope
But I want to include the types in the message and it would look as
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; 
xmlns:xsd=http://www.w3.org/2001/XMLSchema; 
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;   /soapenv:Header   
soapenv:Body      ns4:PBSNR xmlns:ns4=bp:ProfileManagementService         
PBSNRT            SNs               SLSLINKED/SLS               SN 
xsi:type=ns1:ServiceTypeEnum12/SN               SNStatus 
xsi:type=xsd:stringACTIVE/SNStatus               ST 
xsi:type=xsd:stringMDN/ST            /SNs            SNs               
SLSINITIAL/SLS               SN xsi:type=ns1:ServiceTypeEnum12/SN     
          SNStatusACTIVE/SNStatus               ST 
xsi:type=xsd:stringMDN/ST            /SNs            user              
 ns7:userSegment xmlns:ns7=http://user.prof.services.bp.com/        
       usernameem...@bp.com/username            /user         /PBSNRT   
   /ns4:PBSNR   /soapenv:Body/soapenv:Envelope
Please note that I have developed the service from the scratch without the 
WSDL.. 
It would be great if you can guide me.
Many Thanks,Raghav.

--- On Fri, 2/12/10, Martin Gainty mgai...@hotmail.com wrote:

From: Martin Gainty mgai...@hotmail.com
Subject: RE: xsi:type
To: axis-user@ws.apache.org
Date: Friday, February 12, 2010, 7:39 AM





 
we would need to see the schema instance namespace declaration such as
schema xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance...

Martin Gainty 
__ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est 
interdite. Ce message sert à l'information seulement et n'aura pas n'importe 
quel effet légalement obligatoire. Étant donné que les email peuvent facilement 
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité 
pour le contenu fourni.




Date: Thu, 11 Feb 2010 16:38:58 -0800
From: ragul...@yahoo.com
Subject: Re: xsi:type
To: axis-user@ws.apache.org

Hi Users,
can anyone help me out please...
Thanks,Raghav.

 

--- On Thu, 2/11/10, Rahul Rulz ragul...@yahoo.com wrote:

From: Rahul Rulz ragul...@yahoo.com
Subject: xsi:type
To: axis-user@ws.apache.org
Date: Thursday, February 11, 2010, 11:03 AM

Hi All,
I am looking to include xsi:type in the responses from my server for a ling 
time :( .. Have not done it till now..Could anyone pl. help me as to do it..I 
have created a service from
 scratch(not from WSDL generated java code) which uses message receivers and 
send the responses. I am using axis2 1.5.1
Thanks for your help.
Regards,Raghav.

 


  
  
Hotmail: Trusted email with powerful SPAM protection. Sign up now. 



  

RE: com.ctc.wstx.exc.WstxEOFException

[Colin Sharples [DATACOM]]

Not easily, as it is commercially confidential.

 

It seems to have resolved itself now. I had renamed a field in one of the 
domain objects, but the schema in the WSDL was still referring to the old field 
name. I changed the schema to use the correct field name, and now the generated 
client works every time.

 

What I want to know now is, why did it work at all!! How did it manage to 
return the correct result some of the time, but not all the time? Weird.

 

Thanks anyway.

 

From: Martin Gainty [mailto:mgai...@hotmail.com] 
Sent: Friday, 12 February 2010 4:09 p.m.
To: axis-user@ws.apache.org
Subject: RE: com.ctc.wstx.exc.WstxEOFException

 

can you publish the wsdl and the accompanying xsds?

Martin Gainty 
__ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité

 
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.

Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est 
interdite. Ce message sert à l'information seulement et n'aura pas n'importe 
quel effet légalement obligatoire. Étant donné que les email peuvent facilement 
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité 
pour le contenu fourni.









Subject: RE: com.ctc.wstx.exc.WstxEOFException
Date: Fri, 12 Feb 2010 15:47:49 +1300
From: colin.sharp...@datacom.co.nz
To: axis-user@ws.apache.org

No, I'm pretty sure this is a problem in the generated client. When I used 
tcpmon, I couldn't get the error at all. I don't get the error when calling the 
web service from SoapUI, nor from the Eclipse Web Services Test explorer.

 

I wrote a standalone Java program using the generated client stub to call the 
web service 10 times. It fails every second call, i.e. 5 out of the 10 calls 
fail, every time I run the program.

 

I'm pretty sure I didn't specify broken=true when I generated the client:

 

taskdef name=wsdl2java 
classname=org.apache.axis2.tool.ant.AntCodegenTask

classpath

fileset dir=${axis2-lib} includes=*.jar/

/classpath

/taskdef

target name=gen-wsdl-client-sch

wsdl2java wsdlfilename=ScheduleService.wsdl 
packagename=nz.co.datacom.foo databindingname=jibx synconly=true 
serverside=false generateservicexml=false unwrap=false 
targetsourcefolderlocation=../Client/src overwrite=true

parameter name=bindingfile value=binding.xml/

/wsdl2java

/target

 

I'm just using the client stub generated by wsdl2java unchanged.

 

From: Amila Suriarachchi [mailto:amilasuriarach...@gmail.com] 
Sent: Thursday, 11 February 2010 6:11 p.m.
To: axis-user@ws.apache.org
Subject: Re: com.ctc.wstx.exc.WstxEOFException

 

 

On Thu, Feb 11, 2010 at 2:26 AM, Colin Sharples [DATACOM] 
colin.sharp...@datacom.co.nz wrote:

I have an Axis2 web service that was working fine, but in the last couple of 
days has started misbehaving. Every now and then, the client gets a 
com.ctc.wstx.exc.WstxEOFException when calling OperationClient.execute().  The 
exception detail says: Unexpected EOF in prolog at [row,col {unknown-source}]: 
[1,0]

 

The stack trace showed the fault occurred in 
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(), just 
after AxisEngine.receive().

 

I put some debugging into my service class, and it is clear that the incoming 
request never gets into the service, which suggests that it is the request from 
the client that is faulty. 


I think it gets this exception when it try to parse the response. see the 
response message. You can use tcpmon[1] for that.

thanks,
Amila.

[1] http://ws.apache.org/commons/tcpmon/download.cgi 

 

Does anyone have any idea what might be causing this?

 

Colin Sharples

 

Solutions Architect | Datacom Systems  Integration

Email: colin.sharp...@datacom.co.nz | Mob: +64-27-457-6628

 




-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

 



Hotmail: Powerful Free email with security by Microsoft. Get it now. 
http://clk.atdmt.com/GBL/go/201469230/direct/01/ 

Re: Basic question on WSDL

[Amila Suriarachchi]

this[1] may help you.

please see how to specify headers.

thanks,
Amila.

[1] http://wso2.org/library/2935

On Fri, Feb 12, 2010 at 7:48 AM, Yashwanth Rajaram -X (yrajaram - Zensar at
Cisco) yraja...@cisco.com wrote:

  Hi All:



 I want to expose a WebService that would take a single parameter. However I
 want the caller to provide certain SOAP header parameters. Is there a way to
 enforce these required header, say, by using an XSD in WSDL or anything
 along those lines?



 thanks,

 --

 Yashwanth

 This email does not reflect the opinion of my employer/cisco.




-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

RE: Interoperability of Axis2

[Sandeep Khurana]

Any pointer on this issue will be helpful...
-Sandeep

From: Sandeep Khurana [mailto:sandeep_khur...@persistent.co.in]
Sent: Thursday, February 11, 2010 6:52 PM
To: axis-user@ws.apache.org
Subject: RE: Interoperability of Axis2

I have checked the request and response messages.
wsdl:message name=getMethodRequest /
wsdl:message name=getMethodResponse
They are present in the WSDL file. Actually I am able to get String Objects but 
not this Custom Objects.
Any pointers will be helpful?

-Sandeep


From: Amila Suriarachchi [mailto:amilasuriarach...@gmail.com]
Sent: Thursday, February 11, 2010 10:34 AM
To: axis-user@ws.apache.org
Subject: Re: Interoperability of Axis2


On Wed, Feb 10, 2010 at 9:31 PM, Sandeep Khurana 
sandeep_khur...@persistent.co.inmailto:sandeep_khur...@persistent.co.in 
wrote:
Hi,
I have created a simple webservice using the POJO class in eclipse. One of the 
web had a custom class as a parameter.
The issue that I faced was when I created the C++ client using gSoap client. 
The Webservice was not able to receive the custom class object and it was null

Is this a known issue or I need to do some more settings?

check the wsdl you get with the deployed service with the request and response 
messages.

thanks,
Amila.

-sandeep

DISCLAIMER == This e-mail may contain privileged and confidential 
information which is the property of Persistent Systems Ltd. It is intended 
only for the use of the individual or entity to which it is addressed. If you 
are not the intended recipient, you are not authorized to read, retain, copy, 
print, distribute or use this message. If you have received this communication 
in error, please notify the sender and delete all copies of this message. 
Persistent Systems Ltd. does not accept any liability for virus infected mails.



--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

DISCLAIMER == This e-mail may contain privileged and confidential 
information which is the property of Persistent Systems Ltd. It is intended 
only for the use of the individual or entity to which it is addressed. If you 
are not the intended recipient, you are not authorized to read, retain, copy, 
print, distribute or use this message. If you have received this communication 
in error, please notify the sender and delete all copies of this message. 
Persistent Systems Ltd. does not accept any liability for virus infected mails.

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

RE : Need suggestions on Axis/c client stub

[Olivier Mengué]

Hi

I'm a recent Axis2/C user. I don't know about Axis-C/C++.

Ashok P wrote:

3) As per the  documentation, axis-c supports ADB binding for client code
generations and none option for raw xml in/out. Is ADB is efficient to
consume non-axis web services?  

I don't know what is ADB binding.
With Axis2/C I had to do manual XML tree building. The Axis2 codegen tool was 
not able to
generate the XML tree building for my WSDL.

5) Does it mandatory to use axis2.xml? I like all these settings through
code by settings the options - like settings the protocol http or https
(ssl), port , ssl certificate, client timeout and more. Does such provision
is available in both C/C++ client generated code?

I'm interested by an answer to this question too.

6)  From the other posting on forum, it's not clear that AXIS2C_HOME
deplorer folder is mandatory or not for client side. Can anybody confirm
this?

It seems to be mandatory to use AXIS2C_HOME as it is the way to find the 
axis2.xml.

axis2.xml is AFAIK mantadory for client side.

 I agree few Dlls are required for client distribution. I like my
client application (along with client stub) should have small footprint for
distribution, so can I build stub statically for depended libraries like
axiom.dll, axis2_http_sender.dll etc?

It looks like the transport layers (http_sender, http_receiver...) are loaded 
dynamically by Axis2/C.
And there is no option in the build system to make a build with statically 
linked transports.

7) Axis-C++ is not recommended for production use. Does I need to test
client generated (stub) for stability considering the recommendation? Any
suggestions on axis-c++ clients to be used on production? Otherwise I need
go with axis-c only.

The recommandation is to use Axis2/C (which is not axis-c).
I understood it as Axis-C++ is buggy and is broken by design, we choose to 
rewrite everything as Axis2/C. Is it really the case? I don't know. That is 
just the feeling I got by reading the site.

Olivier Mengué
winmail.dat

RE : Need suggestions on Axis/c client stub

[Nadir Amra]

Axis-C++ client-side is not broken or buggy.  It is perfectly functional 
and in some cases much easier to use than axis2/C.
 

Nadir Amra


Olivier Mengué omen...@oxymel.com wrote on 02/10/2010 04:41:51 AM:

 [image removed] 
 
 RE : Need suggestions on Axis/c client stub
 
 Olivier Mengué 
 
 to:
 
 Apache AXIS C User List
 
 02/10/2010 04:42 AM
 
 Please respond to Apache AXIS C User List
 
 Hi
 
 I'm a recent Axis2/C user. I don't know about Axis-C/C++.
 
 Ashok P wrote:
 
.
.
.
 
 7) Axis-C++ is not recommended for production use. Does I need to test
 client generated (stub) for stability considering the recommendation? 
Any
 suggestions on axis-c++ clients to be used on production? Otherwise I 
need
 go with axis-c only.
 
 The recommandation is to use Axis2/C (which is not axis-c).
 I understood it as Axis-C++ is buggy and is broken by design, we 
 choose to rewrite everything as Axis2/C. Is it really the case? I 
 don't know. That is just the feeling I got by reading the site.
 
 Olivier Mengué

Re: RE : Need suggestions on Axis/c client stub

[Ashok P]

Thanks to all for suggestions and inputs.

Any suggestions on point-1 - data type mapping? for example if you check
typemap.dat in case of gsoap which gives us a easy way to map data types.  I
am planning to take a look on code generation source code. Will it work if I
change  for data types?

I will update on point 5 and 6 as I started investigations on it.

/// Ashok



Nadir Amra wrote:
 
 Axis-C++ client-side is not broken or buggy.  It is perfectly functional 
 and in some cases much easier to use than axis2/C.
  
 
 Nadir Amra
 
 
 Olivier Mengué omen...@oxymel.com wrote on 02/10/2010 04:41:51 AM:
 
 [image removed] 
 
 RE : Need suggestions on Axis/c client stub
 
 Olivier Mengué 
 
 to:
 
 Apache AXIS C User List
 
 02/10/2010 04:42 AM
 
 Please respond to Apache AXIS C User List
 
 Hi
 
 I'm a recent Axis2/C user. I don't know about Axis-C/C++.
 
 Ashok P wrote:
 
 .
 .
 .
 
 7) Axis-C++ is not recommended for production use. Does I need to test
 client generated (stub) for stability considering the recommendation? 
 Any
 suggestions on axis-c++ clients to be used on production? Otherwise I 
 need
 go with axis-c only.
 
 The recommandation is to use Axis2/C (which is not axis-c).
 I understood it as Axis-C++ is buggy and is broken by design, we 
 choose to rewrite everything as Axis2/C. Is it really the case? I 
 don't know. That is just the feeling I got by reading the site.
 
 Olivier Mengué
 
 

-- 
View this message in context: 
http://old.nabble.com/Need-suggestions-on-Axis-c-client-stub-tp27518586p27542741.html
Sent from the Axis - C++ - User mailing list archive at Nabble.com.

RE: Location to call getCurrentMessageContext

[Christian Schouten]

Hi Deepal,

Thanks, it sounds very logical and it is probably exactly what I need to
first retrieve client, then context, then message. I am just wondering
though how to retrieve the service client instance.
I need to place my code in a JAR that is called automatically by ODE
upon finding a reference in the BPEL (i.e.
bpel:fromprefix:functionName($thisReceive__requestRequestMsg.body/name
space:wsdlField, param)/bpel:from). I do not start the server or
call a service directly myself, I am simply placed in the middle.
So I guess my first question to ask is, is there a standardized way to
reach above into Axis2 or should I ask this question in an ODE-specific
group?

Met vriendelijke groet,
 
Christian C. Schouten


-Original Message-
From: Deepal jayasinghe [mailto:deep...@gmail.com] 
Sent: woensdag 10 februari 2010 0:16
To: axis-user@ws.apache.org
Subject: Re: Location to call getCurrentMessageContext

First get the service client instance, and then call the following
method to get the OperationContext, once you have operation context you
have access to both in and out messages contexts.

getLastOperationContext

Thanks,
Deepal

 Dear all,

  

 From within a webservice that runs on Axis2, I need to access some
 soap header information (the wsse:BinarySecurityToken to be exact, I
 need to find out which certificate was passed for client
authentication).

  

 Application architecture: I am running Intalio BPMS, which is Apache
 ODE that seems to auto-create a webservice and its WSDL on Axis2
 (without programming on my side). This runs on Tomcat.

  

 I do not have access to the code generated by ODE or to the
 integration between ODE and Axis2 (I think...) but I can place a JAR
in
 ODE's classpath. Any (static) functions within that JAR are
 automatically visible to ODE.

 In other words, I can for instance define a jar with a static function
 f that accepts as input one of my wsdl parameters and outputs
 something that can be used in following steps of the ODE-managed
process.

 So far so good, no problems there since I've remained within the realm
 of the data sent as input to the WSDL (i.e. only parameters from
 inside the soap:body that are automatically available).

  

 Now as mentioned I need to access the soap:header and there I've got a
 problem since the bpel layer is happily unaware of the existence of
 such a thing as the soap:header.

 After some googling I started to think that my best bet was to add a
 jar/function in ode's classpath and to call
 MessageContext.getCurrentMessageContext() from there (am I correct in
 assuming this or is there a better alternative?).

 Unfortunately my first attempt stranded with a null coming back from
 it. All functions are accessible/callable and also have the Axis2
 jar's in the same classpath directory so that should be ok. My guess
 is I'm in a different thread or context due to placing it in a
 separate jar maybe but how do I find out if this is true? And how can
 I access another thread's information if this is the problem? The
 entire process spans a single (synchronous) soap request/response
 dialog so I guess there should be a message context somewhere (as the
 request comes in before the call to my new jar and the response is
 sent out after the call to it).

  

 Any help or pointers is more than appreciated,

  

 Best,

  

 Christian C. Schouten

  

  



-- 
Thank you!


http://blogs.deepal.org
http://deepal.org

RE: Initializing Web Service (Server) before first request received

[Oded Onn]

Deepal,
Can you please elaborate a bit more. I am not sure I quite understand
what you mean.
Thanks,
Oded

-Original Message-
From: Deepal Jayasinghe [mailto:dee...@opensource.lk] 
Sent: Wednesday, February 10, 2010 00:58
To: axis-user@ws.apache.org
Subject: Re: Initializing Web Service (Server) before first request
received

Deploy there service in Application scope.

Thanks,
Deepal

 Hi all,

  

 I am deploying an AXIS2 web service (server side).

  

 My problem: The skeleton class (the one that performs all the business
 logic) is read for the first time only when the first request is
 received by the server. It means that the first response takes a
 really long time (up to 20 seconds on a weak machine) since there are
 a lot of initialization I have to perform (static init).

  

 Solution: I am assuming I can write some sort of a main class that
 will try to call the skeleton class. This is not only ugly but also
 prone to all sorts of errors. Is there a proper way to init my service
 class? I would expect some mechanism to be used, such as utilizing the
 servlet init of the axis servlet.

  

 Anyone? Thanks!

 Oded


-- 
Thank you!


http://blogs.deepal.org
http://deepal.org

RE: Initializing Web Service (Server) before first request received

[Doughty, Michael]

In your services.xml file, add 'scope= application' to the service element, 
as follows:

service name=***your service name*** scope= application

The service will then be deployable in application mode.

Now a question to Deepal... will this actually load the implementation class 
immediately on deployment and thus cause all static initialization in the class 
to take place?

I know that application mode will cause Axis2 to treat the implementation class 
as a singleton and reuse the same instance for each service call, but I was 
still under the impression that it would require that first service call to be 
made still.  If the class is loaded on deployment or the singleton is 
constructed prior to the first service call, then that is definitely good news.

-Original Message-
From: Oded Onn [mailto:oded@mobixell.com] 
Sent: Wednesday, February 10, 2010 3:21 AM
To: axis-user@ws.apache.org
Subject: RE: Initializing Web Service (Server) before first request received

Deepal,
Can you please elaborate a bit more. I am not sure I quite understand
what you mean.
Thanks,
Oded

-Original Message-
From: Deepal Jayasinghe [mailto:dee...@opensource.lk] 
Sent: Wednesday, February 10, 2010 00:58
To: axis-user@ws.apache.org
Subject: Re: Initializing Web Service (Server) before first request
received

Deploy there service in Application scope.

Thanks,
Deepal

 Hi all,

  

 I am deploying an AXIS2 web service (server side).

  

 My problem: The skeleton class (the one that performs all the business
 logic) is read for the first time only when the first request is
 received by the server. It means that the first response takes a
 really long time (up to 20 seconds on a weak machine) since there are
 a lot of initialization I have to perform (static init).

  

 Solution: I am assuming I can write some sort of a main class that
 will try to call the skeleton class. This is not only ugly but also
 prone to all sorts of errors. Is there a proper way to init my service
 class? I would expect some mechanism to be used, such as utilizing the
 servlet init of the axis servlet.

  

 Anyone? Thanks!

 Oded


-- 
Thank you!


http://blogs.deepal.org
http://deepal.org

Re: change EPR

[Charles Galpin]

http://amilachinthaka.blogspot.com/2010/01/changing-axis2-application-path.html

hth
charles

On Feb 10, 2010, at 4:16 AM, Sandeep Khurana wrote:

 I am creating simple pojo webservice like TemperatureConversion. I was able 
 to make deploy it and generate wsdl from it.
 The problem is that I want to change the EPR / address 
 fromhttp://172.x.x.x:8080/MyWebservice/services/TemperatureConversion 
 tohttp://172.x.x.x:8080/MyWebservice/TemperatureConversion
 Is that possible?
 Thanks.

Re: Initializing Web Service (Server) before first request received

[Charles Galpin]

I'm not sure I ever fully understood this, even after reading the docs on the 
service lifecycle a few times. What I found was that the methods did not fire 
the same way during hot deployment as they do on startup so don't get fooled by 
that. The best I came up with was use application scope, restart tomcat 
whenever I needed to apply a change, and the init method was the best place to 
put any one time setup code.

hth
charles

On Feb 10, 2010, at 5:23 AM, Doughty, Michael wrote:

 In your services.xml file, add 'scope= application' to the service 
 element, as follows:
 
 service name=***your service name*** scope= application
 
 The service will then be deployable in application mode.
 
 Now a question to Deepal... will this actually load the implementation class 
 immediately on deployment and thus cause all static initialization in the 
 class to take place?
 
 I know that application mode will cause Axis2 to treat the implementation 
 class as a singleton and reuse the same instance for each service call, but I 
 was still under the impression that it would require that first service call 
 to be made still.  If the class is loaded on deployment or the singleton is 
 constructed prior to the first service call, then that is definitely good 
 news.
 
 -Original Message-
 From: Oded Onn [mailto:oded@mobixell.com] 
 Sent: Wednesday, February 10, 2010 3:21 AM
 To: axis-user@ws.apache.org
 Subject: RE: Initializing Web Service (Server) before first request received
 
 Deepal,
 Can you please elaborate a bit more. I am not sure I quite understand
 what you mean.
 Thanks,
 Oded
 
 -Original Message-
 From: Deepal Jayasinghe [mailto:dee...@opensource.lk] 
 Sent: Wednesday, February 10, 2010 00:58
 To: axis-user@ws.apache.org
 Subject: Re: Initializing Web Service (Server) before first request
 received
 
 Deploy there service in Application scope.
 
 Thanks,
 Deepal
 
 Hi all,
 
 
 
 I am deploying an AXIS2 web service (server side).
 
 
 
 My problem: The skeleton class (the one that performs all the business
 logic) is read for the first time only when the first request is
 received by the server. It means that the first response takes a
 really long time (up to 20 seconds on a weak machine) since there are
 a lot of initialization I have to perform (static init).
 
 
 
 Solution: I am assuming I can write some sort of a main class that
 will try to call the skeleton class. This is not only ugly but also
 prone to all sorts of errors. Is there a proper way to init my service
 class? I would expect some mechanism to be used, such as utilizing the
 servlet init of the axis servlet.
 
 
 
 Anyone? Thanks!
 
 Oded
 
 
 -- 
 Thank you!
 
 
 http://blogs.deepal.org
 http://deepal.org
 

RE: change EPR

[Sandeep Khurana]

Thanks. That was very simple to follow and it woked.


From: Charles Galpin [mailto:cgal...@lhsw.com]
Sent: Wednesday, February 10, 2010 5:49 PM
To: axis-user@ws.apache.org
Subject: Re: change EPR

http://amilachinthaka.blogspot.com/2010/01/changing-axis2-application-path.html

hth
charles

On Feb 10, 2010, at 4:16 AM, Sandeep Khurana wrote:


I am creating simple pojo webservice like TemperatureConversion. I was able to 
make deploy it and generate wsdl from it.
The problem is that I want to change the EPR / address 
fromhttp://172.x.x.x:8080/MyWebservice/services/TemperatureConversion 
tohttp://172.x.x.x:8080/MyWebservice/TemperatureConversion
Is that possible?
Thanks.


DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

Re: WSDL2Java throws IOException

[Venkatesh Audinarayanan]

After I renamed the namespace name to fix the issue, started getting an NPE
in Axis parser code (with both 1.2 and 1.4):
java.lang.NullPointerException
   at
org.apache.axis.wsdl.toJava.JavaBeanHelperWriter.getAsFieldName(JavaB
eanHelperWriter.java:435)
   at
org.apache.axis.wsdl.toJava.JavaBeanHelperWriter.writeMetaData(JavaBe
anHelperWriter.java:325)
   at
org.apache.axis.wsdl.toJava.JavaBeanHelperWriter.writeFileBody(JavaBe
anHelperWriter.java:183)
   at
org.apache.axis.wsdl.toJava.JavaWriter.generate(JavaWriter.java:127)
   at
org.apache.axis.wsdl.toJava.JavaBeanWriter.writeFileBody(JavaBeanWrit
er.java:257)
   at
org.apache.axis.wsdl.toJava.JavaWriter.generate(JavaWriter.java:127)
   at
org.apache.axis.wsdl.toJava.JavaBeanWriter.generate(JavaBeanWriter.ja
va:1406)
   at
org.apache.axis.wsdl.toJava.JavaTypeWriter.generate(JavaTypeWriter.ja
va:113)
   at
org.apache.axis.wsdl.toJava.JavaGeneratorFactory$Writers.generate(Jav
aGeneratorFactory.java:421)
   at org.apache.axis.wsdl.gen.Parser.generateTypes(Parser.java:547)
   at org.apache.axis.wsdl.gen.Parser.generate(Parser.java:432)
   at org.apache.axis.wsdl.gen.Parser.access$000(Parser.java:45)
   at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:362)
   at java.lang.Thread.run(Unknown Source)
Thanks,
Venkatesh.


On Wed, Feb 10, 2010 at 11:33 AM, Venkatesh Audinarayanan 
venkatesh.a...@gmail.com wrote:

 Hi All,
 Am getting the following error while trying to parse my service wsdl with
 Axis 1.2 wsdl2java:
 Feb 10, 2010 11:28:59 AM org.apache.axis.utils.JavaUtils
 isAttachmentSupported
 WARNING: Unable to find required classes (javax.activation.DataHandler and
 javax
 .mail.internet.MimeMultipart). Attachment support is disabled.
 java.io.IOException: Type {
 http://www.w3.org/2000/09/xmldsig#}SignaturePropertyhttp://www.w3.org/2000/09/xmldsig#%7DSignatureProperty
 is referenced but not defined.
 at
 org.apache.axis.wsdl.symbolTable.SymbolTable.checkForUndefined(Symbol
 Table.java:665)
 at
 org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:545
 )
 at
 org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav
 a:518)
 at
 org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav
 a:495)
 at
 org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361)
 at java.lang.Thread.run(Unknown Source)

 is it reporting the actual error? is this due to some issue with WSDL?
 Appreciate your help.
 Thanks,
 Venkatesh.

Re: WS-Eventing

[Yashvant chauhan]

It is working fine we don't required to get message at Client.java
ListenerService1.java is getting the published message

On 1/10/10, Yashvant chauhan c.yashv...@gmail.com wrote:
 Hi Prabath,

 Can you please upload or mail the source code of following.

 1) axis2-savan-event-sink
 2) axis2-savan-client
 3) axis2-savan-event-source

 Regards,
 Yashvant

 On Sat, Jan 2, 2010 at 9:20 PM, Yashvant chauhan
 c.yashv...@gmail.comwrote:

 Hi,

 I tried Savan eventing Sample there were one PublisherService and two
 ListenerService.
 Client able to subscribe a Service but not able to get the Notification
 how
 I updates the Client.java to get the generated notification

 Regards,
 yashvant

 On Tue, Dec 29, 2009 at 12:27 AM, Gilbert Pilz
 gilbert.p...@oracle.comwrote:

 Hi Martin,

 Sorry, I'm missing a bit of context here. RIA events? WS-Eventing
 supports
 the Subscribe operation. What you are subscribing to is outside the
 scope
 of WS-Eventing.

 - gp

 On 12/26/2009 6:55 PM, Martin Gainty wrote:

 Good Evening Gilbert

 In the other apache projects we've registered listeners to predefined
 RIA
 events such as ContainerStart,SessionStart,SessionEnd..I would be very
 interested to know if this registration process for known RIA events is
 supported by WS-Eventing or is there some other algorithm implmenented
 to
 register the events and/or configure a custom dispatcher to dispatch to
 the
 correct listener

 thanks,
 Martin Gainty
 __
 Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité

 Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene
 Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede
 unbefugte
 Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese
 Nachricht
 dient lediglich dem Austausch von Informationen und entfaltet keine
 rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von
 E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.

 Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas
 le destinataire prévu, nous te demandons avec bonté que pour satisfaire
 informez l'expéditeur. N'importe quelle diffusion non autorisée ou la
 copie de ceci est interdite. Ce message sert à l'information seulement et
 n'aura pas n'importe quel effet légalement obligatoire. Étant donné que
 les email peuvent facilement être sujets à la manipulation, nous ne
 pouvons accepter aucune responsabilité pour le contenu fourni.






 --
 Date: Sat, 26 Dec 2009 16:26:24 -0800
 From: gilbert.p...@oracle.com
 To: axis-user@ws.apache.org
 Subject: Re: WS-Eventing

 If you are interested in WS-Eventing, you might want to keep an eye on
 what is going on at the W3C Web Services Resource Access Working Group
 [1]
 which is working on standardizing (among other things) WS-Eventing.

 [1] http://www.w3.org/2002/ws/ra/

 Gilbert Pilz | Standards Architect | Middleware Standards | Oracle
 Corporation

 On 12/23/2009 12:46 PM, Prabath Siriwardena wrote:

 Please have a look at [1].

 Thanks  regards.
 -Prabath

 [1]: http://blog.facilelogin.com/search/label/Savan

 Yashvant chauhan wrote:

 How I can develope a WS-Eventing in Axis2







 --
 Hotmail: Trusted email with Microsoft’s powerful SPAM protection. Sign
 up
 now. http://clk.atdmt.com/GBL/go/177141664/direct/01/




 --
 
 Yashvant Singh Chauhan
 Mobile- 09845277271
 Bangalore

 *




 --
 
 Yashvant Singh Chauhan
 Mobile- 09845277271
 Bangalore

 *



-- 

Yashvant Singh Chauhan
Mobile- 09845277271
Bangalore

*

Re: Initializing Web Service (Server) before first request received

[KOUKI Fakhreddine]

Hello,

If you are using Tomcat , you can create an InitializerServlet Class that
extend HttpServlet , you override the init() method and put into a call to
your business logic.

On the web.xml :

servlet
servlet-nameTheInitializerServlet/servlet-name
servlet-classpackage.InitializerServlet/servlet-class
load-on-startup100/load-on-startup
/servlet

So the servlet will be loaded at start up and , you business logic will be
executed for the first time (so all classes needed will be loaded) ,
After, when you make the first request to your service it will not take the
time of loading classes.

Ragards,



On 2/10/10, Oded Onn oded@mobixell.com wrote:

 Deepal,
 Can you please elaborate a bit more. I am not sure I quite understand
 what you mean.
 Thanks,
 Oded

 -Original Message-
 From: Deepal Jayasinghe [mailto:dee...@opensource.lk]
 Sent: Wednesday, February 10, 2010 00:58
 To: axis-user@ws.apache.org
 Subject: Re: Initializing Web Service (Server) before first request
 received

 Deploy there service in Application scope.

 Thanks,
 Deepal
 
  Hi all,
 
 
 
  I am deploying an AXIS2 web service (server side).
 
 
 
  My problem: The skeleton class (the one that performs all the business
  logic) is read for the first time only when the first request is
  received by the server. It means that the first response takes a
  really long time (up to 20 seconds on a weak machine) since there are
  a lot of initialization I have to perform (static init).
 
 
 
  Solution: I am assuming I can write some sort of a main class that
  will try to call the skeleton class. This is not only ugly but also
  prone to all sorts of errors. Is there a proper way to init my service
  class? I would expect some mechanism to be used, such as utilizing the
  servlet init of the axis servlet.
 
 
 
  Anyone? Thanks!
 
  Oded
 

 --
 Thank you!


 http://blogs.deepal.org
 http://deepal.org

Re: Location to call getCurrentMessageContext

[Deepal Jayasinghe]

I think you should ask that from ODE first, if they know how to access
ServiceClient instances, then you know the rest.

Deepal

Christian Schouten wrote:
 Hi Deepal,

 Thanks, it sounds very logical and it is probably exactly what I need to
 first retrieve client, then context, then message. I am just wondering
 though how to retrieve the service client instance.
 I need to place my code in a JAR that is called automatically by ODE
 upon finding a reference in the BPEL (i.e.
 bpel:fromprefix:functionName($thisReceive__requestRequestMsg.body/name
 space:wsdlField, param)/bpel:from). I do not start the server or
 call a service directly myself, I am simply placed in the middle.
 So I guess my first question to ask is, is there a standardized way to
 reach above into Axis2 or should I ask this question in an ODE-specific
 group?

 Met vriendelijke groet,
  
 Christian C. Schouten


 -Original Message-
 From: Deepal jayasinghe [mailto:deep...@gmail.com] 
 Sent: woensdag 10 februari 2010 0:16
 To: axis-user@ws.apache.org
 Subject: Re: Location to call getCurrentMessageContext

 First get the service client instance, and then call the following
 method to get the OperationContext, once you have operation context you
 have access to both in and out messages contexts.

 getLastOperationContext

 Thanks,
 Deepal
   
 Dear all,

  

 From within a webservice that runs on Axis2, I need to access some
 soap header information (the wsse:BinarySecurityToken to be exact, I
 need to find out which certificate was passed for client
 
 authentication).
   
  

 Application architecture: I am running Intalio BPMS, which is Apache
 ODE that seems to auto-create a webservice and its WSDL on Axis2
 (without programming on my side). This runs on Tomcat.

  

 I do not have access to the code generated by ODE or to the
 integration between ODE and Axis2 (I think...) but I can place a JAR
 
 in
   
 ODE's classpath. Any (static) functions within that JAR are
 automatically visible to ODE.

 In other words, I can for instance define a jar with a static function
 f that accepts as input one of my wsdl parameters and outputs
 something that can be used in following steps of the ODE-managed
 
 process.
   
 So far so good, no problems there since I've remained within the realm
 of the data sent as input to the WSDL (i.e. only parameters from
 inside the soap:body that are automatically available).

  

 Now as mentioned I need to access the soap:header and there I've got a
 problem since the bpel layer is happily unaware of the existence of
 such a thing as the soap:header.

 After some googling I started to think that my best bet was to add a
 jar/function in ode's classpath and to call
 MessageContext.getCurrentMessageContext() from there (am I correct in
 assuming this or is there a better alternative?).

 Unfortunately my first attempt stranded with a null coming back from
 it. All functions are accessible/callable and also have the Axis2
 jar's in the same classpath directory so that should be ok. My guess
 is I'm in a different thread or context due to placing it in a
 separate jar maybe but how do I find out if this is true? And how can
 I access another thread's information if this is the problem? The
 entire process spans a single (synchronous) soap request/response
 dialog so I guess there should be a message context somewhere (as the
 request comes in before the call to my new jar and the response is
 sent out after the call to it).

  

 Any help or pointers is more than appreciated,

  

 Best,

  

 Christian C. Schouten

  

  

 


   

-- 
Thank you!


http://blogs.deepal.org
http://deepal.org

Re: com.ctc.wstx.exc.WstxEOFException

[Amila Suriarachchi]

On Thu, Feb 11, 2010 at 2:26 AM, Colin Sharples [DATACOM] 
colin.sharp...@datacom.co.nz wrote:

  I have an Axis2 web service that was working fine, but in the last couple
 of days has started misbehaving. Every now and then, the client gets a 
 *com.ctc.wstx.exc.WstxEOFException
 *when calling OperationClient.execute().  The exception detail says: 
 “*Unexpected
 EOF in prolog at [row,col {unknown-source}]: [1,0]*”



 The stack trace showed the fault occurred in *
 org.apache.axis2.description.OutInAxisOperationClient.handleResponse()*,
 just after AxisEngine.receive().



 I put some debugging into my service class, and it is clear that the
 incoming request never gets into the service, which suggests that it is the
 request from the client that is faulty.


I think it gets this exception when it try to parse the response. see the
response message. You can use tcpmon[1] for that.

thanks,
Amila.

[1] http://ws.apache.org/commons/tcpmon/download.cgi



 Does anyone have any idea what might be causing this?



 Colin Sharples



 Solutions Architect | Datacom Systems  Integration

 Email: colin.sharp...@datacom.co.nz | Mob: +64-27-457-6628






-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Re: Need suggestions on Axis/c client stub

[paul . deadman]

I cant provide an answer to all your questions, but for this question:-

2) My requirement is to generate the clients for non-axis web services 
like
.net, JBOSS-WS, etc. So Is there any limitations for such clients? I 
believe
all web services can easily consumed with axis/c client considering they
adhere with WSDL specifications. 

 I found that WSDL2C (from AXIS2) does not work out the box with WCF 
because the WCF WSDL split the schema into at 
least 3 XSD files. This is not the problem in itself, as it is possible to 
download the individual elements and
create a single WSDL file and point WSDL2C at this. But the problem comes 
in that the Data Contract elements
 have a namespace which can not be  changed (or I have not found out how) 
in WCF Visual Studio designer, it is constructed from
a number of elements within the class defintion.
The namespace for the Data Contract elements is different from the other 
elements Operations etc which can be changed
the default is http://tempuri.org . So you need to create a WSDL file with 
schema elements in multiple 
namespaces, this I found hard to do, or at least I could find no examples 
of XSD schema covering multiple namespaces.
I worked round this problem by pasting all the XSD schema elements (using 
the Operations namespace)
together and then editing the stub code 
which is generated, its not difficult as for each Data Contract class in 
WCF you get a .c file from WSDL2C. And
changing the namespace name (which is hardcoded as a string).

My only other comment is that you will need to recompile the 1.6 source 
code for AXIS2C for Windows as the 
downloadable binaryies have a bug, whereby the directory seperator is set 
for a Unix value of / and not a 
windows \. This was a quite painless exercise compared to the WSDL 
manipulation.

Im using it for a production application to connect Lotus Notes, via a DLL 
to a WCF service. And it appears to work
fine.

Paul Deadman
Mobile: 07769 930 235
Skype: Paul Deadman, York
Longfield Ltd
2 Maple House, Northminster Business Park,York,YO26 6QW

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom it is addressed. If 
you are not the intended recipient or there are problems please notify the 
sender and then delete it from your system. We have taken steps to keep 
this email and attachments free from viruses. However, we accept no 
liability for any loss or damage howsoever caused as a result of any virus 
being passed on. It is the responsibility of the recipient to perform all 
necessary checks.



Ashok P ashvit...@gmail.com 
09/02/2010 17:09
Please respond to
Apache AXIS C User List axis-c-user@ws.apache.org


To
axis-c-user@ws.apache.org
cc

Subject
Need suggestions on Axis/c client stub







I want to clear my understandings about axis-c/c++. I got few answers in
email archives and like to understand thoroughly.  Newbie to Axis-c.. :) I
apologize for any repeated  questions. 

1) Can I provide custom mappings for C/C++ data types for code generation
tool?
Wsdl2c/wsd2ws generates the code for xs:string as “char* (axis-char)” and
“std::string” respectively. Is there any way to mention mapping like
“wchar*”  or std::wstring (c++) to toolkit considering Unicode enabled
project?   Does char* processing problematic in case of Unicode string? 

2) My requirement is to generate the clients for non-axis web services 
like
.net, JBOSS-WS, etc. So Is there any limitations for such clients? I 
believe
all web services can easily consumed with axis/c client considering they
adhere with WSDL specifications. 

3) As per the  documentation, axis-c supports “ADB” binding for client 
code
generations and “none” option for raw xml in/out. Is ADB is efficient to
consume non-axis web services? 

4) As per analysis, wsdl2c can generate client code for RPC/document 
literal
styles only. Am I correct? Is there any support available for RPC-encoded
style in near feature?

5) Does it mandatory to use axis2.xml? I like all these settings through
code by settings the options – like settings the protocol “http” or https
(ssl), port , ssl certificate, client timeout and more. Does such 
provision
is available in both C/C++ client generated code?

6)  From the other posting on forum, it’s not clear that “AXIS2C_HOME”
deplorer folder is mandatory or not for client side. Can anybody confirm
this? I agree few Dlls are required for client distribution. I like my
client application (along with client stub) should have small footprint 
for
distribution, so can I build stub statically for depended libraries like
axiom.dll, axis2_http_sender.dll etc?

7) Axis-C++ is not recommended for production use. Does I need to test
client generated (stub) for stability considering the recommendation? Any
suggestions on axis-c++ clients to be used on production? Otherwise I need
go with axis-c only.


Thanks in advance and appreciate your help.
 

-- 
View this message in context: 

Re: Need suggestions on Axis/c client stub

[Nadir Amra]

As far as the Axis-C++ client, it is recommended for production useas 
long as you build the client from the latest code in SVN.

But ensure that it supports what you need supported, which is WSDL 1.1 and 
SOAP 1.1. 

Nadir Amra


Ashok P ashvit...@gmail.com wrote on 02/09/2010 11:09:09 AM:

 [image removed] 
 
 Need suggestions on Axis/c client stub
 
 Ashok P 
 
 to:
 
 axis-c-user
 
 02/09/2010 11:09 AM
 
 Please respond to Apache AXIS C User List
 
 
 I want to clear my understandings about axis-c/c++. I got few answers in
 email archives and like to understand thoroughly.  Newbie to Axis-c.. :) 
 I
 apologize for any repeated  questions. 
 
 1) Can I provide custom mappings for C/C++ data types for code 
generation
 tool?
 Wsdl2c/wsd2ws generates the code for xs:string as ?char* (axis-char)? 
and
 ?std::string? respectively. Is there any way to mention mapping like
 ?wchar*?  or std::wstring (c++) to toolkit considering Unicode enabled
 project?   Does char* processing problematic in case of Unicode string? 
 
 2) My requirement is to generate the clients for non-axis web services 
like
 .net, JBOSS-WS, etc. So Is there any limitations for such clients? I 
believe
 all web services can easily consumed with axis/c client considering they
 adhere with WSDL specifications. 
 
 3) As per the  documentation, axis-c supports ?ADB? binding for client 
code
 generations and ?none? option for raw xml in/out. Is ADB is efficient to
 consume non-axis web services? 
 
 4) As per analysis, wsdl2c can generate client code for RPC/document 
literal
 styles only. Am I correct? Is there any support available for 
RPC-encoded
 style in near feature?
 
 5) Does it mandatory to use axis2.xml? I like all these settings through
 code by settings the options ? like settings the protocol ?http? or 
https
 (ssl), port , ssl certificate, client timeout and more. Does such 
provision
 is available in both C/C++ client generated code?
 
 6)  From the other posting on forum, it?s not clear that ?AXIS2C_HOME?
 deplorer folder is mandatory or not for client side. Can anybody confirm
 this? I agree few Dlls are required for client distribution. I like my
 client application (along with client stub) should have small footprint 
for
 distribution, so can I build stub statically for depended libraries like
 axiom.dll, axis2_http_sender.dll etc?
 
 7) Axis-C++ is not recommended for production use. Does I need to test
 client generated (stub) for stability considering the recommendation? 
Any
 suggestions on axis-c++ clients to be used on production? Otherwise I 
need
 go with axis-c only.
 
 
 Thanks in advance and appreciate your help.
 
 
 -- 
 View this message in context: http://old.nabble.com/Need-
 suggestions-on-Axis-c-client-stub-tp27518586p27518586.html
 Sent from the Axis - C++ - User mailing list archive at Nabble.com.
 

Re: Need suggestions on Axis/c client stub

[Ashok P]

Thanks Nadir and Paul for your quick response and valuable inputs.Now I have
got confidence to go ahead... I got my sample clients working with axis/c
and c++ on windows.

I believe that I will get answers for my other questions also.




Nadir Amra wrote:
 
 As far as the Axis-C++ client, it is recommended for production useas 
 long as you build the client from the latest code in SVN.
 
 But ensure that it supports what you need supported, which is WSDL 1.1 and 
 SOAP 1.1. 
 
 Nadir Amra
 
 
 Ashok P ashvit...@gmail.com wrote on 02/09/2010 11:09:09 AM:
 
 [image removed] 
 
 Need suggestions on Axis/c client stub
 
 Ashok P 
 
 to:
 
 axis-c-user
 
 02/09/2010 11:09 AM
 
 Please respond to Apache AXIS C User List
 
 
 I want to clear my understandings about axis-c/c++. I got few answers in
 email archives and like to understand thoroughly.  Newbie to Axis-c.. :) 
  I
 apologize for any repeated  questions. 
 
 1) Can I provide custom mappings for C/C++ data types for code 
 generation
 tool?
 Wsdl2c/wsd2ws generates the code for xs:string as ?char* (axis-char)? 
 and
 ?std::string? respectively. Is there any way to mention mapping like
 ?wchar*?  or std::wstring (c++) to toolkit considering Unicode enabled
 project?   Does char* processing problematic in case of Unicode string? 
 
 2) My requirement is to generate the clients for non-axis web services 
 like
 .net, JBOSS-WS, etc. So Is there any limitations for such clients? I 
 believe
 all web services can easily consumed with axis/c client considering they
 adhere with WSDL specifications. 
 
 3) As per the  documentation, axis-c supports ?ADB? binding for client 
 code
 generations and ?none? option for raw xml in/out. Is ADB is efficient to
 consume non-axis web services? 
 
 4) As per analysis, wsdl2c can generate client code for RPC/document 
 literal
 styles only. Am I correct? Is there any support available for 
 RPC-encoded
 style in near feature?
 
 5) Does it mandatory to use axis2.xml? I like all these settings through
 code by settings the options ? like settings the protocol ?http? or 
 https
 (ssl), port , ssl certificate, client timeout and more. Does such 
 provision
 is available in both C/C++ client generated code?
 
 6)  From the other posting on forum, it?s not clear that ?AXIS2C_HOME?
 deplorer folder is mandatory or not for client side. Can anybody confirm
 this? I agree few Dlls are required for client distribution. I like my
 client application (along with client stub) should have small footprint 
 for
 distribution, so can I build stub statically for depended libraries like
 axiom.dll, axis2_http_sender.dll etc?
 
 7) Axis-C++ is not recommended for production use. Does I need to test
 client generated (stub) for stability considering the recommendation? 
 Any
 suggestions on axis-c++ clients to be used on production? Otherwise I 
 need
 go with axis-c only.
 
 
 Thanks in advance and appreciate your help.
 
 
 -- 
 View this message in context: http://old.nabble.com/Need-
 suggestions-on-Axis-c-client-stub-tp27518586p27518586.html
 Sent from the Axis - C++ - User mailing list archive at Nabble.com.
 
 
 
 

-- 
View this message in context: 
http://old.nabble.com/Need-suggestions-on-Axis-c-client-stub-tp27518586p27526468.html
Sent from the Axis - C++ - User mailing list archive at Nabble.com.

Re: [Axis2] - Error setting SOAP 1.1

[Juan Felipe Alvarez Saldarriaga]

Hey.

What about if I force the client to be SOAP 1.1? this will change those
namepsaces, right?

Thanks for any help.

On Mon, Feb 8, 2010 at 10:16 PM, Juan Felipe Alvarez Saldarriaga 
nebi...@gmail.com wrote:

 Hey Amila.

 Thanks for asking, yes, same libraries in both servers, I just copy those
 from one server to the other, pretty odd eh?

 Thanks.


 On Mon, Feb 8, 2010 at 10:07 PM, Amila Suriarachchi 
 amilasuriarach...@gmail.com wrote:



 On Tue, Feb 9, 2010 at 2:26 AM, Juan Felipe Alvarez Saldarriaga 
 nebi...@gmail.com wrote:

 Hey!.

 I got some question about Axis2, in one machine when I create a request
 using Axis2 it creates this request:

 ?xml version='1.0' encoding='utf-8'?
 soapenv:Envelope xmlns:soapenv=
 http://schemas.xmlsoap.org/soap/envelope/;
 soapenv:Header
 wsse:Security xmlns:wsse=
 http://schemas.xmlsoap.org/ws/2002/07/secext;
 soapenv:mustUnderstand=1
 wsse:BinarySecurityToken xmlns:wsu=
 http://schemas.xmlsoap.org/ws/2002/07/utility;
 EncodingType=wsse:Base64Binary ValueType=wsse:X509v3
 wsu:Id=CertId-36765048
 /* Secure message */
 /wsse:BinarySecurityToken
 ds:Signature xmlns:ds=http://www.w3.org/2000/09/xmldsig#;
 Id=Signature-28340672
 ds:SignedInfo
 ds:CanonicalizationMethod Algorithm=
 http://www.w3.org/2001/10/xml-exc-c14n#; /
 ds:SignatureMethod Algorithm=
 http://www.w3.org/2000/09/xmldsig#rsa-sha1; /
 ds:Reference URI=#id-1283730842
 ds:Transforms
 ds:Transform Algorithm=
 http://www.w3.org/2001/10/xml-exc-c14n#; /
 /ds:Transforms
 ds:DigestMethod Algorithm=
 http://www.w3.org/2000/09/xmldsig#sha1; /
 ds:DigestValue
 /* Some digest */
 /ds:DigestValue
 /ds:Reference
 /ds:SignedInfo
 ds:SignatureValue
 /* Sign value */
 /ds:SignatureValue
 ds:KeyInfo Id=KeyId-1727788317
 wsse:SecurityTokenReference xmlns:wsu=
 http://schemas.xmlsoap.org/ws/2002/07/utility; wsu:Id=STRId-664369085
 wsse:Reference URI=#CertId-36765048
 ValueType=wsse:X509v3 /
 /wsse:SecurityTokenReference
 /ds:KeyInfo
 /ds:Signature
 wsu:Timestamp xmlns:wsu=
 http://schemas.xmlsoap.org/ws/2002/07/utility;
 wsu:Id=Timestamp-1735528613
 wsu:Created2010-02-06T02:52:19.946Z/wsu:Created
 /wsu:Timestamp
 /wsse:Security
 messageHeader xmlns=
 http://www.uc-council.org/smp/schemas/eanucc;
 soapenv:mustUnderstand=0
 /* Message header */
 /messageHeader
 /soapenv:Header
 soapenv:Body xmlns:wsu=
 http://schemas.xmlsoap.org/ws/2002/07/utility; wsu:Id=id-1283730842
 /* Body */
 /soapenv:Body
 /soapenv:Envelope

 And on the other machine, the same code change the namespaces from
 http://schemas.xmlsoap.org/* to http://docs.oasis-open.org/* and doesn't
 work with our server:

 ?xml version='1.0' encoding='utf-8'?
 soapenv:Envelope xmlns:soapenv=
 http://schemas.xmlsoap.org/soap/envelope/;
 soapenv:Header
 wsse:Security xmlns:wsse=
 http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd;
 soapenv:mustUnderstand=1
 wsse:BinarySecurityToken xmlns:wsu=
 http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
 EncodingType=wsse:Base64Binary ValueType=wsse:X509v3
 wsu:Id=CertId-36765048
 /* Secure message */
 /wsse:BinarySecurityToken
 ds:Signature xmlns:ds=http://www.w3.org/2000/09/xmldsig#;
 Id=Signature-1809025927
 ds:SignedInfo
 ds:CanonicalizationMethod Algorithm=
 http://www.w3.org/2001/10/xml-exc-c14n#; /
 ds:SignatureMethod Algorithm=
 http://www.w3.org/2000/09/xmldsig#rsa-sha1; /
 ds:Reference URI=#id-47973429
 ds:Transforms
 ds:Transform Algorithm=
 http://www.w3.org/2001/10/xml-exc-c14n#; /
 /ds:Transforms
 ds:DigestMethod Algorithm=
 http://www.w3.org/2000/09/xmldsig#sha1; /
 ds:DigestValue
 /* Some digest */
 /ds:DigestValue
 /ds:Reference
 /ds:SignedInfo
 ds:SignatureValue
 /* Sign value */
 /ds:SignatureValue
 ds:KeyInfo Id=KeyId-923425825
 wsse:SecurityTokenReference xmlns:wsu=
 http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
 wsu:Id=STRId-1148428095
 wsse:Reference URI=#CertId-36765048
 ValueType=wsse:X509v3 /
 /wsse:SecurityTokenReference
 /ds:KeyInfo
 

Re: [Axis2] - Error setting SOAP 1.1

[Amila Suriarachchi]

hi,

as I see both of your request in the same name space.
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;

what is difference is the ws security header namespace. Please send this
question to rampar-dev as well.

thanks,
Amila.


On Tue, Feb 9, 2010 at 7:35 PM, Juan Felipe Alvarez Saldarriaga 
nebi...@gmail.com wrote:

 Hey.

 What about if I force the client to be SOAP 1.1? this will change those
 namepsaces, right?




 Thanks for any help.


 On Mon, Feb 8, 2010 at 10:16 PM, Juan Felipe Alvarez Saldarriaga 
 nebi...@gmail.com wrote:

 Hey Amila.

 Thanks for asking, yes, same libraries in both servers, I just copy those
 from one server to the other, pretty odd eh?

 Thanks.


 On Mon, Feb 8, 2010 at 10:07 PM, Amila Suriarachchi 
 amilasuriarach...@gmail.com wrote:



 On Tue, Feb 9, 2010 at 2:26 AM, Juan Felipe Alvarez Saldarriaga 
 nebi...@gmail.com wrote:

 Hey!.

 I got some question about Axis2, in one machine when I create a request
 using Axis2 it creates this request:

 ?xml version='1.0' encoding='utf-8'?
 soapenv:Envelope xmlns:soapenv=
 http://schemas.xmlsoap.org/soap/envelope/;
 soapenv:Header
 wsse:Security xmlns:wsse=
 http://schemas.xmlsoap.org/ws/2002/07/secext;
 soapenv:mustUnderstand=1
 wsse:BinarySecurityToken xmlns:wsu=
 http://schemas.xmlsoap.org/ws/2002/07/utility;
 EncodingType=wsse:Base64Binary ValueType=wsse:X509v3
 wsu:Id=CertId-36765048
 /* Secure message */
 /wsse:BinarySecurityToken
 ds:Signature xmlns:ds=http://www.w3.org/2000/09/xmldsig#;
 Id=Signature-28340672
 ds:SignedInfo
 ds:CanonicalizationMethod Algorithm=
 http://www.w3.org/2001/10/xml-exc-c14n#; /
 ds:SignatureMethod Algorithm=
 http://www.w3.org/2000/09/xmldsig#rsa-sha1; /
 ds:Reference URI=#id-1283730842
 ds:Transforms
 ds:Transform Algorithm=
 http://www.w3.org/2001/10/xml-exc-c14n#; /
 /ds:Transforms
 ds:DigestMethod Algorithm=
 http://www.w3.org/2000/09/xmldsig#sha1; /
 ds:DigestValue
 /* Some digest */
 /ds:DigestValue
 /ds:Reference
 /ds:SignedInfo
 ds:SignatureValue
 /* Sign value */
 /ds:SignatureValue
 ds:KeyInfo Id=KeyId-1727788317
 wsse:SecurityTokenReference xmlns:wsu=
 http://schemas.xmlsoap.org/ws/2002/07/utility;
 wsu:Id=STRId-664369085
 wsse:Reference URI=#CertId-36765048
 ValueType=wsse:X509v3 /
 /wsse:SecurityTokenReference
 /ds:KeyInfo
 /ds:Signature
 wsu:Timestamp xmlns:wsu=
 http://schemas.xmlsoap.org/ws/2002/07/utility;
 wsu:Id=Timestamp-1735528613
 wsu:Created2010-02-06T02:52:19.946Z/wsu:Created
 /wsu:Timestamp
 /wsse:Security
 messageHeader xmlns=
 http://www.uc-council.org/smp/schemas/eanucc;
 soapenv:mustUnderstand=0
 /* Message header */
 /messageHeader
 /soapenv:Header
 soapenv:Body xmlns:wsu=
 http://schemas.xmlsoap.org/ws/2002/07/utility; wsu:Id=id-1283730842
 /* Body */
 /soapenv:Body
 /soapenv:Envelope

 And on the other machine, the same code change the namespaces from
 http://schemas.xmlsoap.org/* to http://docs.oasis-open.org/* and
 doesn't work with our server:

 ?xml version='1.0' encoding='utf-8'?
 soapenv:Envelope xmlns:soapenv=
 http://schemas.xmlsoap.org/soap/envelope/;
 soapenv:Header
 wsse:Security xmlns:wsse=
 http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd;
 soapenv:mustUnderstand=1
 wsse:BinarySecurityToken xmlns:wsu=
 http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
 EncodingType=wsse:Base64Binary ValueType=wsse:X509v3
 wsu:Id=CertId-36765048
 /* Secure message */
 /wsse:BinarySecurityToken
 ds:Signature xmlns:ds=http://www.w3.org/2000/09/xmldsig#;
 Id=Signature-1809025927
 ds:SignedInfo
 ds:CanonicalizationMethod Algorithm=
 http://www.w3.org/2001/10/xml-exc-c14n#; /
 ds:SignatureMethod Algorithm=
 http://www.w3.org/2000/09/xmldsig#rsa-sha1; /
 ds:Reference URI=#id-47973429
 ds:Transforms
 ds:Transform Algorithm=
 http://www.w3.org/2001/10/xml-exc-c14n#; /
 /ds:Transforms
 ds:DigestMethod Algorithm=
 http://www.w3.org/2000/09/xmldsig#sha1; /
 ds:DigestValue
 /* Some digest */
 /ds:DigestValue
 /ds:Reference
 /ds:SignedInfo
 ds:SignatureValue
 /* Sign value */
 /ds:SignatureValue
 

Re: Initializing Web Service (Server) before first request received

[sri ram]

If you are using Tomcat as your webserver.
then you can configureit  in the web.xml .
To initialize a servlet on start up add this in the web.xml
load-on-startup1/load-on-startup..



-Sriram





From: Oded Onn oded@mobixell.com
To: axis-user@ws.apache.org
Sent: Tue, 9 February, 2010 7:56:48 PM
Subject: Initializing Web Service (Server) before first request received

 
Hi all,
 
I am deploying an AXIS2 web service (server side). 
 
My problem: The skeleton class (the one that performs all
the business logic) is read for the first time only when the first request is 
received
by the server. It means that the first response takes a really long time (up to
20 seconds on a weak machine) since there are a lot of initialization I have to
perform (static init).
 
Solution: I am assuming I can write some sort of a main
class that will try to call the skeleton class. This is not only ugly but also
prone to all sorts of errors. Is there a proper way to init my service class? I
would expect some mechanism to be used, such as utilizing the servlet init of
the axis servlet.
 
Anyone? Thanks!
Oded


  The INTERNET now has a personality. YOURS! See your Yahoo! Homepage. 
http://in.yahoo.com/

Re: Axis - javascript

[Demetris]

I will do so - thanks Amila.

Amila Suriarachchi wrote:



On Sat, Feb 6, 2010 at 12:41 AM, Demetris demet...@ece.neu.edu 
mailto:demet...@ece.neu.edu wrote:



Does anyone know any tool that can either generate javascript code
from wsdl documents or
any examples of how a remote client can use the wsdl file to build
soap calls within javascript
that can access an Axis remote service. In other words my goal
here is to avoid generating
and compiling the stubs.


please have a look at here[1]. WSO2 Mashup server allows you to 
develop web services using javascript.

and generate the code as well.

thanks,
Amila.

[1] http://wso2.org/downloads/mashup


Thanks




--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Re: Initializing Web Service (Server) before first request received

[Deepal Jayasinghe]

Deploy there service in Application scope.

Thanks,
Deepal

 Hi all,

  

 I am deploying an AXIS2 web service (server side).

  

 My problem: The skeleton class (the one that performs all the business
 logic) is read for the first time only when the first request is
 received by the server. It means that the first response takes a
 really long time (up to 20 seconds on a weak machine) since there are
 a lot of initialization I have to perform (static init).

  

 Solution: I am assuming I can write some sort of a main class that
 will try to call the skeleton class. This is not only ugly but also
 prone to all sorts of errors. Is there a proper way to init my service
 class? I would expect some mechanism to be used, such as utilizing the
 servlet init of the axis servlet.

  

 Anyone? Thanks!

 Oded


-- 
Thank you!


http://blogs.deepal.org
http://deepal.org

Re: Location to call getCurrentMessageContext

[Deepal jayasinghe]

First get the service client instance, and then call the following
method to get the OperationContext, once you have operation context you
have access to both in and out messages contexts.

getLastOperationContext

Thanks,
Deepal

 Dear all,

  

 From within a webservice that runs on Axis2, I need to access some
 soap header information (the wsse:BinarySecurityToken to be exact, I
 need to find out which certificate was passed for client authentication).

  

 Application architecture: I am running Intalio BPMS, which is Apache
 ODE that seems to auto-create a webservice and its WSDL on Axis2
 (without programming on my side). This runs on Tomcat.

  

 I do not have access to the code generated by ODE or to the
 integration between ODE and Axis2 (I think…) but I can place a JAR in
 ODE’s classpath. Any (static) functions within that JAR are
 automatically visible to ODE.

 In other words, I can for instance define a jar with a static function
 f that accepts as input one of my wsdl parameters and outputs
 something that can be used in following steps of the ODE-managed process.

 So far so good, no problems there since I’ve remained within the realm
 of the data sent as input to the WSDL (i.e. only parameters from
 inside the soap:body that are automatically available).

  

 Now as mentioned I need to access the soap:header and there I’ve got a
 problem since the bpel layer is happily unaware of the existence of
 such a thing as the soap:header.

 After some googling I started to think that my best bet was to add a
 jar/function in ode’s classpath and to call
 MessageContext.getCurrentMessageContext() from there (am I correct in
 assuming this or is there a better alternative?).

 Unfortunately my first attempt stranded with a null coming back from
 it. All functions are accessible/callable and also have the Axis2
 jar’s in the same classpath directory so that should be ok. My guess
 is I’m in a different thread or context due to placing it in a
 separate jar maybe but how do I find out if this is true? And how can
 I access another thread’s information if this is the problem? The
 entire process spans a single (synchronous) soap request/response
 dialog so I guess there should be a message context somewhere (as the
 request comes in before the call to my new jar and the response is
 sent out after the call to it).

  

 Any help or pointers is more than appreciated,

  

 Best,

  

 Christian C. Schouten

  

  



-- 
Thank you!


http://blogs.deepal.org
http://deepal.org

Re: Inaccessible WSDL files after enabling both HTTP and HTTPS in Axis2/Tomcat

[Andreas Veithen]

Michael,

This looks like another example of the issue described in AXIS2-4465.
Not sure if it is possible to make this work properly in 1.5.1, but in
the current trunk the configuration mechanism to enable HTTP and HTTPS
in a servlet environment is much more transparent (and known to work
properly).

Andreas

[1] http://people.apache.org/~veithen/axis2/1_6/servlet-transport.html

On Mon, Feb 8, 2010 at 14:10, Doughty, Michael michael_doug...@bmc.com wrote:
 I have a problem that I am hoping someone could shed some light on.



 I have enabled both HTTP and one-way HTTPS in my Tomcat 6 instance.
 Likewise, I have added the correct configuration information to my axis2.xml
 in the war distribution of Axis2 1.5.1.  The HTTP port is 8080 and the HTTPS
 port is 8443.  They are running on a 1.5 JRE.



 Doing so seems to work ok.  The Web services are all accessible at both the
 HTTP and HTTPS endpoints, so there seems to be no real issue there.
 However, the WSDL and XSD files are inaccessible.  The same endpoints that
 allow SOAP requests no longer allow any of these “GET” requests to access
 WSDL and XSD files:  “?wsdl”, “?wsdl=somefile.wsdl”, “?xsd=somefile.xsd”.
 In all cases, I get the message “Internal server error”.  This happens
 whether or not I use the HTTP or HTTPS endpoints to access them.  Note that
 I can  still access these files directly by simply adding “/somefile.wsdl”
 to the end of the endpoint, but this is undesirable in the case of the main
 WSDL of the service as the service endpoints are not replaced properly.



 Note that this happens whether or not I explicitly declare the available
 transports in services.xml for the services in question.  I found a FAQ
 somewhere that said I needed to make sure that xalan-2.7.0.jar was copied
 into the lib directory of the war distribution, but that file is already
 there.



 Is there something else I need to do here to make this work?  Or is this a
 known issue that cannot be worked around at this time?

Re: Axis - javascript

[Demetris]

Hi again,

any idea on the question below? I want to avoid generating stubs on the 
client side (even though
I do have the WSDL file) but rather generate the SOAP message directly. 
Is there a tool that

can generate that or at least and automated method for it?

Thanks

Demetris wrote:


Does anyone know any tool that can either generate javascript code 
from wsdl documents or
any examples of how a remote client can use the wsdl file to build 
soap calls within javascript
that can access an Axis remote service. In other words my goal here is 
to avoid generating

and compiling the stubs.

Thanks

Re: [Axis2] - Error setting SOAP 1.1

[Amila Suriarachchi]

On Tue, Feb 9, 2010 at 2:26 AM, Juan Felipe Alvarez Saldarriaga 
nebi...@gmail.com wrote:

 Hey!.

 I got some question about Axis2, in one machine when I create a request
 using Axis2 it creates this request:

 ?xml version='1.0' encoding='utf-8'?
 soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/
 
 soapenv:Header
 wsse:Security xmlns:wsse=
 http://schemas.xmlsoap.org/ws/2002/07/secext; soapenv:mustUnderstand=1
 wsse:BinarySecurityToken xmlns:wsu=
 http://schemas.xmlsoap.org/ws/2002/07/utility;
 EncodingType=wsse:Base64Binary ValueType=wsse:X509v3
 wsu:Id=CertId-36765048
 /* Secure message */
 /wsse:BinarySecurityToken
 ds:Signature xmlns:ds=http://www.w3.org/2000/09/xmldsig#;
 Id=Signature-28340672
 ds:SignedInfo
 ds:CanonicalizationMethod Algorithm=
 http://www.w3.org/2001/10/xml-exc-c14n#; /
 ds:SignatureMethod Algorithm=
 http://www.w3.org/2000/09/xmldsig#rsa-sha1; /
 ds:Reference URI=#id-1283730842
 ds:Transforms
 ds:Transform Algorithm=
 http://www.w3.org/2001/10/xml-exc-c14n#; /
 /ds:Transforms
 ds:DigestMethod Algorithm=
 http://www.w3.org/2000/09/xmldsig#sha1; /
 ds:DigestValue
 /* Some digest */
 /ds:DigestValue
 /ds:Reference
 /ds:SignedInfo
 ds:SignatureValue
 /* Sign value */
 /ds:SignatureValue
 ds:KeyInfo Id=KeyId-1727788317
 wsse:SecurityTokenReference xmlns:wsu=
 http://schemas.xmlsoap.org/ws/2002/07/utility; wsu:Id=STRId-664369085
 wsse:Reference URI=#CertId-36765048
 ValueType=wsse:X509v3 /
 /wsse:SecurityTokenReference
 /ds:KeyInfo
 /ds:Signature
 wsu:Timestamp xmlns:wsu=
 http://schemas.xmlsoap.org/ws/2002/07/utility;
 wsu:Id=Timestamp-1735528613
 wsu:Created2010-02-06T02:52:19.946Z/wsu:Created
 /wsu:Timestamp
 /wsse:Security
 messageHeader xmlns=http://www.uc-council.org/smp/schemas/eanucc;
 soapenv:mustUnderstand=0
 /* Message header */
 /messageHeader
 /soapenv:Header
 soapenv:Body xmlns:wsu=http://schemas.xmlsoap.org/ws/2002/07/utility;
 wsu:Id=id-1283730842
 /* Body */
 /soapenv:Body
 /soapenv:Envelope

 And on the other machine, the same code change the namespaces from
 http://schemas.xmlsoap.org/* to http://docs.oasis-open.org/* and doesn't
 work with our server:

 ?xml version='1.0' encoding='utf-8'?
 soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/
 
 soapenv:Header
 wsse:Security xmlns:wsse=
 http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd;
 soapenv:mustUnderstand=1
 wsse:BinarySecurityToken xmlns:wsu=
 http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
 EncodingType=wsse:Base64Binary ValueType=wsse:X509v3
 wsu:Id=CertId-36765048
 /* Secure message */
 /wsse:BinarySecurityToken
 ds:Signature xmlns:ds=http://www.w3.org/2000/09/xmldsig#;
 Id=Signature-1809025927
 ds:SignedInfo
 ds:CanonicalizationMethod Algorithm=
 http://www.w3.org/2001/10/xml-exc-c14n#; /
 ds:SignatureMethod Algorithm=
 http://www.w3.org/2000/09/xmldsig#rsa-sha1; /
 ds:Reference URI=#id-47973429
 ds:Transforms
 ds:Transform Algorithm=
 http://www.w3.org/2001/10/xml-exc-c14n#; /
 /ds:Transforms
 ds:DigestMethod Algorithm=
 http://www.w3.org/2000/09/xmldsig#sha1; /
 ds:DigestValue
 /* Some digest */
 /ds:DigestValue
 /ds:Reference
 /ds:SignedInfo
 ds:SignatureValue
 /* Sign value */
 /ds:SignatureValue
 ds:KeyInfo Id=KeyId-923425825
 wsse:SecurityTokenReference xmlns:wsu=
 http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
 wsu:Id=STRId-1148428095
 wsse:Reference URI=#CertId-36765048
 ValueType=wsse:X509v3 /
 /wsse:SecurityTokenReference
 /ds:KeyInfo
 /ds:Signature
 wsu:Timestamp xmlns:wsu=
 http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
 wsu:Id=Timestamp-1179468258
 wsu:Created2010-02-08T15:08:55.749Z/wsu:Created
 /wsu:Timestamp
 /wsse:Security
 messageHeader xmlns=http://www.uc-council.org/smp/schemas/eanucc;
 soapenv:mustUnderstand=0
 /* Message header */
 /messageHeader
 /soapenv:Header
 soapenv:Body xmlns:wsu=
 

Re: Axis - javascript

[Amila Suriarachchi]

On Sat, Feb 6, 2010 at 12:41 AM, Demetris demet...@ece.neu.edu wrote:


 Does anyone know any tool that can either generate javascript code from
 wsdl documents or
 any examples of how a remote client can use the wsdl file to build soap
 calls within javascript
 that can access an Axis remote service. In other words my goal here is to
 avoid generating
 and compiling the stubs.


please have a look at here[1]. WSO2 Mashup server allows you to develop web
services using javascript.
and generate the code as well.

thanks,
Amila.

[1] http://wso2.org/downloads/mashup


 Thanks




-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Re: [Axis2] - Error setting SOAP 1.1

[Juan Felipe Alvarez Saldarriaga]

Hey Amila.

Thanks for asking, yes, same libraries in both servers, I just copy those
from one server to the other, pretty odd eh?

Thanks.

On Mon, Feb 8, 2010 at 10:07 PM, Amila Suriarachchi 
amilasuriarach...@gmail.com wrote:



 On Tue, Feb 9, 2010 at 2:26 AM, Juan Felipe Alvarez Saldarriaga 
 nebi...@gmail.com wrote:

 Hey!.

 I got some question about Axis2, in one machine when I create a request
 using Axis2 it creates this request:

 ?xml version='1.0' encoding='utf-8'?
 soapenv:Envelope xmlns:soapenv=
 http://schemas.xmlsoap.org/soap/envelope/;
 soapenv:Header
 wsse:Security xmlns:wsse=
 http://schemas.xmlsoap.org/ws/2002/07/secext; soapenv:mustUnderstand=1
 wsse:BinarySecurityToken xmlns:wsu=
 http://schemas.xmlsoap.org/ws/2002/07/utility;
 EncodingType=wsse:Base64Binary ValueType=wsse:X509v3
 wsu:Id=CertId-36765048
 /* Secure message */
 /wsse:BinarySecurityToken
 ds:Signature xmlns:ds=http://www.w3.org/2000/09/xmldsig#;
 Id=Signature-28340672
 ds:SignedInfo
 ds:CanonicalizationMethod Algorithm=
 http://www.w3.org/2001/10/xml-exc-c14n#; /
 ds:SignatureMethod Algorithm=
 http://www.w3.org/2000/09/xmldsig#rsa-sha1; /
 ds:Reference URI=#id-1283730842
 ds:Transforms
 ds:Transform Algorithm=
 http://www.w3.org/2001/10/xml-exc-c14n#; /
 /ds:Transforms
 ds:DigestMethod Algorithm=
 http://www.w3.org/2000/09/xmldsig#sha1; /
 ds:DigestValue
 /* Some digest */
 /ds:DigestValue
 /ds:Reference
 /ds:SignedInfo
 ds:SignatureValue
 /* Sign value */
 /ds:SignatureValue
 ds:KeyInfo Id=KeyId-1727788317
 wsse:SecurityTokenReference xmlns:wsu=
 http://schemas.xmlsoap.org/ws/2002/07/utility; wsu:Id=STRId-664369085
 wsse:Reference URI=#CertId-36765048
 ValueType=wsse:X509v3 /
 /wsse:SecurityTokenReference
 /ds:KeyInfo
 /ds:Signature
 wsu:Timestamp xmlns:wsu=
 http://schemas.xmlsoap.org/ws/2002/07/utility;
 wsu:Id=Timestamp-1735528613
 wsu:Created2010-02-06T02:52:19.946Z/wsu:Created
 /wsu:Timestamp
 /wsse:Security
 messageHeader xmlns=
 http://www.uc-council.org/smp/schemas/eanucc; soapenv:mustUnderstand=0
 /* Message header */
 /messageHeader
 /soapenv:Header
 soapenv:Body xmlns:wsu=
 http://schemas.xmlsoap.org/ws/2002/07/utility; wsu:Id=id-1283730842
 /* Body */
 /soapenv:Body
 /soapenv:Envelope

 And on the other machine, the same code change the namespaces from
 http://schemas.xmlsoap.org/* to http://docs.oasis-open.org/* and doesn't
 work with our server:

 ?xml version='1.0' encoding='utf-8'?
 soapenv:Envelope xmlns:soapenv=
 http://schemas.xmlsoap.org/soap/envelope/;
 soapenv:Header
 wsse:Security xmlns:wsse=
 http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd;
 soapenv:mustUnderstand=1
 wsse:BinarySecurityToken xmlns:wsu=
 http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
 EncodingType=wsse:Base64Binary ValueType=wsse:X509v3
 wsu:Id=CertId-36765048
 /* Secure message */
 /wsse:BinarySecurityToken
 ds:Signature xmlns:ds=http://www.w3.org/2000/09/xmldsig#;
 Id=Signature-1809025927
 ds:SignedInfo
 ds:CanonicalizationMethod Algorithm=
 http://www.w3.org/2001/10/xml-exc-c14n#; /
 ds:SignatureMethod Algorithm=
 http://www.w3.org/2000/09/xmldsig#rsa-sha1; /
 ds:Reference URI=#id-47973429
 ds:Transforms
 ds:Transform Algorithm=
 http://www.w3.org/2001/10/xml-exc-c14n#; /
 /ds:Transforms
 ds:DigestMethod Algorithm=
 http://www.w3.org/2000/09/xmldsig#sha1; /
 ds:DigestValue
 /* Some digest */
 /ds:DigestValue
 /ds:Reference
 /ds:SignedInfo
 ds:SignatureValue
 /* Sign value */
 /ds:SignatureValue
 ds:KeyInfo Id=KeyId-923425825
 wsse:SecurityTokenReference xmlns:wsu=
 http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
 wsu:Id=STRId-1148428095
 wsse:Reference URI=#CertId-36765048
 ValueType=wsse:X509v3 /
 /wsse:SecurityTokenReference
 /ds:KeyInfo
 /ds:Signature
 wsu:Timestamp xmlns:wsu=
 http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
 wsu:Id=Timestamp-1179468258
 wsu:Created2010-02-08T15:08:55.749Z/wsu:Created

RE: Inaccessible WSDL files after enabling both HTTP and HTTPS in Axis2/Tomcat

[Doughty, Michael]

Thanks for the information.  I am glad to hear it is fixed in the main trunk, 
which I hope means it will make it into the next version of Axis2.

For the time being I've implemented my own logic to create these files at 
deployment time by modifying the original WSDL file to contain the policy 
reference, the policy statements, and the modified service endpoint.  They will 
just have to be accessible for now from the 
http(s)://host:port/axis2/services/service/service.wsdl format.

-Original Message-
From: Andreas Veithen [mailto:andreas.veit...@gmail.com] 
Sent: Monday, February 08, 2010 8:44 AM
To: axis-user@ws.apache.org
Subject: Re: Inaccessible WSDL files after enabling both HTTP and HTTPS in 
Axis2/Tomcat

Michael,

This looks like another example of the issue described in AXIS2-4465.
Not sure if it is possible to make this work properly in 1.5.1, but in
the current trunk the configuration mechanism to enable HTTP and HTTPS
in a servlet environment is much more transparent (and known to work
properly).

Andreas

[1] http://people.apache.org/~veithen/axis2/1_6/servlet-transport.html

On Mon, Feb 8, 2010 at 14:10, Doughty, Michael michael_doug...@bmc.com wrote:
 I have a problem that I am hoping someone could shed some light on.



 I have enabled both HTTP and one-way HTTPS in my Tomcat 6 instance.
 Likewise, I have added the correct configuration information to my axis2.xml
 in the war distribution of Axis2 1.5.1.  The HTTP port is 8080 and the HTTPS
 port is 8443.  They are running on a 1.5 JRE.



 Doing so seems to work ok.  The Web services are all accessible at both the
 HTTP and HTTPS endpoints, so there seems to be no real issue there.
 However, the WSDL and XSD files are inaccessible.  The same endpoints that
 allow SOAP requests no longer allow any of these GET requests to access
 WSDL and XSD files:  ?wsdl, ?wsdl=somefile.wsdl, ?xsd=somefile.xsd.
 In all cases, I get the message Internal server error.  This happens
 whether or not I use the HTTP or HTTPS endpoints to access them.  Note that
 I can  still access these files directly by simply adding /somefile.wsdl
 to the end of the endpoint, but this is undesirable in the case of the main
 WSDL of the service as the service endpoints are not replaced properly.



 Note that this happens whether or not I explicitly declare the available
 transports in services.xml for the services in question.  I found a FAQ
 somewhere that said I needed to make sure that xalan-2.7.0.jar was copied
 into the lib directory of the war distribution, but that file is already
 there.



 Is there something else I need to do here to make this work?  Or is this a
 known issue that cannot be worked around at this time?

Re: Preventing Axis2/Rampart from encrypting faults

[Amila Suriarachchi]

On Mon, Feb 8, 2010 at 7:25 AM, Doughty, Michael michael_doug...@bmc.comwrote:

  We’ve rewritten several of our services from another Web services stack
 to Axis2 1.5.1.  We are using Rampart 1.4 to handle the WS-Security 1.0
 functionality from our previous services.



 There have been a few differences though and I am unable to resolve some of
 them.  The most important one right now is in the fault messages being sent
 from the service.



 In our previous implementation, Fault messages were never signed and
 encrypted.  However, in this Axis2 version they are always signed and
 encrypted.  I’ve tried a few things I’ve seen from Google searches to see if
 I can prevent this.  One of them was to remove the security phase from the
 OutFaultFlow section of the axis2.xml file in the WEB-INF/conf directory.
 However, this causes the Axis2 bundle to fail to load properly.



 Is there any way to prevent the faults from being signed and encrypted
 while still allowing the standard outbound messages to be signed and
 encrypted?


you can unpack the rampart.mar file and edit the module.xml file so that no
handlers goes to outFaultFlow. Then recreate the mar file. This won't create
any problem when loading modules.

thanks,
Amila.




-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

RE: Preventing Axis2/Rampart from encrypting faults

[Doughty, Michael]

That seems to have worked.  Thanks very much for your help.

From: Amila Suriarachchi [mailto:amilasuriarach...@gmail.com]
Sent: Sunday, February 07, 2010 9:46 PM
To: axis-user@ws.apache.org
Subject: Re: Preventing Axis2/Rampart from encrypting faults


On Mon, Feb 8, 2010 at 7:25 AM, Doughty, Michael 
michael_doug...@bmc.commailto:michael_doug...@bmc.com wrote:
We've rewritten several of our services from another Web services stack to 
Axis2 1.5.1.  We are using Rampart 1.4 to handle the WS-Security 1.0 
functionality from our previous services.

There have been a few differences though and I am unable to resolve some of 
them.  The most important one right now is in the fault messages being sent 
from the service.

In our previous implementation, Fault messages were never signed and encrypted. 
 However, in this Axis2 version they are always signed and encrypted.  I've 
tried a few things I've seen from Google searches to see if I can prevent this. 
 One of them was to remove the security phase from the OutFaultFlow section of 
the axis2.xml file in the WEB-INF/conf directory.  However, this causes the 
Axis2 bundle to fail to load properly.

Is there any way to prevent the faults from being signed and encrypted while 
still allowing the standard outbound messages to be signed and encrypted?

you can unpack the rampart.mar file and edit the module.xml file so that no 
handlers goes to outFaultFlow. Then recreate the mar file. This won't create 
any problem when loading modules.

thanks,
Amila.




--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Re: Axis2/C and client side SWA attachments

[Michael Huffman]

How about Axis2/Java or Axis2/C++?  What are my options if I need to
support SwA attachments, but still want to stay with the Axis project?

--Mike.

On Fri, Feb 5, 2010 at 1:24 AM, Samisa Abeysinghe sam...@wso2.com wrote:
 Axis2/C does not support SWA, but MTOM only.
 Samisa...

 On Fri, Feb 5, 2010 at 2:29 AM, Michael Huffman michael.mhuff...@gmail.com
 wrote:

 I've been searching for an example of sending SwA attachments via Axis2/C.

 I've seen examples in Axis2/Java, but I'm a little lost as to how to
 accomplish the same in Axis2/C.  Can someone please point me in a
 direction?

 Thanks in advance,
 --Mike.



 --
 Samisa Abeysinghe
 Director, Engineering - WSO2 Inc.

 http://wso2.com/ - lean . enterprise . middleware

Re: Axis2/C and client side SWA attachments

[Samisa Abeysinghe]

You can use Axis2/Java.

Samisa...

On Sat, Feb 6, 2010 at 1:05 AM, Michael Huffman
michael.mhuff...@gmail.comwrote:

 How about Axis2/Java or Axis2/C++?  What are my options if I need to
 support SwA attachments, but still want to stay with the Axis project?

 --Mike.

 On Fri, Feb 5, 2010 at 1:24 AM, Samisa Abeysinghe sam...@wso2.com wrote:
  Axis2/C does not support SWA, but MTOM only.
  Samisa...
 
  On Fri, Feb 5, 2010 at 2:29 AM, Michael Huffman 
 michael.mhuff...@gmail.com
  wrote:
 
  I've been searching for an example of sending SwA attachments via
 Axis2/C.
 
  I've seen examples in Axis2/Java, but I'm a little lost as to how to
  accomplish the same in Axis2/C.  Can someone please point me in a
  direction?
 
  Thanks in advance,
  --Mike.
 
 
 
  --
  Samisa Abeysinghe
  Director, Engineering - WSO2 Inc.
 
  http://wso2.com/ - lean . enterprise . middleware
 




-- 
Samisa Abeysinghe
Director, Engineering - WSO2 Inc.

http://wso2.com/ - lean . enterprise . middleware

Re: Axis2/C and client side SWA attachments

[Samisa Abeysinghe]

Axis2/C does not support SWA, but MTOM only.

Samisa...

On Fri, Feb 5, 2010 at 2:29 AM, Michael Huffman
michael.mhuff...@gmail.comwrote:

 I've been searching for an example of sending SwA attachments via Axis2/C.

 I've seen examples in Axis2/Java, but I'm a little lost as to how to
 accomplish the same in Axis2/C.  Can someone please point me in a
 direction?

 Thanks in advance,
 --Mike.




-- 
Samisa Abeysinghe
Director, Engineering - WSO2 Inc.

http://wso2.com/ - lean . enterprise . middleware

Re: Invalid services.xml found

[Giacomo Petronio]

Il 04/02/2010 11:34, Valerio Synclab ha scritto:


Hi all,

...

Any suggestion ?

Best regards

Valerio Vianello


Try with service instead of services tag

Re: How to debug TypeMapping problem?

[Brian K]

I'm having the exact same problem.  I have a field of type object and if it
is a string, Axis serializes it as a guid and then the server cannot parse
the request because it's not a guid.  

-- 
View this message in context: 
http://old.nabble.com/How-to-debug-TypeMapping-problem--tp27308436p27461242.html
Sent from the Axis - User mailing list archive at Nabble.com.

Re: xml payload

[Amila Suriarachchi]

On Fri, Feb 5, 2010 at 12:29 AM, Joe White joe.wh...@eyefinity.com wrote:

  I’m calling a SOAP service and one of the input methods is a String
 object.

 The problem I’m having is that this String object, is actually an xml
 document.

 When Axis attempts to send to payload, it’s encoding all of the special
 characters IE xml version=”1.0” encoding=”UTF-8” etc..

 Is being send over encoded. lt;?xml version=quot;1.0quot;
 encoding=quot;UTF-8quot;?gt;


In fact this is the correct way to do it. if you use Axis2 try to build an
Axiom Object from the string and attached it.

thanks,
Amila.



 How can I tell the Apache Engine to NOT encode this? The server I’m talking
 to is having issues ciphering the data because of this.







 MailGate.vsp.com made the following annotations
 -
 NOTICE: This message is intended only for the individual to whom it is
 addressed and may contain information that is confidential or privileged. If
 you are not the intended recipient, or the employee or person responsible
 for delivering it to the intended recipient, you are hereby notified that
 any dissemination, distribution, copying or use is strictly prohibited. If
 you have received this communication in error, please notify the sender and
 destroy or delete this communication immediately.
 -




-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Re: help needed building axis2 using NetBeans 6.8 and maven 2.2.1

[Andreas Veithen]

On Tue, Feb 2, 2010 at 10:06, Stadelmann Josef
josef.stadelm...@axa-winterthur.ch wrote:
 Andreas,

 Summary:

 Builds using MAVEN 2.2.1
 Source Code used,
 Cmd window              NetBeans IDE 6.8                        Maven
 Flags
 downloaded by SVN Tortoise                                      Maven
 2.2.1           external Maven 2.2.1

 Ant 1.7.0               external Ant 1.7.0

 C:\asf\webservices\axis2\tags\java\v1.5.1               fails
 fails                                   -Dmave.test.skip=true
 C:\asf\webservices\axis2\tags\java\v1.5.1               success
 success                         .NA.

 C:\asf\webservices\axis2\trunk\java                             success
 success                         -Dmave.test.skip=true
 C:\asf\webservices\axis2\trunk\java                             success
 success                         .NA.

 Builds using MAVEN 3.0-SNAPSHOT                         AXIS2 is not yet
 maven 3.0-Snapshot ready!

 If you have NetBeans IDE 6.8 with the internal or external maven
 3.0-snapshot then you are unable to open the axis2 root POM correctly.
 However one is  still able to build some off the axis2
 components/artifacts correctly. In short AXIS2 Trunk sources and earlier
 are not yet ready for MAVEN 3.0-SNAPSHOT!

 Josef

Maven 3.0 (alpha-6) actually works surprisingly well on the Axis2
build. There are only two issues:

- A duplicate dependency declaration in the integration module; this
is now fixed.

- The root POM has an antrun execution that depends on the output of
several of its sub-modules by directly accessing
modules/xxx/target/classes, but no provisions are made to make sure
that these modules are built before the antrun execution. Depending on
the output of other modules in that way is bad practice, and leads to
unstable/unpredictable build. With Maven 2.0 the build order is such
that it works correctly, but this is probably more a coincidence. We
will probably have to use some maven-assembly-plugin magic to do this
correctly and to make the build order predictable.

Andreas

Re: doc/literal style and wsdl:part combination

[rahul yadav]

one more query on standards

Can we have multipart messages in wsdl of doc/lit type? As per my
understanding for multipart messages wsdl should be of rpc/enc type.

If answer for above query is yes...then i have seen some wsdls with
multipart messages following doc/lit style, these wsdls are
consumed(wsdl2java) well by .net and Axis1.4 but fails with Axis2. how Can
we justify this ?

Thanks  Regards,
Rahul Yadav

Can we have multipart messages in

Following wsdl has multipart messages and is doc/lit type, Axis2 does
not support multipart messages in doc/lit wsdl, it has to be a rpc/enc
wsdl.



On Tue, Feb 2, 2010 at 10:39 AM, Amila Suriarachchi 
amilasuriarach...@gmail.com wrote:



 On Mon, Feb 1, 2010 at 11:05 PM, rahul yadav rahulyada...@gmail.comwrote:

 Hi All,

 Will it be true to say If your WSDL is a document-literal style, then
 wsdl:part should point to an element instead of type.

 yes.
 see [1] R2204 and R2203. if it is rpc-literal the part should refer to a
 type.

 basic profile does not talk about rpc-enc

 thanks,
 Amila.


 [1] http://www.ws-i.org/Profiles/BasicProfile-1.1.html#Bindings_and_Parts

 And if WSDL is a rpc-enc style, then wsdl:part should point to type.






 --
 Amila Suriarachchi
 WSO2 Inc.
 blog: http://amilachinthaka.blogspot.com/

Re: Axis2 JAX-WS: The service class cannot be found for this AxisService

[Andreas Veithen]

Note that the portName=HelloPort in your implementation class is not
consistent with the WSDL you posted earlier. This should be
helloPort. Maybe that could be the reason. BTW, what do the logs
say?

Andreas

On Mon, Feb 1, 2010 at 23:37, Daniel Walsh walsh94...@gmail.com wrote:
 Andreas:

 The annotations generated by wsimport are:

 HelloService:

 @WebServiceClient(name = HelloService, targetNamespace = com/wb/hello,
 wsdlLocation = file:/C:/axis2-1.5.1/hello2/service/hello.wsdl)

 HelloPortType:

 @WebService(name = helloPortType, targetNamespace = com/wb/hello)
 @SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE)
 @XmlSeeAlso({
     ObjectFactory.class
 })

  HelloPort:

 @WebService(name = helloPort, targetNamespace = com/wb/hello)
 @SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE)
 @XmlSeeAlso({
     ObjectFactory.class
 })

 I'm not sure why, but based on timestamps wsimport right now isn't
 generating HelloPortType. On the other hand, it isn't referenced anywhere in
 any of the other code, so I don't know if it matters.

 Dan


 On Mon, Feb 1, 2010 at 1:51 PM, Andreas Veithen andreas.veit...@gmail.com
 wrote:

 Can you show me the annotations on HelloService, HelloPortType and
 HelloPort?

 Andreas

 On Mon, Feb 1, 2010 at 21:12, Daniel Walsh walsh94...@gmail.com wrote:
  Andreas,
 
  I annotated my service class per your example and I am still getting the
  No
  annotated classes found in the jar message when I click on the link
 
  Faulty Services
 
  c:\tomcat-6.0.20\webapps\axis2\WEB-INF\servicejars\HelloService.jar
 
  on the list services page at
  http://localhost:8080/axis2/services/listServices;
 
  My annotated implementation class, HelloPortImpl, is pretty simple:
 
  package com.wb.hello;
 
  import java.io.PrintStream;
 
  import javax.jws.WebMethod;
  import javax.jws.WebParam;
  import javax.jws.WebResult;
  import javax.jws.WebService;
  import javax.jws.soap.SOAPBinding;
  import javax.xml.bind.annotation.XmlSeeAlso;
 
  @WebService(endpointInterface = com.wb.hello.HelloPort,
      serviceName = HelloService,
      portName = HelloPort,
      targetNamespace = com/wb/hello,
      wsdlLocation = META-INF/hello.wsdl)
 
  public class HelloPortImpl implements HelloPort {
 
      @WebMethod
      @WebResult(name = helloResponseElement, targetNamespace =
  com/wb/hello, partName = parameters)
      public HelloResponseType hello(HelloRequestType helloRequestType) {
      HelloResponseType helloResponseType = new HelloResponseType();
      helloResponseType.setResponse(Hello  +
  helloRequestType.getRequest());
      return helloResponseType;
      }
  }
 
 
  And the class shows up in the jar file:
 
  $ jar tvf
  c:/tomcat-6.0.20/webapps/axis2/WEB-INF/servicejars/HelloService.jar
   0 Mon Feb 01 12:11:02 PST 2010 META-INF/
      71 Mon Feb 01 12:11:02 PST 2010 META-INF/MANIFEST.MF
     890 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloPort.class
    1095 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloPortImpl.class
     898 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloPortType.class
     752 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloRequestType.class
     758 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloResponseType.class
    2003 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloService.class
    1708 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/ObjectFactory.class
     230 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/package-info.class
    1804 Mon Feb 01 12:11:00 PST 2010 META-INF/hello.wsdl
     805 Mon Feb 01 12:11:00 PST 2010 META-INF/helloSchema.xsd
     296 Sat Jan 30 16:26:00 PST 2010 META-INF/service.xml
 
  If you have any thoughts as to why I can't get this thing to deploy I
  would
  sure be happy to hear them.
 
  Dan
 
 
 
  andreas.veit...@gmail.com wrote:
 
  Dan,
 
  Actually the error message should read No @WebService annotated
  service implementations found or something like that :-)
 
  In fact, you also need to annotate your service implementation with
  @WebService. Note that while this is the same annotation type than on
  the service interface (generated by wsimport), the attributes have a
  different meaning. There is an example here [1]. Note that this
  requirement is not specific to Axis2, but comes from JSR-109/181.
 
  Andreas
 
  [1]
 
  https://svn.apache.org/repos/asf/webservices/axis2/scratch/java/veithen/AXIS2-4611/jaxws-calculator-aar/src/main/java/org/apache/axis2/jaxws/calculator/impl/CalculatorImpl.java
 
  On Thu, Jan 28, 2010 at 19:46, Daniel Walsh walsh94...@gmail.com
  wrote:
   Andreas,
  
   Thanks for the tip. I would never have figured that out by myself.
  
   Unfortunately, simply moving the services/HelloService.aar file to
   servicejars/HelloServices.jar seems to have made things worse.
   Whereas
   before I saw the service listed as deployed on the listServices page
   (but
   got the exception when trying to run the client), now the service
   doesn't
   even deploy. Clicking 

Re: doc/literal style and wsdl:part combination

[Amila Suriarachchi]

On Wed, Feb 3, 2010 at 7:40 PM, rahul yadav rahulyada...@gmail.com wrote:

 one more query on standards

 Can we have multipart messages in wsdl of doc/lit type? As per my
 understanding for multipart messages wsdl should be of rpc/enc type.

 If answer for above query is yes...then i have seen some wsdls with
 multipart messages following doc/lit style, these wsdls are
 consumed(wsdl2java) well by .net and Axis1.4 but fails with Axis2. how Can
 we justify this ?


see R2210 with the same link. There can be only one soap boady child.

thanks,
Amila.


 Thanks  Regards,
 Rahul Yadav

 Can we have multipart messages in

 Following wsdl has multipart messages and is doc/lit type, Axis2 does not 
 support multipart messages in doc/lit wsdl, it has to be a rpc/enc wsdl.



 On Tue, Feb 2, 2010 at 10:39 AM, Amila Suriarachchi 
 amilasuriarach...@gmail.com wrote:



 On Mon, Feb 1, 2010 at 11:05 PM, rahul yadav rahulyada...@gmail.comwrote:

 Hi All,

 Will it be true to say If your WSDL is a document-literal style, then
 wsdl:part should point to an element instead of type.

 yes.
 see [1] R2204 and R2203. if it is rpc-literal the part should refer to a
 type.

 basic profile does not talk about rpc-enc

 thanks,
 Amila.


 [1] http://www.ws-i.org/Profiles/BasicProfile-1.1.html#Bindings_and_Parts

 And if WSDL is a rpc-enc style, then wsdl:part should point to type.






 --
 Amila Suriarachchi
 WSO2 Inc.
 blog: http://amilachinthaka.blogspot.com/





-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Re: Embedding Axis2 into an existing web-app

[Amila Suriarachchi]

hi,

this[1] may help you.

thanks,
Amila.


[1] http://wso2.org/library/90

On Wed, Feb 3, 2010 at 4:55 PM, Chris Mannion
chris.mann...@icasework.comwrote:

 I Wonder if anyone can help, I'm trying to embed Axis2 into an existing
 web-app running on Tomcat 5.5 in order to server web-services from the app.
 I've done everything I can think of to do based on reading around the
 subject on various web-pages but whenever I try to hit any of the services
 I've deployed, the client program I'm using (soapUI 3.0.1) reports a
 connection refused error.  My web-app is setup as follows -

 web-app
 -- classes
 -- -- TransactionTypesWs
 -- -- -- TransactionTypes.class
 -- conf
 -- -- axis2.xml
 -- lib
 -- modules
 -- services
 -- -- TransactionTypes
 -- -- -- META-INF
 -- -- -- -- services.xml

 The axis2.xml file in conf is that version included in the Axis2 bin
 download, as are all the modules in the modules directory.  The lib
 directory contains all the jar files distributed with Axis2 and Axiom.  The
 services.xml in /service/TransactionType/META-INF reads as follows -

 ?xml version=1.0 encoding=UTF-8?
 service name=TransactionTypes
   descriptionLists the transaction type ids of any transactions submitted
 to the system in a specified date rage./description
   parameter
 name=ServiceClassTransactionTypesWs.TransactionTypes/parameter
   operation name=getTransactionTypes
 messageReceiver
 class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/
   /operation
 /service

 And refers to the class file included in the classes/TransactionTypesWs
 directory.  I'm sure I previously had this service successfully embedded
 using Axis2 but now I come to redeploy it I'm constantly hitting problems
 that I can't seem to get past.  Can anyone help or at least recommend a
 good, in depth tutorial on embedding Axis2?  I'd be very grateful, thanks.

 --
 Chris Mannion
 iCasework and LocalAlert implementation team
 0208 144 4416




-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Re: SOAP Version

[paul . deadman]

Hi 

Thanks, Ive found the underlying problem, The WSDL2C code generator has 
added an explicit statement to set the SOAP version to 1.1, so even if you 
change it to 1.2 the stub code changes it back. I just changed the stub to 
state 1.2. Im not certain if this is a bug in the WSDL2C code emitter as 
the WSDL binding states 1.2. However thanks for your thoughts.

Cheers

Paul Deadman
Mobile: 07769 930 235
Skype: Paul Deadman, York
Longfield Ltd
2 Maple House, Northminster Business Park,York,YO26 6QW

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom it is addressed. If 
you are not the intended recipient or there are problems please notify the 
sender and then delete it from your system. We have taken steps to keep 
this email and attachments free from viruses. However, we accept no 
liability for any loss or damage howsoever caused as a result of any virus 
being passed on. It is the responsibility of the recipient to perform all 
necessary checks.



Nandika Jayawardana jayaw...@gmail.com 
02/02/2010 07:46
Please respond to
Apache AXIS C User List axis-c-user@ws.apache.org


To
Apache AXIS C User List axis-c-user@ws.apache.org
cc

Subject
Re: SOAP Version






You can obtain the service client struct and from that, you can get the 
axis2 options instance associated with the stub. The set the SOAP version 
to the options. 

svc_client = axis2_stub_get_svc_client(stub, env);
options = axis2_svc_client_get_options(svc_client, env);
axis2_options_set_soap_version(options, env, AXIOM_SOAP12);

This should solve your issue.

Regards
Nandika


On Sun, Jan 31, 2010 at 5:25 AM, paul.dead...@longfield.co.uk wrote:

Hi 

I have a problem with the SOAP version, with Axis2c as a client (on XP) to 
a WCF service. The WCF Service is a wsHttpbinding with Anonymous 
authentication. (As an aside im using 1.6.0 which I downloaded 2 days ago. 
The binary version appeared to have a problem with the file seperator to 
locate the lib directory, so I took the source, change the file seperator 
in the windows specific elements to \ compiled it and it allowed it to 
load the http sender.) 

Now down to my problem:- 

1. I get the following in the log file:- 

[Sat Jan 30 23:02:06 2010] [debug] 
..\..\src\core\transport\http\sender\http_transport_sender.c(246) ctx_epr:
http://win7dev03/mexdelegation/emmdel.svc 
[Sat Jan 30 23:02:06 2010] [debug] 
..\..\src\core\transport\http\sender\http_transport_sender.c(805) using 
axis2 native http sender. 
[Sat Jan 30 23:02:06 2010] [debug] 
..\..\src\core\transport\http\sender\http_sender.c(416) 
msg_ctx_id:urn:uuid:3979014b-3c85-465b-ba42-50fa313230c0 
[Sat Jan 30 23:02:07 2010] [error] 
..\..\src\core\transport\http\sender\http_sender.c(1442) Error occurred in 
transport 
[Sat Jan 30 23:02:07 2010] [error] ..\..\src\core\engine\engine.c(179) 
Transport sender invoke failed 
[Sat Jan 30 23:02:07 2010] [error] c:\documents and settings\pdeadman\my 
documents\visual studio 
2008\projects\testaxisclient\testaxisclient\testaxisclient.cpp(92) Stub 
invoke FAILED: Error code: 74 :: Error occurred in transport 

2. I get the following from a network trace 

This is in the Content-Type: 

text/xml;charset=UTF-8 


And the following is returned:- 

HTTP/1.1 415 Cannot process the message because the content type 
'text/xml;charset=UTF-8' was not the expected type 'application/soap+xml; 
charset=utf-8'.\r\n 

3) In the code I have inserted a line 

int mysoapver = axis2_options_get_soap_version(options,env); 

Which returns a value of 2. 

Do I have to specify any specific options to force SOAP1.2 ? 

The code in question is fairly simple, I using a stub from the WSDL2C to 
create the service (named Service1 here) and then calling the method 
ConnectMEX. 
The mysoapver is returned with a value of 2. 

myservice = 
axis2_stub_create_Service1(env,client_home,endpoint_ref); 

int mysoapver = axis2_options_get_soap_version(options,env); 

// Try to force application/xml+soap 
rc=axis2_options_set_soap_version(options,env,AXIOM_SOAP12); 

adb_ConnectMEXResponse_t *response=NULL; 
adb_ConnectMEX_t *package; 
package = adb_ConnectMEX_create(env); 

response = 
axis2_stub_op_Service1_ConnectMEX(myservice,env,package); 


Im new to AXIS2C but have used other web service apps. 

Paul Deadman
Mobile: 07769 930 235
Skype: Paul Deadman, York




-- 
http://nandikajayawardana.blogspot.com/
WSO2 Inc: http://www.wso2.com

Re: axis2 configuration fine tuning: Local Transport and transportReceiver

[gshum]

I managed to configure axis2.xml with 'hostname' parameter that substitute
server part of EPR.

But I wonder is there a way to configure axis2 to use http 'host' header as
part of generated EPR? Host value should contain the server name as it 's
seen by the service consumer, which, I believe, is exactly what is desired
in the most of scenarios (BTW, that's how axis 1 handled EPR generation).
 
Thanks,
Gennady


Andreas Veithen-2 wrote:
 
 Gennady,
 
 AxisServlet will always process requests received through the servlet
 container, and the transportReceiver settings in axis2.xml have no
 impact on this. These settings are only used to generate the proper
 endpoint URIs in the WSDL (original or generated). Note that this is
 only true for the servlet transport. For other transports, the
 transportReceiver settings also determine how the transport receives
 requests.
 
 Andreas
 
 On Tue, Dec 29, 2009 at 12:16, Gennady Shumakher gshumak...@gmail.com
 wrote:
 Andreas,
 thanks for clarification.

 According to AXIS2-4465 the documentation is on its way, but I'd like to
 be
 sure we configure that properly.
 I am running on 1.5.1 and would like to support both http, https and we
 use
 useOriginalwsdl=true (so wsdl is served as is, no generation).


 As I see from the code the AxisServlet does implements TransportListener
 directly that mentioned as problematic in AXIS2-4465...

 Anyhow the current behavior I face that if no explicit transportReceiver
 defined in axis2.xml the services

 both via http and https work as expected via the ports defined for web
 application and ?wsdl returns wsdl document.

 But if axis2.xml is configured as:
 transportReceiver name=default
 class=org.apache.axis2.transport.http.AxisServlet /


 the services http/s work well, but ?wsdl request fails with null
 exception.
 Do I miss something in configuration to make it work?

 Thanks,
 Gennady


 On Mon, Dec 28, 2009 at 07:36, wrote:
 Hi,


 I am fine tuning axis2 configuration for our use cases which are
 stateless
 web services available over http(s) only. Now I wonder regarding
 relevance
 of Local Transport settings in our scenario. Unfortunately I couldn't
 fine

 the documentation on that topic, but I suppose it is optimized for calls
 within the same web application?

 The local transport is primarily used in unit tests. Not sure if it is
 usable in a production environment.


 Additionally we embed axis2 within our web application. I successfully
 tested that in this case the default transportReceiver name=http
 class=org.apache.axis2.transport.http.SimpleHTTPServer  can be
 removed
 so

 ports and other parameters are defined by web application connection.
 But
 I
 wonder how that works if I don't have any explicit configuration for
 transportReceiver, are there some defaults?


 The issue AXIS2-4465 sheds some light on how transport receivers
 are/were managed by AxisServlet.

 Thanks,
 Gennady




 
 

-- 
View this message in context: 
http://old.nabble.com/axis2-configuration-fine-tuning%3A-Local-Transport-and--transportReceiver-tp26940227p27421714.html
Sent from the Axis - User mailing list archive at Nabble.com.

Re: next release

[Andreas Veithen]

There are no plans for 1.6 yet. If there is sufficient demand, we
could do a maintenance release (1.5.2), but this would assume that the
fix for your issue could be merged to the 1.5 branch. Do you have a
reference to the JIRA or the SVN commit for that issue?

Andreas

On Tue, Feb 2, 2010 at 17:19, Larry Gilliam lgill...@innovim.com wrote:
 Hello,

 There is a bug in Axis2 1.5 affecting us (http://modis.gsfc.nasa.gov/) which 
 is fixed in the latest trunk. We'd prefer to wait until the next release to 
 deploy a new version. Is there any ETA for a
 release? It appears the last was in October and they come every few months. I 
 appreciate any info, thanks.

 -Larry Gilliam

Re: next release

[Larry Gilliam]

Andreas Veithen wrote:
 There are no plans for 1.6 yet. If there is sufficient demand, we
 could do a maintenance release (1.5.2), but this would assume that the
 fix for your issue could be merged to the 1.5 branch. Do you have a
 reference to the JIRA or the SVN commit for that issue?
 

Sorry I should have included that. Here is the issue:

http://issues.apache.org/jira/browse/AXIS2-4492

Its still marked unresolved, but the reporter is no longer on the project and I 
can verify that the issue is fixed as of SVN r894701.

A maintenance release would be sufficient for us, FWIW. Thanks again.

Re: next release

[Andreas Veithen]

Unfortunately the issue is not linked to a Subversion commit (which is
the precondition to be able to merge the fix to the 1.5 branch). Maybe
Keith or Amila have an idea where in the code this was fixed?

Andreas

On Tue, Feb 2, 2010 at 18:04, Larry Gilliam lgill...@innovim.com wrote:
 Andreas Veithen wrote:
 There are no plans for 1.6 yet. If there is sufficient demand, we
 could do a maintenance release (1.5.2), but this would assume that the
 fix for your issue could be merged to the 1.5 branch. Do you have a
 reference to the JIRA or the SVN commit for that issue?


 Sorry I should have included that. Here is the issue:

 http://issues.apache.org/jira/browse/AXIS2-4492

 Its still marked unresolved, but the reporter is no longer on the project and 
 I can verify that the issue is fixed as of SVN r894701.

 A maintenance release would be sufficient for us, FWIW. Thanks again.

Re: help needed building axis2 using NetBeans 6.8 and maven 2.2.1

[Andreas Veithen]

On Tue, Feb 2, 2010 at 10:06, Stadelmann Josef
josef.stadelm...@axa-winterthur.ch wrote:
 Andreas,

 Summary:

 Builds using MAVEN 2.2.1
 Source Code used,
 Cmd window              NetBeans IDE 6.8                        Maven
 Flags
 downloaded by SVN Tortoise                                      Maven
 2.2.1           external Maven 2.2.1

 Ant 1.7.0               external Ant 1.7.0

 C:\asf\webservices\axis2\tags\java\v1.5.1               fails
 fails                                   -Dmave.test.skip=true
 C:\asf\webservices\axis2\tags\java\v1.5.1               success
 success                         .NA.

 C:\asf\webservices\axis2\trunk\java                             success
 success                         -Dmave.test.skip=true
 C:\asf\webservices\axis2\trunk\java                             success
 success                         .NA.

 Builds using MAVEN 3.0-SNAPSHOT                         AXIS2 is not yet
 maven 3.0-Snapshot ready!

 If you have NetBeans IDE 6.8 with the internal or external maven
 3.0-snapshot then you are unable to open the axis2 root POM correctly.
 However one is  still able to build some off the axis2
 components/artifacts correctly. In short AXIS2 Trunk sources and earlier
 are not yet ready for MAVEN 3.0-SNAPSHOT!

 Josef

You are probably one of the first persons to attempt building Axis2
with Maven 3.0. Normally Maven 3.0 is meant to be a drop-in
replacement for Maven 2.x so there should be no major problems. I will
give it a try.

Andreas

RE : How to set SOAPAction header for SOAP 1.1?

[Olivier Mengué]

Thanks. My bug was really too obvious.

Olivier.

 Message d'origine
De: Doughty, Michael [mailto:michael_doug...@bmc.com]
Date: dim. 31/01/2010 07 h 28
À: Apache AXIS C User List
Objet : RE: How to set SOAPAction header for SOAP 1.1?
 
It looks like you're setting the soap action to a string pointer that you 
haven't initialized or set to the proper value.  From looking at the WSDL it 
seems like that value should be the local value get_Password, but the example 
they have on that site shows that it should be set to the qualified value 
http://www.mellbourn.com/WebServices/get_Password;.  So set the string value 
of the action to the latter of the two and rebuild.
winmail.dat

Re: SOAP Version

[Nandika Jayawardana]

You can obtain the service client struct and from that, you can get the
axis2 options instance associated with the stub. The set the SOAP version to
the options.

svc_client = axis2_stub_get_svc_client(stub, env);
options = axis2_svc_client_get_options(svc_client, env);
axis2_options_set_soap_version(options, env, AXIOM_SOAP12);

This should solve your issue.

Regards
Nandika


On Sun, Jan 31, 2010 at 5:25 AM, paul.dead...@longfield.co.uk wrote:


 Hi

 I have a problem with the SOAP version, with Axis2c as a client (on XP) to
 a WCF service. The WCF Service is a wsHttpbinding with Anonymous
 authentication. (As an aside im using 1.6.0 which I downloaded 2 days ago.
 The binary version appeared to have a problem with the file seperator to
 locate the lib directory, so I took the source, change the file seperator in
 the windows specific elements to \ compiled it and it allowed it to load
 the http sender.)

 Now down to my problem:-

 1. I get the following in the log file:-

 [Sat Jan 30 23:02:06 2010] [debug]
 ..\..\src\core\transport\http\sender\http_transport_sender.c(246) ctx_epr:
 http://win7dev03/mexdelegation/emmdel.svc
 [Sat Jan 30 23:02:06 2010] [debug]
 ..\..\src\core\transport\http\sender\http_transport_sender.c(805) using
 axis2 native http sender.
 [Sat Jan 30 23:02:06 2010] [debug]
 ..\..\src\core\transport\http\sender\http_sender.c(416)
 msg_ctx_id:urn:uuid:3979014b-3c85-465b-ba42-50fa313230c0
 [Sat Jan 30 23:02:07 2010] [error]
 ..\..\src\core\transport\http\sender\http_sender.c(1442) Error occurred in
 transport
 [Sat Jan 30 23:02:07 2010] [error] ..\..\src\core\engine\engine.c(179)
 Transport sender invoke failed
 [Sat Jan 30 23:02:07 2010] [error] c:\documents and settings\pdeadman\my
 documents\visual studio
 2008\projects\testaxisclient\testaxisclient\testaxisclient.cpp(92) Stub
 invoke FAILED: Error code: 74 :: Error occurred in transport

 2. I get the following from a network trace

 This is in the Content-Type:

 text/xml;charset=UTF-8


 And the following is returned:-

 HTTP/1.1 415 Cannot process the message because the content type
 'text/xml;charset=UTF-8' was not the expected type 'application/soap+xml;
 charset=utf-8'.\r\n

 3) In the code I have inserted a line

 int mysoapver = axis2_options_get_soap_version(options,env);

 Which returns a value of 2.

 Do I have to specify any specific options to force SOAP1.2 ?

 The code in question is fairly simple, I using a stub from the WSDL2C to
 create the service (named Service1 here) and then calling the method
 ConnectMEX.
 The mysoapver is returned with a value of 2.

 myservice =
 axis2_stub_create_Service1(env,client_home,endpoint_ref);

 int mysoapver = axis2_options_get_soap_version(options,env);

 // Try to force application/xml+soap
 rc=axis2_options_set_soap_version(options,env,AXIOM_SOAP12);

 adb_ConnectMEXResponse_t *response=NULL;
 adb_ConnectMEX_t *package;
 package = adb_ConnectMEX_create(env);

 response =
 axis2_stub_op_Service1_ConnectMEX(myservice,env,package);


 Im new to AXIS2C but have used other web service apps.

 Paul Deadman
 Mobile: 07769 930 235
 Skype: Paul Deadman, York




-- 
http://nandikajayawardana.blogspot.com/
WSO2 Inc: http://www.wso2.com

Re: unsubscribe

[Andreas Veithen]

You need to send a mail to axis-user-unsubscr...@ws.apache.org

On Mon, Feb 1, 2010 at 07:54, amardeep singh khera
amardeepsinghkh...@gmail.com wrote:

Re: unsubscribe

[Darshana Jayasinghe]

Sorry if you need to unsubscribe, you need to send the mail to this address
axis-user-unsubscr...@ws.apache.org

On Mon, Feb 1, 2010 at 7:35 PM, Amol Naidu amol.na...@rsystems.com wrote:



   Disclaimer *




 This mail, including any attachments contains confidential and privileged
 information for the sole use of the addressee(s). If you are not the
 intended recipient,

 please notify the sender by e-mail and delete the original message.  Any
 unauthorized review, use, disclosure, dissemination, forwarding, printing or
 copying of

  this email or any action taken in reliance on this e-mail is strictly
 prohibited and are unlawful. This e-mail may contain viruses. R Systems
 International Limited  has

 taken every reasonable precaution to minimize this risk.  R Systems
 International Limited is not liable for any damage you may sustain as a
 result of any virus in this e-mail.

 Before opening the e-mail or attachment, You should carry out your own
 virus checks. R Systems International Limited reserves the right to record,
 monitor, and inspect

  all email communications through its internal and external networks.  R
 Systems International Ltd prohibits its information systems from being used
 to view, store or forward

 offensive or discriminatory material.



  End of Disclaimer 




-- 
DÄrshana

Re: Use of HTTP/1.0 or 1.1 in Axis 1.4

[Chris Mannion]

Yashwanth,

Thank you, we discovered that the reason HTTP 1.1 and chunking was
being used was because a client-config.wsdd file had been altered to
use the CommonsHTTPSender rather than the default Axis HTTP handler.
This was done because some MapPoint/Virtual Earth services we connect
to require Digest/NTLM authentication which the default Axis handler
doesn't support.  However, the CommonsHTTPSender defaults to HTTP 1.1
whereas the default Axis handler defaults to HTTP 1.0, and now we're
hitting another service which doesn't seem to support either the 1.1
or chunking or both.

I'm aware that we can switch off chunking in the properties, and have
an Axis2 version of the client code which does so, however my Axis1.x
version of the code is programmed using the javax.xml.soap interfaces
rather than using Axis objects directly so I haven't worked out how to
get hold of the properties object in order to set that property.
Thanks for the help anyway, there are a few other avenues we can
explore now we know what is setting the HTTP versions.

On 28 January 2010 19:03, Yashwanth Rajaram -X (yrajaram - Zensar at
Cisco) yraja...@cisco.com wrote:
 Chris,

 Instead of that do you want to try turning off chunking?

 setProperty(HTTPConstants.CHUNKED, false);

 or

 See http://wso2.org/library/209 for info on forcing HTTP version to be
 used etc


 thanks,
 --
 Yashwanth
 These are my openion only and not that of my employer(s).

 -Original Message-
 From: Chris Mannion [mailto:chris.mann...@nonstopgov.com]
 Sent: Thursday, January 28, 2010 1:34 AM
 To: axis-user
 Subject: Use of HTTP/1.0 or 1.1 in Axis 1.4

 Hi All

 Can anybody tell me what determines which HTTP version is used when an
 Axis 1.4 client, running under Tomcat 5.5, sends an out-going request
 to a web-service?  I have two servers that are both running the same
 code and the version of the Axis 1.4 libraries connecting to an
 external web-service.  The problem arrises because the web-service
 doesn't seem to support HTTP/1.1 requests with chunked encoding and
 the HTTP headers on the out-going messages shows that one of the
 servers is sending over HTTP/1.0 and connecting successfully to the
 service while the other is sending over HTTP/1.1 with chunked encoding
 and the request fails.  I've no idea what has caused the difference
 between the two servers but, if possible, forcing the second to us
 HTTP/1.0 would solve the problem.

 Does anyone know what determines the HTTP version that the outgoing
 messages are sent over and how to set it?

 --
 Chris Mannion
 iCasework and LocalAlert implementation team
 0208 144 4416




-- 
Chris Mannion
iCasework and LocalAlert implementation team
0208 144 4416

Re: help needed building axis2 using NetBeans 6.8 and maven 2.2.1

[Andreas Veithen]

Josef,

Please see AXIS2-3290 and AXIS2-4460. This issue has been fixed
recently in the trunk.

Andreas

On Mon, Feb 1, 2010 at 16:35, Stadelmann Josef
josef.stadelm...@axa-winterthur.ch wrote:
 Hi all,

 I’ve used subversion to catch down axis2

 /trunk/java/

 /tags/java/v1.5.1

 /branches/java/v1.5

 Then I used a Vista cmd window and maven 2.2.1 to build axis2

 CD C:\asf\webservices\axis2\tags\java\v1.5.1

 C:\asf\webservices\axis2\tags\java\v1.5.1  mvn install

 And all was built perfect, greatre success, error free.

 Now I struggle with the same doing it from with NetBeans 6.8,

 using external maven 2.2.1 from the same location as done using maven from
 the vista cmd window

 C:\asf\webservices\axis2\tags\java\v1.5.1ant -version

 Apache Ant version 1.7.1 compiled on June 27 2008

 C:\asf\webservices\axis2\tags\java\v1.5.1

 It fails while building JAXWS Integration Tests

 Any ideas and hints welcome. What can I do to get my axis2 cleanly built
 using NetBeans IDE 6.8 and maven 2.2.1 ?

 I will use NB 6.8 for debugging axis2 running on a Integrity OpenVMS
 maschine under Tomcat,

 with a NetBeans IDE debugger attached to the JVM on OpenVMS.

 Regards

 Josef.Stadelmann

 @Axa-winterthur.ch

 NetBeans: Executing
 'C:\Users\C770817\SW-UMGEBUNG\apache-maven-2.2.1\bin\mvn.bat
 -Dmaven.test.skip=true -Dnetbeans.execution=true
 -Dmaven.repo.local=C:\Users\C770817\.m2\repository --errors -e clean
 install'

 NetBeans:  JAVA_HOME=C:\Program Files\JAVA\jdk1.6.0_14

 + Error stacktraces are turned on.

 Scanning for projects...

 

 Building Apache Axis2 - JAXWS Integration Tests

    task-segment: [clean, install]

 

 [clean:clean]

 Deleting directory
 C:\asf\webservices\axis2\tags\java\v1.5.1\modules\jaxws-integration\target

 [resources:resources]

 Using default encoding to copy filtered resources.

 [compiler:compile]

 No sources to compile

 [antrun:run]

 Executing tasks

     [mkdir] Created dir:
 C:\asf\webservices\axis2\tags\java\v1.5.1\modules\jaxws-integration\target\schema

     [mkdir] Created dir:
 C:\asf\webservices\axis2\tags\java\v1.5.1\modules\jaxws-integration\target\schema\src

     [mkdir] Created dir:
 C:\asf\webservices\axis2\tags\java\v1.5.1\modules\jaxws-integration\target\schema\classes

  [echo] Generating JAX-B classes from XSDs

  [echo] Generating java from soap 11

  [echo] Generating java from echo.xsd

  [echo] Generating java from stock1.xsd

  [echo] Generating java from stock2.xsd

  [echo] Generating java from samplemtom.xsd

  [echo] Generating java from greeterTypes.xsd

  [echo] Generating java from ProxyDocLitWrapped.wsdl

  [echo] Generating java from AddNumbers.wsdl

  [echo] Generating java from ProxyDocLitnonWrapped.wsdl

  [echo] Generating java from samplemtomjpeg.wsdl

  [echo] Generating java from RPCLit.wsdl

  [echo] Generating java from RPCLitSWA.wsdl

  [echo] Generating java from gorilla_dlw.wsdl

  [echo] Generating java from SOAP12Echo.wsdl

  [echo] Generating java from AddNumbersHandler.wsdl

  [echo] Generating java from async_doclitwr.wsdl

  [echo] Generating java from async_doclitwr2.wsdl

  [echo] Generating java from FaultyWebService.wsdl

  [echo] Generating java from FaultsService.wsdl

  [echo] Generating java from jaxbsource

  [echo] Generating java from doclit_nonwrap.wsdl for javabean endpoint

  [echo] support

  [echo] Generating java from doclitwrap.wsdl for javabean endpoint

  [echo] support

  [echo] Generating java from doclitbare.wsdl for javabean endpoint

  [echo] support

  [echo] Generating java from EchoMessage.wsdl for javabean endpoint

  [echo] support

  [echo] Generating java from resourceinjection.wsdl for javabean

  [echo] endpoint Resource Injection
 support

  [echo] Generating java from AnyType.wsdl for javabean endpoint

  [echo] AnyType support

  [echo] Generating java from MessageContext.wsdl for message context

  [echo] properties support

  [echo] Generating java from WSDLMultiTests.wsdl

  [echo] Generating java from Polymorphic shapes.wsdl for javabean

  [echo] endpoint support

  [echo] Generating java from SOAPActionTest.wsdl

  [echo] Generating java from rpclitenum.wsdl

  [echo] Generating java from AddNumbersHandler.wsdl

  [echo] Generating java from rpclitstringarray.wsdl

  [echo] Generating java from swamtomservice.wsdl

 Executed tasks

 [resources:testResources]

 Using default encoding to 

Re: help needed building axis2 using NetBeans 6.8 and maven 2.2.1

[Andreas Veithen]

On Mon, Feb 1, 2010 at 17:35, Stadelmann Josef
josef.stadelm...@axa-winterthur.ch wrote:
 Thank you Andreas,

 But why does under NetBeans IDE control, maven build/makes only 26 files 
 while running maven in a vista cmd window maven builds/makes 50 files.
 And that is what the error says. File not found ... osn't it?

NetBeans somehow decided to run the build with maven.test.skip set to
true. That is what causes the AppleFinderService issue (we figured
that out last weekend after several people had a look into that
issue).

 Looking at the POM I do not understand why this file and others are not built 
 when maven is used from NetBeans IDE.

 So your saying that I have no choice to have a error free build using 
 NetBeans IDE 6.8. I tried to build error free from the trunk sources and in 
 absence of a well running build I switched to the tags/v1.5.1 sources, which 
 did it perfectly when I used maven 2.2.1 from a Vista cmd window, but fails 
 now with the latest greatest NetBeans IDE 6.8

Does this imply that you had a build failure using the trunk sources
and plain Maven?

 Then I like to formulate my question differently.
 What source code version of axis2 shall I use to have an error free build 
 using NetBeans IDE 6.8 with external maven 2.2.1 and ant 1.7?

Our priority is to have a build that works correctly with (plain)
Maven. We do not systematically test importing the sources into
various IDEs, so it's impossible to tell which version works with the
particular combination of tools you are using. However, we are happy
to fix issues that occur with specific IDEs (if the required fix has
no negative impact on the normal Maven build) when they are reported.
E.g., myself, from time to time I fix issues to simplify working with
the sources in Eclipse.

 Thank you
 Josef



 -Ursprüngliche Nachricht-
 Von: Andreas Veithen [mailto:andreas.veit...@gmail.com]
 Gesendet: Montag, 1. Februar 2010 17:03
 An: axis-user@ws.apache.org
 Betreff: Re: help needed building axis2 using NetBeans 6.8 and maven 2.2.1

 Josef,

 Please see AXIS2-3290 and AXIS2-4460. This issue has been fixed
 recently in the trunk.

 Andreas

 On Mon, Feb 1, 2010 at 16:35, Stadelmann Josef
 josef.stadelm...@axa-winterthur.ch wrote:
 Hi all,

 I've used subversion to catch down axis2

 /trunk/java/

 /tags/java/v1.5.1

 /branches/java/v1.5

 Then I used a Vista cmd window and maven 2.2.1 to build axis2

 CD C:\asf\webservices\axis2\tags\java\v1.5.1

 C:\asf\webservices\axis2\tags\java\v1.5.1  mvn install

 And all was built perfect, greatre success, error free.

 Now I struggle with the same doing it from with NetBeans 6.8,

 using external maven 2.2.1 from the same location as done using maven from
 the vista cmd window

 C:\asf\webservices\axis2\tags\java\v1.5.1ant -version

 Apache Ant version 1.7.1 compiled on June 27 2008

 C:\asf\webservices\axis2\tags\java\v1.5.1

 It fails while building JAXWS Integration Tests

 Any ideas and hints welcome. What can I do to get my axis2 cleanly built
 using NetBeans IDE 6.8 and maven 2.2.1 ?

 I will use NB 6.8 for debugging axis2 running on a Integrity OpenVMS
 maschine under Tomcat,

 with a NetBeans IDE debugger attached to the JVM on OpenVMS.

 Regards

 Josef.Stadelmann

 @Axa-winterthur.ch

 NetBeans: Executing
 'C:\Users\C770817\SW-UMGEBUNG\apache-maven-2.2.1\bin\mvn.bat
 -Dmaven.test.skip=true -Dnetbeans.execution=true
 -Dmaven.repo.local=C:\Users\C770817\.m2\repository --errors -e clean
 install'

 NetBeans:  JAVA_HOME=C:\Program Files\JAVA\jdk1.6.0_14

 + Error stacktraces are turned on.

 Scanning for projects...

 

 Building Apache Axis2 - JAXWS Integration Tests

    task-segment: [clean, install]

 

 [clean:clean]

 Deleting directory
 C:\asf\webservices\axis2\tags\java\v1.5.1\modules\jaxws-integration\target

 [resources:resources]

 Using default encoding to copy filtered resources.

 [compiler:compile]

 No sources to compile

 [antrun:run]

 Executing tasks

     [mkdir] Created dir:
 C:\asf\webservices\axis2\tags\java\v1.5.1\modules\jaxws-integration\target\schema

     [mkdir] Created dir:
 C:\asf\webservices\axis2\tags\java\v1.5.1\modules\jaxws-integration\target\schema\src

     [mkdir] Created dir:
 C:\asf\webservices\axis2\tags\java\v1.5.1\modules\jaxws-integration\target\schema\classes

  [echo] Generating JAX-B classes from XSDs

  [echo] Generating java from soap 11

  [echo] Generating java from echo.xsd

  [echo] Generating java from stock1.xsd

  [echo] Generating java from stock2.xsd

  [echo] Generating java from samplemtom.xsd

  [echo] Generating java from greeterTypes.xsd

  [echo] Generating java from ProxyDocLitWrapped.wsdl

  [echo] Generating java from AddNumbers.wsdl

  [echo] Generating java from ProxyDocLitnonWrapped.wsdl

  [echo] Generating java from

Re: help needed building axis2 using NetBeans 6.8 and maven 2.2.1

[Andreas Veithen]

On Mon, Feb 1, 2010 at 18:10, Stadelmann Josef
josef.stadelm...@axa-winterthur.ch wrote:
 Andreas,

 The problem I am faced with is twofold.

 1. When I turn oft in NetBeans IDE 6.8 under Option at the Maven tag the 
 checkbox labeled:
 Skip test for any build executions not directly related to testing
 those resulting in forcing the maven command having a 
 -Dmaven.test.skip=true on board,
 then turning this flag OFF in the option menu for maven
 makes all test classes generated (around 50) and then
 the dedicated copy tasks as shown in the POM runs but al tests run as well 
 (very lengthy)

 Therefore: To get an error free build using NetBeans IDE 6.8 and maven 2.2.1 
 I have to work for JAXWS Integration with this flag set to OFF


 2. And maybe I get something wrong here but maybe of interest to you:
 When I use the vista cmd window
 ...  mvn -Dmaven.test.skip=true clean install

 The build
 C:\asf\webservices\axis2\tags\java\v1.5.1\modules\jaxws-integrationmvn 
 -Dmaven.test.skip=true clean install
 fails too.

That is the issue we fixed last weekend. See:

http://svn.apache.org/viewvc?view=revisionrevision=904780

 So are you saying I have to use the POM from the trunk for JAXWS Integration 
 to build correctly?
 OR
 Where do you think it was fixed; sorry but I am not getting more insight 
 reading the two JIRA's

 Josef





 -Ursprüngliche Nachricht-
 Von: Stadelmann Josef [mailto:josef.stadelm...@axa-winterthur.ch]
 Gesendet: Montag, 1. Februar 2010 17:35
 An: axis-user@ws.apache.org
 Betreff: AW: help needed building axis2 using NetBeans 6.8 and maven 2.2.1

 Thank you Andreas,

 But why does under NetBeans IDE control, maven build/makes only 26 files 
 while running maven in a vista cmd window maven builds/makes 50 files.
 And that is what the error says. File not found ... osn't it?

 Looking at the POM I do not understand why this file and others are not built 
 when maven is used from NetBeans IDE.

 So your saying that I have no choice to have a error free build using 
 NetBeans IDE 6.8. I tried to build error free from the trunk sources and in 
 absence of a well running build I switched to the tags/v1.5.1 sources, which 
 did it perfectly when I used maven 2.2.1 from a Vista cmd window, but fails 
 now with the latest greatest NetBeans IDE 6.8

 Then I like to formulate my question differently.
 What source code version of axis2 shall I use to have an error free build 
 using NetBeans IDE 6.8 with external maven 2.2.1 and ant 1.7?

 Thank you
 Josef



 -Ursprüngliche Nachricht-
 Von: Andreas Veithen [mailto:andreas.veit...@gmail.com]
 Gesendet: Montag, 1. Februar 2010 17:03
 An: axis-user@ws.apache.org
 Betreff: Re: help needed building axis2 using NetBeans 6.8 and maven 2.2.1

 Josef,

 Please see AXIS2-3290 and AXIS2-4460. This issue has been fixed
 recently in the trunk.

 Andreas

 On Mon, Feb 1, 2010 at 16:35, Stadelmann Josef
 josef.stadelm...@axa-winterthur.ch wrote:
 Hi all,

 I've used subversion to catch down axis2

 /trunk/java/

 /tags/java/v1.5.1

 /branches/java/v1.5

 Then I used a Vista cmd window and maven 2.2.1 to build axis2

 CD C:\asf\webservices\axis2\tags\java\v1.5.1

 C:\asf\webservices\axis2\tags\java\v1.5.1  mvn install

 And all was built perfect, greatre success, error free.

 Now I struggle with the same doing it from with NetBeans 6.8,

 using external maven 2.2.1 from the same location as done using maven from
 the vista cmd window

 C:\asf\webservices\axis2\tags\java\v1.5.1ant -version

 Apache Ant version 1.7.1 compiled on June 27 2008

 C:\asf\webservices\axis2\tags\java\v1.5.1

 It fails while building JAXWS Integration Tests

 Any ideas and hints welcome. What can I do to get my axis2 cleanly built
 using NetBeans IDE 6.8 and maven 2.2.1 ?

 I will use NB 6.8 for debugging axis2 running on a Integrity OpenVMS
 maschine under Tomcat,

 with a NetBeans IDE debugger attached to the JVM on OpenVMS.

 Regards

 Josef.Stadelmann

 @Axa-winterthur.ch

 NetBeans: Executing
 'C:\Users\C770817\SW-UMGEBUNG\apache-maven-2.2.1\bin\mvn.bat
 -Dmaven.test.skip=true -Dnetbeans.execution=true
 -Dmaven.repo.local=C:\Users\C770817\.m2\repository --errors -e clean
 install'

 NetBeans:  JAVA_HOME=C:\Program Files\JAVA\jdk1.6.0_14

 + Error stacktraces are turned on.

 Scanning for projects...

 

 Building Apache Axis2 - JAXWS Integration Tests

    task-segment: [clean, install]

 

 [clean:clean]

 Deleting directory
 C:\asf\webservices\axis2\tags\java\v1.5.1\modules\jaxws-integration\target

 [resources:resources]

 Using default encoding to copy filtered resources.

 [compiler:compile]

 No sources to compile

 [antrun:run]

 Executing tasks

     [mkdir] Created dir:
 C:\asf\webservices\axis2\tags\java\v1.5.1\modules\jaxws-integration\target\schema

     [mkdir] Created dir:
 C:\asf\webservices\axis2\tags

Re: Axis2 JAX-WS: The service class cannot be found for this AxisService

[Daniel Walsh]

Andreas,

I annotated my service class per your example and I am still getting the No
annotated classes found in the jar message when I click on the link
Faulty Services
c:\tomcat-6.0.20\webapps\axis2\WEB-INF\servicejars\HelloService.jarhttp://localhost:8080/axis2/services/ListFaultyServices?serviceName=c:%5Ctomcat-6.0.20%5Cwebapps%5Caxis2%5CWEB-INF%5Cservicejars%5CHelloService.jaron
the list services page at http://localhost:8080/axis2/services/listServices


My annotated implementation class, HelloPortImpl, is pretty simple:

package com.wb.hello;

import java.io.PrintStream;

import javax.jws.WebMethod;
import javax.jws.WebParam;
import javax.jws.WebResult;
import javax.jws.WebService;
import javax.jws.soap.SOAPBinding;
import javax.xml.bind.annotation.XmlSeeAlso;

@WebService(endpointInterface = com.wb.hello.HelloPort,
serviceName = HelloService,
portName = HelloPort,
targetNamespace = com/wb/hello,
wsdlLocation = META-INF/hello.wsdl)

public class HelloPortImpl implements HelloPort {

@WebMethod
@WebResult(name = helloResponseElement, targetNamespace =
com/wb/hello, partName = parameters)
public HelloResponseType hello(HelloRequestType helloRequestType) {
HelloResponseType helloResponseType = new HelloResponseType();
helloResponseType.setResponse(Hello  + helloRequestType.getRequest());
return helloResponseType;
}
}


And the class shows up in the jar file:

$ jar tvf
c:/tomcat-6.0.20/webapps/axis2/WEB-INF/servicejars/HelloService.jar
 0 Mon Feb 01 12:11:02 PST 2010 META-INF/
71 Mon Feb 01 12:11:02 PST 2010 META-INF/MANIFEST.MF
   890 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloPort.class
  1095 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloPortImpl.class
   898 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloPortType.class
   752 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloRequestType.class
   758 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloResponseType.class
  2003 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloService.class
  1708 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/ObjectFactory.class
   230 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/package-info.class
  1804 Mon Feb 01 12:11:00 PST 2010 META-INF/hello.wsdl
   805 Mon Feb 01 12:11:00 PST 2010 META-INF/helloSchema.xsd
   296 Sat Jan 30 16:26:00 PST 2010 META-INF/service.xml

If you have any thoughts as to why I can't get this thing to deploy I would
sure be happy to hear them.

Dan



andreas.veit...@gmail.com wrote:

 Dan,

 Actually the error message should read No @WebService annotated
 service implementations found or something like that :-)

 In fact, you also need to annotate your service implementation with
 @WebService. Note that while this is the same annotation type than on
 the service interface (generated by wsimport), the attributes have a
 different meaning. There is an example here [1]. Note that this
 requirement is not specific to Axis2, but comes from JSR-109/181.

 Andreas

 [1]
 https://svn.apache.org/repos/asf/webservices/axis2/scratch/java/veithen/AXIS2-4611/jaxws-calculator-aar/src/main/java/org/apache/axis2/jaxws/calculator/impl/CalculatorImpl.java

 On Thu, Jan 28, 2010 at 19:46, Daniel Walsh walsh94...@gmail.com wrote:
  Andreas,
 
  Thanks for the tip. I would never have figured that out by myself.
 
  Unfortunately, simply moving the services/HelloService.aar file to
  servicejars/HelloServices.jar seems to have made things worse. Whereas
  before I saw the service listed as deployed on the listServices page (but
  got the exception when trying to run the client), now the service doesn't
  even deploy. Clicking through the faulty services link on the
 listServices
  page gives me this:
 
  Error: No annotated classes found in the jar:
 
 file:/c:/tomcat-6.0.20/webapps/axis2/WEB-INF/servicejars/HelloService.jar.
  Service deployment failed.
 
  Looking for annotations in just the .java files generated by wsimport
 -keep
  -verbose hello.wsdl (the .class files of which are in the jar file) I
 find
  the following (I used grep ^@ | sort)
 
  @SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE)
  @WebService(name = helloPort, targetNamespace = com/wb/hello)
  @WebServiceClient(name = HelloService, targetNamespace =
 com/wb/hello,
  wsdlL
  ocation =
  file:/C:/Documents%20and%20Settings/dan/My%20Documents/tmp/hello2/ser
  vice/hello.wsdl)
  @XmlAccessorType(XmlAccessType.FIELD)
  @XmlAccessorType(XmlAccessType.FIELD)
  @XmlRegistry
  @XmlSeeAlso({
  @XmlType(name = helloRequestType, propOrder = {
  @XmlType(name = helloResponseType, propOrder = {
  @javax.xml.bind.annotation.XmlSchema(namespace = com/wb/hello)
 
  Clearly, there are lots of annotations, so the error message is
 incorrect.
 
  I'm not sure what to do at this point.
 
  Dan
 
 
  On Wed, Jan 27, 2010 at 12:46 PM, Andreas Veithen
  andreas.veit...@gmail.com wrote:
 
  Daniel,
 
  Please have a look at AXIS2-4611 [1]. If deploying as a servicejar is
  not an option for 

Re: Axis2 JAX-WS: The service class cannot be found for this AxisService

[Andreas Veithen]

Can you show me the annotations on HelloService, HelloPortType and HelloPort?

Andreas

On Mon, Feb 1, 2010 at 21:12, Daniel Walsh walsh94...@gmail.com wrote:
 Andreas,

 I annotated my service class per your example and I am still getting the No
 annotated classes found in the jar message when I click on the link

 Faulty Services

 c:\tomcat-6.0.20\webapps\axis2\WEB-INF\servicejars\HelloService.jar

 on the list services page at
 http://localhost:8080/axis2/services/listServices;

 My annotated implementation class, HelloPortImpl, is pretty simple:

 package com.wb.hello;

 import java.io.PrintStream;

 import javax.jws.WebMethod;
 import javax.jws.WebParam;
 import javax.jws.WebResult;
 import javax.jws.WebService;
 import javax.jws.soap.SOAPBinding;
 import javax.xml.bind.annotation.XmlSeeAlso;

 @WebService(endpointInterface = com.wb.hello.HelloPort,
     serviceName = HelloService,
     portName = HelloPort,
     targetNamespace = com/wb/hello,
     wsdlLocation = META-INF/hello.wsdl)

 public class HelloPortImpl implements HelloPort {

     @WebMethod
     @WebResult(name = helloResponseElement, targetNamespace =
 com/wb/hello, partName = parameters)
     public HelloResponseType hello(HelloRequestType helloRequestType) {
     HelloResponseType helloResponseType = new HelloResponseType();
     helloResponseType.setResponse(Hello  + helloRequestType.getRequest());
     return helloResponseType;
     }
 }


 And the class shows up in the jar file:

 $ jar tvf
 c:/tomcat-6.0.20/webapps/axis2/WEB-INF/servicejars/HelloService.jar
  0 Mon Feb 01 12:11:02 PST 2010 META-INF/
     71 Mon Feb 01 12:11:02 PST 2010 META-INF/MANIFEST.MF
    890 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloPort.class
   1095 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloPortImpl.class
    898 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloPortType.class
    752 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloRequestType.class
    758 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloResponseType.class
   2003 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloService.class
   1708 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/ObjectFactory.class
    230 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/package-info.class
   1804 Mon Feb 01 12:11:00 PST 2010 META-INF/hello.wsdl
    805 Mon Feb 01 12:11:00 PST 2010 META-INF/helloSchema.xsd
    296 Sat Jan 30 16:26:00 PST 2010 META-INF/service.xml

 If you have any thoughts as to why I can't get this thing to deploy I would
 sure be happy to hear them.

 Dan



 andreas.veit...@gmail.com wrote:

 Dan,

 Actually the error message should read No @WebService annotated
 service implementations found or something like that :-)

 In fact, you also need to annotate your service implementation with
 @WebService. Note that while this is the same annotation type than on
 the service interface (generated by wsimport), the attributes have a
 different meaning. There is an example here [1]. Note that this
 requirement is not specific to Axis2, but comes from JSR-109/181.

 Andreas

 [1]
 https://svn.apache.org/repos/asf/webservices/axis2/scratch/java/veithen/AXIS2-4611/jaxws-calculator-aar/src/main/java/org/apache/axis2/jaxws/calculator/impl/CalculatorImpl.java

 On Thu, Jan 28, 2010 at 19:46, Daniel Walsh walsh94...@gmail.com wrote:
  Andreas,
 
  Thanks for the tip. I would never have figured that out by myself.
 
  Unfortunately, simply moving the services/HelloService.aar file to
  servicejars/HelloServices.jar seems to have made things worse. Whereas
  before I saw the service listed as deployed on the listServices page
  (but
  got the exception when trying to run the client), now the service
  doesn't
  even deploy. Clicking through the faulty services link on the
  listServices
  page gives me this:
 
  Error: No annotated classes found in the jar:
 
  file:/c:/tomcat-6.0.20/webapps/axis2/WEB-INF/servicejars/HelloService.jar.
  Service deployment failed.
 
  Looking for annotations in just the .java files generated by wsimport
  -keep
  -verbose hello.wsdl (the .class files of which are in the jar file) I
  find
  the following (I used grep ^@ | sort)
 
  @SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE)
  @WebService(name = helloPort, targetNamespace = com/wb/hello)
  @WebServiceClient(name = HelloService, targetNamespace =
  com/wb/hello,
  wsdlL
  ocation =
  file:/C:/Documents%20and%20Settings/dan/My%20Documents/tmp/hello2/ser
  vice/hello.wsdl)
  @XmlAccessorType(XmlAccessType.FIELD)
  @XmlAccessorType(XmlAccessType.FIELD)
  @XmlRegistry
  @XmlSeeAlso({
  @XmlType(name = helloRequestType, propOrder = {
  @XmlType(name = helloResponseType, propOrder = {
  @javax.xml.bind.annotation.XmlSchema(namespace = com/wb/hello)
 
  Clearly, there are lots of annotations, so the error message is
  incorrect.
 
  I'm not sure what to do at this point.
 
  Dan
 
 
  On Wed, Jan 27, 2010 at 12:46 PM, Andreas Veithen
  andreas.veit...@gmail.com wrote:
 
  Daniel,
 
  Please have a 

Re: Axis2 JAX-WS: The service class cannot be found for this AxisService

[Daniel Walsh]

Andreas:

The annotations generated by wsimport are:

HelloService:

@WebServiceClient(name = HelloService, targetNamespace = com/wb/hello,
wsdlLocation = file:/C:/axis2-1.5.1/hello2/service/hello.wsdl)

HelloPortType:

@WebService(name = helloPortType, targetNamespace = com/wb/hello)
@SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE)
@XmlSeeAlso({
ObjectFactory.class
})

 HelloPort:

@WebService(name = helloPort, targetNamespace = com/wb/hello)
@SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE)
@XmlSeeAlso({
ObjectFactory.class
})

I'm not sure why, but based on timestamps wsimport right now isn't
generating HelloPortType. On the other hand, it isn't referenced anywhere in
any of the other code, so I don't know if it matters.

Dan


On Mon, Feb 1, 2010 at 1:51 PM, Andreas Veithen
andreas.veit...@gmail.comwrote:

 Can you show me the annotations on HelloService, HelloPortType and
 HelloPort?

 Andreas

 On Mon, Feb 1, 2010 at 21:12, Daniel Walsh walsh94...@gmail.com wrote:
  Andreas,
 
  I annotated my service class per your example and I am still getting the
 No
  annotated classes found in the jar message when I click on the link
 
  Faulty Services
 
  c:\tomcat-6.0.20\webapps\axis2\WEB-INF\servicejars\HelloService.jar
 
  on the list services page at
  http://localhost:8080/axis2/services/listServices;
 
  My annotated implementation class, HelloPortImpl, is pretty simple:
 
  package com.wb.hello;
 
  import java.io.PrintStream;
 
  import javax.jws.WebMethod;
  import javax.jws.WebParam;
  import javax.jws.WebResult;
  import javax.jws.WebService;
  import javax.jws.soap.SOAPBinding;
  import javax.xml.bind.annotation.XmlSeeAlso;
 
  @WebService(endpointInterface = com.wb.hello.HelloPort,
  serviceName = HelloService,
  portName = HelloPort,
  targetNamespace = com/wb/hello,
  wsdlLocation = META-INF/hello.wsdl)
 
  public class HelloPortImpl implements HelloPort {
 
  @WebMethod
  @WebResult(name = helloResponseElement, targetNamespace =
  com/wb/hello, partName = parameters)
  public HelloResponseType hello(HelloRequestType helloRequestType) {
  HelloResponseType helloResponseType = new HelloResponseType();
  helloResponseType.setResponse(Hello  +
 helloRequestType.getRequest());
  return helloResponseType;
  }
  }
 
 
  And the class shows up in the jar file:
 
  $ jar tvf
  c:/tomcat-6.0.20/webapps/axis2/WEB-INF/servicejars/HelloService.jar
   0 Mon Feb 01 12:11:02 PST 2010 META-INF/
  71 Mon Feb 01 12:11:02 PST 2010 META-INF/MANIFEST.MF
 890 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloPort.class
1095 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloPortImpl.class
 898 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloPortType.class
 752 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloRequestType.class
 758 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloResponseType.class
2003 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/HelloService.class
1708 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/ObjectFactory.class
 230 Mon Feb 01 12:11:02 PST 2010 com/wb/hello/package-info.class
1804 Mon Feb 01 12:11:00 PST 2010 META-INF/hello.wsdl
 805 Mon Feb 01 12:11:00 PST 2010 META-INF/helloSchema.xsd
 296 Sat Jan 30 16:26:00 PST 2010 META-INF/service.xml
 
  If you have any thoughts as to why I can't get this thing to deploy I
 would
  sure be happy to hear them.
 
  Dan
 
 
 
  andreas.veit...@gmail.com wrote:
 
  Dan,
 
  Actually the error message should read No @WebService annotated
  service implementations found or something like that :-)
 
  In fact, you also need to annotate your service implementation with
  @WebService. Note that while this is the same annotation type than on
  the service interface (generated by wsimport), the attributes have a
  different meaning. There is an example here [1]. Note that this
  requirement is not specific to Axis2, but comes from JSR-109/181.
 
  Andreas
 
  [1]
 
 https://svn.apache.org/repos/asf/webservices/axis2/scratch/java/veithen/AXIS2-4611/jaxws-calculator-aar/src/main/java/org/apache/axis2/jaxws/calculator/impl/CalculatorImpl.java
 
  On Thu, Jan 28, 2010 at 19:46, Daniel Walsh walsh94...@gmail.com
 wrote:
   Andreas,
  
   Thanks for the tip. I would never have figured that out by myself.
  
   Unfortunately, simply moving the services/HelloService.aar file to
   servicejars/HelloServices.jar seems to have made things worse.
 Whereas
   before I saw the service listed as deployed on the listServices page
   (but
   got the exception when trying to run the client), now the service
   doesn't
   even deploy. Clicking through the faulty services link on the
   listServices
   page gives me this:
  
   Error: No annotated classes found in the jar:
  
  
 file:/c:/tomcat-6.0.20/webapps/axis2/WEB-INF/servicejars/HelloService.jar.
   Service deployment failed.
  
   Looking for annotations in just the .java files generated by 

Re: Axis2 clustering error

[Shailesh Potnis]

It got resolved when I commented out the localMemberHost element.

 Thank You and Best Regards


Sincerely


Shailesh





From: Shailesh Potnis potnis2...@yahoo.com
To: axis-user@ws.apache.org
Sent: Mon, February 1, 2010 4:58:13 PM
Subject: Axis2 clustering error


Hi:

I am trying to get a better understanding of the following parameters and how 
to set them for Axis 2. 1.5 cluster:

mcastBindAddress

localMemberHost

I have set mcastBindAddress to 127.0.0.1 and localMemberHost to IP address of 
one of the hosts in the cluster.  (I tried to set localMemberHost to 127.0.0.1 
as well but I get an error that it cannot bind to that address as well)  (I 
have hidden the actual IP address to protect confidential information)

I used WSO2 Carbon Cluster Configuration Language which indicated that 
localMemberHost should be set to a value other than localhost and may set it to 
the IP address bound to the network interface which is used for 
communicating with members in the group. (I am trying to determine what that 
address might be)  

http://wso2.org/library/articles/wso2-carbon-cluster-configuration-language

All helpful suggestions are highly appreciated.

I get the following error:
---

[INFO] Deploying JAXWS annotated class sample.jaxws.Version as a service - JAXWS
Version.VersionPort
[INFO] Initializing cluster...
[INFO] Cluster domain: apache.axis2.domain
[INFO] Using multicast based membership management scheme
Feb 1, 2010 3:56:07 PM org.apache.catalina.tribes.transport.ReceiverBase bind
INFO: Unable to bind server socket to:/xx.xxx.xxx.xxx:4099 throwing error.
Feb 1, 2010 3:56:07 PM org.apache.catalina.tribes.transport.nio.NioReceiver star
t
SEVERE: Unable to start cluster receiver
java.net.BindException: Cannot assign requested address
at sun.nio.ch.Net.bind(Native Method)
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:
119)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:52)
at org.apache.catalina.tribes.transport.ReceiverBase.bind(ReceiverBase.j
ava:205)
at org.apache.catalina.tribes.transport.ReceiverBase.bind(ReceiverBase.j
ava:217)
at org.apache.catalina.tribes.transport.ReceiverBase.bind(ReceiverBase.j
ava:217)
@

. additional stack omitted.
---


 Thank You and Best Regards


Sincerely


Shailesh


  

Re: help needed building axis2 using NetBeans 6.8 and maven 2.2.1

[Amila Suriarachchi]

On Mon, Feb 1, 2010 at 10:05 PM, Stadelmann Josef 
josef.stadelm...@axa-winterthur.ch wrote:

 Thank you Andreas,

 But why does under NetBeans IDE control, maven build/makes only 26 files
 while running maven in a vista cmd window maven builds/makes 50 files.
 And that is what the error says. File not found ... osn't it?

 Looking at the POM I do not understand why this file and others are not
 built when maven is used from NetBeans IDE.

 So your saying that I have no choice to have a error free build using
 NetBeans IDE 6.8. I tried to build error free from the trunk sources and in
 absence of a well running build I switched to the tags/v1.5.1 sources, which
 did it perfectly when I used maven 2.2.1 from a Vista cmd window, but fails
 now with the latest greatest NetBeans IDE 6.8

 Then I like to formulate my question differently.
 What source code version of axis2 shall I use to have an error free build
 using NetBeans IDE 6.8 with external maven 2.2.1 and ant 1.7?


As Andreas has told this is fixed in current trunk and available  with next
release.
For the moment you can remove the jaxws-integration module (this contains
some integration tests for jaxws and since you skip tests anyway it is not
useful) from the root pom.xml

Amila.


 Thank you
 Josef



 -Ursprüngliche Nachricht-
 Von: Andreas Veithen [mailto:andreas.veit...@gmail.com]
 Gesendet: Montag, 1. Februar 2010 17:03
 An: axis-user@ws.apache.org
 Betreff: Re: help needed building axis2 using NetBeans 6.8 and maven 2.2.1

 Josef,

 Please see AXIS2-3290 and AXIS2-4460. This issue has been fixed
 recently in the trunk.

 Andreas

 On Mon, Feb 1, 2010 at 16:35, Stadelmann Josef
 josef.stadelm...@axa-winterthur.ch wrote:
  Hi all,
 
  I've used subversion to catch down axis2
 
  /trunk/java/
 
  /tags/java/v1.5.1
 
  /branches/java/v1.5
 
  Then I used a Vista cmd window and maven 2.2.1 to build axis2
 
  CD C:\asf\webservices\axis2\tags\java\v1.5.1
 
  C:\asf\webservices\axis2\tags\java\v1.5.1  mvn install
 
  And all was built perfect, greatre success, error free.
 
  Now I struggle with the same doing it from with NetBeans 6.8,
 
  using external maven 2.2.1 from the same location as done using maven
 from
  the vista cmd window
 
  C:\asf\webservices\axis2\tags\java\v1.5.1ant -version
 
  Apache Ant version 1.7.1 compiled on June 27 2008
 
  C:\asf\webservices\axis2\tags\java\v1.5.1
 
  It fails while building JAXWS Integration Tests
 
  Any ideas and hints welcome. What can I do to get my axis2 cleanly built
  using NetBeans IDE 6.8 and maven 2.2.1 ?
 
  I will use NB 6.8 for debugging axis2 running on a Integrity OpenVMS
  maschine under Tomcat,
 
  with a NetBeans IDE debugger attached to the JVM on OpenVMS.
 
  Regards
 
  Josef.Stadelmann
 
  @Axa-winterthur.ch
 
  NetBeans: Executing
  'C:\Users\C770817\SW-UMGEBUNG\apache-maven-2.2.1\bin\mvn.bat
  -Dmaven.test.skip=true -Dnetbeans.execution=true
  -Dmaven.repo.local=C:\Users\C770817\.m2\repository --errors -e clean
  install'
 
  NetBeans:  JAVA_HOME=C:\Program Files\JAVA\jdk1.6.0_14
 
  + Error stacktraces are turned on.
 
  Scanning for projects...
 
  
 
  Building Apache Axis2 - JAXWS Integration Tests
 
 task-segment: [clean, install]
 
  
 
  [clean:clean]
 
  Deleting directory
 
 C:\asf\webservices\axis2\tags\java\v1.5.1\modules\jaxws-integration\target
 
  [resources:resources]
 
  Using default encoding to copy filtered resources.
 
  [compiler:compile]
 
  No sources to compile
 
  [antrun:run]
 
  Executing tasks
 
  [mkdir] Created dir:
 
 C:\asf\webservices\axis2\tags\java\v1.5.1\modules\jaxws-integration\target\schema
 
  [mkdir] Created dir:
 
 C:\asf\webservices\axis2\tags\java\v1.5.1\modules\jaxws-integration\target\schema\src
 
  [mkdir] Created dir:
 
 C:\asf\webservices\axis2\tags\java\v1.5.1\modules\jaxws-integration\target\schema\classes
 
   [echo] Generating JAX-B classes from XSDs
 
   [echo] Generating java from soap 11
 
   [echo] Generating java from echo.xsd
 
   [echo] Generating java from stock1.xsd
 
   [echo] Generating java from stock2.xsd
 
   [echo] Generating java from samplemtom.xsd
 
   [echo] Generating java from greeterTypes.xsd
 
   [echo] Generating java from ProxyDocLitWrapped.wsdl
 
   [echo] Generating java from AddNumbers.wsdl
 
   [echo] Generating java from ProxyDocLitnonWrapped.wsdl
 
   [echo] Generating java from samplemtomjpeg.wsdl
 
   [echo] Generating java from RPCLit.wsdl
 
   [echo] Generating java from RPCLitSWA.wsdl
 
   [echo] Generating java from gorilla_dlw.wsdl
 
   [echo] Generating java from SOAP12Echo.wsdl
 
   [echo] Generating java from AddNumbersHandler.wsdl
 
   [echo] Generating java from async_doclitwr.wsdl
 
   [echo] Generating java from async_doclitwr2.wsdl

Re: doc/literal style and wsdl:part combination

[Amila Suriarachchi]

On Mon, Feb 1, 2010 at 11:05 PM, rahul yadav rahulyada...@gmail.com wrote:

 Hi All,

 Will it be true to say If your WSDL is a document-literal style, then
 wsdl:part should point to an element instead of type.

yes.
see [1] R2204 and R2203. if it is rpc-literal the part should refer to a
type.

basic profile does not talk about rpc-enc

thanks,
Amila.


[1] http://www.ws-i.org/Profiles/BasicProfile-1.1.html#Bindings_and_Parts

 And if WSDL is a rpc-enc style, then wsdl:part should point to type.






-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/