Re: FW: Axis2 Webservice wsdl version
Hi, I don't use Weblogic but have seen this error. Perhaps there is some error in your original wsdl, or it references an XML schema file that the server is not able to get. PeterRajesh wrote: > > > > >> Hi, >> >> After deployed the Axis2 webservice (.aar file) in Weblogic, clicked >> the wsdl url for example, >> http://localhost:7001/axis2/services/ABCProcessingService?wsdl and got >> the below error >> >> >> Unable to generate WSDL 1.1 for this >> service >> If you wish Axis2 to automatically generate the WSDL 1.1, then >> please +set useOriginalwsdl as false in your services.xml >> >> >> But if I mention the wsdl version as wsdl2.0 as below, I can see the >> wsdl displayed. >> >> http://localhost:7001/axis2/services/ABCProcessingService?wsdl=wsdl2.0 >> >> >> Please let me know what I need to do to display the wsdl without >> mentioning the version wsdl2.0 >> >> Thanks & Regards, >> >> Peter Rajesh >> >> > > > * > This communication, including attachments, is > for the exclusive use of addressee and may contain proprietary, > confidential and/or privileged information. If you are not the intended > recipient, any use, copying, disclosure, dissemination or distribution is > strictly prohibited. If you are not the intended recipient, please notify > the sender immediately by return e-mail, delete this communication and > destroy all copies. > * > > > -- View this message in context: http://www.nabble.com/FW%3A-Axis2-Webservice-wsdl-version-tp20116806p20141280.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Very confused about NTLM Story
Hi all I'm fighting against a WS running .net. The WS uses NTML Authentication. Now, I started to implement an java AXIS 2 1.4.1 CLIENT and tried to connect to this WS! I read a lot, I mean A LOT, but didn't find out how this mechanism works. I everytime get a 401. I found many solutions and promised fixes inside the mail archive. And all the time they are talking about some magic java constants called HTTPConstants.NTML_AUTHENTICATE and other constants which are not real! I had a look into the sources. Didn't found anything about. But at the same time at the newest javadoc those constants are described! So.. I am very snoopy about a solution? Are there any serious examples about how to connect to NTLM authenticated WS? I'm very thankful for any advise. best regards norbert
Re: Rampart one way only
Ok I added an axis2.xml file in my repo, however commenting out any Security phase causes errors indicating that the Security phase is missing. I'm wondering if you would ALSO have to remove any phase info from the modules.xml file in the rampart mar? In this case I'm the client, but receiving a response. Wouldn't I want to remove the security phase from the InFlow not out? Chris82KS wrote: > > Hello, > inside the axis2.xml you have the different flows (inFlow, OutFlow, > InFault and OutFault). Just remove the phase "Security" from the OutFlow > and the OutFaultFlow. > > Greetings > Christian > > > - original Nachricht > > Betreff: Rampart one way only > Gesendet: Do, 23. Okt 2008 > Von: RonnieMJ<[EMAIL PROTECTED]> > >> >> Is it possible to have rampart NOT be concerned with security on a return >> message in a synchronous transaction? >> >> Example: >> I send to server X with security headers. They return an OK message or a >> fault. Neither of which would have security heading information. >> -- >> View this message in context: >> http://www.nabble.com/Rampart-one-way-only-tp20133511p20133511.html >> Sent from the Axis - User mailing list archive at Nabble.com. >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --- original Nachricht Ende > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Rampart-one-way-only-tp20133511p20137306.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Rampart one way only
What if you're using a policy.xml file? I haven't been using a custom axis2 file. I wasn't sure if I needed to with using Policies. Chris82KS wrote: > > Hello, > inside the axis2.xml you have the different flows (inFlow, OutFlow, > InFault and OutFault). Just remove the phase "Security" from the OutFlow > and the OutFaultFlow. > > Greetings > Christian > > > - original Nachricht > > Betreff: Rampart one way only > Gesendet: Do, 23. Okt 2008 > Von: RonnieMJ<[EMAIL PROTECTED]> > >> >> Is it possible to have rampart NOT be concerned with security on a return >> message in a synchronous transaction? >> >> Example: >> I send to server X with security headers. They return an OK message or a >> fault. Neither of which would have security heading information. >> -- >> View this message in context: >> http://www.nabble.com/Rampart-one-way-only-tp20133511p20133511.html >> Sent from the Axis - User mailing list archive at Nabble.com. >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --- original Nachricht Ende > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Rampart-one-way-only-tp20133511p20136376.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
attachments directry and security policy issue
hi - i am getting the below exception while starting my web-app. it ran fine on my dev env but getting the below err while starting my app in PROD. I dont have the write policies enabled in production, so my only option is to tell Axis somehow skip this step...any help will be really appreciated...thank uservlet AxisServlet threw exceptioncom.sun.enterprise.web.connector.httpservice.HttpServiceProcessor.process(HttpServiceProcessor.java:234)com.sun.enterprise.web.HttpServiceWebContainer.service(HttpServiceWebContainer.java:2160)root cause java.security.AccessControlException: access denied (java.io.FilePermission /var/opt/SUNWappserver/nodeagents/sdlc104/IC/applications/j2ee-apps/ic-ear-4/interaction-war-4_0-RC2_war/WEB-INF/attachments write)java.security.AccessControlContext.checkPermission(AccessControlContext.java:264)java.security.AccessController.checkPermission(AccessController.java:427)java.lang.SecurityManager.checkPermission(SecurityManager.java:532)java.lang.SecurityManager.checkWrite(SecurityManager.java:962)java.io.File.mkdir(File.java:1119)java.io.File.mkdirs(File.java:1148)org.apache.axis.server.DefaultAxisServerFactory.getServer(DefaultAxisServerFactory.java:89)org.apache.axis.server.AxisServer.getServer(AxisServer.java:73)org.apache.axis.transport.http.AxisServletBase.getEngine(AxisServletBase.java:185)org.apache.axis.transport.http.AxisServletBase.getOption(AxisServletBase.java:396)org.apache.axis.transport.http.AxisServletBase.init(AxisServletBase.java:112)org.apache.axis.transport.http.AxisServlet.init(AxisServlet.java:156)javax.servlet.GenericServlet.init(GenericServlet.java:261)sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)java.lang.reflect.Method.invoke(Method.java:585)org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:249)java.security.AccessController.doPrivileged(Native Method)javax.security.auth.Subject.doAsPrivileged(Subject.java:517)org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:282)org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:165)org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:118)com.sun.enterprise.web.connector.httpservice.HttpServiceProcessor.process(HttpServiceProcessor.java:234)com.sun.enterprise.web.HttpServiceWebContainer.service(HttpServiceWebContainer.java:2160)This message contains information from Equifax Inc. which may be confidential and privileged. If you are not an intended recipient, please refrain from any disclosure, copying, distribution or use of this information and note that such actions are prohibited. If you have received this transmission in error, please notify by e-mail [EMAIL PROTECTED]
Re: [Axis2] - too many services in one servicegroup???
Nope there is no such limitation. Anyway it is interesting to investigate the problem you are facing so could you please create a JIRA and attach your service aar file? -Deepal Jan Verstuyft wrote: > Hi, > > I've received the following error when I've added another service to > the servicegroup, there were 18 services in the group. Are there any > limitation in the amount of services for one group? Is there > something we can do about? > > I'm using axis2 1.3 > > org.apache.axis2.deployment.DeploymentException: The following error > occurred during schema generation: 3 > at > org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:144) > at > org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:78) > at > org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:137) > at > org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:571) > at > org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:141) > at > org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:318) > at > org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:220) > at > org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:118) > at > org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:272) > at > org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:78) > at > org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:500) > at > org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:420) > at > weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:1070) > at > weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317) > at > weblogic.security.service.SecurityManager.runAs(SecurityManager.java:97) > at > weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:893) > at > weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:842) > at > weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:782) > at > weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3191) > at > weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3148) > at > weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3134) > at > weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3109) > at > weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletContext.java:5559) > at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:853) > at > weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2012) > at > weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2053) > at > weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2558) > at > weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2483) > at > weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2308) > at > weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDeployer.java:2390) > at > weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.java:2302) > at > weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2455) > at > weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:829) > at > weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:538) > at > weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:496) > at > weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25) > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178) > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151) > Caused by: org.apache.axis2.deployment.DeploymentException: The > following error occurred during schema generation: 3 > at > org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:106) > at > org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:103) > at > org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:137) > ... 37 more > Caused by: org.apache.axis
Re: Rampart one way only
Hello, inside the axis2.xml you have the different flows (inFlow, OutFlow, InFault and OutFault). Just remove the phase "Security" from the OutFlow and the OutFaultFlow. Greetings Christian - original Nachricht Betreff: Rampart one way only Gesendet: Do, 23. Okt 2008 Von: RonnieMJ<[EMAIL PROTECTED]> > > Is it possible to have rampart NOT be concerned with security on a return > message in a synchronous transaction? > > Example: > I send to server X with security headers. They return an OK message or a > fault. Neither of which would have security heading information. > -- > View this message in context: > http://www.nabble.com/Rampart-one-way-only-tp20133511p20133511.html > Sent from the Axis - User mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --- original Nachricht Ende - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Rampart one way only
Is it possible to have rampart NOT be concerned with security on a return message in a synchronous transaction? Example: I send to server X with security headers. They return an OK message or a fault. Neither of which would have security heading information. -- View this message in context: http://www.nabble.com/Rampart-one-way-only-tp20133511p20133511.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: mustUnderstand attribute not declared
You might try posting the SOAP message. From your post I can't tell if it's an addressing section or security related. Karl Moss wrote: > > Just a little more information: > > I have tried both Axis2 versions 1.3 and 1.4 and get the same error > message. > > Karl. > > -Original Message- > From: Karl Moss [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 22, 2008 2:11 PM > To: axis-user@ws.apache.org > Subject: mustUnderstand attribute not declared > > I'm somewhat new to Axis2 and running into a problem. I'm using the > Exchange Web Services wsdl and attempting to invoke a method on the stub. > I appear to be authenticating fine, but am getting the exception: > > org.apache.axis2.AxisFault: The request failed schema validation: The > 'http://schemas.xmlsoap.org/soap/envelope/:mustUnderstand' attribute is > not declared. > > I've tried to set the ADD_MUST_UNDERSTAND_TO_ADDRESSING_HEADERS to my > MessageContext properties, but no luck. > > Any ideas? > > Thanks, > > Karl. > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/mustUnderstand-attribute-not-declared-tp20116637p20133355.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: mustUnderstand attribute not declared
Just a little more information: I have tried both Axis2 versions 1.3 and 1.4 and get the same error message. Karl. -Original Message- From: Karl Moss [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 22, 2008 2:11 PM To: axis-user@ws.apache.org Subject: mustUnderstand attribute not declared I'm somewhat new to Axis2 and running into a problem. I'm using the Exchange Web Services wsdl and attempting to invoke a method on the stub. I appear to be authenticating fine, but am getting the exception: org.apache.axis2.AxisFault: The request failed schema validation: The 'http://schemas.xmlsoap.org/soap/envelope/:mustUnderstand' attribute is not declared. I've tried to set the ADD_MUST_UNDERSTAND_TO_ADDRESSING_HEADERS to my MessageContext properties, but no luck. Any ideas? Thanks, Karl. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
axis2 - jaxws - complex types
I am running axis2 inside of glassfish. I've got an axis2 web service running (built with NetBeans 6.1). It works great. I then add a WS client to my axis project and make a call from my axis2 ws to the jax-ws ws. If I call an operation that does not have complex types, it works great. However, if I try to call an operation that has complex types, it gives me the following error: com.sun.xml.ws.model.RuntimeModelerException: runtime modeler error: Wrapper class com.playground.Foo is not found. Have you run APT to generate them? at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:285) at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:596) When I look in my Axis2Test project's aar file, the generated classes are there (including Foo). I've tried copying Foo to Axis2 WebInf/classes and to glassfish/domains/domain2/lib/classes. Neither seem to make a difference. The jax-ws web service that I am calling is correctly read and executed by soapui as well as can be consumed by a simple servlet, so I believe it's structure is right. Does anyone have any suggestions? Thanks in advance. -- View this message in context: http://www.nabble.com/axis2---jaxws---complex-types-tp20130884p20130884.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: difference in AxisFault handling in server between SOAP 11 and SOAP 12
Hi, Nandana
yes, AXIOM trunk fixed this issue.
thanks
-jason
Nandana Mihindukulasooriya wrote:
Hi Json,
Did you try using AXIOM trunk ? There was an issue in AXIOM which
created wrong structure for SOAP 1.1 fault, but it is now fixed in the
trunk. Please have a look at these two issues. [1], [2]
thanks,
nandana
[1] - https://issues.apache.org/jira/browse/WSCOMMONS-343
[2] - http://issues.apache.org/jira/browse/RAMPART-164
On Thu, Oct 23, 2008 at 12:36 PM, jason
zhang <[EMAIL PROTECTED]>
wrote:
Hi
I use AXIOM style client code to invoke service. My service is
implemented using generated stub. It uses policy for security. To test
the fault handling, my server code always throws AxisFault.
If the client code has this line:
"options.setSoapVersionURI(org.apache.axiom.soap.SOAP12Constants.SOAP_ENVELOPE_NAMESPACE_URI);",
the AxisFault is reported back correctly to client. The response is
like this
HTTP/1.1 500 Internal Server Error
Server: Apache-Coyote/1.1
Content-Type: application/soap+xml; action=""true"
href="http://www.w3.org/2005/08/addressing/soap/fault" target="_blank">http://www.w3.org/2005/08/addressing/soap/fault";charset=UTF-8
Transfer-Encoding: chunked
Date: Thu, 23 Oct 2008 04:29:32 GMT
Connection: close
http://www.w3.org/2003/05/soap-envelope">http://schemas.xmlsoap.org/soap/envelope/">axis2ns5:Server
de
error
...
--
If the client code does not have that line, the message is sent to
server using SOAP 11 style,
The response is a HTTP error from tomcat.
-
HTTP/1.1 500 Internal Server Error
Server: Apache-Coyote/1.1
Content-Type: text/html;charset=utf-8
Content-Length: 1000
Date: Thu, 23 Oct 2008 04:30:06 GMT
Connection: close
Apache Tomcat/6.0.16 - Error
report...
HTTP Status 500 - type Status
reportmessage
description
The server encountered an internal error () that prevented it
from fulfilling this request.Apache
Tomcat/6.0.16
I traced the error to
org.apache.axiom.soap.impl.builder.SOAP11BuilderHelper line 151
private void processText(XMLStreamReader parser, OMElement value) {
try {
146 int token = parser.next();
147 while (token != XMLStreamReader.END_ELEMENT) {
148 if (token == XMLStreamReader.CHARACTERS) {
149 factory.createOMText(value, parser.getText());
150 } else {
151 throw new SOAPProcessingException(
"Only Characters are allowed here");
}
token = parser.next();
}
} catch (XMLStreamException e) {
throw new SOAPProcessingException(e);
}
}
When the error occurs, the value is an
org.apache.axiom.soap.impl.dom.soap11.SOAP11FaultCodeImpl element.
token is 1(StartElement).
Is this a bug or something wrong in my code?
thanks
-jason
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Nandana Mihindukulasooriya
WSO2 inc.
http://nandana83.blogspot.com/
http://www.wso2.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
axis 1.4 problems with php associative array
I have php SOAP service which returning php associative array, when I use axis
client I get strange result.
code:
call.setReturnClass(HashMap.class);
msg = (HashMap) call.invoke(new Object[] {});
for(Object o : msg.values()) {
System.out.println("obj " +o.getClass()+",
isHashMap="+o.getClass().isInstance(new HashMap()));
}
I get:
class [Ljava.util.HashMap;
Enyone know how to typecsat or how to set setReturnType for associative array?
Best Regard, Tomaz
begin:vcard
fn;quoted-printable:Toma=C5=BE Majerhold
n;quoted-printable:Majerhold;Toma=C5=BE
org:ARNES, Slovenian NREN;Development team
adr:;;Jamova 39;Ljubljana;;;Slovenia
title:Developer
tel;work:+386 1425 38 01
tel;fax:+386 1 479 88 99
url:http://www.arnes.si/
version:2.1
end:vcard
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] - too many services in one servicegroup???
Hi, I've received the following error when I've added another service to the servicegroup, there were 18 services in the group. Are there any limitation in the amount of services for one group? Is there something we can do about? I'm using axis2 1.3 org.apache.axis2.deployment.DeploymentException: The following error occurred during schema generation: 3 at org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:144) at org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:78) at org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:137) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:571) at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:141) at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:318) at org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:220) at org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:118) at org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:272) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:78) at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:500) at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:420) at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:1070) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:97) at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:893) at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:842) at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:782) at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3191) at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3148) at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3134) at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3109) at weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletContext.java:5559) at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:853) at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2012) at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2053) at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2558) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2483) at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2308) at weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDeployer.java:2390) at weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.java:2302) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2455) at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:829) at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:538) at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:496) at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151) Caused by: org.apache.axis2.deployment.DeploymentException: The following error occurred during schema generation: 3 at org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:106) at org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:103) at org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:137) ... 37 more Caused by: org.apache.axis2.deployment.DeploymentException: The following error occurred during schema generation: 3 at org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:389) at org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101) ... 39 more Caused by: org.apache.axis2.deployment.DeploymentException: The fol
Problem with content-length and chunking.
Hi, I have a problem with calling an external (another system, another network, another technology base) webservice. The external webservice seems to crash if it doesn't get the HTTP header content length. modern webservices seem to prefer chunked, but the external webservice crashes then. Luckily I can change to send the content-length header, by setting: options.setProperty(HTTPConstants.CHUNKED,"false"); The problem I then get is that Axis2 and Axis1 (I've tried both) doesn't gets a HTTP 200 answer without a body, but with a header saying that the body is chunked. I hereby suspect that Axis can't pick up the body, because I've turned off chunking? I know that the external service works, I've sucessfully invoked it via a home made java client and the firefox plugin poster. Is there a possibility to turn off chunking when sending request and support it when reading response? or am I on a wild goose chase? Thanks for any help. Tomas
Axis2 wsdl2java client: How to add processing instructions
Hi,
I am trying to implement a client with axis2 1.4.1 (REST) for a "legacy
webservice". This webservice is defined as just sending XML per HTTP
POST (x-www-form-urlencoded) and getting the answer message as a
supplement of the http response.
I generated a WSDL file according to the specification provided by the
webservice provider and created a client with wsdl2java (ADB). This is
working pretty fine, but i have two problems, i couldn't solve so far:
a) My requests are answered with an error message hinting towards two
missing processing instructions, at the beginnning of the request like
I found a mailthread(Need for Child API in OMDocument:
http://markmail.org/search/?q=axis2+%22Need+for+Child+API+in+OMDocument+
%22 ) that suggests a possibility, to add such instructions before the
transport, but i did not find a way to use this. Can anybody give me a
hint, how to do this or where to look further? Or is it possible to
declare such processing instructions already inside the WSDL?
b) the received http response of the webservice (containing the error
message in the XML supplement) is not recognized by axis2, though it
looks quite correct. The error message is
org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException:
Unexpected subelement EngineAnswer
I have not finally analyzed the exact reason by debugging through the
code, but I am affraid i will have to manipulate the http response in a
similar manner like the request, before it is handed over to the axis2
parsing. So, if anybody has a way to achieve this at his fingertips, his
help is appreciated very much!
I'm pretty new to axis ( and java as well ) so please forgive me, if
this is a BRTFM.
Thanks in advance for any hint and best regards
Martin Berns
P.S.: My actual configuration is:
AxisConfiguration axisConfig = new AxisConfiguration();
ConfigurationContext myConfigContext;
try {
myConfigContext =
ConfigurationContextFactory.createConfigurationContextFromFileSystem(nul
l , null);
} catch (AxisFault e1) {
// TODO Auto-generated catch block
e1.printStackTrace();
return;
}
myConfigContext.setProperty(Constants.Configuration.ENABLE_REST,
Constants.VALUE_TRUE);
myConfigContext.setProperty(Constants.Configuration.HTTP_METHOD ,
org.apache.axis2.Constants.Configuration.HTTP_METHOD_POST);
myConfigContext.setProperty(Constants.Configuration.DISABLE_SOAP_ACTION,
Constants.VALUE_TRUE);
myConfigContext.setProperty(Constants.Configuration.CONTENT_TYPE ,
HTTPConstants.MEDIA_TYPE_X_WWW_FORM);
myConfigContext.setProperty(org.apache.axis2.transport.http.HTTPConstant
s.CHUNKED, Boolean.FALSE);
org.apache.axis2.transport.http.HttpTransportProperties.ProxyProperties
proxy = new
org.apache.axis2.transport.http.HttpTransportProperties.ProxyProperties(
);
proxy.setProxyName(proxyName);
proxy.setProxyPort(8080);
myConfigContext.setProperty(HTTPConstants.PROXY , proxy);
myConfigContext.setProperty(HTTPConstants.PROTOCOL_VERSION ,
HTTPConstants.HEADER_PROTOCOL_10);
try {
myServiceStub myStub = new myServiceStub(myConfigContext,
myUrl);
...
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2]: Messages lost with JMS
Hi community, I use Axis2 (version 1.1.1) webservices with JMS in the following environment: * ActiveMQ as standalone JMS server * JBoss with the deployed Axis2 webservice as webserver I send SOAP messages to an ActiveMQ. The webservice processes the message and a response is generated. The response is sent to an ActiveMQ response queue. This works fine until the JBoss falls down for some reasons. In this case the message is lost because it was acknowledged after receiving (before it was processed and before the response was sent). When Axis2 initializes the JMS Listener a session in AUTOACKNOWLEDGE mode is created which is not transacted (hard coded). Therefore the message is acknowledged when it arrives at the message receiver. When the JBoss is killed in at this point the message can not be processed but it is already removed from the queue. I want to have the scenario that the message is acknowledged not until a response is sent to the response queue. Is there a possibility to configure the Axis2 in this way or is there a possibility to patch it? Regards Ines
Re: difference in AxisFault handling in server between SOAP 11 and SOAP 12
Hi Json,
Did you try using AXIOM trunk ? There was an issue in AXIOM which created
wrong structure for SOAP 1.1 fault, but it is now fixed in the trunk. Please
have a look at these two issues. [1], [2]
thanks,
nandana
[1] - https://issues.apache.org/jira/browse/WSCOMMONS-343
[2] - http://issues.apache.org/jira/browse/RAMPART-164
On Thu, Oct 23, 2008 at 12:36 PM, jason zhang <[EMAIL PROTECTED]>wrote:
> Hi
>
> I use AXIOM style client code to invoke service. My service is implemented
> using generated stub. It uses policy for security. To test the fault
> handling, my server code always throws AxisFault.
> If the client code has this line:
> "options.setSoapVersionURI(org.apache.axiom.soap.SOAP12Constants.SOAP_ENVELOPE_NAMESPACE_URI);",
> the AxisFault is reported back correctly to client. The response is like
> this
>
> HTTP/1.1 500 Internal Server Error
> Server: Apache-Coyote/1.1
> Content-Type: application/soap+xml; action="
> http://www.w3.org/2005/08/addressing/soap/fault";charset=UTF-8
> Transfer-Encoding: chunked
> Date: Thu, 23 Oct 2008 04:29:32 GMT
> Connection: close
>
> http://www.w3.org/2003/05/soap-envelope";> xmlns:axis2ns5="http://schemas.xmlsoap.org/soap/envelope/
> ">axis2ns5:Server
> de
> error
> ...
> --
> If the client code does not have that line, the message is sent to server
> using SOAP 11 style,
> The response is a HTTP error from tomcat.
> -
> HTTP/1.1 500 Internal Server Error
> Server: Apache-Coyote/1.1
> Content-Type: text/html;charset=utf-8
> Content-Length: 1000
> Date: Thu, 23 Oct 2008 04:30:06 GMT
> Connection: close
>
> Apache Tomcat/6.0.16 - Error
> report... HTTP Status 500 - size="1" noshade="noshade">type Status reportmessage
> description The server encountered an internal error
> () that prevented it from fulfilling this request. noshade="noshade">Apache Tomcat/6.0.16
>
>
> I traced the error to
> org.apache.axiom.soap.impl.builder.SOAP11BuilderHelper line 151
> private void processText(XMLStreamReader parser, OMElement value) {
> try {
> 146int token = parser.next();
> 147 while (token != XMLStreamReader.END_ELEMENT) {
> 148if (token == XMLStreamReader.CHARACTERS) {
> 149factory.createOMText(value, parser.getText());
> 150} else {
> 151throw new SOAPProcessingException(
> "Only Characters are allowed here");
> }
> token = parser.next();
> }
>
>
> } catch (XMLStreamException e) {
> throw new SOAPProcessingException(e);
> }
> }
>
> When the error occurs, the value is an
> org.apache.axiom.soap.impl.dom.soap11.SOAP11FaultCodeImpl element. token is
> 1(StartElement).
>
> Is this a bug or something wrong in my code?
>
> thanks
>
> -jason
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Nandana Mihindukulasooriya
WSO2 inc.
http://nandana83.blogspot.com/
http://www.wso2.org
