[jira] Created: (AXIS2C-647) axis2_engine_create_fault_msg_ctx() function does not create proper soap fault
axis2_engine_create_fault_msg_ctx() function does not create proper soap fault -- Key: AXIS2C-647 URL: https://issues.apache.org/jira/browse/AXIS2C-647 Project: Axis2-C Issue Type: Bug Affects Versions: Current (Nightly) Reporter: Sahan Gamage Inside the axis2_engine_create_fault_msg_ctx() function only creates a soap envelope, but not a fault part. We need to change the function prototype to get at least the fault code and reason and then create the proper soap fault. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[AXIS2] axiom_text_get_text should be exported
forwarding with proper subject. Hi devs, Currently the axiom_text_get_text() function in om_text.c is declared static. This function is of use when someone is handling the text node directly, when MTOM optimization is used. For example the RAMPARTC-23 iira issue [1] can be solved elegantly with this function exported. Hence I suggest that we make this function AXIS2_EXTERN. -Dumindu. [1] https://issues.apache.org/jira/browse/RAMPARTC-23 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [AXIS2] axiom_text_get_text should be exported
+1 for exposing the function. -Manjula. On Tue, 2007-07-24 at 15:27 +0530, Dumindu Pallewela wrote: forwarding with proper subject. Hi devs, Currently the axiom_text_get_text() function in om_text.c is declared static. This function is of use when someone is handling the text node directly, when MTOM optimization is used. For example the RAMPARTC-23 iira issue [1] can be solved elegantly with this function exported. Hence I suggest that we make this function AXIS2_EXTERN. -Dumindu. [1] https://issues.apache.org/jira/browse/RAMPARTC-23 - 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]
Re: [AXIS2] axiom_text_get_text should be exported
Dumindu Pallewela wrote: forwarding with proper subject. Hi devs, Currently the axiom_text_get_text() function in om_text.c is declared static. This function is of use when someone is handling the text node directly, when MTOM optimization is used. For example the RAMPARTC-23 iira issue [1] can be solved elegantly with this function exported. Hence I suggest that we make this function AXIS2_EXTERN. +1 -Dumindu. [1] https://issues.apache.org/jira/browse/RAMPARTC-23 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://kaushalye.blogspot.com/ http://wso2.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2C-648) wsdl2c tool does not generate correct code when modules are engaed.
wsdl2c tool does not generate correct code when modules are engaed. --- Key: AXIS2C-648 URL: https://issues.apache.org/jira/browse/AXIS2C-648 Project: Axis2-C Issue Type: Bug Components: wsdl2c tool Affects Versions: Current (Nightly) Reporter: Manjula Peiris When a module is engaged (programmatically or through axis2.xml) the generated code does not add those gloabally engaed module informations to service. To do this following code segment should be generated in the client stub populated service method. svc_ctx = axis2_svc_client_get_svc_ctx(svc_client, env); conf_ctx = axis2_svc_ctx_get_conf_ctx(svc_ctx, env); conf = axis2_conf_ctx_get_conf(conf_ctx, env); info = axis2_conf_get_phases_info(conf, env); -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2C-648) wsdl2c tool does not generate correct code when modules are engaed.
[ https://issues.apache.org/jira/browse/AXIS2C-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manjula Peiris updated AXIS2C-648: -- Description: When a module is engaged (programmatically or through axis2.xml) the generated code does not add those gloabally engaed module informations to service. To do this following code segment should be generated in the client stub populated service method. svc_ctx = axis2_svc_client_get_svc_ctx(svc_client, env); conf_ctx = axis2_svc_ctx_get_conf_ctx(svc_ctx, env); conf = axis2_conf_ctx_get_conf(conf_ctx, env); info = axis2_conf_get_phases_info(conf, env); and axis2_phases_info_set_op_phases(info, env, op); for each operation. was: When a module is engaged (programmatically or through axis2.xml) the generated code does not add those gloabally engaed module informations to service. To do this following code segment should be generated in the client stub populated service method. svc_ctx = axis2_svc_client_get_svc_ctx(svc_client, env); conf_ctx = axis2_svc_ctx_get_conf_ctx(svc_ctx, env); conf = axis2_conf_ctx_get_conf(conf_ctx, env); info = axis2_conf_get_phases_info(conf, env); wsdl2c tool does not generate correct code when modules are engaed. --- Key: AXIS2C-648 URL: https://issues.apache.org/jira/browse/AXIS2C-648 Project: Axis2-C Issue Type: Bug Components: wsdl2c tool Affects Versions: Current (Nightly) Reporter: Manjula Peiris When a module is engaged (programmatically or through axis2.xml) the generated code does not add those gloabally engaed module informations to service. To do this following code segment should be generated in the client stub populated service method. svc_ctx = axis2_svc_client_get_svc_ctx(svc_client, env); conf_ctx = axis2_svc_ctx_get_conf_ctx(svc_ctx, env); conf = axis2_conf_ctx_get_conf(conf_ctx, env); info = axis2_conf_get_phases_info(conf, env); and axis2_phases_info_set_op_phases(info, env, op); for each operation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2C-647) axis2_engine_create_fault_msg_ctx() function does not create proper soap fault
[ https://issues.apache.org/jira/browse/AXIS2C-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahan Gamage resolved AXIS2C-647. - Resolution: Fixed Change the function to take fault code and reason and create a proper soap and set to the fault msg_ctx axis2_engine_create_fault_msg_ctx() function does not create proper soap fault -- Key: AXIS2C-647 URL: https://issues.apache.org/jira/browse/AXIS2C-647 Project: Axis2-C Issue Type: Bug Affects Versions: Current (Nightly) Reporter: Sahan Gamage Inside the axis2_engine_create_fault_msg_ctx() function only creates a soap envelope, but not a fault part. We need to change the function prototype to get at least the fault code and reason and then create the proper soap fault. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (AXIS2-2992) Issues in ADBXMLStreamReaderImpl when data is associated with DOOM and MTOM
[ https://issues.apache.org/jira/browse/AXIS2-2992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe reassigned AXIS2-2992: Assignee: Amila Chinthaka Suriarachchi Issues in ADBXMLStreamReaderImpl when data is associated with DOOM and MTOM --- Key: AXIS2-2992 URL: https://issues.apache.org/jira/browse/AXIS2-2992 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: adb Affects Versions: 1.2 Reporter: Dimuthu Leelarathne Assignee: Amila Chinthaka Suriarachchi Priority: Critical To create the situation 1) Client must be code generated 2) Rampart must be engaged 3) MTOM must be expected out of the message. In this situation the Problem is * When converting to DOOM we use StAXBuilder and ADBXMLStreamReaderImpl to create the DOM object. But isDataHandlerAware method retuns false and isBinary method returns false. Because of this OMText Node's isOptimized value is not set. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (AXIS2-2987) The method fromString(XMLStreamReader, String, String) in the type AttrType_purpose_type0.Factory is not applicable for the arguments (String, String)
[ https://issues.apache.org/jira/browse/AXIS2-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe reassigned AXIS2-2987: Assignee: Amila Chinthaka Suriarachchi The method fromString(XMLStreamReader, String, String) in the type AttrType_purpose_type0.Factory is not applicable for the arguments (String, String) -- Key: AXIS2-2987 URL: https://issues.apache.org/jira/browse/AXIS2-2987 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.2, nightly Environment: Windows XP Service Pack2 Rational Application Developer v7.0.0.2 java version 1.5.0 Java(TM) 2 Runtime Environment, Standard Edition (build pwi32devifx-20070323 (if ix 117674: SR4 + 116644 + 114941 + 116110 + 114881)) IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32 j9vmwi3223ifx-2007 0323 (JIT enabled) J9VM - 20070322_12058_lHdSMR JIT - 20070109_1805ifx3_r8 GC - WASIFIX_2007) JCL - 20070131 Reporter: Josh Assignee: Amila Chinthaka Suriarachchi Using the XLiff v1.1 XSD http://www.oasis-open.org/committees/xliff/documents/xliff-core-1.1.xsd Generate Java classes using org.apache.axis2.schema.XSD2Java When try to compile generate Java code in RAD, receive the following compile errors The method fromString(XMLStreamReader, String, String) in the type AttrType_purpose_type0.Factory is not applicable for the arguments (String, String)Test/_1/_1/document/xliff/tc/names/oasis AttrType_purpose.java line 3201184795630816 19863 The method fromString(XMLStreamReader, String, String) in the type Lang_type0.Factory is not applicable for the arguments (String, String) Test/_1/_1/document/xliff/tc/names/oasisElemType_altTrans.java line 1589 1184795630691 19601 The method fromString(XMLStreamReader, String, String) in the type Lang_type0.Factory is not applicable for the arguments (String, String) Test/_1/_1/document/xliff/tc/names/oasisElemType_altTrans.java line 1594 1184795630691 19602 The method fromString(XMLStreamReader, String, String) in the type Lang_type0.Factory is not applicable for the arguments (String, String) Test/_1/_1/document/xliff/tc/names/oasisElemType_note.java line 4921184795630378 18653 The method fromString(XMLStreamReader, String, String) in the type Lang_type0.Factory is not applicable for the arguments (String, String) Test/_1/_1/document/xliff/tc/names/oasisElemType_note.java line 4971184795630378 18654 The method fromString(XMLStreamReader, String, String) in the type Lang_type0.Factory is not applicable for the arguments (String, String) Test/_1/_1/document/xliff/tc/names/oasisElemType_prop.java line 4821184795630316 18493 The method fromString(XMLStreamReader, String, String) in the type Lang_type0.Factory is not applicable for the arguments (String, String) Test/_1/_1/document/xliff/tc/names/oasisElemType_prop.java line 4871184795630316 18494 The method fromString(XMLStreamReader, String, String) in the type Lang_type0.Factory is not applicable for the arguments (String, String) Test/_1/_1/document/xliff/tc/names/oasisElemType_source.javaline 5741184795630300 18444 The method fromString(XMLStreamReader, String, String) in the type Lang_type0.Factory is not applicable for the arguments (String, String) Test/_1/_1/document/xliff/tc/names/oasisElemType_source.javaline 5791184795630300 18445 The method fromString(XMLStreamReader, String, String) in the type Lang_type0.Factory is not applicable for the arguments (String, String) Test/_1/_1/document/xliff/tc/names/oasisElemType_target.javaline 8101184795630285 18397 The method fromString(XMLStreamReader, String, String) in the type Lang_type0.Factory is not applicable for the arguments (String, String) Test/_1/_1/document/xliff/tc/names/oasisElemType_target.javaline 8151184795630285 18398 The method fromString(XMLStreamReader, String, String) in the type Lang_type0.Factory is not applicable for the arguments (String, String) Test/_1/_1/document/xliff/tc/names/oasisXliff.java line 519 1184795630097 18025 The method fromString(XMLStreamReader, String, String) in the type Lang_type0.Factory is not applicable for the arguments (String, String) Test/_1/_1/document/xliff/tc/names/oasisXliff.java line 524 1184795630097 18026 -- This message is automatically generated by JIRA. -
[jira] Reopened: (AXIS2-3003) Unable to engage addressing at client side, want to know the specific location of addressing.mar in the project
[
https://issues.apache.org/jira/browse/AXIS2-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
tommy reopened AXIS2-3003:
--
public static void main(java.lang.String args[]) {
try {
StockQuoteServiceStockQuoteServiceHttpportStub stub =
new StockQuoteServiceStockQuoteServiceHttpportStub(
http://localhost:6080/axis2/services/StockQuoteService;);
stub._getServiceClient().engageModule(addressing);
stub._getServiceClient().getOptions().setUseSeparateListener(true);
getPrice(stub);
update(stub);
} catch (Exception e) {
e.printStackTrace();
System.err.println(\n\n\n);
}
}
/* fire and forget */
public static void update(
StockQuoteServiceStockQuoteServiceHttpportStub stub) {
try {
StockQuoteServiceStockQuoteServiceHttpportStub.Update
req = new StockQuoteServiceStockQuoteServiceHttpportStub.Update();
StockQuoteServiceStockQuoteServiceHttpportCallbackHandler callback = new
StockQuoteServiceStockQuoteServiceHttpportCallbackHandler() {
};
req.setSymbol(ABC);
req.setPrice(42.35);
stub.startupdate(req, callback);
System.err.println(done);
} catch (Exception e) {
e.printStackTrace();
System.err.println(\n\n\n);
}
}
/* two way call/receive */
public static void getPrice(
StockQuoteServiceStockQuoteServiceHttpportStub stub) {
try {
StockQuoteServiceStockQuoteServiceHttpportStub.GetPrice
req = new StockQuoteServiceStockQuoteServiceHttpportStub.GetPrice();
StockQuoteServiceStockQuoteServiceHttpportCallbackHandler callback = new
StockQuoteServiceStockQuoteServiceHttpportCallbackHandler() {
public void
receiveResultgetPrice(StockQuoteServiceStockQuoteServiceHttpportStub.GetPriceResponse
result) {
System.out.println(result.get_return());
}
};
req.setSymbol(ABC);
stub.startgetPrice(req, callback);
} catch (Exception e) {
e.printStackTrace();
System.err.println(\n\n\n);
}
}
I tried Axis2 1.3 RC, but it didn't work! The problem is still there, it seems
like nothing changed, but 'stub._getServiceClient().engageModule(new
QName(addressing));' was changed to
'stub._getServiceClient().engageModule(addressing);';
Unable to engage addressing at client side, want to know the specific
location of addressing.mar in the project
---
Key: AXIS2-3003
URL: https://issues.apache.org/jira/browse/AXIS2-3003
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: Addressing
Affects Versions: 1.2
Environment: winxp, axis2
Reporter: tommy
I got the same problem with Unable to engage module : addressing , I've
added the line 'stub._getServiceClient().engageModule(new
QName(addressing));' in my client codes. Could anyone be kind to tell where
I should place addressing-1.2.mar in my class-path. I copyed it everywhere it
could be, but the program still cannot recognize the .mar file in my project.
Ask for help, thanks in advance.
[ Show » ] tommy - [22/Jul/07 11:28 PM ] I got the same problem with Unable
to engage module : addressing , I've added the line
'stub._getServiceClient().engageModule(new QName(addressing));' in my
client codes. Could anyone be kind to tell where I should place
addressing-1.2.mar in my class-path. I copyed it everywhere it could be, but
the program still cannot recognize the .mar file in my project. Ask for help,
thanks in advance.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (AXIS2-2995) Codegen bug with different namespaces (including proposed fix)
[ https://issues.apache.org/jira/browse/AXIS2-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe reassigned AXIS2-2995: Assignee: Amila Chinthaka Suriarachchi Codegen bug with different namespaces (including proposed fix) -- Key: AXIS2-2995 URL: https://issues.apache.org/jira/browse/AXIS2-2995 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.2 Environment: I already changed the JAXB RI jars to 2.1.3, but this isn't the problem Reporter: Michael Pollmeier Assignee: Amila Chinthaka Suriarachchi Attachments: wsdl.zip Axis codegen has a problem when there are objects with the same name in different namespaces. I will upload a sample wsdl. If you use wsdl2java to create a service like this: wsdl2java -uri EVBService-2.0.1.0.wsdl -ss -sd -d jaxbri -o service you will get an exception on console: Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang. reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:256) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.extension.JAXBRIExtension.engage(JAXBRIExtension.java:109) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:209) ... 2 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.axis2.wsdl.codegen.extension.JAXBRIExtension.engage(JAXBRIExtension.java:98) ... 3 more Caused by: java.lang.RuntimeException: java.lang.NullPointerException at org.apache.axis2.jaxbri.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:126) ... 8 more Caused by: java.lang.NullPointerException at org.apache.axis2.jaxbri.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:105) ... 8 more ... which seems to be an optimizable design, because you do not see the real exception. When I debugged the code I got the real exception: org.xml.sax.SAXParseException: A class/interface with the same name net.bipro.www.namespace.evb.CTStatusResponse is already in use. Use a class customization to resolve this conflict. I saw that JAXBs XJC compiler does not have any problems with our schema, so there had to be a difference of parameters between xjc batch and axis2 codegen. So I found out that if you comment out the statement sc.setDefaultPackageName(pkg); in CodeGenerationUtility:processSchemas(), everything is generated just fine! This might have some side effects, so someone who really knows what happens down the code should have a look at this. Maybe a solution would be to have another command line parameter for wsdl2java to not set the default package. There is another, smaller problem which occurs when you use my bugfix: when the code is generated, the message receiver class cannot be compiled because of an obviously wrong code: the method toOM() needs three parameters, but only two are submitted: toOM(e.getFaultMessage(),false)); If you change it to toOM(e.getFaultMessage(), getSOAPFactory(msgContext), false), everything can be compiled and works. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2995) Codegen bug with different namespaces (including proposed fix)
[ https://issues.apache.org/jira/browse/AXIS2-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514859 ] Deepal Jayasinghe commented on AXIS2-2995: -- Amila , Do you consider this as a blocker ? Thanks Deepal Codegen bug with different namespaces (including proposed fix) -- Key: AXIS2-2995 URL: https://issues.apache.org/jira/browse/AXIS2-2995 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.2 Environment: I already changed the JAXB RI jars to 2.1.3, but this isn't the problem Reporter: Michael Pollmeier Assignee: Amila Chinthaka Suriarachchi Attachments: wsdl.zip Axis codegen has a problem when there are objects with the same name in different namespaces. I will upload a sample wsdl. If you use wsdl2java to create a service like this: wsdl2java -uri EVBService-2.0.1.0.wsdl -ss -sd -d jaxbri -o service you will get an exception on console: Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang. reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:256) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.extension.JAXBRIExtension.engage(JAXBRIExtension.java:109) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:209) ... 2 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.axis2.wsdl.codegen.extension.JAXBRIExtension.engage(JAXBRIExtension.java:98) ... 3 more Caused by: java.lang.RuntimeException: java.lang.NullPointerException at org.apache.axis2.jaxbri.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:126) ... 8 more Caused by: java.lang.NullPointerException at org.apache.axis2.jaxbri.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:105) ... 8 more ... which seems to be an optimizable design, because you do not see the real exception. When I debugged the code I got the real exception: org.xml.sax.SAXParseException: A class/interface with the same name net.bipro.www.namespace.evb.CTStatusResponse is already in use. Use a class customization to resolve this conflict. I saw that JAXBs XJC compiler does not have any problems with our schema, so there had to be a difference of parameters between xjc batch and axis2 codegen. So I found out that if you comment out the statement sc.setDefaultPackageName(pkg); in CodeGenerationUtility:processSchemas(), everything is generated just fine! This might have some side effects, so someone who really knows what happens down the code should have a look at this. Maybe a solution would be to have another command line parameter for wsdl2java to not set the default package. There is another, smaller problem which occurs when you use my bugfix: when the code is generated, the message receiver class cannot be compiled because of an obviously wrong code: the method toOM() needs three parameters, but only two are submitted: toOM(e.getFaultMessage(),false)); If you change it to toOM(e.getFaultMessage(), getSOAPFactory(msgContext), false), everything can be compiled and works. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (AXIS2-2993) the async message receiver could use NIO
[ https://issues.apache.org/jira/browse/AXIS2-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe reassigned AXIS2-2993: Assignee: Deepal Jayasinghe the async message receiver could use NIO Key: AXIS2-2993 URL: https://issues.apache.org/jira/browse/AXIS2-2993 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: kernel Affects Versions: 1.2 Environment: all Reporter: Michele Mazzucco Assignee: Deepal Jayasinghe AbstractMessageReceiver does the job of deciding (based on the AbstractMessageReceiver.DO_ASYNC property) whether or not to spin up a thread to do the work of invokeBusinessLogic(MessageContext). What about using NIO instead? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2990) WSDL port address is not correctly generated for machines having multiple network interfaces
[ https://issues.apache.org/jira/browse/AXIS2-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514861 ] Deepal Jayasinghe commented on AXIS2-2990: -- Try to use hostname parameter , then you will be able to generate the wsdl with the corrcte host name , then no need to wory abt the IP addresses WSDL port address is not correctly generated for machines having multiple network interfaces Key: AXIS2-2990 URL: https://issues.apache.org/jira/browse/AXIS2-2990 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: wsdl Affects Versions: 1.2 Environment: Windows Reporter: Haneef Ali WSDL portAddress is filled with machines IP address. The code to get the IP address org.apache.axis2.transport.http.sever.HTTPUtils.getIpAddress() always takes the first available network interfaces ip address. This may not work in machine which has vmvare installed, or machines having multiple network interfaces or just a laptop which has wireless and wired lan. I believe that Correct way to do that it, is to use the hostName and resolve it to ipAddress. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (AXIS2-2998) custom handler is not executed
[ https://issues.apache.org/jira/browse/AXIS2-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe reassigned AXIS2-2998: Assignee: Deepal Jayasinghe custom handler is not executed -- Key: AXIS2-2998 URL: https://issues.apache.org/jira/browse/AXIS2-2998 Project: Axis 2.0 (Axis2) Issue Type: Bug Environment: linux 2.6.14, java 1.5, axis2 1.1.1, tomcat 5.5.20 Reporter: Michele Mazzucco Assignee: Deepal Jayasinghe Fix For: 1.1.1 Attachments: axis2_logs.log, catalina.out, module.xml, node_axis2.xml, qosp_debug.log, QOSPRequestURIBasedDispatcher.java Scenario: I have a custom handler which replaces RequestURIBasedDispatcher and deploys services on the fly from a remote repository. Problem: it used to work with axis2 1.1, but since using axis2 1.1.1 it's not called any more (it looks like there are no errors, apart that the request fails because the service is not available). No log statements from my custom handler are printed, which makes me think that the handler is not called. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3004) Turn on WSDL 2.0 validation which is turned off by default
[ https://issues.apache.org/jira/browse/AXIS2-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514862 ] Deepal Jayasinghe commented on AXIS2-3004: -- Well , if the test pases and if you are sure that you are not going to break anything then please go ahead and commit the changes Turn on WSDL 2.0 validation which is turned off by default -- Key: AXIS2-3004 URL: https://issues.apache.org/jira/browse/AXIS2-3004 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: kernel Affects Versions: 1.3 Reporter: Keith Godwin Chapman Assignee: Keith Godwin Chapman Fix For: 1.3 WSDL 2.0 validation is turned off by default in Woden. It'll be good if we can turn this on. I will check this into trunk. Thanks Chathura for pointing this out. Deepal can we check this into the 1.3 branch too? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3002) Axis 1.3RC2 does not work properly on websphere
[ https://issues.apache.org/jira/browse/AXIS2-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514866 ] Charitha Kankanamge commented on AXIS2-3002: Deepal, I deployed Axis2-1.3.war on WebSphere 6.1. As you can see in the attached screen shot, happyaxis page says the installation is succcessful. However when I issued ?wsdl2 of version service, got following errors. Error Message: Error reported: 404 Error Code: 404 Target Servlet: AxisServlet Error Stack: com.ibm.ws.webcontainer.webapp.WebAppErrorReport: Error reported: 404 at com.ibm.ws.webcontainer.webapp.WebAppDispatcherContext.sendError(WebAppDispatcherContext.java:532) at com.ibm.ws.webcontainer.srt.SRTServletResponse.sendError(SRTServletResponse.java:909) at com.ibm.ws.webcontainer.srt.SRTServletResponse.sendError(SRTServletResponse.java:892) at org.apache.axis2.transport.http.ListingAgent.processListService(ListingAgent.java:223) at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:224) at javax.servlet.http.HttpServlet.service(HttpServlet.java:743) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:966) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478) at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:463) at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:92) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:744) at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1425) at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:92) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:465) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:394) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:274) at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214) at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113) at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:152) at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:213) at com.ibm.io.async.AbstractAsyncFuture.fireCompletionActions(AbstractAsyncFuture.java:195) at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136) at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:193) at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:725) at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:847) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1498) Error Page Exception: Error Message: SRVE0199E: OutputStream already obtained Error Code: 0 Target Servlet: null Error Stack: java.lang.IllegalStateException: SRVE0199E: OutputStream already obtained at com.ibm.ws.webcontainer.srt.SRTServletResponse.getWriter(SRTServletResponse.java:528) at org.apache.jasper.runtime.JspWriterImpl.initOut(JspWriterImpl.java:187) at org.apache.jasper.runtime.JspWriterImpl.flushBuffer(JspWriterImpl.java:175) at org.apache.jasper.runtime.PageContextImpl.release(PageContextImpl.java:225) at org.apache.jasper.runtime.JspFactoryImpl.internalReleasePageContext(JspFactoryImpl.java:170) at org.apache.jasper.runtime.JspFactoryImpl.releasePageContext(JspFactoryImpl.java:138) at com.ibm._jsp._error404._jspService(_error404.java:81) at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:85) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:966) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478) at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:463) at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:115) at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.handleRequest(AbstractJSPExtensionServletWrapper.java:168) at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.include(WebAppRequestDispatcher.java:606) at com.ibm.ws.webcontainer.webapp.WebApp.sendError(WebApp.java:2676) at com.ibm.ws.webcontainer.webapp.WebAppDispatcherContext.sendError(WebAppDispatcherContext.java:540) at com.ibm.ws.webcontainer.srt.SRTServletResponse.sendError(SRTServletResponse.java:909) at
[jira] Updated: (AXIS2-3002) Axis 1.3RC2 does not work properly on websphere
[ https://issues.apache.org/jira/browse/AXIS2-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charitha Kankanamge updated AXIS2-3002: --- Attachment: Websphere-axis2.JPG Attached screen shot. Axis 1.3RC2 does not work properly on websphere --- Key: AXIS2-3002 URL: https://issues.apache.org/jira/browse/AXIS2-3002 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Affects Versions: 1.3 Environment: Websphere 6.0.2 Reporter: Kent Watanabe Assignee: Charitha Kankanamge Attachments: Websphere-axis2.JPG The new axis2.war does not work properly on websphere. There are problems with the wsdl2 generation, and the wsdl 1.1 genaration. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3003) Unable to engage addressing at client side, want to know the specific location of addressing.mar in the project
[ https://issues.apache.org/jira/browse/AXIS2-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514868 ] Deepal Jayasinghe commented on AXIS2-3003: -- If you do the following then it should work (I tested and it worked) - Download Axis2 1.3 RC2 - And drop the jar file into class path. - The run you code. Unable to engage addressing at client side, want to know the specific location of addressing.mar in the project --- Key: AXIS2-3003 URL: https://issues.apache.org/jira/browse/AXIS2-3003 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: Addressing Affects Versions: 1.2 Environment: winxp, axis2 Reporter: tommy I got the same problem with Unable to engage module : addressing , I've added the line 'stub._getServiceClient().engageModule(new QName(addressing));' in my client codes. Could anyone be kind to tell where I should place addressing-1.2.mar in my class-path. I copyed it everywhere it could be, but the program still cannot recognize the .mar file in my project. Ask for help, thanks in advance. [ Show » ] tommy - [22/Jul/07 11:28 PM ] I got the same problem with Unable to engage module : addressing , I've added the line 'stub._getServiceClient().engageModule(new QName(addressing));' in my client codes. Could anyone be kind to tell where I should place addressing-1.2.mar in my class-path. I copyed it everywhere it could be, but the program still cannot recognize the .mar file in my project. Ask for help, thanks in advance. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2]Secure + Reliable with SMTP issue
+1 ... I think we need to ship an Axis2 that can compose nicely and easily with Rampart and Sandesha to make secure+RM work correctly for HTTP and SMTP (basically for all transports we support). Sanjiva. Deepal Jayasinghe wrote: Hi Dims, No the issues is client side when someone tries to use RM+ Security then he has to go and change axis2.xml. Other thing is for security to work correctly it is required to have addressing based dispatcher before security handlers. And using a security is common case so I think default axis2.xml should support that. Thanks Deepal Deepal, IMHO, This can be documented and fixed post 1.3 I can see folks who are working on an advanced scenario comfortable with a custom axis2.xml. thanks, dims On 7/23/07, Deepal Jayasinghe [EMAIL PROTECTED] wrote: Hi all. In oder to get security to work in one way transport (like SMTP) we need to have addressing around. In simple word the only way to dispatch service and operation is using addressing. According to my knowledge addressing headers will not encrypt in the practical scenario though it is possible in theoretically , therefore we can safely assume that one can sign wsa headers but not encrypt. So we can run addressing handlers and addressing based dispatchers before security handlers. If someone has intercepted the message when the addressing headers has signed , then when it come to security handlers it will identify that and throw exception . So whether we run addressing before or after the security the behavior will be the same . So we can move addressing handlers before security handlers , next the question is to where do we move them . In this case we have two options Option 1: Move PreDispatch phase before security phase (since all the addressing handlers in the PreDispatch) Option 2 : Introduce new phase called Addressing before the security phase and keep the PreDispatch has it is If we do the first option then we are breaking the backward compatibility (That is why I reverted my change 558707) , and semantically the phase will not the PreDispatch since it is before the security phase (rather PreSecurity). If we do the second option we will not break the backward compatibility and will introduce a very meaningfully phase to deploy addressing handlers. Since this is going to be a configuration file change , I would like to do that before 1.3. And the important thing is we can not get security + addressing working in SMTP or any other one way transport without moving addressing handlers. So if we are doing so we need to do it properly , I personally think the option 2 is the most suitable option and I am +1 for going forward with option2 and implement that for 1.3 Thanks Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Sanjiva Weerawarana, Ph.D. Founder Director; Lanka Software Foundation; http://www.opensource.lk/ Founder, Chairman CEO; WSO2, Inc.; http://www.wso2.com/ Director; Open Source Initiative; http://www.opensource.org/ Member; Apache Software Foundation; http://www.apache.org/ Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3004) Turn on WSDL 2.0 validation which is turned off by default
[ https://issues.apache.org/jira/browse/AXIS2-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Godwin Chapman updated AXIS2-3004: Attachment: patch.txt Patch that turns validation on. Turn on WSDL 2.0 validation which is turned off by default -- Key: AXIS2-3004 URL: https://issues.apache.org/jira/browse/AXIS2-3004 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: kernel Affects Versions: 1.3 Reporter: Keith Godwin Chapman Assignee: Keith Godwin Chapman Fix For: 1.3 Attachments: patch.txt WSDL 2.0 validation is turned off by default in Woden. It'll be good if we can turn this on. I will check this into trunk. Thanks Chathura for pointing this out. Deepal can we check this into the 1.3 branch too? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3001) Problem in 1.3 RC with deserialization of java.util.Date objects that are DateTime formatted.
[ https://issues.apache.org/jira/browse/AXIS2-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514906 ] Amila Chinthaka Suriarachchi commented on AXIS2-3001: - see http://www.w3.org/TR/xmlschema-2/#date the xml date is defined to only have date parts Problem in 1.3 RC with deserialization of java.util.Date objects that are DateTime formatted. - Key: AXIS2-3001 URL: https://issues.apache.org/jira/browse/AXIS2-3001 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: adb Affects Versions: 1.3 Environment: Axis 1.3 RC2, JDK 1.6 on Linux Reporter: Sathija Pavuluri Assignee: Amila Chinthaka Suriarachchi Priority: Blocker This bug was introduced after the fix that was made for jira AXIS2-2701. I had originally written my comment against 2701 but since the bug is marked as resolved, thought this new issue should be tracked separately. The fix for AXIS2-2701 makes it impossible for java.util.Date objects to be deserialized when the date is datetime formatted (i.e. -mm-dd hh:mm:ss). It now only works for date format objects (i.e. -mm-dd) For example I have an object with attribute: java.util.Date timeStarted; The element in the response looks like this: ax26:timeStarted2007-07-23T13:20:46.861Z/ax26:timeStarted The deserialization of this element fails with this exception: java.lang.RuntimeException: In valid string sufix at org.apache.axis2.databinding.utils.ConverterUtil.convertToDate(ConverterUtil.java:378) at org.apache.axis2.databinding.typemapping.SimpleTypeMapper.makeDate(SimpleTypeMapper.java:304) at org.apache.axis2.databinding.typemapping.SimpleTypeMapper.getSimpleTypeObject(SimpleTypeMapper.java:117) at org.apache.axis2.databinding.utils.BeanUtil.deserialize(BeanUtil.java:364) at org.apache.axis2.databinding.utils.BeanUtil.processObject(BeanUtil.java:644) at org.apache.axis2.databinding.utils.BeanUtil.ProcessElement(BeanUtil.java:592) at org.apache.axis2.databinding.utils.BeanUtil.deserialize(BeanUtil.java:528) Looking at the code, it seems like the ConverterUtil expects the Date object to be only of -mm-dd format. It fails in the case when Date is -mm-dd hh:mm:ss formatted? Thanks, Sathija. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to deploy exploded .aar under axis2?
Is it possible to deploy an exploded .aar under axis2? If so, how? Do I simply unpack the file webapps/axis2/WEB-INF/services/my-service-1.0.aar into webapps/axis2/WEB-INF/services/my-service-1.0/... ? Kind regards, -- -- Gertjan van Oosten, [EMAIL PROTECTED], West Consulting B.V., +31 15 2191 600 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to deploy exploded .aar under axis2?
Is it possible to deploy an exploded .aar under axis2? If so, how? Do I simply unpack the file webapps/axis2/WEB-INF/services/my-service-1.0.aar into webapps/axis2/WEB-INF/services/my-service-1.0/... Yes that is correct webapps/axis2/WEB-INF/services/my-service-1.0/ /META-INF services.xml ? Kind regards, -- Thanks, Deepal The highest tower is built one brick at a time - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-3004) Turn on WSDL 2.0 validation which is turned off by default
[ https://issues.apache.org/jira/browse/AXIS2-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Godwin Chapman resolved AXIS2-3004. - Resolution: Fixed Applying patch attached here. This throws an Exception only if there is a fatal error. Else it prints out the warnings and errors. Fixed in revision 558957. Applied patch to both branch and trunk. Turn on WSDL 2.0 validation which is turned off by default -- Key: AXIS2-3004 URL: https://issues.apache.org/jira/browse/AXIS2-3004 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: kernel Affects Versions: 1.3 Reporter: Keith Godwin Chapman Assignee: Keith Godwin Chapman Fix For: 1.3 Attachments: patch.txt WSDL 2.0 validation is turned off by default in Woden. It'll be good if we can turn this on. I will check this into trunk. Thanks Chathura for pointing this out. Deepal can we check this into the 1.3 branch too? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3005) [7/12/07 9:09:32:923 CEST] 82d122f SRTServletRes W WARNING: Cannot set header. Response already committed. is logged when ever a Axis2 based webservice is called
[7/12/07 9:09:32:923 CEST] 82d122f SRTServletRes W WARNING: Cannot set header. Response already committed. is logged when ever a Axis2 based webservice is called -- Key: AXIS2-3005 URL: https://issues.apache.org/jira/browse/AXIS2-3005 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.2 Environment: WebSphere 5.1.1.14 HP UX operating system Reporter: Muhammad Hamza Hakim Priority: Minor We have implemented Web Services using Axis2 and facing the below mentioned problem when ever the a request is made to Web Service: We now installed WebSphere 5.1.1.14 In the logs we still see below error-messages filling our logs. So the fixpack did not solve this issue. Can you please arrange that these messages do not appear anymore in the logs? [7/12/07 9:09:32:923 CEST] 82d122f SRTServletRes W WARNING: Cannot set header. Response already committed. Our Finding: WebSphere logs the warning message SRTServletRes W WARNING: Cannot set header. Response already committed. in SystemOut.log due to Axis2. Axis2 processes the incomming request sends the response and then tries to set a header property in response. Because at this point WebSphere has already committed the response so it logs a warning in the log. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] Shivantha Huruggamuwa
Hi All, Shivantha has been helping Axis2 for quite a while now, he has done a number of bug fixes in Axis2 IDEA plug-in. He has spend most his time on getting both Eclipse and IntelJ Idea plugins to consistent state. He has created a number of JIRAs and submitted more then 12 patches , so I think he has done more than enough to get Axis2 commit access. Here is my +1 for Shivantha as an Axis2 commiter. Thanks Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE][Axis2] Shivantha Huruggamuwa as an Axis2 commiter
Hi All, Shivantha has been helping Axis2 for quite a while now, he has done a number of bug fixes in Axis2 IDEA plug-in. He has spend most his time on getting both Eclipse and IntelJ Idea plugins to consistent state. He has created a number of JIRAs and submitted more then 12 patches , so I think he has done more than enough to get Axis2 commit access. Here is my +1 for Shivantha as an Axis2 commiter. Thanks Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2]Secure + Reliable with SMTP issue
I will introduce a new phase called Addressing and go forward , let's revert that if we found and issue. Thanks Deepal Sanjiva Weerawarana wrote: +1 ... I think we need to ship an Axis2 that can compose nicely and easily with Rampart and Sandesha to make secure+RM work correctly for HTTP and SMTP (basically for all transports we support). Sanjiva. Deepal Jayasinghe wrote: Hi Dims, No the issues is client side when someone tries to use RM+ Security then he has to go and change axis2.xml. Other thing is for security to work correctly it is required to have addressing based dispatcher before security handlers. And using a security is common case so I think default axis2.xml should support that. Thanks Deepal Deepal, IMHO, This can be documented and fixed post 1.3 I can see folks who are working on an advanced scenario comfortable with a custom axis2.xml. thanks, dims - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to deploy exploded .aar under axis2?
As quoted from Deepal Jayasinghe [EMAIL PROTECTED]: Is it possible to deploy an exploded .aar under axis2? If so, how? Do I simply unpack the file webapps/axis2/WEB-INF/services/my-service-1.0.aar into webapps/axis2/WEB-INF/services/my-service-1.0/... Yes that is correct webapps/axis2/WEB-INF/services/my-service-1.0/ /META-INF services.xml The .aar file contains more than just the services.xml of course, so I exploded the rest there as well (lib, classes). First of all, I get the same error I got before with my .aar file https://issues.apache.org/jira/browse/AXIS2-2889 but now for the directory: INFO: org.apache.axis2.deployment.DeploymentException: The my-service-1 service group name is not valid. If I then rename the directoy to my-service and restart Tomcat, Axis complains that: 24-Jul-2007 08:46:14 org.apache.axis2.deployment.ServiceDeployer deploy INFO: Deploying Web service: my-service 24-Jul-2007 08:46:15 org.apache.axis2.deployment.ServiceDeployer deploy SEVERE: The my-service service, which is not valid, caused Two services cannot have same name. A service with the MyFirstService name already exists in the system. org.apache.axis2.AxisFault: Two services cannot have same name. A service with the MyFirstService name already exists in the system. at org.apache.axis2.engine.AxisConfiguration.addToAllServicesMap(AxisConfiguration.java:356) at org.apache.axis2.description.AxisServiceGroup.addService(AxisServiceGroup.java:111) at org.apache.axis2.deployment.DeploymentEngine.fillServiceGroup(DeploymentEngine.java:490) at org.apache.axis2.deployment.DeploymentEngine.addServiceGroup(DeploymentEngine.java:453) at org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:82) at org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:137) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:551) at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:135) 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:116) at org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:271) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:78) at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:494) at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:414) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1105) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:932) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3917) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4201) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:904) at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:867) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:474) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1122) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1021) at org.apache.catalina.core.StandardHost.start(StandardHost.java:718) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442) at org.apache.catalina.core.StandardService.start(StandardService.java:450) at org.apache.catalina.core.StandardServer.start(StandardServer.java:709) at org.apache.catalina.startup.Catalina.start(Catalina.java:551) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at
Re: How to deploy exploded .aar under axis2?
Could you please send me the service archive file. Thanks Deepal As quoted from Deepal Jayasinghe [EMAIL PROTECTED]: Is it possible to deploy an exploded .aar under axis2? If so, how? Do I simply unpack the file webapps/axis2/WEB-INF/services/my-service-1.0.aar into webapps/axis2/WEB-INF/services/my-service-1.0/... Yes that is correct webapps/axis2/WEB-INF/services/my-service-1.0/ /META-INF services.xml The .aar file contains more than just the services.xml of course, so I exploded the rest there as well (lib, classes). First of all, I get the same error I got before with my .aar file https://issues.apache.org/jira/browse/AXIS2-2889 but now for the directory: INFO: org.apache.axis2.deployment.DeploymentException: The my-service-1 service group name is not valid. If I then rename the directoy to my-service and restart Tomcat, Axis - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [axis2] [Fwd: Jar version changes between Axis2 1.2 and Axis2 1.3RC2]
Fixed on 1_3 branch and trunk. Changed xercesImpl version to 2.8.1 Changed commons-io version to 1.2 Changed log4j version to 1.2.14 Thanks, sumedha On 7/24/07, Sanjiva Weerawarana [EMAIL PROTECTED] wrote: FYI. -- Sanjiva Weerawarana, Ph.D. Founder Director; Lanka Software Foundation; http://www.opensource.lk/ Founder, Chairman CEO; WSO2, Inc.; http://www.wso2.com/ Director; Open Source Initiative; http://www.opensource.org/ Member; Apache Software Foundation; http://www.apache.org/ Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/ -- Forwarded message -- From: Alick Buckley [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Tue, 24 Jul 2007 11:26:25 +1000 Subject: Jar version changes between Axis2 1.2 and Axis2 1.3RC2 Hi Guys, Doing a quick compare of axis2-1.2.zip and axis2-1.3RC2-bin.zip download lib directory jar files. http://ws.apache.org/axis2/download.cgi You have gone from xercesImpl-2.8.1.jar back to xercesImpl-2.6.2.jar commons-io-1.2.jar back to commons-io-1.1.jar You have included log4j-1.2.13.jar, the latest is 1.2.14 http://logging.apache.org/log4j/docs/download.html axis2-1.3RC2.txt axis2-1.2.txt regards *Alick Buckley*** LANSA Research and Development LANSA Pty Ltd Phone: +61289070243 *http://www.lansa.com* *mailto:Alick.Buckley@ Alick.Buckley@lansa.com.au* - 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]
Re: How to deploy exploded .aar under axis2?
As quoted from Deepal jayasinghe [EMAIL PROTECTED]: Could you please send me the service archive file. I'm afraid not: first of all it's over 25 MBytes, and second it contains proprietary stuff that I'm not allowed to send out. :-( Regards, -- -- Gertjan van Oosten, [EMAIL PROTECTED], West Consulting B.V., +31 15 2191 600 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to deploy exploded .aar under axis2?
Can you post your services.xml? The error seems to say that you have two services with the same name. Sanjiva. Gertjan van Oosten wrote: As quoted from Deepal Jayasinghe [EMAIL PROTECTED]: Is it possible to deploy an exploded .aar under axis2? If so, how? Do I simply unpack the file webapps/axis2/WEB-INF/services/my-service-1.0.aar into webapps/axis2/WEB-INF/services/my-service-1.0/... Yes that is correct webapps/axis2/WEB-INF/services/my-service-1.0/ /META-INF services.xml The .aar file contains more than just the services.xml of course, so I exploded the rest there as well (lib, classes). First of all, I get the same error I got before with my .aar file https://issues.apache.org/jira/browse/AXIS2-2889 but now for the directory: INFO: org.apache.axis2.deployment.DeploymentException: The my-service-1 service group name is not valid. If I then rename the directoy to my-service and restart Tomcat, Axis complains that: 24-Jul-2007 08:46:14 org.apache.axis2.deployment.ServiceDeployer deploy INFO: Deploying Web service: my-service 24-Jul-2007 08:46:15 org.apache.axis2.deployment.ServiceDeployer deploy SEVERE: The my-service service, which is not valid, caused Two services cannot have same name. A service with the MyFirstService name already exists in the system. org.apache.axis2.AxisFault: Two services cannot have same name. A service with the MyFirstService name already exists in the system. at org.apache.axis2.engine.AxisConfiguration.addToAllServicesMap(AxisConfiguration.java:356) at org.apache.axis2.description.AxisServiceGroup.addService(AxisServiceGroup.java:111) at org.apache.axis2.deployment.DeploymentEngine.fillServiceGroup(DeploymentEngine.java:490) at org.apache.axis2.deployment.DeploymentEngine.addServiceGroup(DeploymentEngine.java:453) at org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:82) at org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:137) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:551) at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:135) 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:116) at org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:271) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:78) at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:494) at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:414) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1105) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:932) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3917) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4201) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:904) at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:867) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:474) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1122) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1021) at org.apache.catalina.core.StandardHost.start(StandardHost.java:718) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442) at org.apache.catalina.core.StandardService.start(StandardService.java:450) at org.apache.catalina.core.StandardServer.start(StandardServer.java:709) at org.apache.catalina.startup.Catalina.start(Catalina.java:551) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at
Re: How to deploy exploded .aar under axis2?
As quoted from Sanjiva Weerawarana [EMAIL PROTECTED]: Can you post your services.xml? The error seems to say that you have two services with the same name. No, it does work if I use the .aar file unexploded. And anyway, the fact that it is reproducable by exploding Axis' own version-1.3-RC2.aar says it all, no? Regards, -- -- Gertjan van Oosten, [EMAIL PROTECTED], West Consulting B.V., +31 15 2191 600 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2]Secure + Reliable with SMTP issue
+1 on Adding a new phase and moving addressing BasedDistpacher before the Security. In this way we can support operational level security polices. I think it is very difficult for a new person to debug and find this problem (handler chain order) if we have shif it in wrong way. Since one of the objectives of Axis2 1.3 to provide a Sandesha and rampart compatible Axis2 release it would be nice to have this for Axis2 1.3. Thanks Amila. On 7/24/07, Deepal Jayasinghe [EMAIL PROTECTED] wrote: I will introduce a new phase called Addressing and go forward , let's revert that if we found and issue. Thanks Deepal Sanjiva Weerawarana wrote: +1 ... I think we need to ship an Axis2 that can compose nicely and easily with Rampart and Sandesha to make secure+RM work correctly for HTTP and SMTP (basically for all transports we support). Sanjiva. Deepal Jayasinghe wrote: Hi Dims, No the issues is client side when someone tries to use RM+ Security then he has to go and change axis2.xml. Other thing is for security to work correctly it is required to have addressing based dispatcher before security handlers. And using a security is common case so I think default axis2.xml should support that. Thanks Deepal Deepal, IMHO, This can be documented and fixed post 1.3 I can see folks who are working on an advanced scenario comfortable with a custom axis2.xml. thanks, dims - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Amila Suriarachchi, WSO2 Inc.
Re: [VOTE][Axis2] Shivantha Huruggamuwa as an Axis2 commiter
Here is my +1... thanks, Thilina On 7/24/07, Deepal Jayasinghe [EMAIL PROTECTED] wrote: Hi All, Shivantha has been helping Axis2 for quite a while now, he has done a number of bug fixes in Axis2 IDEA plug-in. He has spend most his time on getting both Eclipse and IntelJ Idea plugins to consistent state. He has created a number of JIRAs and submitted more then 12 patches , so I think he has done more than enough to get Axis2 commit access. Here is my +1 for Shivantha as an Axis2 commiter. Thanks Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thilina Gunarathne - http://www.wso2.com - http://thilinag.blogspot.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][Axis2] Shivantha Huruggamuwa as an Axis2 commiter
+1 Milinda On 7/24/07, Thilina Gunarathne [EMAIL PROTECTED] wrote: Here is my +1... thanks, Thilina On 7/24/07, Deepal Jayasinghe [EMAIL PROTECTED] wrote: Hi All, Shivantha has been helping Axis2 for quite a while now, he has done a number of bug fixes in Axis2 IDEA plug-in. He has spend most his time on getting both Eclipse and IntelJ Idea plugins to consistent state. He has created a number of JIRAs and submitted more then 12 patches , so I think he has done more than enough to get Axis2 commit access. Here is my +1 for Shivantha as an Axis2 commiter. Thanks Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thilina Gunarathne - http://www.wso2.com - http://thilinag.blogspot.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- [EMAIL PROTECTED] WSO2, Inc: http://www.wso2.com Oxygenating the Web Service Platform http://www.milindalakmal.wordpress.com
Re: [VOTE][Axis2] Shivantha Huruggamuwa as an Axis2 commiter
Here is my +1 Charitha Milinda Pathirage wrote: +1 Milinda On 7/24/07, *Thilina Gunarathne* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Here is my +1... thanks, Thilina On 7/24/07, Deepal Jayasinghe [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi All, Shivantha has been helping Axis2 for quite a while now, he has done a number of bug fixes in Axis2 IDEA plug-in. He has spend most his time on getting both Eclipse and IntelJ Idea plugins to consistent state. He has created a number of JIRAs and submitted more then 12 patches , so I think he has done more than enough to get Axis2 commit access. Here is my +1 for Shivantha as an Axis2 commiter. Thanks Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -- Thilina Gunarathne - http://www.wso2.com - http://thilinag.blogspot.com - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -- [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] WSO2, Inc: http://www.wso2.com Oxygenating the Web Service Platform http://www.milindalakmal.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][Axis2] Shivantha Huruggamuwa as an Axis2 commiter
+1 Amila. On 7/24/07, Charitha Kankanamge [EMAIL PROTECTED] wrote: Here is my +1 Charitha Milinda Pathirage wrote: +1 Milinda On 7/24/07, *Thilina Gunarathne* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Here is my +1... thanks, Thilina On 7/24/07, Deepal Jayasinghe [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi All, Shivantha has been helping Axis2 for quite a while now, he has done a number of bug fixes in Axis2 IDEA plug-in. He has spend most his time on getting both Eclipse and IntelJ Idea plugins to consistent state. He has created a number of JIRAs and submitted more then 12 patches , so I think he has done more than enough to get Axis2 commit access. Here is my +1 for Shivantha as an Axis2 commiter. Thanks Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -- Thilina Gunarathne - http://www.wso2.com - http://thilinag.blogspot.com - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -- [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] WSO2, Inc: http://www.wso2.com Oxygenating the Web Service Platform http://www.milindalakmal.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Amila Suriarachchi, WSO2 Inc.
Re: [VOTE][Axis2] Shivantha Huruggamuwa as an Axis2 commiter
+1 sumedha. On 7/24/07, Deepal Jayasinghe [EMAIL PROTECTED] wrote: Hi All, Shivantha has been helping Axis2 for quite a while now, he has done a number of bug fixes in Axis2 IDEA plug-in. He has spend most his time on getting both Eclipse and IntelJ Idea plugins to consistent state. He has created a number of JIRAs and submitted more then 12 patches , so I think he has done more than enough to get Axis2 commit access. Here is my +1 for Shivantha as an Axis2 commiter. Thanks Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-3000) Add new phase to add all the addressing handlers
[ https://issues.apache.org/jira/browse/AXIS2-3000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe resolved AXIS2-3000. -- Resolution: Fixed Fixed the issues both trunk and the branch (559017 in branch) Add new phase to add all the addressing handlers Key: AXIS2-3000 URL: https://issues.apache.org/jira/browse/AXIS2-3000 Project: Axis 2.0 (Axis2) Issue Type: Improvement Reporter: Deepal Jayasinghe It is nice to have a phase to add all the addressing handlers rather than adding them to PreDispatch phase -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3002) Axis 1.3RC2 does not work properly on websphere
[ https://issues.apache.org/jira/browse/AXIS2-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514951 ] Dustin Amrhein commented on AXIS2-3002: --- Charitha, One thing that you will have to do (and you may have already done this) is to configure the classloader for the axis2.war. The default classloader policy for deployed WARs on WebSphere is PARENT_FIRST. In order to load classes within your module first you need to change this policy to PARENT_LAST. You may have already done this, but I hope it helps. Axis 1.3RC2 does not work properly on websphere --- Key: AXIS2-3002 URL: https://issues.apache.org/jira/browse/AXIS2-3002 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Affects Versions: 1.3 Environment: Websphere 6.0.2 Reporter: Kent Watanabe Assignee: Charitha Kankanamge Attachments: Websphere-axis2.JPG The new axis2.war does not work properly on websphere. There are problems with the wsdl2 generation, and the wsdl 1.1 genaration. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
ADBDataSource getReader() method implementation.
ADB databinding in axis2 uses the ADBDatasource to return the OMElement.
Currently ADBDatasource getReader and serialize methods are like this.
public abstract void serialize(XMLStreamWriter xmlWriter)
throws XMLStreamException;
public XMLStreamReader getReader() throws XMLStreamException {
return bean.getPullParser(parentQName);
}
When we want to serialize the xml stream directly to transport we use
serialize method and the getReader is used in building the OMElemnet.
Specially Rampart module always build the OMElement and hence call for
getReader() method.
The serialize method is worked fine and it is the well tested method in ADB
and the getReader method which uses the ADBXmlStremReader has some issue
regarding extension and binary handling.
To solve this problem I wrote OMElmentStreamWriter [1] which build the
OMElement from the writer.
So now the getReader method looks like this. It use the serialize method to
create the OMElement.
public XMLStreamReader getReader() throws XMLStreamException {
OMElementStreamWriter omElementStreamWriter = new
OMElementStreamWriter();
serialize(omElementStreamWriter);
return omElementStreamWriter.getOMElement().getXMLStreamReader();
}
this method perfectly works except the following two problems.
1. It is bit in efficient
OMElementStreamWriter first creates the OMElement and then it is used to get
the reader and again buid the OMElement.
To solve that either we can introduce a method to OMDataSource to directly
return the OMElement or AXIOM it self can use the above writer to build the
OMElement using the serilize method.
2. problems with the MTOM
This writer is not aware mtom. so it always serialize it as base64binary.
To fix this problem we can test for this pirticular writer in ADB generated
code (using instanceof or using a property) and set the data handler
to the element using a special method.
So this way we can create an OMElement which has a datahandler object in it.
in ADB bean class
if (writer instanceof OMElementStreamWriter){
(OMElementStreamWriter)writer).setDataHandler(dataHandler);
}
in OMElementStreamWriter
public void setDataHandler(DataHandler dataHandler){
OMText omText = omFactory.createOMText(dataHandler,true);
currentOMElement.addChild(omText);
}
would this solve our problem?
And can someone has a better knowledge with Axiom comment on these?
The main advantage ADB has from this is to use the well tested serialize
method and hence keep one method to serailize the bean.
thanks,
Amila.
[1]
https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/modules/adb/src/org/apache/axis2/databinding/utils/writer/OMElementStreamWriter.java
--
Amila Suriarachchi,
WSO2 Inc.
[jira] Created: (AXIS2-3006) base64binary serialization
base64binary serialization
--
Key: AXIS2-3006
URL: https://issues.apache.org/jira/browse/AXIS2-3006
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: databinding
Affects Versions: 1.3
Environment: tested on Axis2 1.2 1.3 RC2
os: *nix , windows,
tomcat : 5.5.23
java 1.6
Reporter: Georgi Yonchev
using POJO's ..
this happens when the response is some object with byte[] parameter inside it.
here is the server class:
public class Test {
public Res test(){
Res res = new Res();
StringBuffer sb = new StringBuffer();
for(int i = 0 ; i 5000; i++){
sb.append(i);
}
res.setData(sb.toString().getBytes());
return res;
}
public byte[] test2(){
StringBuffer sb = new StringBuffer();
for(int i = 0 ; i 5000; i++){
sb.append(i);
}
return sb.toString().getBytes();
}
}
Res class:
public class Res {
private byte[] data;
public byte[] getData() {
return data;
}
public void setData(byte[] data) {
this.data = data;
}
}
and the wsdl:
wsdl:definitions xmlns:ns=http://;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
xmlns:http=http://schemas.xmlsoap.org/wsdl/http/; xmlns:xsd=http:///xsd;
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:mime=http://schemas.xmlsoap.org/wsdl/mime/;
xmlns:soap12=http://schemas.xmlsoap.org/wsdl/soap12/;
targetNamespace=http://;wsdl:typesxs:schema
xmlns:xs=http://www.w3.org/2001/XMLSchema;
xmlns:ax26=http://ws.apache.org/axis2/xsd; attributeFormDefault=qualified
elementFormDefault=qualified targetNamespace=http://ws.apache.org/axis2/xsd;
xs:element name=Res type=ax26:Res /
xs:complexType name=Res
xs:sequence
xs:element name=data nillable=true type=xs:base64Binary /
/xs:sequence
/xs:complexType
/xs:schemaxs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema;
xmlns:ns0=http://ws.apache.org/axis2/xsd; attributeFormDefault=qualified
elementFormDefault=qualified targetNamespace=http:///xsd;
xs:element name=testResponse
xs:complexType
xs:sequence
xs:element name=return nillable=true type=ns0:Res /
/xs:sequence
/xs:complexType
/xs:element
xs:element name=test2Response
xs:complexType
xs:sequence
xs:element name=return nillable=true type=xs:base64Binary /
/xs:sequence
/xs:complexType
/xs:element
/xs:schema/wsdl:typeswsdl:message name=testMessage /wsdl:message
name=testResponseMessagewsdl:part name=part1 element=xsd:testResponse
//wsdl:messagewsdl:message name=test2Message /wsdl:message
name=test2ResponseMessagewsdl:part name=part1 element=xsd:test2Response
//wsdl:messagewsdl:portType name=TestPortTypewsdl:operation
name=testwsdl:input xmlns:wsaw=http://www.w3.org/2006/05/addressing/wsdl;
wsaw:Action=urn:test message=ns:testMessage /wsdl:output
xmlns:wsaw=http://www.w3.org/2006/05/addressing/wsdl;
message=ns:testResponseMessage wsaw:Action=urn:test
//wsdl:operationwsdl:operation name=test2wsdl:input
xmlns:wsaw=http://www.w3.org/2006/05/addressing/wsdl; wsaw:Action=urn:test2
message=ns:test2Message /wsdl:output
xmlns:wsaw=http://www.w3.org/2006/05/addressing/wsdl;
message=ns:test2ResponseMessage wsaw:Action=urn:test2
//wsdl:operation/wsdl:portTypewsdl:binding name=TestSOAP11Binding
type=ns:TestPortTypesoap:binding
transport=http://schemas.xmlsoap.org/soap/http; style=document
/wsdl:operation name=testsoap:operation soapAction=urn:test
style=document /wsdl:inputsoap:body use=literal
//wsdl:inputwsdl:outputsoap:body use=literal
//wsdl:output/wsdl:operationwsdl:operation name=test2soap:operation
soapAction=urn:test2 style=document /wsdl:inputsoap:body use=literal
//wsdl:inputwsdl:outputsoap:body use=literal
//wsdl:output/wsdl:operation/wsdl:bindingwsdl:binding
name=TestSOAP12Binding type=ns:TestPortTypesoap12:binding
transport=http://schemas.xmlsoap.org/soap/http; style=document
/wsdl:operation name=testsoap12:operation soapAction=urn:test
style=document /wsdl:inputsoap12:body use=literal
//wsdl:inputwsdl:outputsoap12:body use=literal
//wsdl:output/wsdl:operationwsdl:operation name=test2soap12:operation
soapAction=urn:test2 style=document /wsdl:inputsoap12:body
use=literal //wsdl:inputwsdl:outputsoap12:body use=literal
//wsdl:output/wsdl:operation/wsdl:bindingwsdl:service
name=Testwsdl:port name=TestSOAP11port
binding=ns:TestSOAP11Bindingsoap:address
location=http://localhost:8080/axis2/services/Test; //wsdl:portwsdl:port
name=TestSOAP12port binding=ns:TestSOAP12Bindingsoap12:address
location=http://localhost:8080/axis2/services/Test;
//wsdl:port/wsdl:service/wsdl:definitions
this wsdl service.xml is generated automatically by the eclipse plug-in
here is the client:
public class Test_client {
public static void main(String
[jira] Updated: (AXIS2-3006) base64binary serialization
[ https://issues.apache.org/jira/browse/AXIS2-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Georgi Yonchev updated AXIS2-3006: -- Attachment: Res.java base64binary serialization -- Key: AXIS2-3006 URL: https://issues.apache.org/jira/browse/AXIS2-3006 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: databinding Affects Versions: 1.3 Environment: tested on Axis2 1.2 1.3 RC2 os: *nix , windows, tomcat : 5.5.23 java 1.6 Reporter: Georgi Yonchev Attachments: Res.java using POJO's .. in Attachments : Res.java (the response object) Test.java (server) Test_client.java services.wsdl this happens when the response is some object with byte[] parameter inside it. this wsdl service.xml is generated automatically by the eclipse plug-in so, test2() always works, small/larger byte[] size in test() if you test with some string.getBytes() will work but larger ... no here is the soap payload : ns:byteData104/ns:byteDatans:byteData111/ns:byteDatans:byteData109/ns:byteDatans:byteData97/ns:byteDatans:byteData44/ns:byteDatans:byteData32/ns:byteDatans:byteData86/ns:byteDatans:byteData101/ns:byteDatans:byteData114/ns:byteDatans:byteData100/ns:byteDatans:byteData97/ns:byteDatans:byteData110/ns:byteDatans:byteData97/ns:byteDatans:byteData44/ns:byteDatans:byteData32/ns:byteDatans:byteData65/ns:byteDatans:byteData114/ns:byteDatans:byteData105/ns:byteDatans:byteData97/ns:byteDatans:byteData108/ns:byteDatans:byteData44/ns:byteDatans:byteData32/ns:byteDatans:byteData72/ns:byteDatans:byteData101/ns:byteDatans:byteData108/ns:byteDatans:byteData118/ns:byteDatans:byteData101/ns:byteDatans:byteData116/ns:byteDatans:byteData105/ns:byteDatans:byteData99/ns:byteDatans:byteData97/ns:byteDatans:byteData59/ns:byteDatans:byteData13/ns:byteDatans:b yteData10/ns:byteDatans:byteData9/ns:byteDatans:byteData102/ns:byteDatans:byteData111/ns:byteDatans:byteData110/ns:byteDatans:byteData116/ns:byteDatans:byteData45/ns:byteDatans:byteData115/ns:byteDatans:byteData105/ns:byteDatans:byteData122/ns:byteDatans:byteData101/ns:byteDatans:byteData58/ns:byteDatans:byteData32/ns:byteDatans:byteData49/ns:byteDatans:byteData48/ns:byteData ns:byteData112/ns:byteDatans:byteData116/ns:byteDatans:byteData59/ns:byteDatans:byteData13/ns:byteDatans:byteData10/ns:byteDatans:byteData9/ns:byteDatans:byteData102/ns:byteDatans:byteData111/ns:byteDatans:byteData110/ns:byteDatans:byteData116/ns:byteDatans:byteData45/ns:byteDatans:byteData119/ns:byteDatans:byteData101/ns:byteDatans:byteData105/ns:byteDatans:byteData103/ns:byteDatans:byteData104/ns:byteDatans:byteData116/ns:byteDatans:byteData58/ns:byteDatans:byteData32/ns:byteDatans:byteData110/ns:byteDatans:byteData111/ns:byteDatans:byteData114/ns:byteDatans:byteData109/ns:byteDatans:byteData97/ns:byteDatans:byteData108/ns:byteDatans:byteData59/ns:byteDatans:byteData13/ns:byteDatans:byteData10/ns:byteDatans:byteData125/ns:byteDatans:byteData13/ns:byteDatans:byteData10/ns:byteDatans:byteData46/ns:byteDatans:byteData99/ns:byteDatans:byteData111/ns:byteDatans:byteData110/n s:byteDatans:byteData 2000 116/ns:byteDatans:byteData101/ns:byteDatans:byteData110/ns:byteDatans:byteData116/ns:byteDatans:byteData49/ns:byteDatans:byteData123/ns:byteDatans:byteData13/ns:byteDatans:byteData10/ns:byteDatans:byteData9/ns:byteDatans:byteData109/ns:byteDatans:byteData97/ns:byteDatans:byteData114/ns:byteDatans:byteData103/ns:byteDatans:byteData105/ns:byteDatans :byteData110/ns:byteDatans:byteData58/ns:byteData is not encoded in base64 !? Best Regards George -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3006) base64binary serialization
[
https://issues.apache.org/jira/browse/AXIS2-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Georgi Yonchev updated AXIS2-3006:
--
Description:
using POJO's ..
in Attachments :
Res.java (the response object)
Test.java (server)
Test_client.java
services.wsdl
this happens when the response is some object with byte[] parameter inside it.
this wsdl service.xml is generated automatically by the eclipse plug-in
so, test2() always works, small/larger byte[] size
in test() if you test with some string.getBytes() will work
but larger ... no
here is the soap payload :
ns:byteData104/ns:byteDatans:byteData111/ns:byteDatans:byteData109/ns:byteDatans:byteData97/ns:byteDatans:byteData44/ns:byteDatans:byteData32/ns:byteDatans:byteData86/ns:byteDatans:byteData101/ns:byteDatans:byteData114/ns:byteDatans:byteData100/ns:byteDatans:byteData97/ns:byteDatans:byteData110/ns:byteDatans:byteData97/ns:byteDatans:byteData44/ns:byteDatans:byteData32/ns:byteDatans:byteData65/ns:byteDatans:byteData114/ns:byteDatans:byteData105/ns:byteDatans:byteData97/ns:byteDatans:byteData108/ns:byteDatans:byteData44/ns:byteDatans:byteData32/ns:byteDatans:byteData72/ns:byteDatans:byteData101/ns:byteDatans:byteData108/ns:byteDatans:byteData118/ns:byteDatans:byteData101/ns:byteDatans:byteData116/ns:byteDatans:byteData105/ns:byteDatans:byteData99/ns:byteDatans:byteData97/ns:byteDatans:byteData59/ns:byteDatans:byteData13/ns:byteDatans:b
yteData10/ns:byteDatans:byteData9/ns:byteDatans:byteData102/ns:byteDatans:byteData111/ns:byteDatans:byteData110/ns:byteDatans:byteData116/ns:byteDatans:byteData45/ns:byteDatans:byteData115/ns:byteDatans:byteData105/ns:byteDatans:byteData122/ns:byteDatans:byteData101/ns:byteDatans:byteData58/ns:byteDatans:byteData32/ns:byteDatans:byteData49/ns:byteDatans:byteData48/ns:byteData
ns:byteData112/ns:byteDatans:byteData116/ns:byteDatans:byteData59/ns:byteDatans:byteData13/ns:byteDatans:byteData10/ns:byteDatans:byteData9/ns:byteDatans:byteData102/ns:byteDatans:byteData111/ns:byteDatans:byteData110/ns:byteDatans:byteData116/ns:byteDatans:byteData45/ns:byteDatans:byteData119/ns:byteDatans:byteData101/ns:byteDatans:byteData105/ns:byteDatans:byteData103/ns:byteDatans:byteData104/ns:byteDatans:byteData116/ns:byteDatans:byteData58/ns:byteDatans:byteData32/ns:byteDatans:byteData110/ns:byteDatans:byteData111/ns:byteDatans:byteData114/ns:byteDatans:byteData109/ns:byteDatans:byteData97/ns:byteDatans:byteData108/ns:byteDatans:byteData59/ns:byteDatans:byteData13/ns:byteDatans:byteData10/ns:byteDatans:byteData125/ns:byteDatans:byteData13/ns:byteDatans:byteData10/ns:byteDatans:byteData46/ns:byteDatans:byteData99/ns:byteDatans:byteData111/ns:byteDatans:byteData110/n
s:byteDatans:byteData
2000
116/ns:byteDatans:byteData101/ns:byteDatans:byteData110/ns:byteDatans:byteData116/ns:byteDatans:byteData49/ns:byteDatans:byteData123/ns:byteDatans:byteData13/ns:byteDatans:byteData10/ns:byteDatans:byteData9/ns:byteDatans:byteData109/ns:byteDatans:byteData97/ns:byteDatans:byteData114/ns:byteDatans:byteData103/ns:byteDatans:byteData105/ns:byteDatans
:byteData110/ns:byteDatans:byteData58/ns:byteData
is not encoded in base64 !?
Best Regards
George
was:
using POJO's ..
this happens when the response is some object with byte[] parameter inside it.
here is the server class:
public class Test {
public Res test(){
Res res = new Res();
StringBuffer sb = new StringBuffer();
for(int i = 0 ; i 5000; i++){
sb.append(i);
}
res.setData(sb.toString().getBytes());
return res;
}
public byte[] test2(){
StringBuffer sb = new StringBuffer();
for(int i = 0 ; i 5000; i++){
sb.append(i);
}
return sb.toString().getBytes();
}
}
Res class:
public class Res {
private byte[] data;
public byte[] getData() {
return data;
}
public void setData(byte[] data) {
this.data = data;
}
}
and the wsdl:
wsdl:definitions xmlns:ns=http://;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
xmlns:http=http://schemas.xmlsoap.org/wsdl/http/; xmlns:xsd=http:///xsd;
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:mime=http://schemas.xmlsoap.org/wsdl/mime/;
xmlns:soap12=http://schemas.xmlsoap.org/wsdl/soap12/;
targetNamespace=http://;wsdl:typesxs:schema
xmlns:xs=http://www.w3.org/2001/XMLSchema;
xmlns:ax26=http://ws.apache.org/axis2/xsd; attributeFormDefault=qualified
elementFormDefault=qualified targetNamespace=http://ws.apache.org/axis2/xsd;
xs:element name=Res type=ax26:Res /
xs:complexType name=Res
xs:sequence
xs:element name=data nillable=true type=xs:base64Binary /
/xs:sequence
/xs:complexType
/xs:schemaxs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema;
[jira] Updated: (AXIS2-3006) base64binary serialization
[ https://issues.apache.org/jira/browse/AXIS2-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Georgi Yonchev updated AXIS2-3006: -- Attachment: services.wsdl base64binary serialization -- Key: AXIS2-3006 URL: https://issues.apache.org/jira/browse/AXIS2-3006 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: databinding Affects Versions: 1.3 Environment: tested on Axis2 1.2 1.3 RC2 os: *nix , windows, tomcat : 5.5.23 java 1.6 Reporter: Georgi Yonchev Attachments: Res.java, services.wsdl, Test.java, Test_client.java using POJO's .. in Attachments : Res.java (the response object) Test.java (server) Test_client.java services.wsdl this happens when the response is some object with byte[] parameter inside it. this wsdl service.xml is generated automatically by the eclipse plug-in so, test2() always works, small/larger byte[] size in test() if you test with some string.getBytes() will work but larger ... no here is the soap payload : ns:byteData104/ns:byteDatans:byteData111/ns:byteDatans:byteData109/ns:byteDatans:byteData97/ns:byteDatans:byteData44/ns:byteDatans:byteData32/ns:byteDatans:byteData86/ns:byteDatans:byteData101/ns:byteDatans:byteData114/ns:byteDatans:byteData100/ns:byteDatans:byteData97/ns:byteDatans:byteData110/ns:byteDatans:byteData97/ns:byteDatans:byteData44/ns:byteDatans:byteData32/ns:byteDatans:byteData65/ns:byteDatans:byteData114/ns:byteDatans:byteData105/ns:byteDatans:byteData97/ns:byteDatans:byteData108/ns:byteDatans:byteData44/ns:byteDatans:byteData32/ns:byteDatans:byteData72/ns:byteDatans:byteData101/ns:byteDatans:byteData108/ns:byteDatans:byteData118/ns:byteDatans:byteData101/ns:byteDatans:byteData116/ns:byteDatans:byteData105/ns:byteDatans:byteData99/ns:byteDatans:byteData97/ns:byteDatans:byteData59/ns:byteDatans:byteData13/ns:byteDatans:b yteData10/ns:byteDatans:byteData9/ns:byteDatans:byteData102/ns:byteDatans:byteData111/ns:byteDatans:byteData110/ns:byteDatans:byteData116/ns:byteDatans:byteData45/ns:byteDatans:byteData115/ns:byteDatans:byteData105/ns:byteDatans:byteData122/ns:byteDatans:byteData101/ns:byteDatans:byteData58/ns:byteDatans:byteData32/ns:byteDatans:byteData49/ns:byteDatans:byteData48/ns:byteData ns:byteData112/ns:byteDatans:byteData116/ns:byteDatans:byteData59/ns:byteDatans:byteData13/ns:byteDatans:byteData10/ns:byteDatans:byteData9/ns:byteDatans:byteData102/ns:byteDatans:byteData111/ns:byteDatans:byteData110/ns:byteDatans:byteData116/ns:byteDatans:byteData45/ns:byteDatans:byteData119/ns:byteDatans:byteData101/ns:byteDatans:byteData105/ns:byteDatans:byteData103/ns:byteDatans:byteData104/ns:byteDatans:byteData116/ns:byteDatans:byteData58/ns:byteDatans:byteData32/ns:byteDatans:byteData110/ns:byteDatans:byteData111/ns:byteDatans:byteData114/ns:byteDatans:byteData109/ns:byteDatans:byteData97/ns:byteDatans:byteData108/ns:byteDatans:byteData59/ns:byteDatans:byteData13/ns:byteDatans:byteData10/ns:byteDatans:byteData125/ns:byteDatans:byteData13/ns:byteDatans:byteData10/ns:byteDatans:byteData46/ns:byteDatans:byteData99/ns:byteDatans:byteData111/ns:byteDatans:byteData110/n s:byteDatans:byteData 2000 116/ns:byteDatans:byteData101/ns:byteDatans:byteData110/ns:byteDatans:byteData116/ns:byteDatans:byteData49/ns:byteDatans:byteData123/ns:byteDatans:byteData13/ns:byteDatans:byteData10/ns:byteDatans:byteData9/ns:byteDatans:byteData109/ns:byteDatans:byteData97/ns:byteDatans:byteData114/ns:byteDatans:byteData103/ns:byteDatans:byteData105/ns:byteDatans :byteData110/ns:byteDatans:byteData58/ns:byteData is not encoded in base64 !? Best Regards George -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3006) base64binary serialization
[ https://issues.apache.org/jira/browse/AXIS2-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Georgi Yonchev updated AXIS2-3006: -- Attachment: Test_client.java base64binary serialization -- Key: AXIS2-3006 URL: https://issues.apache.org/jira/browse/AXIS2-3006 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: databinding Affects Versions: 1.3 Environment: tested on Axis2 1.2 1.3 RC2 os: *nix , windows, tomcat : 5.5.23 java 1.6 Reporter: Georgi Yonchev Attachments: Res.java, services.wsdl, Test.java, Test_client.java using POJO's .. in Attachments : Res.java (the response object) Test.java (server) Test_client.java services.wsdl this happens when the response is some object with byte[] parameter inside it. this wsdl service.xml is generated automatically by the eclipse plug-in so, test2() always works, small/larger byte[] size in test() if you test with some string.getBytes() will work but larger ... no here is the soap payload : ns:byteData104/ns:byteDatans:byteData111/ns:byteDatans:byteData109/ns:byteDatans:byteData97/ns:byteDatans:byteData44/ns:byteDatans:byteData32/ns:byteDatans:byteData86/ns:byteDatans:byteData101/ns:byteDatans:byteData114/ns:byteDatans:byteData100/ns:byteDatans:byteData97/ns:byteDatans:byteData110/ns:byteDatans:byteData97/ns:byteDatans:byteData44/ns:byteDatans:byteData32/ns:byteDatans:byteData65/ns:byteDatans:byteData114/ns:byteDatans:byteData105/ns:byteDatans:byteData97/ns:byteDatans:byteData108/ns:byteDatans:byteData44/ns:byteDatans:byteData32/ns:byteDatans:byteData72/ns:byteDatans:byteData101/ns:byteDatans:byteData108/ns:byteDatans:byteData118/ns:byteDatans:byteData101/ns:byteDatans:byteData116/ns:byteDatans:byteData105/ns:byteDatans:byteData99/ns:byteDatans:byteData97/ns:byteDatans:byteData59/ns:byteDatans:byteData13/ns:byteDatans:b yteData10/ns:byteDatans:byteData9/ns:byteDatans:byteData102/ns:byteDatans:byteData111/ns:byteDatans:byteData110/ns:byteDatans:byteData116/ns:byteDatans:byteData45/ns:byteDatans:byteData115/ns:byteDatans:byteData105/ns:byteDatans:byteData122/ns:byteDatans:byteData101/ns:byteDatans:byteData58/ns:byteDatans:byteData32/ns:byteDatans:byteData49/ns:byteDatans:byteData48/ns:byteData ns:byteData112/ns:byteDatans:byteData116/ns:byteDatans:byteData59/ns:byteDatans:byteData13/ns:byteDatans:byteData10/ns:byteDatans:byteData9/ns:byteDatans:byteData102/ns:byteDatans:byteData111/ns:byteDatans:byteData110/ns:byteDatans:byteData116/ns:byteDatans:byteData45/ns:byteDatans:byteData119/ns:byteDatans:byteData101/ns:byteDatans:byteData105/ns:byteDatans:byteData103/ns:byteDatans:byteData104/ns:byteDatans:byteData116/ns:byteDatans:byteData58/ns:byteDatans:byteData32/ns:byteDatans:byteData110/ns:byteDatans:byteData111/ns:byteDatans:byteData114/ns:byteDatans:byteData109/ns:byteDatans:byteData97/ns:byteDatans:byteData108/ns:byteDatans:byteData59/ns:byteDatans:byteData13/ns:byteDatans:byteData10/ns:byteDatans:byteData125/ns:byteDatans:byteData13/ns:byteDatans:byteData10/ns:byteDatans:byteData46/ns:byteDatans:byteData99/ns:byteDatans:byteData111/ns:byteDatans:byteData110/n s:byteDatans:byteData 2000 116/ns:byteDatans:byteData101/ns:byteDatans:byteData110/ns:byteDatans:byteData116/ns:byteDatans:byteData49/ns:byteDatans:byteData123/ns:byteDatans:byteData13/ns:byteDatans:byteData10/ns:byteDatans:byteData9/ns:byteDatans:byteData109/ns:byteDatans:byteData97/ns:byteDatans:byteData114/ns:byteDatans:byteData103/ns:byteDatans:byteData105/ns:byteDatans :byteData110/ns:byteDatans:byteData58/ns:byteData is not encoded in base64 !? Best Regards George -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3006) base64binary serialization
[ https://issues.apache.org/jira/browse/AXIS2-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Georgi Yonchev updated AXIS2-3006: -- Attachment: Test.java base64binary serialization -- Key: AXIS2-3006 URL: https://issues.apache.org/jira/browse/AXIS2-3006 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: databinding Affects Versions: 1.3 Environment: tested on Axis2 1.2 1.3 RC2 os: *nix , windows, tomcat : 5.5.23 java 1.6 Reporter: Georgi Yonchev Attachments: Res.java, services.wsdl, Test.java, Test_client.java using POJO's .. in Attachments : Res.java (the response object) Test.java (server) Test_client.java services.wsdl this happens when the response is some object with byte[] parameter inside it. this wsdl service.xml is generated automatically by the eclipse plug-in so, test2() always works, small/larger byte[] size in test() if you test with some string.getBytes() will work but larger ... no here is the soap payload : ns:byteData104/ns:byteDatans:byteData111/ns:byteDatans:byteData109/ns:byteDatans:byteData97/ns:byteDatans:byteData44/ns:byteDatans:byteData32/ns:byteDatans:byteData86/ns:byteDatans:byteData101/ns:byteDatans:byteData114/ns:byteDatans:byteData100/ns:byteDatans:byteData97/ns:byteDatans:byteData110/ns:byteDatans:byteData97/ns:byteDatans:byteData44/ns:byteDatans:byteData32/ns:byteDatans:byteData65/ns:byteDatans:byteData114/ns:byteDatans:byteData105/ns:byteDatans:byteData97/ns:byteDatans:byteData108/ns:byteDatans:byteData44/ns:byteDatans:byteData32/ns:byteDatans:byteData72/ns:byteDatans:byteData101/ns:byteDatans:byteData108/ns:byteDatans:byteData118/ns:byteDatans:byteData101/ns:byteDatans:byteData116/ns:byteDatans:byteData105/ns:byteDatans:byteData99/ns:byteDatans:byteData97/ns:byteDatans:byteData59/ns:byteDatans:byteData13/ns:byteDatans:b yteData10/ns:byteDatans:byteData9/ns:byteDatans:byteData102/ns:byteDatans:byteData111/ns:byteDatans:byteData110/ns:byteDatans:byteData116/ns:byteDatans:byteData45/ns:byteDatans:byteData115/ns:byteDatans:byteData105/ns:byteDatans:byteData122/ns:byteDatans:byteData101/ns:byteDatans:byteData58/ns:byteDatans:byteData32/ns:byteDatans:byteData49/ns:byteDatans:byteData48/ns:byteData ns:byteData112/ns:byteDatans:byteData116/ns:byteDatans:byteData59/ns:byteDatans:byteData13/ns:byteDatans:byteData10/ns:byteDatans:byteData9/ns:byteDatans:byteData102/ns:byteDatans:byteData111/ns:byteDatans:byteData110/ns:byteDatans:byteData116/ns:byteDatans:byteData45/ns:byteDatans:byteData119/ns:byteDatans:byteData101/ns:byteDatans:byteData105/ns:byteDatans:byteData103/ns:byteDatans:byteData104/ns:byteDatans:byteData116/ns:byteDatans:byteData58/ns:byteDatans:byteData32/ns:byteDatans:byteData110/ns:byteDatans:byteData111/ns:byteDatans:byteData114/ns:byteDatans:byteData109/ns:byteDatans:byteData97/ns:byteDatans:byteData108/ns:byteDatans:byteData59/ns:byteDatans:byteData13/ns:byteDatans:byteData10/ns:byteDatans:byteData125/ns:byteDatans:byteData13/ns:byteDatans:byteData10/ns:byteDatans:byteData46/ns:byteDatans:byteData99/ns:byteDatans:byteData111/ns:byteDatans:byteData110/n s:byteDatans:byteData 2000 116/ns:byteDatans:byteData101/ns:byteDatans:byteData110/ns:byteDatans:byteData116/ns:byteDatans:byteData49/ns:byteDatans:byteData123/ns:byteDatans:byteData13/ns:byteDatans:byteData10/ns:byteDatans:byteData9/ns:byteDatans:byteData109/ns:byteDatans:byteData97/ns:byteDatans:byteData114/ns:byteDatans:byteData103/ns:byteDatans:byteData105/ns:byteDatans :byteData110/ns:byteDatans:byteData58/ns:byteData is not encoded in base64 !? Best Regards George -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to provide own WSDL?
Please add that in your services.xml -- dims On 7/24/07, Gertjan van Oosten [EMAIL PROTECTED] wrote: I've set up a webapp following Dims' tutorial at: http://wso2.org/library/90 I want to return my own WSDL from the service by setting parameter name=useOriginalwsdltrue/parameter but where do I need to put the WSDL file (and the schemata it includes)? I tried the obvious places but I get either the standard reply[*] or zero-length content. [*] errordescriptionUnable to generate WSDL 1.1 for this service/descriptionreasonIf you wish Axis2 to automatically generate the WSDL 1.1, then please +set useOriginalwsdl as false in your services.xml/reason/error Regards, -- -- Gertjan van Oosten, [EMAIL PROTECTED], West Consulting B.V., +31 15 2191 600 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to provide own WSDL?
As quoted from Davanum Srinivas [EMAIL PROTECTED]: Please add that in your services.xml Pardon my ignorance, but add what to my services.xml? I already have the parameter name=useOriginalwsdltrue/parameter in there; the question was: where do I put the WSDL file and XML schemata themselves such that the Axis2 service handler is able to find them? Kind regards, -- -- Gertjan van Oosten, [EMAIL PROTECTED], West Consulting B.V., +31 15 2191 600 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3007) RESTful services invocation self induces Input Stream Closed error
RESTful services invocation self induces Input Stream Closed error
--
Key: AXIS2-3007
URL: https://issues.apache.org/jira/browse/AXIS2-3007
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Affects Versions: 1.2
Environment: Windows 2000, Eclipse IDE
Reporter: Jason Kania
When making REST GET calls to an API, Axis 2 core sets its input stream to null
and then complains later that its stream has been closed. The following partial
stack trace demonstrates the problem.
ApplicationXMLBuilder.processDocument(InputStream, String, MessageContext)
line: 49
TransportUtils.createSOAPMessage(MessageContext, InputStream, String) line: 130
RESTUtil.processURLRequest(MessageContext, OutputStream, String) line: 98
AxisServlet$ProcessRESTRequest.processURLRequest() line: 776
AxisServlet.doGet(HttpServletRequest, HttpServletResponse) line: 238
AxisServlet(HttpServlet).service(HttpServletRequest, HttpServletResponse) line:
707
AxisServlet(HttpServlet).service(ServletRequest, ServletResponse) line: 820
ServletHolder.handle(ServletRequest, ServletResponse) line: 487
...
In RESTUtil, method processURLRequest, the following call is made on line 98
soapEnvelope = TransportUtils
.createSOAPMessage(msgContext, null, contentType);
where the null is supposed to be the input stream
Thus, when line 49 of ApplicationXMLBuilder in method processDocument is
encountered,
PushbackInputStream pushbackInputStream = new
PushbackInputStream(inputStream);
where inputStream is null,
the exception java.io.IOException: Stream closed is generated once the empty
stream is read at line 51
of ApplicationXMLBuilder:
if ((b = pushbackInputStream.read()) 0) {
For straight Axis use, this issue is a blocker, but I have worked around the
problem by filtering empty get methods at the servlet level and am populating
them with content for now.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2972) Vague error produced for ServiceClient invocation within a service where class pathing is a problem
[ https://issues.apache.org/jira/browse/AXIS2-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Kania updated AXIS2-2972: --- Please hold the issue open as I am too busy to strip the code down to a presentable test case now, but I will get to it. Vague error produced for ServiceClient invocation within a service where class pathing is a problem --- Key: AXIS2-2972 URL: https://issues.apache.org/jira/browse/AXIS2-2972 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: databinding, deployment Affects Versions: 1.2 Environment: Running in windows XP under eclipse and with axis2 1.2 embedded under Jetty. Reporter: Jason Kania Assignee: Deepal Jayasinghe The problem I have seen occurs when a component is not in the deployment directory, but is being referenced externally. Instead of encountering a ClassNotFoundException or similar, a vague error is produced when attempting to: 1) create a ServiceClient within a service 2) load a configuration context within a service The client was external to the jar because it will be used both remotely and as a part of the service. The text of the exception is misleading because the receivers in use as per the services.xml have nothing to do with those seen in the error. To create the error, simply attempt to create a new ServiceClient() in a class that is not contained within the deployment directory, but is referenced by a class in the deployment directory. The error seen is the following: java.lang.ClassCastException: org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver cannot be cast to org.apache.axis2.engine.MessageReceiver at org.apache.axis2.deployment.DescriptionBuilder.loadMessageReceiver(DescriptionBuilder.java:190) at org.apache.axis2.deployment.DescriptionBuilder$1.run(DescriptionBuilder.java:142) at org.apache.axis2.java.security.AccessController.doPrivileged(AccessController.java:130) at org.apache.axis2.deployment.DescriptionBuilder.processMessageReceivers(DescriptionBuilder.java:138) at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:92) at org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(DeploymentEngine.java:640) at org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration(FileSystemConfigurator.java:105) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:60) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:174) at org.apache.axis2.client.ServiceClient.initializeTransports(ServiceClient.java:211) at org.apache.axis2.client.ServiceClient.configureServiceClient(ServiceClient.java:138) at org.apache.axis2.client.ServiceClient.init(ServiceClient.java:133) at org.apache.axis2.client.ServiceClient.init(ServiceClient.java:229) at com.test.client.BasicClient.init(BasicClient.java:76) at com.test.client.TestClient.init(TestClient.java:31) at com.test.client.servlet.TestServer.init(TestServer.java:452) at com.test.client.TestServer.getInstance(TestServer.java:65) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.test.client.ClientMessageHandler.init(ClientMessageHandler.java:51) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.axis2.engine.DependencyManager.initServiceClass(DependencyManager.java:56) at org.apache.axis2.engine.DependencyManager.initService(DependencyManager.java:94) at org.apache.axis2.context.ConfigurationContextFactory.initApplicationScopeServices(ConfigurationContextFactory.java:91) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:76) at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:486) at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:406) at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:433) at
[jira] Commented: (AXIS2-3001) Problem in 1.3 RC with deserialization of java.util.Date objects that are DateTime formatted.
[ https://issues.apache.org/jira/browse/AXIS2-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514966 ] Sathija Pavuluri commented on AXIS2-3001: - The Date object in java contains a complete timestamp with date and time. It should be mapped to a dateTime value in XML. When the Date object is serialized, Axis is serializing it to a dateTime xml value (as can be seen in the xml response in my earlier comment). But when it's deserialized, it's attempting to deserialze it as a date xml value which causes the above exception. The name Date in java is a bit misleading, it's not really just a date, it's a timestamp and should be mapped as such to xml. Axis is now mapping the Calendar object to xml dateTime, but developers seldom use Calendar for literal date (and dateTime) representation. Calendar is a heavier weight object and is mostly used when date manipulations and conversions are to be made. This approach that Axis is taking forces Calendar object to be used for dateTime representation when java does provide the more convenient Date object. This may also be breaking backward compatibility forcing all Date objects that were used for timestamp representation be changed to Calendar objects. Problem in 1.3 RC with deserialization of java.util.Date objects that are DateTime formatted. - Key: AXIS2-3001 URL: https://issues.apache.org/jira/browse/AXIS2-3001 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: adb Affects Versions: 1.3 Environment: Axis 1.3 RC2, JDK 1.6 on Linux Reporter: Sathija Pavuluri Assignee: Amila Chinthaka Suriarachchi Priority: Blocker This bug was introduced after the fix that was made for jira AXIS2-2701. I had originally written my comment against 2701 but since the bug is marked as resolved, thought this new issue should be tracked separately. The fix for AXIS2-2701 makes it impossible for java.util.Date objects to be deserialized when the date is datetime formatted (i.e. -mm-dd hh:mm:ss). It now only works for date format objects (i.e. -mm-dd) For example I have an object with attribute: java.util.Date timeStarted; The element in the response looks like this: ax26:timeStarted2007-07-23T13:20:46.861Z/ax26:timeStarted The deserialization of this element fails with this exception: java.lang.RuntimeException: In valid string sufix at org.apache.axis2.databinding.utils.ConverterUtil.convertToDate(ConverterUtil.java:378) at org.apache.axis2.databinding.typemapping.SimpleTypeMapper.makeDate(SimpleTypeMapper.java:304) at org.apache.axis2.databinding.typemapping.SimpleTypeMapper.getSimpleTypeObject(SimpleTypeMapper.java:117) at org.apache.axis2.databinding.utils.BeanUtil.deserialize(BeanUtil.java:364) at org.apache.axis2.databinding.utils.BeanUtil.processObject(BeanUtil.java:644) at org.apache.axis2.databinding.utils.BeanUtil.ProcessElement(BeanUtil.java:592) at org.apache.axis2.databinding.utils.BeanUtil.deserialize(BeanUtil.java:528) Looking at the code, it seems like the ConverterUtil expects the Date object to be only of -mm-dd format. It fails in the case when Date is -mm-dd hh:mm:ss formatted? Thanks, Sathija. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to provide own WSDL?
Sorry, I misread your email. Please add the wsdl/xsd under meta-inf directory. WEB-INF/services/BookService/META-INF thanks, dims On 7/24/07, Gertjan van Oosten [EMAIL PROTECTED] wrote: As quoted from Davanum Srinivas [EMAIL PROTECTED]: Please add that in your services.xml Pardon my ignorance, but add what to my services.xml? I already have the parameter name=useOriginalwsdltrue/parameter in there; the question was: where do I put the WSDL file and XML schemata themselves such that the Axis2 service handler is able to find them? Kind regards, -- -- Gertjan van Oosten, [EMAIL PROTECTED], West Consulting B.V., +31 15 2191 600 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3008) attribute not supported by Axis2.0 in the .xsd file
attribute not supported by Axis2.0 in the .xsd file --- Key: AXIS2-3008 URL: https://issues.apache.org/jira/browse/AXIS2-3008 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: databinding Affects Versions: 1.0 Environment: linxu AS , Reporter: Amit Kumar Banerjee Attribute is not supported by Axis2.0? While parsing the request at server side, it gives an error unexpected subelement AuthDetails and when i change attribute to element or comment them it works fine . below is the part of .xsd file. xsd:complexType name=AuthDetails xsd:sequence xsd:element name=ClientName type=xsd:string minOccurs=1 maxOccurs=1 / xsd:element name=Password type=xsd:string minOccurs=0 maxOccurs=1 / xsd:element name=Role type=xsd:string minOccurs=0 maxOccurs=1 / xsd:element name=ClientAuthIdA type=xsd:int minOccurs=0 maxOccurs=1 / xsd:element name=ClientAuthIdB type=xsd:int minOccurs=0 maxOccurs=1 / /xsd:sequence *xsd:attribute name=MajorVersion type=xsd:int / xsd:attribute name=MinorVersion type=xsd:int / * /xsd:complexType -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Fwd: [AXIOM] Undeclare default namespace
By undeclare I believe Xinjun means that he wants to declare the default namespace as no value, e.g., xmlns=. Anne On 7/23/07, Xinjun Chen [EMAIL PROTECTED] wrote: Hi Chinthaka, I have an element a xmlns=urn:ecNamespace bbValue/b /a. I have another element c which is created by another OMStaxBuilder. c is unqualified. Now I need to add a to c as a child of c but I want to remove the namespace in a and make a unqualified. I tried the AXIOM API to undeclare the default namespace of a but failed. I can only change the default namespace to another value but not empty string, i.e., I cannot undeclare it. Regards, Xinjun On 7/23/07, Eran Chinthaka [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 What did u mean by undeclare? If you point me what you want with some code, perhaps I can answer better. Thanks, Chinthaka Xinjun Chen wrote: Hi Axis2 Developers, Is it possible to undeclare a default namespace from an OMElement in AXIOM? I tried several ways but failed to undeclare a default namespace. Could anyone point me a way out? Thanks. Regards, Xinjun -- Forwarded message -- From: *Xinjun Chen* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Date: Jul 19, 2007 12:54 PM Subject: [AXIOM] Undeclare default namespace To: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Hi, I have some problem undeclaring the default namespace in an OMElement. I have tried the following three ways but all failed. The default namespace is still in the OMElement. #1: OMElement reqElement = ; reqElement.declareDefaultNamespace (); #2: OMElement reqElement = ; reqElement.declareNamespace(, ); #3: OMElement reqElement = ; OMFactory omFactory = reqElement.getOMFactory(); OMNamespace ns = omFactory.createOMNamespace(, ); reqElement.declareNamespace(ns); Could anyone point me out what I can do to undeclare the default namespace in AXIOM? Thanks for your help in advance. Regards, Xinjun -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGo5JvjON2uBzUhh8RAlM6AJoDKg+9UJTRdIVIDgwMgrtIkcvyZQCgmVss gisWSWkZr/pLyS9lRjOPGjY= =zx5V -END PGP SIGNATURE- - 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]
Re: How to provide own WSDL?
As quoted from Davanum Srinivas [EMAIL PROTECTED]: Please add the wsdl/xsd under meta-inf directory. WEB-INF/services/BookService/META-INF I have WEB-INF/services/my-services/META-INF/services.xml which contains various services (MyFirstService, MySecondService, and so on). Do I put the WSDL and XSD under: WEB-INF/services/my-services/META-INF/services.xml MyFirstService.wsdl MySecondService.wsdl ... xsd0.xsd xsd1.xsd ... or do I create: WEB-INF/services/MyFirstService/META-INF/ MyFirstService.wsdl xsd0.xsd xsd1.xsd ... WEB-INF/services/MySecondService/META-INF/ MySecondService.wsdl xsd0.xsd xsd1.xsd ... etc.? Kind regards, -- -- Gertjan van Oosten, [EMAIL PROTECTED], West Consulting B.V., +31 15 2191 600 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3009) Problem in returning comples type by WebService
Problem in returning comples type by WebService --- Key: AXIS2-3009 URL: https://issues.apache.org/jira/browse/AXIS2-3009 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: client-api Affects Versions: 1.2 Environment: Axis2 -1.2 Reporter: Amit Panwar Hi I am using axis2-1.2 . When i m trying to call the webservice it giving a RunTimeException. Exception in thread main java.lang.RuntimeException: java.lang.RuntimeException: Unexpected subelement Text at com.agilis.ils.ws.IlsAdminPublicAPIWSHttpportStub.fromOM(IlsAdminPublicAPIWSHttpportStub.java:46923) at com.agilis.ils.ws.IlsAdminPublicAPIWSHttpportStub.findMatchingProducts(IlsAdminPublicAPIWSHttpportStub.java:3380) at com.agilis.ils.ws.clientcode.IlsProductAdminWSClient.main(IlsProductAdminWSClient.java:203) Caused by: java.lang.RuntimeException: Unexpected subelement Text at com.agilis.ils.ws.IlsAdminPublicAPIWSHttpportStub$FindMatchingProductsResponse$Factory.parse(IlsAdminPublicAPIWSHttpportStub.java:33121) at com.agilis.ils.ws.IlsAdminPublicAPIWSHttpportStub.fromOM(IlsAdminPublicAPIWSHttpportStub.java:46861) I think this is beacuse of returning a complex type from webservice . if (reader.isStartElement() new javax.xml.namespace.QName(http://ws.ils.agilis.com/xsd,return;).equals(reader.getName())) I think this code is giving error. If anybody have any idea , then please reply. Thanks in advance. Thanks and regards Amit Panwar -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to provide own WSDL?
Option #1. On 7/24/07, Gertjan van Oosten [EMAIL PROTECTED] wrote: As quoted from Davanum Srinivas [EMAIL PROTECTED]: Please add the wsdl/xsd under meta-inf directory. WEB-INF/services/BookService/META-INF I have WEB-INF/services/my-services/META-INF/services.xml which contains various services (MyFirstService, MySecondService, and so on). Do I put the WSDL and XSD under: WEB-INF/services/my-services/META-INF/services.xml MyFirstService.wsdl MySecondService.wsdl ... xsd0.xsd xsd1.xsd ... or do I create: WEB-INF/services/MyFirstService/META-INF/ MyFirstService.wsdl xsd0.xsd xsd1.xsd ... WEB-INF/services/MySecondService/META-INF/ MySecondService.wsdl xsd0.xsd xsd1.xsd ... etc.? Kind regards, -- -- Gertjan van Oosten, [EMAIL PROTECTED], West Consulting B.V., +31 15 2191 600 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to provide own WSDL?
As quoted from Davanum Srinivas [EMAIL PROTECTED]: Option #1. On 7/24/07, Gertjan van Oosten [EMAIL PROTECTED] wrote: As quoted from Davanum Srinivas [EMAIL PROTECTED]: Please add the wsdl/xsd under meta-inf directory. WEB-INF/services/BookService/META-INF I have WEB-INF/services/my-services/META-INF/services.xml which contains various services (MyFirstService, MySecondService, and so on). Do I put the WSDL and XSD under: WEB-INF/services/my-services/META-INF/services.xml MyFirstService.wsdl MySecondService.wsdl ... xsd0.xsd xsd1.xsd ... If I do that, getting the WSDL: http://localhost:8080/my-webapp/services/MyFirstService?wsdl returns exactly 0 bytes, and my web services throw an exception: HTTP/1.1 500 Internal Server Error Server: Apache-Coyote/1.1 Content-Type: text/xml;charset=UTF-8 Transfer-Encoding: chunked Date: Tue, 24 Jul 2007 14:21:38 GMT Connection: close ?xml version='1.0' encoding='UTF-8'?soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;soapenv:Bodysoapenv:Faultfaultcodesoapenv:Client/faultcodefaultstringThe service cannot be found for the endpoint reference (EPR) http://localhost:8080/my-webapp-ws/services/MyFirstService/faultstringdetailExceptionorg.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) http://localhost:8080/my-webapp/services/MyFirstService at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:63) at org.apache.axis2.engine.Phase.invoke(Phase.java:308) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:132) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:276) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:119) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:541) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) /Exception/detail/soapenv:Fault/soapenv:Body/soapenv:Envelope So what now? Kind regards, -- -- Gertjan van Oosten, [EMAIL PROTECTED], West Consulting B.V., +31 15 2191 600 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][Axis2] Shivantha Huruggamuwa as an Axis2 commiter
+1 from me Rajith On 7/24/07, Lahiru Sandakith [EMAIL PROTECTED] wrote: +1 indeed, He was the main contributer to make the two IDE plugins looks similar and behave with similar functionalities. On 7/24/07, Deepal Jayasinghe [EMAIL PROTECTED] wrote: Hi All, Shivantha has been helping Axis2 for quite a while now, he has done a number of bug fixes in Axis2 IDEA plug-in. He has spend most his time on getting both Eclipse and IntelJ Idea plugins to consistent state. He has created a number of JIRAs and submitted more then 12 patches , so I think he has done more than enough to get Axis2 commit access. Here is my +1 for Shivantha as an Axis2 commiter. Thanks Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
[jira] Commented: (AXIS2-3002) Axis 1.3RC2 does not work properly on websphere
[ https://issues.apache.org/jira/browse/AXIS2-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515002 ] Kent Watanabe commented on AXIS2-3002: -- Dustin, One other thing, the soap 1.1 wsdl also has a problem, where it is requiring the useOriginalwsdl to be set in the services.xml. When the same axis2.war and version.aar is executed it responds with you must have useOriginalwsdl set to false in order to auto generate wsdl. I tried setting this parameter and tried to set the service tag's attribute and that does not seem to work. Kent Axis 1.3RC2 does not work properly on websphere --- Key: AXIS2-3002 URL: https://issues.apache.org/jira/browse/AXIS2-3002 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Affects Versions: 1.3 Environment: Websphere 6.0.2 Reporter: Kent Watanabe Assignee: Charitha Kankanamge Attachments: Websphere-axis2.JPG The new axis2.war does not work properly on websphere. There are problems with the wsdl2 generation, and the wsdl 1.1 genaration. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to deploy exploded .aar under axis2?
Gertjan van Oosten wrote: As quoted from Sanjiva Weerawarana [EMAIL PROTECTED]: Can you post your services.xml? The error seems to say that you have two services with the same name. No, it does work if I use the .aar file unexploded. And anyway, the fact that it is reproducable by exploding Axis' own version-1.3-RC2.aar says it all, no? It does certainly .. sorry for the pain :(. We'll fix it. Sanjiva. -- Sanjiva Weerawarana, Ph.D. Founder Director; Lanka Software Foundation; http://www.opensource.lk/ Founder, Chairman CEO; WSO2, Inc.; http://www.wso2.com/ Director; Open Source Initiative; http://www.opensource.org/ Member; Apache Software Foundation; http://www.apache.org/ Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Rampart 1.2 source code
Hello, I went to the SVN repository according to this page: http://ws.apache.org/rampart/source-repository.html I checked out the Rampart source code anonymously, but it is the latest version, and I want to check out the Rampart 1.2 release source code. How can I do this? Thanks in advance, Estevao Rohr.
[jira] Commented: (AXIS2-2990) WSDL port address is not correctly generated for machines having multiple network interfaces
[ https://issues.apache.org/jira/browse/AXIS2-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515038 ] Haneef Ali commented on AXIS2-2990: --- Though I haven't tested this, not sure how this will work. Consider the following scenario. 1) Weblogic with two servers running in host1 and host2. 2) If i have MyWebapp.war , single war can be deployed in both host1 and host2 3) axis.war is now deployed in both host1 and host2. Hostname is part of axis.xml. Do you want me to hardcode the hostname. If it is hardcoded, then it breaks the concept of deploying single war in many servers. Haneef WSDL port address is not correctly generated for machines having multiple network interfaces Key: AXIS2-2990 URL: https://issues.apache.org/jira/browse/AXIS2-2990 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: wsdl Affects Versions: 1.2 Environment: Windows Reporter: Haneef Ali WSDL portAddress is filled with machines IP address. The code to get the IP address org.apache.axis2.transport.http.sever.HTTPUtils.getIpAddress() always takes the first available network interfaces ip address. This may not work in machine which has vmvare installed, or machines having multiple network interfaces or just a laptop which has wireless and wired lan. I believe that Correct way to do that it, is to use the hostName and resolve it to ipAddress. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3002) Axis 1.3RC2 does not work properly on websphere
[ https://issues.apache.org/jira/browse/AXIS2-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515037 ] Dustin Amrhein commented on AXIS2-3002: --- Kent, I have not seen this particular problem before. Is this problem specific to SOAP 1.1 WSDL? Do you have any more information about the error (i.e. traces/stack traces)? Thanks, Dustin Axis 1.3RC2 does not work properly on websphere --- Key: AXIS2-3002 URL: https://issues.apache.org/jira/browse/AXIS2-3002 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Affects Versions: 1.3 Environment: Websphere 6.0.2 Reporter: Kent Watanabe Assignee: Charitha Kankanamge Attachments: Websphere-axis2.JPG The new axis2.war does not work properly on websphere. There are problems with the wsdl2 generation, and the wsdl 1.1 genaration. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3002) Axis 1.3RC2 does not work properly on websphere
[ https://issues.apache.org/jira/browse/AXIS2-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515040 ] Kent Watanabe commented on AXIS2-3002: -- No stack trace just a response from the webservice Axis 1.3RC2 does not work properly on websphere --- Key: AXIS2-3002 URL: https://issues.apache.org/jira/browse/AXIS2-3002 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Affects Versions: 1.3 Environment: Websphere 6.0.2 Reporter: Kent Watanabe Assignee: Charitha Kankanamge Attachments: Websphere-axis2.JPG The new axis2.war does not work properly on websphere. There are problems with the wsdl2 generation, and the wsdl 1.1 genaration. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Rampart 1.2 source code
Check out the source code from the following url. http://svn.apache.org/repos/asf/webservices/rampart/tags/java/1_2/ Regards Sameera On 7/24/07, Estêvão Rohr [EMAIL PROTECTED] wrote: Hello, I went to the SVN repository according to this page: http://ws.apache.org/rampart/source-repository.html I checked out the Rampart source code anonymously, but it is the latest version, and I want to check out the Rampart 1.2 release source code. How can I do this? Thanks in advance, Estevao Rohr. -- Sameera http://sameera-jayasoma.blogspot.com/ http://www.flickr.com/photos/sameera-jayasoma - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2990) WSDL port address is not correctly generated for machines having multiple network interfaces
[ https://issues.apache.org/jira/browse/AXIS2-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515042 ] Davanum Srinivas commented on AXIS2-2990: - Haneef, Please Use Axis2 1.3 RC2, don't use hostname, the correct name is picked up from the http header host1 or host2 thanks, dims WSDL port address is not correctly generated for machines having multiple network interfaces Key: AXIS2-2990 URL: https://issues.apache.org/jira/browse/AXIS2-2990 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: wsdl Affects Versions: 1.2 Environment: Windows Reporter: Haneef Ali WSDL portAddress is filled with machines IP address. The code to get the IP address org.apache.axis2.transport.http.sever.HTTPUtils.getIpAddress() always takes the first available network interfaces ip address. This may not work in machine which has vmvare installed, or machines having multiple network interfaces or just a laptop which has wireless and wired lan. I believe that Correct way to do that it, is to use the hostName and resolve it to ipAddress. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][Axis2] Shivantha Huruggamuwa as an Axis2 commiter
+1 Thanks, Keith. On 7/24/07, Deepal Jayasinghe [EMAIL PROTECTED] wrote: Hi All, Shivantha has been helping Axis2 for quite a while now, he has done a number of bug fixes in Axis2 IDEA plug-in. He has spend most his time on getting both Eclipse and IntelJ Idea plugins to consistent state. He has created a number of JIRAs and submitted more then 12 patches , so I think he has done more than enough to get Axis2 commit access. Here is my +1 for Shivantha as an Axis2 commiter. Thanks Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Keith Chapman WSO2 Inc. Oxygen for Web Services Developers. http://wso2.org/
Re: [Axis2] Axis2 1.3 branch created
I agree. we should remove clustering from axis2-version.jar for 1.3 thanks, dims On 7/23/07, Saminda Abeyruwan [EMAIL PROTECTED] wrote: Hi, When creating the axi2-version.jar, it does include clustering related classes as well. Should we do so ?. If it should be included, Axis2 need to be compiled in Java 1.5 though MVN compiler source is 1.4. On the other hand integration module has dependency to JWS module. This cause compilation to fail on 1.4. Should we need to cleanup this for 1.3 ? Thank you Saminda On 7/20/07, Davanum Srinivas [EMAIL PROTECTED] wrote: Great!. Am willing to help with merging stuff from the trunk as usual. Another biggie left is the docs and javadocs integration into the generated artifacts! thanks, dims On 7/20/07, Deepal Jayasinghe [EMAIL PROTECTED] wrote: Hi Dims Deepal, So the POA is to get the releases out for all the dependencies that we use SNAPSHOT for and then cut Final? I think we can get the Axiom , XmlScheam and neethi soon in the next week and Woden will start their M7b release on Monday. How about an ETA, Next Friday? Sound good. Thanks Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Saminda Abeyruwan Software Engineer WSO2 Inc. - www.wso2.org -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3001) Problem in 1.3 RC with deserialization of java.util.Date objects that are DateTime formatted.
[ https://issues.apache.org/jira/browse/AXIS2-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-3001: Fix Version/s: 1.3 Problem in 1.3 RC with deserialization of java.util.Date objects that are DateTime formatted. - Key: AXIS2-3001 URL: https://issues.apache.org/jira/browse/AXIS2-3001 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: adb Affects Versions: 1.3 Environment: Axis 1.3 RC2, JDK 1.6 on Linux Reporter: Sathija Pavuluri Assignee: Amila Chinthaka Suriarachchi Priority: Blocker Fix For: 1.3 This bug was introduced after the fix that was made for jira AXIS2-2701. I had originally written my comment against 2701 but since the bug is marked as resolved, thought this new issue should be tracked separately. The fix for AXIS2-2701 makes it impossible for java.util.Date objects to be deserialized when the date is datetime formatted (i.e. -mm-dd hh:mm:ss). It now only works for date format objects (i.e. -mm-dd) For example I have an object with attribute: java.util.Date timeStarted; The element in the response looks like this: ax26:timeStarted2007-07-23T13:20:46.861Z/ax26:timeStarted The deserialization of this element fails with this exception: java.lang.RuntimeException: In valid string sufix at org.apache.axis2.databinding.utils.ConverterUtil.convertToDate(ConverterUtil.java:378) at org.apache.axis2.databinding.typemapping.SimpleTypeMapper.makeDate(SimpleTypeMapper.java:304) at org.apache.axis2.databinding.typemapping.SimpleTypeMapper.getSimpleTypeObject(SimpleTypeMapper.java:117) at org.apache.axis2.databinding.utils.BeanUtil.deserialize(BeanUtil.java:364) at org.apache.axis2.databinding.utils.BeanUtil.processObject(BeanUtil.java:644) at org.apache.axis2.databinding.utils.BeanUtil.ProcessElement(BeanUtil.java:592) at org.apache.axis2.databinding.utils.BeanUtil.deserialize(BeanUtil.java:528) Looking at the code, it seems like the ConverterUtil expects the Date object to be only of -mm-dd format. It fails in the case when Date is -mm-dd hh:mm:ss formatted? Thanks, Sathija. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2994) Problem when trying to move service from axis 1.4 to axis 2 1.3RC2
[ https://issues.apache.org/jira/browse/AXIS2-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-2994: Fix Version/s: 1.3 Problem when trying to move service from axis 1.4 to axis 2 1.3RC2 -- Key: AXIS2-2994 URL: https://issues.apache.org/jira/browse/AXIS2-2994 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: databinding Affects Versions: 1.3 Environment: XP Professional, Tomcat App server 5.5 Reporter: Steve Kruse Assignee: Amila Chinthaka Suriarachchi Priority: Blocker Fix For: 1.3 Attachments: TrackLiteDataHandlerWSServiceMessageReceiverInOut.java, wsdl_schema.zip I use a wsdl file which works in 1.4 and run it thru wsdl2java in axis2 1.3rc2 and everything builds properly. The service deploys fine and then when I try to use the service I get the following stack trace from the soap monitor: ?xml version='1.0' encoding='utf-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body soapenv:Fault faultcodesoapenv:Client/faultcode faultstringorg.apache.xmlbeans.impl.values.XmlComplexContentImpl cannot be cast to peoiws5.mdiapps.soap.HandleTrackInfoLiteEventDocument/faultstring detail Exception org.apache.axis2.AxisFault: org.apache.xmlbeans.impl.values.XmlComplexContentImpl cannot be cast to peoiws5.mdiapps.soap.HandleTrackInfoLiteEventDocument#xd; at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417)#xd; at com.am.service.xmlbeans.TrackLiteDataHandlerWSServiceMessageReceiverInOut.fromOM(TrackLiteDataHandlerWSServiceMessageReceiverInOut.java:322)#xd; at com.am.service.xmlbeans.TrackLiteDataHandlerWSServiceMessageReceiverInOut.invokeBusinessLogic(TrackLiteDataHandlerWSServiceMessageReceiverInOut.java:42)#xd; at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.invokeBusinessLogic(AbstractInOutSyncMessageReceiver.java:42)#xd; at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:95)#xd; at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:145)#xd; at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:276)#xd; at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:119)#xd; at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)#xd; at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)#xd; at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)#xd; at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)#xd; at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210)#xd; at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)#xd; at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)#xd; at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)#xd; at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)#xd; at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)#xd; at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870)#xd; at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)#xd; at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)#xd; at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)#xd; at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685)#xd; at java.lang.Thread.run(Thread.java:619)#xd; Caused by: java.lang.ClassCastException: org.apache.xmlbeans.impl.values.XmlComplexContentImpl cannot be cast to peoiws5.mdiapps.soap.HandleTrackInfoLiteEventDocument#xd; at peoiws5.mdiapps.soap.HandleTrackInfoLiteEventDocument$Factory.parse(HandleTrackInfoLiteEventDocument.java:128)#xd; at com.am.service.xmlbeans.TrackLiteDataHandlerWSServiceMessageReceiverInOut.fromOM(TrackLiteDataHandlerWSServiceMessageReceiverInOut.java:220)#xd; ... 22 more#xd; /Exception /detail /soapenv:Fault /soapenv:Body /soapenv:Envelope The wsdl I am using is below: ?xml version=1.0 encoding=UTF-8? wsdl:definitions targetNamespace=urn:soap.mdiapps.peoiws5
Re: [VOTE][Axis2] Shivantha Huruggamuwa as an Axis2 commiter
+1 Thanks! Rich Scheuerle IBM Web Services Apache Axis2 ([EMAIL PROTECTED]) 512-838-5115 (IBM TL 678-5115) keith chapman [EMAIL PROTECTED] wrote on 07/24/2007 12:42:58 PM: +1 Thanks, Keith. On 7/24/07, Deepal Jayasinghe [EMAIL PROTECTED] wrote: Hi All, Shivantha has been helping Axis2 for quite a while now, he has done a number of bug fixes in Axis2 IDEA plug-in. He has spend most his time on getting both Eclipse and IntelJ Idea plugins to consistent state. He has created a number of JIRAs and submitted more then 12 patches , so I think he has done more than enough to get Axis2 commit access. Here is my +1 for Shivantha as an Axis2 commiter. Thanks Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Keith Chapman WSO2 Inc. Oxygen for Web Services Developers. http://wso2.org/
Re: [VOTE][Axis2] Shivantha Huruggamuwa as an Axis2 commiter
+1 - Ann Deepal Jayasinghe [EMAIL PROTECTED] e.lk To axis-dev@ws.apache.org 07/24/2007 03:33 axis-dev@ws.apache.org AM cc Subject Please respond to [VOTE][Axis2] Shivantha Huruggamuwa [EMAIL PROTECTED] as an Axis2 commiter e.org Hi All, Shivantha has been helping Axis2 for quite a while now, he has done a number of bug fixes in Axis2 IDEA plug-in. He has spend most his time on getting both Eclipse and IntelJ Idea plugins to consistent state. He has created a number of JIRAs and submitted more then 12 patches , so I think he has done more than enough to get Axis2 commit access. Here is my +1 for Shivantha as an Axis2 commiter. Thanks Deepal inline: graycol.gifinline: pic00888.gifinline: ecblank.gif
[jira] Created: (AXIS2-3010) BeanUtil Deserialize has exponential runtime error when deserializing arrays
BeanUtil Deserialize has exponential runtime error when deserializing arrays Key: AXIS2-3010 URL: https://issues.apache.org/jira/browse/AXIS2-3010 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: adb Affects Versions: 1.1.1, 1.2 Environment: Windows xp, tomcat, java 1.5, running POJO services via RPCServiceClient Reporter: Nathan Wray When an OMElement is deserialized into a POJO and the POJO has a setter/getter pair with an Array parameter, the result object is created and set into the POJO once for each member of the array. So for example an object with String [] getHeaders() void setHeaders(String[] h) where h[] is an array with 80 elements, the array h will be created 80 times and setHeaders will be called 80 times rather than once. This causes incredibly poor performance. It appears to be due to a pattern where each child in the element tree causes a jump back up to the parent and a re-creation of that array result. This is very easy to recreate by instrumenting a set method that accepts an array. I patched this locally in the 1_1_1 version of BeanUtil by changing line 283 from PropertyDescriptor prty = (PropertyDescriptor) properties.get(partsLocalName); to PropertyDescriptor prty = (PropertyDescriptor) properties.remove(partsLocalName); This removes the definition of the set method after it's called the first time, so the remainder of the array elements don't cause the entire result to be recreated over and over. I looked at the 1.2 code and this does not appear to be resolved. The performance impact in my case, with 4700 result objects in an array, with each result object having a further array of 77 fields, was huge. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Missing spring and soapmonitor jars in RC2
Deepal, Dims et all, These jars were in the 1.2 release war, and are missing in the 1.3 RC2 axis2 war : axis2-soapmonitor-1.3.jar axis2-spring-1.2.jar Robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3011) ServiceDescription caching leads to memory leak
ServiceDescription caching leads to memory leak --- Key: AXIS2-3011 URL: https://issues.apache.org/jira/browse/AXIS2-3011 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Jarek Gawor The DescriptionFactoryImpl.createServiceDescription() function attempts to cache/reuse the ServiceDescription objects and that leads to memory leaks. First, a Hashtable is used for the cache. That means, any ServiceDescription created will always live in the cache and won't ever be reclaimed (and there is no clear cache function). Some sort of WeakHashMap could help the problem so that at least some unused ServiceDescription objects could be reclaimed. Second, the createServiceDescription() uses the DescriptionFactory.createClientConfigurationFactory().getClientConfigurationContext() to get the client configuration context. It looks like by default the ClientConfigurationFactory.getClientConfigurationContext() does NOT cache the configuration context. Therefore, each call creates a new configuration object. That means, that by default ServiceDescription will NOT be reused since the configuration context object instance is used to determine if the ServiceDescription should be reused or not (see DescriptionKey.equals() function). So, a simple program that calls createServiceDescription() repeatably in a loop (with the same arguments) will quickly run out of memory. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3012) Invalid param in content-Type with multipart/related value
Invalid param in content-Type with multipart/related value -- Key: AXIS2-3012 URL: https://issues.apache.org/jira/browse/AXIS2-3012 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: transports Reporter: Samuel Isokpunwu Per RFC2387, A content-Type header field with a multipart/related value must not include any encoding as a parameter. Current implementation is including charset=UTF-8 parameter in the content-type header field. Will be providing a patch to resolve this defect. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[XmlSchema] Pluggability for XSD import/include resolvers?
Hi, We currently use XmlSchema to load XSDs. To resolve the import/include directives using our schemes, we provide an implementation of org.apache.ws.commons.schema.resolver.URIResolver and set it to org.apache.ws.commons.schema.XmlSchemaCollection. It works well if the schemaLocation attribute for the xsd:import or xsd:include is set. Now we would like to handle the cases where the schemaLocation attribute is not present. For example, xsd:import namespace=http://ns1/. Without the schemaLocation, we resolve the import/include by namespace. In this case, we already have a map keyed by namespace for a list of XmlSchema objects loaded from a catalog or other files and we want to reuse them. Would it be possible to open the XmlSchemaCollection.getSchema(SchemaKey) method so that we can override/customize the behavior to associate existing XmlSchema instances to a SchemaKey? BTW, using a singleton of XmlSchemaCollection to keep the schema map is not always feasible. Another observation is that a NPE will be thrown if the URIResolver.resolveEntity() returns null. Is there any way to disable the aggressive resolving/loading of import/include? [EMAIL PROTECTED] Raymond Feng Apache Tuscany - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3012) Invalid param in content-Type with multipart/related value
[ https://issues.apache.org/jira/browse/AXIS2-3012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Isokpunwu updated AXIS2-3012: Attachment: bt68092patch.txt A patch to resolve code defect. Invalid param in content-Type with multipart/related value -- Key: AXIS2-3012 URL: https://issues.apache.org/jira/browse/AXIS2-3012 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: transports Reporter: Samuel Isokpunwu Attachments: bt68092patch.txt Per RFC2387, A content-Type header field with a multipart/related value must not include any encoding as a parameter. Current implementation is including charset=UTF-8 parameter in the content-type header field. Will be providing a patch to resolve this defect. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3002) Axis 1.3RC2 does not work properly on websphere
[ https://issues.apache.org/jira/browse/AXIS2-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515136 ] Dustin Amrhein commented on AXIS2-3002: --- Kent, Are you just requesting the WSDL for the web service via something like ?wsdl? I am not too sure what you are trying to do here. Does this problem still occur with the classloader policy change I mentioned above? Does it only occur on SOAP 1.1? Thanks Axis 1.3RC2 does not work properly on websphere --- Key: AXIS2-3002 URL: https://issues.apache.org/jira/browse/AXIS2-3002 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Affects Versions: 1.3 Environment: Websphere 6.0.2 Reporter: Kent Watanabe Assignee: Charitha Kankanamge Attachments: Websphere-axis2.JPG The new axis2.war does not work properly on websphere. There are problems with the wsdl2 generation, and the wsdl 1.1 genaration. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-3002) Axis 1.3RC2 does not work properly on websphere
[ https://issues.apache.org/jira/browse/AXIS2-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-3002. - Resolution: Fixed Charitha, Checked in a fix to both trunk (559291) and branch (559293). Please cross check. thanks, dims Axis 1.3RC2 does not work properly on websphere --- Key: AXIS2-3002 URL: https://issues.apache.org/jira/browse/AXIS2-3002 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Affects Versions: 1.3 Environment: Websphere 6.0.2 Reporter: Kent Watanabe Assignee: Charitha Kankanamge Attachments: Websphere-axis2.JPG The new axis2.war does not work properly on websphere. There are problems with the wsdl2 generation, and the wsdl 1.1 genaration. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2]Secure + Reliable with SMTP issue
+1 for adding a new phase and resolve the issue. That way it clear for anybody to figure out the order Addressing-Security-RM -jaliya - Original Message - From: Deepal Jayasinghe [EMAIL PROTECTED] To: axis-dev@ws.apache.org Sent: Tuesday, July 24, 2007 4:35 AM Subject: Re: [Axis2]Secure + Reliable with SMTP issue I will introduce a new phase called Addressing and go forward , let's revert that if we found and issue. Thanks Deepal Sanjiva Weerawarana wrote: +1 ... I think we need to ship an Axis2 that can compose nicely and easily with Rampart and Sandesha to make secure+RM work correctly for HTTP and SMTP (basically for all transports we support). Sanjiva. Deepal Jayasinghe wrote: Hi Dims, No the issues is client side when someone tries to use RM+ Security then he has to go and change axis2.xml. Other thing is for security to work correctly it is required to have addressing based dispatcher before security handlers. And using a security is common case so I think default axis2.xml should support that. Thanks Deepal Deepal, IMHO, This can be documented and fixed post 1.3 I can see folks who are working on an advanced scenario comfortable with a custom axis2.xml. thanks, dims - 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]
Re: How to deploy exploded .aar under axis2?
Hi Gertjan, I tested that in both tomcat and standalone version but I did not get the exception and the service got deployed without having any issues. Thanks Deepal As quoted from Sanjiva Weerawarana [EMAIL PROTECTED]: Can you post your services.xml? The error seems to say that you have two services with the same name. No, it does work if I use the .aar file unexploded. And anyway, the fact that it is reproducable by exploding Axis' own version-1.3-RC2.aar says it all, no? Regards, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to deploy exploded .aar under axis2?
I did the same thing and it worked for me as well. Thanks Deepal Gertjan van Oosten wrote: Hi Deepal, As quoted from Deepal jayasinghe [EMAIL PROTECTED]: If that is the case try to provide me to regenerate the issue , may be you can write light weight version and send It's even simpler than that: I can reproduce it by unpacking the version-1.3-RC2.aar that's bundled with axis2-1.3-RC2.war! So there you go: a perfect testcase for you. ;-) I unpacked version-1.3-RC2.aar which comes with Axis2 and restarted tomcat (I was running tomcat 6.0.10). I did not get such an error. FYI: I attached a screen shot with my exploded aar and tomcat startup. You will definitely get the following exception if both unpacked aar and version-*.aar are placed in the WEB-INF/services directory. Probably you haven't removed one of them. 2007-07-24 22:43:18,703 ERROR org.apache.axis2.deployment.ServiceDeployer - The version-1.3-RC2.aar service, which is not valid, caused Two services cannot have same name. A service with the Version name already exists in the system. org.apache.axis2.AxisFault: Two services cannot have same name. A service with the Version name alr eady exists in the system. at org.apache.axis2.engine.AxisConfiguration.addToAllServicesMap(AxisConfiguration.java:356) Thanks and regards Charitha - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [axis2] Re: svn commit: r559011 - in /webservices/axis2/trunk/java/modules: addressing/src/META-INF/ integration/conf/ integration/test-resources/deployment/ integration/test-resources/mtom/ integ
Hi Glen, Yes I have to agree with you , but let's do that for next release. I would like to consider that as the first item to be fixed. Thanks Deepal [Forward with correct prefix] Gosh. If only Modules ... http://marc.info/?l=axis-devm=118117804705440w=2 ... could define their own Phases http://marc.info/?l=axis-devm=114404998012486w=2 this commit could have consisted of a simple change to the Addressing module's module.xml, and that would basically be it. This demonstrates, once again, exactly the problem with the current overly-static design. I still stand by the position I wrote up last year: http://marc.info/?l=axis-devm=114417377917696w=2 This needs to be fixed after 1.3, folks. --Glen [EMAIL PROTECTED] wrote: Author: deepal Date: Tue Jul 24 04:41:00 2007 New Revision: 559011 URL: http://svn.apache.org/viewvc?view=revrev=559011 Log: -Add a phase called Addressing as I mentioned in the mailing list - Move all the addressing handlers into Addressing phase - Had to modify a set of axis2.xml and test cases to cope this chang [This is a big commit but no need to worry :) ] Modified: webservices/axis2/trunk/java/modules/addressing/src/META-INF/module.xml webservices/axis2/trunk/java/modules/integration/conf/axis2.xml webservices/axis2/trunk/java/modules/integration/test-resources/deployment/deployment.both.axis2.xml webservices/axis2/trunk/java/modules/integration/test-resources/mtom/MTOM-enabled-axis2.xml webservices/axis2/trunk/java/modules/integration/test-resources/mtom/MTOM-fileCache-enabled-axis2.xml webservices/axis2/trunk/java/modules/integration/test-resources/swa/SwA-enabled-axis2.xml webservices/axis2/trunk/java/modules/integration/test-resources/swa/SwA-fileCache-enabled-axis2.xml webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/engine/HandlerExecutionTest.java webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/engine/chunking-disabled-axis2.xml webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/engine/chunking-enabled-axis2.xml webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/engine/commons-http-enabled-axis2.xml webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/jms/jms-enabled-client-axis2.xml webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/jms/jms-enabled-server-axis2.xml webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/mail/mail-enabled-axis2.xml webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/mail/mail-enabled-client-axis2.xml webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/mail/mail-enabled-server-axis2.xml webservices/axis2/trunk/java/modules/kernel/conf/axis2.xml webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/axis2_default.xml webservices/axis2/trunk/java/modules/kernel/test/org/apache/axis2/deployment/ModuleDisengagementTest.java - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3013) axis2server console output is not shown
axis2server console output is not shown --- Key: AXIS2-3013 URL: https://issues.apache.org/jira/browse/AXIS2-3013 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.3 Environment: winxp, jdk15 Reporter: Charitha Kankanamge Assignee: Deepal Jayasinghe Priority: Critical When starting axis2server, it does not return output to the server console. Steps to reproduce: 1. Start axis2server in axis2-1.3-RC2 2. Check the console. Nothing will be shown there. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3014) java.lang.IllegalStateException when deploying axis2.war on tomcat 4.0.3
java.lang.IllegalStateException when deploying axis2.war on tomcat 4.0.3 Key: AXIS2-3014 URL: https://issues.apache.org/jira/browse/AXIS2-3014 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.3 Environment: winxp, jdk14, tomcat 4.0.3, Axis2-1.3-RC2 Reporter: Charitha Kankanamge Following exception thrown when accessing axis2 admin page (http://localhost:8080/axis2) if axis2.war is deployed on tomcat4.0.3. java.lang.IllegalStateException at org.apache.jasper.runtime.ServletResponseWrapperInclude.getOutputStream(ServletResponseWrapperInclude.java:109) at org.apache.catalina.servlets.DefaultServlet.serveResource(DefaultServlet.java:1146) at org.apache.catalina.servlets.DefaultServlet.doGet(DefaultServlet.java:519) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:683) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:497) at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:819) at org.apache.jsp.index$jsp._jspService(index$jsp.java:76) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:202) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:382) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:474) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2343) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1012) at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1107) at java.lang.Thread.run(Thread.java:534) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (AXIS2-3012) Invalid param in content-Type with multipart/related value
[ https://issues.apache.org/jira/browse/AXIS2-3012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe reassigned AXIS2-3012: Assignee: Thilina Gunarathne Invalid param in content-Type with multipart/related value -- Key: AXIS2-3012 URL: https://issues.apache.org/jira/browse/AXIS2-3012 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: transports Reporter: Samuel Isokpunwu Assignee: Thilina Gunarathne Attachments: bt68092patch.txt Per RFC2387, A content-Type header field with a multipart/related value must not include any encoding as a parameter. Current implementation is including charset=UTF-8 parameter in the content-type header field. Will be providing a patch to resolve this defect. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: measuring Axix 1.4 overhead
As I know in WSO2 WSAS you can deploy Axis1 services inside Axis2 without having any pain. So that you do not need to re-write anything to use Axis2 , if you are an Axis1 user. Thanks Deepal Please see this http://ws.apache.org/axis2/1_2/migration.html -jaliya - Original Message - *From:* Firas Khasawneh (fkhasawn) mailto:[EMAIL PROTECTED] *To:* Jaliya Ekanayake mailto:[EMAIL PROTECTED] *Cc:* axis-dev@ws.apache.org mailto:axis-dev@ws.apache.org *Sent:* Tuesday, July 24, 2007 12:22 PM *Subject:* RE: measuring Axix 1.4 overhead Hi Jaliya, To use Axis2 do I need to change anything in my service code or rebuild it or can I just replace the library jars? Thanks, Firas *From:* Jaliya Ekanayake [mailto:[EMAIL PROTECTED] *Sent:* Tuesday, July 24, 2007 10:44 AM *To:* Firas Khasawneh (fkhasawn) *Cc:* axis-dev@ws.apache.org mailto:axis-dev@ws.apache.org *Subject:* Re: measuring Axix 1.4 overhead Hi Firas, Did you try Axis2 http://ws.apache.org/axis2/ ? In axis2 processing starts without fully building the soap envelope. And the performance figures for Axis2 is http://www.wso2.org/library/588 Thanks, -jaliya - Original Message - *From:* Firas Khasawneh (fkhasawn) mailto:[EMAIL PROTECTED] *To:* Jaliya Ekanayake mailto:[EMAIL PROTECTED] *Sent:* Tuesday, July 24, 2007 8:48 AM *Subject:* RE: measuring Axix 1.4 overhead Hi Jaliya, I tested with small size messages and 1 mb messages and there is big difference, looks like Axis takes long time to process large messages, but t4-t0 should give the processing time and not the transport time. Also invoke time t3-t0 should give only Axis engine overhead. Thanks, Firas *From:* Jaliya Ekanayake [mailto:[EMAIL PROTECTED] *Sent:* Monday, July 23, 2007 4:34 PM *To:* Firas Khasawneh (fkhasawn) *Subject:* Re: measuring Axix 1.4 overhead Hi Firas, Yes, t4-t0 should give you the results. However the problem is that you use large message size. My guess is that the processing happens before the total retrieval of the message and hence it include the time it takes to transfer the message as well. Did you try with a small message sizes? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3009) Problem in returning comples type by WebService
[ https://issues.apache.org/jira/browse/AXIS2-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515198 ] Deepal Jayasinghe commented on AXIS2-3009: -- How can we guess what the issues is without looking at the WSDL file, you could do one of the following two steps - Download Axis2 1.3-RC2 and test with that - Attach the WSDL file Thanks Deepal Problem in returning comples type by WebService --- Key: AXIS2-3009 URL: https://issues.apache.org/jira/browse/AXIS2-3009 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: client-api Affects Versions: 1.2 Environment: Axis2 -1.2 Reporter: Amit Panwar Hi I am using axis2-1.2 . When i m trying to call the webservice it giving a RunTimeException. Exception in thread main java.lang.RuntimeException: java.lang.RuntimeException: Unexpected subelement Text at com.agilis.ils.ws.IlsAdminPublicAPIWSHttpportStub.fromOM(IlsAdminPublicAPIWSHttpportStub.java:46923) at com.agilis.ils.ws.IlsAdminPublicAPIWSHttpportStub.findMatchingProducts(IlsAdminPublicAPIWSHttpportStub.java:3380) at com.agilis.ils.ws.clientcode.IlsProductAdminWSClient.main(IlsProductAdminWSClient.java:203) Caused by: java.lang.RuntimeException: Unexpected subelement Text at com.agilis.ils.ws.IlsAdminPublicAPIWSHttpportStub$FindMatchingProductsResponse$Factory.parse(IlsAdminPublicAPIWSHttpportStub.java:33121) at com.agilis.ils.ws.IlsAdminPublicAPIWSHttpportStub.fromOM(IlsAdminPublicAPIWSHttpportStub.java:46861) I think this is beacuse of returning a complex type from webservice . if (reader.isStartElement() new javax.xml.namespace.QName(http://ws.ils.agilis.com/xsd,return;).equals(reader.getName())) I think this code is giving error. If anybody have any idea , then please reply. Thanks in advance. Thanks and regards Amit Panwar -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (AXIS2-3007) RESTful services invocation self induces Input Stream Closed error
[
https://issues.apache.org/jira/browse/AXIS2-3007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe reassigned AXIS2-3007:
Assignee: Keith Godwin Chapman
RESTful services invocation self induces Input Stream Closed error
--
Key: AXIS2-3007
URL: https://issues.apache.org/jira/browse/AXIS2-3007
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Affects Versions: 1.2
Environment: Windows 2000, Eclipse IDE
Reporter: Jason Kania
Assignee: Keith Godwin Chapman
When making REST GET calls to an API, Axis 2 core sets its input stream to
null and then complains later that its stream has been closed. The following
partial stack trace demonstrates the problem.
ApplicationXMLBuilder.processDocument(InputStream, String, MessageContext)
line: 49
TransportUtils.createSOAPMessage(MessageContext, InputStream, String) line:
130
RESTUtil.processURLRequest(MessageContext, OutputStream, String) line: 98
AxisServlet$ProcessRESTRequest.processURLRequest() line: 776
AxisServlet.doGet(HttpServletRequest, HttpServletResponse) line: 238
AxisServlet(HttpServlet).service(HttpServletRequest, HttpServletResponse)
line: 707
AxisServlet(HttpServlet).service(ServletRequest, ServletResponse) line: 820
ServletHolder.handle(ServletRequest, ServletResponse) line: 487
...
In RESTUtil, method processURLRequest, the following call is made on line 98
soapEnvelope = TransportUtils
.createSOAPMessage(msgContext, null, contentType);
where the null is supposed to be the input stream
Thus, when line 49 of ApplicationXMLBuilder in method processDocument is
encountered,
PushbackInputStream pushbackInputStream = new
PushbackInputStream(inputStream);
where inputStream is null,
the exception java.io.IOException: Stream closed is generated once the
empty stream is read at line 51
of ApplicationXMLBuilder:
if ((b = pushbackInputStream.read()) 0) {
For straight Axis use, this issue is a blocker, but I have worked around the
problem by filtering empty get methods at the servlet level and am populating
them with content for now.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3007) RESTful services invocation self induces Input Stream Closed error
[
https://issues.apache.org/jira/browse/AXIS2-3007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515204
]
Keith Godwin Chapman commented on AXIS2-3007:
-
Axis2 uses a pluggable builder concept here. There is a mapping in your
axis2.xml which specifies the builder to use for a specific contentType. When
you do a GET (obviously it does not have a method body hence the inputStream is
null here) the content type would be application/x-www-form-urlencoded most
often than not (Firefox sends null hence we do a check and set the appropriate
content type). There is a mapping which says application/x-www-form-urlencoded
will be processed by org.apache.axis2.builder.XFormURLEncodedBuilder. In your
case whats happened is that it has tried to process it using
ApplicationXMLBuilder (which is the one to be used when the content type is
application/xml which had a body).
Can you check your axis2.xml on this. You should be able to solve it there
without using the workaround u've specified. I wonderwhether there was another
problem somewhere else. Could u please verify this. If the problem persists
please provide the steps to recreate the issue to gether with the builder
mappings in your axis2.xml.
RESTful services invocation self induces Input Stream Closed error
--
Key: AXIS2-3007
URL: https://issues.apache.org/jira/browse/AXIS2-3007
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Affects Versions: 1.2
Environment: Windows 2000, Eclipse IDE
Reporter: Jason Kania
Assignee: Keith Godwin Chapman
When making REST GET calls to an API, Axis 2 core sets its input stream to
null and then complains later that its stream has been closed. The following
partial stack trace demonstrates the problem.
ApplicationXMLBuilder.processDocument(InputStream, String, MessageContext)
line: 49
TransportUtils.createSOAPMessage(MessageContext, InputStream, String) line:
130
RESTUtil.processURLRequest(MessageContext, OutputStream, String) line: 98
AxisServlet$ProcessRESTRequest.processURLRequest() line: 776
AxisServlet.doGet(HttpServletRequest, HttpServletResponse) line: 238
AxisServlet(HttpServlet).service(HttpServletRequest, HttpServletResponse)
line: 707
AxisServlet(HttpServlet).service(ServletRequest, ServletResponse) line: 820
ServletHolder.handle(ServletRequest, ServletResponse) line: 487
...
In RESTUtil, method processURLRequest, the following call is made on line 98
soapEnvelope = TransportUtils
.createSOAPMessage(msgContext, null, contentType);
where the null is supposed to be the input stream
Thus, when line 49 of ApplicationXMLBuilder in method processDocument is
encountered,
PushbackInputStream pushbackInputStream = new
PushbackInputStream(inputStream);
where inputStream is null,
the exception java.io.IOException: Stream closed is generated once the
empty stream is read at line 51
of ApplicationXMLBuilder:
if ((b = pushbackInputStream.read()) 0) {
For straight Axis use, this issue is a blocker, but I have worked around the
problem by filtering empty get methods at the servlet level and am populating
them with content for now.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3001) Problem in 1.3 RC with deserialization of java.util.Date objects that are DateTime formatted.
[ https://issues.apache.org/jira/browse/AXIS2-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515210 ] Amila Chinthaka Suriarachchi commented on AXIS2-3001: - As I saw in the you have declared an xml element as xs:date type and you have received a response as ax26:timeStarted2007-07-23T13:20:46.861Z/ax26:timeStarted So you have received an invalid element(according to the xml spec). ADB serializes the Date object correctly(only date parts). please have look at with the RC2. if you want to parse that response then you have to declare your element as dateTime instead of date. But you make one point here. Why ADB has used the Calendar to resent the dateTime while it would have used the java.util.Date? Actually I can not give you an answer this question without going through the code and see any side effects of using the java.util.date. I think this was there from the begining. Please add a new jira for this as an ADB improvement. Problem in 1.3 RC with deserialization of java.util.Date objects that are DateTime formatted. - Key: AXIS2-3001 URL: https://issues.apache.org/jira/browse/AXIS2-3001 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: adb Affects Versions: 1.3 Environment: Axis 1.3 RC2, JDK 1.6 on Linux Reporter: Sathija Pavuluri Assignee: Amila Chinthaka Suriarachchi Priority: Blocker Fix For: 1.3 This bug was introduced after the fix that was made for jira AXIS2-2701. I had originally written my comment against 2701 but since the bug is marked as resolved, thought this new issue should be tracked separately. The fix for AXIS2-2701 makes it impossible for java.util.Date objects to be deserialized when the date is datetime formatted (i.e. -mm-dd hh:mm:ss). It now only works for date format objects (i.e. -mm-dd) For example I have an object with attribute: java.util.Date timeStarted; The element in the response looks like this: ax26:timeStarted2007-07-23T13:20:46.861Z/ax26:timeStarted The deserialization of this element fails with this exception: java.lang.RuntimeException: In valid string sufix at org.apache.axis2.databinding.utils.ConverterUtil.convertToDate(ConverterUtil.java:378) at org.apache.axis2.databinding.typemapping.SimpleTypeMapper.makeDate(SimpleTypeMapper.java:304) at org.apache.axis2.databinding.typemapping.SimpleTypeMapper.getSimpleTypeObject(SimpleTypeMapper.java:117) at org.apache.axis2.databinding.utils.BeanUtil.deserialize(BeanUtil.java:364) at org.apache.axis2.databinding.utils.BeanUtil.processObject(BeanUtil.java:644) at org.apache.axis2.databinding.utils.BeanUtil.ProcessElement(BeanUtil.java:592) at org.apache.axis2.databinding.utils.BeanUtil.deserialize(BeanUtil.java:528) Looking at the code, it seems like the ConverterUtil expects the Date object to be only of -mm-dd format. It fails in the case when Date is -mm-dd hh:mm:ss formatted? Thanks, Sathija. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (AXIS2-3006) base64binary serialization
[ https://issues.apache.org/jira/browse/AXIS2-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe reassigned AXIS2-3006: Assignee: Deepal Jayasinghe base64binary serialization -- Key: AXIS2-3006 URL: https://issues.apache.org/jira/browse/AXIS2-3006 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: databinding Affects Versions: 1.3 Environment: tested on Axis2 1.2 1.3 RC2 os: *nix , windows, tomcat : 5.5.23 java 1.6 Reporter: Georgi Yonchev Assignee: Deepal Jayasinghe Attachments: Res.java, services.wsdl, Test.java, Test_client.java using POJO's .. in Attachments : Res.java (the response object) Test.java (server) Test_client.java services.wsdl this happens when the response is some object with byte[] parameter inside it. this wsdl service.xml is generated automatically by the eclipse plug-in so, test2() always works, small/larger byte[] size in test() if you test with some string.getBytes() will work but larger ... no here is the soap payload : ns:byteData104/ns:byteDatans:byteData111/ns:byteDatans:byteData109/ns:byteDatans:byteData97/ns:byteDatans:byteData44/ns:byteDatans:byteData32/ns:byteDatans:byteData86/ns:byteDatans:byteData101/ns:byteDatans:byteData114/ns:byteDatans:byteData100/ns:byteDatans:byteData97/ns:byteDatans:byteData110/ns:byteDatans:byteData97/ns:byteDatans:byteData44/ns:byteDatans:byteData32/ns:byteDatans:byteData65/ns:byteDatans:byteData114/ns:byteDatans:byteData105/ns:byteDatans:byteData97/ns:byteDatans:byteData108/ns:byteDatans:byteData44/ns:byteDatans:byteData32/ns:byteDatans:byteData72/ns:byteDatans:byteData101/ns:byteDatans:byteData108/ns:byteDatans:byteData118/ns:byteDatans:byteData101/ns:byteDatans:byteData116/ns:byteDatans:byteData105/ns:byteDatans:byteData99/ns:byteDatans:byteData97/ns:byteDatans:byteData59/ns:byteDatans:byteData13/ns:byteDatans:b yteData10/ns:byteDatans:byteData9/ns:byteDatans:byteData102/ns:byteDatans:byteData111/ns:byteDatans:byteData110/ns:byteDatans:byteData116/ns:byteDatans:byteData45/ns:byteDatans:byteData115/ns:byteDatans:byteData105/ns:byteDatans:byteData122/ns:byteDatans:byteData101/ns:byteDatans:byteData58/ns:byteDatans:byteData32/ns:byteDatans:byteData49/ns:byteDatans:byteData48/ns:byteData ns:byteData112/ns:byteDatans:byteData116/ns:byteDatans:byteData59/ns:byteDatans:byteData13/ns:byteDatans:byteData10/ns:byteDatans:byteData9/ns:byteDatans:byteData102/ns:byteDatans:byteData111/ns:byteDatans:byteData110/ns:byteDatans:byteData116/ns:byteDatans:byteData45/ns:byteDatans:byteData119/ns:byteDatans:byteData101/ns:byteDatans:byteData105/ns:byteDatans:byteData103/ns:byteDatans:byteData104/ns:byteDatans:byteData116/ns:byteDatans:byteData58/ns:byteDatans:byteData32/ns:byteDatans:byteData110/ns:byteDatans:byteData111/ns:byteDatans:byteData114/ns:byteDatans:byteData109/ns:byteDatans:byteData97/ns:byteDatans:byteData108/ns:byteDatans:byteData59/ns:byteDatans:byteData13/ns:byteDatans:byteData10/ns:byteDatans:byteData125/ns:byteDatans:byteData13/ns:byteDatans:byteData10/ns:byteDatans:byteData46/ns:byteDatans:byteData99/ns:byteDatans:byteData111/ns:byteDatans:byteData110/n s:byteDatans:byteData 2000 116/ns:byteDatans:byteData101/ns:byteDatans:byteData110/ns:byteDatans:byteData116/ns:byteDatans:byteData49/ns:byteDatans:byteData123/ns:byteDatans:byteData13/ns:byteDatans:byteData10/ns:byteDatans:byteData9/ns:byteDatans:byteData109/ns:byteDatans:byteData97/ns:byteDatans:byteData114/ns:byteDatans:byteData103/ns:byteDatans:byteData105/ns:byteDatans :byteData110/ns:byteDatans:byteData58/ns:byteData is not encoded in base64 !? Best Regards George -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3006) base64binary serialization
[ https://issues.apache.org/jira/browse/AXIS2-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe updated AXIS2-3006: - Priority: Blocker (was: Major) base64binary serialization -- Key: AXIS2-3006 URL: https://issues.apache.org/jira/browse/AXIS2-3006 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: databinding Affects Versions: 1.3 Environment: tested on Axis2 1.2 1.3 RC2 os: *nix , windows, tomcat : 5.5.23 java 1.6 Reporter: Georgi Yonchev Assignee: Deepal Jayasinghe Priority: Blocker Attachments: Res.java, services.wsdl, Test.java, Test_client.java using POJO's .. in Attachments : Res.java (the response object) Test.java (server) Test_client.java services.wsdl this happens when the response is some object with byte[] parameter inside it. this wsdl service.xml is generated automatically by the eclipse plug-in so, test2() always works, small/larger byte[] size in test() if you test with some string.getBytes() will work but larger ... no here is the soap payload : ns:byteData104/ns:byteDatans:byteData111/ns:byteDatans:byteData109/ns:byteDatans:byteData97/ns:byteDatans:byteData44/ns:byteDatans:byteData32/ns:byteDatans:byteData86/ns:byteDatans:byteData101/ns:byteDatans:byteData114/ns:byteDatans:byteData100/ns:byteDatans:byteData97/ns:byteDatans:byteData110/ns:byteDatans:byteData97/ns:byteDatans:byteData44/ns:byteDatans:byteData32/ns:byteDatans:byteData65/ns:byteDatans:byteData114/ns:byteDatans:byteData105/ns:byteDatans:byteData97/ns:byteDatans:byteData108/ns:byteDatans:byteData44/ns:byteDatans:byteData32/ns:byteDatans:byteData72/ns:byteDatans:byteData101/ns:byteDatans:byteData108/ns:byteDatans:byteData118/ns:byteDatans:byteData101/ns:byteDatans:byteData116/ns:byteDatans:byteData105/ns:byteDatans:byteData99/ns:byteDatans:byteData97/ns:byteDatans:byteData59/ns:byteDatans:byteData13/ns:byteDatans:b yteData10/ns:byteDatans:byteData9/ns:byteDatans:byteData102/ns:byteDatans:byteData111/ns:byteDatans:byteData110/ns:byteDatans:byteData116/ns:byteDatans:byteData45/ns:byteDatans:byteData115/ns:byteDatans:byteData105/ns:byteDatans:byteData122/ns:byteDatans:byteData101/ns:byteDatans:byteData58/ns:byteDatans:byteData32/ns:byteDatans:byteData49/ns:byteDatans:byteData48/ns:byteData ns:byteData112/ns:byteDatans:byteData116/ns:byteDatans:byteData59/ns:byteDatans:byteData13/ns:byteDatans:byteData10/ns:byteDatans:byteData9/ns:byteDatans:byteData102/ns:byteDatans:byteData111/ns:byteDatans:byteData110/ns:byteDatans:byteData116/ns:byteDatans:byteData45/ns:byteDatans:byteData119/ns:byteDatans:byteData101/ns:byteDatans:byteData105/ns:byteDatans:byteData103/ns:byteDatans:byteData104/ns:byteDatans:byteData116/ns:byteDatans:byteData58/ns:byteDatans:byteData32/ns:byteDatans:byteData110/ns:byteDatans:byteData111/ns:byteDatans:byteData114/ns:byteDatans:byteData109/ns:byteDatans:byteData97/ns:byteDatans:byteData108/ns:byteDatans:byteData59/ns:byteDatans:byteData13/ns:byteDatans:byteData10/ns:byteDatans:byteData125/ns:byteDatans:byteData13/ns:byteDatans:byteData10/ns:byteDatans:byteData46/ns:byteDatans:byteData99/ns:byteDatans:byteData111/ns:byteDatans:byteData110/n s:byteDatans:byteData 2000 116/ns:byteDatans:byteData101/ns:byteDatans:byteData110/ns:byteDatans:byteData116/ns:byteDatans:byteData49/ns:byteDatans:byteData123/ns:byteDatans:byteData13/ns:byteDatans:byteData10/ns:byteDatans:byteData9/ns:byteDatans:byteData109/ns:byteDatans:byteData97/ns:byteDatans:byteData114/ns:byteDatans:byteData103/ns:byteDatans:byteData105/ns:byteDatans :byteData110/ns:byteDatans:byteData58/ns:byteData is not encoded in base64 !? Best Regards George -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
