RE: Webservice with XML input parameter
Doy you really need soap, end thus axis ? Do you know you can invoke any kind of service over HTTP without axis or soap, and also without xml. If you need a lightweight protocol you can use xml-rpc... In my opinion, jsp, or php, or any other kind of web scripting pages must not handle application logic, and should always delegate it to a separate layer. Beyond a more suitable design, this brings a lot of benefits, such as unit testing facilities... The good thing with soap and axis is precisely that you don't have to handle xml translations and encodings, since these well specified operations can be automated by tools and libraries. If these protocols don't meet your needs, don't use them... But i'm afraid you're going to work a lot... --Ephemeris Lappis -Original Message-From: John Henry Xu [mailto:[EMAIL PROTECTED]Sent: Friday, June 10, 2005 8:28 PMTo: axis-user@ws.apache.orgSubject: Re: Webservice with XML input parameterHi Anne,To me, pass xml as a string input is very important. If I call a web service from a JSP, PHP, ASPX or other client applications, I don't want write functions inside these pages or client applications to parse the string to xml dom.I rather like web service handle it. Besides, to parse a xml string, I may not want use dom but sax. So I like web service taking xml string as an option, just for convenience of applications.Jack H. Xu Technology columnist and author http://www.usanalyst.com http://www.getusjobs.com- Original Message - From: "Anne Thomas Manes" <[EMAIL PROTECTED]>To: axis-user@ws.apache.org Subject: Re: Webservice with XML input parameter Date: Fri, 10 Jun 2005 07:31:25 -0400 > > Axis isn't really designed to work with XML strings particularly well. > It works with Java objects (RPC, Wrapped, and Document styles) and > with XML DOM (message style). I suggest you convert your strings to > DOM and use the messaging style. See the documentation. > > Anne > > On 6/9/05, Johan Kumps <[EMAIL PROTECTED]>wrote: > > Hi all, > > > > I would like to deploy a webservice using Axis 1.2 with a > > XML-string as input parameter and a XML-string as return value. > > > > Can you point me in the right direction? Code sample? > > > > Thanks in advance, > > > > Kind regards, > > > > Johan Kumps > > > > > > Jack H. Xu Technology columnist and author http://www.usanalyst.com http://www.getusjobs.com-- ___Sign-up for Ads Free at Mail.comhttp://www.mail.com/?sr=signup
Re: [Axis2] java.lang.UnsupportedOperationException: service element is not allowed in the server.xml
Hi Mike; As I can see you have done a mistake I mean to strat the DeploymentEngine you shoud pass argument as server.xml NOT service.xml. And inorder to create a AxisConfiguration pls use the following procedure. ConfigurationContextFactory cf = new ConfigurationContextFactory(); ConfigurationContext = cf.buildEngineContext(String RepositaryName); and RepositaryName is the location of the parent directory taht you are going to deploy your web services in your case it might me basePath. Thanks and regards; Deepal - Original Message - From: "Mike Haller" <[EMAIL PROTECTED]> To: Sent: Friday, June 10, 2005 6:13 PM Subject: [Axis2] java.lang.UnsupportedOperationException: service element is not allowed in the server.xml Why is element not allowed in (generated) service.xml ? the code snippet from ..ServerTest.java: DeploymentEngine deploymentEngine = new DeploymentEngine(basePath,"service.xml"); AxisConfiguration axisConfig = deploymentEngine.load(); my service.xml: name="ServiceClass">de.innovations.licenseserver.axis2.ILicenseServerSkeleton java.lang.UnsupportedOperationException: service element is not allowed in the server.xml at org.apache.axis.deployment.DeploymentParser.processGlobalConfig(DeploymentParser.java:200) at org.apache.axis.deployment.DeploymentEngine.load(DeploymentEngine.java:208) at de.innovations.licenseserver.axis2.server.ILicenseServerTest.setUp(ILicenseServerTest.java:40) at junit.framework.TestCase.runBare(TestCase.java:125) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:474) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:342) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:194)
RE: Blockers for Axis 1.2.1 Release(?)
Sorry for the repost, but getting a lot of bounce mail today ... The patch posted by Dave Tompkins and applied to axis 1.2 final works for me on both WebShere 5.1.1 and Tomcat 5.0.28 (not that there was ever a problem with tomcat). Thanks, Raul Flores -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Friday, June 10, 2005 3:23 PM To: axis-user@ws.apache.org Subject: Re: Blockers for Axis 1.2.1 Release(?) Raul, does the fix work for you too? -- dims On 6/10/05, Flores, Raul <[EMAIL PROTECTED]> wrote: > I would also like to see 1903 get fixed. > > > Raul Flores > > > -Original Message- > From: Vy Ho [mailto:[EMAIL PROTECTED] > Sent: Friday, June 10, 2005 10:09 AM > To: axis-user@ws.apache.org > Subject: Re: Blockers for Axis 1.2.1 Release(?) > > Is there any chance that this issue: > > http://issues.apache.org/jira/browse/AXIS-1903 > > get fixed? It seems to have problem with many platforms. > > Davanum Srinivas wrote: > > >Folks, > > > >I see 5 blockers...Does anyone else have others that needs fixed ASAP? > >I may or may not downgrade some of these depending on various factors > >(which i will of course add to the comments). > > > >http://issues.apache.org/jira/browse/AXIS-2046 > >http://issues.apache.org/jira/browse/AXIS-1986 > >http://issues.apache.org/jira/browse/AXIS-1985 > >http://issues.apache.org/jira/browse/AXIS-1976 > >http://issues.apache.org/jira/browse/AXIS-1366 > > > >thanks, > >dims > > > >On 6/1/05, Dan Armbrust <[EMAIL PROTECTED]> wrote: > > > > > >>If my opinion counts... this one is a critical blocker... > >> > >>http://issues.apache.org/jira/browse/AXIS-2021 > >> > >>Dan > >> > >>Davanum Srinivas wrote: > >> > >> > >> > > -- Davanum Srinivas -http://blogs.cocoondev.org/dims/
RE: Blockers for Axis 1.2.1 Release(?)
The patch posted by Dave Tompkins and applied to axis 1.2 final works for me on both WebShere 5.1.1 and Tomcat 5.0.28 (not that there was ever a problem with tomcat). Thanks, Raul Flores -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Friday, June 10, 2005 3:23 PM To: axis-user@ws.apache.org Subject: Re: Blockers for Axis 1.2.1 Release(?) Raul, does the fix work for you too? -- dims On 6/10/05, Flores, Raul <[EMAIL PROTECTED]> wrote: > I would also like to see 1903 get fixed. > > > Raul Flores > > > -Original Message- > From: Vy Ho [mailto:[EMAIL PROTECTED] > Sent: Friday, June 10, 2005 10:09 AM > To: axis-user@ws.apache.org > Subject: Re: Blockers for Axis 1.2.1 Release(?) > > Is there any chance that this issue: > > http://issues.apache.org/jira/browse/AXIS-1903 > > get fixed? It seems to have problem with many platforms. > > Davanum Srinivas wrote: > > >Folks, > > > >I see 5 blockers...Does anyone else have others that needs fixed ASAP? > >I may or may not downgrade some of these depending on various factors > >(which i will of course add to the comments). > > > >http://issues.apache.org/jira/browse/AXIS-2046 > >http://issues.apache.org/jira/browse/AXIS-1986 > >http://issues.apache.org/jira/browse/AXIS-1985 > >http://issues.apache.org/jira/browse/AXIS-1976 > >http://issues.apache.org/jira/browse/AXIS-1366 > > > >thanks, > >dims > > > >On 6/1/05, Dan Armbrust <[EMAIL PROTECTED]> wrote: > > > > > >>If my opinion counts... this one is a critical blocker... > >> > >>http://issues.apache.org/jira/browse/AXIS-2021 > >> > >>Dan > >> > >>Davanum Srinivas wrote: > >> > >> > >> > > -- Davanum Srinivas -http://blogs.cocoondev.org/dims/
Re: Blockers for Axis 1.2.1 Release AXIS-1391
Run a sample web service using latest nightly on stand-alone tomcat (4.1.31). If there's a problem. Let me know. If there is no problem, then run latest nightly (same sample web service) on the tomcat inside JBoss 3.2.7. thanks, dims On 6/10/05, Jay, Thomas <[EMAIL PROTECTED]> wrote: > > What about the memory leak issue > http://issues.apache.org/jira/browse/AXIS-1391 > > I am using JBoss 3.2.7 the Tomcat that is wrapped in this. > When I do Load and Performance testing is dies after a couple > of hours. > > Even with the sample web services, I get the same errors, it runs out of > memory. > > I have been putting my project onhold > until this is resolved. > > Any progress ? > > > > > > > > > > -- Davanum Srinivas -http://blogs.cocoondev.org/dims/
Blockers for Axis 1.2.1 Release AXIS-1391
What about the memory leak issue http://issues.apache.org/jira/browse/AXIS-1391 I am using JBoss 3.2.7 the Tomcat that is wrapped in this. When I do Load and Performance testing is dies after a couple of hours. Even with the sample web services, I get the same errors, it runs out of memory. I have been putting my project onhold until this is resolved. Any progress ?
Re: Blockers for Axis 1.2.1 Release(?)
upgraded to blocker. see my last comment in the bug report. -- dims On 6/10/05, Flores, Raul <[EMAIL PROTECTED]> wrote: > I would also like to see 1903 get fixed. > > > Raul Flores > > > -Original Message- > From: Vy Ho [mailto:[EMAIL PROTECTED] > Sent: Friday, June 10, 2005 10:09 AM > To: axis-user@ws.apache.org > Subject: Re: Blockers for Axis 1.2.1 Release(?) > > Is there any chance that this issue: > > http://issues.apache.org/jira/browse/AXIS-1903 > > get fixed? It seems to have problem with many platforms. > > Davanum Srinivas wrote: > > >Folks, > > > >I see 5 blockers...Does anyone else have others that needs fixed ASAP? > >I may or may not downgrade some of these depending on various factors > >(which i will of course add to the comments). > > > >http://issues.apache.org/jira/browse/AXIS-2046 > >http://issues.apache.org/jira/browse/AXIS-1986 > >http://issues.apache.org/jira/browse/AXIS-1985 > >http://issues.apache.org/jira/browse/AXIS-1976 > >http://issues.apache.org/jira/browse/AXIS-1366 > > > >thanks, > >dims > > > >On 6/1/05, Dan Armbrust <[EMAIL PROTECTED]> wrote: > > > > > >>If my opinion counts... this one is a critical blocker... > >> > >>http://issues.apache.org/jira/browse/AXIS-2021 > >> > >>Dan > >> > >>Davanum Srinivas wrote: > >> > >> > >> > > -- Davanum Srinivas -http://blogs.cocoondev.org/dims/
Re: Blockers for Axis 1.2.1 Release(?)
Raul, does the fix work for you too? -- dims On 6/10/05, Flores, Raul <[EMAIL PROTECTED]> wrote: > I would also like to see 1903 get fixed. > > > Raul Flores > > > -Original Message- > From: Vy Ho [mailto:[EMAIL PROTECTED] > Sent: Friday, June 10, 2005 10:09 AM > To: axis-user@ws.apache.org > Subject: Re: Blockers for Axis 1.2.1 Release(?) > > Is there any chance that this issue: > > http://issues.apache.org/jira/browse/AXIS-1903 > > get fixed? It seems to have problem with many platforms. > > Davanum Srinivas wrote: > > >Folks, > > > >I see 5 blockers...Does anyone else have others that needs fixed ASAP? > >I may or may not downgrade some of these depending on various factors > >(which i will of course add to the comments). > > > >http://issues.apache.org/jira/browse/AXIS-2046 > >http://issues.apache.org/jira/browse/AXIS-1986 > >http://issues.apache.org/jira/browse/AXIS-1985 > >http://issues.apache.org/jira/browse/AXIS-1976 > >http://issues.apache.org/jira/browse/AXIS-1366 > > > >thanks, > >dims > > > >On 6/1/05, Dan Armbrust <[EMAIL PROTECTED]> wrote: > > > > > >>If my opinion counts... this one is a critical blocker... > >> > >>http://issues.apache.org/jira/browse/AXIS-2021 > >> > >>Dan > >> > >>Davanum Srinivas wrote: > >> > >> > >> > > -- Davanum Srinivas -http://blogs.cocoondev.org/dims/
Re: deploying web service
hihi, the deploy/undeploy.wsdd are not needed in production. they are used to generate the server-config.wsdd the server-config.wsdd goes into your webapp/WEB-INF folder (same as your web.xml deployment descriptor file) if you have web services working on your local machine, deploying it on 'the network' requires no change to your web service. you should be able to just copy your entire web service app to your network server and have it work just the same. only the clients who access the web service needs to change, they need to know where the new location of your web service is (eg. the proxy/stub classes if you're using any). hth, woodchuck --- Plorks mail <[EMAIL PROTECTED]> wrote: > > > Hi all > > I've developeed a web service on my local PC. > > I now need to deploy this to our network so it can be used. > > Can someone point to an example of deploying a webservice to tomcat. > I've > read a few articles but they don't seem to be relevant/quite complex > to > understand > > I have my deploy/undeploy/server-cofig wsdd and my wsdl - i just > don't know > where to put them and what to change once they are on the network e.g > the > endpoint in the wsdl file > > Also, i don't understand how the web service will see the java files. > It > works on my PC i have a project with packages and java files in each > and my > web service can see them > > Sorry for my dumb questions > > Thanks for any help > > _ > It's fast, it's easy and it's free. Get MSN Messenger 7.0 today! > http://messenger.msn.co.uk > > __ Yahoo! Mail Mobile Take Yahoo! Mail with you! Check email on your mobile phone. http://mobile.yahoo.com/learn/mail
Re: Webservice with XML input parameter
Hi Anne,To me, pass xml as a string input is very important. If I call a web service from a JSP, PHP, ASPX or other client applications, I don't want write functions inside these pages or client applications to parse the string to xml dom.I rather like web service handle it. Besides, to parse a xml string, I may not want use dom but sax. So I like web service taking xml string as an option, just for convenience of applications.Jack H. Xu Technology columnist and author http://www.usanalyst.com http://www.getusjobs.com- Original Message - From: "Anne Thomas Manes" <[EMAIL PROTECTED]>To: axis-user@ws.apache.org Subject: Re: Webservice with XML input parameter Date: Fri, 10 Jun 2005 07:31:25 -0400 > > Axis isn't really designed to work with XML strings particularly well. > It works with Java objects (RPC, Wrapped, and Document styles) and > with XML DOM (message style). I suggest you convert your strings to > DOM and use the messaging style. See the documentation. > > Anne > > On 6/9/05, Johan Kumps <[EMAIL PROTECTED]>wrote: > > Hi all, > > > > I would like to deploy a webservice using Axis 1.2 with a > > XML-string as input parameter and a XML-string as return value. > > > > Can you point me in the right direction? Code sample? > > > > Thanks in advance, > > > > Kind regards, > > > > Johan Kumps > > > > > > Jack H. Xu Technology columnist and author http://www.usanalyst.com http://www.getusjobs.com -- ___Sign-up for Ads Free at Mail.com http://www.mail.com/?sr=signup
List and Map
Hello: There are API's that is already exposed that needs to be converted to webservices which use Lists and Maps as arguements and return types. Could someone throw some pointers/exampels n how to do this with Axis. Thanks, Ravi
attachments truncate on JDK 1.5 Axis1.2?
same application that ran OK on jdk 1.4 is truncating attachement files at 8K? a wild guess is that the portion of Axis that is chunking the stream on the Wire is sending 1 segment and dropping the connection. is this just my environment or is there a problem running Axis 1.2 on JDK 1.5? I presume that i made a mistake with the migration to Jdk1.5 and the recompile of my application. robert rowntree Borneo Consulting Inc 415 642 4162 415 335 5539 M
Re: making a call through a proxy
AxisProperties.setProperty("http.proxyUser", "user name");
AxisProperties.setProperty("http.proxyPassword", "password");
They are Java system properties that are specific
to the code that needs them, Janos. As far as I can tell, they are simply
hard-coded rather that formally enumerated in documentation.
Jeff
- Original Message -
From:
Janos Mucsi
To: axis-user@ws.apache.org
Sent: Friday, June 10, 2005 1:15 PM
Subject: Re: making a call through a
proxy
Thanks, Jeff, are these properties enumerated somewhere? I also need user
id and password.
Thanks.
Janos
Just call these static methods before you call
the web service:
AxisProperties.setProperty("http.proxyHost",
"123.123.123.123");
AxisProperties.setProperty("http.proxyPort", "1234");
Where 123.123.123.123 is the IP address of the
proxy server and 1234 is the port to connect to.
Jeff
RE: Blockers for Axis 1.2.1 Release(?)
I would also like to see 1903 get fixed. Raul Flores -Original Message- From: Vy Ho [mailto:[EMAIL PROTECTED] Sent: Friday, June 10, 2005 10:09 AM To: axis-user@ws.apache.org Subject: Re: Blockers for Axis 1.2.1 Release(?) Is there any chance that this issue: http://issues.apache.org/jira/browse/AXIS-1903 get fixed? It seems to have problem with many platforms. Davanum Srinivas wrote: >Folks, > >I see 5 blockers...Does anyone else have others that needs fixed ASAP? >I may or may not downgrade some of these depending on various factors >(which i will of course add to the comments). > >http://issues.apache.org/jira/browse/AXIS-2046 >http://issues.apache.org/jira/browse/AXIS-1986 >http://issues.apache.org/jira/browse/AXIS-1985 >http://issues.apache.org/jira/browse/AXIS-1976 >http://issues.apache.org/jira/browse/AXIS-1366 > >thanks, >dims > >On 6/1/05, Dan Armbrust <[EMAIL PROTECTED]> wrote: > > >>If my opinion counts... this one is a critical blocker... >> >>http://issues.apache.org/jira/browse/AXIS-2021 >> >>Dan >> >>Davanum Srinivas wrote: >> >> >>
Re: making a call through a proxy
Thanks, Jeff, are these properties enumerated somewhere? I also need user id and password.
Thanks.
Janos
Just call these static methods before you call the web service:
AxisProperties.setProperty("http.proxyHost", "123.123.123.123"); AxisProperties.setProperty("http.proxyPort", "1234");
Where 123.123.123.123 is the IP address of the proxy server and 1234 is the port to connect to.
Jeff
Re: making a call through a proxy
Just call these static methods before you call the
web service:
AxisProperties.setProperty("http.proxyHost",
"123.123.123.123");
AxisProperties.setProperty("http.proxyPort", "1234");
Where 123.123.123.123 is the IP address of the
proxy server and 1234 is the port to connect to.
Jeff
- Original Message -
From:
Janos Mucsi
To: axis-user@ws.apache.org ; [EMAIL PROTECTED]
Sent: Friday, June 10, 2005 12:45
PM
Subject: making a call through a
proxy
Hi
I am new to Axis, so here is my question: I need to submit a request to a
web service, but since I am in the corporate network, I need to go through a
proxy. How do I do it?
I am using the Axis-generated client (stub, etc).
Thanks.
Janos
making a call through a proxy
Hi I am new to Axis, so here is my question: I need to submit a request to a web service, but since I am in the corporate network, I need to go through a proxy. How do I do it? I am using the Axis-generated client (stub, etc). Thanks. Janos
re: error using axis-1_2, works with 1_2RC3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I am curious what may have changed that leads to some odd behavior. My application is working with RC3, but I realized today that I didn't upgrade to 1_2 final, so I tried it. My unit test is failing, and here is what is feels is the root cause of the error, look for the '#' symbol. It isn't telling me what is missing, obviously it is finding WSDDOperation. Thank you for any help. LMSClient.LMSMonitorTest.TestGetItemTypeList : System.InvalidOperationException : Client found response content type of 'text/html;charset=ISO-8859-1', but expected 'text/xml'. The request failed with the error message: - -- Exception reportmessage description The server encountered an internal error () that prevented it from fulfilling this request.exception javax.servlet.ServletException: Servlet.init() for servlet AxisServlet threw exception org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799) org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705) org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577) org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683) java.lang.Thread.run(Thread.java:595) ### root cause java.lang.NoClassDefFoundError org.apache.axis.deployment.wsdd.WSDDOperation.(WSDDOperation.java:46) org.apache.axis.deployment.wsdd.WSDDService. (WSDDService.java:157) org.apache.axis.deployment.wsdd.WSDDDeployment. (WSDDDeployment.java:191) org.apache.axis.deployment.wsdd.WSDDDocument.setDocument(WSDDDocument.java:139) org.apache.axis.deployment.wsdd.WSDDDocument. (WSDDDocument.java:65) org.apache.axis.configuration.FileProvider.configureEngine(FileProvider.java:179) org.apache.axis.AxisEngine.init(AxisEngine.java:172) org.apache.axis.AxisEngine. (AxisEngine.java:156) org.apache.axis.server.AxisServer. (AxisServer.java:88) org.apache.axis.server.DefaultAxisServerFactory.createServer(DefaultAxisServerFactory.java:109) org.apache.axis.server.DefaultAxisServerFactory.getServer(DefaultAxisServerFactory.java:73) org.apache.axis.server.AxisServer.getServer(AxisServer.java:73) org.apache.axis.transport.http.AxisServletBase.getEngine(AxisServletBase.java:185) org.apache.axis.transport.http.AxisServletBase.getOption(AxisServletBase.java:396) org.apache.axis.transport.http.AxisServletBase.init(AxisServletBase.java:112) org.apache.axis.transport.http.AxisServlet.init(AxisServlet.java:156) javax.servlet.GenericServlet.init(GenericServlet.java:211) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799) org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705) org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577) org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683) java.lang.Thread.run(Thread.java:595) - --. - -- "Love is mutual self-giving that ends in self-recovery." Fulton Sheen James Black[EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCqcDKikQgpVn8xrARAlSqAJ0XggM6fqUgnbJwYVYdNuOOPbUdgQCaAmfZ rKocwiCmZTxLa36lH7QdNhE= =KvZD -END PGP SIGNATURE-
Re: deploying web service
Hi Thanks for your reply Something like this java org.apache.axis.client.AdminClient deploy.wsdd I would have top copy my java files/jars etc to tomcat first? Thanks From: Tom Ziemer <[EMAIL PROTECTED]> Reply-To: axis-user@ws.apache.org To: axis-user@ws.apache.org Subject: Re: deploying web service Date: Fri, 10 Jun 2005 17:35:02 +0200 Hi, you can use the ant tasks supplied with axis to deploy/undeploy your service. Regards, Tom Plorks mail wrote: Hi all I've developeed a web service on my local PC. I now need to deploy this to our network so it can be used. Can someone point to an example of deploying a webservice to tomcat. I've read a few articles but they don't seem to be relevant/quite complex to understand I have my deploy/undeploy/server-cofig wsdd and my wsdl - i just don't know where to put them and what to change once they are on the network e.g the endpoint in the wsdl file Also, i don't understand how the web service will see the java files. It works on my PC i have a project with packages and java files in each and my web service can see them Sorry for my dumb questions Thanks for any help _ It's fast, it's easy and it's free. Get MSN Messenger 7.0 today! http://messenger.msn.co.uk _ It's fast, it's easy and it's free. Get MSN Messenger 7.0 today! http://messenger.msn.co.uk
[Axis2] java.lang.UnsupportedOperationException: service element is not allowed in the server.xml
Why is element not allowed in (generated) service.xml ? the code snippet from ..ServerTest.java: DeploymentEngine deploymentEngine = new DeploymentEngine(basePath,"service.xml"); AxisConfiguration axisConfig = deploymentEngine.load(); my service.xml: name="ServiceClass">de.innovations.licenseserver.axis2.ILicenseServerSkeleton java.lang.UnsupportedOperationException: service element is not allowed in the server.xml at org.apache.axis.deployment.DeploymentParser.processGlobalConfig(DeploymentParser.java:200) at org.apache.axis.deployment.DeploymentEngine.load(DeploymentEngine.java:208) at de.innovations.licenseserver.axis2.server.ILicenseServerTest.setUp(ILicenseServerTest.java:40) at junit.framework.TestCase.runBare(TestCase.java:125) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:474) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:342) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:194)
Re: deploying web service
Hi, you can use the ant tasks supplied with axis to deploy/undeploy your service. Regards, Tom Plorks mail wrote: Hi all I've developeed a web service on my local PC. I now need to deploy this to our network so it can be used. Can someone point to an example of deploying a webservice to tomcat. I've read a few articles but they don't seem to be relevant/quite complex to understand I have my deploy/undeploy/server-cofig wsdd and my wsdl - i just don't know where to put them and what to change once they are on the network e.g the endpoint in the wsdl file Also, i don't understand how the web service will see the java files. It works on my PC i have a project with packages and java files in each and my web service can see them Sorry for my dumb questions Thanks for any help _ It's fast, it's easy and it's free. Get MSN Messenger 7.0 today! http://messenger.msn.co.uk
strange nillable error
Hello!
When we are trying to submit to our web service, we get an
error saying
SEVERE: Admin:5 Exception --
(http-8080-Processor22) -- AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.io.IOException:
java.io.IOException: Non nillable element 'folderId' is null.
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:java.io.IOException:
java.io.IOException: Non nillable element 'folderId' is null.
at
org.apache.axis.encoding.ser.BeanSerializer.serialize(BeanSerializer.java:275)
at
org.apache.axis.encoding.SerializationContext.serializeActual(SerializationContext.java:1417)
at
org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:912)
at
org.apache.axis.message.RPCParam.serialize(RPCParam.java:197)
at
org.apache.axis.message.RPCElement.outputImpl(RPCElement.java:433)
at
org.apache.axis.message.MessageElement.output(MessageElement.java:1207)
at
org.apache.axis.message.SOAPBody.outputImpl(SOAPBody.java:139)
at
org.apache.axis.message.SOAPEnvelope.outputImpl(SOAPEnvelope.java:477)
at
org.apache.axis.message.MessageElement.output(MessageElement.java:1207)
at
org.apache.axis.SOAPPart.writeTo(SOAPPart.java:315)
at
org.apache.axis.SOAPPart.writeTo(SOAPPart.java:269)
at
org.apache.axis.SOAPPart.saveChanges(SOAPPart.java:530)
However, when we provide a default value for the folderId,
we then get an error complaining
SEVERE: Admin:8 Exception --
(http-8080-Processor25) --
AxisFault
faultCode: Client
faultSubcode:
faultString: Soap Client error.
faultActor:
faultNode:
faultDetail:
{http://schemas.xmlsoap.org/soap/envelope/}RequestName:GetFolderItems
{http://schemas.xmlsoap.org/soap/envelope/}ErrorCode:6033
{http://schemas.xmlsoap.org/soap/envelope/}Description:
Unexpected parameter
name.
FolderId
I’m at a loss here as to what is going
on. Any ideas? Can I add the nillable attribute to the elements and set
it to true so that I can get past this?
Thanks,
Carolyn
Re: Webservice with XML input parameter
Axis isn't really designed to work with XML strings particularly well. It works with Java objects (RPC, Wrapped, and Document styles) and with XML DOM (message style). I suggest you convert your strings to DOM and use the messaging style. See the documentation. Anne On 6/9/05, Johan Kumps <[EMAIL PROTECTED]> wrote: > Hi all, > > I would like to deploy a webservice using Axis 1.2 with a XML-string as input > parameter and a XML-string as return value. > > Can you point me in the right direction? Code sample? > > Thanks in advance, > > Kind regards, > > Johan Kumps > > >
Re: org.xml.sax.SAXException: Found character data inside an array element while des
I got around this problem by casting an ArrayList to a String [] and that
solved it
Thanks for answering my query though
From: thomas <[EMAIL PROTECTED]>
Reply-To: axis-user@ws.apache.org
To: axis-user@ws.apache.org
Subject: Re: org.xml.sax.SAXException: Found character data inside an array
element while des
Date: Fri, 10 Jun 2005 09:42:20 +0200
Have you a complete stack trace ?
On Jun 9, 2005, at 11:40 AM, Plorks mail wrote:
When I write a test client and call this method i get the error:
org.xml.sax.SAXException: Found character data inside an array element
while deserializing
My service method gets data from a db table and pus it into an array. I
call this method using this:
String [] ret = (String [])call.invoke(new Object[] {myString});
Can someone help me solve this problem
Many thanks
_
Be the first to hear what's new at MSN - sign up to our free newsletters!
http://www.msn.co.uk/newsletters
deploying web service
Hi all I've developeed a web service on my local PC. I now need to deploy this to our network so it can be used. Can someone point to an example of deploying a webservice to tomcat. I've read a few articles but they don't seem to be relevant/quite complex to understand I have my deploy/undeploy/server-cofig wsdd and my wsdl - i just don't know where to put them and what to change once they are on the network e.g the endpoint in the wsdl file Also, i don't understand how the web service will see the java files. It works on my PC i have a project with packages and java files in each and my web service can see them Sorry for my dumb questions Thanks for any help _ It's fast, it's easy and it's free. Get MSN Messenger 7.0 today! http://messenger.msn.co.uk
Re: org.xml.sax.SAXException: Found character data inside an array element while des
Have you a complete stack trace ?
On Jun 9, 2005, at 11:40 AM, Plorks mail wrote:
When I write a test client and call this method i get the error:
org.xml.sax.SAXException: Found character data inside an array element
while deserializing
My service method gets data from a db table and pus it into an array.
I call this method using this:
String [] ret = (String [])call.invoke(new Object[] {myString});
Can someone help me solve this problem
Many thanks
Re: "Invocation arguments were modified" exception in HandlerChainImpl class
Hi - With Axis 1.2 when I try to modify a child within the soap body using a client handler I am getting : "java.lang.RuntimeException: Invocation arguments were modified" exception at org.apache.axis.handlers.HandlerChainImpl.postInvoke(HandlerChainImpl.java:201) This was I believe working okay with axis 1.1. (Inserting and deleting child elements seems okay in 1.1. & 1.2) I think I am experiencing a similar problem as reported on 2005-03-22 by Timour Mouratov in msg : Re: "Invocation arguments were modified" exception in HandlerChainImpl class I did not see any resolution to his question ? I note that there was work done recently to HandlerChainImp.java file - is that to fix this problem ? See http://cvs.apache.org/viewcvs.cgi/ws-axis/java/src/org/apache/axis/handlers/HandlerChainImpl.java?r1=1.18&r2=1.19 Cheers, Kieran ___ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com
RE: Array serialize Axis 1.2 Final
The WSDLs are the same. -Original Message- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: 10 iunie 2005 14:50 To: axis-user Subject: Re: Array serialize Axis 1.2 Final Note that 1.2 Final included a bunch of fixes to array processing, so I'm not suprised that the processing changed between 1.2RC and 1.2 Final. Anne On 6/10/05, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > The 1.2 response matches your WSDL. Perhaps the WSDL changed between > 1.2RC and 1.2. Can you also send us the 1.2RC WSDL? > > On 6/9/05, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > > -- Forwarded message -- > > From: Popa Horia <[EMAIL PROTECTED]> > > Date: Jun 9, 2005 2:12 AM > > Subject: RE: Array serialize Axis 1.2 Final > > To: axis-user@ws.apache.org > > > > > > > > I have attached it... > > > > -Original Message- > > From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] > > Sent: 4 iunie 2005 14:37 > > To: Popa Horia > > Subject: Re: Array serialize Axis 1.2 Final > > > > I still need to see your WSDL. > > > > On 6/3/05, Popa Horia <[EMAIL PROTECTED]> wrote: > > > > > > I have started with a WSDD file where I have defined my services and > > > all the data types that my service is using. WSDL is generated by the > > server. > > > Here are two type mappings from my WSDD file: > > > > > > ARRAY: > > > > > >> > > > > > > xmlns:ns="http://beans.dataobjects.matrix.websitepros.com/SerialNumberHistor > > yBean" > > >qname="ns:ArrayOfSerialNumberHistoryBean" > > >type="java:default.SerialNumberHistoryBean[]" > > > > > > serializer="org.apache.axis.encoding.ser.ArraySerializerFactory" > > > > > > deserializer="org.apache.axis.encoding.ser.ArrayDeserializerFactory" > > > > > > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/> > > > > > > BEAN: > > > > > >> > > > > > > xmlns:ns="http://beans.dataobjects.matrix.websitepros.com/SerialNumberHistor > > yBean" > > >qname="ns:SerialNumberHistoryBean" > > >type="java:default.SerialNumberHistoryBean" > > > > > > serializer="org.apache.axis.encoding.ser.BeanSerializerFactory" > > > > > > deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory" > > > > > > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/> > > > > > > Below is the complete schema as requested: > > > > > > Axis 1.2 Final > > > > > > > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; > > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > > > > > > > > > > xmlns="http://webservices.installer.fusion7.fusion.websitepros.com/FusionAcc > > ountsManager"> > > > > > >false > > > > > > > > > 113.210.236.206 > > > > > > > > >45 > > > > > > > > > > > > > > > > > > > > > > > > > > > Axis 1.2 RC3 > > > > > > > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; > > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > > > > > > > > > > xmlns="http://webservices.installer.fusion7.fusion.websitepros.com/FusionAcc > > ountsManager"> > > > > > >false > > > > > > > > > 113.210.236.206 > > > > > > > > >45 > > > > > > > > > > > > > > > > > > > > > -Original Message- > > > From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] > > > Sent: 3 iunie 2005 22:30 > > > To: axis-user@ws.apache.org > > > Subject: Re: Array serialize Axis 1.2 Final > > > > > > Is there a default namespace specified higher up in the message? > > > And how does your WSDL describe the structure? (please include the > > > entire > > > schema) > > > > > > Anne > > > > > > On 6/3/05, Popa Horia <[EMAIL PROTECTED]> wrote: > > > > > > > > I moved from Axis 1.2 RC3 to Axis 1.2 final and I have noticed that > > > > my application doesn't work anymore. The application is a Axis 1.5 C++ > > stub. > > > > The reason is that the Array are serialized different in Axis 1.2 > > > > RC3 and Axis 1.2 Final. > > > > > > > > If you have some information about this please write back. > > > > > > > > Thanks > > > > > > > > Below are the samples: > > > > > > > > Axis 1.2 RC3 > > > > > > > > > > > > > > > > 193.230.236.206 > > > > 2005-05-27T07:50:08.000Z > > > > false > > > > 851830523 > > > > 41 > > > > 0 > > > > nPower installation > > > > 0 > > > > false > > > > > > > > > > > > > > > > Axis 1.2 Final > > > > > > > >
Re: Blockers for Axis 1.2.1 Release(?)
Is there any chance that this issue: http://issues.apache.org/jira/browse/AXIS-1903 get fixed? It seems to have problem with many platforms. Davanum Srinivas wrote: Folks, I see 5 blockers...Does anyone else have others that needs fixed ASAP? I may or may not downgrade some of these depending on various factors (which i will of course add to the comments). http://issues.apache.org/jira/browse/AXIS-2046 http://issues.apache.org/jira/browse/AXIS-1986 http://issues.apache.org/jira/browse/AXIS-1985 http://issues.apache.org/jira/browse/AXIS-1976 http://issues.apache.org/jira/browse/AXIS-1366 thanks, dims On 6/1/05, Dan Armbrust <[EMAIL PROTECTED]> wrote: If my opinion counts... this one is a critical blocker... http://issues.apache.org/jira/browse/AXIS-2021 Dan Davanum Srinivas wrote:
Re: How to specify a MessageFactory for SOAP?
Just to sate my curiosity, what do you mean by "the reference
implementation of SOAP"? As far as I'm aware, there is no such thing.
Anne
On 6/8/05, John Reinhold <[EMAIL PROTECTED]> wrote:
> OK,
>
> As murphey's law would have it, all it took was for me to post the
> question to a couple forums and the I clearly would find the answer.
>
> I have an extra space (trailing space) in my setProperty keyname.
> When I take out the trailing space and use:
>
> System.setProperty("javax.xml.soap.MessageFactory",
> "com.sun.xml.messaging.soap.MessageFactoryImpl" );
>
> it works fine.
>
> Sorry, and thank you.
>
> -John
>
>
>
> On Jun 8, 2005, at 4:35 PM, John Reinhold wrote:
>
> > I have an application which provides and consumes web services, and
> > uses Axis to do so. Lets call this "WebApp". It runs on a servlet
> > engine, say Tomcat or within Websphere...
> >
> > However, there is a link to another project which will call another
> > piece of code from another system which uses the reference
> > implementation of SOAP. Lets call this "MessageApp". It runs stand-
> > alone.
> >
> > If I am in "WebApp" and I call "MessageApp" my SOAP MessageFactory
> > is using Axis, and breaks the SOAP stuff in "MessageApp". I cannot
> > change "MessageApp" to use Axis (It is not under my control).
> >
> > How can I specify which MessageFactory I use?
> >
> > I have tried:
> > System.setProperty("javax.xml.soap.MessageFactory ",
> > "com.sun.xml.messaging.soap.MessageFactoryImpl" );
> >
> > and
> > System.setProperty("javax.xml.soap.MessageFactory
> > ","com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl" )
> > ;
> >
> > Neither one does any good.
> >
> > When "MessageApp" runs by itself, the MessageFactory used is:
> > com.sun.xml.messaging.soap.MessageFactoryImpl
> >
> > When I call "MessageApp" from within "WebApp" the message factory is:
> > org.apache.axis.soap.MessageFactoryImpl
> >
> > Thanks in advance...
> >
>
>
Re: Axis Fault
You're sending DOMs back and forth, right? Use "message" style rather
than RPC/encoded.
On 6/8/05, Frank <[EMAIL PROTECTED]> wrote:
> Anyone have a clue what my problem might be? I don't even know where to
> start
> Calling code:
>XSSRPCService xssSer = new XSSRPCServiceLocator();
>XSSRPC xss = xssSer.getXSSRPC();
>sanitizedDoc = xss.sanitize(inputDoc);
>
>
>
>
> java.lang.reflect.InvocationTargetException
> AxisFault
> faultCode:
> {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
> faultSubcode:
> faultString: java.lang.reflect.InvocationTargetException
> faultActor:
> faultNode:
> faultDetail:
> {http://xml.apache.org/axis/}hostname:kwdev
> java.lang.reflect.InvocationTargetException
> at
> org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221)
> at
> org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:128)
> at
> org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
> at
> org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1675)
> at
> org.apache.crimson.parser.Parser2.content(Parser2.java:1926)
> at
> org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1654)
> at
> org.apache.crimson.parser.Parser2.content(Parser2.java:1926)
> at
> org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1654)
> at
> org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:634)
> at
> org.apache.crimson.parser.Parser2.parse(Parser2.java:333)
> at
> org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448)
> at
> javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
> at
> org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
> at
> org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
> at
> org.apache.axis.Message.getSOAPEnvelope(Message.java:424)
> at
> org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
> at
> org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
> at
> org.apache.axis.client.Call.invokeEngine(Call.java:2765)
> at org.apache.axis.client.Call.invoke(Call.java:2748)
> at org.apache.axis.client.Call.invoke(Call.java:2424)
> at org.apache.axis.client.Call.invoke(Call.java:2347)
> at org.apache.axis.client.Call.invoke(Call.java:1804)
> at
> kwdev.axis.XSSRPC_jws.XSSRPCSoapBindingStub.sanitize(XSSRPCSoapBindingStub.java:103)
> at DBS.startDBS(DBS.java:75)
> at RunDBS.main(RunDBS.java:10)
>
>
> WSDL
> ---
>
>
>
> - targetNamespace="http://kwdev:8080/axis/XSSRPC.jws";
> xmlns:apachesoap="http://xml.apache.org/xml-soap";
> xmlns:impl="http://kwdev:8080/axis/XSSRPC.jws";
> xmlns:intf="http://kwdev:8080/axis/XSSRPC.jws";
> xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
> xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
>
> -
>
> -
>
>
>
>
>
> -
>
>
>
>
>
> -
>
>
> -
>
>
>
>
>
>
>
>
> -
>
>
>transport="http://schemas.xmlsoap.org/soap/http"; />
>
> -
>
>
>
>
> -
>
>
>encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
> namespace="http://DefaultNamespace"; use="encoded" />
>
>
> -
>
>
>encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
> namespace="http://kwdev:8080/axis/XSSRPC.jws"; use="encoded"
> />
>
>
>
>
> -
>
>
> -
>
>
>location="http://kwdev:8080/axis/XSSRPC.jws"; />
>
>
>
>
>
>
Re: Array serialize Axis 1.2 Final
The 1.2 response matches your WSDL. Perhaps the WSDL changed between 1.2RC and 1.2. Can you also send us the 1.2RC WSDL? On 6/9/05, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > -- Forwarded message -- > From: Popa Horia <[EMAIL PROTECTED]> > Date: Jun 9, 2005 2:12 AM > Subject: RE: Array serialize Axis 1.2 Final > To: axis-user@ws.apache.org > > > > I have attached it... > > -Original Message- > From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] > Sent: 4 iunie 2005 14:37 > To: Popa Horia > Subject: Re: Array serialize Axis 1.2 Final > > I still need to see your WSDL. > > On 6/3/05, Popa Horia <[EMAIL PROTECTED]> wrote: > > > > I have started with a WSDD file where I have defined my services and > > all the data types that my service is using. WSDL is generated by the > server. > > Here are two type mappings from my WSDD file: > > > > ARRAY: > > > >> > > > xmlns:ns="http://beans.dataobjects.matrix.websitepros.com/SerialNumberHistor > yBean" > >qname="ns:ArrayOfSerialNumberHistoryBean" > >type="java:default.SerialNumberHistoryBean[]" > > > > serializer="org.apache.axis.encoding.ser.ArraySerializerFactory" > > > > deserializer="org.apache.axis.encoding.ser.ArrayDeserializerFactory" > > > > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/> > > > > BEAN: > > > >> > > > xmlns:ns="http://beans.dataobjects.matrix.websitepros.com/SerialNumberHistor > yBean" > >qname="ns:SerialNumberHistoryBean" > >type="java:default.SerialNumberHistoryBean" > > > > serializer="org.apache.axis.encoding.ser.BeanSerializerFactory" > > > > deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory" > > > > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/> > > > > Below is the complete schema as requested: > > > > Axis 1.2 Final > > > > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > > > > > > xmlns="http://webservices.installer.fusion7.fusion.websitepros.com/FusionAcc > ountsManager"> > > > >false > > > > > > 113.210.236.206 > > > > > >45 > > > > > > > > > > > > > > > > > > Axis 1.2 RC3 > > > > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > > > > > > xmlns="http://webservices.installer.fusion7.fusion.websitepros.com/FusionAcc > ountsManager"> > > > >false > > > > > > 113.210.236.206 > > > > > >45 > > > > > > > > > > > > > > -Original Message- > > From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] > > Sent: 3 iunie 2005 22:30 > > To: axis-user@ws.apache.org > > Subject: Re: Array serialize Axis 1.2 Final > > > > Is there a default namespace specified higher up in the message? > > And how does your WSDL describe the structure? (please include the > > entire > > schema) > > > > Anne > > > > On 6/3/05, Popa Horia <[EMAIL PROTECTED]> wrote: > > > > > > I moved from Axis 1.2 RC3 to Axis 1.2 final and I have noticed that > > > my application doesn't work anymore. The application is a Axis 1.5 C++ > stub. > > > The reason is that the Array are serialized different in Axis 1.2 > > > RC3 and Axis 1.2 Final. > > > > > > If you have some information about this please write back. > > > > > > Thanks > > > > > > Below are the samples: > > > > > > Axis 1.2 RC3 > > > > > > > > > > > > 193.230.236.206 > > > 2005-05-27T07:50:08.000Z > > > false > > > 851830523 > > > 41 > > > 0 > > > nPower installation > > > 0 > > > false > > > > > > > > > > > > Axis 1.2 Final > > > > > > > > > 193.230.236.206 > > > 2005-05-27T07:50:08.000Z > > > false > > > 851830523 > > > 41 > > > 0 > > > nPower installation > > > 0 > > > false > > > > > > > > > > > > > > > > > > > > >
Re: [Axis2] NPE trying to use eclipse code-gen plugin
Chathura, you're the best :-) Like dims, who fixed the bug so fast hehe. You're so right about the deps. I've written down the list of all project dependencies and external jar files, so the next newbie can use it: OM == .xml module. OM: (Project org.apache.ws.axis2.xml) - Dependency to jsr173_api.jar (javax.namespace..) - Dependency to commons-logging.jar (Logging) WSDL: (Project org.apache.ws.axis2.wsdl) - Dependency to jsr173_api.jar - Dependency to wsdl4j-1.5.1.jar - Dependency to Project org.apache.ws.axis2.xml (OM) CORE: (Project org.apache.ws.axis2.core) - Dependency to jsr173_api.jar - Dependency to commons-logging.jar - Dependency to wsdl4j-1.5.1.jar - Dependency to mailapi_1_3_1.jar - Dependency to servlet.jar - Dependency to Project org.apache.ws.axis2.xml (OM) - Dependency to Project org.apache.ws.axis2.wsdl (WSDL) Addressing: (Project org.apache.ws.axis2.addressing) - Dep. to Project org.apache.ws.axis2.core - Dep. to Project org.apache.ws.axis2.xmlö - Dep. to jsr173_api.jar - Dep. to commons-logging.jar SAAJ: (Project org.apache.ws.axis2.saaj) - Dep. to jsr173_api.jar - Dep. to activation.jar - Dep. to Project org.apache.ws.axis2.addressing - Dep. to Project org.apache.ws.axis2.core - Dep. to Project org.apache.ws.axis2.xml Samples: (Project org.apache.ws.axis2.samples) - Dep. to Project org.apache.ws.axis2.core - Dep. to Project org.apache.ws.axis2.wsdl - Dep. to Project org.apache.ws.axis2.xml - Dep. to commons-logging.jar - Dep. to jsr173_api.jar Tool: (project org.apache.ws.axis2.tool.code-gen) - Dep. to ant-1.6.jar - Dep. to wsdl4j-1.5.1jar - Dep. to Project org.apache.ws.axis2.wsdl I'm currently on the CodegenWizard and will provide the preferences enhancements as patch. regards Mike Chathura Herath schrieb: Hi Mike. First of all thank you for the input I am creating a Eclipse projects for each module and there are no cyclic dependencies. It cannot be the case. I ll list the dependencies .. OM No dependencies WSDL --> OM CORE --> OM &WSDL Addressing --> CORE &OM SAAJ --> CORE & Addressing & OM Samples --> CORE & WSDL & OM TOOl --> WSDL That's it .. No cyclic references. Moving to Plug-in ... Saving the values in the store/preference definite +1 Regarding the check box issue... We might want to generate both server side and client side at the same time along with a test case. For the test case to work both the server side and the client side should be generated. (The test case that is generated will create a dummy implementation of the service and deploy it in a SimpleHttpServer and use the Stubs that was generated to invoke the operations.) That was the idea. If this leads to user confusion then of course we can put a radio button and if the test case option is selected we ll generate both server side and client side. Comments?? Thanks. Chathura -Original Message- From: Mike Haller [mailto:[EMAIL PROTECTED] Sent: Thursday, June 09, 2005 9:18 PM To: axis-dev@ws.apache.org Subject: Re: [Axis2] NPE trying to use eclipse code-gen plugin Hi Chathura, thanks for working on this so fast!!! That's incredible :-] [AXIS2-25] After trying to recompile Axis2 the last few hours (i tried to use the modules as separated projects in the eclipse workspace, and that wasn't a good idea -> cyclic dependencies and such). The patch worked fine! Comments on the plugin: - please replace the checkbox "Generate serverside code" with a radio button, since only one of client OR server is generated. Checking server checkbox automatically disables generating client stubs. Alternatively change the label to "Generate serverside code instead of clientside code" :) - please save the values in a store/preference, so you don't always have to type them in all over again. Again, thanks for the fast patch! regards Mike Chathura Herath schrieb: Hi Mike, Think this is a problem and I just opened a JIRA issue on this. Issue is fixed now. Please take an update and check. Can I check in your WSDL for a test case??? Thanks. Chathura -Original Message- From: Mike Haller [mailto:[EMAIL PROTECTED] Sent: Thursday, June 09, 2005 2:32 PM To: axis-dev@ws.apache.org Subject: Re: [Axis2] NPE trying to use eclipse code-gen plugin Hi, attached you will find my wsdl, the imported schema and the complete plugin errorlog. I hope this is not against the axis-dev policies (to attach files). regards Mike Chathura Herath schrieb: Can I have a look at the WSDL??? On 6/8/05, Mike Haller <[EMAIL PROTECTED]> wrote: Hey, i was able to compile axis2 src and create an eclipse plugin Btw, the /modules/tool/maven.xml doesn't create a ".project" file for the eclipse plugins - any reason? if it would create the .project files, too, you could import the folder directly as projects. Then, you don't need to manually create a Plug-In Project in Eclipse and copy all the files and set the build paths correctly etc. If you need more infos, please let me know (errorlogs,
returning and receiving XML DOM object
Hi all, I'm developing a server side web service that will get results from a db table. I want to reurn this data as XML DOM. Can anyone point me to an example where a server-side method returns a DOM object. Also to test this i will need to write a simple client. Can anyone point me to an example of a client calling a web service method and receives a DOM object Thanks for any help _ Want to block unwanted pop-ups? Download the free MSN Toolbar now! http://toolbar.msn.co.uk/
Re: Webservice with XML input parameter
On 6/9/05, Johan Kumps <[EMAIL PROTECTED]> wrote: > Hi all, > > I would like to deploy a webservice using Axis 1.2 with a XML-string as input > parameter and a XML-string as return value. > > Can you point me in the right direction? Code sample? > > Thanks in advance, > > Kind regards, > > Johan Kumps > > > I would do something like: 1) describe my service to take string input and return string response. 2) Use any tool which provides xml-java binding (like castor or JAXB) and generate request, response java classes from xsds. 3) Use the generated classes to marshal/unmarshal request/response java objects to xml. Deepesh
pls help, how to turn on Axis1.2 RC3's SOAP 1.2 feature
Hi, I am using Axis1.2 RC3 for both client and server sides. I found the SOAP message sent by the client is SOAP1.1 message. Is there any way to let the client send SOAP1.2 message ? Thanks,Feng
Re: Body not found
These two settings are incompatible:
style="message" provider="java:RPC"
You want to use provider="java:MESSAGE" when using message style.
Anne
On 6/9/05, Marc Rabil <[EMAIL PROTECTED]> wrote:
>
>
>
> Hi All,
>
>
>
> I am having trouble calling a service of style message and was wondering if
> someone can help.
>
>
>
> 1. Here's my service definition:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> 2. Here is the service class:
>
>
>
> public class TestService {
>
>
>
> public Element[] invoke(Element[] bodies) {
>
> System.out.println("invoke called...");
>
> return null;
>
> }
>
> }
>
>
>
> 3. Here is the SOAP I am sending (it is coming from the Axis client, but
> that should not matter right?):
>
>
>
> POST /services/servlet/AxisServlet HTTP/1.0
>
> Content-Type: text/xml; charset=utf-8
>
> Accept: application/soap+xml, application/dime, multipart/related, text/*
>
> User-Agent: Axis/1.1
>
> Host: 127.0.0.1
>
> Cache-Control: no-cache
>
> Pragma: no-cache
>
> SOAPAction: ""
>
> Content-Length: 508
>
>
>
>
>
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
>
>
>
>soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
> xmlns:ns1="TEST_SERVICE">
>
> xsi:type="xsd:string">FOHENNEAKMHA
>
>12345
>
>
>
>
>
>
>
>
>
> The server is returning a fault with the message: java.lang.Exception: Body
> not found. Clearly the inbound SOAP message has a body. It does not seem to
> be a problem with the message created as the return SOAP either since the
> invoke method never gets called.
>
>
>
> Any ideas as to what I am doing wrong?
>
>
>
> Thanks in advance for any help.
>
>
>
> Marc
>
>
>
>
Re: Array serialize Axis 1.2 Final
Note that 1.2 Final included a bunch of fixes to array processing, so I'm not suprised that the processing changed between 1.2RC and 1.2 Final. Anne On 6/10/05, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > The 1.2 response matches your WSDL. Perhaps the WSDL changed between > 1.2RC and 1.2. Can you also send us the 1.2RC WSDL? > > On 6/9/05, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > > -- Forwarded message -- > > From: Popa Horia <[EMAIL PROTECTED]> > > Date: Jun 9, 2005 2:12 AM > > Subject: RE: Array serialize Axis 1.2 Final > > To: axis-user@ws.apache.org > > > > > > > > I have attached it... > > > > -Original Message- > > From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] > > Sent: 4 iunie 2005 14:37 > > To: Popa Horia > > Subject: Re: Array serialize Axis 1.2 Final > > > > I still need to see your WSDL. > > > > On 6/3/05, Popa Horia <[EMAIL PROTECTED]> wrote: > > > > > > I have started with a WSDD file where I have defined my services and > > > all the data types that my service is using. WSDL is generated by the > > server. > > > Here are two type mappings from my WSDD file: > > > > > > ARRAY: > > > > > >> > > > > > > xmlns:ns="http://beans.dataobjects.matrix.websitepros.com/SerialNumberHistor > > yBean" > > >qname="ns:ArrayOfSerialNumberHistoryBean" > > >type="java:default.SerialNumberHistoryBean[]" > > > > > > serializer="org.apache.axis.encoding.ser.ArraySerializerFactory" > > > > > > deserializer="org.apache.axis.encoding.ser.ArrayDeserializerFactory" > > > > > > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/> > > > > > > BEAN: > > > > > >> > > > > > > xmlns:ns="http://beans.dataobjects.matrix.websitepros.com/SerialNumberHistor > > yBean" > > >qname="ns:SerialNumberHistoryBean" > > >type="java:default.SerialNumberHistoryBean" > > > > > > serializer="org.apache.axis.encoding.ser.BeanSerializerFactory" > > > > > > deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory" > > > > > > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/> > > > > > > Below is the complete schema as requested: > > > > > > Axis 1.2 Final > > > > > > > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; > > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > > > > > > > > > > xmlns="http://webservices.installer.fusion7.fusion.websitepros.com/FusionAcc > > ountsManager"> > > > > > >false > > > > > > > > > 113.210.236.206 > > > > > > > > >45 > > > > > > > > > > > > > > > > > > > > > > > > > > > Axis 1.2 RC3 > > > > > > > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; > > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > > > > > > > > > > xmlns="http://webservices.installer.fusion7.fusion.websitepros.com/FusionAcc > > ountsManager"> > > > > > >false > > > > > > > > > 113.210.236.206 > > > > > > > > >45 > > > > > > > > > > > > > > > > > > > > > -Original Message- > > > From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] > > > Sent: 3 iunie 2005 22:30 > > > To: axis-user@ws.apache.org > > > Subject: Re: Array serialize Axis 1.2 Final > > > > > > Is there a default namespace specified higher up in the message? > > > And how does your WSDL describe the structure? (please include the > > > entire > > > schema) > > > > > > Anne > > > > > > On 6/3/05, Popa Horia <[EMAIL PROTECTED]> wrote: > > > > > > > > I moved from Axis 1.2 RC3 to Axis 1.2 final and I have noticed that > > > > my application doesn't work anymore. The application is a Axis 1.5 C++ > > stub. > > > > The reason is that the Array are serialized different in Axis 1.2 > > > > RC3 and Axis 1.2 Final. > > > > > > > > If you have some information about this please write back. > > > > > > > > Thanks > > > > > > > > Below are the samples: > > > > > > > > Axis 1.2 RC3 > > > > > > > > > > > > > > > > 193.230.236.206 > > > > 2005-05-27T07:50:08.000Z > > > > false > > > > 851830523 > > > > 41 > > > > 0 > > > > nPower installation > > > > 0 > > > > false > > > > > > > > > > > > > > > > Axis 1.2 Final > > > > > > > > > > > > 193.230.236.206 > > > > 2005-05-27T07:50:08.000Z > > > > false > > > > 851830523 > >
Re: Blockers for Axis 1.2.1 Release(?)
Folks, I see 5 blockers...Does anyone else have others that needs fixed ASAP? I may or may not downgrade some of these depending on various factors (which i will of course add to the comments). http://issues.apache.org/jira/browse/AXIS-2046 http://issues.apache.org/jira/browse/AXIS-1986 http://issues.apache.org/jira/browse/AXIS-1985 http://issues.apache.org/jira/browse/AXIS-1976 http://issues.apache.org/jira/browse/AXIS-1366 thanks, dims On 6/1/05, Dan Armbrust <[EMAIL PROTECTED]> wrote: > If my opinion counts... this one is a critical blocker... > > http://issues.apache.org/jira/browse/AXIS-2021 > > Dan > > Davanum Srinivas wrote: > > >Hi all, > > > >Let's get the ball rolling again...Anyone see blockers for a minor > >release? Please make sure the problem exists in latest CVS, > >write/upload a test case and finally change the priority on the JIRA > >issue to blocker. > > > >Thanks, > >dims > > > > > -- Davanum Srinivas -http://blogs.cocoondev.org/dims/
Re: Bug 1.2RC3->1.2: Using CommonsHttpClient fails
unfortunately the patch it's not working for me.
what am I'm doing wrong?
I added this to my stub code:
protected void setUserHeader( MessageContext msgContext ) {
Hashtable userHeaderTable = new Hashtable();
userHeaderTable.put(HTTPConstants.HEADER_TRANSFER_ENCODING_CHUNKED,
"false");
msgContext.setProperty(HTTPConstants.REQUEST_HEADERS,
userHeaderTable );
}
org.apache.axis.client.Call _call = createCall();
_call.setOperation(_operations[0]);
_call.setUseSOAPAction(true);
_call.setSOAPActionURI("");
_call.setSOAPVersion(org.apache.axis.soap.SOAPConstants.SOAP11_CONSTANTS);
_call.setOperationName(new
javax.xml.namespace.QName("urn:Eusoda", "lastChange"));
setUserHeader( _call.getMessageContext() );
I'm still getting the old error message. I didn't update the code on the
server side, but I think this is not necessary, right?
I have used this nightly build:
axis-bin-1_2_1.zip 09-Jun-2005 21:07 11M
regards,
andreas
