axis 12.1 help
Dear wsdl memebers, > > I am having problem using axis.> > I am using.> > Axis 12.1 > > Tomcat 5.5.9 > > Java 1.5, But I followed installation guide of axis?> > > 1. when i run the samples i got org.apache.axis or> ClaassDefNotfound like this error. does anyone know> this kind of things? > > 2. IF anyone has experience using axis please tell> me how can i set CLASSPATH on windows XP for axis?> > 3. How can I run samples in axis?> > Thank you. Do what you can, for who you can, with what you have, and where you are South Korea.Seoul. Janarbek Matay Tel:82-10-3141-5857 mail:[EMAIL PROTECTED] [EMAIL PROTECTED] Start your day with Yahoo! - make it your home page
Re: management application
Hi Andy, http://sourceforge.net/projects/wsabi4axis http://demo.wsabi.org/index.do Stay tuned for a new release just around the corner. Al Quoting Andy Kriger <[EMAIL PROTECTED]>: > A while back I ran across an open-source, 3rd party web application > that can monitor and manage Axis web services. Of course, now that I > need it, I can't find it. Does anyone know of something that fits the > bill? > > thx > andy >
[Axis2] 0.91 (Re: [Axis2] 0.95 Release RoadMap_)
Eran, Could we please rename this to 0.91. gives us some breathing room (as per glen in the other email). thanks, dims On 8/5/05, Eran Chinthaka <[EMAIL PROTECTED]> wrote: > Sorry, re-sending with Axis2 prefix. > > > > Hi Axis2 Developers/Users, > > > > I'd like to propose to release Axis2 0.95 on next Friday (12-08-2005) and to > have a code freeze on next Tuesday (9-8-2005). > > > > Followings are MUST do things before the release: 116, 112, 103, 100, 95, > 82, 55, 51. > > Guys please give us a helping hand to fix these, before Tuesday. > > > > If you have any updates to Axis2 documentations, please do it, by the end of > Wednesday. > > > > Followings were fixed in this release, up to now. If you have any comments, > suggestions, please let us know. > > > > > > > > 1. [AXIS2-72] Network downloading of WSDL file. > > 2. [AXIS2-97] Turn off web services through Axis2 web admin module > > 3. [AXIS2-110] Inability to handle faults before creating message context > > 4. [AXIS2-57] User guide documentation: Help out people familiar with Axis > 1.X > > 5. [AXIS2-102] Code generated by WSDL2Code won't compile > > 6. [AXIS2-113] Client side exception handling > > 7. [AXIS2-111] Remove all unnecessary System.out > > 8. [AXIS2-114] Introducing the Data binding for the Asynchronous > programming model case > > 9. [AXIS2-106] Preserve Whitespaces > > 10. [AXIS2-115] Some critical test cases failed when shifted to Commons > transports which is > > 11. [AXIS2-91] Code Generator Throws a null pointer Exception > > 12. [AXIS2-87] Faults based on SOAP version? > > 13. [AXIS2-43] Chuncking support for the simple HTTP Server and Axis2 > default http transport > > 14. [AXIS2-33] Samples/docs need for SMTP transport > > 15. [AXIS2-108] SOAPEnvelope with XML declaration > > 16. [AXIS2-80] Support for UTF-16 (and ability to add others later) > > 17. [AXIS2-101] staxSOAPModelBuilder missing comments processing > > 18. [AXIS2-103] Remove code duplication > > 19. [AXIS2-55] Children order in SOAPElements > > 20. [AXIS2-51] blocking access to some OMElement methods within > SOAPElements > > 21. [AXIS2-118] OMDocument must have XML Version and Char encoding > > 22. [AXIS2-100] Separating sample and test cases form Sample module > > 23. [AXIS2-95] SOAP with Attachements sample > > > > Regards, > > Eran Chinthaka > > > > > > > -- Davanum Srinivas -http://blogs.cocoondev.org/dims/
Exception in thread "main" java.lang.NoClassDefFoundError: org.apache.commons???
Don, >From your copy and paste below, it appears that you put the AXISCLASSPATH >variable in quotation marks. Don't do that; you want the shell to fill in the >actual value--that's what the percent signs are for. Meghan Pietila Granite Consulting On a Win box, I followed the Axis 1.2 Installation Guide and tried the Run the admin client java -cp %AXISCLASSPATH% org.apache.axis.client.AdminClient -lhttp://localhost:8080/axis/services/AdminService deploy.wsdd I am pretty sure the path %AXISCLASSPATH% was set right, but I still got this errors: D:\axis121\AXIS-1~1\samples\stock>java -cp "%AXISCLASSPATH%" org.apache.axis. axis/services/AdminService deploy.wsdd Exception in thread "main" java.lang.NoClassDefFoundError: org.apache.commons at org.apache.axis.components.logger.LogFactory.class$(LogFactory.jav at org.apache.axis.components.logger.LogFactory$1.run(LogFactory.java at java.security.AccessController.doPrivileged(Native Method) at org.apache.axis.components.logger.LogFactory.getLogFactory(LogFact at org.apache.axis.components.logger.LogFactory.(LogFactory.j at org.apache.axis.client.AdminClient.(AdminClient.java:48) Is this related to the JCL classloader issue or something else? How can I go around it? This is my configure: Axis 1.2 Tomcat5.5.9, WinXPPro, JRE1.5. Thanks, Don
management application
A while back I ran across an open-source, 3rd party web application that can monitor and manage Axis web services. Of course, now that I need it, I can't find it. Does anyone know of something that fits the bill? thx andy
Re: Happyaxis reports problems loading libraries, found but with problems
On 8/5/05, Jonathan J. Vargas R. <[EMAIL PROTECTED]> wrote: > To play the last chance, I tried placing activation.jar in > /common/lib, and leaving xmlsec.jar first on shared/lib and > later in webapps dir, as expected, they also didn't work. It should work with both on /WEB-INF/lib > According to the code in happyaxis.jsp, when invoking its method > needClass(String className) it is throwing NoClassDefFoundError > exception. If it were unable to find the class, it will lauch a > ClassNotFoundException (method classExists(String className) in > happyaxis.jsp), right? It finds the class but it has a wrong class > definition or doesn't exist (according with doc found about java api). NoClassDefFoundError means "a class that was there on compile time isn't there at runtime". For example, if you have a class A that imports class B, and class B has a static initializer, and there's an exception in said initializer, class B won't be loaded at all (ExceptionInInitializerError). Then, if you try to use A you'll get a NoClassDefFoundError because B isn't there and should be. I tried with a clean axis install on tomcat 5.0.28. These are the jars on the WEB-INF/lib directory of the webapp: activation.jar .jar axis-ant.jar axis.jar commons-discovery-0.2.jar commons-logging-1.0.4.jar jaxrpc.jar log4j-1.2.9.jar saaj.jar wsdl4j-1.5.1.jar xmlsec-1.2.1.jar Happyaxis says it's ok except for attachments since I didn't provide mail.jar. Check your shared and common lib dirs for stale jars. 99% of the time it's better to not have anything on those dirs. The only jar I use outside the app's WEB-INF/lib dir is usually the jdbc driver so that I can use the tomcat built-in connection pools. Everything else goes in the webapp dir. A stale/mismatched version in common or shared lib dirs can break your app. -- Javier Gonzalez Nicolini
Re: Happyaxis reports problems loading libraries, found but with problems
Hi,
I tried with several combinations. I had xmlsec.jar and activation.jar
in the same folder, it was /shared/lib, and it caused the
problem I just told you.
Then, I though to move xmlsec.jar to the webapp lib directory and left
activation.jar into shared/lib, according with the classloader order I
understood from you. Then I restarted tomcat, refreshed happyaxis
page, and it told me the same problem.
So I decided to place both jars in the webapp directory, restarted and
reloaded page.. the same prob..
As last option, I left activation.jar in the webapp dir and xmlsec.jar
into /shared/lib, did the same restart process, and it was the
same problem.
To play the last chance, I tried placing activation.jar in
/common/lib, and leaving xmlsec.jar first on shared/lib and
later in webapps dir, as expected, they also didn't work.
According to the code in happyaxis.jsp, when invoking its method
needClass(String className) it is throwing NoClassDefFoundError
exception. If it were unable to find the class, it will lauch a
ClassNotFoundException (method classExists(String className) in
happyaxis.jsp), right? It finds the class but it has a wrong class
definition or doesn't exist (according with doc found about java api).
Is this a version incompatibility ?
What could I do then?
this is happyaxis dump:
---
Needed Components
Found SAAJ API (javax.xml.soap.SOAPMessage) at D:\Programas\Tomcat
5.5\webapps\axis\WEB-INF\lib\saaj.jar
Found JAX-RPC API (javax.xml.rpc.Service) at D:\Programas\Tomcat
5.5\webapps\axis\WEB-INF\lib\jaxrpc.jar
Found Apache-Axis (org.apache.axis.transport.http.AxisServlet) at
D:\Programas\Tomcat 5.5\webapps\axis\WEB-INF\lib\axis.jar
Found Jakarta-Commons Discovery
(org.apache.commons.discovery.Resource) at D:\Programas\Tomcat
5.5\webapps\axis\WEB-INF\lib\commons-discovery.jar
Found Jakarta-Commons Logging (org.apache.commons.logging.Log) at
D:\Programas\Tomcat%205.5\bin\commons-logging-api.jar
Found Log4j (org.apache.log4j.Layout) at D:\Programas\Tomcat
5.5\webapps\axis\WEB-INF\lib\log4j-1.2.8.jar
Found IBM's WSDL4Java (com.ibm.wsdl.factory.WSDLFactoryImpl) at
D:\Programas\Tomcat 5.5\webapps\axis\WEB-INF\lib\wsdl4j.jar
Found JAXP implementation (javax.xml.parsers.SAXParserFactory) at an
unknown location
Found Activation API (javax.activation.DataHandler) at
D:\Programas\Tomcat 5.5\shared\lib\activation.jar
Optional Components
Warning: could not find class javax.mail.internet.MimeMessage from file mail.jar
Attachments will not work
See http://java.sun.com/products/javamail/
Warning: could not find a dependency of class
org.apache.xml.security.Init from file xmlsec.jar
XML Security is not supported
See http://xml.apache.org/security/
The root cause was: org/apache/xpath/compiler/FuncLoader
This can happen e.g. if org.apache.xml.security.Init is in the
'common' classpath, but a dependency like activation.jar is only in
the webapp classpath.
Found Java Secure Socket Extension (javax.net.ssl.SSLSocketFactory) at
an unknown location
The core axis libraries are present. 2 optional axis libraries are missing
Examining Application Server
Servlet version 2.4
XML Parser com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl
XML ParserLocation an unknown location
xamining System Properties
java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
sun.boot.library.path=D:\Programas\JRE 1.5\bin
java.vm.version=1.5.0_02-b09
shared.loader=${catalina.base}/shared/classes,${catalina.base}/shared/lib/*.jar
java.vm.vendor=Sun Microsystems Inc.
java.vendor.url=http://java.sun.com/
path.separator=;
java.vm.name=Java HotSpot(TM) Client VM
tomcat.util.buf.StringCache.byte.enabled=true
file.encoding.pkg=sun.io
user.country=CR
sun.os.patch.level=Service Pack 2
java.vm.specification.name=Java Virtual Machine Specification
user.dir=C:\WINDOWS\system32
java.runtime.version=1.5.0_02-b09
java.awt.graphicsenv=sun.awt.Win32GraphicsEnvironment
java.endorsed.dirs=D:\Programas\Tomcat 5.5\common\endorsed
os.arch=x86
java.io.tmpdir=D:\Programas\Tomcat 5.5\temp
line.separator=
java.vm.specification.vendor=Sun Microsystems Inc.
user.variant=
java.util.logging.manager=org.apache.juli.ClassLoaderLogManager
java.naming.factory.url.pkgs=org.apache.naming
os.name=Windows XP
sun.jnu.encoding=Cp1252
java.library.path=D:\Programas\Tomcat
5.5\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Archivos de
programa\Windows Resource
Kits\Tools\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;D:\Programas\MySQL
Server 4.1\bin
java.specification.name=Java Platform API Specification
java.class.version=49.0
sun.management.compiler=HotSpot Client Compiler
os.version=5.1
user.home=C:\
user.timezone=GMT-06:00
catalina.useNaming=true
java.awt.printerjob=sun.awt.windows.WPrinterJob
java.specification.version=1.5
file.encoding=Cp1252
catalina.home=D:\Programas\Tomcat 5.5
user.name=SYSTEM
java.class.path=D:\Programas\Tomcat 5.5\bin\bootstrap.jar
java.naming.factory.initial=org.apache.naming.java.javaURLContextFactory
pac
Exception in thread "main" java.lang.NoClassDefFoundError: org.apache.commons???
On a Win box, I followed the Axis 1.2 “Installation Guide” and tried the “Run the admin client” java -cp %AXISCLASSPATH% org.apache.axis.client.AdminClient -lhttp://localhost:8080/axis/services/AdminService deploy.wsdd I am pretty sure the path %AXISCLASSPATH% was set right, but I still got this errors: D:\axis121\AXIS-1~1\samples\stock>java -cp "%AXISCLASSPATH%" org.apache.axis. axis/services/AdminService deploy.wsdd Exception in thread "main" java.lang.NoClassDefFoundError: org.apache.commons at org.apache.axis.components.logger.LogFactory.class$(LogFactory.jav at org.apache.axis.components.logger.LogFactory$1.run(LogFactory.java at java.security.AccessController.doPrivileged(Native Method) at org.apache.axis.components.logger.LogFactory.getLogFactory(LogFact at org.apache.axis.components.logger.LogFactory.(LogFactory.j at org.apache.axis.client.AdminClient.(AdminClient.java:48) Is this related to the JCL classloader issue or something else? How can I go around it? This is my configure: Axis 1.2 Tomcat5.5.9, WinXPPro, JRE1.5. Thanks, Don
RE: [Axis2] 0.95 Release RoadMap
On a Win box, I followed the Axis 1.2 “Installation Guide” and tried the “Run the admin client” java -cp %AXISCLASSPATH% org.apache.axis.client.AdminClient -lhttp://localhost:8080/axis/services/AdminService deploy.wsdd I am pretty sure the path %AXISCLASSPATH% was set right, but I still got this errors: D:\axis121\AXIS-1~1\samples\stock>java -cp "%AXISCLASSPATH%" org.apache.axis. axis/services/AdminService deploy.wsdd Exception in thread "main" java.lang.NoClassDefFoundError: org.apache.commons at org.apache.axis.components.logger.LogFactory.class$(LogFactory.jav at org.apache.axis.components.logger.LogFactory$1.run(LogFactory.java at java.security.AccessController.doPrivileged(Native Method) at org.apache.axis.components.logger.LogFactory.getLogFactory(LogFact at org.apache.axis.components.logger.LogFactory.(LogFactory.j at org.apache.axis.client.AdminClient.(AdminClient.java:48) Is this related to the JCL classloader issue or something else? How can I go around it? This is my configure: Axis 1.2 Tomcat5.5.9, WinXPPro, JRE1.5. Thanks, Don From: Eran Chinthaka [mailto:[EMAIL PROTECTED] Sent: Friday, August 05, 2005 12:52 AM To: axis-dev@ws.apache.org; axis-user@ws.apache.org Subject: [Axis2] 0.95 Release RoadMap Sorry, re-sending with Axis2 prefix……… Hi Axis2 Developers/Users, I'd like to propose to release Axis2 0.95 on next Friday (12-08-2005) and to have a code freeze on next Tuesday (9-8-2005). Followings are MUST do things before the release: 116, 112, 103, 100, 95, 82, 55, 51. Guys please give us a helping hand to fix these, before Tuesday. If you have any updates to Axis2 documentations, please do it, by the end of Wednesday. Followings were fixed in this release, up to now. If you have any comments, suggestions, please let us know. 1. [AXIS2-72] Network downloading of WSDL file. 2. [AXIS2-97] Turn off web services through Axis2 web admin module 3. [AXIS2-110] Inability to handle faults before creating message context 4. [AXIS2-57] User guide documentation: Help out people familiar with Axis 1.X 5. [AXIS2-102] Code generated by WSDL2Code won't compile 6. [AXIS2-113] Client side exception handling 7. [AXIS2-111] Remove all unnecessary System.out 8. [AXIS2-114] Introducing the Data binding for the Asynchronous programming model case 9. [AXIS2-106] Preserve Whitespaces 10. [AXIS2-115] Some critical test cases failed when shifted to Commons transports which is 11. [AXIS2-91] Code Generator Throws a null pointer Exception 12. [AXIS2-87] Faults based on SOAP version? 13. [AXIS2-43] Chuncking support for the simple HTTP Server and Axis2 default http transport 14. [AXIS2-33] Samples/docs need for SMTP transport 15. [AXIS2-108] SOAPEnvelope with XML declaration 16. [AXIS2-80] Support for UTF-16 (and ability to add others later) 17. [AXIS2-101] staxSOAPModelBuilder missing comments processing 18. [AXIS2-103] Remove code duplication 19. [AXIS2-55] Children order in SOAPElements 20. [AXIS2-51] blocking access to some OMElement methods within SOAPElements 21. [AXIS2-118] OMDocument must have XML Version and Char encoding 22. [AXIS2-100] Separating sample and test cases form Sample module 23. [AXIS2-95] SOAP with Attachements sample Regards, Eran Chinthaka
Re: WS-Addressing Support
Location has moved... http://cvs.apache.org/viewcvs.cgi/ws-addressing/ In your cvs checkout use "ws-addressing" instead of "ws-fx/addressing" -- dims On 8/5/05, Paul Grillo <[EMAIL PROTECTED]> wrote: > > > > Can somebody confirm for me the existence or no longer existence of Apache > Addressing project that was referenced in email here? > > > > http://ws.apache.org/addressing/ appears to exist, but I'm > not able to see any activity or access CVS > > > > http://cvs.apache.org/viewcvs.cgi/ws-fx/addressing/ gives a > 404, and I tried downloading source code and the cvs module no longer > exists. Has it been retired? Does anybody have a pointer or suggestions on > implementing some support for ws-addressing within Axis? > > > > Anything would help. > > > > thanks. > > > > -- Davanum Srinivas -http://blogs.cocoondev.org/dims/
WS-Addressing Support
Can somebody confirm for me the existence or no longer existence of Apache Addressing project that was referenced in email here? http://ws.apache.org/addressing/ appears to exist, but I’m not able to see any activity or access CVS http://cvs.apache.org/viewcvs.cgi/ws-fx/addressing/ gives a 404, and I tried downloading source code and the cvs module no longer exists. Has it been retired? Does anybody have a pointer or suggestions on implementing some support for ws-addressing within Axis? Anything would help. thanks.
RE: "Invalid element" error - Lower-case property name
All right, I've discovered that those classes I originally generated using WSDL2Java--with the missing meta-data--looked so odd because when I installed WebSphere Application Developer, it had WSDL2Java on the classpath. And it was earlier in the classpath than my Axis 1.2.1 jar. So I've been trying to get this stuff to work with code generated from something at least 2 years old... (no wonder there were IBM messages in the Javadoc! I thought the Axis team just hadn't cleaned the code up after IBM donated it...) So... for anyone else who has WSAD installed on their machine... now you know to be careful! If you're trying to generate code from WSDL with JMS endpoints, also be aware that you'll need to set the appropriate system property for the "jms" URL (i.e. -Djava.protocol.handler.pkgs="org.apache.axis.transport") I need to make some changes and then I can try running some different tests, hopefully this will clear up many of my errors. I noticed that quite a few of the Call properties are being set differently than in the "how to do JMS" pdf... Meghan Pietila Granite Consulting
[Q] Scope Changes
Title: [Q] Scope Changes I am new to Axis and web services and am maintaining an existing Axis application. I noticed that our application currently uses the default scope of Request. However, I would like to change the scope to Application. My questions is, does this require the Axis code for the client to the server to be regenerated or can I simply make the change to the config file? Thank you, Ken Hoying ** This message, including any attachments, contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, please contact sender immediately by reply e-mail and destroy all copies. You are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. TIAA-CREF **
SAXParser error while compiling ejb sample in axis 1.2.1
Hi , Since yesterday I am trying to compile the ejb sample given with axis 1.2.1 distribution. I tried with every type of parser jar but still I get the same error. I have tried with all possible versions of xml-xerces distribution. If someone tells me which exact version(or jar file) would work, I wil be very thankful. java.lang.NoSuchMethodError: javax.xml.parsers.SAXParserFactory.getSchema()Ljava x/xml/validation/Schema; at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.(Unknown Source) at com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl.newSAXPa rser(Unknown Source) at org.apache.tools.ant.util.JAXPUtils.newSAXParser(JAXPUtils.java:205) at org.apache.tools.ant.util.JAXPUtils.getNamespaceXMLReader(JAXPUtils.j ava:163) at org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java: 184) at org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java: 131) at org.apache.tools.ant.ProjectHelper.configureProject(ProjectHelper.jav a:91) at org.apache.tools.ant.Main.runBuild(Main.java:658) at org.apache.tools.ant.Main.startAnt(Main.java:188) at org.apache.tools.ant.Main.start(Main.java:151) at org.apache.tools.ant.Main.main(Main.java:241) javax.xml.parsers.SAXParserFactory.getSchema()Ljavax/xml/validation/Schema; Thanks Prashant
Re: Change the Port that Axis Service runs as
My last thought is that maybe there something in WebDAV that is getting in the
way.
-James
Quoting J H <[EMAIL PROTECTED]>:
> Thanks for trying this on your computer! I have basically the same
> configuration, JDK 5, Tomcat 5.5, and Axis 1.2.1.
>
> 1st Webapp
> --
> Slide
> (Handles External Webdav Requests via http://localhost:8080/mywebdav, makes
> axis/soap calls to the second webapp inside of the Tomcat container to get
> the data from the database.)
>
>
> 2nd Webapp
> --
> Self Contained Axis Webapp (I just made my own webapp and included the axis
> jars in the web-inf/lib directory)
> (Handles Requests from the 1st Webapp, via
> http://localhost:8080/myservice/services/MyService and retrieves data from a
> database via JDBC)
>
>
> >From: James Wilson <[EMAIL PROTECTED]>
> >Reply-To: axis-user@ws.apache.org
> >To: axis-user@ws.apache.org
> >Subject: Re: Change the Port that Axis Service runs as
> >Date: Fri, 05 Aug 2005 08:06:07 -0500
> >
> >I just setup a quick sample. Using Axis 1.2.1 and Tomcat 5.5 running in
> >JRE 5.0
> >I installed a second web app into tomcat. It worked.
> >
> >I installed the two web apps by putting XML config files under
> >CATALINA_HOME/conf/Catalina/localhost/ like below. Both pointed at two
> >different exploded-war directories
> >
> >
> >
> >
> >I then start Tomcat using the this command (allows remote debug from
> >eclipse):
> > %CATALINA_HOME%\bin\catalina.bat jpda start
> >
> >This is my standard development procedure. My client connected to the Axis
> >server via:
> >MyServiceLocator loc = new MyServiceLocator();
> >
> >loc.setMyPortEndpointAddress("http://127.0.0.1:8080/server/services/MyPort";);
> >MyPortType port = loc.getMyPort();
> >port.invokeMyFunction();
> >
> >
> >Hows is your procedure different? I don't know if it's important, but
> >during
> >this test I had all of the Axis jar dependencies in both war/WEB-INF/lib
> >directories (duplicated).
> >
> >Quoting J H <[EMAIL PROTECTED]>:
> >
> > > Here's is the complete stack trace...
> > >
> > > Again, the scenario is that when I install the 2 wars on seperate
> >machines,
> > > everything works fine. When I install the wars on the same machine,
> >nothing
> > > works and I get the message pasted below after about 5 minutes from the
> > > first client axis/soap call.
> > >
> > > My theory is that both webapplications are serving out to port 8080 and
> >when
> > > the axis client is trying to communicate with the axis server it
> >connects to
> > > port 8080, but it is talking to the wrong webapp. That is why
> >everything
> > > works fine when I move the webapps to different machines.
> > >
> > > Thanks again,
> > > Jeff
> > >
> > > Caught SOAPException :; nested exception is:
> > > java.net.SocketTimeoutException: Read timed out
> > > AxisFault
> > > faultCode:
> >{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
> > > faultSubcode:
> > > faultString: java.net.SocketTimeoutException: Read timed out
> > > faultActor:
> > > faultNode:
> > > faultDetail:
> > >
> > {http://xml.apache.org/axis/}stackTrace:java.net.SocketTimeoutException:
> > > Read timed out
> > > at java.net.SocketInputStream.socketRead0(Native Method)
> > > at java.net.SocketInputStream.read(SocketInputStream.java:129)
> > > at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
> > > at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
> > > at
> > >
>
>org.apache.axis.transport.http.HTTPSender.readHeadersFromSocket(HTTPSender.java:583)
> > > at
> >org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:143)
> > > at
> > >
>
>org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
> > > at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
> > > at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
> > > at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
> > > 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 com.project.slide.store.SoapMessage.sendMessage(SoapMessage.java:51)
> > > at
> > >
> >com.project.slide.store.SecurityStore.retrieveObject(SecurityStore.java:118)
> > > at
> > >
> >org.apache.slide.store.StandardStore.retrieveObject(StandardStore.java:171)
> > > at
> >org.apache.slide.structure.StructureImpl.create(StructureImpl.java:321)
> > > at
> > >
>
>org.apache.slide.common.XMLUnmarshaller.loadObjectNode(XMLUnmarshaller.java:194)
> > > at
> > >
>
>org.apache.slide.common.XMLUnmarshaller.loadObjectNode(XMLUnmarshaller.java:299)
> > > at
> > >
> >org.apache.slide.common.XMLUnmarshaller.unmarshal(XMLUnmarshaller.java:126)
> > > at
> > >
>
>org.apache.slide.com
RE: Custom HTTP Listener
Hi Again, Okay, never mind about the question of where to deploy classes/jars. I have confirmed that on my own. Somehow I missed it while reading the documentation. However, if anyone has any thoughts on sub-classing AxisServlet, they would be most welcome. Thanks again, Shelli -Original Message- From: Shelli D. Orton [mailto:[EMAIL PROTECTED] Sent: Friday, August 05, 2005 9:12 AM To: axis-user@ws.apache.org Subject: Custom HTTP Listener Hello, I'm very new to Axis/Tomcat and am working on my first web service and have a couple of questions. I'm developing on a Win2K box running Tomcat 4.1.31 and Axis 1.2.1. In everything that I've read on deployment of services, it gives good insruction on how to deploy using the AdminClient to update the server-config.wsdd but do not say explicitly where the services class/jar files should be deployed? Am I correct in thinking that it's Tomcat's webapps/axis/WEB-INF classes/lib directories? Also, I've been reading "Building Web Services with Java" and the chapter on Axis mentions that the built-in HTTP listener is the AxisServlet class. I would like to sub-class this with our own servlet that does some initialization. Is this possible? If so, how do I specify that Axis should use this class? Thanks in advance, Shelli
Problem in passing int value from a java client to a .NET Web Service
Hi,
The
problem is related to binding / registering input parameters to proper XSD
types. I am trying to access a .NET Web Service from a java client using AXIS.
I need to send int & Boolean values as input to the web
service.
Below is the code for adding parameter to the call
qName =
new QName("http://tempuri.org/GPIDWebService/Service1",
"Birthday");
call.addParameter(qName, XMLType.XSD_INT,
ParameterMode.IN);
qName =
new QName("http://tempuri.org/GPIDWebService/Service1",
"ForceCreate");
call.addParameter(qName,
XMLType.XSD_BOOLEAN, ParameterMode.IN);
In the invoke call I am passing primitive “int” &
“boolean” values.
When I execute the program I am getting below error message
Server
was unable to read request. --> There is an error in XML document (1, 796).
--> Input string was not in a correct format.
In
GPIDDataMigrationManager-GPIDCreate Exception.. java.lang.NullPointerException
When I modified same .NET Web service to take all the input
parameters as string & pass all strings from the java client, program is
executing properly & returning the expected object.
Can any one help me in understanding what is it that I am
doing wrong / missed some code / should take care of.
Any help in this regard is highly appreciated!!!
Thanks for the help in advance!
Regards,
Sekhar
Confidentiality Notice
The information contained in this electronic message and any attachments to this message are intended
for the exclusive use of the addressee(s) and may contain confidential or privileged information. If
you are not the intended recipient, please notify the sender at Wipro or [EMAIL PROTECTED] immediately
and destroy all copies of this message and any attachments.
Re: Happyaxis reports problems loading libraries, found but with problems
The first problem could be avoided by leaving xmlsec in the webapp lib dir.
As for the second one... I do not know :(
On 8/5/05, Thad Humphries <[EMAIL PROTECTED]> wrote:
> I have almost the problem as Jonathan. I'm running Tomcat 5.5.9 with Java 1.5
> on Linux. My message reads:
>
> See http://xml.apache.org/security/ {4}
> The root cause was: org/apache/commons/logging/LogFactory
>
> This happens whether I put xmlsec-1.2.1.jar in $CATALINA_HOME/common/lib or
> $CATALINA_HOME/common/endorsed. When I put xmlsec-1.2.1.jar in
> $CATALINA_HOME/webapps/axis/WEB-INF/lib, the message was
>
> See http://xml.apache.org/security/ {4}
> The root cause was: {0}
>
> What does this mean? Should I be using an older version of xmlsec-1.2.1.jar?
>
> On Friday 05 August 2005 09:58, Javier Gonzalez wrote:
> > Where are xmlsec.jar and activation.jar located? (the hint that the
> > error message told you)
> >
> > IIRC, in Tomcat the classloaders are ordered like this: webapp ->
> > shared -> common -> system. The classloaders can look in that order
> > and not in the reverse order. That is, if A.jar is on the webapp lib
> > dir, B.jar is in shared/lib, and A depends on B, it's ok, since the
> > webapp classloader can ask the next classloader for B. But if B
> > depends on A, then you'll have an error because the shared classloader
> > can't look "back" into the webapp classloader.
> >
> > On 8/5/05, Jonathan J. Vargas R. <[EMAIL PROTECTED]> wrote:
> > > Greets,
> > >
> > > I tried to install xmlsec into axis, but seems axis has problems doing
> > > this. The problem is with xmlsec, but I still don't know how to solve
> > > it or fix it. I am using tomcat, This is the happyaxis report:
> > >
> > >
> > > Optional Components
> > >
> > >
> > > Warning: could not find a dependency of class
> > > org.apache.xml.security.Init from file xmlsec.jar
> > > XML Security is not supported
> > > See http://xml.apache.org/security/
> > > The root cause was: org/apache/xpath/compiler/FuncLoader
> > > This can happen e.g. if org.apache.xml.security.Init is in the
> > > 'common' classpath, but a dependency like activation.jar is only in
> > > the webapp classpath.
> > >
> > > Found Java Secure Socket Extension (javax.net.ssl.SSLSocketFactory) at
> > > an unknown location
>
--
Javier Gonzalez Nicolini
Re: Change the Port that Axis Service runs as
Thanks for trying this on your computer! I have basically the same
configuration, JDK 5, Tomcat 5.5, and Axis 1.2.1.
1st Webapp
--
Slide
(Handles External Webdav Requests via http://localhost:8080/mywebdav, makes
axis/soap calls to the second webapp inside of the Tomcat container to get
the data from the database.)
2nd Webapp
--
Self Contained Axis Webapp (I just made my own webapp and included the axis
jars in the web-inf/lib directory)
(Handles Requests from the 1st Webapp, via
http://localhost:8080/myservice/services/MyService and retrieves data from a
database via JDBC)
From: James Wilson <[EMAIL PROTECTED]>
Reply-To: axis-user@ws.apache.org
To: axis-user@ws.apache.org
Subject: Re: Change the Port that Axis Service runs as
Date: Fri, 05 Aug 2005 08:06:07 -0500
I just setup a quick sample. Using Axis 1.2.1 and Tomcat 5.5 running in
JRE 5.0
I installed a second web app into tomcat. It worked.
I installed the two web apps by putting XML config files under
CATALINA_HOME/conf/Catalina/localhost/ like below. Both pointed at two
different exploded-war directories
I then start Tomcat using the this command (allows remote debug from
eclipse):
%CATALINA_HOME%\bin\catalina.bat jpda start
This is my standard development procedure. My client connected to the Axis
server via:
MyServiceLocator loc = new MyServiceLocator();
loc.setMyPortEndpointAddress("http://127.0.0.1:8080/server/services/MyPort";);
MyPortType port = loc.getMyPort();
port.invokeMyFunction();
Hows is your procedure different? I don't know if it's important, but
during
this test I had all of the Axis jar dependencies in both war/WEB-INF/lib
directories (duplicated).
Quoting J H <[EMAIL PROTECTED]>:
> Here's is the complete stack trace...
>
> Again, the scenario is that when I install the 2 wars on seperate
machines,
> everything works fine. When I install the wars on the same machine,
nothing
> works and I get the message pasted below after about 5 minutes from the
> first client axis/soap call.
>
> My theory is that both webapplications are serving out to port 8080 and
when
> the axis client is trying to communicate with the axis server it
connects to
> port 8080, but it is talking to the wrong webapp. That is why
everything
> works fine when I move the webapps to different machines.
>
> Thanks again,
> Jeff
>
> Caught SOAPException :; nested exception is:
>java.net.SocketTimeoutException: Read timed out
> AxisFault
> faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
> faultSubcode:
> faultString: java.net.SocketTimeoutException: Read timed out
> faultActor:
> faultNode:
> faultDetail:
>
{http://xml.apache.org/axis/}stackTrace:java.net.SocketTimeoutException:
> Read timed out
>at java.net.SocketInputStream.socketRead0(Native Method)
>at java.net.SocketInputStream.read(SocketInputStream.java:129)
>at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
>at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
>at
>
org.apache.axis.transport.http.HTTPSender.readHeadersFromSocket(HTTPSender.java:583)
> at
org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:143)
>at
>
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
>at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
>at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
>at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
>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 com.project.slide.store.SoapMessage.sendMessage(SoapMessage.java:51)
>at
>
com.project.slide.store.SecurityStore.retrieveObject(SecurityStore.java:118)
>at
>
org.apache.slide.store.StandardStore.retrieveObject(StandardStore.java:171)
> at
org.apache.slide.structure.StructureImpl.create(StructureImpl.java:321)
>at
>
org.apache.slide.common.XMLUnmarshaller.loadObjectNode(XMLUnmarshaller.java:194)
>at
>
org.apache.slide.common.XMLUnmarshaller.loadObjectNode(XMLUnmarshaller.java:299)
>at
>
org.apache.slide.common.XMLUnmarshaller.unmarshal(XMLUnmarshaller.java:126)
>at
>
org.apache.slide.common.NamespaceAccessTokenImpl.importData(NamespaceAccessTokenImpl.java:306)
>at org.apache.slide.common.Namespace.loadBaseData(Namespace.java:821)
>at org.apache.slide.common.Domain.initNamespace(Domain.java:859)
>at org.apache.slide.common.Domain.init(Domain.java:478)
>at org.apache.slide.common.Domain.init(Domain.java:412)
>at org.apache.slide.common.Domain.init(Domain.java:375)
>at org.apache.slide.webdav.WebdavServlet.init(WebdavServlet.java:286)
>at javax.servlet.Gene
Re: WSDL2Java and BCEL ?
Sun's standard JRE license allows you to distribute a JRE with your app with tools.jar included. Jeff - Original Message - From: "Davanum Srinivas" <[EMAIL PROTECTED]> To: Sent: Friday, August 05, 2005 8:03 AM Subject: Re: WSDL2Java and BCEL ? You could always use jdtcore from eclipse to compile the java classes. that does not use tools.jar and is available under a open source license. -- dims On 8/5/05, Murali Yelamanchili <[EMAIL PROTECTED]> wrote: > Hi, > > Is there a plan to integrate BCEL with Axis WSDL2Java > ? > Right now, WSDL2Java generates .java files for the > complex types present in a WSDL - > > We are working on a standalone Java application, that > could be deployed in a machine without a JDK install. > The application requirements states that only a JRE is > required. > > This Java application uses Axis to invoke Web > Services. If the Web Services uses complex types, then > we would have to generate the corresponding Java stubs > and Beans. But the absence of a compiler on that > machine, means we may to write out bytecode for the > Beans directly. > > Bundling JDK tools.jar with our application is a NO at > this time. > > Axis WSDL2Java seems to have classes such as JavaBean > Writer, and JavaClassWriter to take care of writing > the Beans. > > Is there any plans to add an option, which will allow > a user to generate Bytecode directly instead - atleast > the Beans for the complex Types. > > > Regards, > Murali > > > > > > Start your day with Yahoo! - make it your home page > http://www.yahoo.com/r/hs > > -- Davanum Srinivas -http://blogs.cocoondev.org/dims/
Re: Happyaxis reports problems loading libraries, found but with problems
I have almost the problem as Jonathan. I'm running Tomcat 5.5.9 with Java 1.5
on Linux. My message reads:
See http://xml.apache.org/security/ {4}
The root cause was: org/apache/commons/logging/LogFactory
This happens whether I put xmlsec-1.2.1.jar in $CATALINA_HOME/common/lib or
$CATALINA_HOME/common/endorsed. When I put xmlsec-1.2.1.jar in
$CATALINA_HOME/webapps/axis/WEB-INF/lib, the message was
See http://xml.apache.org/security/ {4}
The root cause was: {0}
What does this mean? Should I be using an older version of xmlsec-1.2.1.jar?
On Friday 05 August 2005 09:58, Javier Gonzalez wrote:
> Where are xmlsec.jar and activation.jar located? (the hint that the
> error message told you)
>
> IIRC, in Tomcat the classloaders are ordered like this: webapp ->
> shared -> common -> system. The classloaders can look in that order
> and not in the reverse order. That is, if A.jar is on the webapp lib
> dir, B.jar is in shared/lib, and A depends on B, it's ok, since the
> webapp classloader can ask the next classloader for B. But if B
> depends on A, then you'll have an error because the shared classloader
> can't look "back" into the webapp classloader.
>
> On 8/5/05, Jonathan J. Vargas R. <[EMAIL PROTECTED]> wrote:
> > Greets,
> >
> > I tried to install xmlsec into axis, but seems axis has problems doing
> > this. The problem is with xmlsec, but I still don't know how to solve
> > it or fix it. I am using tomcat, This is the happyaxis report:
> >
> >
> > Optional Components
> >
> >
> > Warning: could not find a dependency of class
> > org.apache.xml.security.Init from file xmlsec.jar
> > XML Security is not supported
> > See http://xml.apache.org/security/
> > The root cause was: org/apache/xpath/compiler/FuncLoader
> > This can happen e.g. if org.apache.xml.security.Init is in the
> > 'common' classpath, but a dependency like activation.jar is only in
> > the webapp classpath.
> >
> > Found Java Secure Socket Extension (javax.net.ssl.SSLSocketFactory) at
> > an unknown location
Custom HTTP Listener
Hello, I'm very new to Axis/Tomcat and am working on my first web service and have a couple of questions. I'm developing on a Win2K box running Tomcat 4.1.31 and Axis 1.2.1. In everything that I've read on deployment of services, it gives good insruction on how to deploy using the AdminClient to update the server-config.wsdd but do not say explicitly where the services class/jar files should be deployed? Am I correct in thinking that it's Tomcat's webapps/axis/WEB-INF classes/lib directories? Also, I've been reading "Building Web Services with Java" and the chapter on Axis mentions that the built-in HTTP listener is the AxisServlet class. I would like to sub-class this with our own servlet that does some initialization. Is this possible? If so, how do I specify that Axis should use this class? Thanks in advance, Shelli
Re: WSDL2Java and BCEL ?
You could always use jdtcore from eclipse to compile the java classes. that does not use tools.jar and is available under a open source license. -- dims On 8/5/05, Murali Yelamanchili <[EMAIL PROTECTED]> wrote: > Hi, > > Is there a plan to integrate BCEL with Axis WSDL2Java > ? > Right now, WSDL2Java generates .java files for the > complex types present in a WSDL - > > We are working on a standalone Java application, that > could be deployed in a machine without a JDK install. > The application requirements states that only a JRE is > required. > > This Java application uses Axis to invoke Web > Services. If the Web Services uses complex types, then > we would have to generate the corresponding Java stubs > and Beans. But the absence of a compiler on that > machine, means we may to write out bytecode for the > Beans directly. > > Bundling JDK tools.jar with our application is a NO at > this time. > > Axis WSDL2Java seems to have classes such as JavaBean > Writer, and JavaClassWriter to take care of writing > the Beans. > > Is there any plans to add an option, which will allow > a user to generate Bytecode directly instead - atleast > the Beans for the complex Types. > > > Regards, > Murali > > > > > > Start your day with Yahoo! - make it your home page > http://www.yahoo.com/r/hs > > -- Davanum Srinivas -http://blogs.cocoondev.org/dims/
RE: "Invalid element" error - Lower-case property name
I think I've made some progress; I found this archived mail: http://marc.theaimsgroup.com/?l=axis-user&m=102260719826152&w=2 It seems to indicate that when I ran WSDL2Java on the Siebel WSDL, some static code _should_ have been generated in my bean classes, to set up the XML -> Java mapping with an upper-case QName. (I ran a very basic WSDL2Java command; I just passed it the WSDL file name, and no options.) Re-reading the User Guide information on WSDL2Java again confirms this, now that I know what to look for. I don't have any idea yet why some expected things didn't generate, but since my number 1 non-standard piece is that I'm using JMS endpoints, my suspicions center there. I guess I'll start running some JIRA searches, then walk through the WSDL2Java code if nothing turns up in JIRA... if any of you out there have ideas, please let me know...! Meghan Pietila Granite Consulting
RE: Deployment strange exception
Con ese nombre, imagino que habla español, asi que:
Seguramente ese error es porque no está especificando el usuario y la
contraseña en la linea de comando al ejecutar el AdminClient.
Sin embargo también es posible que la parte de servidor esté identificando
la petición del AdminClient como proveniente de una dirección IP distinta a
la de localhost.
Si es asi, creo que podria probar alguna de estas dos opciones:
1) bajar la interfaz de red del SO usando ifdown e intentar nuevamente
2) Configurar el Axis para que acepte peticiones desde una IP diferente de
localhost. La verdad no me acuerdo en este momento como se hace, pero estoy
seguro que en la documentació de referencia de Axis dice como hacerlo.
Suerte
Hello,
I have a problem deploying my web service with axis using the
AdminClient tool. I get the following error:
Processing file deployServicioMessageDocument.wsdd
Exception: AxisFault
faultCode: {http://xml.apache.org/axis/}HTTP
faultSubcode:
faultString: (401)Unauthorized
faultActor:
faultNode:
faultDetail:
{}:return code: 401
401 Unauthorized
Unauthorized
{http://xml.apache.org/axis/}HttpErrorCode:401
I am using Tomcat5.5.9 and axis1.2 over Linux. What is this error due to?
Could anybody be so kind as to help me, please?
Thank you very much in advance.
Regards,
Antonio.
"Invalid element" error - Lower-case property name
I was encountering an "Invalid element" error when I attempted to receive a response message with my Axis client (Siebel service). I found this error mentioned many times in the axis-user mailing list archives, but was unable to find anyone listing an explanation or a solution. I debugged through the Axis code and noticed that the error was occurring because when BeanDeserializer.onStartChild is called, the "propertyMap" has "listOfUsbCustomerElement" as the child description, while the element is actually named "ListOfUsbCustomerElement". When I traced this back, I found that the lower-case name is coming from a call in the BeanDeserializerFactory that ends up retrieving the bean properties through introspection; hence, lower-case first letter in property names. As the archived email I reference below explains, one way around it is to customize the BeanInfo interface... I imagine Axis must somewhere normally provide a mapping to get from the Java name to the XML name... can anyone point me in the right direction? I suspect something is missing in my set up. In the meantime, I'll continue exploring... if I figure it out, I'll post the solution back here for anyone else who runs into this... Meghan Pietila Granite Consulting Archived mail referencing this problem: http://marc.theaimsgroup.com/?l=axis-user&m=103705794612785&w=2 Partial stacktrace illustrating the resulting error (Axis 1.2.1): 04-08-2005 15:16:36,688 [ERROR] org.apache.axis.client.Call: Exception: org.xml.sax.SAXException: Invalid element in com.blank.www.ListOfUsbCustomerOfferTopElmt - ListOfUsbCustomerOffer at org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserializer.java:258) at org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1 035) at org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165) at org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141) at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:345) at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384) at org.apache.axis.client.Call.invoke(Call.java:2448) at org.apache.axis.client.Call.invoke(Call.java:2347) at org.apache.axis.client.Call.invoke(Call.java:1804)
Re: AxisServlet Provide HTML Input Form?
+1 from me. None is planned. -- dims On 8/5/05, James Wilson <[EMAIL PROTECTED]> wrote: > I've worked in the past with BEA's web service generation. I found it usefull > to have the simple HTML input form they provide for sending test messages into > the service. Is there any plans to expand the reportServiceInfo(...) method > on > the AxisServlet to provide a simple HTML service interface? > > I would expect that this could be done completely dynamic, building the HTML > form based on the WSDL of the service requested: > http://localhost:8080/mywebapp/services/MyServicePort > > If none is planned, I may try to find time to investigate the viability of > such > a solution... > > -James > -- Davanum Srinivas -http://blogs.cocoondev.org/dims/
AxisServlet Provide HTML Input Form?
I've worked in the past with BEA's web service generation. I found it usefull to have the simple HTML input form they provide for sending test messages into the service. Is there any plans to expand the reportServiceInfo(...) method on the AxisServlet to provide a simple HTML service interface? I would expect that this could be done completely dynamic, building the HTML form based on the WSDL of the service requested: http://localhost:8080/mywebapp/services/MyServicePort If none is planned, I may try to find time to investigate the viability of such a solution... -James
Re: Happyaxis reports problems loading libraries, found but with problems
Where are xmlsec.jar and activation.jar located? (the hint that the error message told you) IIRC, in Tomcat the classloaders are ordered like this: webapp -> shared -> common -> system. The classloaders can look in that order and not in the reverse order. That is, if A.jar is on the webapp lib dir, B.jar is in shared/lib, and A depends on B, it's ok, since the webapp classloader can ask the next classloader for B. But if B depends on A, then you'll have an error because the shared classloader can't look "back" into the webapp classloader. On 8/5/05, Jonathan J. Vargas R. <[EMAIL PROTECTED]> wrote: > Greets, > > I tried to install xmlsec into axis, but seems axis has problems doing > this. The problem is with xmlsec, but I still don't know how to solve > it or fix it. I am using tomcat, This is the happyaxis report: > > > Optional Components > > > Warning: could not find a dependency of class > org.apache.xml.security.Init from file xmlsec.jar > XML Security is not supported > See http://xml.apache.org/security/ > The root cause was: org/apache/xpath/compiler/FuncLoader > This can happen e.g. if org.apache.xml.security.Init is in the > 'common' classpath, but a dependency like activation.jar is only in > the webapp classpath. > > Found Java Secure Socket Extension (javax.net.ssl.SSLSocketFactory) at > an unknown location > > > -- > Jonathan J. Vargas Rodriguez > [EMAIL PROTECTED] > "Conservar el silencio interior cuando vuelo en la tormenta me es > mejor, porque asi ya no soy otra gota de la tempestad" > -- Javier Gonzalez Nicolini
Re: Change the Port that Axis Service runs as
I just setup a quick sample. Using Axis 1.2.1 and Tomcat 5.5 running in JRE 5.0
I installed a second web app into tomcat. It worked.
I installed the two web apps by putting XML config files under
CATALINA_HOME/conf/Catalina/localhost/ like below. Both pointed at two
different exploded-war directories
I then start Tomcat using the this command (allows remote debug from eclipse):
%CATALINA_HOME%\bin\catalina.bat jpda start
This is my standard development procedure. My client connected to the Axis
server via:
MyServiceLocator loc = new MyServiceLocator();
loc.setMyPortEndpointAddress("http://127.0.0.1:8080/server/services/MyPort";);
MyPortType port = loc.getMyPort();
port.invokeMyFunction();
Hows is your procedure different? I don't know if it's important, but during
this test I had all of the Axis jar dependencies in both war/WEB-INF/lib
directories (duplicated).
Quoting J H <[EMAIL PROTECTED]>:
> Here's is the complete stack trace...
>
> Again, the scenario is that when I install the 2 wars on seperate machines,
> everything works fine. When I install the wars on the same machine, nothing
> works and I get the message pasted below after about 5 minutes from the
> first client axis/soap call.
>
> My theory is that both webapplications are serving out to port 8080 and when
> the axis client is trying to communicate with the axis server it connects to
> port 8080, but it is talking to the wrong webapp. That is why everything
> works fine when I move the webapps to different machines.
>
> Thanks again,
> Jeff
>
> Caught SOAPException :; nested exception is:
> java.net.SocketTimeoutException: Read timed out
> AxisFault
> faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
> faultSubcode:
> faultString: java.net.SocketTimeoutException: Read timed out
> faultActor:
> faultNode:
> faultDetail:
> {http://xml.apache.org/axis/}stackTrace:java.net.SocketTimeoutException:
> Read timed out
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(SocketInputStream.java:129)
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
> at
>
org.apache.axis.transport.http.HTTPSender.readHeadersFromSocket(HTTPSender.java:583)
> at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:143)
> at
>
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
> at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
> at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
> at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
> 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 com.project.slide.store.SoapMessage.sendMessage(SoapMessage.java:51)
> at
> com.project.slide.store.SecurityStore.retrieveObject(SecurityStore.java:118)
> at
> org.apache.slide.store.StandardStore.retrieveObject(StandardStore.java:171)
> at
> org.apache.slide.structure.StructureImpl.create(StructureImpl.java:321)
> at
>
org.apache.slide.common.XMLUnmarshaller.loadObjectNode(XMLUnmarshaller.java:194)
> at
>
org.apache.slide.common.XMLUnmarshaller.loadObjectNode(XMLUnmarshaller.java:299)
> at
> org.apache.slide.common.XMLUnmarshaller.unmarshal(XMLUnmarshaller.java:126)
> at
>
org.apache.slide.common.NamespaceAccessTokenImpl.importData(NamespaceAccessTokenImpl.java:306)
> at org.apache.slide.common.Namespace.loadBaseData(Namespace.java:821)
> at org.apache.slide.common.Domain.initNamespace(Domain.java:859)
> at org.apache.slide.common.Domain.init(Domain.java:478)
> at org.apache.slide.common.Domain.init(Domain.java:412)
> at org.apache.slide.common.Domain.init(Domain.java:375)
> at org.apache.slide.webdav.WebdavServlet.init(WebdavServlet.java:286)
> at javax.servlet.GenericServlet.init(GenericServlet.java:256)
> at org.apache.slide.webdav.WebdavServlet.init(WebdavServlet.java:228)
> at
> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:935)
> at
> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:823)
> at
>
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3421)
> at
> org.apache.catalina.core.StandardContext.start(StandardContext.java:3609)
> at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188)
> at org.apache.catalina.core.StandardHost.start(StandardHost.java:738)
> at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188)
> at
> org.apache.cat
Deployment strange exception
Hello,
I have a problem deploying my web service with axis using the
AdminClient tool. I get the following error:
Processing file deployServicioMessageDocument.wsdd
Exception: AxisFault
faultCode: {http://xml.apache.org/axis/}HTTP
faultSubcode:
faultString: (401)Unauthorized
faultActor:
faultNode:
faultDetail:
{}:return code: 401
401 Unauthorized
Unauthorized
{http://xml.apache.org/axis/}HttpErrorCode:401
I am using Tomcat5.5.9 and axis1.2 over Linux. What is this error due
to? Could anybody be so kind as to help me, please?
Thank you very much in advance.
Regards,
Antonio.
Re: minOccurs and nillable
Anne,
Yes, I came to the conclusion there was a difference, but I added both
purely to try and persuade Axis to handle the error.
I think Axis is ignoring the minOccurs="0", despite the fact I can see it
being set up in the source code generated:
elemField = new org.apache.axis.description.ElementDesc();
elemField.setFieldName("requestCategoryCode");
elemField.setXmlName(new
javax.xml.namespace.QName("http://www.caps-solutions.co.uk/schema/uniform/72b/servicerequest/sr/srtypes","RequestCategoryCode";));
elemField.setXmlType(new
javax.xml.namespace.QName("http://www.caps-solutions.co.uk/schema/uniform/72b/common/uniformtypes";,
"CNCODE_CodeValue"));
elemField.setMinOccurs(0);
elemField.setNillable(true);
Can this really be an Axis bug? I thought this would be fairly heavily tested?
John
On Fri, Aug 05, 2005 at 08:08:08AM -0400, Anne Thomas Manes wrote:
> John,
>
> There's a difference between missing and null. If the element had a
> null value, then the element would be there, and it would say
> .
>
> If the schema says minOccurs="0", then this message is valid.
> It appears that Axis is not properly handling minOccurs="0".
>
> Anne
>
> On 8/5/05, John Baker <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I am using a WSDL file supplied to be by a third party and I suspect it
> > doesn't quite reflect what their .NET server is returning in the SOAP
> > messages. I am getting this exception:
> >
> > java.io.IOException: Non nillable element 'requestCategoryCode' is null.
> > at
> > org.apache.axis.encoding.ser.BeanSerializer.serialize(BeanSerializer.
> > java:215)
> > at
> > org.apache.axis.encoding.SerializationContext.serializeActual(Seriali
> > zationContext.java:1426)
> > at
> > org.apache.axis.encoding.SerializationContext.serialize(Serialization
> > Context.java:914)
> > at
> > org.apache.axis.encoding.SerializationContext.serialize(Serialization
> > Context.java:702)
> > at
> > org.apache.axis.encoding.ser.BeanSerializer.serialize(BeanSerializer.
> > java:230)
> > at
> > org.apache.axis.encoding.SerializationContext.serializeActual(Seriali
> > zationContext.java:1426)
> > at
> > org.apache.axis.encoding.SerializationContext.serialize(Serialization
> > Context.java:914)
> >
> > So looking at (an extract of) the XML received by Axis:
> >
> > PESTM > plaintTypeText>MiceCRMTES
> > CRM Test
> > OfficerCC > vedCode>Call
> > Centre2005-08-04T0
> > 6:52:03.000+01:00RECRece
> > ivedEEastern Area
> > Team > AreaTeamText>
> >
> > And here's the relevant part of the WSDL:
> >
> >
> >
> > Contains details of status,
> > allocated officer
> > codes etc
> >
> >
> >> type="uni:CNCODE_CodeValue">
> >
> > Code
> > value for complaint
> > type
> >
> >
> > > type="uni:CNCODE_TextValue">
> >
> >
> > Full text of complaint type - read
> > only
> >
> >
> > > type="uni:CNCODE_CodeValue">
> >
> >
> > complaint type category code if set
> >
> >
> >
> >
> >
> >Officer code for
> > allocated officer > tion>
> >
> >
> > > type="uni:CNCODE_TextValue">
> >
> > Full name of allocated
> > officer > >
> >
> >
> > > type="xs:dateTime" minOccurs="0">
> >
> > The date and time the request
> > was allocated to a
> > n officer to investigate
> >
> >
> > > type="uni:CNCODE_CodeValue">
> >
> > Code value indicating how the
> > complaint was rece
> > ived
> >
> >
> > > type="uni:CNCODE_TextValue">
> >
> > Full description of how received
> > code > ntation>
> >
> >
> >
> > (etc.)
> >
> > It would seem to me that this change needs to be made:
> >
> >> minOccurs="0" nillable="true">
> >
> > As the .NET server has not sent back a RequestCategoryCode element.
> >
> > Does this sound correct?
> >
> > Thanks,
> >
> >
> > John
> >
Re: minOccurs and nillable
John, There's a difference between missing and null. If the element had a null value, then the element would be there, and it would say . If the schema says minOccurs="0", then this message is valid. It appears that Axis is not properly handling minOccurs="0". Anne On 8/5/05, John Baker <[EMAIL PROTECTED]> wrote: > Hi, > > I am using a WSDL file supplied to be by a third party and I suspect it > doesn't quite reflect what their .NET server is returning in the SOAP > messages. I am getting this exception: > > java.io.IOException: Non nillable element 'requestCategoryCode' is null. > at > org.apache.axis.encoding.ser.BeanSerializer.serialize(BeanSerializer. > java:215) > at > org.apache.axis.encoding.SerializationContext.serializeActual(Seriali > zationContext.java:1426) > at > org.apache.axis.encoding.SerializationContext.serialize(Serialization > Context.java:914) > at > org.apache.axis.encoding.SerializationContext.serialize(Serialization > Context.java:702) > at > org.apache.axis.encoding.ser.BeanSerializer.serialize(BeanSerializer. > java:230) > at > org.apache.axis.encoding.SerializationContext.serializeActual(Seriali > zationContext.java:1426) > at > org.apache.axis.encoding.SerializationContext.serialize(Serialization > Context.java:914) > > So looking at (an extract of) the XML received by Axis: > > PESTM plaintTypeText>MiceCRMTES > CRM Test > OfficerCC vedCode>Call > Centre2005-08-04T0 > 6:52:03.000+01:00RECRece > ivedEEastern Area > Team AreaTeamText> > > And here's the relevant part of the WSDL: > > > > Contains details of status, > allocated officer > codes etc > > > type="uni:CNCODE_CodeValue"> > > Code > value for complaint > type > > > type="uni:CNCODE_TextValue"> > > > Full text of complaint type - read > only > > > type="uni:CNCODE_CodeValue"> > > > complaint type category code if set > > > > > >Officer code for > allocated officer tion> > > > type="uni:CNCODE_TextValue"> > > Full name of allocated > officer > > > > type="xs:dateTime" minOccurs="0"> > > The date and time the request > was allocated to a > n officer to investigate > > > type="uni:CNCODE_CodeValue"> > > Code value indicating how the > complaint was rece > ived > > > type="uni:CNCODE_TextValue"> > > Full description of how received > code ntation> > > > > (etc.) > > It would seem to me that this change needs to be made: > >minOccurs="0" nillable="true"> > > As the .NET server has not sent back a RequestCategoryCode element. > > Does this sound correct? > > Thanks, > > > John >
minOccurs and nillable
Hi, I am using a WSDL file supplied to be by a third party and I suspect it doesn't quite reflect what their .NET server is returning in the SOAP messages. I am getting this exception: java.io.IOException: Non nillable element 'requestCategoryCode' is null. at org.apache.axis.encoding.ser.BeanSerializer.serialize(BeanSerializer. java:215) at org.apache.axis.encoding.SerializationContext.serializeActual(Seriali zationContext.java:1426) at org.apache.axis.encoding.SerializationContext.serialize(Serialization Context.java:914) at org.apache.axis.encoding.SerializationContext.serialize(Serialization Context.java:702) at org.apache.axis.encoding.ser.BeanSerializer.serialize(BeanSerializer. java:230) at org.apache.axis.encoding.SerializationContext.serializeActual(Seriali zationContext.java:1426) at org.apache.axis.encoding.SerializationContext.serialize(Serialization Context.java:914) So looking at (an extract of) the XML received by Axis: PESTMMiceCRMTES CRM Test OfficerCCCall Centre2005-08-04T0 6:52:03.000+01:00RECRece ivedEEastern Area Team And here's the relevant part of the WSDL: Contains details of status, allocated officer codes etc Code value for complaint type Full text of complaint type - read only complaint type category code if set Officer code for allocated officer Full name of allocated officer The date and time the request was allocated to a n officer to investigate Code value indicating how the complaint was rece ived Full description of how received code (etc.) It would seem to me that this change needs to be made: As the .NET server has not sent back a RequestCategoryCode element. Does this sound correct? Thanks, John
webservice with inout parameters
Hello, I have to implement a SOAP webservice in Java (using tomcat as a servlet container) that offers a method with a given signature. The webservice will be called by a Visual Basic client using the Microsoft SOAP Toolkit. The signature of the method requires a string parameter which is passed 'by reference'. The question is how to tell the AXIS-Server to generate a SOAP-reply which returns not only the return-value of the function itself but additionally the manipulated string parameter without making changes to the client-implementation. Thanks Rainer Rogatzki mailto:[EMAIL PROTECTED] Gemeinsames Gebietsrechenzentrum Hagen GGRZ Hagen - Hoheleye 3a - 58093 Hagen Fon 02331/987-621 Fax 02331/987-77621 Telearbeitsplatz Fon 0208 / 2 999 369 Internet: http://www.ggrz-hagen.nrw.de Anfahrt: http://www.ggrz-hagen.nrw.de/anschrift.htm
Re: Axis version which supports SOAP with attachments
Hi again.
Sorry, I forgot to mention that AFAIK, you need activation.jar and
mail.jar to get attachment support. If you have just started your
project, I'd suggest you take a look at MTOM (AXIS2), which is a better
way of sending attachments.
Regards,
Tom
Mukesh Kumar Maniraj wrote:
Hello,
Can any one please let me know, which version of axis supports SOAP with
attachments,
I am using axis 1.1 with activation1.0.1.jar and saaj-api.jar and I
am getting the
following AxisFault exception,
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.lang.RuntimeException : No support for attachments
faultActor:
faultNode:
faultDetail:
{ http://xml.apache.org/axis/}stackTrace:
java.lang.RuntimeException: No support for attachments.
Greatly appreciate your help,
-Mukesh
Re: Axis version which supports SOAP with attachments
Hi,
I used 1.2.1, but it had a bug (2084) so I switched to the CVS Version
(1.3) which is working nicely.
Regards,
Tom
Mukesh Kumar Maniraj wrote:
Hello,
Can any one please let me know, which version of axis supports SOAP with
attachments,
I am using axis 1.1 with activation1.0.1.jar and saaj-api.jar and I
am getting the
following AxisFault exception,
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.lang.RuntimeException : No support for attachments
faultActor:
faultNode:
faultDetail:
{ http://xml.apache.org/axis/}stackTrace:
java.lang.RuntimeException: No support for attachments.
Greatly appreciate your help,
-Mukesh
