Re: AW: [jira] Commented: (AXIS2-3300) minOccurs=0 always generated by Java2WSDL - problems with .NET client generation

2009-07-31 Thread WJ Krpelan
Hi folks, Right - by pure doctrine. However, the need to master xml-schema and wsdl doesnt make life so much easier for web service developers, does it? Cheers Wolfgang --- On Thu, 7/30/09, Ajith Ranabahu ajith.ranab...@gmail.com wrote: From: Ajith Ranabahu ajith.ranab...@gmail.com Subject:

[jira] Updated: (AXIS2-4456) Cannot process a POJO-based Web Service (i.e. uses RPCMessageReceiver). If any of its operations take Array of NON-OMelement parameters when requested with Wrapped-Array

2009-07-31 Thread Dobri Kitipov (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov updated AXIS2-4456: - Attachment: ArrayServiceSimple.aar Attaching ArrayServiceSimple.aar as a sample AAR that can

[jira] Created: (AXIS2-4456) Cannot process a POJO-based Web Service (i.e. uses RPCMessageReceiver). If any of its operations take Array of NON-OMelement parameters when requested with Wrapped-Array

2009-07-31 Thread Dobri Kitipov (JIRA)
Cannot process a POJO-based Web Service (i.e. uses RPCMessageReceiver). If any of its operations take Array of NON-OMelement parameters when requested with Wrapped-Array

[jira] Commented: (AXIS2-4456) Cannot process a POJO-based Web Service (i.e. uses RPCMessageReceiver). If any of its operations take Array of NON-OMelement parameters when requested with Wrapped-Array

2009-07-31 Thread Dobri Kitipov (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12737488#action_12737488 ] Dobri Kitipov commented on AXIS2-4456: -- Patches created are for the one-dimensional

Re: Please help me to debug RAMPART issue

2009-07-31 Thread Chinmoy Chakraborty
Hi, I noticed following property was not set while sending the message back: 179781 DEBUG [http8080-Processor24] org.apache.axis2.context.AbstractContext - Property set on object org.apache.axis2.context.messagecont...@12f0ce9 179781 DEBUG [http8080-Processor24]

[jira] Commented: (AXIS2-897) WSDL2Java should support --user and --password command-line arguments

2009-07-31 Thread sathish (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12737602#action_12737602 ] sathish commented on AXIS2-897: --- Any updates on this issuePls let me know if this is fixed

Re: Please help me to debug RAMPART issue

2009-07-31 Thread Andreas Veithen
Chinmoy, The Could not find a Builder error is because Tomcat returns an HTML error page and Axis2 on the client side doesn't know what to do with it. That is certainly not the root cause of the problem. Andreas On Fri, Jul 31, 2009 at 14:43, Chinmoy Chakrabortycch...@gmail.com wrote: Hi, I

Re: Please help me to debug RAMPART issue

2009-07-31 Thread Chinmoy Chakraborty
Andreas, Thanks a lot for your reply. You are right. Could not find a Builder is not root cause of the problem. I commented out following portion (OutFaultFlow params) in module.xml of rampart-1.4.mar and then it works as expected. OutFaultFlow handler name=PolicyBasedSecurityOutHandler

Re: Please help me to debug RAMPART issue

2009-07-31 Thread Nandana Mihindukulasooriya
Hi Chinmoy, If you comment out this part, the out going Fault messages will not be secured. Segment of the module.xml you have attached is the one which places Rampart handlers in the Out Fault Flow. It will not effect the normal flow. I didn't see any active development in parameter