date:20081015

Re: Difference between SOAP 1.1, SOAP 1.2 and SOAP HTTP

2008-10-15 Thread keith chapman

Hi If you take this WSDL
[1] as an example,
it has a SOAP 1.1 (system-version-SOAP11Binding) as well
as a SOAP 1.2 (system-version-SOAP12Binding) Binding. If you further look
into its content you will see that they use different namespaces, For e.g
SOAP 1.1 Binding uses "http://schemas.xmlsoap.org/soap/http"; style="document"/>" whereas SOAP 1.2
Binding uses "http://schemas.xmlsoap.org/soap/http"; style="document"/>" and the soap12
namespace is xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"; whereas
the soap namespace is xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";.

As you can see there is a difference between the two.

Thanks,
Keith.

[1] https://mooshup.com/services/system/version?wsdl

On Thu, Oct 16, 2008 at 12:35 AM, Bai Shen <[EMAIL PROTECTED]> wrote:

> I looked at the wsdl again, and there's literally no difference.  As far as
> I can tell, they both reference the same namespace.
>
>
> On Wed, Oct 15, 2008 at 2:00 PM, keith chapman <[EMAIL PROTECTED]>wrote:
>
>> The SOAP 1.1 and SOAP 1.2 Bindings look identical but they have a small
>> difference. They indicate to the client what SOAP version to use. If you
>> generate a client specifying the endpoint it will generate it so that the
>> message generated by the client would match the requirements specified in
>> the corresponding binding. You could differentiate between SOAP 1.1 and 1.2
>> using the namespace.
>>
>> SOAP 1.2 namespace is http://www.w3.org/2003/05/soap-envelope while SOAP
>> 1.1 namespace is http://schemas.xmlsoap.org/soap/envelope/
>>
>> Thanks,
>> Keith.
>>
>> On Wed, Oct 15, 2008 at 11:14 PM, Bai Shen <[EMAIL PROTECTED]>wrote:
>>
>>> I created a java class, and then used Axis2 to create a web service from
>>> that. However, in the WSDL, it created three connections.  A SOAP 1.1, a
>>> SOAP 1.2, and a SOAP HTTP.  The SOAP 1.1 and SOAP 1.2 ones look identical to
>>> me.  So I was wondering what the difference was. And is there a need for
>>> them?  How does Axis2 know whether it's a 1.1 or 1.2?  TIA.
>>>
>>> Bai Shen
>>>
>>
>>
>>
>> --
>> Keith Chapman
>> Senior Software Engineer
>> WSO2 Inc.
>> Oxygenating the Web Service Platform.
>> http://wso2.org/
>>
>> blog: http://www.keith-chapman.org
>>
>
>

-- 
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org

Re: Client address on messagecontext??

2008-10-15 Thread Igor Nogueira

So,  I must set the ReplyTo parameter explicitly  at the client before the
invocation ?
If I copy the "":http://www.w3.org/2005/08/addressing/anonymous"; endpoint I
can't trust the answer will be sent to the same specific client, isn't it?

Thanks,

Igor

2008/10/15 Amila Suriarachchi <[EMAIL PROTECTED]>

>
>
> On Wed, Oct 15, 2008 at 9:35 AM, Igor Nogueira <
> [EMAIL PROTECTED]> wrote:
>
>> Guys, I have a doubt. I have handler engaged on the inflow and outflow.
>> I'd like to know what's the client's address . I tested the MessageContext's
>> "From" and "To"  parameters  and I have the following situation:
>>
>
> Does client sends the Addressing headers. if so this detail can be found in
> To Header.
>
>>
>>
>> At Inflow:
>> "From" value is 127.0.0.1 (I invoke the webservice from localhost);
>> "To" value is "http://127.0.0.1:8080/axis2/services/ShoppingCart1";.
>>
>> At outflow:
>> "From" is null;
>> "To" is ":http://www.w3.org/2005/08/addressing/anonymous";
>>
>
> This means the response is send in the back channel.  if the client
> message has given a reply to address it would have showed the address.
>
> thanks,
> Amila.
>
>>
>>
>>
>> Is it possible to retrieve the real client's address on the messagecontext
>> received as parameter of the handler's invoke method? Or is it built on a
>> later phase of OutFlow and I can' access it?
>>
>>
>>
>> Thanks in advance,
>>
>> Igor
>>
>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>

Re: Difference between SOAP 1.1, SOAP 1.2 and SOAP HTTP

2008-10-15 Thread keith chapman

Hi If you take this WSDL
[1] as an example,
it has a SOAP 1.1 (system-version-SOAP11Binding) as well
as a SOAP 1.2 (system-version-SOAP12Binding) Binding. If you further look
into its content you will see that they use different namespaces, For e.g
SOAP 1.1 Binding uses "http://schemas.xmlsoap.org/soap/http"; style="document"/>" whereas SOAP 1.2
Binding uses "http://schemas.xmlsoap.org/soap/http"; style="document"/>" and the soap12
namespace is xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"; whereas
the soap namespace is xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";.

As you can see there is a difference between the two.

Thanks,
Keith.

[1] https://mooshup.com/services/system/version?wsdl

On Thu, Oct 16, 2008 at 12:35 AM, Bai Shen <[EMAIL PROTECTED]> wrote:

> I looked at the wsdl again, and there's literally no difference.  As far as
> I can tell, they both reference the same namespace.
>
>
> On Wed, Oct 15, 2008 at 2:00 PM, keith chapman <[EMAIL PROTECTED]>wrote:
>
>> The SOAP 1.1 and SOAP 1.2 Bindings look identical but they have a small
>> difference. They indicate to the client what SOAP version to use. If you
>> generate a client specifying the endpoint it will generate it so that the
>> message generated by the client would match the requirements specified in
>> the corresponding binding. You could differentiate between SOAP 1.1 and 1.2
>> using the namespace.
>>
>> SOAP 1.2 namespace is http://www.w3.org/2003/05/soap-envelope while SOAP
>> 1.1 namespace is http://schemas.xmlsoap.org/soap/envelope/
>>
>> Thanks,
>> Keith.
>>
>> On Wed, Oct 15, 2008 at 11:14 PM, Bai Shen <[EMAIL PROTECTED]>wrote:
>>
>>> I created a java class, and then used Axis2 to create a web service from
>>> that. However, in the WSDL, it created three connections.  A SOAP 1.1, a
>>> SOAP 1.2, and a SOAP HTTP.  The SOAP 1.1 and SOAP 1.2 ones look identical to
>>> me.  So I was wondering what the difference was. And is there a need for
>>> them?  How does Axis2 know whether it's a 1.1 or 1.2?  TIA.
>>>
>>> Bai Shen
>>>
>>
>>
>>
>> --
>> Keith Chapman
>> Senior Software Engineer
>> WSO2 Inc.
>> Oxygenating the Web Service Platform.
>> http://wso2.org/
>>
>> blog: http://www.keith-chapman.org
>>
>
>

-- 
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org

Re: AXIS JAVA Client - JMS Transport Authenication

2008-10-15 Thread Asankha C. Perera


Sam

What is the version of Axis2 and the JMS transport which you are using? 
i.e. is it the SNAPSHOT versions or a previous release? The JMS 
transport implementation used by Apache Synapse ESB now lives in the 
WSCommons project so that Axis2 users can share is more naturally. That 
has support to define connection properties for outgoing JMS on your 
axis2.xml for the JMS sender. You could define JNDI properties (i.e. 
credentials) there for them to be picked up. Anyway, some more 
background information would help us help you better


asankha

Kuhn, Samuel M wrote:

I need to provide a username and password to my AXIS client which is
attempting to invoke a web service provider over a TIBCO EMS (JMS
implementation) endpoint.  I tried setting the username and password
using the Call.setUsername() and Call.setPassword() methods with no
luck.  I also tried adding java.naming.security.principal and
java.naming.security.credentials to the URL with no luck.

Here's what my String url looks like:

static String sampleJmsUrl = "jms:/queue.sample?" +
 "vendor=JNDI" +
 
"&java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialConte

xtFactory" +
 
"&java.naming.provider.url=tcp://localhost:7222" +

 "&java.naming.security.principal=abc" +
 "&java.naming.security.credentials=xyz"
+
 
"&ConnectionFactoryJNDIName=QueueConnectionFactory" +

 "&deliveryMode=persistent" +
 "&priority=5" +
 "&ttl=1" +
 "&debug=true";

It appears my AXIS client is trying to log on using an "anonymous" user
based on the error message I'm getting from the EMS server.  Any help in
resolving this would be appreciated.

Sincerely,
Sam Kuhn

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


  


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

RE: Out Only MEP and Rest support

2008-10-15 Thread Martin Gainty


the action you're specifying is null 

Service Description : ClientService
Service Status : Active
Available Operations 
notify 

so in the axis 2.13 there is a fibonacci sample so your wsdl your action should 
look something like..

http://schemas.xmlsoap.org/soap/http"; 
style="document">




as earlier suggested please read the doc at http://wso2.org/library/3726
thanks
Martin 
__ 
Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relates to the official business 
of Sender. This transmission is of a confidential nature and Sender does not 
endorse distribution to any party other than intended recipient. Sender does 
not necessarily endorse content contained within this transmission. 


Date: Wed, 15 Oct 2008 16:28:09 -0700
From: [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Subject: Re: Out Only MEP and Rest support

Keith, thanks for the info, it helped somewhat as I am further along...calling 
it a night though, and will resume tomorrow.  This I am left off:

[ERROR] org.apache.axis2.AxisFault: Exception occurred while trying to invoke 
service method notify

[ERROR] Exception occurred while trying to invoke service method notify
org.apache.axis2.AxisFault: namespace mismatch require 
http://ws.apache.org/axis2 found http://ws.apache.org/axis2/xsd


On Wed, Oct 15, 2008 at 11:03 AM, keith chapman <[EMAIL PROTECTED]> wrote:

Perhaps having a look at this article [1] would explain to you how REST works 
in Axis2.

Thanks,
Keith.

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



On Wed, Oct 15, 2008 at 11:20 PM, Barry Alexander <[EMAIL PROTECTED]> wrote:


After send this 
http://localhost:8080/axis2/services/ActiveService/register?notifyEpr=http://localhost:8080/axis2/services/ClientServic




I see this in the tomcat logs:

[ERROR] The endpoint reference (EPR) for the Operation not found is 
/axis2/services/ActiveService/register?notifyEpr=http://localhost:8080/axis2/services/ClientService
 and the WSA Action = null



org.apache.axis2.AxisFault: The endpoint reference (EPR) for the Operation not 
found is 
/axis2/services/ActiveService/register?notifyEpr=http://localhost:8080/axis2/services/ClientService
 and the WSA Action = null



at 
org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:89)
at org.apache.axis2.engine.Phase.invoke(Phase.java:333)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:264)



at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:163)
at 
org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine(RESTUtil.java:136)
at 
org.apache.axis2.transport.http.util.RESTUtil.processURLRequest(RESTUtil.java:130)



at 
org.apache.axis2.transport.http.AxisServlet$RestRequestProcessor.processURLRequest(AxisServlet.java:829)
at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:255)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)



at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)



at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)



at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)



at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)



at java.lang.Thread.run(Unknown Source)


On Wed, Oct 15, 2008 at 10:02 AM, Barry Alexander <[EMAIL PROTECTED]> wrote:



Hi Axis2 users,

 

I am trying the sample application at http://wso2.org/library/406 and have a 
few questions:




 

1)  I have built and successfully deployed the two mentioned services in 
the sample referenced above (ActiveService and ClientService), when attempting 
to register with 
http://localhost:8080/axis2/rest/ActiveService?register?notifyEpr=http://localhost:8080/axis2/services/ClientService
 I get "Requested resource not found!"





2)  I modified the axis2.xml as follows:













rest





 

   

   false

This seemed to have no effect.





 

How do I enable the 'rest' url to register my client service?
 
Environment details:
 
  
Axis2 Happiness Page
Examining webapp configuration
Essential Components
Found Apache-Axi

Re: Out Only MEP and Rest support

2008-10-15 Thread Barry Alexander

Keith, thanks for the info, it helped somewhat as I am further
along...calling it a night though, and will resume tomorrow.  This I am left
off:

[ERROR] org.apache.axis2.AxisFault: Exception occurred while trying to
invoke service method notify
[ERROR] Exception occurred while trying to invoke service method notify
org.apache.axis2.AxisFault: namespace mismatch require
http://ws.apache.org/axis2 found http://ws.apache.org/axis2/xsd

On Wed, Oct 15, 2008 at 11:03 AM, keith chapman <[EMAIL PROTECTED]>wrote:

> Perhaps having a look at this article  [1]
> would explain to you how REST works in Axis2.
>
> Thanks,
> Keith.
>
> [1] http://wso2.org/library/3726
>
>
> On Wed, Oct 15, 2008 at 11:20 PM, Barry Alexander <
> [EMAIL PROTECTED]> wrote:
>
>> After send this
>> http://localhost:8080/axis2/services/ActiveService/register?notifyEpr=http://localhost:8080/axis2/services/ClientServic
>>
>> I see this in the tomcat logs:
>>
>> [ERROR] The endpoint reference (EPR) for the Operation not found is
>> /axis2/services/ActiveService/register?notifyEpr=
>> http://localhost:8080/axis2/services/ClientService and the WSA Action =
>> null
>> org.apache.axis2.AxisFault: The endpoint reference (EPR) for the Operation
>> not found is /axis2/services/ActiveService/register?notifyEpr=
>> http://localhost:8080/axis2/services/ClientService and the WSA Action =
>> null
>> at
>> org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:89)
>> at org.apache.axis2.engine.Phase.invoke(Phase.java:333)
>> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:264)
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:163)
>> at
>> org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine(RESTUtil.java:136)
>> at
>> org.apache.axis2.transport.http.util.RESTUtil.processURLRequest(RESTUtil.java:130)
>> at
>> org.apache.axis2.transport.http.AxisServlet$RestRequestProcessor.processURLRequest(AxisServlet.java:829)
>> at
>> org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:255)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>> at
>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>> at
>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
>> at
>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
>> at
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>> at
>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>> at
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
>> at
>> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
>> at
>> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
>> at
>> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
>> at java.lang.Thread.run(Unknown Source)
>>
>>
>>
>> On Wed, Oct 15, 2008 at 10:02 AM, Barry Alexander <
>> [EMAIL PROTECTED]> wrote:
>>
>>> Hi Axis2 users,
>>>
>>>
>>>
>>> I am trying the sample application at http://wso2.org/library/406 and
>>> have a few questions:
>>>
>>>
>>>
>>> 1)  I have built and successfully deployed the two mentioned services
>>> in the sample referenced above (ActiveService and ClientService), when
>>> attempting to register with
>>> http://localhost:8080/axis2/rest/ActiveService?register?notifyEpr=http://localhost:8080/axis2/services/ClientServiceI
>>>  get "Requested resource not found!"
>>>
>>> 2)  I modified the axis2.xml as follows:
>>>
>>> 
>>>
>>> 
>>>
>>> 
>>>
>>> 
>>>
>>> rest
>>>
>>>
>>>
>>>
>>>
>>>false
>>>
>>> This seemed to have no effect.
>>>
>>>
>>>
>>> How do I enable the 'rest' url to register my client service?
>>>
>>> Environment details:
>>>
>>>
>>> Axis2 Happiness Page
>>> Examining webapp configuration
>>> Essential Components
>>> Found Apache-Axis (org.apache.axis2.transport.http.AxisServlet)
>>>   at C:\Program Files\Apache Software Foundation\Tomcat
>>> 6.0\webapps\axis2\WEB-INF\lib\axis2-kernel-1.4.1.jar
>>> Found Jakarta-Commons Logging (org.apache.commons.logging.Log)
>>>   at C:\Program Files\Apache Software Foundation\Tomcat
>>> 6.0\webapps\axis2\WEB-INF\lib\commons-logging-1.1.1.jar
>>> Found Streaming API for XML (javax.xml.stream.XMLStreamReader)
>>>   at an unknown location
>>> Found Streaming API for XML implementation
>>> (org.codehaus.stax2.XMLStreamWriter2)
>>>   at C:\Program Files\Apache Software Foundation\Tomcat
>>> 6.0\webapps\axis2\WEB-INF\lib\wstx-asl-3.2

AXIS JAVA Client - JMS Transport Authenication

2008-10-15 Thread Kuhn, Samuel M

I need to provide a username and password to my AXIS client which is
attempting to invoke a web service provider over a TIBCO EMS (JMS
implementation) endpoint.  I tried setting the username and password
using the Call.setUsername() and Call.setPassword() methods with no
luck.  I also tried adding java.naming.security.principal and
java.naming.security.credentials to the URL with no luck.

Here's what my String url looks like:

static String sampleJmsUrl = "jms:/queue.sample?" +
 "vendor=JNDI" +
 
"&java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialConte
xtFactory" +
 
"&java.naming.provider.url=tcp://localhost:7222" +
 "&java.naming.security.principal=abc" +
 "&java.naming.security.credentials=xyz"
+
 
"&ConnectionFactoryJNDIName=QueueConnectionFactory" +
 "&deliveryMode=persistent" +
 "&priority=5" +
 "&ttl=1" +
 "&debug=true";

It appears my AXIS client is trying to log on using an "anonymous" user
based on the error message I'm getting from the EMS server.  Any help in
resolving this would be appreciated.

Sincerely,
Sam Kuhn

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

Strings and Axis2

2008-10-15 Thread Meeusen, Christopher W.

Hello everyone first time poster here,
 
I have a service which is returning a string.  I need to have the
service return the string in it's entirety, right now it's truncating
the empty spaces at the beginning and end of the string.  
 
For example String a = " abcdef 1234  "; 
 
The outbound soap message has 
 
String a = "abcdef 1234";
 
Thanks!
 
Chris Meeusen

 

Information Technology

Mayo Integrated Clinical Systems

Phone: (507) 538-4733

E-mail: mailto:[EMAIL PROTECTED]

_

 

Mayo Clinic

200 First Street S.W.

Rochester, MN 55905

www.mayoclinic.org

Re: namespaces error

2008-10-15 Thread Harm de Laat

Anybody has an idea on this. We're quite stuck on our project because of
this.

Kind regards,

Harm de Laat


On Tue, Oct 14, 2008 at 5:52 PM, Harm de Laat <[EMAIL PROTECTED]> wrote:

> The message generated by SOAPUI looks like:
>
> http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:mdc="http://webservices.sanoma-uitgevers.nl/AdvPortal/MDC/";
> xmlns:sch="
> http://schemas.sanoma-uitgevers.nl/AdvPortal/MDC/SchemaOrderInfoRequestWeb
> ">
>
>
>   
>  
> 135756.010
>  
>   
>
> 
>
> This works out of the box.
>
> The difference seems to be that SOAPUI declares all namespaces in the
> Envelope tag, and Axis does not.
> Also the Axis generated message does not include a namespace(prefix) on the
> OrderInfo tag.
>
> No matter what I try the Axis generated client does not work.
>
> Any idea?
>
> Thanks for your help,
>
> Harm!
>
>
>
> On Tue, Oct 14, 2008 at 3:57 PM, keith chapman <[EMAIL PROTECTED]>wrote:
>
>> Looking at the WSDL it looks like a correct message should be of the form.
>>
>> http://www.w3.org/2003/05/soap-envelope
>> ">
>>
>>   http://webservices.sanoma-uitgevers.nl/AdvPortal/MDC/";>
>>  http://schemas.sanoma-uitgevers.nl/AdvPortal/MDC/SchemaOrderInfoRequestWeb
>> ">
>> 123456.123
>>  
>>   
>>
>> 
>>
>> Could you a sample message generated using SOAPUI.
>>
>> Thanks,
>> Keith.
>>
>>
>> On Tue, Oct 14, 2008 at 6:52 PM, Harm de Laat <[EMAIL PROTECTED]> wrote:
>>
>>> Here is the complete WSDL file (I just commented out the IP address for
>>> the service).
>>>
>>> What may be worth of mentioning is that I tried using SOAPUI, which
>>> worked instantly with this specific WSDL.
>>>
>>>
>>> 
>>> http://schemas.xmlsoap.org/wsdl/soap/";
>>> xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/"; xmlns:soapenc="
>>> http://schemas.xmlsoap.org/soap/encoding/"; xmlns:mime="
>>> http://schemas.xmlsoap.org/wsdl/mime/"; xmlns:tns="
>>> http://webservices.sanoma-uitgevers.nl/AdvPortal/MDC/"; xmlns:s1="
>>> http://schemas.sanoma-uitgevers.nl/AdvPortal/MDC/SchemaOrderInfoRequestWeb";
>>> xmlns:s="http://www.w3.org/2001/XMLSchema"; xmlns:s2="
>>> http://schemas.sanoma-uitgevers.nl/AdvPortal/MDC/SchemaOrderInfoResultWeb";
>>> xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"; xmlns:http="
>>> http://schemas.xmlsoap.org/wsdl/http/"; targetNamespace="
>>> http://webservices.sanoma-uitgevers.nl/AdvPortal/MDC/"; xmlns:wsdl="
>>> http://schemas.xmlsoap.org/wsdl/";>
>>>   http://schemas.xmlsoap.org/wsdl/";>BizTalk
>>> assembly "Sanoma.BizTalk.AdvertentiePortal.MDC, Version=1.0.0.0,
>>> Culture=neutral, PublicKeyToken=8c063b3a22630ca9" published web
>>> service.
>>>   
>>> http://webservices.sanoma-uitgevers.nl/AdvPortal/MDC/";>
>>>   http://schemas.sanoma-uitgevers.nl/AdvPortal/MDC/SchemaOrderInfoRequestWeb";
>>> />
>>>   http://schemas.sanoma-uitgevers.nl/AdvPortal/MDC/SchemaOrderInfoResultWeb";
>>> />
>>>   
>>> 
>>>   
>>> 
>>>   
>>> 
>>>   
>>>   
>>> 
>>>   
>>> >> ref="s2:OrderInfoResult" />
>>>   
>>> 
>>>   
>>> 
>>> http://schemas.sanoma-uitgevers.nl/AdvPortal/MDC/SchemaOrderInfoRequestWeb
>>> ">
>>>   
>>> 
>>>   
>>> >> name="Referentienummer" type="s:string" />
>>>   
>>> 
>>>   
>>> 
>>> http://schemas.sanoma-uitgevers.nl/AdvPortal/MDC/SchemaOrderInfoResultWeb
>>> ">
>>>   
>>> 
>>>   
>>> >> name="Referentienr" type="s:string" />
>>> >> name="NameAdvertiser" type="s:string" />
>>> >> name="TypeOfAd" type="s:string" />
>>> >> name="titleId" type="s:string" />
>>> >> name="editionId" type="s:string" />
>>> >> name="orderStatus" type="s:integer" />
>>> >> name="returnCode" type="s:integer" />
>>> >> name="returnMessage" type="s:string" />
>>>   
>>> 
>>>   
>>> 
>>>   
>>>   
>>> 
>>>   
>>>   
>>> 
>>>   
>>>   >> name="WebService_Sanoma_BizTalk_AdvertentiePortal_MDCSoap">
>>> 
>>>   
>>>   
>>> 
>>>   
>>>   >> name="WebService_Sanoma_BizTalk_AdvertentiePortal_MDCSoap"
>>> type="tns:WebService_Sanoma_BizTalk_AdvertentiePortal_MDCSoap">
>>> http://schemas.xmlsoap.org/soap/http"; />
>>> 
>>>   http://webservices.sanoma-uitgevers.nl/AdvPortal/MDC/WebService_Sanoma_BizTalk_AdvertentiePortal_MDC/GetOrderDetails";
>>> style="document" />
>>>   
>>> 
>>>   
>>>   
>>> 
>>>   
>>> 
>>>   
>>>   >> name="WebService_Sanoma_BizTalk_AdvertentiePortal_MDCSoap12"
>>> type="tns:WebService_Sanoma_BizTalk_AdvertentiePortal_MDCSoap">
>>> http://schemas.xmlsoap.org/soap/http"; />
>>> 
>>>   http://webservices.sanoma-uitgevers.nl/AdvPortal/MDC/WebService_Sanoma_BizTalk_AdvertentiePortal_MDC/GetOrderDetails";
>>> style="document"

Re: FW: Integrating Axis2 with Tomcat and Eclipse

2008-10-15 Thread Bai Shen

I managed to complete the tutorial, and figured out how to set my default
environment to Axis2.

However, now I want to configure Axis2 to use Rampart so I can do security.

Firstly, the link on the Axis2 page directs me to Rampart 1.1.  I finally
found a link to the modules from the page that lead to Rampart 1.3.  Is that
the most current version?

Secondly, how do I add Rampart to the Axis2/Eclipse setup I currently have?
All I did to configure Axis2 was point Eclipse at the runtime. What I've
seen so far tells me to drop Rampart in a WEB-INF sub.  Is that the only
way, or can I configure it to be automatically added for all projects?

TIA.

Bai Shen

On Thu, Oct 2, 2008 at 8:48 PM, Bai Shen <[EMAIL PROTECTED]> wrote:

> I found out what the problem was.  Apparently when creating a web service,
> you can choose between Axis and Axis2.  I didn't realize this and it was
> defaulting to Axis.  So that got rid of the adminservice issue.
>
> I ran into a couple other problems, but I haven't had a chance to figure
> them out yet.
>
>
> On Thu, Oct 2, 2008 at 1:45 PM, Bai Shen <[EMAIL PROTECTED]> wrote:
>
>> The Axis2_Test path is from the name of my project.  Apparently, when
>> using an integrated Tomcat it puts the name of the project in the url to
>> differentiate from the various things you have running.
>>
>> I can still pull up the service list, etc, so Axis2 is working correctly.
>> It just doesn't seem to have an Admin service.
>>
>> As for the war, I didn't install that.  I simply pointed Eclipse at the
>> Axis2 binary files as mentioned in the beginning of the first link that
>> Markus posted.
>> Eclipse WTP Tutorials - Creating Top Down Web Service via Apache 
>> Axis2
>>
>> I do have a log files directory.  However, as I mentioned, I didn't have
>> any log files written to it.
>>
>> In my services dir under WEB-INF I only have a version service.
>>
>> I think I'm gonna try pointing Eclipse at the war version of Axis2 and see
>> if that changes things.
>>
>>
>> On Thu, Oct 2, 2008 at 1:01 PM, Barry Alexander <[EMAIL PROTECTED]>wrote:
>>
>>>  I tried to reply to the axis-user list but it kept bouncing…So I'll try
>>> sending directly:
>>>
>>>
>>>
>>> I have installed Tomcat stand alone (outside of Eclipse) so that explains
>>> my install path.  I would imagine even with embedded in Eclipse, there
>>> should be logs files written somewhere on Tomcat statrtup.  Sorry I am not
>>> familiar with embedded Tomcat.
>>>
>>>
>>>
>>> Shouldn't your endpoint address be something like
>>> http://localhost:8080/axis2/services/listServices ?
>>>
>>>
>>>
>>> Yours has "Axis2_Test" in place of axis2.  How did you install your
>>> axis2.war in Tomcat?
>>>
>>>
>>>
>>> What is your directory under Tomcat 6.0\webapps look like?
>>>
>>>
>>>
>>> This is what mine looks like: ..\Tomcat
>>> 6.0\webapps\axis2\WEB-INF\services\services.list
>>>
>>>
>>> 
>>>   \
>>> version-1.4.1.aar
>>>
>>>
>>>
>>>
>>>
>>> *From:* Bai Shen [mailto:[EMAIL PROTECTED]
>>> *Sent:* Thursday, October 02, 2008 7:17 AM
>>>
>>> *To:* axis-user@ws.apache.org
>>> *Subject:* Re: Integrating Axis2 with Tomcat and Eclipse
>>>
>>>
>>>
>>> I'm not sure where you got that install path.  I've never seen that in
>>> any setup of Tomcat that I've done.
>>>
>>> Anyways, I'm running Tomcat integrated into Eclipse along with Axis2.  So
>>> the log files aren't in the normal spot.  I looked in the temp dir that
>>> Eclipse created, and there were no log files there either.  The console
>>> doesn't contain any reference to the AdminService.
>>>
>>> So I'm not sure what the deal is.  The only thing I noticed out of place
>>> in the console was this.
>>>
>>> [ERROR] Unable to find config file.  Creating new servlet engine config
>>> file: /WEB-INF/server-config.wsdd
>>>
>>>  On Wed, Oct 1, 2008 at 5:47 PM, Barry Alexander <
>>> [EMAIL PROTECTED]> wrote:
>>>
>>> Can you take a look in your Tomcat logs directory for recent logs for any
>>> issues reported there.  Path should be [installDIr]\Apache Software
>>> Foundation\Tomcat 6.0\logs
>>>
>>>
>>>
>>> You should see [INFO] entry for whether your AdminService was/was not
>>> deployed
>>>
>>>
>>>
>>> *From:* Bai Shen [mailto:[EMAIL PROTECTED]
>>> *Sent:* Wednesday, October 01, 2008 1:45 PM
>>>
>>>
>>> *To:* axis-user@ws.apache.org
>>> *Subject:* Re: Integrating Axis2 with Tomcat and Eclipse
>>>
>>>
>>>
>>> Okay, that worked.  Thanks.
>>>
>>> However, I didn't see any way to enable AdminService.  Any ideas on that?
>>>
>>> On Wed, Oct 1, 2008 at 3:47 PM, Barry Alexander <[EMAIL PROTECTED]>
>>> wrote:
>>>
>>> >>
>>>
>>>
>>> * * *admin*
>>>
>>> * * *axis2*
>>>
>>>
>>>
>>> Ch
>>>
>>>
>>>
>>> *From:* Bai Shen [mailto:[EMAIL PROTECTED]
>>> *Sent:* Wednesday, October 01, 2008 12:35 PM
>>> *To:* axis-user@ws.apache.org
>>> *Subj

Re: Difference between SOAP 1.1, SOAP 1.2 and SOAP HTTP

2008-10-15 Thread Bai Shen

I looked at the wsdl again, and there's literally no difference.  As far as
I can tell, they both reference the same namespace.

On Wed, Oct 15, 2008 at 2:00 PM, keith chapman <[EMAIL PROTECTED]>wrote:

> The SOAP 1.1 and SOAP 1.2 Bindings look identical but they have a small
> difference. They indicate to the client what SOAP version to use. If you
> generate a client specifying the endpoint it will generate it so that the
> message generated by the client would match the requirements specified in
> the corresponding binding. You could differentiate between SOAP 1.1 and 1.2
> using the namespace.
>
> SOAP 1.2 namespace is http://www.w3.org/2003/05/soap-envelope while SOAP
> 1.1 namespace is http://schemas.xmlsoap.org/soap/envelope/
>
> Thanks,
> Keith.
>
> On Wed, Oct 15, 2008 at 11:14 PM, Bai Shen <[EMAIL PROTECTED]>wrote:
>
>> I created a java class, and then used Axis2 to create a web service from
>> that. However, in the WSDL, it created three connections.  A SOAP 1.1, a
>> SOAP 1.2, and a SOAP HTTP.  The SOAP 1.1 and SOAP 1.2 ones look identical to
>> me.  So I was wondering what the difference was. And is there a need for
>> them?  How does Axis2 know whether it's a 1.1 or 1.2?  TIA.
>>
>> Bai Shen
>>
>
>
>
> --
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
>

Clustering

2008-10-15 Thread Igor Nogueira

Guys with Axis2 clusering is it possible to build passive or active
replication schemas? Or both? ;-)

Best Regards,

Igor Nogueira Santos

Re: Out Only MEP and Rest support

2008-10-15 Thread keith chapman

Perhaps having a look at this article  [1]
would explain to you how REST works in Axis2.

Thanks,
Keith.

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

On Wed, Oct 15, 2008 at 11:20 PM, Barry Alexander <[EMAIL PROTECTED]
> wrote:

> After send this
> http://localhost:8080/axis2/services/ActiveService/register?notifyEpr=http://localhost:8080/axis2/services/ClientServic
>
> I see this in the tomcat logs:
>
> [ERROR] The endpoint reference (EPR) for the Operation not found is
> /axis2/services/ActiveService/register?notifyEpr=
> http://localhost:8080/axis2/services/ClientService and the WSA Action =
> null
> org.apache.axis2.AxisFault: The endpoint reference (EPR) for the Operation
> not found is /axis2/services/ActiveService/register?notifyEpr=
> http://localhost:8080/axis2/services/ClientService and the WSA Action =
> null
> at
> org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:89)
> at org.apache.axis2.engine.Phase.invoke(Phase.java:333)
> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:264)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:163)
> at
> org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine(RESTUtil.java:136)
> at
> org.apache.axis2.transport.http.util.RESTUtil.processURLRequest(RESTUtil.java:130)
> at
> org.apache.axis2.transport.http.AxisServlet$RestRequestProcessor.processURLRequest(AxisServlet.java:829)
> at
> org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:255)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
> at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
> at
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
> at
> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
> at java.lang.Thread.run(Unknown Source)
>
>
>
> On Wed, Oct 15, 2008 at 10:02 AM, Barry Alexander <
> [EMAIL PROTECTED]> wrote:
>
>> Hi Axis2 users,
>>
>>
>>
>> I am trying the sample application at http://wso2.org/library/406 and
>> have a few questions:
>>
>>
>>
>> 1)  I have built and successfully deployed the two mentioned services
>> in the sample referenced above (ActiveService and ClientService), when
>> attempting to register with
>> http://localhost:8080/axis2/rest/ActiveService?register?notifyEpr=http://localhost:8080/axis2/services/ClientServiceI
>>  get "Requested resource not found!"
>>
>> 2)  I modified the axis2.xml as follows:
>>
>> 
>>
>> 
>>
>> 
>>
>> 
>>
>> rest
>>
>>
>>
>>
>>
>>false
>>
>> This seemed to have no effect.
>>
>>
>>
>> How do I enable the 'rest' url to register my client service?
>>
>> Environment details:
>>
>>
>> Axis2 Happiness Page
>> Examining webapp configuration
>> Essential Components
>> Found Apache-Axis (org.apache.axis2.transport.http.AxisServlet)
>>   at C:\Program Files\Apache Software Foundation\Tomcat
>> 6.0\webapps\axis2\WEB-INF\lib\axis2-kernel-1.4.1.jar
>> Found Jakarta-Commons Logging (org.apache.commons.logging.Log)
>>   at C:\Program Files\Apache Software Foundation\Tomcat
>> 6.0\webapps\axis2\WEB-INF\lib\commons-logging-1.1.1.jar
>> Found Streaming API for XML (javax.xml.stream.XMLStreamReader)
>>   at an unknown location
>> Found Streaming API for XML implementation
>> (org.codehaus.stax2.XMLStreamWriter2)
>>   at C:\Program Files\Apache Software Foundation\Tomcat
>> 6.0\webapps\axis2\WEB-INF\lib\wstx-asl-3.2.4.jar
>> The core axis2 libraries are present.
>> Note: Even if everything this page probes for is present, there is no
>> guarantee your Axis Service will work, because there are many configuration
>> options that we do not check for. These tests are necessary but not
>> sufficient
>> Examining Version Service
>> Found Axis2 default Version service and Axis2 is working properly.
>> Now you can drop a service archive in axis2/WEB-INF/services. Following
>> output was produced while invoking Axis2 version service
>> Hello I am Axis2 version service , My version is 1.4.1
>> Examining Application Server
>> Servlet version 2.5
>> Platform Apa

Re: Difference between SOAP 1.1, SOAP 1.2 and SOAP HTTP

2008-10-15 Thread keith chapman

The SOAP 1.1 and SOAP 1.2 Bindings look identical but they have a small
difference. They indicate to the client what SOAP version to use. If you
generate a client specifying the endpoint it will generate it so that the
message generated by the client would match the requirements specified in
the corresponding binding. You could differentiate between SOAP 1.1 and 1.2
using the namespace.

SOAP 1.2 namespace is http://www.w3.org/2003/05/soap-envelope while SOAP 1.1
namespace is http://schemas.xmlsoap.org/soap/envelope/

Thanks,
Keith.

On Wed, Oct 15, 2008 at 11:14 PM, Bai Shen <[EMAIL PROTECTED]> wrote:

> I created a java class, and then used Axis2 to create a web service from
> that. However, in the WSDL, it created three connections.  A SOAP 1.1, a
> SOAP 1.2, and a SOAP HTTP.  The SOAP 1.1 and SOAP 1.2 ones look identical to
> me.  So I was wondering what the difference was. And is there a need for
> them?  How does Axis2 know whether it's a 1.1 or 1.2?  TIA.
>
> Bai Shen
>

-- 
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org

Re: Out Only MEP and Rest support

2008-10-15 Thread Barry Alexander

After send this
http://localhost:8080/axis2/services/ActiveService/register?notifyEpr=http://localhost:8080/axis2/services/ClientServic

I see this in the tomcat logs:

[ERROR] The endpoint reference (EPR) for the Operation not found is
/axis2/services/ActiveService/register?notifyEpr=
http://localhost:8080/axis2/services/ClientService and the WSA Action = null
org.apache.axis2.AxisFault: The endpoint reference (EPR) for the Operation
not found is /axis2/services/ActiveService/register?notifyEpr=
http://localhost:8080/axis2/services/ClientService and the WSA Action = null
at
org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:89)
at org.apache.axis2.engine.Phase.invoke(Phase.java:333)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:264)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:163)
at
org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine(RESTUtil.java:136)
at
org.apache.axis2.transport.http.util.RESTUtil.processURLRequest(RESTUtil.java:130)
at
org.apache.axis2.transport.http.AxisServlet$RestRequestProcessor.processURLRequest(AxisServlet.java:829)
at
org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:255)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Unknown Source)


On Wed, Oct 15, 2008 at 10:02 AM, Barry Alexander <[EMAIL PROTECTED]
> wrote:

> Hi Axis2 users,
>
>
>
> I am trying the sample application at http://wso2.org/library/406 and have
> a few questions:
>
>
>
> 1)  I have built and successfully deployed the two mentioned services
> in the sample referenced above (ActiveService and ClientService), when
> attempting to register with
> http://localhost:8080/axis2/rest/ActiveService?register?notifyEpr=http://localhost:8080/axis2/services/ClientServiceI
>  get "Requested resource not found!"
>
> 2)  I modified the axis2.xml as follows:
>
> 
>
> 
>
> 
>
> 
>
> rest
>
>
>
>
>
>false
>
> This seemed to have no effect.
>
>
>
> How do I enable the 'rest' url to register my client service?
>
> Environment details:
>
>
> Axis2 Happiness Page
> Examining webapp configuration
> Essential Components
> Found Apache-Axis (org.apache.axis2.transport.http.AxisServlet)
>   at C:\Program Files\Apache Software Foundation\Tomcat
> 6.0\webapps\axis2\WEB-INF\lib\axis2-kernel-1.4.1.jar
> Found Jakarta-Commons Logging (org.apache.commons.logging.Log)
>   at C:\Program Files\Apache Software Foundation\Tomcat
> 6.0\webapps\axis2\WEB-INF\lib\commons-logging-1.1.1.jar
> Found Streaming API for XML (javax.xml.stream.XMLStreamReader)
>   at an unknown location
> Found Streaming API for XML implementation
> (org.codehaus.stax2.XMLStreamWriter2)
>   at C:\Program Files\Apache Software Foundation\Tomcat
> 6.0\webapps\axis2\WEB-INF\lib\wstx-asl-3.2.4.jar
> The core axis2 libraries are present.
> Note: Even if everything this page probes for is present, there is no
> guarantee your Axis Service will work, because there are many configuration
> options that we do not check for. These tests are necessary but not
> sufficient
> Examining Version Service
> Found Axis2 default Version service and Axis2 is working properly.
> Now you can drop a service archive in axis2/WEB-INF/services. Following
> output was produced while invoking Axis2 version service
> Hello I am Axis2 version service , My version is 1.4.1
> Examining Application Server
> Servlet version 2.5
> Platform Apache Tomcat/6.0.16
>
> Examining System Properties
> java.runtime.name Java(TM) SE Runtime Environment
>
> sun.boot.library.path C: \Program Files\Java\jre1.6.0_05\bin
>
> java.vm.version 10.0-b19
>
> shared.loader
>
> java.vm.vendor Sun Microsystems Inc.
>
> java.vendor.url http: //java.sun.com/
>
> path.separator ;
>
> java.vm.name Java HotSpot(TM) Client VM
>
> tomcat.util.buf.StringCache.byte.enabled true
>
> file.encodin

Difference between SOAP 1.1, SOAP 1.2 and SOAP HTTP

2008-10-15 Thread Bai Shen

I created a java class, and then used Axis2 to create a web service from
that. However, in the WSDL, it created three connections.  A SOAP 1.1, a
SOAP 1.2, and a SOAP HTTP.  The SOAP 1.1 and SOAP 1.2 ones look identical to
me.  So I was wondering what the difference was. And is there a need for
them?  How does Axis2 know whether it's a 1.1 or 1.2?  TIA.

Bai Shen

Re: In-flow request insertion

2008-10-15 Thread Igor Nogueira

> I am not clear about your requirement. But may be looking at Axis2
> clustering would be usefull to you.
>
>
>   Amila, Basically I want to do this: I have several services distributed
on several servers. Only one of them will process client's requests- the
primary one. If the primary fails, then one of the sleeping replicas will be
elected as the new primary and will respond to the client's invocations from
this moment on. My problem is: If the primary fails processing a specific
client's invocation   the new elected primary must be aware of the client's
address in order to process and answer this request. On the next requests
the client will invoke the new functional primary, so there's no problem.
 On clustering used by Axis, all requests are spread to all replicas, ins't
it? In passive replication, only primary receives client's requests while
the replicas sleep. If the primary fails, a replica will be elected new
primary

Thanks!

Out Only MEP and Rest support

2008-10-15 Thread Barry Alexander

Hi Axis2 users,



I am trying the sample application at http://wso2.org/library/406 and have a
few questions:



1)  I have built and successfully deployed the two mentioned services in
the sample referenced above (ActiveService and ClientService), when
attempting to register with
http://localhost:8080/axis2/rest/ActiveService?register?notifyEpr=http://localhost:8080/axis2/services/ClientServiceI
get "Requested resource not found!"

2)  I modified the axis2.xml as follows:









rest



   

   false

This seemed to have no effect.



How do I enable the 'rest' url to register my client service?

Environment details:


Axis2 Happiness Page
Examining webapp configuration
Essential Components
Found Apache-Axis (org.apache.axis2.transport.http.AxisServlet)
  at C:\Program Files\Apache Software Foundation\Tomcat
6.0\webapps\axis2\WEB-INF\lib\axis2-kernel-1.4.1.jar
Found Jakarta-Commons Logging (org.apache.commons.logging.Log)
  at C:\Program Files\Apache Software Foundation\Tomcat
6.0\webapps\axis2\WEB-INF\lib\commons-logging-1.1.1.jar
Found Streaming API for XML (javax.xml.stream.XMLStreamReader)
  at an unknown location
Found Streaming API for XML implementation
(org.codehaus.stax2.XMLStreamWriter2)
  at C:\Program Files\Apache Software Foundation\Tomcat
6.0\webapps\axis2\WEB-INF\lib\wstx-asl-3.2.4.jar
The core axis2 libraries are present.
Note: Even if everything this page probes for is present, there is no
guarantee your Axis Service will work, because there are many configuration
options that we do not check for. These tests are necessary but not
sufficient
Examining Version Service
Found Axis2 default Version service and Axis2 is working properly.
Now you can drop a service archive in axis2/WEB-INF/services. Following
output was produced while invoking Axis2 version service
Hello I am Axis2 version service , My version is 1.4.1
Examining Application Server
Servlet version 2.5
Platform Apache Tomcat/6.0.16

Examining System Properties
java.runtime.name Java(TM) SE Runtime Environment

sun.boot.library.path C: \Program Files\Java\jre1.6.0_05\bin

java.vm.version 10.0-b19

shared.loader

java.vm.vendor Sun Microsystems Inc.

java.vendor.url http: //java.sun.com/

path.separator ;

java.vm.name Java HotSpot(TM) Client VM

tomcat.util.buf.StringCache.byte.enabled true

file.encoding.pkg sun.io

java.util.logging.config.file C: \Program Files\Apache Software
Foundation\Tomcat 6.0\conf\logging.properties

user.country US

sun.os.patch.level Service Pack 2

java.vm.specification.name Java Virtual Machine Specification

user.dir C: \Program Files\Apache Software Foundation\Tomcat 6.0

java.runtime.version 1.6.0_05-b13

java.awt.graphicsenv sun.awt.Win32GraphicsEnvironment

java.endorsed.dirs C: \Program Files\Apache Software Foundation\Tomcat
6.0\common\endorsed

os.arch x86

java.io.tmpdir C: \Program Files\Apache Software Foundation\Tomcat 6.0\temp


line.separator

java.vm.specification.vendor Sun Microsystems Inc.

user.variant

java.util.logging.manager org.apache.juli.ClassLoaderLogManager

java.naming.factory.url.pkgs org.apache.naming

os.name Windows XP

sun.jnu.encoding Cp1252

java.library.path C: \Program Files\Apache Software Foundation\Tomcat
6.0\bin;.;C: \WINDOWS1\Sun\Java\bin;C: \WINDOWS1\system32;C: \WINDOWS1;D:
\Program Files\Java\jdk1.5.0_15\bin;D: \axis\axis2-1.4.1\bin;c: \ruby\bin;C:
\Program Files\IBM\WebSphere MQ\Java\lib;C:
\OraHome_2\jre\1.4.2\bin\client;C: \OraHome_2\jre\1.4.2\bin;C:
\oracle\ora92\bin;C: \WINDOWS1\system32;C: \WINDOWS1;C:
\WINDOWS1\System32\Wbem;C: \Program Files\UltraEdit;C: \Program
Files\IBM\WebSphere MQ\bin;C: \Program Files\IBM\WebSphere
MQ\tools\c\samples\bin;"C: \Program
Files\Hummingbird\Connectivity\7.00\Accessories\";C: \Program
Files\Subversion\bin;C: \Program Files\Support Tools\;c: \Program
Files\Microsoft SQL Server\90\Tools\binn\;C: \Program Files\svnmerge;D:
\apache-ant-1.7.0\bin;D: \Sun\SDK\bin;C: \Program
Files\QuickTime\QTSystem\;D: \groovy\groovy-1.5.6\bin

java.specification.name Java Platform API Specification

java.class.version 50.0

sun.management.compiler HotSpot Client Compiler

os.version 5.1

user.home C: \

user.timezone America/Los_Angeles

catalina.useNaming true

java.awt.printerjob sun.awt.windows.WPrinterJob

java.specification.version 1.6

file.encoding Cp1252

catalina.home C: \Program Files\Apache Software Foundation\Tomcat 6.0

user.name SYSTEM

java.class.path C: \Program Files\Apache Software Foundation\Tomcat
6.0\bin\bootstrap.jar

java.naming.factory.initial org.apache.naming.java.javaURLContextFactory

package.definition
sun.,java.,org.apache.catalina.,org.apache.coyote.,org.apache.tomcat.,org.apache.jasper.


java.vm.specification.version 1.0

sun.arch.data.model 32

java.home C: \Program Files\Java\jre1.6.0_05

java.specification.vendor Sun Microsystems Inc.

user.language en

awt.toolkit sun.awt.windows.WToolkit

java.vm.info mixed mode, sharing

java.version 1.6.0_05

java.ext.dirs C:

Error on auto-generated wsdl using JAXWSDeployer...

2008-10-15 Thread silver17


Hi guys,

I've been looking at a standard way to develop web services that could
potentially be slightly more portable across multiple servers, and the best
way I've seen so far is to use JAX-WS annotations.

I created a simple java program in eclipse.  After that I export the project
as a jar file and deploy that jar to Axis2 1.4.  First I create the
servicejars folder in Axis2.  When I run Axis2 as a standalone server
(AXIS2_HOME/bin/Axis2Server.bat) it deploys and runs fine.

http://localhost:8080/axis2/services/CalculatorService.CalculatorPort?wsdl

However when I create the war file off the binary distribution, deploy that
to Tomcat 5.5 and export Calculator.jar to the servicejars folder i get an
error.  However if I issue the command:

http://localhost:8080/axis2/services/CalculatorService.CalculatorPort?wsdl2

It works fine on both the standalone axis2-1.4 as well as the deployed
webapp to tomcat 5.5.

Here's the Code:

package ca.math.calculator;

import javax.jws.WebMethod;
import javax.jws.WebService;

/**
 * Calculator service class.
 *
 */
@WebService(
name="Calculator",
serviceName="CalculatorService",
targetNamespace="http://ca/math/Calculator1";
)
public class Calculator {

/**
 * Adds two integers.
 * @param x first integer.
 * @param y second integer.
 * @return the sum of two integers.
 */
@WebMethod(operationName="add", action="urn:Add")
public int add(int x, int y) {
return x+y;
}

/**
 * Subtracts two integers.
 * @param x first integer.
 * @param y second integer.
 * @return the subtraction of two integers.
 */
@WebMethod(operationName="subtract", action="urn:Substract")
public int subtract(int x, int y) {
return x-y;
}

}

Here's the error:


Unable to generate WSDL 1.1 for this service

If you wish Axis2 to automatically generate the WSDL 1.1, then please +set
useOriginalwsdl as false in your services.xml

javax.xml.ws.WebServiceException: Error occurred generating WSDL file for
Web service implementation class {ca.gc.agr.math.calculator.Calculator}:
{java.lang.ClassNotFoundException:
com.sun.tools.ws.spi.WSToolsObjectFactory}
at
org.apache.axis2.jaxws.description.builder.JAXWSRIWSDLGenerator.generateWsdl(JAXWSRIWSDLGenerator.java:187)
at
org.apache.axis2.jaxws.description.builder.JAXWSRIWSDLGenerator.initialize(JAXWSRIWSDLGenerator.java:371)
at
org.apache.axis2.jaxws.description.builder.JAXWSRIWSDLGenerator.getWSDL(JAXWSRIWSDLGenerator.java:364)
at
org.apache.axis2.description.AxisService.printWSDL(AxisService.java:1322)
at
org.apache.axis2.transport.http.ListingAgent.processListService(ListingAgent.java:287)
at 
org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:242)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:627)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:875)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.ClassNotFoundException:
com.sun.tools.ws.spi.WSToolsObjectFactory
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1386)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1232)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:164)
at
org.apache.axis2.jaxws.description.builder.JAXWSRIWSDLGenerator.generateWsdl(JAXWSRIWSDLGenerator.java:166)
... 21 more



Cheers,

Bill
-- 
View this message in context: 
h

org.apache.axis2.AxisFault: com.ctc.wstx.exc.WstxParsingException: Expected a text token, got START_ELEMENT

2008-10-15 Thread Audino, Jeremy

I'm receiving the following exception when attempting to connect from my Axis2 
based client to a Axis 2/SimpleHTTPServer based server.

org.apache.axis2.AxisFault: com.ctc.wstx.exc.WstxParsingException: Expected a 
text token, got START_ELEMENT.
 at [row,col {unknown-source}]: [1,252]
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at com.philips.cirs.calculator.CalculatorStub.fromOM(Unknown Source)
at com.philips.cirs.calculator.CalculatorStub.add(Unknown Source)
at com.philips.cirs.calculator.CalculatorClient.main(Unknown Source)
Caused by: org.apache.axiom.om.impl.exception.OMStreamingException: 
com.ctc.wstx.exc.WstxParsingException: Expected a text token, got START_ELEMENT.
 at [row,col {unknown-source}]: [1,252]
at 
org.apache.axiom.om.impl.llom.OMStAXWrapper.getElementText(OMStAXWrapper.java:901)
at com.philips.cirs.calculator.IntReturn$Factory.parse(Unknown Source)
... 3 more
Caused by: com.ctc.wstx.exc.WstxParsingException: Expected a text token, got 
START_ELEMENT.
 at [row,col {unknown-source}]: [1,252]
at 
com.ctc.wstx.sr.StreamScanner.constructWfcException(StreamScanner.java:605)
at com.ctc.wstx.sr.StreamScanner.throwParseError(StreamScanner.java:461)
at 
com.ctc.wstx.sr.BasicStreamReader.getElementText(BasicStreamReader.java:677)
at 
org.apache.axiom.om.impl.llom.OMStAXWrapper.getElementText(OMStAXWrapper.java:899)
... 4 more

A gSoap server based from the sample WSDL works great with both the C++ and 
Java clients.

Any clue what might be happening? Do I have any errors in my WSDL?



Jeremy F. Audino
Senior Software Development Engineer
Philips Healthcare -- Nuclear Medicine
Tel: 440-483-7444
E-mail: [EMAIL PROTECTED]



The information contained in this message may be confidential and legally 
protected under applicable law. The message is intended solely for the 
addressee(s). If you are not the intended recipient, you are hereby notified 
that any use, forwarding, dissemination, or reproduction of this message is 
strictly prohibited and may be unlawful. If you are not the intended recipient, 
please contact the sender by return e-mail and destroy all copies of the 
original message.


calculator.wsdl
Description: calculator.wsdl


CalculatorServer.java
Description: CalculatorServer.java


CalculatorServer_SimpleAxisServer.java
Description: CalculatorServer_SimpleAxisServer.java


CalculatorClient.java
Description: CalculatorClient.java
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: SOAP-based web service question

2008-10-15 Thread Martin Gainty


Hi Chris

in $TOMCAT_HOME/webapps/axis2/axis2.xml you should see a port specifier such as

8080


Please ping users axis-user@ws.apache.org for further direction

Thanks,
Martin 
__ 
Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relates to the official business 
of Sender. This transmission is of a confidential nature and Sender does not 
endorse distribution to any party other than intended recipient. Sender does 
not necessarily endorse content contained within this transmission. 


> Subject: SOAP-based web service question
> Date: Wed, 15 Oct 2008 11:01:12 -0400
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> 
> Hello,
> 
> We'd like to do the following, and it *almost* works.  We want multiple
> ports serving multiple web applications, and following the various
> how-tos on the web we've got multiple Service/Connector/Engine/Host
> setups going.  This is Tomcat 5.5.16.
> 
> We've got regular web application 'A' served on port 8081.
> We've got a SOAP-based web service 'B' (based on web app 'A') served on
> port 8023.
> We've got a SOAP-based web service 'C' served on port 8054.
> 
> This all works, EXCEPT you can also access web service 'B' on port 8054,
> and you can access web service 'C' on port 8023.  It doesn't appear to
> care.
> 
> Any clues?  Is this segregation possible?
> 
>   Thanks!
>   --chris sterritt
> 
> -
> To start a new topic, e-mail: [EMAIL PROTECTED]
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

_
Stay up to date on your PC, the Web, and your mobile phone with Windows Live.
http://clk.atdmt.com/MRT/go/msnnkwxp1020093185mrt/direct/01/

Re: In-flow request insertion

2008-10-15 Thread Igor Nogueira

Thanks! I'm thinking about invoking the "normal" way from the handler
creating the serviceclient, options etc...But I just need the original's
client's address in order to send the response to the client and not to the
handler, got it? ;-) So on outflow I'd have to change the reply address form
the handler's address to the client's address...


Thank you very much!



2008/10/15 Amila Suriarachchi <[EMAIL PROTECTED]>

>
>
> On Tue, Oct 14, 2008 at 10:17 PM, Igor Nogueira <
> [EMAIL PROTECTED]> wrote:
>
>>
>> Actually I want to develop a passive replication schema, so I have the
>> handlers together in a group. If the Active member fails, I'll have to
>> re-invoke the message, but in another handler in another server. I'm
>> serializing the Messagecontext and moving it through the replicas, so when
>> a
>> fault is detected I'll invoke the message again, but in another service .
>> Is
>> there a way to do that?I tryed to use LocalTranportSender, but it returns
>> me
>> a nullexception error...I've opened another thread on the list about
>> it...if
>> you have time, could you take a lokk at it too? ;-)
>
>
> I am not clear about your requirement. But may be looking at Axis2
> clustering would be usefull to you.
>
> thanks,
> Amila.
>
>>
>>
>> Thanks again!!!,
>>
>> Igor Nogueira
>>
>>
>> Amila Suriarachchi wrote:
>> >
>> > On Mon, Oct 13, 2008 at 4:29 PM, Igor Nogueira
>> > <[EMAIL PROTECTED]
>> >> wrote:
>> >
>> >> Amila, thank you! I've tested what you said, but I've got this
>> exception:
>> >> "A message was added that is not valid. However, the operation context
>> >> was
>> >> complete."
>> >>
>> >
>> > this means it try to add an Axis2 Message to an operation context which
>> > already has required number of Axis2 messages. This may happen when it
>> > goes
>> > through the dispatches again.
>> >
>> >>
>> >> Here's the code I'm using:
>> >>
>> >> contextomensagem.setCurrentHandlerIndex(0);
>> >> contextomensagem.setCurrentPhaseIndex(0);
>> >> AxisEngine engine = new
>> >> AxisEngine(contextomensagem.getConfigurationContext());
>> >> try {
>> >> engine.receive(contextomensagem);
>> >>
>> > you can simply called . AxisEngine.receive() since this is a static
>> > method.
>> >
>> >>
>> >> } catch (AxisFault e1) {
>> >>
>> >> e1.printStackTrace();
>> >> return (e1.getReason());
>> >> }
>> >>
>> >> "contextomensagem" is a static variable that keeps a copy of the
>> >> MessageContext received at the invoke method. As I'm testing I didin't
>> >> change the SOAPEnvelope, I'm  just trying to re-send the same message.
>> Is
>> >> there something else to do?
>> >>
>> >
>> > Are you experimenting with Axis2 Engine or what do you try to archive?
>> why
>> > you want to send the same message twice?
>> >
>> > thanks,
>> > Amila.
>> >
>> >>
>> >>
>> >> Thanks!
>> >>
>> >
>> >
>> >
>> > --
>> > Amila Suriarachchi
>> > WSO2 Inc.
>> > blog: http://amilachinthaka.blogspot.com/
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/In-flow-request-insertion-tp19946886p19977558.html
>> Sent from the Axis - User mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>

Re: Help! How to get the XML data from a SOAP client and respond with a result XML file?

2008-10-15 Thread Amila Suriarachchi

On Wed, Oct 15, 2008 at 5:24 AM, Tian Chi <[EMAIL PROTECTED]> wrote:

> Hi all,
>
> I'm new at using Axis2. Don't know how to do this?
> Can anyone give me some guidance about this or tell me
> where to find examples/documents about this?
>
> Basically I need to provide a web service and the client program (a SOAP
> client not using Axis2) will post an XML file to the service. The service
> program should save the data in the XML file to my database and respond with
> result message to the client.
>
> I noticed in the Axis2 'Quick Start Guide', there's an example about
> building the service using AXIOM. I wonder if that's the way to do it.
>
> The function is like
>
>public OMElement getPrice(OMElement element) throws XMLStreamException {
>element.build();
>element.detach();
>
>OMElement symbolElement = element.getFirstElement();
>String symbol = symbolElement.getText();
>
>String returnText = "42";
>Double price = (Double) map.get(symbol);
>if(price != null){
>returnText  = "" + price.doubleValue();
>}
>OMFactory fac = OMAbstractFactory.getOMFactory();
>OMNamespace omNs =
>fac.createOMNamespace("
> http://axiom.service.quickstart.samples/xsd";, "tns");
>OMElement method = fac.createOMElement("getPriceResponse", omNs);
>OMElement value = fac.createOMElement("price", omNs);
>value.addChild(fac.createOMText(value, returnText));
>method.addChild(value);
>return method;
>}
>
> Does this mean the 'element' object is the XML element sent from the client
> program?

This is what comes under the SoapBody in your request in case it is soap
binding. for an HTTP binding this is the xml payload it has received.



>
>
> Also do I need to do anything else to write (OutputStream stuff) the
> returned object 'method' to the client?


No. Axis2 do it automatically.

thanks,
Amila.

>
>
> thanks in advance,
>
> -tian
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


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

Re: Difference between SOAP 1.1, SOAP 1.2 and SOAP HTTP

Re: Client address on messagecontext??

Re: Difference between SOAP 1.1, SOAP 1.2 and SOAP HTTP

Re: AXIS JAVA Client - JMS Transport Authenication

RE: Out Only MEP and Rest support

Re: Out Only MEP and Rest support

AXIS JAVA Client - JMS Transport Authenication

Strings and Axis2

Re: namespaces error

Re: FW: Integrating Axis2 with Tomcat and Eclipse

Re: Difference between SOAP 1.1, SOAP 1.2 and SOAP HTTP

Clustering

Re: Out Only MEP and Rest support

Re: Difference between SOAP 1.1, SOAP 1.2 and SOAP HTTP

Re: Out Only MEP and Rest support

Difference between SOAP 1.1, SOAP 1.2 and SOAP HTTP

Re: In-flow request insertion

Out Only MEP and Rest support

Error on auto-generated wsdl using JAXWSDeployer...

org.apache.axis2.AxisFault: com.ctc.wstx.exc.WstxParsingException: Expected a text token, got START_ELEMENT

RE: SOAP-based web service question

Re: In-flow request insertion

Re: Help! How to get the XML data from a SOAP client and respond with a result XML file?

23 matches

Site Navigation

Mail list logo

Footer information