Re: Understanding WS-*
On Wed, 2009-04-01 at 07:21 -0400, Sam Carleton wrote: I know that Axis2/C supports all these WS-* things, I have read over the pages about them, but I still don't understand exactly how to fit them into the big picture. Can anyone recommend where I could go (or maybe a book I could read) that would help explain Web Services in general and how how to use all these WS-* in developing a solution? It does *NOT* need to be Axis2/C centric, any language is fine with me actually. http://wso2.org/library and msdn also has some good articles. Sam
Using JAX-B in Axis2 Service without JAX-WS
Is it possible to use JAX-B binding without using JAX-WS deployment?
As an example, I have a User class that is annotated with JAX-B
annotations. And I have a simple service that creates users:
public interface MyService {
public User createUser(User userSpecification);
}
And I have a services.xml like this:
service name=Axis2UserService
parameter name=ServiceClass
locked=falseexample.MyService/parameter
operation name=createUser
messageReceiver
class=org.apache.axis2.jaxws.server.JAXWSMessageReceiver/
/operation
/service
The generated wsdl still uses ADB bindings. What message receiver do I
need to use to get the JAX-B bindings? If I deploy the same service as
a JAX-WS service then it all works find and the schema is as I need it.
However, I don't want to deploy as JAX-WS. I want to deploy as a normal
Axis2 service so I can reuse my existing modules and Spring
configuration.
Is this possible?
--
Hamlet D'Arcy
hamlet.da...@pearson.com
+1(952)681-3636
Where is Axis 1.3 Final download site?
Hello All, I am trying to find Axis 1.3 Final release but i can't find in download section, all the download mirrors have deleted the file!!! If any have the dist it would be great to re-upload it as Axis 1.4 have a severe bug for me. Regards, Abu Bakr Awad
Re: Where is Axis 1.3 Final download site?
You can always get old artifacts from the central Maven repository [1], but these are only the individual JARs. Andreas [1] http://repo2.maven.org/maven2/axis/axis/ On Wed, Apr 1, 2009 at 14:59, Abu Bakr Awad bakr.a...@gmail.com wrote: Hello All, I am trying to find Axis 1.3 Final release but i can't find in download section, all the download mirrors have deleted the file!!! If any have the dist it would be great to re-upload it as Axis 1.4 have a severe bug for me. Regards, Abu Bakr Awad
Re: Where is Axis 1.3 Final download site?
Thanks, But if you have the whole package it would be great. On Wed, Apr 1, 2009 at 3:08 PM, Andreas Veithen andreas.veit...@gmail.comwrote: You can always get old artifacts from the central Maven repository [1], but these are only the individual JARs. Andreas [1] http://repo2.maven.org/maven2/axis/axis/ On Wed, Apr 1, 2009 at 14:59, Abu Bakr Awad bakr.a...@gmail.com wrote: Hello All, I am trying to find Axis 1.3 Final release but i can't find in download section, all the download mirrors have deleted the file!!! If any have the dist it would be great to re-upload it as Axis 1.4 have a severe bug for me. Regards, Abu Bakr Awad
Re: Where is Axis 1.3 Final download site?
Abu Bakr Awad schreef: I am trying to find Axis 1.3 Final release but i can't find in download section, all the download mirrors have deleted the file!!! If any have the dist it would be great to re-upload it as Axis 1.4 have a severe bug for me. http://archive.apache.org/dist/ws/axis2/1_3/ for Axis2 http://archive.apache.org/dist/ws/axis/1_3/ for Axis Kind regards, Anton
The client keeps running when using Sandesha2
Hi, I've been doing some tests with Sandesha2, mainly following the user guide (http://ws.apache.org/sandesha/sandesha2/userGuide.html). Despite some errors in the documentation and the usage of some deprecated stuff, I've managed to make the ping and the echo examples run using Sandesha2. There's one problem, however, that I can't solve: the client keeps running even after receiving responses from the server and after sending TerminateSequence to the server. Has anyone faced this problem? What am I possibly doing wrong? Best regards, José Ricardo.
Re: Cannot see service give 500 Error
You could grab the war distribution for Axis2 and simple drop it into
Tomcat. You dont need to configure anything, It will work out of the box.
Thanks,
Keith.
On Wed, Apr 1, 2009 at 2:27 AM, Cyril Furtado cyr...@skire.com wrote:
Hi
I deployed axis1.4.1 on Tomcat 5.0 , using all the jars provided in the
axis2 lib , added jms,jar , used the /conf/axis2.xml
Using the samples/pojo put StockQuoteService.aar as given in samples under
/services directory
I have configured web.xml to start the Axis2 servlet
I have checked almost everything, but I cannot see the service
Here is the log --
2009-03-31 13:37:15,761 DEBUG engine.AxisEngine -
[MessageContext: logID=urn:uuid:64582CF668548213C21238531835777]
sendFault:null
2009-03-31 13:37:15,761 DEBUG engine.Phase-
[MessageContext: logID=urn:uuid:64582CF668548213C21238531835777] Checking
pre-condition for Phase MessageOut
2009-03-31 13:37:15,761 DEBUG engine.Phase-
[MessageContext: logID=urn:uuid:64582CF668548213C21238531835777] Invoking
phase MessageOut
2009-03-31 13:37:15,761 DEBUG engine.Phase-
[MessageContext: logID=urn:uuid:64582CF668548213C21238531835777] Checking
post-conditions for phase MessageOut
2009-03-31 13:37:15,761 DEBUG engine.Phase-
[MessageContext: logID=urn:uuid:64582CF668548213C21238531835777] Checking
pre-condition for Phase Security
2009-03-31 13:37:15,761 DEBUG engine.Phase-
[MessageContext: logID=urn:uuid:64582CF668548213C21238531835777] Invoking
phase Security
2009-03-31 13:37:15,761 DEBUG engine.Phase-
[MessageContext: logID=urn:uuid:64582CF668548213C21238531835777] Checking
post-conditions for phase Security
2009-03-31 13:37:15,761 DEBUG addressing.EndpointReference-
hasAnonymousAddress: http://www.w3.org/2005/08/addressing/anonymous is
Anonymous: true
2009-03-31 13:37:15,761 DEBUG http.ApplicationXMLFormatter-
contentType set from messageContext =null
2009-03-31 13:37:15,761 DEBUG om.OMOutputFormat - Start
getContentType: OMOutputFormat [ mimeBoundary =null rootContentId=null
doOptimize=false doingSWA=false isSOAP11=false charSetEncoding=UTF-8
xmlVersion=null contentType=null ignoreXmlDeclaration=false
autoCloseWriter=true actionProperty=null optimizedThreshold=0]
2009-03-31 13:37:15,761 DEBUG om.OMOutputFormat -
getContentType= {application/soap+xml} OMOutputFormat [ mimeBoundary =null
rootContentId=null doOptimize=false doingSWA=false isSOAP11=false
charSetEncoding=UTF-8 xmlVersion=null contentType=application/soap+xml
ignoreXmlDeclaration=false autoCloseWriter=true actionProperty=null
optimizedThreshold=0]
2009-03-31 13:37:15,761 DEBUG http.ApplicationXMLFormatter- (NOTE)
contentType from format is=application/soap+xml
2009-03-31 13:37:15,761 DEBUG http.ApplicationXMLFormatter-
contentType returned =application/xml; charset=UTF-8
2009-03-31 13:37:15,761 DEBUG http.ApplicationXMLFormatter- start
writeTo()
2009-03-31 13:37:15,761 DEBUG util.StAXUtils -
XMLStreamWriter is com.ctc.wstx.sw.SimpleNsStreamWriter
2009-03-31 13:37:15,761 DEBUG http.ApplicationXMLFormatter- end
writeTo()
2009-03-31 13:37:15,761 DEBUG transport.TransportUtils- Did not
find RequestResponseTransport cannot set response written
2009-03-31 13:37:15,761 DEBUG engine.Phase-
[MessageContext: logID=urn:uuid:64582CF668548213C21238531835777] Invoking
flowComplete() in Phase Security
2009-03-31 13:37:15,761 DEBUG engine.Phase-
[MessageContext: logID=urn:uuid:64582CF668548213C21238531835777] Invoking
flowComplete() in Phase MessageOut
Please let me know whats wrong
Thanks
Cyril
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
Re: AxisFault namespace mismatch require
The exception says it all... The server expects your request to be in the http://hello.axis2.com/xsd namespace but your request was in the http://hello.axis2.com http://hello.axis2.com/xsd namespace. If you fix this it would work. BTW how did you write your client? If you used wsdl2Java to generate a stub it would have handled this namespace issue. Thanks, Keith. On Wed, Apr 1, 2009 at 1:56 AM, bandrm rajivband...@gmail.com wrote: Hello, I developed a simple web service using predominantly ant build script. The web service is deployed in tomcat and it is working fine. I have generated wsdl using using ant tool (Class org.apache.axis2.tool.ant.Java2WSDLTask). I developed client and consumed this wsdl. Now, when I execute the client program, I get the following exception. This might be elementary, but would like to get it resolved. 485 ERROR org.apache.axis2.rpc.receivers.RPCMessageReceiver - Exception occurred while trying to invoke service method sayHello org.apache.axis2.AxisFault: namespace mismatch require http://hello.axis2.com/xsd found http://hello.axis2.com at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:103) at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:39) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:144) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:279) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:116) at javax.servlet.http.HttpServlet.service(HttpServlet.java:647) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:875) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689) at java.lang.Thread.run(Unknown Source) -- View this message in context: http://www.nabble.com/AxisFault-namespace-mismatch-require-tp22811514p22811514.html Sent from the Axis - User mailing list archive at Nabble.com. -- Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org
Is it possible to invoke the same ws from intranet and internet?
I am lost. Is it possible to invoke the same webservice from intranet (port: 8080) or internet (public ip address:80)? And have automatically the right wsdl file? Is there any document that can help me? My configuration is: Axis2 1.4.1 over Tomcat (6.0) behind an Apache http server (2.02). Which are the parameters I must manage to have the same ws working automatically? 1) axis2.xml: parameter name=proxyPort80/parameter? 2) axis2.xml: parameter name=httpFrontendHostUrlhttp://xx.xx.xx.xx/ws_site/parameter? 3) httpd.conf: ProxyPassReverse /ws_site/ http://localhost:8080/ws_site ? 4) axis2.xml parameter name=hostnamehttp://xx..xx.xx.xx/ws_site/parameter ? 5) services.xml: useOriginalWSDL ? 6) services.xml: modifyUserWSDLPortAddress ? Thanks Marco
Re: Problem with two services in a serviceGroup with scope soapsession sharing ServiceGroupContext
I am new in AXIS2 and the problem is in this configuration:
- Two clases, in each class there is a service with operations to invoke.
- The first class(service Autenticacion) it is used to autenticate the
user in the application
- The second class(service Directorio) do a job, but it validates that
the user is autenticated
- I want a unique ServiceGroupContext where the first service
Autenticacion puts a valid sessionId if the user+password is valid.
- Then a new request to the second service Directorio gets from
ServiceGroupContext the sessionId
-- The problem is that there are two contexts!!! see the details..
Thanks
I have this service.xml configuration:
serviceGroup
service name=Autenticacion scope=soapsession
Description Servicio WEB de autenticacion/Description
parameter name=ServiceClass
locked=falsees.upv.wsasic.app.Autenticacion/parameter
messageReceivers
messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-only;
class=org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver /
messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-out;
class=org.apache.axis2.rpc.receivers.RPCMessageReceiver /
/messageReceivers
/service
service name=Directorio scope=soapsession
Description Servicio WEB de directorio/Description
parameter name=ServiceClass
locked=falsees.upv.wsasic.app.Directorio/parameter
messageReceivers
messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-only;
class=org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver /
messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-out;
class=org.apache.axis2.rpc.receivers.RPCMessageReceiver /
/messageReceivers
/service
module ref=addressing /
/serviceGroup
-- Continue ---
I have generated the Stubs from the WSDL :
wsdl2java.bat -uri Autenticacion.wsdl -p es.upv.wsasic.cliente -d adb -s
wsdl2java.bat -uri Directorio.wsdl -p es.upv.wsasic.cliente -d adb -s
Then i have incluided in both stubs constructors:
.
_serviceClient.engageModule(addressing);
_serviceClient.getOptions().setManageSession(true);
.
-Continue-
package es.upv.wsasic.cliente;
public class ClientAutenticacion {
public static void main(String[] args) {
String puntoFinalAutenticacion =
http://mymachine:8080/wsasic-app/services/Autenticacion;;
String puntoFinalDirectorio =
http://mymachine:8080/wsasic-app/services/Directorio;;
String modulos =
C:\\jupv\\ws_ganymedes\\wsasic-appClient\\WebContent\\WEB-INF;
String axis2xml =
C:\\jupv\\ws_ganymedes\\wsasic-appClient\\WebContent\\WEB-INF\\conf\\axis2.xml;
ConfigurationContext contextoConfiguracion;
contextoConfiguracion =
ConfigurationContextFactory.createConfigurationContextFromFileSystem(modulos,
axis2xml); AutenticacionStub
autenticacionStub = new
AutenticacionStub(contextoConfiguracion,puntoFinalAutenticacion);
byte[] sessionId;=
obtieneSessionId(autenticacionStub);
DirectorioStub directorioStub = new
DirectorioStub(contextoConfiguracion,puntoFinalDirectorio);
Person persona = getInfoPerson(directorioStub,new
String(Base64.encodeBase64(sessionId)),226805);
}
public static byte[] obtieneSessionId(AutenticacionStub stub) {
byte[] sessionId=null;
try {
AutenticacionStub.ObtieneSessionId req = new
AutenticacionStub.ObtieneSessionId();
req.setUsuario(user1);
req.setPassword(mypwd235);
AutenticacionStub.ObtieneSessionIdResponse res =
stub.obtieneSessionId(req); DataHandler
respuesta = res.get_return();
InputStream is = respuesta.getInputStream();
ByteArrayOutputStream baos = new ByteArrayOutputStream();
byte[] b= new byte[1024];
int num = is.read(b);
while (num 0) {
baos.write(b, 0, num);
num = is.read(b);
}
sessionId = baos.toByteArray(); } catch
(Exception e) {
e.printStackTrace();
}
return sessionId; }
public static Person getInfoPerson(DirectorioStub stub,String
sessionId,String dni){
try {
DirectorioStub.GetInfoPersonaBasica req = new
DirectorioStub.GetInfoPersonaBasica();
req.setSessionId(sessionId);
req.setDni(dni);
DirectorioStub.GetInfoPersonaBasicaResponse res =
stub.getInfoPersonaBasica(req);
Person persona = res.get_return();
return persona;
} catch
Re: AxisFault namespace mismatch require
Thank you for responding, Keith. I don't understand why it is resulting in an exception, since I have generated the wsdl using ant (Class org.apache.axis2.tool.ant.Java2WSDLTask). There were no changes made to the wsdl after it was generated by this tool. Please note I didn't use Eclipse here, everything is worked out using ant build script. To develop the client, I have used org.apache.axis2.wsdl.WSDL2Java class in ant to consume the wsdl generated from the above task. Again, client stub is generated by the ant build script. Now, here is an interesting thing. I developed the same web service using Eclipse as described in this URL http://www.eclipse.org/webtools/community/tutorials/BottomUpAxis2WebService/bu_tutorial.html Eclipse Axis2 Web Service . After the web service was up and running. I created the client using the same procedure as mentioned in my previous paragraph. And the result is, it works very fine. I compared the files between the two webservices, one using ant and other eclipse, everything is same between the two web services I developed, like the services.xml etc. Except, I guess, the way the wsdl is getting generated. Using ant build script, i am using class org.apache.axis2.tool.ant.Java2WSDLTask, whereas using Eclipse, eclipse is generating the wsdl on its own. Now, the client is the same for both web services, first web service doesn't work, whereas second, using eclipse, works for this client. I hope I am making sense. Keithgchapman wrote: The exception says it all... The server expects your request to be in the http://hello.axis2.com/xsd namespace but your request was in the http://hello.axis2.com http://hello.axis2.com/xsd namespace. If you fix this it would work. BTW how did you write your client? If you used wsdl2Java to generate a stub it would have handled this namespace issue. Thanks, Keith. On Wed, Apr 1, 2009 at 1:56 AM, bandrm rajivband...@gmail.com wrote: Hello, I developed a simple web service using predominantly ant build script. The web service is deployed in tomcat and it is working fine. I have generated wsdl using using ant tool (Class org.apache.axis2.tool.ant.Java2WSDLTask). I developed client and consumed this wsdl. Now, when I execute the client program, I get the following exception. This might be elementary, but would like to get it resolved. 485 ERROR org.apache.axis2.rpc.receivers.RPCMessageReceiver - Exception occurred while trying to invoke service method sayHello org.apache.axis2.AxisFault: namespace mismatch require http://hello.axis2.com/xsd found http://hello.axis2.com at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:103) at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:39) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:144) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:279) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:116) at javax.servlet.http.HttpServlet.service(HttpServlet.java:647) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:875) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689) at java.lang.Thread.run(Unknown Source) -- View this message in context: http://www.nabble.com/AxisFault-namespace-mismatch-require-tp22811514p22811514.html Sent from the Axis - User mailing list archive at Nabble.com. -- Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org -- View this message in context: http://www.nabble.com/AxisFault-namespace-mismatch-require-tp22811514p22831885.html Sent from the Axis - User mailing list archive at Nabble.com.
JAVA2WSDL -l option (HTTPS)
Hi, We are using apache axis 1.2 java2wsdl to generate the WSDL, when we specify java2wsdl -l http:\\url.. - WSDL is getting genrated with the specified port address - https://10.116.194.30:9101/servlet_jsp/axis2/services/XCDAuth?wsdl# wsdl:service name=xxx - https://10.116.194.30:9101/servlet_jsp/axis2/services/XCDAuth?wsdl# wsdl:port name=xxx binding=xxx soap12:address location=http://url http://url/ / /wsdl:port - https://10.116.194.30:9101/servlet_jsp/axis2/services/XCDAuth?wsdl# wsdl:port name=xxx binding=xxx http:address location=http://url/ / /wsdl:port - https://10.116.194.30:9101/servlet_jsp/axis2/services/XCDAuth?wsdl# wsdl:port name=xxx binding=xxx soap:address location=http://url/ / /wsdl:port /wsdl:service but when we give java2wsdl -l https:\\url - WSDL is getting generated but it doesnt have the port address and location info. hence we run the WSDL2JAVA - we are getting an error ERROR parsing WSDL. Any help on this would be appreciable. Thanks, Kumar. Please do not print this email unless it is absolutely necessary. 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 proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com
Services are not seen is there something Im doing wrong? please help
I look at /HappyAxis.jsp
It says all core jars are found and located
I have deployed StockQuoteService service as given in the examples
When I open http://localhost:8081/axis2-web/listService.jsp
It says There seems to be no services listed! Try hitting refresh
Also I keep getting
2009-04-01 12:30:58,891 [http-8081-Processor24] DEBUG
http.ApplicationXMLFormatter- end writeTo()
2009-04-01 12:30:58,891 [http-8081-Processor24] DEBUG transport.TransportUtils
- Did not find RequestResponseTransport cannot set response written
I look at the log4j and see the following log
2009-04-01 13:04:25,131 [main] INFO deployment.ServiceDeployer -
Deploying Web service: StockQuoteService.aar -
file:/D:/unifier/apps/ROOT/WEB-INF/services/StockQuoteService.aar
2009-04-01 13:04:25,131 [main] DEBUG util.Utils - Created
temporary file :
D:\unifier\work\Catalina\localhost\_\_axis2\axis24180version.aar
2009-04-01 13:04:25,146 [main] DEBUG util.StAXUtils -
XMLStreamReader is com.ctc.wstx.sr.ValidatingStreamReader
2009-04-01 13:04:25,146 [main] DEBUG builder.StAXOMBuilder - SPACE: [
]
2009-04-01 13:04:25,146 [main] DEBUG builder.StAXOMBuilder -
START_ELEMENT: service:service
2009-04-01 13:04:25,099 [main] DEBUG description.AxisService - Get
operation for getPrice
2009-04-01 13:04:25,099 [main] DEBUG description.AxisService - Target
namespace: http://quickstart.samples/
2009-04-01 13:04:25,099 [main] DEBUG description.AxisService -
Operations aliases map: {}
2009-04-01 13:04:25,099 [main] DEBUG description.AxisService - Imported
namespaces: null
2009-04-01 13:04:25,099 [main] DEBUG description.AxisService - Found
axis operation: null
2009-04-01 13:04:25,115 [main] DEBUG description.AxisService -
mapActionToOperation: Mapping Action to Operation: action: getPriceRequest;
operation: org.apache.axis2.description.inoutaxisoperat...@82674bnamed: getPrice
2009-04-01 13:04:25,115 [main] DEBUG description.AxisService -
mapActionToOperation: Mapping Action to Operation: action: getPriceResponse;
operation: org.apache.axis2.description.inoutaxisoperat...@82674bnamed: getPrice
2009-04-01 13:04:25,115 [main] DEBUG description.AxisService -
mapActionToOperation: Mapping Action to Operation: action: getPrice; operation:
org.apache.axis2.description.inoutaxisoperat...@82674bnamed: getPrice
2009-04-01 13:04:25,115 [main] DEBUG description.AxisService -
mapActionToOperation: Mapping Action to Operation: action: urn:getPrice;
operation: org.apache.axis2.description.inoutaxisoperat...@82674bnamed: getPrice
2009-04-01 13:04:25,115 [main] DEBUG description.AxisService - Get
operation for update
2009-04-01 13:04:25,115 [main] DEBUG description.AxisService - Target
namespace: http://quickstart.samples/
2009-04-01 13:04:25,115 [main] DEBUG description.AxisService -
Operations aliases map:
{urn:getprice=org.apache.axis2.description.inoutaxisoperat...@82674b,
getpriceresponse=org.apache.axis2.description.inoutaxisoperat...@82674b,
getprice=org.apache.axis2.description.inoutaxisoperat...@82674b,
getpricerequest=org.apache.axis2.description.inoutaxisoperat...@82674b}
2009-04-01 13:04:25,115 [main] DEBUG description.AxisService - Imported
namespaces: null
2009-04-01 13:04:25,115 [main] DEBUG description.AxisService - Found
axis operation: null
2009-04-01 13:04:25,115 [main] DEBUG description.AxisService -
mapActionToOperation: Mapping Action to Operation: action: updateRequest;
operation: org.apache.axis2.description.inonlyaxisoperat...@14b84c7named: update
2009-04-01 13:04:25,115 [main] DEBUG description.AxisService -
mapActionToOperation: Mapping Action to Operation: action: update; operation:
org.apache.axis2.description.inonlyaxisoperat...@14b84c7named: update
2009-04-01 13:04:25,115 [main] DEBUG description.AxisService -
mapActionToOperation: Mapping Action to Operation: action: urn:update;
operation: org.apache.axis2.description.inonlyaxisoperat...@14b84c7named: update
2009-04-01 13:04:25,131 [main] DEBUG description.AxisService - Get
operation for getPrice
2009-04-01 13:04:25,131 [main] DEBUG description.AxisService - Found
axis operation: org.apache.axis2.description.inoutaxisoperat...@82674b
2009-04-01 13:04:25,131 [main] DEBUG engine.Phase- Handler
MustUnderstandChecker added to Phase OperationInPhase
2009-04-01 13:04:25,131 [main] DEBUG description.AxisService -
mapActionToOperation: Mapping Action to Operation: action: getPriceRequest;
operation: org.apache.axis2.description.inoutaxisoperat...@82674bnamed: getPrice
2009-04-01 13:04:25,131 [main] DEBUG description.AxisService -
mapActionToOperation: This operation is already mapped to this action:
getPriceRequest; AxisOperation:
org.apache.axis2.description.inoutaxisoperat...@82674b named:
RE: Services are not seen is there something Im doing wrong? please help
the service.xml packaged inside your aar is not valid
unzip your .aar
locate service.xml contained within .aar
and validate service.xml with a XML Validator..e.g.
http://www.stg.brown.edu/service/xmlvalid
Martin
__
Disclaimer and confidentiality note
This message is confidential and may be privileged. If you are not the intended
recipient, we kindly ask you to please inform the sender. Any unauthorised
dissemination or copying hereof is prohibited. This message serves for
information purposes only and shall not have any legally binding effect. Given
that e-mails can easily be subject to manipulation, we can not accept any
liability for the content provided.
From: cyr...@skire.com
To: axis-user@ws.apache.org
Date: Wed, 1 Apr 2009 13:17:50 -0700
Subject: Services are not seen is there something Im doing wrong? please help
I look at /HappyAxis.jsp
It says all core jars are found and located
I have deployed StockQuoteService service as given in the
examples
When I open http://localhost:8081/axis2-web/listService.jsp
It says “There seems to be no services listed! Try
hitting refresh”
Also I keep getting
2009-04-01 12:30:58,891 [http-8081-Processor24] DEBUG
http.ApplicationXMLFormatter- end writeTo()
2009-04-01 12:30:58,891 [http-8081-Processor24] DEBUG
transport.TransportUtils- Did not
find RequestResponseTransport cannot set response written
I look at the log4j and see the following log
2009-04-01 13:04:25,131 [main] INFO
deployment.ServiceDeployer - Deploying Web
service: StockQuoteService.aar -
file:/D:/unifier/apps/ROOT/WEB-INF/services/StockQuoteService.aar
2009-04-01 13:04:25,131 [main] DEBUG util.Utils -
Created temporary file :
D:\unifier\work\Catalina\localhost\_\_axis2\axis24180version.aar
2009-04-01 13:04:25,146 [main] DEBUG
util.StAXUtils
- XMLStreamReader is com.ctc.wstx.sr.ValidatingStreamReader
2009-04-01 13:04:25,146 [main] DEBUG
builder.StAXOMBuilder
- SPACE: [
]
2009-04-01 13:04:25,146 [main] DEBUG builder.StAXOMBuilder
- START_ELEMENT: service:service
2009-04-01 13:04:25,099 [main] DEBUG
description.AxisService - Get
operation for getPrice
2009-04-01 13:04:25,099 [main] DEBUG
description.AxisService -
Target namespace: http://quickstart.samples/
2009-04-01 13:04:25,099 [main] DEBUG description.AxisService
- Operations aliases map: {}
2009-04-01 13:04:25,099 [main] DEBUG
description.AxisService -
Imported namespaces: null
2009-04-01 13:04:25,099 [main] DEBUG
description.AxisService - Found
axis operation: null
2009-04-01 13:04:25,115 [main] DEBUG
description.AxisService -
mapActionToOperation: Mapping Action to Operation: action: getPriceRequest;
operation: org.apache.axis2.description.inoutaxisoperat...@82674bnamed:
getPrice
2009-04-01 13:04:25,115 [main] DEBUG
description.AxisService -
mapActionToOperation: Mapping Action to Operation: action: getPriceResponse;
operation: org.apache.axis2.description.inoutaxisoperat...@82674bnamed:
getPrice
2009-04-01 13:04:25,115 [main] DEBUG description.AxisService
- mapActionToOperation: Mapping Action to Operation: action: getPrice;
operation: org.apache.axis2.description.inoutaxisoperat...@82674bnamed:
getPrice
2009-04-01 13:04:25,115 [main] DEBUG
description.AxisService -
mapActionToOperation: Mapping Action to Operation: action: urn:getPrice;
operation: org.apache.axis2.description.inoutaxisoperat...@82674bnamed:
getPrice
2009-04-01 13:04:25,115 [main] DEBUG
description.AxisService - Get
operation for update
2009-04-01 13:04:25,115 [main] DEBUG
description.AxisService -
Target namespace: http://quickstart.samples/
2009-04-01 13:04:25,115 [main] DEBUG
description.AxisService -
Operations aliases map:
{urn:getprice=org.apache.axis2.description.inoutaxisoperat...@82674b,
getpriceresponse=org.apache.axis2.description.inoutaxisoperat...@82674b,
getprice=org.apache.axis2.description.inoutaxisoperat...@82674b,
getpricerequest=org.apache.axis2.description.inoutaxisoperat...@82674b}
2009-04-01 13:04:25,115 [main] DEBUG
description.AxisService -
Imported namespaces: null
2009-04-01 13:04:25,115 [main] DEBUG
description.AxisService - Found
axis operation: null
2009-04-01 13:04:25,115 [main] DEBUG
description.AxisService -
mapActionToOperation: Mapping Action to Operation: action: updateRequest;
operation: org.apache.axis2.description.inonlyaxisoperat...@14b84c7named:
update
2009-04-01 13:04:25,115 [main] DEBUG
description.AxisService -
mapActionToOperation: Mapping Action to Operation: action: update; operation:
org.apache.axis2.description.inonlyaxisoperat...@14b84c7named: update
2009-04-01 13:04:25,115 [main] DEBUG
description.AxisService -
mapActionToOperation: Mapping Action to Operation: action:
Adding Axis2 service to existing web application.
I have a working web application and want to add an axis2 service to it. The aar file I have been testing with is a simple java class with a public method which echos a string. The service is tested and worked in axis2 standalone server and when axis2 is a web application in Tomcat (axis2.war). But I cannot get it to work when trying to add the service only through my web application. I have added the aar file to the folder myApp.war/WEB-INF/services/ It contains: net/ HelloEcho.class META-INF/ MANIFEST services.xml zzz.wsdl The wsdl is auto-made by java2wsdl and the aar file is made by the service archiver codegen in eclipse. I read in an article (http://www.developer.com/open/article.php/10930_3777111_2) that it could be done by adding the text written at the bottom to the web.xml file in my war which I did. I also added a dependency for axis2 (see below). It deploys without error and the original web application works, but I cannot get the service to work. I get the error mentioned at the bottom when trying to type in http://localhost:8080/myAppl/services/zzz?wsdl . Actually I get this not matter what I write behind the services/ . But zzz is the name of the service and what I wrote in the axis2 servers so I guess the error has to do with axis2 not being properly configured? The article in the link above mentions axis2.xml in a conf/ folder in the WEB-INF, but doesn't say where it is from or what it contains.. Do I have to add more dependencies to maven or more in the web.xml file? Anything I have forgotten or is there an easier way to do what I want? -Az. Web.xml: servlet servlet-nameAxisServlet/servlet-name display-nameApache-Axis Servlet/display-name servlet-class org.apache.axis2.transport.http.AxisServlet /servlet-class load-on-startup1/load-on-startup /servlet servlet-mapping servlet-nameAxisServlet/servlet-name url-pattern/services/*/url-pattern /servlet-mapping--Pom.xml:dependency groupIdorg.apache.axis2/groupId artifactIdaxis2/artifactId version1.4.1/version /dependency-Error when trying to check if service is deployed/working:javax.servlet.ServletException: Servlet.init() for servlet AxisServlet threw exception org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845) org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) java.lang.Thread.run(Thread.java:619) root cause java.lang.NoClassDefFoundError: javax/wsdl/xml/WSDLLocator org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:516) org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:436) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845) org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) java.lang.Thread.run(Thread.java:619) root cause java.lang.ClassNotFoundException: javax.wsdl.xml.WSDLLocator org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1387) org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1233) java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:516) org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:436) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845) org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) java.lang.Thread.run(Thread.java:619) _ Ditt liv. Dine ting. Alt på ett sted med Windows Live™. http://windowslive.no
Line breaks in SOAP response when recombining MTOM+XOP
Hi, I've run into an interesting problem with MTOM response handling. Not sure if this is a bug or intended functionality to keep schema compliance (not an expert in MTOM+XOP). Currently using Axis2 v1.4.1 and Axiom v1.2.7. The service I'm calling is returning responses as SOAP/MTOM+XOP, but the SOAP is pretty-printed (kind of, mainly line breaks between elements). The problem I'm running into is with the recombination of the XOP parts into the XML (base64binary fields). The MTOM builder keeps the line breaks between Document and Include intact after building, even though it seems to be a proper XML element hierarchy. See the following snippet from the SOAP payload: Document Include xmlns=http://www.w3.org/2004/08/xop/include; href=cid:urn:uuid: 56443C4239C2E4EC851238526572016/ /Document It finds the attachment(s) without problem. But, when I call getChildren() on the Document element, I get three OMText nodes: 1) OMText: \n 2) OMText: The optimized node containing the binary data and Datahandler 3) OMText: \n and when I call serialize and print, the line breaks remain: Document [base64-encoded text] /Document Please let me know if this should be directed to the AXIOM folks instead. Thanks, -Matt
Needs help with ServiceLifeCycle
Hi Everyone I work in a team that is creating a new web service using jax-ws. Our SOAP interface is defined using a wsdl file. We generate code from our wsdl using wsimport under maven. Initial attempt failed at using the aar archive format, so we got success packaging our web service as a jar file. This file is deployed in the WEB-INF/servicejars directory of axis2. Axis2 1.4.1, runs inside tomcat 5.5. We are using Java 1.5. These versions are dictated by the deployment environment. The deployment under servicejars does not require a services.xml. I did some searching and found out I could get initialization code called by specifying a class that implement ServiceLifeCycle in the services.xml file. (The LifeCycle interface does not seem adequate for our need) Something like: service name=MyService class=x.y.MyInitializer... Initial testing seems to indicate that the services.xml is ignored if the service is deployed in servicejars directory. The entry class for our service is properly annotated with @WebService... Question1: Is there a way to get x.y.MyInitializer called at deployment time, for a web service deployed in servicejars? - - - - - - Alternatively I'm currently trying to use the aar format and deploy under WEB-INF/services I found a few things. - The wsdl file that we specify in our service class implementation using: @WebService(...wsdlLocation = META-INF/wsdl/myWSDL.wsdl is ignored. I suspect that the wsdlLocation attribute is not used when deployed as a aar file. - I renamed my wsdl file service.wsdl and moved it to META-INF/service.wsdl Now axis2 is reading it. I was surprised to see that the wsdl name was hard-coded, but a page found on the web indicated this constraint. - My next fight is defining the messageReceivers in the services.xml I'm only starting to explore this area, I need to do more homework. What I know although is that when I made a small web service prototype and used axis2 wsdl2java, I ended up with files like xxxServiceMessageReceiverInOut that could be used as messageReceivers. wsimport does not generate these files. Question 2: Is there some predefined messageReceivers that I should use when deploying a jaxws-based web service? Thank you for your help Alain - Alain Drolet email: adro...@nortel.com
Re: Line breaks in SOAP response when recombining MTOM+XOP
Matt, If my interpretation of the specs [1] is correct, then your service doesn't return a valid XOP package (see points 3 and 4 in section 3.1). Andreas [1] http://www.w3.org/TR/xop10/ On Wed, Apr 1, 2009 at 23:32, Matthew Davis gazat...@gmail.com wrote: Hi, I've run into an interesting problem with MTOM response handling. Not sure if this is a bug or intended functionality to keep schema compliance (not an expert in MTOM+XOP). Currently using Axis2 v1.4.1 and Axiom v1.2.7. The service I'm calling is returning responses as SOAP/MTOM+XOP, but the SOAP is pretty-printed (kind of, mainly line breaks between elements). The problem I'm running into is with the recombination of the XOP parts into the XML (base64binary fields). The MTOM builder keeps the line breaks between Document and Include intact after building, even though it seems to be a proper XML element hierarchy. See the following snippet from the SOAP payload: Document Include xmlns=http://www.w3.org/2004/08/xop/include; href=cid:urn:uuid: 56443C4239C2E4EC851238526572016/ /Document It finds the attachment(s) without problem. But, when I call getChildren() on the Document element, I get three OMText nodes: 1) OMText: \n 2) OMText: The optimized node containing the binary data and Datahandler 3) OMText: \n and when I call serialize and print, the line breaks remain: Document [base64-encoded text] /Document Please let me know if this should be directed to the AXIOM folks instead. Thanks, -Matt
Re: Adding Axis2 service to existing web application.
On Wed, Apr 1, 2009 at 6:13 PM, Azazel Se azazel...@hotmail.com wrote: java.lang.ClassNotFoundException: javax.wsdl.xml.WSDLLocator You need that class, the wsdl4j jar that was released with axis2 should contain one. Try putting that jar in WEB-INF/lib . - R
Re: Line breaks in SOAP response when recombining MTOM+XOP
Andreas, Thank you for the quick reply. It's actually point 5 of section 3.1 that motivated my original email. It seems to indicate that xop:Include is a serialized element in the XML Infoset, not text under the ns:Document element (thus white spaces between ns:Document and xop:Include should be ignored by the parser). I agree the base64binary form should contain no preceding or trailing white spaces on the ns:Document text. If the SOAP response contains this: DocumentInclude xmlns=http://www.w3.org/2004/08/xop/include; href=cid:urn:uuid:56443C4239C2E4EC851238526572016//Document Then I only see one child under ns:Document and the serialized form is correct. Unfortunately this isn't my service, I'm just a consumer of it. Thanks, -Matt On Wed, Apr 1, 2009 at 2:54 PM, Andreas Veithen andreas.veit...@gmail.comwrote: Matt, If my interpretation of the specs [1] is correct, then your service doesn't return a valid XOP package (see points 3 and 4 in section 3.1). Andreas [1] http://www.w3.org/TR/xop10/ On Wed, Apr 1, 2009 at 23:32, Matthew Davis gazat...@gmail.com wrote: Hi, I've run into an interesting problem with MTOM response handling. Not sure if this is a bug or intended functionality to keep schema compliance (not an expert in MTOM+XOP). Currently using Axis2 v1.4.1 and Axiom v1.2.7. The service I'm calling is returning responses as SOAP/MTOM+XOP, but the SOAP is pretty-printed (kind of, mainly line breaks between elements). The problem I'm running into is with the recombination of the XOP parts into the XML (base64binary fields). The MTOM builder keeps the line breaks between Document and Include intact after building, even though it seems to be a proper XML element hierarchy. See the following snippet from the SOAP payload: Document Include xmlns=http://www.w3.org/2004/08/xop/include; href=cid:urn:uuid: 56443C4239C2E4EC851238526572016/ /Document It finds the attachment(s) without problem. But, when I call getChildren() on the Document element, I get three OMText nodes: 1) OMText: \n 2) OMText: The optimized node containing the binary data and Datahandler 3) OMText: \n and when I call serialize and print, the line breaks remain: Document [base64-encoded text] /Document Please let me know if this should be directed to the AXIOM folks instead. Thanks, -Matt
RE: Adding Axis2 service to existing web application.
Date: Wed, 1 Apr 2009 19:09:23 -0300 Subject: Re: Adding Axis2 service to existing web application. From: robertlazar...@gmail.com To: axis-user@ws.apache.org On Wed, Apr 1, 2009 at 6:13 PM, Azazel Se azazel...@hotmail.com wrote: java.lang.ClassNotFoundException: javax.wsdl.xml.WSDLLocator You need that class, the wsdl4j jar that was released with axis2 should contain one. Try putting that jar in WEB-INF/lib . - R Thanks. :) As mentioned in my mail I added the entire axis2 lib to the maven pom.xml file and thought this was enough. But as I added the jar file you mentioned to the lib I got another axis2 classnotfoundexception so I manually added all the jars to the war file and then it worked. I am new to maven, why isn't it enough to add the jars to the pom and thereby the Maven Dependencies folder/library? I thought this was the purpose for dependency, that it everything is copied when using for instance maven package? -Az. _ Windows Live™ Mail. Flere kontoer på ett sted. http://download.live.com/wlmail
Re: Line breaks in SOAP response when recombining MTOM+XOP
Whitespace is never ignored by the parser: An XML processor must always pass all characters in a document that are not markup through to the application. A validating XML processor must also inform the application which of these characters constitute white space appearing in element content. Andreas On Thu, Apr 2, 2009 at 00:15, Matthew Davis gazat...@gmail.com wrote: Andreas, Thank you for the quick reply. It's actually point 5 of section 3.1 that motivated my original email. It seems to indicate that xop:Include is a serialized element in the XML Infoset, not text under the ns:Document element (thus white spaces between ns:Document and xop:Include should be ignored by the parser). I agree the base64binary form should contain no preceding or trailing white spaces on the ns:Document text. If the SOAP response contains this: DocumentInclude xmlns=http://www.w3.org/2004/08/xop/include; href=cid:urn:uuid:56443C4239C2E4EC851238526572016//Document Then I only see one child under ns:Document and the serialized form is correct. Unfortunately this isn't my service, I'm just a consumer of it. Thanks, -Matt On Wed, Apr 1, 2009 at 2:54 PM, Andreas Veithen andreas.veit...@gmail.com wrote: Matt, If my interpretation of the specs [1] is correct, then your service doesn't return a valid XOP package (see points 3 and 4 in section 3.1). Andreas [1] http://www.w3.org/TR/xop10/ On Wed, Apr 1, 2009 at 23:32, Matthew Davis gazat...@gmail.com wrote: Hi, I've run into an interesting problem with MTOM response handling. Not sure if this is a bug or intended functionality to keep schema compliance (not an expert in MTOM+XOP). Currently using Axis2 v1.4.1 and Axiom v1.2.7. The service I'm calling is returning responses as SOAP/MTOM+XOP, but the SOAP is pretty-printed (kind of, mainly line breaks between elements). The problem I'm running into is with the recombination of the XOP parts into the XML (base64binary fields). The MTOM builder keeps the line breaks between Document and Include intact after building, even though it seems to be a proper XML element hierarchy. See the following snippet from the SOAP payload: Document Include xmlns=http://www.w3.org/2004/08/xop/include; href=cid:urn:uuid: 56443C4239C2E4EC851238526572016/ /Document It finds the attachment(s) without problem. But, when I call getChildren() on the Document element, I get three OMText nodes: 1) OMText: \n 2) OMText: The optimized node containing the binary data and Datahandler 3) OMText: \n and when I call serialize and print, the line breaks remain: Document [base64-encoded text] /Document Please let me know if this should be directed to the AXIOM folks instead. Thanks, -Matt
Re: Line breaks in SOAP response when recombining MTOM+XOP
Andreas, Thanks for your response. I get your point. Will just write a workaround. Thanks again On Wed, Apr 1, 2009 at 3:51 PM, Andreas Veithen andreas.veit...@gmail.comwrote: Whitespace is never ignored by the parser: An XML processor must always pass all characters in a document that are not markup through to the application. A validating XML processor must also inform the application which of these characters constitute white space appearing in element content. Andreas On Thu, Apr 2, 2009 at 00:15, Matthew Davis gazat...@gmail.com wrote: Andreas, Thank you for the quick reply. It's actually point 5 of section 3.1 that motivated my original email. It seems to indicate that xop:Include is a serialized element in the XML Infoset, not text under the ns:Document element (thus white spaces between ns:Document and xop:Include should be ignored by the parser). I agree the base64binary form should contain no preceding or trailing white spaces on the ns:Document text. If the SOAP response contains this: DocumentInclude xmlns=http://www.w3.org/2004/08/xop/include; href=cid:urn:uuid:56443C4239C2E4EC851238526572016//Document Then I only see one child under ns:Document and the serialized form is correct. Unfortunately this isn't my service, I'm just a consumer of it. Thanks, -Matt On Wed, Apr 1, 2009 at 2:54 PM, Andreas Veithen andreas.veit...@gmail.com wrote: Matt, If my interpretation of the specs [1] is correct, then your service doesn't return a valid XOP package (see points 3 and 4 in section 3.1). Andreas [1] http://www.w3.org/TR/xop10/ On Wed, Apr 1, 2009 at 23:32, Matthew Davis gazat...@gmail.com wrote: Hi, I've run into an interesting problem with MTOM response handling. Not sure if this is a bug or intended functionality to keep schema compliance (not an expert in MTOM+XOP). Currently using Axis2 v1.4.1 and Axiom v1.2.7. The service I'm calling is returning responses as SOAP/MTOM+XOP, but the SOAP is pretty-printed (kind of, mainly line breaks between elements). The problem I'm running into is with the recombination of the XOP parts into the XML (base64binary fields). The MTOM builder keeps the line breaks between Document and Include intact after building, even though it seems to be a proper XML element hierarchy. See the following snippet from the SOAP payload: Document Include xmlns=http://www.w3.org/2004/08/xop/include; href=cid:urn:uuid: 56443C4239C2E4EC851238526572016/ /Document It finds the attachment(s) without problem. But, when I call getChildren() on the Document element, I get three OMText nodes: 1) OMText: \n 2) OMText: The optimized node containing the binary data and Datahandler 3) OMText: \n and when I call serialize and print, the line breaks remain: Document [base64-encoded text] /Document Please let me know if this should be directed to the AXIOM folks instead. Thanks, -Matt
Services and Group services last problem is http 500 problem before axis2 is up
Sorry for one more item, I do not know how to reply to the message!. After going thru the log and configuring the servlet, I found that the service cannot be seen under services, but can be seen under service groups. I see the following List Single service StockQuoteService Service EPR : http://localhost:8081/services/StockQuoteService Service REST epr :http://localhost:8081/rest/StockQuoteService Service Description : StockQuoteService Service Status : Active Available operations getPrice update even the wsdl generation is correct. Only issue is But when I do a http://localhost:8081/services/StockQuoteService it says http 500http://localhost:8081/services/StockQuoteService%20it%20says%20http%20500 And the log shows 2009-04-01 16:41:08,189 DEBUG util.StAXUtils - XMLStreamWriter is com.ctc.wstx.sw.SimpleNsStreamWriter 2009-04-01 16:41:08,205 DEBUG http.ApplicationXMLFormatter - end writeTo() 2009-04-01 16:41:08,205 DEBUG transport.TransportUtils - Did not find RequestResponseTransport cannot set response written Why is this occurring??
RE: Adding Axis2 service to existing web application.
pls download wsdl4j.jar into WEB-INF/lib http://www.java2s.com/Code/Jar/AXIS2/Downloadwsdl4j162jar.htm Martin __ Disclaimer and confidentiality note This message is confidential and may be privileged. If you are not the intended recipient, we kindly ask you to please inform the sender. Any unauthorised dissemination or copying hereof is prohibited. This message serves for information purposes only and shall not have any legally binding effect. Given that e-mails can easily be subject to manipulation, we can not accept any liability for the content provided. From: azazel...@hotmail.com To: axis-user@ws.apache.org Subject: Adding Axis2 service to existing web application. Date: Wed, 1 Apr 2009 21:13:24 + I have a working web application and want to add an axis2 service to it. The aar file I have been testing with is a simple java class with a public method which echos a string. The service is tested and worked in axis2 standalone server and when axis2 is a web application in Tomcat (axis2.war). But I cannot get it to work when trying to add the service only through my web application. I have added the aar file to the folder myApp.war/WEB-INF/services/ It contains: net/ HelloEcho.class META-INF/ MANIFEST services.xml zzz.wsdl The wsdl is auto-made by java2wsdl and the aar file is made by the service archiver codegen in eclipse. I read in an article (http://www.developer.com/open/article.php/10930_3777111_2) that it could be done by adding the text written at the bottom to the web.xml file in my war which I did. I also added a dependency for axis2 (see below). It deploys without error and the original web application works, but I cannot get the service to work. I get the error mentioned at the bottom when trying to type in http://localhost:8080/myAppl/services/zzz?wsdl . Actually I get this not matter what I write behind the services/ . But zzz is the name of the service and what I wrote in the axis2 servers so I guess the error has to do with axis2 not being properly configured? The article in the link above mentions axis2.xml in a conf/ folder in the WEB-INF, but doesn't say where it is from or what it contains.. Do I have to add more dependencies to maven or more in the web.xml file? Anything I have forgotten or is there an easier way to do what I want? -Az. Web.xml: servlet servlet-nameAxisServlet/servlet-name display-nameApache-Axis Servlet/display-name servlet-class org.apache.axis2.transport.http.AxisServlet /servlet-class load-on-startup1/load-on-startup /servlet servlet-mapping servlet-nameAxisServlet/servlet-name url-pattern/services/*/url-pattern /servlet-mapping--Pom.xml:dependency groupIdorg.apache.axis2/groupId artifactIdaxis2/artifactId version1.4.1/version /dependency-Error when trying to check if service is deployed/working:javax.servlet.ServletException: Servlet.init() for servlet AxisServlet threw exception org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845) org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) java.lang.Thread.run(Thread.java:619) root cause java.lang.NoClassDefFoundError: javax/wsdl/xml/WSDLLocator org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:516) org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:436) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845) org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) java.lang.Thread.run(Thread.java:619) root cause java.lang.ClassNotFoundException: javax.wsdl.xml.WSDLLocator org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1387) org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1233) java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:516) org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:436) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
