RE: sending calendar object in axis stub

[Senthivel U S]

Hi Jeff,

 

Thanks for your clue. I have sorted out the issue. Now I am trying to sign.
Please throw me some light how to engage the security modules only for
created stub. I have tried this, but it gives the error, "Security token not
found".

 

My code:

 

URL endPointURL = new URL("http:// ");

EngineConfiguration config = new FileProvider("services.xml");

Service service = new Service();

DefaultSoapStub stub = new DefaultSoapStub(endPointURL, service);

 

 

Service.xml is

 





Testing







  

Timestamp

service.properties

SKIKeyIdentifier

useReqSigCert

client

service.properties

 
com.unistream.client.ServiceSecurityHandler  

 
{Element}{http://docs.oasis-open.org/wss/2004/01/oasis-20040
1-wss-wssecurity-utility-1.0.xsd}Timestamp;{Element}{http://schemas.xmlsoap.
org/soap/envelope/}Body

 

  



 

 

TIA,

-senthil

 

  _  

From: Walker, Jeff [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 15, 2007 6:32 PM
To: axis-user@ws.apache.org
Subject: RE: sending calendar object in axis stub

 

Hi Senthil,

shame on them for writing a language-specific web serivce!

 

Anyway, if they are the authors of the web service and you are the client,
then you must have gotten the wsdl from them. The wsdl must have a
complexType in it that declares the issuedDate as non-nillable.  But I can't
tell why the line "transfer.setIssueDate(Calendar.getInstance());" failed.

You'll have to debug it and step through slowly at this point to see if the
instance returned from Calendar.getInstance() is null or not. (If it is not
null, then it is getting nulled out later before the stub attempts to
serialize everything).

This is my guess.

-jeff

 

  _  

From: Senthivel U S [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 15, 2007 9:38 AM
To: axis-user@ws.apache.org
Subject: RE: sending calendar object in axis stub

Hi Jeff,

 

Thanks for your comments and I do agree with you. The service was deployed
by third party and I want to consume the service. I have created my stub
using wsdl (Eclipse IDE).

 

TIA,

-senthil

 

 


  _  


From: Walker, Jeff [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 15, 2007 5:08 PM
To: axis-user@ws.apache.org
Subject: RE: sending calendar object in axis stub

 

Hi Senthil,

Don't pass language specific constructs like Calendar, in a web service
call.

 

You are better taking the less obvious route; just pass the minimal amount
number fo fields in the Calendar object that can be used by a client to
regenerate the equivalent object on their side. That is, build a new
complexType in XML Schema and use Doc/Lit-wrapped web services.

 

The main reason is simply, interoperability. Even of you know all of your
clients will be Java going forward, it's bad practice to pass language
specific objects in a web service. If indeed all of your clients will always
be Java, then you would benefit from RMI or EJB where you would get a
significant speed increase. Web Services is for interoperability across
disparate systems.

Regards,

-jeff

 


  _  


From: Senthivel U S [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 15, 2007 8:27 AM
To: axis-user@ws.apache.org
Subject: sending calendar object in axis stub

Hi,

 

I have a stub, in that I want to pass calendar object, while passing I am
getting the following error.  Is any serializer to be included to pass
calendar object.

 

java.io.IOException: Non nillable element 'issuedDate' is null.

at
org.apache.axis.encoding.ser.BeanSerializer.serialize(BeanSerializer.java:21
5)

at
org.apache.axis.encoding.SerializationContext.serializeActual(SerializationC
ontext.java:1502)

 

My code is 

 

transfer.setIssueDate(Calendar.getInstance());

stub.insertTransfer(transfer);

 

TIA,

-senthil

 

Java heap problems with Axis2

[Matthew Fadoul]

Hi all,

 

I've got an app that is making the JVM run out of heap.  I'd like to adjust
the heap size.  I've read about the "-Xmx" option for running java on the
command line.  Unfortunately, I'm just a lowly C++ programmer who's still
trying to find his way around Java, so I'm scratching my head trying to
figure out how that translates into adjusting my JVM.maybe there's a secret
batch file or configuration window where I can adjust the value?

 

For the context, my system is:

* WindowsXP Pro.

* Java EE 5 SDK

* Apache Tomcat

* Apache Axis2

 

Here is the actual error reported by Axis2:

 

Error: java.lang.OutOfMemoryError: Java heap space at
java.util.Vector.(Unknown Source) at java.util.Vector.(Unknown Source) at
java.util.Vector.(Unknown Source) at
org.apache.ws.commons.schema.XmlSchemaObjectCollection.(XmlSchemaObjectColle
ction.java:37) at
org.apache.ws.commons.schema.XmlSchemaSimpleTypeRestriction.(XmlSchemaSimple
TypeRestriction.java:36) at
org.apache.ws.commons.schema.SchemaBuilder.handleSimpleType(SchemaBuilder.ja
va:354) at
org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuil
der.java:152) at
org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:82) at
org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.ja
va:359) at
org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.ja
va:304) at
org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.ja
va:1884) at
org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.ja
va:1902) at
org.apache.ws.commons.schema.SchemaBuilder.handleImport(SchemaBuilder.java:1
627) at
org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuil
der.java:175) at
org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.ja
va:347) at
org.apache.axis2.description.WSDLToAxisServiceBuilder.getXMLSchema(WSDLToAxi
sServiceBuilder.java:140) at
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.copyExtensibleElemen
ts(WSDL11ToAxisServiceBuilder.java:2186) at
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.processTypes(WSDL11T
oAxisServiceBuilder.java:306) at
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.processTypes(WSDL11T
oAxisServiceBuilder.java:297) at
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL
11ToAxisServiceBuilder.java:265) at
org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateAllServi
ces(WSDL11ToAllAxisServicesBuilder.java:109) at
org.apache.axis2.deployment.repository.util.ArchiveReader.processWSDLFile(Ar
chiveReader.java:230) at
org.apache.axis2.deployment.repository.util.ArchiveReader.processWSDLs(Archi
veReader.java:332) at
org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:64)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(Deploy
mentFileData.java:137) at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:
571) at
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.jav
a:141) at
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.jav
a:318) at
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListe
ner.java:220) at
org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.j
ava:118) at
org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAx
isConfigurator.java:272) at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationCont
ext(ConfigurationContextFactory.java:78)

 

Any help would be greatly appreciated!

 

Matt

Axis 1.4 and .NET interop

[M N]

We have been using AXIS 1.1 ( yeah I know its old) for past few years with 
Jboss and everythings looks fine.We have removed the jbossws.sar directory 
completely.
   
  Anyway so we have this new requirement where we have to provide webservices 
to a .NET client. No matter what we provide .NET client keeps getting 
exceptions. We found yesterday that .NET does not support RPC transport from 
java webservices. So we decided to use DOCUMENT/LITERAL style in WSDL ( created 
using ANT JAVA2WSDL tool) . But then even when I test the WS from Java side it 
keeps giving me NOT A ARGUMENT(or something like that) error. I read later on 
that AXIS 1.1 doesnt support the DOCUMENT/LITERAL style well. So we decided to 
upgrade to 1.4.
   
  I still kept getting the NOT A ERROR except when I 
mention in ANT JAVA2WSDL utility that I need WRAPPED/LITERAL style. Any other 
style doesnt seem to work. So now with WRAPPED/LITERAL style my Java client 
stubs can successfully work with Java WSs. We will be testing it with .NET 
tomorrow. I am wondering if it will work and there wont be any exceptions. 
   
  Thanks
   

   
-
Moody friends. Drama queens. Your life? Nope! - their life, your story.
 Play Sims Stories at Yahoo! Games. 

Re: Axis2 1.3 and Servlet Spec

[Sanka Samaranayke]

Hi

I believe its servlet specification 2.3 version.

--Sanka


Kiran Kumar Sriram wrote:

Hi Martin,
 
It is just not only with Tomcat, If i have to select any other 
webserver then i need to know what is the servlet spec Axis2 1.3 needs 
at minimum.
 
I didn't find that info on the requirements page of Axis2 website.
 
Thanks,

Kiran


From: [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Subject: Re: Axis2 1.3 and Servlet Spec
Date: Fri, 13 Oct 2000 17:53:47 -0400

depends on the container that axis wil be implement on e.g.
Apache Tomcat version 5.5 implements the Servlet 2.4
Apache Tomcat version 6.0 implements the Servlet 2.5
 
Are you using a different container?

Martin--

- Original Message -
*From:* Kiran Kumar Sriram 
*To:* axis-user@ws.apache.org 
*Sent:* Friday, October 12, 2007 2:15 PM
*Subject:* Axis2 1.3 and Servlet Spec

Hello All,

Axis2 1.3 can be installed in any Servlet Container, but is
there any minimum Servlet specification(2.1 or 2.3) that is
needed for Axis2 1.3 ?

Any help is greatly appreciated.

Thanks,
Kiran



Boo! Scare away worms, viruses and so much more! Try Windows
Live OneCare! Try now!






Peek-a-boo FREE Tricks & Treats for You! Get 'em! 




--
Sanka Samaranayake
WSO2 Inc.

http://www.bloglines.com/blog/sanka
http://www.wso2.org/


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

Re: [ANN] Apache Savan/C 0.90 Released

[Demetris G]

Thanks Sanka ...

Sanka Samaranayke wrote:

Hi,



Demetris G wrote:


Is there a Savan/Java ?
  


https://svn.apache.org/repos/asf/webservices/savan/trunk/java/

AFAIK, there wasn't an official release of SAVAN.

Best,
--Sanka



Damitha Kumarage wrote:

Hi List,
Apache Savan/C Team is pleased to announce the release of Apache 
Savan/C version 0.90

You can download this release from
http://ws.apache.org/savan/c/download.cgi
This release is supposed to be used with the Axis2C 1.1.0 
distribution which is released recently.


Key Features:

1 Support for WS-Eventing Specification August 2004.
2 Support for Subscribe, Unsubscribe, Renew and GetStatus 
operations.

3 Support for subscription management endpoint which could be the
Event Source itself or separate subscription management 
endpoint.

4 Persistent storage for subscribers.
5 Support for both SOAP 1.1 and 1.2.
6 Samples to test scenarios.
7 Documentation

We welcome your early feedback on this implementation.
Thanks for your interest in Savan/C

-- Apache Savan/C Team -- 


-
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: Soap Faults and Exception

[Amila Suriarachchi]

can you send your wsdl?

On 10/15/07, Kahler, Jason J (US SSA) <[EMAIL PROTECTED]> wrote:
>
>  I am using adb. I don't think it is a wsdl issue, because this wsdl
> generated Service.Exception fine using Axis 1.
>
> I also have only one method in my wsdl that throws that fault. It does in
> fact generate the Fault classes. But they do not extend Throwable.
>
>
>  --
>
> *From:* Amila Suriarachchi [mailto:[EMAIL PROTECTED]
> *Sent:* Monday, October 15, 2007 1:06 AM
> *To:* axis-user@ws.apache.org
> *Subject:* Re: Soap Faults and Exception
>
>
>
> what is the data bind you use?
> Axis2 generates a seperate class for every element. and each fault
> message. so if an element with the wsdl namespace with the name same as the
> fault message then both classes would have the same package and class names.
>
>
> to avoid this use -p option to specify a seperate package name for wsdl
> namespace.
>
>  On 10/12/07, *Kahler, Jason J (US SSA)* < [EMAIL PROTECTED]>
> wrote:
>
> I am using Axis2 1.3
>
> I have defined a custom Fault in my WSDL. It worked fine using axis 1.
>
> But now when I run WSDL2code via the maven2 pluggin I get errors when I
> try to compile my classes such as:
>
>
>
> java:[63,17] incompatible types
>
> found   : wfnp.ServiceException
>
> required: java.lang.Throwable
>
>
>
> the wfnp.ServiceException class doesn't even extend any kind of throwable,
> so how can my classes actually
>
> throw it ? I am very frustrated and confused.
>
>
>
> Jay
>
>
>
>
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.
>



-- 
Amila Suriarachchi,
WSO2 Inc.

Re: [ANN] Apache Savan/C 0.90 Released

[Sanka Samaranayke]

Hi,



Demetris G wrote:


Is there a Savan/Java ?
  


https://svn.apache.org/repos/asf/webservices/savan/trunk/java/

AFAIK, there wasn't an official release of SAVAN.

Best,
--Sanka



Damitha Kumarage wrote:

Hi List,
Apache Savan/C Team is pleased to announce the release of Apache 
Savan/C version 0.90

You can download this release from
http://ws.apache.org/savan/c/download.cgi
This release is supposed to be used with the Axis2C 1.1.0 
distribution which is released recently.


Key Features:

1 Support for WS-Eventing Specification August 2004.
2 Support for Subscribe, Unsubscribe, Renew and GetStatus 
operations.

3 Support for subscription management endpoint which could be the
Event Source itself or separate subscription management 
endpoint.

4 Persistent storage for subscribers.
5 Support for both SOAP 1.1 and 1.2.
6 Samples to test scenarios.
7 Documentation

We welcome your early feedback on this implementation.
Thanks for your interest in Savan/C

-- Apache Savan/C Team -- 


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





--
Sanka Samaranayake
WSO2 Inc.

http://www.bloglines.com/blog/sanka
http://www.wso2.org/


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

Re: [Axis2 1.2] Axis2 attachment interoperability???

[Xinjun Chen]

Hi Skudx,

I suggest you handle MessageContext directly if you want to solve the
attachment interoperability issue.
The MessageContext give you flexibility to handle your attachments.

Axis2 recommend the use of "start" parameter but doesn't mandate it. I have
tested that.

But as for preserving the order of attachments, I don't think Axis2
developers will consider this request. You should not rely on the order of
the attachments. You should use something like contentID or name to
associate an ID with certain attachment.


Regards,
Xinjun


On 10/10/07, skudx <[EMAIL PROTECTED]> wrote:
>
>
>
> Hi Thilina/ Xinjun,
>
> Could you pl have a look at
> https://issues.apache.org/jira/browse/AXIS2-3245
> & give me some pointers to move ahead?
>
> My current requirements force me to use jax-ws-ri on the server-side &
> axis2
> on the client-side. The request/ response messages typically have more
> than
> one binary attachments and the order of attachments must be preserved.
>
> Thanks
> Regards
>
>
> --
> View this message in context:
> http://www.nabble.com/-Axis2-1.2--Axis2-attachment-interoperabilitytf3906797.html#a13125936
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: axis question revisited

[Chad DeBauch]

The easiest way I have found to get past this issue temporarily, or if you
don't care about having your web services be modular, you can dump your jars
in the WEB-INF/lib directory.  This way you don't have to worry about the
ClassLoader.  If you don't want to take that approach here is how you get
the ClassLoader from the aar:

MessageContext.getCurrentMessageContext().getAxisService().getClassLoader();

Depending on what application server you are deploying your app to, the app
server may load jars before they load the ones in your app, causing
ClassNotFound or MethodNotFound Excpetions.

Chad

On 10/15/07, Kahler, Jason J (US SSA) <[EMAIL PROTECTED]> wrote:
>
>  Can you give an example ?
>
>
>
>
>
> The jars in your lib aar directory will be loaded in a separate
> classloader.  So you must reference those classes using that classloader.
> You can do this by getting the MessageContext.
>
> Chad
>
> On 10/12/07, *Kahler, Jason J (US SSA)* <[EMAIL PROTECTED]>
> wrote:
>
> I am building my aar using the maven2 pluggin. Everything builds but when
> I deploy I get NoClassDefFound
> ERRORS all over. This was working as a war in tomcat using axis 1. All the
> required jars are in
>
>
>
> myArr.arr/lib what could be wrong ?
>
>
>
> Jay
>
>
>

Re: problem of soap version in axis2/java 1.2

[Thilina Gunarathne]

You can set the following parameters to true..

 false

  false

thanks,
Thilina

On 10/15/07, donald yang <[EMAIL PROTECTED]> wrote:
> Hi Thilina,
>
> thank you very much for your reply.
>
> How can I modify axis2.xml in the server side for axis2/java 1.2? So that I
> can send the new full stack trace.
>
> best regards
> yong
>
>
>  On 10/12/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >
> > This can be due to the action= parameter of the content type of
> > the MIME message generated by Axis2/c (Notice the unnecessary
> > quotes)...  Modify your Axis2.xml of the server to send the full stack
> > trace with faults and post the full stack trace..
> >
> > Also log a JIRA with Axis2/C.
> >
> > ~Thilina
> >
> >
> >
> > On 10/12/07, donald yang <[EMAIL PROTECTED]> wrote:
> > > Hi Keith,
> > >
> > > Thanks for your reply. The problem I currently have is that I will
> reveive
> > > an exception "Invalid Content Type Field in the Mime Message"  as a SOAP
> > > reply when I set the soap version to 1.2 in the web service client
> written
> > > using AXIS2/C 1.0. But when I set the soap version to 1.1 in the web
> service
> > > client, it works as what I expect.  The environment for this test case
> is as
> > > follows:
> > >
> > >  Web service Client: use AXIS2/C 1.0
> > >  Web Service: POJO web serice and AXIS2/JAVA 1.2
> > >  WSDL : automatically generated by AXIS2/JAVA 1.2 which has three
> port:
> > > HTTP, SOAP1.2 , SOAP1.1
> > >
> > > The soap messages for this test case can be found in the attachment.
> > >
> > > best regards
> > > donald
> > >
> > > On 10/12/07, keith chapman < [EMAIL PROTECTED]> wrote:
> > > >
> > > > No need to change anything. If the request is SOAP 1.1 the response
> will
> > > > be SOAP 1.1. if it is SOAP 1.2 the response will be SOAP 1.2.
> > > >
> > > > Thanks,
> > > > Keith.
> > > >
> > > > On 10/12/07, donald yang <[EMAIL PROTECTED]> wrote:
> > > > >
> > > > > Hi everyone,
> > > > >
> > > > > First I wrote a simple web service using AXIS2/JAVA 1.2. Then I
> wrote a
> > > > > web service client test case using AXIS2/C 1.0 to access the web
> > > > > service. In the client,  I have enabled MTOM even if there is no
> binaary
> > > > > attachment to send in fact and set the SOAP version to SOAP 1.2. I
> got
> > > > > one exception
> > > > >
> > > > >  " Invalid Content Type Field in the Mime Message"
> > > > >
> > > > > Then I compared the soap request created by AXIS2/C 1.0 with the
> soap
> > > > > request created by AXIS2/JAVA 1.2. I found the major difference is
> that
> > > > > the value of start-info is "application/xop+xml" not "text/xml" in
> the
> > > soap
> > > > > request created by AXIS2/C.
> > > > >
> > > > > Then I resetting the SOAP vesion to SOAP 1.1 in the web service
> client
> > > > > wrote using AXIS2/C 1.0. It works fine. But when I looked at the
> wsdl
> > > > > generated by AXIS2/JAVA 1.2, it has three ports, HTTP PORT, SOAP
> > > 1.1PORT,
> > > > > SOAP1.2 PORT. That means it should support the SOAP request with
> version
> > > > > 1.2. Is there anyone can tell me how to enable  the server support
> SOAP
> > > > > 1.2 in AXIS2/JAVA 1.2? many thanks in advnace.
> > > > >
> > > > > best regards
> > > > > yong
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Keith Chapman
> > > > WSO2 Inc.
> > > > Oxygen for Web Services Developers.
> > > > http://wso2.org/
> > >
> >
> >
> > --
> > Thilina Gunarathne  - http://thilinag.blogspot.com
> >
> >
> -
> > To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>


-- 
Thilina Gunarathne  - http://thilinag.blogspot.com

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

Re: uploading a file

[Charitha Kankanamge]

feh wrote:


Hi folks.

I've got an Axis2 client that needs to send a text file to an Axis2 server.
What's the best way to accomplish this?

Thanks!
 

MTOM (SOAP message transmission and optimization mechanism) can be used 
to sernd binary data in axis2. MTOMSample 
(AXIS2_HOME/samples/MTOMsample), which is included in axis2 binary 
distribution will help you to get an initial understanding on this.

Also, please check http://ws.apache.org/axis2/1_3/mtom-guide.html

regards
Charitha


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

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



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

Axis 1.4: WSDL2Java fails with ClassNotFound error for javax.wsdl.QName

[Gamble, Wesley (WG10)]

All,

 

Trying to use WSDL2Java to generate some WS glue code and it fails with
the following exception:

 

java org.apache.axis.wsdl.WSDL2Java
https://api.channeladvisor.com/ChannelAdvisorAPI/v1/ShippingService.asmx
?WSDL

Exception in thread "Thread-1" java.lang.NoClassDefFoundError:
javax/wsdl/QName

at
org.apache.axis.wsdl.toJava.Utils.getNodeQName(Utils.java:213)

at
org.apache.axis.wsdl.toJava.SymbolTable.addTypes(SymbolTable.java:550)

at
org.apache.axis.wsdl.toJava.SymbolTable.addTypes(SymbolTable.java:638)

at
org.apache.axis.wsdl.toJava.SymbolTable.populateTypes(SymbolTable.java:5
31)

at
org.apache.axis.wsdl.toJava.SymbolTable.populate(SymbolTable.java:424)

at
org.apache.axis.wsdl.toJava.SymbolTable.add(SymbolTable.java:330)

at org.apache.axis.wsdl.toJava.Emitter.emit(Emitter.java:188)

at org.apache.axis.wsdl.toJava.Emitter.emit(Emitter.java:155)

at
org.apache.axis.wsdl.WSDL2Java$WSDLRunnable.run(WSDL2Java.java:725)

at java.lang.Thread.run(Thread.java:619)

 

I'm using JDK 1.6.0_01 and I have all of the libraries in axis-1.4/lib
on my CLASSPATH.  

 

I have successfully generated WSDL for two other services using this
scheme.  What am I missing?

 

Thanks,

Wes

RE: Axis2 1.3 and Servlet Spec

[Kiran Kumar Sriram]

Hi Martin,
 
It is just not only with Tomcat, If i have to select any other webserver then i 
need to know what is the servlet spec Axis2 1.3 needs at minimum.
 
I didn't find that info on the requirements page of Axis2 website.
 
Thanks,
Kiran


From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: Re: Axis2 1.3 and Servlet SpecDate: 
Fri, 13 Oct 2000 17:53:47 -0400



depends on the container that axis wil be implement on e.g.
Apache Tomcat version 5.5 implements the Servlet 2.4
Apache Tomcat version 6.0 implements the Servlet 2.5
 
Are you using a different container?
Martin--

- Original Message - 
From: Kiran Kumar Sriram 
To: axis-user@ws.apache.org 
Sent: Friday, October 12, 2007 2:15 PM
Subject: Axis2 1.3 and Servlet Spec
Hello All,Axis2 1.3 can be installed in any Servlet Container, but is there any 
minimum Servlet specification(2.1 or 2.3) that is needed for Axis2 1.3 ?Any 
help is greatly appreciated.Thanks,Kiran

Boo! Scare away worms, viruses and so much more! Try Windows Live OneCare! Try 
now! 
_
Peek-a-boo FREE Tricks & Treats for You!
http://www.reallivemoms.com?ocid=TXT_TAGHM&loc=us

uploading a file

[feh]

Hi folks.

I've got an Axis2 client that needs to send a text file to an Axis2 server.
What's the best way to accomplish this?

Thanks!
-- 
View this message in context: 
http://www.nabble.com/uploading-a-file-tf4629708.html#a13219738
Sent from the Axis - User mailing list archive at Nabble.com.


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

Re: Deploy axis2 in WAS5.2.1

[Todd Allen]

The following link may help.
http://ws.apache.org/axis2/1_3/app_server.html


mohcine wrote:

hi
i m having serious troubles when trying to deploy axis2 in WAS5.1
pleae is there any tuto desciping this matter any help is welcome i am
really stuck in here
thanks
  


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

RE: [Axis2] Axis2 jars and dependencies

[Pantvaidya, Vishwajit]

Take a look at 
http://www.nabble.com/-AXIS2--Which-axis2-1.3-jars-to-bundle-tf4262663.html#a12131425
 - explains some of the jars.


- Vish.

>-Original Message-
>From: Anders Kristensen [mailto:[EMAIL PROTECTED]
>Sent: Thursday, October 11, 2007 4:58 PM
>To: axis-user@ws.apache.org
>Subject: Re: [Axis2] Axis2 jars and dependencies
>
>It would be a bit difficult to feel confident that a jar isn't needed
>just because one or more method calls didn't fail when the service was
>deployed without the jar being present.
>
>I think the Axis developers need to provide some guidance on when the
>various jars are needed.
>
>Thanks,
>Anders
>
>Martin Gainty wrote:
>> Easiest way is to add clover into the build
>> http://www.atlassian.com/software/clover/
>> to determine which classes or packages have been orphaned
>>
>>>From the front end to look at Call Graph I would use either VTune
>> http://www.intel.com/support/performancetools/sb/cs-021631.htm
>>
>> or perhaps Jprofiler
>> http://www.ej-technologies.com/products/jprofiler/overview.html
>>
>> Then again you can just rename the libraries e.g. from *.jar  to
>*.jar.old
>> and add them back in one at a time..
>>
>> Martin-
>> - Original Message -
>> From: "Lawrence Mandel" <[EMAIL PROTECTED]>
>> To: 
>> Sent: Thursday, October 11, 2007 5:42 PM
>> Subject: Re: [Axis2] Axis2 jars and dependencies
>>
>>
>>> *I cleaned up the lists below as they were difficult to read.*
>>>
>>> The Axis2 download includes 19 Axis2 jars and 39 third party jars. I'm
>>> trying to understand:
>>>
>>> 1. Why Axis2 has to be broken up into 19 separate jars. Can any of these
>>> be amalgamated to produce less jars? (I find it confusing that there are
>>> so many and I think most people just put them all on the classpath
>instead
>>>
>>> of thinking about it.)
>>> 2. Why Axis2 has so many dependencies. Are some of these dependencies
>>> optional or can they be made optional?
>>>
>>> I'd appreciate any help in understanding the requirement, even if just a
>>> pointer to an existing document that I've missed. I did find one wiki
>page
>>>
>>> [1] that started this discussion about a year ago but it's out of date.
>>>
>>> [1] http://wiki.apache.org/ws/FrontPage/Axis2/axis2_std_build_list
>>>
>>> Here are lists of the Axis2 jars and the third party jars.
>>>
>>> Axis2
>>> 
>>> axis2-adb-1.3.jarUsed by Java2WSDL and WSDL2Java?
>>> axis2-adb-codegen-1.3.jarUsed by Java2WSDL and WSDL2Java?
>>> axis2-clustering-1.3.jar ?
>>> axis2-codegen-1.3.jarWSDL2Java?
>>> axis2-fastinfoset-1.3.jar?
>>> axis2-java2wsdl-1.3.jar  Used by the Axis2 kernel to general WSDL
>>>  on the fly - Am I correct that this is also
>>>  used for the standalone tool?
>>> axis2-jaxbri-1.3.jar ?
>>> axis2-jaxws-1.3.jar  Used by kernel? Anything else make use of
>>> this?
>>> axis2-jaxws-api-1.3.jar  Used by kernel? Anything else make use of
>>> this?
>>> axis2-jibx-1.3.jar   Optional?
>>> axis2-json-1.3.jar   Optional? Do I need this if I don't want
>JSON
>>>
>>>  support?
>>> axis2-jws-api-1.3.jarJava Web Services API? Is this used by
>>> multiple
>>>  tools/runtimes?
>>> axis2-kernel-1.3.jar Core Axis2
>>> axis2-metadata-1.3.jar   ?
>>> axis2-mtompolicy-1.3.jar Optional?
>>> axis2-saaj-1.3.jar   SOAP attachments - optional?
>>> axis2-saaj-api-1.3.jar   SOAP attachments - optional?
>>> axis2-spring-1.3.jar Optional?
>>> axis2-xmlbeans-1.3.jar   Optional?
>>>
>>> Third Party
>>> 
>>> activation-1.1.jarMIME support
>>> annogen-0.1.0.jar Annotation support
>>> axiom-api-1.2.5.jar   XML pull parsing
>>> axiom-dom-1.2.5.jar   XML pull parsing
>>> axiom-impl-1.2.5.jar  XML pull parsing
>>> backport-util-concurrent-2.2.jar  ?
>>> commons-codec-1.3.jar URL encoding?
>>> commons-fileupload-1.1.1.jar  Used for uploading new service
>>>   files in the admin client?
>>> commons-httpclient-3.0.1.jar  Used by the Axis2 kernel?
>>> commons-io-1.2.jar?
>>> commons-logging-1.1.jar   Is this related to Log4J?
>>> geronimo-annotation_1.0_spec-1.1.jar  More annotation support?
>>> geronimo-jms_1.1_spec-1.1.jar JMS bindings?
>>> httpcore-4.0-alpha5.jar   Used by the Axis2 kernel?
>>> httpcore-nio-4.0-alpha5.jar   Used by the Axis2 kernel?
>>> httpcore-niossl-4.0-alpha5.jarUsed by the Axis2 kernel?
>>> jaxb-api-2.0.jar  Used by the Axis2 kernel?
>>> jaxb-impl-2.0.5.jar   Used by the Axis2 kernel?
>>> jaxb-xjc-2.0.5.jarUsed by the Axis2 kernel?
>>> jaxen-1.1.1.jar   XPath engine - where 

Deploy axis2 in WAS5.2.1

[mohcine]

hi
i m having serious troubles when trying to deploy axis2 in WAS5.1
pleae is there any tuto desciping this matter any help is welcome i am
really stuck in here
thanks
-- 
View this message in context: 
http://www.nabble.com/Deploy-axis2-in-WAS5.2.1-tf4628840.html#a13217009
Sent from the Axis - User mailing list archive at Nabble.com.


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

Re: Web Service REST + JSON

[Kimberly Nicholls]

Did you ever find an answer for this?  I would also like to use a mapped 
service with POJO services, but I've searched and searched and can't 
find any information on how to get it working.


I've tried adding elementFormDefaultQualified="false"/> to my service (found on the How to 
remove namespaces from SOAP response in Axis2 thread), and 
targetNamespace="" to my  tag. That gets me a response like this:


http://webservice.company.com"; 
xmlns:ax21="http://webservice.company.com/xsd";>

   kntest01
   kntest02


So there's  instead of , but there's still a 
namespace on the reponse, and I still get "Mapped formatted JSON with 
namespaces are not supported in Axis2. Make sure that your request 
doesn't include namespaces or use the Badgerfish convention" in my error 
log.


If I can't get this working, my next idea is to write some sort of 
handler that can parse the badgerfish output into something actually 
usable by a JavaScript developer, but it seems like I shouldn't have to 
do that...


Kimberly Nicholls

Karina Pereyra wrote:

I don't have errors using badgerfish but i want to parse it into
javascript and mapped is easier than badgerfish  to parse.

also i'm a neebie in java and axis2, could you suggest me some guides
to create services using axiom or how to specify namespaces to
default?

thanks a lot.




On 10/3/07, Thilina Gunarathne <[EMAIL PROTECTED]> wrote:
  

AFAIK POJO support by defualt generates namespaces. But you can try
specifying nameapce to package mapping pointing to the defualt
namespace... Not sure whether it'll work..

If not you will have to either create your service using Axiom or
using a code generation...

These are the results of impedence mismatch's between JSON and XML..

Also wat's the error you are getting with badgerfish.

Thanks,
Thilina

On 10/3/07, Karina Pereyra <[EMAIL PROTECTED]> wrote:


i'd like to use mapped service not badgerfish but when i try to use
mapped i have this error
Mapped formatted JSON with namespaces are not supported in Axis2.
Make sure that your request doesn't include namespaces or use the
Badgerfish convention.

do you know how i can remove namespaces?



On 10/3/07, keith chapman <[EMAIL PROTECTED]> wrote:
  

Sorry Karina I'm not very familiar with Badgerfish. Did you have a look at
http://wso2.org/library/768 ?

Thanks,
Keith.


On 10/3/07, Karina Pereyra <[EMAIL PROTECTED]> wrote:


I'm nearby of success.
I have now my pojo services with this method, but i have the last problem.
When i use Badgerfish response comes to client (response is difficult
to parse in javascript),
But when i use Mapped i have the next error:

Mapped formatted JSON with namespaces are not supported in Axis2.
Make sure that your request doesn't include namespaces or use the
Badgerfish convention.

How i could use mapped formatter in axis2 with pojo?

public User UserInfo(String username ) throws AxisFault{
MessageContext msgContext =

  

org.apache.axis2.context.MessageContext.getCurrentMessageContext().getCurrentMessageContext().getOperationContext().getMessageContext(
WSDLConstants.MESSAGE_LABEL_OUT_VALUE


);

  

msgContext.setProperty(Constants.Configuration.MESSAGE_TYPE,"application/json");


return (User)entries.get(username);
}


  

-


To unsubscribe, e-mail:
  

[EMAIL PROTECTED]


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


  


--
Keith Chapman
WSO2 Inc.
Oxygen for Web Services Developers.
http://wso2.org/


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


  

--
Thilina Gunarathne  - http://thilinag.blogspot.com

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





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



  

RE: Peculiar Issue while testing a service

[Gudla, Natraj (GE Money, consultant)]

Thanks for the response. But i made sure to delete the complete services.aar 
file and then regenerated it to make sure. On the other hand, as soon as i 
place these simple types into their own complex type, things work fine. 

-Original Message-
From: Jon Hanshew [mailto:[EMAIL PROTECTED]
Sent: 15 October 2007 16:54
To: axis-user@ws.apache.org
Subject: Re: Peculiar Issue while testing a service



Whenever this has happened to me, it was because I somehow failed to update
the server side with the new WSDL.  Either an unreplaced or unregenerated
jar or ...


Gudla, Natraj (GE Money, consultant) wrote:
> 
> Hi,
> 
> I am reporting a peculiar issue which i am facing since yesterday working
> with AXIS2 1.2. Addition of an extra simple element to an existing complex
> type of an xsd throws an "Un Expected Element" error. Following is the
> brief.
> 
> The current set up : Working Fine.
> 
> The complext type part of my xsd 
>   
>   
>type="GEM_Ln_LoanPreference"/>
>type="GEM_Ln_CustomerDetails"/>
>type="GEM_Ln_CustomerAddr"/>
>type="GEM_Ln_EmployerDetails"/>
>type="GEM_Ln_CustomerFinances"/>
>type="GEM_Ln_CardDetails"
> minOccurs="0"/>
>type="GEM_Ln_LoanDetails"
> minOccurs="0"/>
>   
>   
> 
> I used a wsdl, generated binding ( ADB ) classes using WSDL to Java tool
> on Axis2 1.2. Using the build.xml, running the jar.server task i created
> the services.aar and deployed on tomcat. Created a sample java class,
> which reads a sample loan request xml ( formed using IDE based on the xsd
> ) and submits a request to the service. 
> Every thing works fine, i get the response as i coded within the skeleton
> method. This looks fine end to end.
> 
> Change to the existing schema: : Not Working
> 
>   
>   
>   
>type="GEM_Ln_LoanPreference"/>
>type="GEM_Ln_CustomerDetails"/>
>type="GEM_Ln_CustomerAddr"/>
>type="GEM_Ln_EmployerDetails"/>
>type="GEM_Ln_CustomerFinances"/>
>type="GEM_Ln_CardDetails"
> minOccurs="0"/>
>type="GEM_Ln_LoanDetails"
> minOccurs="0"/>
>   
>   
> 
> I have a need to add new field to hold a product id. after this, i
> generated the binding classes again ( to make sure, i deleted all the
> existing classes, and re generated every thing ). Then did the same
> procedure as above to generated the services.aar, then created the sample
> java class callling the stub. Changed the sample xml file to add a product
> id tag and then executed the program. This time un expectedley i get the
> "Un expected sub element Product Id" error repeatedly.
> 
> Not sure what is the problem, this looks to be simple. I tried various
> combinations adding a test tag, then making product id a simple type etc
> etc. Any idea why this occurs. I made sure, i replaced the correct
> services.aar on the server. The new resource folder generated second time,
> properly refers to the product id which was included.
> 
> Just as a work around, i tested with some sample test and test simple
> tags, observed the xml input on TCP Monitor. For your reference attached
> is the request and response xmls from the monitory. Observe for the "test"
> and "testsimple" tags. The actual loan request xml read by my program is
> also attached for reference.
> 
>  <>  <>  <> 
> 
> Cheers
> -Natraj.
> 
> 
> 
> 
> 
> HTTP/1.1 500 Internal Server Error
> 
> Content-Type: text/xml;charset=UTF-8
> 
> Transfer-Encoding: chunked
> 
> Date: Tue, 09 Oct 2007 08:55:18 GMT
> 
> Server: Apache-Coyote/1.1
> 
> Connection: close
> 
> 
> 
> 147
> 
> 
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
>   
>  
> soapenv:Client
> java.lang.RuntimeException: Unexpected subelement
> testsimple
> 
>  
>   
>
> 0
> 
> 
> 
> POST /axis/services/LoanOriginationService HTTP/1.1
> 
> Content-Type: text/xml; charset=UTF-8
> 
> SOAPAction: "LoanOrigination"
> 
> User-Agent: Axis2
> 
> Host: 127.0.0.1:
> 
> Transfer-Encoding: chunked
> 
> 
> 
> bce
> 
> 
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
>   
>  
> 
>
>   User-Agent
>   IE/5.0 libwww/2.17b3
>
>
>   Date
>   Tue, Aug 21 2007 15:46:00 GMT
>
>
>   ClientIP
>   3.22.234.12
>
> 
> 
>Client1234
>ABCXYZ
>PASWDXYZ
> 
> 
>Test Simple
>Test
>
>

RE: NoClassDefFoundErrors ins AXIS2 aar

[Kahler, Jason J (US SSA)]

Ok sorry for all the spam I have just been frustrated over all these
classpath issues.

It seems that I am loading most jars from with my aar file now. But some
classes (related to hibernate) that are in the aar/lib/*.jar 

Still throw a NoClassDefFoundError. I read someones suggestion on using
the proper classloader, but I may not have access to make 

Those changes in the offending classes. 

 

I am just really stuck here.

 

 

 

  _  

From: Kahler, Jason J (US SSA) 
Sent: Monday, October 15, 2007 9:59 AM
To: axis-user@ws.apache.org
Subject: RE: NoClassDefFoundErrors ins AXIS2 aar

 

If I copy all the needed jars over to AXIS2_HOME/WEB-INF/lib 

Most of my NoClassDefFoundErrors disappear and my Web Service

Get much farther. Then I get another NoClassDefFoundError but this time
it is a class 

Generated by my wsdl. It is in the same package as my generated server
code in the aar.

How is it possible that axis can't find it ? I mean the first call in
the execution chain is in a 

Service class in the exact same package ?

 

  _  

From: Kahler, Jason J (US SSA) 
Sent: Monday, October 15, 2007 8:15 AM
To: axis-user@ws.apache.org
Subject: RE: NoClassDefFoundErrors ins AXIS2 aar

 

I found an article that explains using the ClassLoader loader =
getClass().getClassLoader();

Then load the class using that loader.

 

Problem is that I am using a large number of my own and Third Party jar
files. Do I need to 

Do that for every class? I just wanted to add my jars to my aar/lib dir
and be done with it.

 

 

 

  _  

From: Kahler, Jason J (US SSA) 
Sent: Monday, October 15, 2007 7:13 AM
To: axis-user@ws.apache.org
Subject: RE: NoClassDefFoundErrors ins AXIS2 aar

 

Can you elaborate, I am not sure how to do this. Also others have
indicated what I am doing Should work fine.

 

Thanks;

 

  _  

From: Chad DeBauch [mailto:[EMAIL PROTECTED] 
Sent: Saturday, October 13, 2007 5:03 PM
To: axis-user@ws.apache.org
Subject: Re: NoClassDefFoundErrors ins AXIS2 aar

 

The jars in your lib aar directory will be loaded in a separate
classloader.  So you must reference those classes using that
classloader.  You can do this by getting the MessageContext.

Chad

On 10/12/07, Kahler, Jason J (US SSA) <[EMAIL PROTECTED]>
wrote:

I am building my aar using the maven2 pluggin. Everything builds but
when I deploy I get NoClassDefFound 
ERRORS all over. This was working as a war in tomcat using axis 1. All
the required jars are in

 

myArr.arr/lib what could be wrong ?

 

Jay

 

Re: Error: Unexpected subelement responseCode

[M K]

Ok. The wsdl does have the attribute set to "qualified". Here is my wsdl again.



StompHub



























http://inbound.adapters.transport.stomp.ens.com/xsd"/>






















































































http://localhost:8080/services/services/StompHub"/>


http://localhost:8080/services/services/StompHub"/>


http://localhost:8080/services/services/StompHub"/>




Thanks,
-- MK
- Original Message 
From: Anne Thomas Manes <[EMAIL PROTECTED]>
To: axis-user@ws.apache.org
Sent: Saturday, October 13, 2007 10:42:48 AM
Subject: Re: Error: Unexpected subelement responseCode

This attribute would be in the schema in the WSDL file -- not in the
services.xml file.

On 10/11/07, M K <[EMAIL PROTECTED]> wrote:
>
> No, the services.xml does not have elementFormDefault="qualified".
 Here is
> my services.xml:
>
> 
> 
> Stomp Hub Service
> 
> 
>  mep="http://www.w3.org/2004/08/wsdl/in-only";
>
> class="org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver"/>
>  mep="http://www.w3.org/2004/08/wsdl/in-out";
>
> class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>
> 
> 
>
>
 com.ens.stomp.transport.adapters.inbound.webservices.stomphub.StompHubServices
> 
> 
>
> Thanks,
> -- MK
>
>
>
> - Original Message 
> From: Anne Thomas Manes <[EMAIL PROTECTED]>
> To: axis-user@ws.apache.org
> Sent: Thursday, October 11, 2007 9:57:55 AM
> Subject: Re: Error: Unexpected subelement responseCode
>
>
> Your schema statements don't appear in the WSDL you posted -- do they
> specify elementFormDefault="qualified"?
>
> Anne
>
> On 10/10/07, M K <[EMAIL PROTECTED]> wrote:
> >
> > Hello,
> >
> > I am using axis2 1.3 and deploy me service on JBOSS 4.0.5. I am
 getting
> > following error when I run my client:
> >
> *
> > org.apache.axis2.AxisFault:
> > org.apache.axis2.databinding.ADBException: Unexpected
> > subelement responseCode
> > at
> > org.apache.axis2.AxisFault.makeFault(AxisFault.java:417)
> > at
> >
>
 
com.ens.stomp.transport.adapters.inbound.webservices.stomphub.StompHubStub.fromOM(StompHubStub.java:5270)
> > at
> >
>
 
com.ens.stomp.transport.adapters.inbound.webservices.stomphub.StompHubStub.transmit(StompHubStub.java:180)
> > at
> >
>
 
webservice.clients.StompHubClientUsingStubsWithWSDL.main(StompHubClientUsingStubsWithWSDL.java:35)
> > Caused by: java.lang.Exception:
> > org.apache.axis2.databinding.ADBException: Unexpected
> > subelement responseCode
> > at
> >
>
 
com.ens.stomp.transport.adapters.inbound.webservices.stomphub.StompHubStub$StompHubResponse$Factory.parse(StompHubStub.java:4491)
> > at
> >
>
 
com.ens.stomp.transport.adapters.inbound.webservices.stomphub.StompHubStub$TransmitResponse$Factory.parse(StompHubStub.java:789)
> > at
> >
>
 
com.ens.stomp.transport.adapters.inbound.webservices.stomphub.StompHubStub.fromOM(StompHubStub.java:5264)
> > ... 2 more
> > Caused by: org.apache.axis2.databinding.ADBException:
> > Unexpected subelement responseCode
> > at
> >
>
 
com.ens.stomp.transport.adapters.inbound.webservices.stomphub.StompHubStub$StompHubResponse$Factory.parse(StompHubStub.java:4485)
> > ... 4 more
> >






   

Pinpoint customers who are looking for what you sell.

Re: Peculiar Issue while testing a service

[Jon Hanshew]

Whenever this has happened to me, it was because I somehow failed to update
the server side with the new WSDL.  Either an unreplaced or unregenerated
jar or ...


Gudla, Natraj (GE Money, consultant) wrote:
> 
> Hi,
> 
> I am reporting a peculiar issue which i am facing since yesterday working
> with AXIS2 1.2. Addition of an extra simple element to an existing complex
> type of an xsd throws an "Un Expected Element" error. Following is the
> brief.
> 
> The current set up : Working Fine.
> 
> The complext type part of my xsd 
>   
>   
>type="GEM_Ln_LoanPreference"/>
>type="GEM_Ln_CustomerDetails"/>
>type="GEM_Ln_CustomerAddr"/>
>type="GEM_Ln_EmployerDetails"/>
>type="GEM_Ln_CustomerFinances"/>
>type="GEM_Ln_CardDetails"
> minOccurs="0"/>
>type="GEM_Ln_LoanDetails"
> minOccurs="0"/>
>   
>   
> 
> I used a wsdl, generated binding ( ADB ) classes using WSDL to Java tool
> on Axis2 1.2. Using the build.xml, running the jar.server task i created
> the services.aar and deployed on tomcat. Created a sample java class,
> which reads a sample loan request xml ( formed using IDE based on the xsd
> ) and submits a request to the service. 
> Every thing works fine, i get the response as i coded within the skeleton
> method. This looks fine end to end.
> 
> Change to the existing schema: : Not Working
> 
>   
>   
>   
>type="GEM_Ln_LoanPreference"/>
>type="GEM_Ln_CustomerDetails"/>
>type="GEM_Ln_CustomerAddr"/>
>type="GEM_Ln_EmployerDetails"/>
>type="GEM_Ln_CustomerFinances"/>
>type="GEM_Ln_CardDetails"
> minOccurs="0"/>
>type="GEM_Ln_LoanDetails"
> minOccurs="0"/>
>   
>   
> 
> I have a need to add new field to hold a product id. after this, i
> generated the binding classes again ( to make sure, i deleted all the
> existing classes, and re generated every thing ). Then did the same
> procedure as above to generated the services.aar, then created the sample
> java class callling the stub. Changed the sample xml file to add a product
> id tag and then executed the program. This time un expectedley i get the
> "Un expected sub element Product Id" error repeatedly.
> 
> Not sure what is the problem, this looks to be simple. I tried various
> combinations adding a test tag, then making product id a simple type etc
> etc. Any idea why this occurs. I made sure, i replaced the correct
> services.aar on the server. The new resource folder generated second time,
> properly refers to the product id which was included.
> 
> Just as a work around, i tested with some sample test and test simple
> tags, observed the xml input on TCP Monitor. For your reference attached
> is the request and response xmls from the monitory. Observe for the "test"
> and "testsimple" tags. The actual loan request xml read by my program is
> also attached for reference.
> 
>  <>  <>  <> 
> 
> Cheers
> -Natraj.
> 
> 
> 
> 
> 
> HTTP/1.1 500 Internal Server Error
> 
> Content-Type: text/xml;charset=UTF-8
> 
> Transfer-Encoding: chunked
> 
> Date: Tue, 09 Oct 2007 08:55:18 GMT
> 
> Server: Apache-Coyote/1.1
> 
> Connection: close
> 
> 
> 
> 147
> 
> 
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
>   
>  
> soapenv:Client
> java.lang.RuntimeException: Unexpected subelement
> testsimple
> 
>  
>   
>
> 0
> 
> 
> 
> POST /axis/services/LoanOriginationService HTTP/1.1
> 
> Content-Type: text/xml; charset=UTF-8
> 
> SOAPAction: "LoanOrigination"
> 
> User-Agent: Axis2
> 
> Host: 127.0.0.1:
> 
> Transfer-Encoding: chunked
> 
> 
> 
> bce
> 
> 
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
>   
>  
> 
>
>   User-Agent
>   IE/5.0 libwww/2.17b3
>
>
>   Date
>   Tue, Aug 21 2007 15:46:00 GMT
>
>
>   ClientIP
>   3.22.234.12
>
> 
> 
>Client1234
>ABCXYZ
>PASWDXYZ
> 
> 
>Test Simple
>Test
>
>   34546.78
>   1
>   02
>   0
>   01
>
>
>   Mr
>   John
>   M
>   S
>   2001-01-01Z
>   M
>   2
>
>
>   U
>   011321897

Re: [ANN] Apache Savan/C 0.90 Released

[Demetris G]

Is there a Savan/Java ?

Damitha Kumarage wrote:

Hi List,
Apache Savan/C Team is pleased to announce the release of Apache 
Savan/C version 0.90

You can download this release from
http://ws.apache.org/savan/c/download.cgi
This release is supposed to be used with the Axis2C 1.1.0 distribution 
which is released recently.


Key Features:

1 Support for WS-Eventing Specification August 2004.
2 Support for Subscribe, Unsubscribe, Renew and GetStatus operations.
3 Support for subscription management endpoint which could be the
Event Source itself or separate subscription management endpoint.
4 Persistent storage for subscribers.
5 Support for both SOAP 1.1 and 1.2.
6 Samples to test scenarios.
7 Documentation

We welcome your early feedback on this implementation.
Thanks for your interest in Savan/C

-- Apache Savan/C Team -- 


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

Re: How to send WS-Addressing headers in AXIOM based client

[Jon Hanshew]

Your "setAction" code will be overwritten in the generated
stub.java code on the client.

Search for "setAction" in the stub.java code.  You will see
that the Action is driven by the WSDL.  If the WSDL is not alterable, you
will have to modify the generated code.

Good Luck,

Jon



Ralph Fernandes wrote:
> 
> I have Axis2-1.3 and am trying to send WS-Addressing headers in the
> request
> using the code snippet below. The only header that gets set is the
> SOAPAction (HTTP) header, but none of the SOAP envelope headers, viz. To,
> From, Action, MessageID. If I try to explicitly engage the module, I get a
> runtime error "unable to engage module". I understood that to enable the
> addressing module, the axis2.xml file needs to have the module entry
> un-commented, which it is by default.
> 
> What should I be doing to get the To, Action, From, Msg. ID sent in the
> SOAP
> header? Besides the default module configuration in axis2.xml, is there
> any
> other configuration?
> 
> (I am not using the wsdl2java ADB code generation since it does not work
> for
> our WSDLs.)
> 
> 
> Thanks
> 
> -
> 
> // TestAXIOMClient.java
> ...
> public static void main(String[] args) {
> // TODO Auto-generated method stub
> OMElement req = createRequestDocument();
> Options options = new Options();
> options.setTo (targetEPR);
> options.setAction(wsaAction);
> options.setFrom(wsaFrom);
> options.setMessageId("ab838db4-c0e5-11da-90b6-7be9a196b6d2");
> options.setTransportInProtocol (Constants.TRANSPORT_HTTP);
> 
> try {
> ServiceClient sender = new ServiceClient();
> sender.engageModule("addressing"); // throws runtime exception below
> sender.setTargetEPR (targetEPR);
> 
> sender.setOptions(options);
> sender.sendReceive(req);
> } catch (java.lang.Exception e) {
> e.printStackTrace();
> }
> 
> }
> 
> 
> 
> ---
> 
> org.apache.axis2.AxisFault: Unable to engage module : addressing
> at org.apache.axis2.client.ServiceClient.engageModule(ServiceClient.java
> :339)
> at com.frk.corp.noam.sharedservices.TestAXIOMClient.main(
> TestAXIOMClient.java :53)
> 
> 

-- 
View this message in context: 
http://www.nabble.com/How-to-send-WS-Addressing-headers-in-AXIOM-based-client-tf4611331.html#a13214829
Sent from the Axis - User mailing list archive at Nabble.com.


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

Re: problem of soap version in axis2/java 1.2

[donald yang]

Hi Thilina,

thank you very much for your reply.

How can I modify axis2.xml in the server side for axis2/java 1.2? So that I
can send the new full stack trace.

best regards
yong

On 10/12/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> This can be due to the action= parameter of the content type of
> the MIME message generated by Axis2/c (Notice the unnecessary
> quotes)...  Modify your Axis2.xml of the server to send the full stack
> trace with faults and post the full stack trace..
>
> Also log a JIRA with Axis2/C.
>
> ~Thilina
>
>
>
> On 10/12/07, donald yang <[EMAIL PROTECTED]> wrote:
> > Hi Keith,
> >
> > Thanks for your reply. The problem I currently have is that I will
> reveive
> > an exception "Invalid Content Type Field in the Mime Message"  as a SOAP
> > reply when I set the soap version to 1.2 in the web service client
> written
> > using AXIS2/C 1.0. But when I set the soap version to 1.1 in the web
> service
> > client, it works as what I expect.  The environment for this test case
> is as
> > follows:
> >
> >  Web service Client: use AXIS2/C 1.0
> >  Web Service: POJO web serice and AXIS2/JAVA 1.2
> >  WSDL : automatically generated by AXIS2/JAVA 1.2 which has three
> port:
> > HTTP, SOAP1.2, SOAP1.1
> >
> > The soap messages for this test case can be found in the attachment.
> >
> > best regards
> > donald
> >
> > On 10/12/07, keith chapman <[EMAIL PROTECTED]> wrote:
> > >
> > > No need to change anything. If the request is SOAP 1.1 the response
> will
> > > be SOAP 1.1. if it is SOAP 1.2 the response will be SOAP 1.2.
> > >
> > > Thanks,
> > > Keith.
> > >
> > > On 10/12/07, donald yang <[EMAIL PROTECTED]> wrote:
> > > >
> > > > Hi everyone,
> > > >
> > > > First I wrote a simple web service using AXIS2/JAVA 1.2. Then I
> wrote a
> > > > web service client test case using AXIS2/C 1.0 to access the web
> > > > service. In the client,  I have enabled MTOM even if there is no
> binaary
> > > > attachment to send in fact and set the SOAP version to SOAP 1.2. I
> got
> > > > one exception
> > > >
> > > >  " Invalid Content Type Field in the Mime Message"
> > > >
> > > > Then I compared the soap request created by AXIS2/C 1.0 with the
> soap
> > > > request created by AXIS2/JAVA 1.2. I found the major difference is
> that
> > > > the value of start-info is "application/xop+xml" not "text/xml" in
> the
> > soap
> > > > request created by AXIS2/C.
> > > >
> > > > Then I resetting the SOAP vesion to SOAP 1.1 in the web service
> client
> > > > wrote using AXIS2/C 1.0. It works fine. But when I looked at the
> wsdl
> > > > generated by AXIS2/JAVA 1.2, it has three ports, HTTP PORT, SOAP
> > 1.1PORT,
> > > > SOAP1.2 PORT. That means it should support the SOAP request with
> version
> > > > 1.2. Is there anyone can tell me how to enable  the server support
> SOAP
> > > > 1.2 in AXIS2/JAVA 1.2? many thanks in advnace.
> > > >
> > > > best regards
> > > > yong
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > Keith Chapman
> > > WSO2 Inc.
> > > Oxygen for Web Services Developers.
> > > http://wso2.org/
> >
>
>
> --
> Thilina Gunarathne  - http://thilinag.blogspot.com
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

RE: No serializer found for class in registry TypeMappingDelegate

[Walker, Jeff]

Alexey,
I'm glad you solved it. Well done.
Sorry I couldn't help more.
-jeff

-Original Message-
From: Alexey Zavizionov [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 15, 2007 10:40 AM
To: axis-user@ws.apache.org
Cc: Roman Pedchenko; Gennady Azarenkov
Subject: Re: No serializer found for class in registry
TypeMappingDelegate

Hello, Jeff

Sorry for the late reply.
I was impressed with your long and understandable answer to my
incomprehensible question .
By now I have solved the problem.

---
Need to serialize (marshal) event Object to Document and then create
MessageElement with it.
On the other side deserialize (unmarshal) it direct to MessageElement.
---

Thanks and regards,
Alexey.

On 10/10/07, Walker, Jeff <[EMAIL PROTECTED]> wrote:
> Alexey,
> Let's step back for a minute. I'm confused as to your system setup.
> Let's go over the basics of Axis1-1.4 first.
>
> Assuming you started with a wsdl file first (Top-Down approach) and
also
> assuming you are creating a Document/Literal based wsdl, you must
create
> XML Schema for every Java class that you intend to send over the
> service. Therefore, the MyEventPub class (which I take it you are
trying
> to send over the wire) must have equivalent XML Schema created for it,
> or at least imported from an external xsd file into your wsdl file.
> Therefore, to send it over the wire, you need to know the structure of
> this class in advance (so that you can write schema for it).
>
> The WSDL2Java generator will read the schema in the wsdl and
essentially
> create two classes for each element/complexType it finds. One is to
> serialize the class (put it into xml) the other is to deserialize it
> (take it from xml and back into a Java object). This is a simplified
> view of the process, but it is essentially correct.
>
> Also generated for you, is a deploy.wsdd file. In the deploy.wsdd
file,
> there are some namespace declarations. And then a section that
describes
> the service, such as what methods are exposed publicly, the port name
> (which is the name of the web service), the name of your skeleton
class
> (which is used by Axis to make sure the correct operation is called on
> your interface), and so on. Further down in deploy.wsdd there are type
> mappings. This is where Axis learns about the classes that can be
> serialized/deserialized. Each type mapping essentially holds a
qualified
> namespace, the type of object your transferring (that is, the package
> and name of your class), and the names of the serializer and
> deserializer classes that will do the work for that type.
>
> Now, your original post hinted that a type mapping was missing from
the
> wsdd file, for the MyEventPub class. There maybe some strange
situations
> where a type mapping may not be created by the generator, even though
> the MyEventPub class has an schema equivalent in the wsdl file. But I
> suspected (in my first reply) that the problem was that you did not
> create any schema for MyEventPub in the first place and so Axis had no
> way of knowing how to serialize/deserialize it. Hence, the type
mapping
> exception.
>
> Now, your following question asks where can you 'store' MyEventPub
> within MessageElement. The problem here, is that your hinting at
trying
> to construct the soap parse tree yourself, and then presumably
serialize
> that tree (with the MyEventPub fields in it somewhere). I strongly
> recommend that you do not approach your web service from this angle. I
> cannot help you further with this direction. (Perhaps you have
previous
> experience with RPC-encoded services and serializing graphs of
objects?
> If not, then this approach will be a difficult task indeed).
>
> I recommend you define MyEventPub in schema (in the wsdl) and let Axis
> do 95% of the work for you. I also recommend that you adopt the
> Document/Literal-Wrapped wsdl format (go here to learn about it:
> http://www.ibm.com/developerworks/webservices/library/ws-whichwsdl/),
> and abandon any attempt at an RPC service. You will get virtually no
> help from this mailing list if you choose to continue with an
RPC-based
> wsdl. (That is because a wsdl based on RPC is essentially deprecated
as
> a web service design, and nobody does web services like that anymore.
> Why not?Because RPC-Encoded is not WSI compliant. There is no standard
> way to interpret the serialize object graph across every platform that
> could conceivably call your service).
>
> In Document Literal-Wrapped, the methods on your interface take a
single
> object and return a single object. Those two objects can obviously
have
> multiple objects within them. Each object is based on schema in your
> wsdl. This is the approach everybody else takes with web services
these
> days.
>
> One more thing. There are only a few of us left still using Axis1.4 on
> our projects. Nearly all subscribers of the Axis mailing list are
using
> Axis2. You cannot use Axis2 to do an RPC Encoded service.
> Does any of this help?
> -jeff
>
>
>
> -Or

Re: No serializer found for class in registry TypeMappingDelegate

[Alexey Zavizionov]

Hello, Jeff

Sorry for the late reply.
I was impressed with your long and understandable answer to my
incomprehensible question .
By now I have solved the problem.

---
Need to serialize (marshal) event Object to Document and then create
MessageElement with it.
On the other side deserialize (unmarshal) it direct to MessageElement.
---

Thanks and regards,
Alexey.

On 10/10/07, Walker, Jeff <[EMAIL PROTECTED]> wrote:
> Alexey,
> Let's step back for a minute. I'm confused as to your system setup.
> Let's go over the basics of Axis1-1.4 first.
>
> Assuming you started with a wsdl file first (Top-Down approach) and also
> assuming you are creating a Document/Literal based wsdl, you must create
> XML Schema for every Java class that you intend to send over the
> service. Therefore, the MyEventPub class (which I take it you are trying
> to send over the wire) must have equivalent XML Schema created for it,
> or at least imported from an external xsd file into your wsdl file.
> Therefore, to send it over the wire, you need to know the structure of
> this class in advance (so that you can write schema for it).
>
> The WSDL2Java generator will read the schema in the wsdl and essentially
> create two classes for each element/complexType it finds. One is to
> serialize the class (put it into xml) the other is to deserialize it
> (take it from xml and back into a Java object). This is a simplified
> view of the process, but it is essentially correct.
>
> Also generated for you, is a deploy.wsdd file. In the deploy.wsdd file,
> there are some namespace declarations. And then a section that describes
> the service, such as what methods are exposed publicly, the port name
> (which is the name of the web service), the name of your skeleton class
> (which is used by Axis to make sure the correct operation is called on
> your interface), and so on. Further down in deploy.wsdd there are type
> mappings. This is where Axis learns about the classes that can be
> serialized/deserialized. Each type mapping essentially holds a qualified
> namespace, the type of object your transferring (that is, the package
> and name of your class), and the names of the serializer and
> deserializer classes that will do the work for that type.
>
> Now, your original post hinted that a type mapping was missing from the
> wsdd file, for the MyEventPub class. There maybe some strange situations
> where a type mapping may not be created by the generator, even though
> the MyEventPub class has an schema equivalent in the wsdl file. But I
> suspected (in my first reply) that the problem was that you did not
> create any schema for MyEventPub in the first place and so Axis had no
> way of knowing how to serialize/deserialize it. Hence, the type mapping
> exception.
>
> Now, your following question asks where can you 'store' MyEventPub
> within MessageElement. The problem here, is that your hinting at trying
> to construct the soap parse tree yourself, and then presumably serialize
> that tree (with the MyEventPub fields in it somewhere). I strongly
> recommend that you do not approach your web service from this angle. I
> cannot help you further with this direction. (Perhaps you have previous
> experience with RPC-encoded services and serializing graphs of objects?
> If not, then this approach will be a difficult task indeed).
>
> I recommend you define MyEventPub in schema (in the wsdl) and let Axis
> do 95% of the work for you. I also recommend that you adopt the
> Document/Literal-Wrapped wsdl format (go here to learn about it:
> http://www.ibm.com/developerworks/webservices/library/ws-whichwsdl/),
> and abandon any attempt at an RPC service. You will get virtually no
> help from this mailing list if you choose to continue with an RPC-based
> wsdl. (That is because a wsdl based on RPC is essentially deprecated as
> a web service design, and nobody does web services like that anymore.
> Why not?Because RPC-Encoded is not WSI compliant. There is no standard
> way to interpret the serialize object graph across every platform that
> could conceivably call your service).
>
> In Document Literal-Wrapped, the methods on your interface take a single
> object and return a single object. Those two objects can obviously have
> multiple objects within them. Each object is based on schema in your
> wsdl. This is the approach everybody else takes with web services these
> days.
>
> One more thing. There are only a few of us left still using Axis1.4 on
> our projects. Nearly all subscribers of the Axis mailing list are using
> Axis2. You cannot use Axis2 to do an RPC Encoded service.
> Does any of this help?
> -jeff
>
>
>
> -Original Message-
> From: Alexey Zavizionov [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 10, 2007 8:28 AM
> To: axis-user@ws.apache.org; [EMAIL PROTECTED]; Roman
> Pedchenko
> Subject: Re: No serializer found for class in registry
> TypeMappingDelegate
>
> Thanks for reply!
>
> This MyEventPub is the sample user's class fired a

RE: sending calendar object in axis stub

[Walker, Jeff]

Hi Senthil,
shame on them for writing a language-specific web serivce!
 
Anyway, if they are the authors of the web service and you are the
client, then you must have gotten the wsdl from them. The wsdl must have
a complexType in it that declares the issuedDate as non-nillable.  But I
can't tell why the line "transfer.setIssueDate(Calendar.getInstance());"
failed.
You'll have to debug it and step through slowly at this point to see if
the instance returned from Calendar.getInstance() is null or not. (If it
is not null, then it is getting nulled out later before the stub
attempts to serialize everything).
This is my guess.
-jeff
 
  _  

From: Senthivel U S [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 15, 2007 9:38 AM
To: axis-user@ws.apache.org
Subject: RE: sending calendar object in axis stub



Hi Jeff,

 

Thanks for your comments and I do agree with you. The service
was deployed by third party and I want to consume the service. I have
created my stub using wsdl (Eclipse IDE).

 

TIA,

-senthil

 

 


  _  


From: Walker, Jeff [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 15, 2007 5:08 PM
To: axis-user@ws.apache.org
Subject: RE: sending calendar object in axis stub

 

Hi Senthil,

Don't pass language specific constructs like Calendar, in a web
service call.

 

You are better taking the less obvious route; just pass the
minimal amount number fo fields in the Calendar object that can be used
by a client to regenerate the equivalent object on their side. That is,
build a new complexType in XML Schema and use Doc/Lit-wrapped web
services.

 

The main reason is simply, interoperability. Even of you know
all of your clients will be Java going forward, it's bad practice to
pass language specific objects in a web service. If indeed all of your
clients will always be Java, then you would benefit from RMI or EJB
where you would get a significant speed increase. Web Services is for
interoperability across disparate systems.

Regards,

-jeff

 


  _  


From: Senthivel U S [mailto:[EMAIL PROTECTED]

Sent: Monday, October 15, 2007 8:27 AM
To: axis-user@ws.apache.org
Subject: sending calendar object in axis stub

Hi,

 

I have a stub, in that I want to pass calendar object,
while passing I am getting the following error.  Is any serializer to be
included to pass calendar object.

 

java.io.IOException: Non nillable element 'issuedDate'
is null.

at
org.apache.axis.encoding.ser.BeanSerializer.serialize(BeanSerializer.jav
a:215)

at
org.apache.axis.encoding.SerializationContext.serializeActual(Serializat
ionContext.java:1502)

 

My code is 

 

transfer.setIssueDate(Calendar.getInstance());

stub.insertTransfer(transfer);

 

TIA,

-senthil

 

Re: [Axis2] Exception handling, differentiating server down, service unavailable, and normal business logic error

[Xinjun Chen]

I think this issue should be a common issue.
Has anyone encountered this problem before?

Regards,
Xinjun


On 10/8/07, Xinjun Chen <[EMAIL PROTECTED]> wrote:
>
> Hi Axis2 users,
>
> I am writing a web service client using Axis2. In the code, I am trying to
> handle the exception. If the exception is due to server down, web service
> unvailable, or any other connectivity problem, I will trigger another
> invocation using another URL. If the exception is due to client input error
> or other error in the web service, as long as the request has reached the
> web service, I will not trigger the second invocation.
>
> Initially, I was thinking of the following code:
>
>
>mepClient = outInOperation.createClient(serviceContext, options);
>mepClient.addMessageContext(mc);
>
>/**
> * Invokes the end web service.
> */
>try {
> mepClient.execute(true);
>} catch (Exception e) {
> // Here I need to differentiate the causes of the exception and
> handle it accordingly
>}
>
> But I am wondering whether this is correct. Can any Axis2 guru enlighten
> me?
>
> Is there a way for me to get the status code of the HTTP response?
>
>
> Regards,
> Xinjun
>
>
>

Re: axis1 Runtime object creation on server

[Alexey Zavizionov]

[SOLVED]

Need to serialize (marshal) it to Document and then create
MessageElement with it.
On the other side deserialize (unmarshal) it direct to MessageElement.

Regards,
Alexey

On 10/6/07, Alexey Zavizionov <[EMAIL PROTECTED]> wrote:
> Hello list!
>
> I wont to know what shold I do to be able server store within
> "org.apache.axis.message.MessageElement" any runtime generated object
> for client?
>
> Any changes on client?
>
> Thanks,
> Alexey
>

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

RE: NoClassDefFoundErrors ins AXIS2 aar

[Kahler, Jason J (US SSA)]

If I copy all the needed jars over to AXIS2_HOME/WEB-INF/lib 

Most of my NoClassDefFoundErrors disappear and my Web Service

Get much farther. Then I get another NoClassDefFoundError but this time
it is a class 

Generated by my wsdl. It is in the same package as my generated server
code in the aar.

How is it possible that axis can't find it ? I mean the first call in
the execution chain is in a 

Service class in the exact same package ?

 

  _  

From: Kahler, Jason J (US SSA) 
Sent: Monday, October 15, 2007 8:15 AM
To: axis-user@ws.apache.org
Subject: RE: NoClassDefFoundErrors ins AXIS2 aar

 

I found an article that explains using the ClassLoader loader =
getClass().getClassLoader();

Then load the class using that loader.

 

Problem is that I am using a large number of my own and Third Party jar
files. Do I need to 

Do that for every class? I just wanted to add my jars to my aar/lib dir
and be done with it.

 

 

 

  _  

From: Kahler, Jason J (US SSA) 
Sent: Monday, October 15, 2007 7:13 AM
To: axis-user@ws.apache.org
Subject: RE: NoClassDefFoundErrors ins AXIS2 aar

 

Can you elaborate, I am not sure how to do this. Also others have
indicated what I am doing Should work fine.

 

Thanks;

 

  _  

From: Chad DeBauch [mailto:[EMAIL PROTECTED] 
Sent: Saturday, October 13, 2007 5:03 PM
To: axis-user@ws.apache.org
Subject: Re: NoClassDefFoundErrors ins AXIS2 aar

 

The jars in your lib aar directory will be loaded in a separate
classloader.  So you must reference those classes using that
classloader.  You can do this by getting the MessageContext.

Chad

On 10/12/07, Kahler, Jason J (US SSA) <[EMAIL PROTECTED]>
wrote:

I am building my aar using the maven2 pluggin. Everything builds but
when I deploy I get NoClassDefFound 
ERRORS all over. This was working as a war in tomcat using axis 1. All
the required jars are in

 

myArr.arr/lib what could be wrong ?

 

Jay

 

RE: sending calendar object in axis stub

[Senthivel U S]

Hi Jeff,

 

Thanks for your comments and I do agree with you. The service was deployed
by third party and I want to consume the service. I have created my stub
using wsdl (Eclipse IDE).

 

TIA,

-senthil

 

 

  _  

From: Walker, Jeff [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 15, 2007 5:08 PM
To: axis-user@ws.apache.org
Subject: RE: sending calendar object in axis stub

 

Hi Senthil,

Don't pass language specific constructs like Calendar, in a web service
call.

 

You are better taking the less obvious route; just pass the minimal amount
number fo fields in the Calendar object that can be used by a client to
regenerate the equivalent object on their side. That is, build a new
complexType in XML Schema and use Doc/Lit-wrapped web services.

 

The main reason is simply, interoperability. Even of you know all of your
clients will be Java going forward, it's bad practice to pass language
specific objects in a web service. If indeed all of your clients will always
be Java, then you would benefit from RMI or EJB where you would get a
significant speed increase. Web Services is for interoperability across
disparate systems.

Regards,

-jeff

 

  _  

From: Senthivel U S [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 15, 2007 8:27 AM
To: axis-user@ws.apache.org
Subject: sending calendar object in axis stub

Hi,

 

I have a stub, in that I want to pass calendar object, while passing I am
getting the following error.  Is any serializer to be included to pass
calendar object.

 

java.io.IOException: Non nillable element 'issuedDate' is null.

at
org.apache.axis.encoding.ser.BeanSerializer.serialize(BeanSerializer.java:21
5)

at
org.apache.axis.encoding.SerializationContext.serializeActual(SerializationC
ontext.java:1502)

 

My code is 

 

transfer.setIssueDate(Calendar.getInstance());

stub.insertTransfer(transfer);

 

TIA,

-senthil

 

RE: [wsf-php-user] key failure *update*

[shams jawaid]

HI, just wanted to say that, 
 
in using tomcat 5.5 i used axis2 1.2, and tomcat 6 - axis2 1.3 for my example.
 
thanks


From: [EMAIL PROTECTED]: [EMAIL PROTECTED]; [EMAIL PROTECTED]: [EMAIL 
PROTECTED]: RE: [wsf-php-user] key failureDate: Mon, 15 Oct 2007 05:51:38 +


Hi kaushalye,  i did this in tomcat 5.5 then in tomcat 6. i attached both the 
outputs in the tomcat window and in tcpmon,  thanks > Date: Mon, 15 Oct 2007 
11:07:12 +0530> From: [EMAIL PROTECTED]> To: [EMAIL PROTECTED]> CC: [EMAIL 
PROTECTED]; axis-user@ws.apache.org> Subject: Re: [wsf-php-user] key failure> > 
Hi Shams,> I think if you could attach a trace of the SOAP message, 
Rampart/Java > guys may be able to find the reason for the fault string in the 
> response. The complaint is about a missing encryption result for an > 
Id(NULL?), which they have to match with the message. The PHP client and > its 
configurations seems to be correct.> -Kaushalye> > shams jawaid wrote:> > Hi,> 
> > > i am currently trying to encrypt and sign a simple service from a php > > 
client to a java web service. the request is encrypted and signed, but > > the 
service side response recieves this error in tcpmon:> > > > 
Missing encryption result for id : > > > > and in 
tomcat, this is the output:> > > > INFO: Server startup in 3734 ms> > [INFO] 
Verification successful for URI '#SigID-402a0180-2c19-4f2e'> > [INFO] 
Verification successful for URI '#SigID-a673ae2e-5835-4d1f'> > > > in my client 
side, i have included the keys:> > > > $my_cert = 
ws_get_cert_from_file('alice_cert.cert'); // client side > > certificate( 
public key)> > $my_key = ws_get_key_from_file('alice_key.pem'); // client side 
key> > $rec_cert = ws_get_cert_from_file('bob_cert.cert'); // server side > > 
certificate (public key )> > > > and in my service side key (service.jks) 
referenced like this:> > > > > > > >  
> 
name='org.apache.ws.security.crypto.merlin.keystore.type'>JKS> 
>  > 
name='org.apache.ws.security.crypto.merlin.file'>service.jks> > 
 > 
name='org.apache.ws.security.crypto.merlin.keystore.password'>apache>
 > > > > > > > 
> > 
 > 
name='org.apache.ws.security.crypto.merlin.keystore.type'>JKS> 
>  > 
name='org.apache.ws.security.crypto.merlin.file'>service.jks> > 
 > 
name='org.apache.ws.security.crypto.merlin.keystore.password'>apache>
 > > > > > > > > > i 
have includeded :> > > > [1] alice_cert> > [2] bob_cert> > [3] bob_key 
(although i am unsure whether this was imported properly, > > and am thinking 
this might be the cause of the error)> > > > i have attached my 
service.properties, service.jks, PWCBHandler.class, > > services.xml and my 
service file.> > > > i have also attached my client side files including the 
alice_key, > > alice_cert, bob_cert, php client file and the policy.xml file.> 
> > > If anyone can solve this error out there it would be a tremendous > > 
help, or if anyone can create a keystore properly if i have not done > > so, 
please do. i suspect this is the reason why. the keystore attached > > is 
service.jks> > > > thanks alot!> > > > > >> > 
> > The 
next generation of MSN Hotmail has arrived - Windows Live Hotmail > > 
> > 
> >> > 
___> > Wsf-php-user mailing list> > 
[EMAIL PROTECTED]> > http://wso2.org/cgi-bin/mailman/listinfo/wsf-php-user> > > 
> > -- > http://kaushalye.blogspot.com/> http://wso2.org/> 

The next generation of MSN Hotmail has arrived - Windows Live Hotmail 
_
100’s of Music vouchers to be won with MSN Music
https://www.musicmashup.co.uk

Re: AxisCallback stuck the application

[Huitang Li]

As mentioned in my previous post, it looks like a bug 
http://issues.apache.org/jira/browse/AXIS2-3265


There is nothing wrong with the wsdl. I am using resin 3.1.3 as the 
server. Probably this is something related to the xmlStreamReader 
implemented by resin? Right now I have no time to verify this. However, 
it will be awesome if I can know whether it is a true axis2 bug. If it 
is not, probably I will try to find time to debug resin. 

Since the old Callback works fine in the same resin server, I would 
assume that it is an Axi2 1.3 bug, though.


Thanks.

Huitang



Amila Suriarachchi wrote:



On 10/12/07, *Huitang Li* <[EMAIL PROTECTED] 
> wrote:



With further debugging, I found something interesting: when the
onMessage() method is done in AxisCallback, the application
proceeds on
the method  "public void run() " in class
OutInAxisOperationClient, and
then somehow the application seems hanging for ever.


I think the problem is here. The correct class to use is AxisCallback. 
Callback class is a  depricated class.

(see the  class comments).
If it work fine when we change to the depricated class that means 
generated code works fine.
on the other hand it is ok to leave onComple method without doing any 
thing. since it is a method to

use if some one need it.
(It is better to add this method to generated callback class and 
expose it to user)


Can you send your wsdl or a part to repoduce the problem?

Amila.

I have not downloaded the axis2 source code to debug, but  I believe
that something is not right after the AxisCallback finishes
onMessage()
and then returns the control to the run() method in
OutInAxisOperationClient.


Thanks.



Rajith Attapattu wrote:
> Put you notification logic in the
>
>  public void onComplete() {
> //nothing here
> }
>
> So when it completes (either fault/error or sucess) , this
method will
> be called.
>
> Here is a faily elementry example (not the most elegant)
> Modify the generated class as follows.
>
>  public void onComplete() {
> _complete = true;
> }
>
> and add a isComplete Method
>
> boolean isComplete()
> {
>   return _complete;
> }
>
> you can now use it like the old Callback class.
>
> while ( !_axisCallBack.isComplete())
> {
>Thread.sleep(1000);
> }
>
> Hope this helps.
>
> On 10/12/07, *Huitang Li* < [EMAIL PROTECTED]

> >> wrote:
>
> Thanks, Deepal. I will be happy to create a JRIA. But can
you show
> me a
> good example using this new API in the client code? I am
working on a
> project, and I cannot wait for the next Axis2 release.
>
> Thanks.
>
> Huitang
>
>
>
> Deepal jayasinghe wrote:
> > Hi Huitang ,
> > Definitely a bug in codegen , please create a JRIA.
> >
> > Thanks
> > Deepal
> >
> >> All these codes are auto-generated by Axis2 1.3 wsdl2java
> command. I
> >> do not know whether it is an old callback or not. But it
does says:
> >>
> >> _operationClient.setCallback(new
> >> org.apache.axis2.client.async.AxisCallback() {
> >> // all the codes that I pasted in my previous email.
> >> }
> >>
> >> In the generated code, the onComplete() method looks like
this:
> >>
> >> public void onComplete() {
> >>// Do nothing by default
> >>}
> >>
> >>
> >> Maybe there is something incorrectly generated by wsdl2java?
> >>
> >>
> >>
> >>
> >> Rajith Attapattu wrote:
> >>
> >>> What do you mean by the "application is stuck" ? How
does your
> >>> application figure out if a response is received?
> >>> Can you please cut paste the code that uses the
AxisCallback.
> >>>
> >>> Does the onMessage, onError or onFault methods get called?
> >>> If so why do u say it is stuck?
> >>>
> >>> Looks like the onMessage and onError methods get called,
bcos
> u seem
> >>> to have put the old callback there and you mentioned that it
> works.
> >>>
> >>>
> >>> public void onComplete() {
> >>> //nothing here
> >>> }
> >>>
> >>>
> >>> I also see that the onComplete method is empty.
> >>>
> >>> --
> >>> Rajith Attapattu
> >>> Red Hat
> >>> Blog http://mutlix.blogspot.com/
> >>>
> >>
>
--

RE: sending calendar object in axis stub

[Walker, Jeff]

Hi Senthil,
Don't pass language specific constructs like Calendar, in a web service
call.
 
You are better taking the less obvious route; just pass the minimal
amount number fo fields in the Calendar object that can be used by a
client to regenerate the equivalent object on their side. That is, build
a new complexType in XML Schema and use Doc/Lit-wrapped web services.
 
The main reason is simply, interoperability. Even of you know all of
your clients will be Java going forward, it's bad practice to pass
language specific objects in a web service. If indeed all of your
clients will always be Java, then you would benefit from RMI or EJB
where you would get a significant speed increase. Web Services is for
interoperability across disparate systems.
Regards,
-jeff
 
  _  

From: Senthivel U S [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 15, 2007 8:27 AM
To: axis-user@ws.apache.org
Subject: sending calendar object in axis stub



Hi,

 

I have a stub, in that I want to pass calendar object, while
passing I am getting the following error.  Is any serializer to be
included to pass calendar object.

 

java.io.IOException: Non nillable element 'issuedDate' is null.

at
org.apache.axis.encoding.ser.BeanSerializer.serialize(BeanSerializer.jav
a:215)

at
org.apache.axis.encoding.SerializationContext.serializeActual(Serializat
ionContext.java:1502)



My code is 

 

transfer.setIssueDate(Calendar.getInstance());

stub.insertTransfer(transfer);

 

TIA,

-senthil

 

Re: Axis2 1.3 Log4J WARNS

[JaviMetal]

The option of copying the file into the src file didn't work (despite it was
copied automatically into the classes' directory) but doing the Add external
folder solution has been enough fortunately, and the WARN messages don't
appear now.

Thank you very much Upul!!


Upul Godage wrote:
> 
> Or the best option, copy the log4j.properties file to the projects src
> directory.  Then it will be copied to the classes directory automatically
> and available in the classpath.
> 
> These are all solutions to client-side.
> 
> Upul
> 
> 
> On 10/15/07, Upul Godage <[EMAIL PROTECTED]> wrote:
>>
>> In run dialog, classpath tab, click advanced button.
>> Select Add external folder and add the folder where log4j.properties is
>> in
>> (folder should not contain unwanted classes)
>>
>> Or
>>
>> Make a jar out of log4j.properties file and add it as a jar.
>> jar cf log4jprops.jar log4j.properties
>>
>> Upul
>>
>>
>> On 10/15/07, JaviMetal < [EMAIL PROTECTED]> wrote:
>> >
>> >
>> > Hello everybody:
>> >
>> > First of all, I know that already exist some post about this problem,
>> > but I
>> > can't solve it.
>> >
>> > I have implement a client and when I run it I get the following
>> messages
>> > ...
>> >
>> > log4j:WARN No appenders could be found for logger
>> > (org.apache.axis2.description.AxisService).
>> > log4j:WARN Please initialize the log4j system properly.
>> >
>> > ... followed by my service response. I mean that the service works
>> > properly,
>> > but according with what I've read in other posts, I need to include a
>> > file
>> > called log4j.properties in the classpath. And my question is: how? I'm
>> > using
>> > Eclipse and it only lets me include .jar files to the classpath.
>> >
>> > Any help will be welcome. Thank you very much
>> > --
>> > View this message in context:
>> > http://www.nabble.com/Axis2-1.3-Log4J-WARNS-tf4626262.html#a13210291
>> > Sent from the Axis - User mailing list archive at Nabble.com.
>> >
>> >
>> > -
>> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> > For additional commands, e-mail: [EMAIL PROTECTED]
>> >
>> >
>>
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Axis2-1.3-Log4J-WARNS-tf4626262.html#a13212327
Sent from the Axis - User mailing list archive at Nabble.com.


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

Re: Axis 2 client part of web app

[Srikanth Muthyala]

Hey Keith, 

I fixed it. It was my services,xml - defining actionMapping as >/"/"< , I 
changed it to >""< and it worked. Thanks a lot for your help. 

Regards, 

Srikanth Muthyala 



- Original Message - 
From: "Srikanth Muthyala" <[EMAIL PROTECTED]> 
To: axis-user@ws.apache.org 
Cc: [EMAIL PROTECTED] 
Sent: Monday, 15 October 2007 09:54:36 PM (GMT+1000) Australia/Sydney 
Subject: Re: Axis 2 client part of web app 





Hi keith, 

I have tried stub._serviceClient.getOptions().setAction(""); but didnt help. 
Here is the wsdl. 

   

- < definitions name =" rtbCallEvent " targetNamespace =" urn:rtbCallEvent/wsdl 
" xmlns:tns =" urn:rtbCallEvent/wsdl " xmlns:xsd =" 
http://www.w3.org/2001/XMLSchema " xmlns:ns2 =" urn:rtbCallEvent/types " 
xmlns:soap =" http://schemas.xmlsoap.org/wsdl/soap/ " xmlns =" 
http://schemas.xmlsoap.org/wsdl/ " > 


- < types > 


- < schema targetNamespace =" urn:rtbCallEvent/types " xmlns =" 
http://www.w3.org/2001/XMLSchema " xmlns:soap11-enc =" 
http://schemas.xmlsoap.org/soap/encoding/ " xmlns:tnsT =" 
urn:rtbCallEvent/types " xmlns:wsdl =" http://schemas.xmlsoap.org/wsdl/ " 
xmlns:xsi =" http://www.w3.org/2001/XMLSchema-instance " > 


- < complexType name =" callEvent " > 


- < sequence > 


  < element name =" recordId " nillable =" false " type =" string " /> 

  < element name =" direction " nillable =" false " type =" string " /> 

  < element name =" callingNumber " nillable =" false " type =" string " /> 

  < element name =" calledNumber " nillable =" false " type =" string " /> 

  < element name =" answerTime " nillable =" false " type =" string " /> 

  < element name =" releaseTime " nillable =" false " type =" string " /> 

  < element name =" group " nillable =" false " type =" string " /> 
   
   

- < complexType name =" callEventResponse " > 


- < sequence > 


  < element name =" result " type =" boolean " /> 
   
   

  < element name =" callEvent " type =" tnsT:callEvent " /> 

  < element name =" callEventResponse " type =" tnsT:callEventResponse " /> 
   
   

- < message name =" rtbCallEventSEI_callEvent " > 


  < part name =" parameters " element =" ns2:callEvent " /> 
   

- < message name =" rtbCallEventSEI_callEventResponse " > 


  < part name =" result " element =" ns2:callEventResponse " /> 
   

- < portType name =" rtbCallEventSEI " > 


- < operation name =" callEvent " > 


  < input message =" tns:rtbCallEventSEI_callEvent " /> 

  < output message =" tns:rtbCallEventSEI_callEventResponse " /> 
   
   

- < binding name =" rtbCallEventSEIBinding " type =" tns:rtbCallEventSEI " > 


  < soap:binding style =" document " transport =" 
http://schemas.xmlsoap.org/soap/http " /> 

- < operation name =" callEvent " > 


  < soap:operation soapAction =" " /> 

- < input > 


  < soap:body use =" literal " /> 
   

- < output > 


  < soap:body use =" literal " /> 
   
   
   

- < service name =" RtbCallEvent " > 


- < port name =" rtbCallEventSEIPort " binding =" tns:rtbCallEventSEIBinding " 
> 


  < soap:address location =" 
http://10.0.0.66:/RTBCustomer/services/RtbCallEvent " /> 
   
   
   

Regards, 

Srikanth Muthyala 

Snr Consultant 
Innovative IT Consultants 

Mobile: +61 401 544 199 
Email:[EMAIL PROTECTED] 

www.iitc.com.au 

- Original Message - 
From: "keith chapman" <[EMAIL PROTECTED]> 
To: axis-user@ws.apache.org 
Sent: Monday, 15 October 2007 06:22:05 PM (GMT+1000) Australia/Sydney 
Subject: Re: Axis 2 client part of web app 

Hi Srikanth, 

When your using the webapp is looks like addressing is engaged. As a workaround 
just set this option on the client 

stub._serviceClient.getOptions().setAction(""); 

As a better solluion can you send me the interface operation section of your 
?wsdl2. Or the whole wsdl. Looks like there is a mismatch in the addreassing 
header in the client and the server. 

Thanks, 
Keith. 

Re: Axis2 1.3 Log4J WARNS

[Upul Godage]

Or the best option, copy the log4j.properties file to the projects src
directory.  Then it will be copied to the classes directory automatically
and available in the classpath.

These are all solutions to client-side.

Upul


On 10/15/07, Upul Godage <[EMAIL PROTECTED]> wrote:
>
> In run dialog, classpath tab, click advanced button.
> Select Add external folder and add the folder where log4j.properties is in
> (folder should not contain unwanted classes)
>
> Or
>
> Make a jar out of log4j.properties file and add it as a jar.
> jar cf log4jprops.jar log4j.properties
>
> Upul
>
>
> On 10/15/07, JaviMetal < [EMAIL PROTECTED]> wrote:
> >
> >
> > Hello everybody:
> >
> > First of all, I know that already exist some post about this problem,
> > but I
> > can't solve it.
> >
> > I have implement a client and when I run it I get the following messages
> > ...
> >
> > log4j:WARN No appenders could be found for logger
> > (org.apache.axis2.description.AxisService).
> > log4j:WARN Please initialize the log4j system properly.
> >
> > ... followed by my service response. I mean that the service works
> > properly,
> > but according with what I've read in other posts, I need to include a
> > file
> > called log4j.properties in the classpath. And my question is: how? I'm
> > using
> > Eclipse and it only lets me include .jar files to the classpath.
> >
> > Any help will be welcome. Thank you very much
> > --
> > View this message in context:
> > http://www.nabble.com/Axis2-1.3-Log4J-WARNS-tf4626262.html#a13210291
> > Sent from the Axis - User mailing list archive at Nabble.com.
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>

sending calendar object in axis stub

[Senthivel U S]

Hi,

 

I have a stub, in that I want to pass calendar object, while passing I am
getting the following error.  Is any serializer to be included to pass
calendar object.

 

java.io.IOException: Non nillable element 'issuedDate' is null.

at
org.apache.axis.encoding.ser.BeanSerializer.serialize(BeanSerializer.java:21
5)

at
org.apache.axis.encoding.SerializationContext.serializeActual(SerializationC
ontext.java:1502)

My code is 

 

transfer.setIssueDate(Calendar.getInstance());

stub.insertTransfer(transfer);

 

TIA,

-senthil

 

RE: NoClassDefFoundErrors ins AXIS2 aar

[Kahler, Jason J (US SSA)]

I found an article that explains using the ClassLoader loader =
getClass().getClassLoader();

Then load the class using that loader.

 

Problem is that I am using a large number of my own and Third Party jar
files. Do I need to 

Do that for every class? I just wanted to add my jars to my aar/lib dir
and be done with it.

 

 

 

  _  

From: Kahler, Jason J (US SSA) 
Sent: Monday, October 15, 2007 7:13 AM
To: axis-user@ws.apache.org
Subject: RE: NoClassDefFoundErrors ins AXIS2 aar

 

Can you elaborate, I am not sure how to do this. Also others have
indicated what I am doing Should work fine.

 

Thanks;

 

  _  

From: Chad DeBauch [mailto:[EMAIL PROTECTED] 
Sent: Saturday, October 13, 2007 5:03 PM
To: axis-user@ws.apache.org
Subject: Re: NoClassDefFoundErrors ins AXIS2 aar

 

The jars in your lib aar directory will be loaded in a separate
classloader.  So you must reference those classes using that
classloader.  You can do this by getting the MessageContext.

Chad

On 10/12/07, Kahler, Jason J (US SSA) <[EMAIL PROTECTED]>
wrote:

I am building my aar using the maven2 pluggin. Everything builds but
when I deploy I get NoClassDefFound 
ERRORS all over. This was working as a war in tomcat using axis 1. All
the required jars are in

 

myArr.arr/lib what could be wrong ?

 

Jay

 

Re: Axis 2 client part of web app

[Srikanth Muthyala]

Hi keith, 

I have tried stub._serviceClient.getOptions().setAction(""); but didnt help. 
Here is the wsdl. 

   

- < definitions name =" rtbCallEvent " targetNamespace =" urn:rtbCallEvent/wsdl 
" xmlns:tns =" urn:rtbCallEvent/wsdl " xmlns:xsd =" 
http://www.w3.org/2001/XMLSchema " xmlns:ns2 =" urn:rtbCallEvent/types " 
xmlns:soap =" http://schemas.xmlsoap.org/wsdl/soap/ " xmlns =" 
http://schemas.xmlsoap.org/wsdl/ " > 


- < types > 


- < schema targetNamespace =" urn:rtbCallEvent/types " xmlns =" 
http://www.w3.org/2001/XMLSchema " xmlns:soap11-enc =" 
http://schemas.xmlsoap.org/soap/encoding/ " xmlns:tnsT =" 
urn:rtbCallEvent/types " xmlns:wsdl =" http://schemas.xmlsoap.org/wsdl/ " 
xmlns:xsi =" http://www.w3.org/2001/XMLSchema-instance " > 


- < complexType name =" callEvent " > 


- < sequence > 


  < element name =" recordId " nillable =" false " type =" string " /> 

  < element name =" direction " nillable =" false " type =" string " /> 

  < element name =" callingNumber " nillable =" false " type =" string " /> 

  < element name =" calledNumber " nillable =" false " type =" string " /> 

  < element name =" answerTime " nillable =" false " type =" string " /> 

  < element name =" releaseTime " nillable =" false " type =" string " /> 

  < element name =" group " nillable =" false " type =" string " /> 
   
   

- < complexType name =" callEventResponse " > 


- < sequence > 


  < element name =" result " type =" boolean " /> 
   
   

  < element name =" callEvent " type =" tnsT:callEvent " /> 

  < element name =" callEventResponse " type =" tnsT:callEventResponse " /> 
   
   

- < message name =" rtbCallEventSEI_callEvent " > 


  < part name =" parameters " element =" ns2:callEvent " /> 
   

- < message name =" rtbCallEventSEI_callEventResponse " > 


  < part name =" result " element =" ns2:callEventResponse " /> 
   

- < portType name =" rtbCallEventSEI " > 


- < operation name =" callEvent " > 


  < input message =" tns:rtbCallEventSEI_callEvent " /> 

  < output message =" tns:rtbCallEventSEI_callEventResponse " /> 
   
   

- < binding name =" rtbCallEventSEIBinding " type =" tns:rtbCallEventSEI " > 


  < soap:binding style =" document " transport =" 
http://schemas.xmlsoap.org/soap/http " /> 

- < operation name =" callEvent " > 


  < soap:operation soapAction =" " /> 

- < input > 


  < soap:body use =" literal " /> 
   

- < output > 


  < soap:body use =" literal " /> 
   
   
   

- < service name =" RtbCallEvent " > 


- < port name =" rtbCallEventSEIPort " binding =" tns:rtbCallEventSEIBinding " 
> 


  < soap:address location =" 
http://10.0.0.66:/RTBCustomer/services/RtbCallEvent " /> 
   
   
   

Regards, 

Srikanth Muthyala 

Snr Consultant 
Innovative IT Consultants 

Mobile: +61 401 544 199 
Email:[EMAIL PROTECTED] 

www.iitc.com.au 

- Original Message - 
From: "keith chapman" <[EMAIL PROTECTED]> 
To: axis-user@ws.apache.org 
Sent: Monday, 15 October 2007 06:22:05 PM (GMT+1000) Australia/Sydney 
Subject: Re: Axis 2 client part of web app 

Hi Srikanth, 

When your using the webapp is looks like addressing is engaged. As a workaround 
just set this option on the client 

stub._serviceClient.getOptions().setAction(""); 

As a better solluion can you send me the interface operation section of your 
?wsdl2. Or the whole wsdl. Looks like there is a mismatch in the addreassing 
header in the client and the server. 

Thanks, 
Keith. 

RE: Soap Faults and Exception

[Kahler, Jason J (US SSA)]

I am using adb. I don't think it is a wsdl issue, because this wsdl
generated Service.Exception fine using Axis 1.

I also have only one method in my wsdl that throws that fault. It does
in fact generate the Fault classes. But they do not extend Throwable.

 

  _  

From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 15, 2007 1:06 AM
To: axis-user@ws.apache.org
Subject: Re: Soap Faults and Exception

 

what is the data bind you use?
Axis2 generates a seperate class for every element. and each fault
message. so if an element with the wsdl namespace with the name same as
the fault message then both classes would have the same package and
class names. 

to avoid this use -p option to specify a seperate package name for wsdl
namespace.



On 10/12/07, Kahler, Jason J (US SSA) < [EMAIL PROTECTED]
 > wrote:

I am using Axis2 1.3 

I have defined a custom Fault in my WSDL. It worked fine using axis 1.

But now when I run WSDL2code via the maven2 pluggin I get errors when I
try to compile my classes such as:

 

java:[63,17] incompatible types

found   : wfnp.ServiceException

required: java.lang.Throwable

 

the wfnp.ServiceException class doesn't even extend any kind of
throwable, so how can my classes actually

throw it ? I am very frustrated and confused.

 

Jay

 




-- 
Amila Suriarachchi,
WSO2 Inc. 

RE: NoClassDefFoundErrors ins AXIS2 aar

[Kahler, Jason J (US SSA)]

Can you elaborate, I am not sure how to do this. Also others have
indicated what I am doing Should work fine.

 

Thanks;

 

  _  

From: Chad DeBauch [mailto:[EMAIL PROTECTED] 
Sent: Saturday, October 13, 2007 5:03 PM
To: axis-user@ws.apache.org
Subject: Re: NoClassDefFoundErrors ins AXIS2 aar

 

The jars in your lib aar directory will be loaded in a separate
classloader.  So you must reference those classes using that
classloader.  You can do this by getting the MessageContext.

Chad

On 10/12/07, Kahler, Jason J (US SSA) <[EMAIL PROTECTED]>
wrote:

I am building my aar using the maven2 pluggin. Everything builds but
when I deploy I get NoClassDefFound 
ERRORS all over. This was working as a war in tomcat using axis 1. All
the required jars are in

 

myArr.arr/lib what could be wrong ?

 

Jay

 

RE: axis2 1.3 wsa:MessageID not in generated service skeleton response

[Erwin Reinhoud]

Hello David,

Thanks for the reply. I created an issue (3275). It is important that every 
message can be related to an ID. I would expect this would be important to 
others too and am surprised it is not an option yet.

Kind regards,
Erwin

-Oorspronkelijk bericht-
Van: David Illsley [mailto:[EMAIL PROTECTED]
Verzonden: maandag 15 oktober 2007 11:35
Aan: axis-user@ws.apache.org
Onderwerp: Re: axis2 1.3 wsa:MessageID not in generated service skeleton
response


Hi Erwin,
At the moment, we omit the wsa:MessageID on the response message as a
performance optimisation. It's not really possible for you to force
Axis2 to include it at the moment. Please raise a JIRA for a way to
toggle this optimisation off if its important to you.
Cheers,
David

On 15/10/2007, Erwin Reinhoud <[EMAIL PROTECTED]> wrote:
> Hello All,
>
> Following the advice below i created my own service having the arguments and 
> returning element being an OMElement. However, what i want is to have the 
> response to include the wsa:MessageId. How do i do this in the service? I 
> need to return the soap:body so i can define the wsa header. Any ideas?
>
> Thanks in advance.
>
> Kind regards,
> Erwin
>
>
>
> -Oorspronkelijk bericht-
> Van: Erwin Reinhoud
> Verzonden: dinsdag 9 oktober 2007 8:43
> Aan: axis-user@ws.apache.org
> Onderwerp: RE: axis2 1.3 wsa:MessageID not in generated service skeleton
> response
>
>
> Hello Deepal,
>
> We have to comply with a standard (governmental) that prescribes the use of a 
>  messageid in request/response. In case on application level the 
> communbication is with jms the messages can be linked. Until now i have used 
> the "contract first" principle to make a service, do i have to let that go 
> now? How about that message below, i guess it will not be implemented?
>
> Thanks in advance.
>
>
> Kind regards,
> Erwin
>
>
> -Oorspronkelijk bericht-
> Van: Deepal jayasinghe [mailto:[EMAIL PROTECTED]
> Verzonden: maandag 8 oktober 2007 17:23
> Aan: axis-user@ws.apache.org
> Onderwerp: Re: axis2 1.3 wsa:MessageID not in generated service skeleton
> response
>
>
> Erwin Reinhoud wrote:
> > Hello All,
> >
> > I generated a serviceskeleton with adb and enabled ws-addressing both
> > on service and client. In the response i don't see the MessageID. How
> > do you set your own messageID in the serviceskeleton code?
> In Axis2 1.3 you do not have a way to set the message ID when you use
> codegeneration (skel). In the meantime having a message id is not an
> mandatory , so may I know why do you want this message id ?
>
> Thanks
> Deepal
> >
> >
> > I found this message, but no related issue in jira:
> > http://mail-archives.apache.org/mod_mbox/ode-user/200707.mbox/[EMAIL 
> > PROTECTED]
> >
> > Anybody know if there is an issue and how to set a certain value for
> > the wsa:messageid from the serviceskeleton?
> >
> > Thanks in advance.
> >
> > Kind regards,
> >
> > Erwin
> >
> >
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
David Illsley - IBM Web Services Development

-
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: Axis2 1.3 Log4J WARNS

[Upul Godage]

In run dialog, classpath tab, click advanced button.
Select Add external folder and add the folder where log4j.properties is in
(folder should not contain unwanted classes)

Or

Make a jar out of log4j.properties file and add it as a jar.
jar cf log4jprops.jar log4j.properties

Upul


On 10/15/07, JaviMetal <[EMAIL PROTECTED]> wrote:
>
>
> Hello everybody:
>
> First of all, I know that already exist some post about this problem, but
> I
> can't solve it.
>
> I have implement a client and when I run it I get the following messages
> ...
>
> log4j:WARN No appenders could be found for logger
> (org.apache.axis2.description.AxisService).
> log4j:WARN Please initialize the log4j system properly.
>
> ... followed by my service response. I mean that the service works
> properly,
> but according with what I've read in other posts, I need to include a file
> called log4j.properties in the classpath. And my question is: how? I'm
> using
> Eclipse and it only lets me include .jar files to the classpath.
>
> Any help will be welcome. Thank you very much
> --
> View this message in context:
> http://www.nabble.com/Axis2-1.3-Log4J-WARNS-tf4626262.html#a13210291
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Axis2 1.3 Log4J WARNS

[JaviMetal]

Hello everybody:

First of all, I know that already exist some post about this problem, but I
can't solve it.

I have implement a client and when I run it I get the following messages ...

log4j:WARN No appenders could be found for logger
(org.apache.axis2.description.AxisService).
log4j:WARN Please initialize the log4j system properly.

... followed by my service response. I mean that the service works properly,
but according with what I've read in other posts, I need to include a file
called log4j.properties in the classpath. And my question is: how? I'm using
Eclipse and it only lets me include .jar files to the classpath.

Any help will be welcome. Thank you very much
-- 
View this message in context: 
http://www.nabble.com/Axis2-1.3-Log4J-WARNS-tf4626262.html#a13210291
Sent from the Axis - User mailing list archive at Nabble.com.


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

Re: [Axis2 1.3] log issue and generated code doesn't compile

[FFF7878]

Hello,
I've created JIRA 3274 : https://issues.apache.org/jira/browse/AXIS2-3274 on
the logging issue

Thanks for the reply

Pierre


Sanka Samaranayke wrote:
> 
> FFF7878 wrote:
>> Hello everybody,
>> I had two problems with Axis2 1.3:
>> 1) commons-logging and websphere 6.1
>> I ran into an issue with Axis2 1.3 when deploying it under websphere 6.1
>> (delegation mode set to PARENT_LAST of course) because websphere 6
>> runtime
>> embedded an older version of commons logging:
>> When deploying Axis2 based application, websphere tries to instantiates
>> AxisServlet and throws following exception:
>> Caused by: org.apache.commons.logging.LogConfigurationException:
>> java.lang.ClassNotFoundException:
>> org.apache.commons.logging.impl.Log4jFactory
>>  at org.apache.commons.logging.LogFactory$2.run(LogFactory.java:609)
>>  at
>> java.security.AccessController.doPrivileged(AccessController.java:193)
>>  at org.apache.commons.logging.LogFactory.newFactory(LogFactory.java:561)
>>  at org.apache.commons.logging.LogFactory.getFactory(LogFactory.java:352)
>>  at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:395)
>>  at
>> org.apache.axis2.transport.http.AxisServlet.(AxisServlet.java:79)
>>
>> The root cause is explained here :
>> http://wiki.apache.org/jakarta-commons/Logging/FrequentlyAskedQuestions?highlight=%28websphere%29
>>
>> In order to get everything works, I had to modify axis2-kernel.jar to add
>> a
>> commons-logging.properties containing:
>> priority=1
>> org.apache.commons.logging.LogFactory=org.apache.commons.logging.impl.LogFactoryImpl
>> org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger
>>
>> I tried to first put this file in my web app classpath but it didn't
>> work.
>> The only solution was to put it in Axis2 Kernel jar.
>>
>> Is there a cleaner solution?
>> If not, it would be a good idea to put the info on the axis2 website I
>> think.
>>   
> 
> AFAIK, this seems to be the only way we have at the moment. And it I
> believe we should have much cleaner approach for doing this. 
> Please raise a JIRA for this (and at least we should document about this
> in the website).
> 
> Thanks,
> Sanka
> 
>>
>>
>> 2) generated code doesn't compile
>>
>> Using JaxBri databinding framework, the WebServiceMessageReceiver class
>> had
>> the following generated code:
>>  boolean wrappedParam = (boolean) fromOM(msgContext.getEnvelope()
>>  
>> .getBody()
>>  
>> .getFirstElement(), boolean.class, 
>> getEnvelopeNamespaces(msgContext.getEnvelope()));
>>
>> This code doesn't compile (Impossible to convert Object into boolean). I
>> had
>> to change it to change Boolean class.
>> Here is the defined request element in the xsd:
>> 
>>
>> I saw a JIRA about the same issue but only for Axis2/C.
>>
>>
>> Thanks in advance
>>
>> Pierre
>>   
> 
> 
> -- 
> Sanka Samaranayake
> WSO2 Inc.
> 
> http://www.bloglines.com/blog/sanka
> http://www.wso2.org/
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/-Axis2-1.3--log-issue-and-generated-code-doesn%27t-compile-tf4617890.html#a13209646
Sent from the Axis - User mailing list archive at Nabble.com.


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

[ANN] Apache Savan/C 0.90 Released

[Damitha Kumarage]

Hi List,
Apache Savan/C Team is pleased to announce the release of Apache Savan/C
version 0.90
You can download this release from
http://ws.apache.org/savan/c/download.cgi
This release is supposed to be used with the Axis2C 1.1.0 distribution which
is released recently.

Key Features:

1 Support for WS-Eventing Specification August 2004.
2 Support for Subscribe, Unsubscribe, Renew and GetStatus operations.
3 Support for subscription management endpoint which could be the
Event Source itself or separate subscription management endpoint.
4 Persistent storage for subscribers.
5 Support for both SOAP 1.1 and 1.2.
6 Samples to test scenarios.
7 Documentation

We welcome your early feedback on this implementation.
Thanks for your interest in Savan/C

-- Apache Savan/C Team --

Re: [Axis2 1.3] log issue and generated code doesn't compile

[Sanka Samaranayke]

FFF7878 wrote:

Hello everybody,
I had two problems with Axis2 1.3:
1) commons-logging and websphere 6.1
I ran into an issue with Axis2 1.3 when deploying it under websphere 6.1
(delegation mode set to PARENT_LAST of course) because websphere 6 runtime
embedded an older version of commons logging:
When deploying Axis2 based application, websphere tries to instantiates
AxisServlet and throws following exception:
Caused by: org.apache.commons.logging.LogConfigurationException:
java.lang.ClassNotFoundException:
org.apache.commons.logging.impl.Log4jFactory
at org.apache.commons.logging.LogFactory$2.run(LogFactory.java:609)
at 
java.security.AccessController.doPrivileged(AccessController.java:193)
at org.apache.commons.logging.LogFactory.newFactory(LogFactory.java:561)
at org.apache.commons.logging.LogFactory.getFactory(LogFactory.java:352)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:395)
at
org.apache.axis2.transport.http.AxisServlet.(AxisServlet.java:79)

The root cause is explained here :
http://wiki.apache.org/jakarta-commons/Logging/FrequentlyAskedQuestions?highlight=%28websphere%29

In order to get everything works, I had to modify axis2-kernel.jar to add a
commons-logging.properties containing:
priority=1
org.apache.commons.logging.LogFactory=org.apache.commons.logging.impl.LogFactoryImpl
org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger

I tried to first put this file in my web app classpath but it didn't work.
The only solution was to put it in Axis2 Kernel jar.

Is there a cleaner solution?
If not, it would be a good idea to put the info on the axis2 website I
think.
  


AFAIK, this seems to be the only way we have at the moment. And it I believe we should have much cleaner approach for doing this. 
Please raise a JIRA for this (and at least we should document about this in the website).


Thanks,
Sanka




2) generated code doesn't compile

Using JaxBri databinding framework, the WebServiceMessageReceiver class had
the following generated code:
 boolean wrappedParam = (boolean) fromOM(msgContext.getEnvelope()
 
.getBody()
 
.getFirstElement(), boolean.class, 
getEnvelopeNamespaces(msgContext.getEnvelope()));


This code doesn't compile (Impossible to convert Object into boolean). I had
to change it to change Boolean class.
Here is the defined request element in the xsd:


I saw a JIRA about the same issue but only for Axis2/C.


Thanks in advance

Pierre
  



--
Sanka Samaranayake
WSO2 Inc.

http://www.bloglines.com/blog/sanka
http://www.wso2.org/


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

Re: axis2 1.3 wsa:MessageID not in generated service skeleton response

[David Illsley]

Hi Erwin,
At the moment, we omit the wsa:MessageID on the response message as a
performance optimisation. It's not really possible for you to force
Axis2 to include it at the moment. Please raise a JIRA for a way to
toggle this optimisation off if its important to you.
Cheers,
David

On 15/10/2007, Erwin Reinhoud <[EMAIL PROTECTED]> wrote:
> Hello All,
>
> Following the advice below i created my own service having the arguments and 
> returning element being an OMElement. However, what i want is to have the 
> response to include the wsa:MessageId. How do i do this in the service? I 
> need to return the soap:body so i can define the wsa header. Any ideas?
>
> Thanks in advance.
>
> Kind regards,
> Erwin
>
>
>
> -Oorspronkelijk bericht-
> Van: Erwin Reinhoud
> Verzonden: dinsdag 9 oktober 2007 8:43
> Aan: axis-user@ws.apache.org
> Onderwerp: RE: axis2 1.3 wsa:MessageID not in generated service skeleton
> response
>
>
> Hello Deepal,
>
> We have to comply with a standard (governmental) that prescribes the use of a 
>  messageid in request/response. In case on application level the 
> communbication is with jms the messages can be linked. Until now i have used 
> the "contract first" principle to make a service, do i have to let that go 
> now? How about that message below, i guess it will not be implemented?
>
> Thanks in advance.
>
>
> Kind regards,
> Erwin
>
>
> -Oorspronkelijk bericht-
> Van: Deepal jayasinghe [mailto:[EMAIL PROTECTED]
> Verzonden: maandag 8 oktober 2007 17:23
> Aan: axis-user@ws.apache.org
> Onderwerp: Re: axis2 1.3 wsa:MessageID not in generated service skeleton
> response
>
>
> Erwin Reinhoud wrote:
> > Hello All,
> >
> > I generated a serviceskeleton with adb and enabled ws-addressing both
> > on service and client. In the response i don't see the MessageID. How
> > do you set your own messageID in the serviceskeleton code?
> In Axis2 1.3 you do not have a way to set the message ID when you use
> codegeneration (skel). In the meantime having a message id is not an
> mandatory , so may I know why do you want this message id ?
>
> Thanks
> Deepal
> >
> >
> > I found this message, but no related issue in jira:
> > http://mail-archives.apache.org/mod_mbox/ode-user/200707.mbox/[EMAIL 
> > PROTECTED]
> >
> > Anybody know if there is an issue and how to set a certain value for
> > the wsa:messageid from the serviceskeleton?
> >
> > Thanks in advance.
> >
> > Kind regards,
> >
> > Erwin
> >
> >
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
David Illsley - IBM Web Services Development

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

RE: axis2 1.3 wsa:MessageID not in generated service skeleton response

[Erwin Reinhoud]

Hello All,

Following the advice below i created my own service having the arguments and 
returning element being an OMElement. However, what i want is to have the 
response to include the wsa:MessageId. How do i do this in the service? I need 
to return the soap:body so i can define the wsa header. Any ideas?

Thanks in advance.

Kind regards,
Erwin



-Oorspronkelijk bericht-
Van: Erwin Reinhoud 
Verzonden: dinsdag 9 oktober 2007 8:43
Aan: axis-user@ws.apache.org
Onderwerp: RE: axis2 1.3 wsa:MessageID not in generated service skeleton
response


Hello Deepal,

We have to comply with a standard (governmental) that prescribes the use of a  
messageid in request/response. In case on application level the communbication 
is with jms the messages can be linked. Until now i have used the "contract 
first" principle to make a service, do i have to let that go now? How about 
that message below, i guess it will not be implemented?

Thanks in advance.


Kind regards,
Erwin


-Oorspronkelijk bericht-
Van: Deepal jayasinghe [mailto:[EMAIL PROTECTED]
Verzonden: maandag 8 oktober 2007 17:23
Aan: axis-user@ws.apache.org
Onderwerp: Re: axis2 1.3 wsa:MessageID not in generated service skeleton
response


Erwin Reinhoud wrote:
> Hello All,
>  
> I generated a serviceskeleton with adb and enabled ws-addressing both
> on service and client. In the response i don't see the MessageID. How
> do you set your own messageID in the serviceskeleton code?
In Axis2 1.3 you do not have a way to set the message ID when you use
codegeneration (skel). In the meantime having a message id is not an
mandatory , so may I know why do you want this message id ?

Thanks
Deepal
>  
>  
> I found this message, but no related issue in jira:
> http://mail-archives.apache.org/mod_mbox/ode-user/200707.mbox/[EMAIL 
> PROTECTED]
>  
> Anybody know if there is an issue and how to set a certain value for
> the wsa:messageid from the serviceskeleton?
>  
> Thanks in advance.
>  
> Kind regards,
>  
> Erwin
>  
>  




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


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


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

Re: [Axis2] JAX-WS & working at xml level on the client side

[Michele Mazzucco]

Hi Martin,

I want to work at the XML level because I don't want to care about WSDLs
since the service is just a proxy service.

Michele


On Sat, 2000-10-14 at 11:27 -0400, Martin Gainty wrote:
> Michele-
> if your properties file contains an Action property set to DEFAULT
> (and the default for Action is DEFAULT)
> you can set the soapAction in your WSDL e.g.
>  
>   
>  transport="http://schemas.xmlsoap.org/soap/http"; />
>  
> 
>   
> 
> Did I miss anything Group?
>  
> Martin
> - Original Message - 
> From: Brian De Pradine 
> To: axis-user@ws.apache.org 
> Sent: Saturday, October 13, 2007 7:16 AM
> Subject: Re: [Axis2] JAX-WS & working at xml level on the
> client side
> 
> 
> 
> Hello Michele, 
> 
> It appears that the request cannot be dispatched based solely
> on the content of the SOAP body. Try setting the SOAPAction
> explicitly before you call dispatch.invoke() 
> 
> Map map =
> dispatch.getRequestContext(); 
> map.put(BindingProvider.SOAPACTION_USE_PROPERTY,
> Boolean.TRUE); 
> map.put(BindingProvider.SOAPACTION_URI_PROPERTY,
> "..."); 
> 
> Cheers
> 
> Brian DePradine
> Web Services Development
> IBM Hursley
> External  +44 (0) 1962 816319 Internal 246319
> 
> If you can't find the time to do it right the first time,
> where will you find the time to do it again?
> 
> 
> Michele Mazzucco <[EMAIL PROTECTED]> wrote on
> 12/10/2007 10:22:35:
> 
> > Nick.
> > 
> > thanks, but I can't get it working.
> > 
> > Here is the service (it's like SOAP12Provider, but without
> > dependencies):
> > 
> > package service.jaxws;
> > 
> > import javax.xml.ws.BindingType;
> > import javax.xml.ws.Provider;
> > import javax.xml.ws.WebServiceProvider;
> > import javax.xml.ws.soap.SOAPBinding;
> > 
> > /**
> >  * A Provider implementation used to test
> sending and 
> >  * receiving SOAP 1.2 messages.
> >  */
> > @WebServiceProvider()
> > @BindingType(SOAPBinding.SOAP12HTTP_BINDING)
> > public class SOAP12Provider implements Provider {
> > 
> > private static final String sampleResponse = 
> > " > \"http://org/apache/axis2/jaxws/test/SOAP12\";>" +
> > "SAMPLE REQUEST MESSAGE"
> +
> > "";
> > 
> > /* 
> >  * @see javax.xml.ws.Provider#invoke(java.lang.Object)
> >  */
> > public String invoke(String obj) {
> > System.out.printf("Received >>> %s\n", obj);
> > return sampleResponse;
> > }
> > 
> > }
> > 
> > 
> > which runs into an embedded axis2 instance:
> > 
> > import java.util.HashMap;
> > import java.util.Map;
> > 
> > 
> > import org.apache.axis2.AxisFault;
> > import org.apache.axis2.context.ConfigurationContext;
> > import org.apache.axis2.context.ConfigurationContextFactory;
> > import org.apache.axis2.description.AxisService;
> > import org.apache.axis2.transport.http.SimpleHTTPServer;
> > import org.apache.log4j.BasicConfigurator;
> > 
> > import service.jaxws.SOAP12Provider;
> > 
> > /**
> >  * http://wso2.org/library/83";>How do I Embed
> SimpleHTTPServer
> > in My
> >  * Application and Deploy a POJO?
> >  * 
> >  */
> > public class EmbeddedAxis2Server {
> > 
> > static {
> > BasicConfigurator.configure();
> > }
> > 
> > /**
> >  * @param args
> >  */
> > public static void main(String[] args) throws AxisFault
> {
> > ConfigurationContext context =
> ConfigurationContextFactory
> >
>   .createConfigurationContextFromFileSystem(null, null);
> > 
> > Map map = new HashMap String>(1);
> > map.put("http://www.w3.org/2004/08/wsdl/in-out";,
> > "org.apache.axis2.jaxws.server.JAXWSMessageReceiver");
> > 
> > AxisService echoJaxWs =
> > AxisService.createService(SOAP12Provider.class.getName(),
> > context.getAxisConfiguration(), map,
> > "http://org/apache/axis2/jaxws/test/SOAP12";,
> > "http://org/apache/axis2/jaxws/test/SOAP12";,
> > Thread.currentThread().getContextClassLoader());
> 

Re: [Axis2] JAX-WS & working at xml level on the client side

[Michele Mazzucco]

Hello Brian,

where do I set the SOAP action on the server side (pls. remember that
the service runs into an embedded jetty/SimpleHTTPServer instance)?


Thanks,
Michele



On Sat, 2007-10-13 at 12:16 +0100, Brian De Pradine wrote:
> 
> Hello Michele, 
> 
> It appears that the request cannot be dispatched based solely on the
> content of the SOAP body. Try setting the SOAPAction explicitly before
> you call dispatch.invoke() 
> 
> Map map = dispatch.getRequestContext(); 
> map.put(BindingProvider.SOAPACTION_USE_PROPERTY,
> Boolean.TRUE); 
> map.put(BindingProvider.SOAPACTION_URI_PROPERTY, "..."); 
> 
> Cheers
> 
> Brian DePradine
> Web Services Development
> IBM Hursley
> External  +44 (0) 1962 816319 Internal 246319
> 
> If you can't find the time to do it right the first time, where will
> you find the time to do it again?
> 
> 
> Michele Mazzucco <[EMAIL PROTECTED]> wrote on 12/10/2007
> 10:22:35:
> 
> > Nick.
> > 
> > thanks, but I can't get it working.
> > 
> > Here is the service (it's like SOAP12Provider, but without
> > dependencies):
> > 
> > package service.jaxws;
> > 
> > import javax.xml.ws.BindingType;
> > import javax.xml.ws.Provider;
> > import javax.xml.ws.WebServiceProvider;
> > import javax.xml.ws.soap.SOAPBinding;
> > 
> > /**
> >  * A Provider implementation used to test sending and 
> >  * receiving SOAP 1.2 messages.
> >  */
> > @WebServiceProvider()
> > @BindingType(SOAPBinding.SOAP12HTTP_BINDING)
> > public class SOAP12Provider implements Provider {
> > 
> > private static final String sampleResponse = 
> > " > \"http://org/apache/axis2/jaxws/test/SOAP12\";>" +
> > "SAMPLE REQUEST MESSAGE" +
> > "";
> > 
> > /* 
> >  * @see javax.xml.ws.Provider#invoke(java.lang.Object)
> >  */
> > public String invoke(String obj) {
> > System.out.printf("Received >>> %s\n", obj);
> > return sampleResponse;
> > }
> > 
> > }
> > 
> > 
> > which runs into an embedded axis2 instance:
> > 
> > import java.util.HashMap;
> > import java.util.Map;
> > 
> > 
> > import org.apache.axis2.AxisFault;
> > import org.apache.axis2.context.ConfigurationContext;
> > import org.apache.axis2.context.ConfigurationContextFactory;
> > import org.apache.axis2.description.AxisService;
> > import org.apache.axis2.transport.http.SimpleHTTPServer;
> > import org.apache.log4j.BasicConfigurator;
> > 
> > import service.jaxws.SOAP12Provider;
> > 
> > /**
> >  * http://wso2.org/library/83";>How do I Embed
> SimpleHTTPServer
> > in My
> >  * Application and Deploy a POJO?
> >  * 
> >  */
> > public class EmbeddedAxis2Server {
> > 
> > static {
> > BasicConfigurator.configure();
> > }
> > 
> > /**
> >  * @param args
> >  */
> > public static void main(String[] args) throws AxisFault {
> > ConfigurationContext context = ConfigurationContextFactory
> > .createConfigurationContextFromFileSystem(null,
> null);
> > 
> > Map map = new HashMap(1);
> > map.put("http://www.w3.org/2004/08/wsdl/in-out";,
> > "org.apache.axis2.jaxws.server.JAXWSMessageReceiver");
> > 
> > AxisService echoJaxWs =
> > AxisService.createService(SOAP12Provider.class.getName(),
> > context.getAxisConfiguration(), map,
> > "http://org/apache/axis2/jaxws/test/SOAP12";,
> > "http://org/apache/axis2/jaxws/test/SOAP12";,
> > Thread.currentThread().getContextClassLoader());
> > context.getAxisConfiguration().addService(echoJaxWs);
> > 
> > SimpleHTTPServer server = new SimpleHTTPServer(context,
> 8080);
> > server.start();
> > }
> > 
> > }
> > 
> > 
> > The client is SOAP12Dispatch + the main method
> > 
> > import java.io.ByteArrayInputStream;
> > import java.io.ByteArrayOutputStream;
> > 
> > import javax.xml.ws.Service.Mode;
> > import javax.xml.namespace.QName;
> > import javax.xml.transform.Source;
> > import javax.xml.transform.Transformer;
> > import javax.xml.transform.TransformerFactory;
> > import javax.xml.transform.stream.StreamResult;
> > import javax.xml.transform.stream.StreamSource;
> > import javax.xml.ws.Dispatch;
> > import javax.xml.ws.Service;
> > import javax.xml.ws.soap.SOAPBinding;
> > import javax.xml.ws.soap.SOAPFaultException;
> > 
> > import org.apache.log4j.BasicConfigurator;
> > 
> > public class SOAP12Dispatch {
> > 
> > private static final QName QNAME_SERVICE = new QName(
> > "http://org/apache/axis2/jaxws/test/SOAP12";,
> "SOAP12Service");
> > 
> > private static final QName QNAME_PORT = new QName(
> > "http://org/apache/axis2/jaxws/test/SOAP12";, "SOAP12Port");
> > 
> > private static final String URL_ENDPOINT =
> > "http://localhost:8080/axis2/services/SOAP12Provider";;
> > 
> > private static final String sampleRequest = " > xmlns:test=\"http://org/apache/axis2/jaxws/test/SOAP12\";>"
> > + "SAMPLE REQUEST MESSAGE" +
> > "";
> > 
> > pri

RE: WSDL2Java, Address already in use: connect

[Michele Mazzucco]

On Sat, 2007-10-13 at 11:00 +0200, Pär Malmqvist wrote:
> I guess the solution you gave me works for both cases, but in this
> case I would like to get a generated client that works fine with not
> much work.
> Not that I am that lazy but I think of the people that dont have that
> much knowledge about Axis2 and we want everybody to use Axis2 in a
> simple way! 

The simple way allows you to achieve simple goals (i.e. single
invocation). If you want something more complicated you'll need more
advanced settings.


Michele


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

Re: Axis 2 client part of web app

[keith chapman]

Hi Srikanth,

When your using the webapp is looks like addressing is engaged. As a
workaround just set this option on the client

stub._serviceClient.getOptions().setAction("");

As a better solluion can you send me the interface operation section of your
?wsdl2. Or the whole wsdl. Looks like there is a mismatch in the addreassing
header in the client and the server.

Thanks,
Keith.

On 10/15/07, Srikanth Muthyala <[EMAIL PROTECTED]> wrote:
>
> Hi Keith,
>
> Thanks for your tip to use TCP Monitor.
> I ran the client using both main method and web app. The difference I
> noticed in request was the header (see below) - other remains the same.
>
> *http://schemas.xmlsoap.org/soap/envelope/*
> *" 
> xmlns:wsa="**http://www.w3.org/2005/08/addressing";>*
> **
> *  http://localhost:8080/RTBCustomer/services/RtbCallEvent
> *
> *  urn:uuid:CEE8CBBEB2653D48CD1192428093191
> *
> *  ""*
> *
> *
>
> Again looking at the fault
> Faultcode = {http://www.w3.org/2005/08/addressing }ActionNotSupported
> Reason = The server did not recognise the action which it received:
>
> ...makes it obvious the header is the culprit. How do I fix this?? FYI, I
> included req/response messages below.
>
> Regards,
>
> Srikanth Muthyala
>
> *Main Method request*
> POST /RTBCustomer/services/RtbCallEvent HTTP/1.1
> Content-Type: text/xml; charset=UTF-8
> SOAPAction: ""
> User-Agent: Axis2
> Host: 127.0.0.1:8080
> Transfer-Encoding: chunked
>
> 1b1
> http://schemas.xmlsoap.org/soap/envelope/";>http://schemas.xmlsoap.org/soap/envelope/%22%3E%3Csoapenv:Body%3E%3Cns1:callEvent>xmlns:ns1="urn:rtbCallEvent/types">sdfsdsdfsdfdsparamparamsdfsuccessq
> 0
>
> *Main Method response*
> HTTP/1.1 200 OK
> Server: Apache-Coyote/1.1
> Content-Type: text/xml;charset=UTF-8
> Transfer-Encoding: chunked
> Date: Mon, 15 Oct 2007 06:00:54 GMT
>
> 109
> http://schemas.xmlsoap.org/soap/envelope/";>http://schemas.xmlsoap.org/soap/envelope/%22%3E%3Csoapenv:Body%3E%3Cns1:callEventResponse>xmlns:ns1="urn:rtbCallEvent/types">true
> 0
>
> *Web app request*
> POST /RTBCustomer/services/RtbCallEvent HTTP/1.1
> Content-Type: text/xml; charset=UTF-8
> SOAPAction: ""
> User-Agent: Axis2
> Host: 127.0.0.1:8080
> Transfer-Encoding: chunked
>
> 2ef
> http://schemas.xmlsoap.org/soap/envelope/"; xmlns:wsa="
> http://www.w3.org/2005/08/addressing";>http://localhost:8080/RTBCustomer/services/RtbCallEventurn:uuid:CEE8CBBEB2653D48CD1192428093191""
> 30779377474759249921344.5360+10
> Originating+61396261104962611002007092501200920070925012015group1
> 0
>
>
> *Web app response*
> HTTP/1.1 500 Internal Server Error
> Server: Apache-Coyote/1.1
> Content-Type: text/xml;charset=UTF-8
> Transfer-Encoding: chunked
> Date: Mon, 15 Oct 2007 06:17:45 GMT
> Connection: close
>
> 285
> http://schemas.xmlsoap.org/soap/envelope/"; xmlns:wsa="
> http://www.w3.org/2005/08/addressing";>http://www.w3.org/2005/08/addressing/faulturn:uuid:CEE8CBBEB2653D48CD1192428093191""wsa:ActionNotSupportedThe[action]
>  cannot be processed at the receiver. />
> 0
>
>
>
>
> **
> **
>
> - Original Message -
> From: "keith chapman" <[EMAIL PROTECTED]>
> To: axis-user@ws.apache.org
> Sent: Monday, 15 October 2007 02:14:19 PM (GMT+1000) Australia/Sydney
> Subject: Re: Axis 2 client part of web app
>
> Hi Srikanth,
>
> Can you use TCP-Monitor (U can use the eclipse plugin) and capture the
> request and responses in the two cases and post it here. That'll help
> diagnose the problem.
>
> Thanks,
> Keith.
>
> On 10/15/07, Srikanth Muthyala <[EMAIL PROTECTED]> wrote:
> >
> > I have a client code generated using Axiscode generator in eclipse. If I
> > make a call to the service when client is running as a *standalone* main
> > method it *works* fine but when the same code is called while running in
> > web app it gets fault
> > Faultcode = {http://www.w3.org/2005/08/addressing }ActionNotSupported
> > Reason = The server did not recognise the action which it received:
> >
> > -I tried running *cient* and server on two different hosts and same host
> > - no change.
> >
> > *This is my services.xml*
> >
> > 
> > 
> > 
> > 
> > 
> > 
> > http://www.w3.org/ns/wsdl/in-out";
> > class="
> > com.customer.service.rtbcallevent.RtbCallEventMessageReceiverInOut"/>
> > 
> > 
> > com.customer.service.rtbcallevent.RtbCallEventSkeleton
> > true
> > true
> > http://www.w3.org/ns/wsdl/in-out
> > ">
> > \"\"
> >
> > urn:rtbCallEvent/wsdl:rtbCallEventSEI:callEventResponse
> >
> > 
> > 
> > 
> >
> > *This is my java code*
> > RtbCallEventStub stub = new RtbCallEventStub("
> > http://10.96.201.30:8080/RTB/services/RtbCallEvent ");
> > CallEvent7 callEvent = new CallEvent7();
> > CallEvent param = new CallEvent();
> >
> > param.setAnswerTime("param");
> >