Re: Bug in "Code Generator Wizard - Eclipse Plug-in"

[Saminda Wijeratne]

What is the jdk version u r using? I remember some users were unable to 
get the problem fixed until they switched to jdk 1.6.


Saminda

Car Toper wrote:

On Tue, Feb 24, 2009 at 12:03 AM, Saminda Wijeratne  wrote:
  

Did you follow whats in
http://www.mail-archive.com/axis-user@ws.apache.org/msg43620.html ??



I tried, I ran eclipse with the -clean command line option and I am
still getting the error.

  

RE: Document/Literal - Handwritten wsdl? Method signature OMELement?

[Attharkar, Asmita]

Hi Guo,

My problem is not about which approach I should follow.
The question is when I using the document/literal can I have a method whose 
signature is String myWebServiceMethod(String, String, String).
If not, and I need to use the method OMElement myWebServiceMethod(OMElement) 
and I need to publish my wsdl how can I tell the web service users that my web 
service needs those three String values and it will return a response that has 
String.

If I need to edit wsdl manually, how do I do it?

Thanks,
Asmita

From: Guo Tianchong [gu...@nec-as.nec.com.cn]
Sent: Tuesday, February 24, 2009 10:50 PM
To: axis-user@ws.apache.org
Subject: Re: Document/Literal - Handwritten wsdl? Method signature OMELement?

hi Asmita,

Your senario seems :
1. write java code
2. java2wsdl
3. publish your wsdl generated by step2.

Is it right?

I met the same confusion ago.
I also created my service by axiom databinding ago.
The generated wsdl in the URL (?wsdl) is xs:anytype and return type is also 
xs:anytype.

It seems that Axis2 will identify OMElement as Object.
and it is xs:anytype in URL (?wsdl).

I'm still not know how to resolve the problem.

but how about the following?
1. write wsdl
2. wsdl2java
3. publish your wsdl generated by step1.


Guo.

- Original Message -
From: Attharkar, Asmita
To: axis-user@ws.apache.org
Sent: Wednesday, February 25, 2009 6:37 AM
Subject: Document/Literal - Handwritten wsdl? Method signature OMELement?

Hi,

 I need to use Document/Literal style in my web service.

My web service needs few (say three) strings from client. The Web service needs 
to send a String back to the client.

I am looking at web service method signature now.

Is it true that the only option I have when using document/literal  my method 
will look something like this? OMElement myWebService (OMElement 
requestElement).

I can add the three parameters needed by the web service to the requestElement 
as its child elements.

The problem now is the wsdl.

When I see the generated wsdl in the URL (?wsdl) I see that xs:anytype is the 
only parameter taken into the webservice and return type is also xs:anytype.

How will my web service client know what exactly are those three parameters and 
what should be their names and what should he be seeing in the return type.

I checked few forum entries and it says that I need to handwrite my wsdl? Is it 
true?

Is there a way that I can automatically generate the wsdl which indicates all 
the parameters needed by my webservice as well as the return String.?

Is there a way that I am implementing RawXMLINOutMessageReceiver but my method 
signature can have the distinct three parameters as separate method arguments?

If not how will I publish my wsdl which explains the parameters and return type 
String to the outside world.

This one is very urgent. My code is ready but now I need to publish my wsdl for 
the world.

I am using ant script to generate the wsdl but I get the error:

java.lang.RuntimeException: java.lang.ClassCastException: 
org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver cannot be cast to 
org.apache.axis2.engine.MessageReceiver




Thanks,
Asmita



(Tel) 732-699-4657 | 4B566 | Telcordia Technologies | Piscataway NJ 08854

Re: Document/Literal - Handwritten wsdl? Method signature OMELement?

[Guo Tianchong]

hi Asmita,

Your senario seems :
1. write java code
2. java2wsdl
3. publish your wsdl generated by step2.

Is it right?

I met the same confusion ago.
I also created my service by axiom databinding ago.
The generated wsdl in the URL (?wsdl) is xs:anytype and return type is also 
xs:anytype.

It seems that Axis2 will identify OMElement as Object.
and it is xs:anytype in URL (?wsdl).

I'm still not know how to resolve the problem.

but how about the following?
1. write wsdl
2. wsdl2java
3. publish your wsdl generated by step1.


Guo.

  - Original Message - 
  From: Attharkar, Asmita
  To: axis-user@ws.apache.org
  Sent: Wednesday, February 25, 2009 6:37 AM
  Subject: Document/Literal - Handwritten wsdl? Method signature OMELement?


  Hi,



   I need to use Document/Literal style in my web service.



  My web service needs few (say three) strings from client. The Web service 
needs to send a String back to the client.



  I am looking at web service method signature now.



  Is it true that the only option I have when using document/literal  my method 
will look something like this? OMElement 
myWebService (OMElement requestElement).



  I can add the three parameters needed by the web service to the 
requestElement as its child elements.



  The problem now is the wsdl.



  When I see the generated wsdl in the URL (?wsdl) I see that xs:anytype is the 
only parameter taken into the webservice and return 
type is also xs:anytype.



  How will my web service client know what exactly are those three parameters 
and what should be their names and what should he be 
seeing in the return type.



  I checked few forum entries and it says that I need to handwrite my wsdl? Is 
it true?



  Is there a way that I can automatically generate the wsdl which indicates all 
the parameters needed by my webservice as well as 
the return String.?



  Is there a way that I am implementing RawXMLINOutMessageReceiver but my 
method signature can have the distinct three parameters as 
separate method arguments?



  If not how will I publish my wsdl which explains the parameters and return 
type String to the outside world.



  This one is very urgent. My code is ready but now I need to publish my wsdl 
for the world.



  I am using ant script to generate the wsdl but I get the error:



  java.lang.RuntimeException: java.lang.ClassCastException: 
org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver cannot be cast to 
org.apache.axis2.engine.MessageReceiver









  Thanks,

  Asmita






--

  (Tel) 732-699-4657 | 4B566 | Telcordia Technologies | Piscataway NJ 08854

Re: Bug in "Code Generator Wizard - Eclipse Plug-in"

[Car Toper]

On Tue, Feb 24, 2009 at 12:03 AM, Saminda Wijeratne  wrote:
> Did you follow whats in
> http://www.mail-archive.com/axis-user@ws.apache.org/msg43620.html ??

I tried, I ran eclipse with the -clean command line option and I am
still getting the error.

location of tcpmon.class

[robert rowntree]

i downloaded axis 2  1.4.1 and scanned the lib directory for some jar 
containing 'tcpmon' or 'org.apache.axis.utils.tcpmon'

where is it now?

there is no longer an 'axis.jar' in the download. 

Document/Literal - Handwritten wsdl? Method signature OMELement?

[Attharkar, Asmita]

Hi,

 I need to use Document/Literal style in my web service.

My web service needs few (say three) strings from client. The Web service needs 
to send a String back to the client.

I am looking at web service method signature now.

Is it true that the only option I have when using document/literal  my method 
will look something like this? OMElement myWebService (OMElement 
requestElement).

I can add the three parameters needed by the web service to the requestElement 
as its child elements.

The problem now is the wsdl.

When I see the generated wsdl in the URL (?wsdl) I see that xs:anytype is the 
only parameter taken into the webservice and return type is also xs:anytype.

How will my web service client know what exactly are those three parameters and 
what should be their names and what should he be seeing in the return type.

I checked few forum entries and it says that I need to handwrite my wsdl? Is it 
true?

Is there a way that I can automatically generate the wsdl which indicates all 
the parameters needed by my webservice as well as the return String.?

Is there a way that I am implementing RawXMLINOutMessageReceiver but my method 
signature can have the distinct three parameters as separate method arguments?

If not how will I publish my wsdl which explains the parameters and return type 
String to the outside world.

This one is very urgent. My code is ready but now I need to publish my wsdl for 
the world.

I am using ant script to generate the wsdl but I get the error:

java.lang.RuntimeException: java.lang.ClassCastException: 
org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver cannot be cast to 
org.apache.axis2.engine.MessageReceiver




Thanks,
Asmita



(Tel) 732-699-4657 | 4B566 | Telcordia Technologies | Piscataway NJ 08854

Re: Pub\Sub Web Service

[Asanka Abeysinghe]

Hi Mike,
Apache Savan/Java [1] implements the WS-Eventing specification and 
brings the pub/sub capability to WS.  Savan can engage as a module to 
Axis2. You can find more information from links [1] [2].

Thx
- Asanka

[1] http://ws.apache.org/savan/source-repository.html
[2] http://blog.facilelogin.com/2008/10/ws-eventing-with-savan.html
[3] http://blog.facilelogin.com/2008/10/savan-behind-scene.html

Michael wrote:

Doug
 
I looked at this before I started my design.  As a standards document 
it did not provide much help with how I might implement the standard 
in a bottom-up Java web service implementation.  The only thing I 
could get out of it is that one other option I did not list in my 
original email was to send the notification back to the client as a 
SOAP message I would construct dynamically from my Java server side 
code and use the WS-Addressing endpoint that I could extract from the 
SOAP message the client sent when they subscribed.
 
Is that what you are suggesting by recommending this specification?
 
Mike


- Original Message -
*From:* Doug Davis 
*To:* axis-user@ws.apache.org 
*Sent:* Monday, February 23, 2009 6:51 PM
*Subject:* Re: Pub\Sub Web Service


checkout ws-baseNotification:
 http://docs.oasis-open.org/wsn/wsn-ws_base_notification-1.3-spec-os.pdf


thanks
-Doug
__
STSM |  Standards Architect  |  IBM Software Group
(919) 254-6905  |  IBM 444-6905  |  d...@us.ibm.com



*Michael mailto:mtarullo...@optonline.net>>*

02/23/2009 06:47 PM
Please respond to
axis-user@ws.apache.org



To
axis-user@ws.apache.org
cc

Subject
Pub\Sub Web Service









I am developing a publish\subscribe engine and have exposed both
the publish and subscribe services with web services.
 
I am looking for advice on how I might implement a push

notification.  Since the occurrence of some event will trigger
notification of all users that subscribed to the publication of
that event how do I go about "pushing" the notification back out
to the clients from the server?
 
I have provided for several options in my design.  I am allowing

the subscribers to tell me how they would like to be notified.
 The options I provided are 1) provide an IP address and port and
I will send the notification using java.net; 2) provide a URL and
I will send the notification using java.net; and 3) provide a URL
and WSDL file and the name of a web service method to call and I
will use the Axis2 API to generate Java code for the WSDL and call
designated method.  Do these options sound reasonable,
particularly the third one?
 
Also, I was wondering if the Axis2 asynchronous call capability

might be a good candidate for this, either in addition to these
methods or to replace them?
 
If anyone has any ideas I would love to hear them.
 
Thanks, Mike  




No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.0.237 / Virus Database: 270.11.3/1968 - Release Date:
02/23/09 18:22:00

Service.aar files with different version libraries issue.

[hping]

Hello,

I have a service aar file from legacy, and I don't have source code to
re-compile it, and it was compiled with an older version axiom 1.2.2 library
since it uses that. Also FYI, Inside the aar file, there are no axiom
libraries. 

Now I want to update the sytem to use the current axis 1.4.1 (which matches
to the new version axiom 1.2.7) to try to provide the same web service.
Should the aar file have no problem or not?

Currently I have problem (java.lang.NoSuchMethodError:
org.apache.axiom.om.OMFactory.createOMElement) to do that, but not sure
whether this is the issue.

Thanks

-- 
View this message in context: 
http://www.nabble.com/Service.aar-files-with-different-version-libraries-issue.-tp22188975p22188975.html
Sent from the Axis - User mailing list archive at Nabble.com.

Quickstartadb: StockQuoteServiceMessageReceiverInOut not found for ADB

[Johnny Fung]

Hi
I am using axis2-1.4.1 running under tomcat 5.5, java1.5 on hp-ux.

I followed the instruction in quickstartadb to generate the service
StockQuoteService.
When I deploy it in tomcat (restart tomcat), I got (from catalina.out):

SEVERE: The StockQuoteService.aar service, which is not valid, caused
Processing Operations Modules with an error of A ClassNotFoundException
error occurred in loading the message receiver
samples.quickstart.service.adb.StockQuoteServiceMessageReceiverInOut
org.apache.axis2.deployment.DeploymentException: Processing Operations
Modules with an error of A ClassNotFoundException error occurred in
loading the message receiver
samples.quickstart.service.adb.StockQuoteServiceMessageReceiverInOut
at
org.apache.axis2.deployment.repository.util.ArchiveReader.processService
Group(ArchiveReader.java:147)

I did ant generate.service and deploy it to tomcat. It generate the
above error. But if I deploy it to the standalone axis2server, it is OK
and I can use it.

Can someone point me to right direction. I also tried axis 1.3 and I
have the same problem.

Johnny Fung

RE: Axis2 SOAP XML response question

[Shaon, ABS (Arif)]

OK Thanks. But is the  element part of standard SOAP message
format?

 

E.g. http://www.w3.org/2003/05/soap-envelope";>

http://stfc.ac.uk";>
 ..

 

If it isn't, there should be a way to remove it without using another
service layer on top of Axis

 

Regards

Arif

 

From: keith chapman [mailto:keithgchap...@gmail.com] 
Sent: 24 February 2009 09:59
To: axis-user@ws.apache.org
Subject: Re: Axis2 SOAP XML response question

 

If you need to put it as XML, you will have to wrap it in a CDATA
element.

Thanks,
Keith.

On Tue, Feb 24, 2009 at 3:26 PM, Shaon, ABS (Arif)
 wrote:

Thanks for your quick response.  Does that mean there is no other way to
display XML as XML rather than text literals,  even if I don't want to
change the format of the SOAP response.

 

Regards

Arif

 

From: keith chapman [mailto:keithgchap...@gmail.com] 
Sent: 24 February 2009 03:54
To: axis-user@ws.apache.org
Subject: Re: Axis2 SOAP XML response question

 

Well you could do this by doing a contract first web service. It looks
like you are using the POJO approach and when u do that you have to live
with the schema that Axis2 would give you. Alternatively you could just
stick an ESB in front and run the response through an XSLT and format it
to the manner you require. This could be done in a single server if you
use the WSO2 Web Services Application Server [1] (This is a Web Services
runtime environment built on top of Axis2 and its available under the
Apache License).

Thanks,
Keith.

[1] http://wso2.org/projects/wsas/java

On Tue, Feb 24, 2009 at 8:25 AM, Shaon, ABS (Arif)
 wrote:

 

Hi Everyone,

 

I am running  a AXIS4 1.4.1 SOAP service that returns an XML document
encoded in the SOAP Body.  The response I get is the following:

 

 

http://www.w3.org/2003/05/soap-envelope";>

http://stfc.ac.uk";>


..

 

But the response I would like is the following:

 

http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>

http://www.w3.org/1999/xlink";
xmlns:wps="http://www.opengis.net/wps/1.0.0";
xmlns:ows="http://www.opengis.net/ows/1.1";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://www.opengis.net/wps/1.0.0
..\wpsGetCapabilities_response.xsd" updateSequence="1">
 
.

 

 

Any idea how I can get AXIS not to display XML tags as literals?

 

Many thanks for your help.

 

Regards

Arif

 




Scanned by iCritical. 




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

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

 




Scanned by iCritical. 




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

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


-- 

Scanned by iCritical.

Axis2 - Rampart: Clientside Policy Configuration

[Berner, Nicolas]

Hi everybody,

 

I´m playing around with Axis2 (1.41) and Rampart (1.4). The Policy 
Configuration works fine.

I attach a Policy to my Axis2-Service and generate the client from wsdl.

So my client is already configured for my desired security operations. Until 
now I configured the clientside rampart-module (crypto-settings, user-settings)

 either static in the client-axis2.xml or dynamically in the Service-Sourcecode.

The configuration-part of the client-axis2.xml looks like that:

http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";


xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy";>

  http://ws.apache.org/rampart/policy";>

client


ClientPWCallbackHandler

service

 



  

JKS

client.jks

test

  



  



Is this the right way to configure the client in a static way or is there 
another possibility?

Maybe a better one?

 

Thanks a lot in advance for your answers!

 

Regards,

Nicolas

Using web service with policy under https

[Håkon Sagehaug]

Hi all,

I've got some web services and before just running under http, and wanted to
try running it under https, this worked fine for all my web service, except
the ones having policies and where the client is calling them, and rampart
is enabled on both sides. Do I've got to have transport token set to https
in the policy? like this

 


I can call the web services with policy on regular http, but when using
https I in the end get this error

Caused by: javax.net.ssl.SSLException: Received close_notify during
handshake

after a number of retries.

I'm running tomcat 6, axis2, any hints on this mather???

cheers, Håkon
-- 
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)

Problem using special character "<"

[Manuel Lenz]

Hi Axis-Users,
I try to call a webservice with a search-request.
The search request includes the special character "<".
The webservice itself works with the html-writing "<".
So I´ve added this code for the search request:

MessageElement operator = new MessageElement();
operator.setName("operator");
operator.setValue("<");

But the webservice ignores the operator.
What is wrong with the search request?

Thanks for your interest,
Manuel

Ps: I´m using Axis 1.2.1






Viessmann IT Service GmbH
Geschäftsführer: Dirk Klöckner, Dr. Harald Dörnbach
Sitz der Gesellschaft: Allendorf (Eder) - Registergericht:
AG Marburg (Lahn) - HRB 5324 - USt-IdNr.: DE258558424

Re: Axis2 SOAP XML response question

[keith chapman]

If you need to put it as XML, you will have to wrap it in a CDATA element.

Thanks,
Keith.

On Tue, Feb 24, 2009 at 3:26 PM, Shaon, ABS (Arif) wrote:

>  Thanks for your quick response.  Does that mean there is no other way to
> display XML as XML rather than text literals,  even if I don’t want to
> change the format of the SOAP response.
>
>
>
> Regards
>
> Arif
>
>
>
> *From:* keith chapman [mailto:keithgchap...@gmail.com]
> *Sent:* 24 February 2009 03:54
> *To:* axis-user@ws.apache.org
> *Subject:* Re: Axis2 SOAP XML response question
>
>
>
> Well you could do this by doing a contract first web service. It looks like
> you are using the POJO approach and when u do that you have to live with the
> schema that Axis2 would give you. Alternatively you could just stick an ESB
> in front and run the response through an XSLT and format it to the manner
> you require. This could be done in a single server if you use the WSO2 Web
> Services Application Server [1] (This is a Web Services runtime environment
> built on top of Axis2 and its available under the Apache License).
>
> Thanks,
> Keith.
>
> [1] http://wso2.org/projects/wsas/java
>
> On Tue, Feb 24, 2009 at 8:25 AM, Shaon, ABS (Arif) 
> wrote:
>
>
>
> *Hi Everyone,*
>
>
>
> I am running  a AXIS4 1.4.1 SOAP service that returns an XML document
> encoded in the SOAP Body.  The response I get is the following:
>
>
>
>
>
> http://www.w3.org/2003/05/soap-envelope";>
> 
> http://stfc.ac.uk";>
>  <
> Capabilities
> xmlns:xlink="http://www.w3.org/1999/xlink"; xmlns="
> http://www.opengis.net/wps/1.0.0";
> xmlns:ows="http://www.opengis.net/ows/1.1";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> version="1.0.0"
> xsi:schemaLocation="http://www.opengis.net/wps/1.0.0
>
> http://schemas.opengis.net/wps/1.0.0/wpsGetCapabilities_response.xsd";>
> ..
>
>
>
> But the response I would like is the following:
>
>
>
> http://schemas.xmlsoap.org/soap/envelope/"xmlns:xsi
> ="http://www.w3.org/2001/XMLSchema-instance"; xmlns:xsd="
> http://www.w3.org/2001/XMLSchema";>
> 
>  version="1.0.0"xml:lang
> ="en-CA" xmlns:xlink="http://www.w3.org/1999/xlink"; xmlns:wps="
> http://www.opengis.net/wps/1.0.0"; xmlns:ows="
> http://www.opengis.net/ows/1.1"; xmlns:xsi="
> http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="
> http://www.opengis.net/wps/1.0.0 
> ..\wpsGetCapabilities_response.xsd"updateSequence
> ="1">
>
> .
>
>
>
>
>
> Any idea how I can get AXIS not to display XML tags as literals?
>
>
>
> Many thanks for your help.
>
>
>
> Regards
>
> Arif
>
>
>  --
>
>
> Scanned by iCritical.
>
>
>
>
> --
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
>
> --
>
> Scanned by iCritical.
>



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

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

RE: Axis2 SOAP XML response question

[Shaon, ABS (Arif)]

Thanks for your quick response.  Does that mean there is no other way to
display XML as XML rather than text literals,  even if I don't want to
change the format of the SOAP response.

 

Regards

Arif

 

From: keith chapman [mailto:keithgchap...@gmail.com] 
Sent: 24 February 2009 03:54
To: axis-user@ws.apache.org
Subject: Re: Axis2 SOAP XML response question

 

Well you could do this by doing a contract first web service. It looks
like you are using the POJO approach and when u do that you have to live
with the schema that Axis2 would give you. Alternatively you could just
stick an ESB in front and run the response through an XSLT and format it
to the manner you require. This could be done in a single server if you
use the WSO2 Web Services Application Server [1] (This is a Web Services
runtime environment built on top of Axis2 and its available under the
Apache License).

Thanks,
Keith.

[1] http://wso2.org/projects/wsas/java

On Tue, Feb 24, 2009 at 8:25 AM, Shaon, ABS (Arif)
 wrote:

 

Hi Everyone,

 

I am running  a AXIS4 1.4.1 SOAP service that returns an XML document
encoded in the SOAP Body.  The response I get is the following:

 

 

http://www.w3.org/2003/05/soap-envelope";>

http://stfc.ac.uk";>


..

 

But the response I would like is the following:

 

http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>

http://www.w3.org/1999/xlink";
xmlns:wps="http://www.opengis.net/wps/1.0.0";
xmlns:ows="http://www.opengis.net/ows/1.1";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://www.opengis.net/wps/1.0.0
..\wpsGetCapabilities_response.xsd" updateSequence="1">
 
.

 

 

Any idea how I can get AXIS not to display XML tags as literals?

 

Many thanks for your help.

 

Regards

Arif

 




Scanned by iCritical. 




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

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


-- 

Scanned by iCritical.

AW: SCOPE="SOAPSESSION"

[Stadelmann Josef]

Dear community;
 
I have found the solution to the problem below.
 
It is that  my Microsoft WCF Client must allow for cookies . Up on a initial 
call ,  via a HTTP transport ,  the client signals that it can accept cookies . 
In turn, the axis2 httptransport will issue a set cookie command with its first 
reply . After that the client will send this cookie, which is JSESSION="  
uuid " string toward the axis2 server. Since I have enabled this by the 
following VB.net code in my WCF client transport binding ,  
 
HttpTransportBindingElement httpTransportBE = new 
HttpTransportBindingElement();
httpTransportBE.AllowCookies = true;
 
the JSESSION cookie is exchanged with each  consecutieve request to the axis2 
server.
 
For sure - I did never expect that multi session capability of axis2 was 
two-fold.
 
a) receiving a ServiceGroupId  up on a frist reply and send it with each 
consecutive request
b) receiving a JSESSION cookie up on a first reply and send it with each 
consecutive request
 
This is a real surprise for me. 
 
Now my VB.net WCF clients work perfect with  the axis2 server, 
and exchanging large junks of nested collections of named value pairs of 
strings as soap xml documents is well done.
 
Sepp

Re: Axis2: how to skip namespace prefixes ?

[GKGT80]

Hello Keith,

Thanx for response. That's true its a defect in OSP 2.4 BPEL engine.But for
some reasoan we can't change the OSP 2.4 BPEL engine. 
Is any way we can get the SOAP response message directly ?

KR,
Gaurav Kumar


Keithgchapman wrote:
> 
> Hi Gaurav,
> 
> Your Response is not valid XML, That is the reason for this error.
> 
> xmlns:urn:="urn:Alcatel_Lucent_OSP_BPEL">
> 
> should have been
> 
> xmlns:urn="urn:Alcatel_Lucent_OSP_BPEL">
> 
> This looks to be a bug in the server (OSP 2.4 BPEL engine)
> 
> Thanks,
> Keith.
> 
> On Mon, Feb 23, 2009 at 10:11 PM, GKGT80  wrote:
> 
>>
>> Hello keith ,
>>
>> I am also facing problem in SOAP response.
>>
>> SOAP Response I am getting (TCP Monitor trace):-
>> *
>> HTTP/1.1 200 OK
>> Server: OSP 2.4 BPEL engine
>> Content-Type: text/xml; charset=ISO-8859-1
>> Content-Length: 1965
>> Connection: close
>>
>> 
>>   > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
>> xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/";
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
>> xmlns:urn:="urn:Alcatel_Lucent_OSP_BPEL">
>>  
>> ...
>>   
>>   
>>
>> *
>>
>> In our SOAP response Envelope 1 semantics error in namespace
>> declaration:-
>> xmlns:urn:="urn:Alcatel_Lucent_OSP_BPEL"
>> Because of this my SOAP client give exception while receiving the SOAP
>> response :
>> *
>> org.apache.axis2.AxisFault: com.ctc.wstx.exc.WstxUnexpectedCharException:
>> Unexpected character ':' (code 58) expected '='
>>  at [row,col {unknown-source}]: [1,284]
>> 
>>
>> Is any work around of this problem ? like getting the raw response etc.
>>
>> KR,
>> Gaurav Kumar
>>
>>
>>
>> Keithgchapman wrote:
>> >
>> > You could have elementFormDefault="unqualified" in the schema of the
>> WSDL.
>> > This instructs the user not to care about the namespaces.
>> >
>> > Thanks,
>> > Keith.
>> >
>> > On Fri, Feb 20, 2009 at 7:39 PM, durbans  wrote:
>> >
>> >>
>> >> I am new to Axis2; i am using ADB.
>> >> I'd like to skip namespace prefixes in XML response. For example if
>> the
>> >> client receive
>> >>
>> >>  John
>> >>
>> >> or receive
>> >>
>> >> John
>> >>
>> >> it must work in both case. At the moment only the second case work,
>> >> because
>> >> in xsd file the namespace is defined.
>> >>
>> >> Are there any way to skip ALWAYS the namespaces ?
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/Axis2%3A-how-to-skip-namespace-prefixes---tp22120392p22120392.html
>> >> Sent from the Axis - User mailing list archive at Nabble.com.
>> >>
>> >>
>> >
>> >
>> > --
>> > Keith Chapman
>> > Senior Software Engineer
>> > WSO2 Inc.
>> > Oxygenating the Web Service Platform.
>> > http://wso2.org/
>> >
>> > blog: http://www.keith-chapman.org
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Axis2%3A-how-to-skip-namespace-prefixes---tp22120392p22165119.html
>> Sent from the Axis - User mailing list archive at Nabble.com.
>>
>>
> 
> 
> -- 
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
> 
> blog: http://www.keith-chapman.org
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Axis2%3A-how-to-skip-namespace-prefixes---tp22120392p22177797.html
Sent from the Axis - User mailing list archive at Nabble.com.