[jira] Created: (AXIS2C-328) unable to return custom SOAP faults
unable to return custom SOAP faults
---
Key: AXIS2C-328
URL: http://issues.apache.org/jira/browse/AXIS2C-328
Project: Axis2-C
Issue Type: Bug
Components: code generation, core/receivers, wsdl2c tool
Affects Versions: 0.93, Current (Nightly)
Reporter: Chris Darroch
Thanks, BTW, for the tcpmon tool -- very helpful!
I have a need to return custom SOAP fault messages from an Axis2/C server.
This turns out to require some patches in a few places. First, the code
generated by the w2c tool always calls a local on_fault handler, named
axis2_svc_skel_foo_on_fault() in the axis2_svc_skel_foo.c file. This function,
as generated by w2c, creates a fault element and returns it in the SOAP body.
Changing axis2_svc_skel_foo_on_fault() to simply return NULL instead allows the
axis2_raw_xml_in_out_msg_recv_invoke_business_logic_sync() function in
modules/core/receivers/raw_xml_in_out_msg_recv.c to recognize that no body
element
has been returned, and create a SOAP fault instead.
The actual business logic that one fills into the axis2_skel_foo.c file can
then simply
do the following:
axis2_skel_foo_Foo(...) {
AXIS2_ERROR_SET_STATUS_CODE(env-error, AXIS2_FAILURE);
AXIS2_ERROR_SET_ERROR_NUMBER(env-error,
AXIS2_ERROR_FOO);
return NULL;
}
This almost works, and
axis2_raw_xml_in_out_msg_recv_invoke_business_logic_sync()
now recognizes the fault condition and calls
axiom_soap_fault_create_default_fault()
to create the SOAP fault element. Good, except that it then returns
AXIS2_FAILURE,
so that its caller, axis2_raw_xml_in_out_msg_recv_receive_sync() in
modules/core/receivers/msg_recv.c, then does this:
status = AXIS2_MSG_RECV_INVOKE_IN_OUT_BUSINESS_LOGIC_SYNC(msg_recv, env,
msg_ctx, out_msg_ctx);
if(AXIS2_SUCCESS != status)
{
axis2_core_utils_reset_out_msg_ctx(env, out_msg_ctx);
AXIS2_MSG_CTX_FREE(out_msg_ctx, env);
return status;
}
which destroys the nice SOAP fault and returns an empty body element instead to
the client!
My current patch is to have
axis2_raw_xml_in_out_msg_recv_invoke_business_logic_sync() return
AXIS2C_SUCCESS instead -- this makes sense to me, because although an fault
condition has been detected, the function has successfully handled it by
creating
the SOAP fault element. Here's the patch:
--- modules/core/receivers/raw_xml_in_out_msg_recv.c.orig 2006-10-07
13:31:17.801951262 -0400
+++ modules/core/receivers/raw_xml_in_out_msg_recv.c2006-10-07
13:31:36.094847670 -0400
@@ -325,7 +325,7 @@
else if (soap_fault)
{
AXIS2_MSG_CTX_SET_SOAP_ENVELOPE(new_msg_ctx, env, default_envelope);
-status = AXIS2_FAILURE; /* if there is a failure we have to return a
failure code */
+status = AXIS2_SUCCESS;
}
else
{
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2C-328) unable to return custom SOAP faults
[
http://issues.apache.org/jira/browse/AXIS2C-328?page=comments#action_12440692 ]
Chris Darroch commented on AXIS2C-328:
--
Oh, right -- I forgot to add that it would be very helpful if the util package
could provide some add_error functions, so that one could register
custom error codes and messages. As it is, I'll have to patch
axis2_error.h and friends so that my custom AXIS2_ERROR_FOO
code and matching message are registered in advance.
Maybe there's an even cleaner way to allow services to return custom soap
faults, but I haven't given it much thought. Sorry.
unable to return custom SOAP faults
---
Key: AXIS2C-328
URL: http://issues.apache.org/jira/browse/AXIS2C-328
Project: Axis2-C
Issue Type: Bug
Components: core/receivers, code generation, wsdl2c tool
Affects Versions: Current (Nightly), 0.93
Reporter: Chris Darroch
Thanks, BTW, for the tcpmon tool -- very helpful!
I have a need to return custom SOAP fault messages from an Axis2/C server.
This turns out to require some patches in a few places. First, the code
generated by the w2c tool always calls a local on_fault handler, named
axis2_svc_skel_foo_on_fault() in the axis2_svc_skel_foo.c file. This
function, as generated by w2c, creates a fault element and returns it in
the SOAP body.
Changing axis2_svc_skel_foo_on_fault() to simply return NULL instead allows
the
axis2_raw_xml_in_out_msg_recv_invoke_business_logic_sync() function in
modules/core/receivers/raw_xml_in_out_msg_recv.c to recognize that no body
element
has been returned, and create a SOAP fault instead.
The actual business logic that one fills into the axis2_skel_foo.c file can
then simply
do the following:
axis2_skel_foo_Foo(...) {
AXIS2_ERROR_SET_STATUS_CODE(env-error, AXIS2_FAILURE);
AXIS2_ERROR_SET_ERROR_NUMBER(env-error,
AXIS2_ERROR_FOO);
return NULL;
}
This almost works, and
axis2_raw_xml_in_out_msg_recv_invoke_business_logic_sync()
now recognizes the fault condition and calls
axiom_soap_fault_create_default_fault()
to create the SOAP fault element. Good, except that it then returns
AXIS2_FAILURE,
so that its caller, axis2_raw_xml_in_out_msg_recv_receive_sync() in
modules/core/receivers/msg_recv.c, then does this:
status = AXIS2_MSG_RECV_INVOKE_IN_OUT_BUSINESS_LOGIC_SYNC(msg_recv, env,
msg_ctx, out_msg_ctx);
if(AXIS2_SUCCESS != status)
{
axis2_core_utils_reset_out_msg_ctx(env, out_msg_ctx);
AXIS2_MSG_CTX_FREE(out_msg_ctx, env);
return status;
}
which destroys the nice SOAP fault and returns an empty body element instead
to the client!
My current patch is to have
axis2_raw_xml_in_out_msg_recv_invoke_business_logic_sync() return
AXIS2C_SUCCESS instead -- this makes sense to me, because although an fault
condition has been detected, the function has successfully handled it by
creating
the SOAP fault element. Here's the patch:
--- modules/core/receivers/raw_xml_in_out_msg_recv.c.orig 2006-10-07
13:31:17.801951262 -0400
+++ modules/core/receivers/raw_xml_in_out_msg_recv.c2006-10-07
13:31:36.094847670 -0400
@@ -325,7 +325,7 @@
else if (soap_fault)
{
AXIS2_MSG_CTX_SET_SOAP_ENVELOPE(new_msg_ctx, env, default_envelope);
-status = AXIS2_FAILURE; /* if there is a failure we have to return a
failure code */
+status = AXIS2_SUCCESS;
}
else
{
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1323) Consume Axis 2 web service in VB.NET
Consume Axis 2 web service in VB.NET Key: AXIS2-1323 URL: http://issues.apache.org/jira/browse/AXIS2-1323 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 0.95 Environment: Win 2003 Reporter: Ravi Please let me know how to hanle request and response object in vb.net client application. i am trying to invoke sample web service from axis2 (getVersion()). It is asking me to pass request object and returns as response object. i have used axis getVersion which returns of type string and directly assign variable and use it. but in axis2 its not the same. Please do help me. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-1323) Consume Axis 2 web service in VB.NET
[ http://issues.apache.org/jira/browse/AXIS2-1323?page=all ] Thilina Gunarathne resolved AXIS2-1323. --- Resolution: Invalid Please post your question to the Axis2 user list... http://ws.apache.org/axis2/mail-lists.html Consume Axis 2 web service in VB.NET Key: AXIS2-1323 URL: http://issues.apache.org/jira/browse/AXIS2-1323 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 0.95 Environment: Win 2003 Reporter: Ravi Please let me know how to hanle request and response object in vb.net client application. i am trying to invoke sample web service from axis2 (getVersion()). It is asking me to pass request object and returns as response object. i have used axis getVersion which returns of type string and directly assign variable and use it. but in axis2 its not the same. Please do help me. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1324) Improvement to document - eclipse-codegen-plugin-help
Improvement to document - eclipse-codegen-plugin-help -- Key: AXIS2-1324 URL: http://issues.apache.org/jira/browse/AXIS2-1324 Project: Apache Axis 2.0 (Axis2) Issue Type: Improvement Components: samples, build,site docs Affects Versions: 1.1 Environment: windows , linux Reporter: Lahiru Sandakith modifications needed for the help file that describes step by step procedure of the eclipse-codegen-plugin -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1324) Improvement to document - eclipse-codegen-plugin-help
[ http://issues.apache.org/jira/browse/AXIS2-1324?page=all ] Lahiru Sandakith updated AXIS2-1324: Attachment: eclipse-codegen-plugin-help-07102005-patch.txt attached file is the patch for the document update Improvement to document - eclipse-codegen-plugin-help -- Key: AXIS2-1324 URL: http://issues.apache.org/jira/browse/AXIS2-1324 Project: Apache Axis 2.0 (Axis2) Issue Type: Improvement Components: samples, build,site docs Affects Versions: 1.1 Environment: windows , linux Reporter: Lahiru Sandakith Attachments: eclipse-codegen-plugin-help-07102005-patch.txt modifications needed for the help file that describes step by step procedure of the eclipse-codegen-plugin -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1324) Improvement to document - eclipse-codegen-plugin-help
[ http://issues.apache.org/jira/browse/AXIS2-1324?page=all ] Lahiru Sandakith updated AXIS2-1324: Attachment: eclipse_codegen_wizard_pics.zip attached file contains the new pictures, that needed to be added Improvement to document - eclipse-codegen-plugin-help -- Key: AXIS2-1324 URL: http://issues.apache.org/jira/browse/AXIS2-1324 Project: Apache Axis 2.0 (Axis2) Issue Type: Improvement Components: samples, build,site docs Affects Versions: 1.1 Environment: windows , linux Reporter: Lahiru Sandakith Attachments: eclipse-codegen-plugin-help-07102005-patch.txt, eclipse_codegen_wizard_pics.zip modifications needed for the help file that describes step by step procedure of the eclipse-codegen-plugin -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Axis2 1.1 release branching - CODE FREEZE
On Thu, 2006-10-05 at 18:09 +0530, Deepal Jayasinghe wrote: Ruchith Fernando wrote: Hi Thilina, Are we going to create nightly builds from this 1.1 branch? good question .. Unless there are objections I propose that we change the nightly builds to be ONLY from the 1.1 branch. Sanjiva. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Axis2 1.1 release branching - CODE FREEZE
On Thu, 2006-10-05 at 17:54 +0530, Deepal Jayasinghe wrote: Seems good , but make unnecessary complication. Right now if I fixed a bug it takes about 40 mins to run the build , but after this I have to spent more than an hour (need to run two separate builds). Do you think this is a good idea ?.. I never agree to have branches , since I knew it going to be difficult task for developers. Even in last Axis2 realsae (Axis2 1.0) we didnt do a branch and we did that after we done the release. *I think we need to reconsider this .* P:S- remember what happen if someone commit while I am running my build , then I need to run the build again. No solution is perfect; we can't keen an indefinite lock on others' progress while the 1.1 release is done. There's been a virtual code freeze now for few weeks .. we just can't do that for so long. Let's be realistic- not every patch will likely make it to trunk right now. We'll all have to have some painful time after the release to sync the trees. Sanjiva. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-1324) Improvement to document - eclipse-codegen-plugin-help
[ http://issues.apache.org/jira/browse/AXIS2-1324?page=all ] Thilina Gunarathne resolved AXIS2-1324. --- Resolution: Fixed Assignee: Thilina Gunarathne Thanx sandakith.. Patch applied.. http://svn.apache.org/viewvc?view=revrev=453969 Improvement to document - eclipse-codegen-plugin-help -- Key: AXIS2-1324 URL: http://issues.apache.org/jira/browse/AXIS2-1324 Project: Apache Axis 2.0 (Axis2) Issue Type: Improvement Components: samples, build,site docs Affects Versions: 1.1 Environment: windows , linux Reporter: Lahiru Sandakith Assigned To: Thilina Gunarathne Attachments: eclipse-codegen-plugin-help-07102005-patch.txt, eclipse_codegen_wizard_pics.zip modifications needed for the help file that describes step by step procedure of the eclipse-codegen-plugin -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1249) BareTests.testTwoWaySync test is failing yet still reporting success
[ http://issues.apache.org/jira/browse/AXIS2-1249?page=comments#action_12440698 ] Jeff Barrett commented on AXIS2-1249: - This testcase was removed from the JAXWSTest driver under the patch for AXIS2-1322. The test continues to fail if it is run, so I am leaving this Jira open. The test needs to be debugged, fixed, and added back into the test driver. BareTests.testTwoWaySync test is failing yet still reporting success Key: AXIS2-1249 URL: http://issues.apache.org/jira/browse/AXIS2-1249 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Jeff Barrett The test org.apache.axis2.jaxws.sample.BareTests.testTwoWaySync is catching an exception. I don't think that exception is expected. It is printing the exception to modules/jaxws/target\test-reports/TEST-org.apache.axis2.jaxws.framework.JAXWSTest.txt, but the test is not failing. The exception is: javax.xml.ws.WebServiceException at org.apache.axis2.jaxws.ExceptionFactory.createWebServiceException(ExceptionFactory.java:217) at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:81) at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:185) at org.apache.axis2.jaxws.core.controller.AxisInvocationController.invoke(AxisInvocationController.java:220) at org.apache.axis2.jaxws.client.proxy.BaseProxyHandler.InvokeSEIMethod(BaseProxyHandler.java:189) at org.apache.axis2.jaxws.client.proxy.BaseProxyHandler.invoke(BaseProxyHandler.java:125) at $Proxy29.twoWaySimple(Unknown Source) at org.apache.axis2.jaxws.sample.BareTests.testTwoWaySync`(BareTests.java:28) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at junit.framework.TestCase.runTest(TestCase.java:164) at junit.framework.TestCase.runBare(TestCase.java:130) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:297) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:672) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:567) Caused by: org.apache.axis2.AxisFault: Operation Not found EPR is /axis2/services/BareDocLitService and WSA Action = at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:298) at org.apache.axis2.jaxws.core.controller.AxisInvocationController.invoke(AxisInvocationController.java:174) ... 25 more Caused by: java.lang.Exception: org.apache.axis2.AxisFault: Operation Not found EPR is /axis2/services/BareDocLitService and WSA Action = at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:47) at org.apache.axis2.engine.Phase.invoke(Phase.java:393) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:535) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:493) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:324) at org.apache.axis2.transport.http.HTTPWorker.service(HTTPWorker.java:238) at org.apache.axis2.transport.http.server.DefaultHttpServiceProcessor.doService(DefaultHttpServiceProcessor.java:179) at org.apache.http.protocol.HttpService.handleRequest(HttpService.java:123) at org.apache.axis2.transport.http.server.DefaultHttpServiceProcessor.run(DefaultHttpServiceProcessor.java:251) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) at
[jira] Resolved: (AXIS2-1322) Adding Initial Holder Support and Refactoring Client and Server Message Marshalling.
[ http://issues.apache.org/jira/browse/AXIS2-1322?page=all ] Jeff Barrett resolved AXIS2-1322. - Resolution: Fixed Patch committed. Adding Initial Holder Support and Refactoring Client and Server Message Marshalling. Key: AXIS2-1322 URL: http://issues.apache.org/jira/browse/AXIS2-1322 Project: Apache Axis 2.0 (Axis2) Issue Type: New Feature Components: jaxws Reporter: Nikhil Thaker Attachments: JIRA_1322_HolderSupportAndMethodMarshaller.txt I am adding Holder support to JAXWS Proxy code. I will add test cases for Wrap and Bare methods that use Holders. Seconldy I am adding the common Method Marshaller code that will be used on client and server to marshall message and demarshal Message. I have discussed the architecure with Rich and Nick on this so they are aware of the changes. As a result of refactoring the abstract ProxyHandler model and Proxy Descriptor on client and Mappler code on server side will be deleted I will submit patch for this JIRA. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-1321) JAXWS test NonWrapTests.testTwoWaySync is failing yet still reporting success
[ http://issues.apache.org/jira/browse/AXIS2-1321?page=all ] Jeff Barrett resolved AXIS2-1321. - Resolution: Fixed The patch for http://issues.apache.org/jira/browse/AXIS2-1322 also addressed this issue. That patch has been commited. JAXWS test NonWrapTests.testTwoWaySync is failing yet still reporting success - Key: AXIS2-1321 URL: http://issues.apache.org/jira/browse/AXIS2-1321 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Jeff Barrett The test org.apache.axis2.jaxws.sample.NonWrapTests.testTwoWaySync is catching an exception. That exception is not expected. The test is simply printing exception to modules/jaxws/target\test-reports/TEST-org.apache.axis2.jaxws.framework.JAXWSTest.txt, but the test is not failing. The exception is: javax.xml.ws.WebServiceException at org.apache.axis2.jaxws.ExceptionFactory.createWebServiceException(ExceptionFactory.java:217) at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:81) at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:185) at org.apache.axis2.jaxws.core.controller.AxisInvocationController.invoke(AxisInvocationController.java:220) at org.apache.axis2.jaxws.client.proxy.BaseProxyHandler.InvokeSEIMethod(BaseProxyHandler.java:189) at org.apache.axis2.jaxws.client.proxy.BaseProxyHandler.invoke(BaseProxyHandler.java:125) at $Proxy26.twoWay(Unknown Source) at org.apache.axis2.jaxws.sample.NonWrapTests.testTwoWaySync(NonWrapTests.java:40) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at junit.framework.TestCase.runTest(TestCase.java:164) at junit.framework.TestCase.runBare(TestCase.java:130) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:297) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:672) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:567) Caused by: org.apache.axis2.AxisFault: unknown at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:295) at org.apache.axis2.jaxws.core.controller.AxisInvocationController.invoke(AxisInvocationController.java:174) ... 25 more Caused by: java.lang.Exception: javax.xml.ws.WebServiceException at org.apache.axis2.jaxws.ExceptionFactory.createWebServiceException(ExceptionFactory.java:217) at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:81) at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:185) at org.apache.axis2.jaxws.server.EndpointController.invoke(EndpointController.java:81) at org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessageReceiver.java:147) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:493) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:324) at org.apache.axis2.transport.http.HTTPWorker.service(HTTPWorker.java:238) at org.apache.axis2.transport.http.server.DefaultHttpServiceProcessor.doService(DefaultHttpServiceProcessor.java:179) at org.apache.http.protocol.HttpService.handleRequest(HttpService.java:123) at org.apache.axis2.transport.http.server.DefaultHttpServiceProcessor.run(DefaultHttpServiceProcessor.java:251) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) at
[jira] Closed: (AXIS2-1321) JAXWS test NonWrapTests.testTwoWaySync is failing yet still reporting success
[ http://issues.apache.org/jira/browse/AXIS2-1321?page=all ] Jeff Barrett closed AXIS2-1321. --- JAXWS test NonWrapTests.testTwoWaySync is failing yet still reporting success - Key: AXIS2-1321 URL: http://issues.apache.org/jira/browse/AXIS2-1321 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Jeff Barrett The test org.apache.axis2.jaxws.sample.NonWrapTests.testTwoWaySync is catching an exception. That exception is not expected. The test is simply printing exception to modules/jaxws/target\test-reports/TEST-org.apache.axis2.jaxws.framework.JAXWSTest.txt, but the test is not failing. The exception is: javax.xml.ws.WebServiceException at org.apache.axis2.jaxws.ExceptionFactory.createWebServiceException(ExceptionFactory.java:217) at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:81) at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:185) at org.apache.axis2.jaxws.core.controller.AxisInvocationController.invoke(AxisInvocationController.java:220) at org.apache.axis2.jaxws.client.proxy.BaseProxyHandler.InvokeSEIMethod(BaseProxyHandler.java:189) at org.apache.axis2.jaxws.client.proxy.BaseProxyHandler.invoke(BaseProxyHandler.java:125) at $Proxy26.twoWay(Unknown Source) at org.apache.axis2.jaxws.sample.NonWrapTests.testTwoWaySync(NonWrapTests.java:40) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at junit.framework.TestCase.runTest(TestCase.java:164) at junit.framework.TestCase.runBare(TestCase.java:130) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:297) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:672) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:567) Caused by: org.apache.axis2.AxisFault: unknown at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:295) at org.apache.axis2.jaxws.core.controller.AxisInvocationController.invoke(AxisInvocationController.java:174) ... 25 more Caused by: java.lang.Exception: javax.xml.ws.WebServiceException at org.apache.axis2.jaxws.ExceptionFactory.createWebServiceException(ExceptionFactory.java:217) at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:81) at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:185) at org.apache.axis2.jaxws.server.EndpointController.invoke(EndpointController.java:81) at org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessageReceiver.java:147) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:493) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:324) at org.apache.axis2.transport.http.HTTPWorker.service(HTTPWorker.java:238) at org.apache.axis2.transport.http.server.DefaultHttpServiceProcessor.doService(DefaultHttpServiceProcessor.java:179) at org.apache.http.protocol.HttpService.handleRequest(HttpService.java:123) at org.apache.axis2.transport.http.server.DefaultHttpServiceProcessor.run(DefaultHttpServiceProcessor.java:251) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:797) Caused by: java.lang.NullPointerException at
[jira] Closed: (AXIS2-1322) Adding Initial Holder Support and Refactoring Client and Server Message Marshalling.
[ http://issues.apache.org/jira/browse/AXIS2-1322?page=all ] Jeff Barrett closed AXIS2-1322. --- Adding Initial Holder Support and Refactoring Client and Server Message Marshalling. Key: AXIS2-1322 URL: http://issues.apache.org/jira/browse/AXIS2-1322 Project: Apache Axis 2.0 (Axis2) Issue Type: New Feature Components: jaxws Reporter: Nikhil Thaker Attachments: JIRA_1322_HolderSupportAndMethodMarshaller.txt I am adding Holder support to JAXWS Proxy code. I will add test cases for Wrap and Bare methods that use Holders. Seconldy I am adding the common Method Marshaller code that will be used on client and server to marshall message and demarshal Message. I have discussed the architecure with Rich and Nick on this so they are aware of the changes. As a result of refactoring the abstract ProxyHandler model and Proxy Descriptor on client and Mappler code on server side will be deleted I will submit patch for this JIRA. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2]WSDL2Java Code generation option
Hi All; Right now When we codegen for server side with WSDL2Java .. when we give -sd or -ss it create only server side code. However it is very useful if it generate both server and client side code. Axis1.1 use to do that. If you think about it .. 90% of the time user will need to check does his service is working and will generate the client side code as well. Thanks Srinath -- Srinath Perera: http://www.cs.indiana.edu/~hperera/ http://www.bloglines.com/blog/hemapani - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2]WSDL2Java Code generation option
:) +1 from me. I tried sneaking this in a couple of times via the testcase generation option. Not sure if it still works. (-ss -sd -t) -- dims On 10/7/06, Srinath Perera [EMAIL PROTECTED] wrote: Hi All; Right now When we codegen for server side with WSDL2Java .. when we give -sd or -ss it create only server side code. However it is very useful if it generate both server and client side code. Axis1.1 use to do that. If you think about it .. 90% of the time user will need to check does his service is working and will generate the client side code as well. Thanks Srinath -- Srinath Perera: http://www.cs.indiana.edu/~hperera/ http://www.bloglines.com/blog/hemapani - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2]WSDL2Java Code generation option
Try the -g option. - Dennis Davanum Srinivas wrote: :) +1 from me. I tried sneaking this in a couple of times via the testcase generation option. Not sure if it still works. (-ss -sd -t) -- dims On 10/7/06, Srinath Perera [EMAIL PROTECTED] wrote: Hi All; Right now When we codegen for server side with WSDL2Java .. when we give -sd or -ss it create only server side code. However it is very useful if it generate both server and client side code. Axis1.1 use to do that. If you think about it .. 90% of the time user will need to check does his service is working and will generate the client side code as well. Thanks Srinath -- Srinath Perera: http://www.cs.indiana.edu/~hperera/ http://www.bloglines.com/blog/hemapani - 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]
[jira] Commented: (AXIS2-969) Missing xsi:type in SOAP-Message
[ http://issues.apache.org/jira/browse/AXIS2-969?page=comments#action_12440710 ] Thomas, Berlinghoff commented on AXIS2-969: --- Thank you for the fix and keep up the great work. BTW think bug 980 (http://issues.apache.org/jira/browse/AXIS2-980) can also be closed since this not an issue with the current nightly snap. Cheers, Thomas Missing xsi:type in SOAP-Message Key: AXIS2-969 URL: http://issues.apache.org/jira/browse/AXIS2-969 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.0 Environment: Windows XP Professional, Tomcat 5.5, Axis2 1.0 and nightly snapshot from 3rd August 2006 Reporter: Desiree Hilbring Assigned To: Sanka Samaranayake Priority: Blocker Attachments: delivery060803-2.xsd, GMLSFClient.java, GMLSFE060803.wsdl, GMLSFESkeleton.java I am trying to create an working inheritance example with Axis2. In the attached example case OAMIFASCapabilitiesType is derived from OAMIServiceSpecificCapabilities. To recognize the inheritance the client needs the xsi:type in the SOAP message, but it is missing. The example will work outcommenting the following lines in GMLSFESkeleton: XmlCursor cur = resp.getOAGetMetaInformationResponse().getFeatureMetaInformation().getOAMIServiceSpecificCapabilities().newCursor(); cur.toFirstChild(); cur.insertAttributeWithValue(type, http://www.w3.org/2001/XMLSchema-instance;, OAMIFASCapabilitiesType); cur.dispose(); Why is the xsi:type not sent? Davanum Srinivas advised my to try the latest nightly snapshot, which is the one from 3rd August 2006. Unforunately I do have another issue with that version, trying to create the code with WSDL2Java. I'll get the following exceptions in the created GMLSFEStub.java: [javac] Compiling 225 source files to C:\hilbring\EclipseWTP\GMLSFE\classes [javac] C:\hilbring\EclipseWTP\GMLSFE\output\src\org\example\types\GMLSFEStub.java:142: toEnvelope(org.apache.axiom.soap.SOAPFactory) in org.example.types.GMLSFEStub cannot be applied to (org.apache.axiom.soap.SOAPFactory,orchestra.oas.building.BuildingStringDocument,boolean) [javac] env = toEnvelope(getFactory(_operationClient.getOptions().getSoapVersionURI()), [javac] ^ [javac] C:\hilbring\EclipseWTP\GMLSFE\output\src\org\example\types\GMLSFEStub.java:247: toEnvelope(org.apache.axiom.soap.SOAPFactory) in org.example.types.GMLSFEStub cannot be applied to (org.apache.axiom.soap.SOAPFactory,orchestra.oas.building.BuildingStringDocument,boolean) [javac] env = toEnvelope(getFactory(_operationClient.getOptions().getSoapVersionURI()), [javac] ^ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2]WSDL2Java Code generation option
Hi, I guess I should say why this style was selected. As for Axis1 the code generator always generates the client code when asked for the server side code. It seemed a bit ugly an somewhat confusing from the users point of view [ I also get a stub when I ask for a skeleton ??] . Hence the option -g to (generate-all) needs to be used to generate both the client and server side code. Ajith On 10/7/06, Dennis Sosnoski [EMAIL PROTECTED] wrote: Try the -g option. - Dennis Davanum Srinivas wrote: :) +1 from me. I tried sneaking this in a couple of times via the testcase generation option. Not sure if it still works. (-ss -sd -t) -- dims On 10/7/06, Srinath Perera [EMAIL PROTECTED] wrote: Hi All; Right now When we codegen for server side with WSDL2Java .. when we give -sd or -ss it create only server side code. However it is very useful if it generate both server and client side code. Axis1.1 use to do that. If you think about it .. 90% of the time user will need to check does his service is working and will generate the client side code as well. Thanks Srinath -- Srinath Perera: http://www.cs.indiana.edu/~hperera/ http://www.bloglines.com/blog/hemapani - 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] -- Ajith Ranabahu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-980) Underlines in typenames does not work with inheritance
[ http://issues.apache.org/jira/browse/AXIS2-980?page=all ] Davanum Srinivas resolved AXIS2-980. Resolution: Fixed Resolved as per comment in AXIS2-969 -- dims Underlines in typenames does not work with inheritance -- Key: AXIS2-980 URL: http://issues.apache.org/jira/browse/AXIS2-980 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.0 Environment: Windows XP Professional Tomcat 5.5 Axis2 1.0 Reporter: Desiree Hilbring Attachments: GMLSFUnderline.zip The attachment includes a little inheritance example, OA_MIFASCapabilitesType is derived from OAMIServiceSpecificCapabilites. To send the xsi:type in the SOAP-Message I am using the following lines: XmlCursor cur = resp.getOAGetMetaInformationResponse().getFeatureMetaInformation().getOAMIServiceSpecificCapabilities().newCursor(); cur.toFirstChild(); cur.insertAttributeWithValue(type, http://www.w3.org/2001/XMLSchema-instance;, OAMIFASCapabilitiesType); cur.dispose(); The SOAP-Message does include the xsi:type but the client does not recognize the subtype OA_MIFASCapabilitiesType. But changing the name of OA_MIFASCapabilitiesType in delivery060803-2.xsd to OAMIFASCapabilitiesType will solve the problem and the example will work. Is it possible to use underlines in the typeNames or are there any restrictions, or is this a bug? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1325) SOAP message using xsi:nil has no definition of xsi
SOAP message using xsi:nil has no definition of xsi --- Key: AXIS2-1325 URL: http://issues.apache.org/jira/browse/AXIS2-1325 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.1 Reporter: Jake Goulding Trying to communicate with Sharepoint web services. Function takes an unsigned int that can be nil. It is in this case, and it is specified on the outgoing SOAP. However, the xsi namespace is not defined. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1325) SOAP message using xsi:nil has no definition of xsi
[ http://issues.apache.org/jira/browse/AXIS2-1325?page=all ] Jake Goulding updated AXIS2-1325: - Attachment: SOAP Message.txt SOAP Message SOAP message using xsi:nil has no definition of xsi --- Key: AXIS2-1325 URL: http://issues.apache.org/jira/browse/AXIS2-1325 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.1 Reporter: Jake Goulding Attachments: Code Snippet.java, SiteData.wsdl.xml, SOAP Message.txt Trying to communicate with Sharepoint web services. Function takes an unsigned int that can be nil. It is in this case, and it is specified on the outgoing SOAP. However, the xsi namespace is not defined. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1325) SOAP message using xsi:nil has no definition of xsi
[ http://issues.apache.org/jira/browse/AXIS2-1325?page=all ] Jake Goulding updated AXIS2-1325: - Attachment: Code Snippet.java Snippets used to recreate the problem. SOAP message using xsi:nil has no definition of xsi --- Key: AXIS2-1325 URL: http://issues.apache.org/jira/browse/AXIS2-1325 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.1 Reporter: Jake Goulding Attachments: Code Snippet.java, SiteData.wsdl.xml, SOAP Message.txt Trying to communicate with Sharepoint web services. Function takes an unsigned int that can be nil. It is in this case, and it is specified on the outgoing SOAP. However, the xsi namespace is not defined. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1325) SOAP message using xsi:nil has no definition of xsi
[ http://issues.apache.org/jira/browse/AXIS2-1325?page=all ] Jake Goulding updated AXIS2-1325: - Attachment: SiteData.wsdl.xml WSDL for the functions in question. SOAP message using xsi:nil has no definition of xsi --- Key: AXIS2-1325 URL: http://issues.apache.org/jira/browse/AXIS2-1325 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.1 Reporter: Jake Goulding Attachments: Code Snippet.java, SiteData.wsdl.xml, SOAP Message.txt Trying to communicate with Sharepoint web services. Function takes an unsigned int that can be nil. It is in this case, and it is specified on the outgoing SOAP. However, the xsi namespace is not defined. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] Nightly builds from Trunk and 1.1 Branch
Folks, FYI, http://people.apache.org/dist/axis2/nightly/ now has the artifacts from both the HEAD/trunk and the 1.1 branch. thanks, dims -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1325) SOAP message using xsi:nil has no definition of xsi
[ http://issues.apache.org/jira/browse/AXIS2-1325?page=comments#action_12440718 ] Davanum Srinivas commented on AXIS2-1325: - Jake, this is not a namespace problem. the schema says s:element minOccurs=1 maxOccurs=1 name=uRowLimit type=s:unsignedInt/ So, you *need* to fill up the field and should not leave it empty. Yes, we need to slightly enhance codegen to not let u leave the field nil... thanks, dims SOAP message using xsi:nil has no definition of xsi --- Key: AXIS2-1325 URL: http://issues.apache.org/jira/browse/AXIS2-1325 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.1 Reporter: Jake Goulding Attachments: Code Snippet.java, SiteData.wsdl.xml, SOAP Message.txt Trying to communicate with Sharepoint web services. Function takes an unsigned int that can be nil. It is in this case, and it is specified on the outgoing SOAP. However, the xsi namespace is not defined. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1325) SOAP message using xsi:nil has no definition of xsi
[
http://issues.apache.org/jira/browse/AXIS2-1325?page=comments#action_12440721 ]
Jake Goulding commented on AXIS2-1325:
--
Interesting... I am working from another implementation, which clearly does not
send that field:
?xml version=1.0 encoding=UTF-8 standalone=yes ?
soap:Envelope xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/;
xmlns=http://schemas.microsoft.com/sharepoint/soap/;
soap:Body
GetListItems
strListName{B6196D27-5408-4CBE-A88E-7AE791202BB7}/strListName
/GetListItems
/soap:Body
/soap:Envelope
Looks like the WSDL itself is wrong...
Also, the namespace not being defined is still wrong, correct?
SOAP message using xsi:nil has no definition of xsi
---
Key: AXIS2-1325
URL: http://issues.apache.org/jira/browse/AXIS2-1325
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Affects Versions: 1.1
Reporter: Jake Goulding
Attachments: Code Snippet.java, SiteData.wsdl.xml, SOAP Message.txt
Trying to communicate with Sharepoint web services. Function takes an
unsigned int that can be nil. It is in this case, and it is specified on the
outgoing SOAP. However, the xsi namespace is not defined.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1325) SOAP message using xsi:nil has no definition of xsi
[ http://issues.apache.org/jira/browse/AXIS2-1325?page=comments#action_12440722 ] Davanum Srinivas commented on AXIS2-1325: - I do see the xmlns:xsi in the soap request...it's defined where it is used which is kosher. ns1:uRowLimit xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:nil=true / -- dims SOAP message using xsi:nil has no definition of xsi --- Key: AXIS2-1325 URL: http://issues.apache.org/jira/browse/AXIS2-1325 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.1 Reporter: Jake Goulding Attachments: Code Snippet.java, SiteData.wsdl.xml, SOAP Message.txt Trying to communicate with Sharepoint web services. Function takes an unsigned int that can be nil. It is in this case, and it is specified on the outgoing SOAP. However, the xsi namespace is not defined. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1325) SOAP message using xsi:nil has no definition of xsi
[ http://issues.apache.org/jira/browse/AXIS2-1325?page=comments#action_12440724 ] Jake Goulding commented on AXIS2-1325: -- Wow... thats what I get for working so late on a weekend. Thanks for showing me my error. :-) SOAP message using xsi:nil has no definition of xsi --- Key: AXIS2-1325 URL: http://issues.apache.org/jira/browse/AXIS2-1325 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.1 Reporter: Jake Goulding Attachments: Code Snippet.java, SiteData.wsdl.xml, SOAP Message.txt Trying to communicate with Sharepoint web services. Function takes an unsigned int that can be nil. It is in this case, and it is specified on the outgoing SOAP. However, the xsi namespace is not defined. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2]Two HTTP server?
Hi All; Axis2 source have two SimpleHTTPServer 's . Is it beocue one is outdated, but not removed or is there a reson for having both? org.apache.axis2.transport.http.server.SimpleHttpServer org.apache.axis2.transport.http.SimpleHTTPServer Thanks Srinath -- Srinath Perera: http://www.cs.indiana.edu/~hperera/ http://www.bloglines.com/blog/hemapani - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2]Two HTTP server?
org.apache.axis2.transport.http.SimpleHTTPServer extends the other one -- dims On 10/7/06, Srinath Perera [EMAIL PROTECTED] wrote: Hi All; Axis2 source have two SimpleHTTPServer 's . Is it beocue one is outdated, but not removed or is there a reson for having both? org.apache.axis2.transport.http.server.SimpleHttpServer org.apache.axis2.transport.http.SimpleHTTPServer Thanks Srinath -- Srinath Perera: http://www.cs.indiana.edu/~hperera/ http://www.bloglines.com/blog/hemapani - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] 1.1 build broken (again)
More security stuff: Testsuite: org.apache.rampart.RampartTest Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 26.55 sec - Standard Output --- Server started on port .Testing WS-Sec: custom scenario 1 Service invoked Testing WS-Sec: custom scenario 2 Service invoked Testing WS-Sec: custom scenario 3 [SimpleHTTPServer] Stop called Server stopped .[SimpleHTTPServer] Stop called - --- - Standard Error - log4j:WARN No appenders could be found for logger (org.apache.axiom.om.util.StAXUtils). log4j:WARN Please initialize the log4j system properly. org.apache.axis2.AxisFault: Error during encryption; nested exception is: org.apache.rampart.RampartException: Error during encryption at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:65) ... Caused by: org.apache.rampart.RampartException: Error during encryption at org.apache.rampart.builder.AsymmetricBindingBuilder.doSignBeforeEncrypt(AsymmetricBindingBuilder.java:415) at org.apache.rampart.builder.AsymmetricBindingBuilder.build(AsymmetricBindingBuilder.java:75) at org.apache.rampart.MessageBuilder.build(MessageBuilder.java:128) at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:59) ... 22 more Caused by: org.apache.ws.security.WSSecurityException: Cannot encrypt/decrypt data; nested exception is: org.apache.xml.security.encryption.XMLEncryptionException: Illegal key size or default parameters Original Exception was java.security.InvalidKeyException: Illegal key size or default parameters at org.apache.ws.security.message.WSSecEncrypt.doEncryption(WSSecEncrypt.java:459) at org.apache.ws.security.message.WSSecEncrypt.doEncryption(WSSecEncrypt.java:399) at org.apache.ws.security.message.WSSecEncrypt.encryptForInternalRef(WSSecEncrypt.java:306) at org.apache.rampart.builder.AsymmetricBindingBuilder.doSignBeforeEncrypt(AsymmetricBindingBuilder.java:407) ... 25 more Caused by: org.apache.xml.security.encryption.XMLEncryptionException: Illegal key size or default parameters Original Exception was java.security.InvalidKeyException: Illegal key size or default parameters at org.apache.xml.security.encryption.XMLCipher.encryptData(Unknown Source) at org.apache.xml.security.encryption.XMLCipher.encryptElementContent(Unknown Source) at org.apache.xml.security.encryption.XMLCipher.doFinal(Unknown Source) at org.apache.ws.security.message.WSSecEncrypt.doEncryption(WSSecEncrypt.java:457) ... 28 more and: Testsuite: org.apache.rahas.RahasSAMLTokenV1205Test Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 42.983 sec - Standard Output --- Server started on port .[SimpleHTTPServer] Stop called Server stopped .[SimpleHTTPServer] Stop called - --- - Standard Error - log4j:WARN No appenders could be found for logger (org.apache.axiom.om.util.StAXUtils). log4j:WARN Please initialize the log4j system properly. org.apache.axis2.AxisFault: Read timed out; nested exception is: java.net.SocketTimeoutException: Read timed out; nested exception is: org.apache.axis2.AxisFault: Read timed out; nested exception is: java.net.SocketTimeoutException: Read timed out at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:227) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:642) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:351) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:281) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:569) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:500) Tried the build twice, resyncing in between, with failures both times. - Dennis -- Dennis M. Sosnoski SOA, Web Services, and XML Training and Consulting http://www.sosnoski.com - http://www.sosnoski.co.nz Seattle, WA +1-425-296-6194 - Wellington, NZ +64-4-298-6117 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
