Re: VOTE: Apache Rampart-1.1 release [Was : VOTE: Apache Ramaprt-1.1 release]

thanks for the correction ... I hope I can count other votes as votes to release "Rampart" :-) Thanks, Ruchith On 11/28/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote: Oops sorry I voted for Rampart, not for Ramaprt ;) Eran Chinthaka wrote: > +1 from me too. > > -- Chinthaka > > Anthony Elder wr

Re: [AXIS2] Proposal for saving the message context

Hi Ann, > > The save/restore of a MessageContext object hierarchy attempts to > reduce the duplication of parent-child objects in that MessageContext > object graph. The re-established MessageContext object graph keeps > the *Context objects to a single set and gets the Axis* objects > through t

[jira] Resolved: (AXIS2-1751) Allow Axis2 to know the IP address and host name of the remote client when using the SimpleHTTPServer

[ http://issues.apache.org/jira/browse/AXIS2-1751?page=all ] Davanum Srinivas resolved AXIS2-1751. - Resolution: Fixed Applied. thanks, dims > Allow Axis2 to know the IP address and host name of the remote client when > using the SimpleHTTPServer >

[jira] Created: (AXIS2-1795) Wrong HTTP response code when async call made under WAR version

Wrong HTTP response code when async call made under WAR version --- Key: AXIS2-1795 URL: http://issues.apache.org/jira/browse/AXIS2-1795 Project: Apache Axis 2.0 (Axis2) Issue Type:

[jira] Commented: (AXIS2-1795) Wrong HTTP response code when async call made under WAR version

[ http://issues.apache.org/jira/browse/AXIS2-1795?page=comments#action_12454661 ] Davanum Srinivas commented on AXIS2-1795: - Looks like Bill and David just committed a fix for this: http://svn.apache.org/viewvc?view=rev&revision=480660 ht

[jira] Resolved: (AXIS2-1795) Wrong HTTP response code when async call made under WAR version

[ http://issues.apache.org/jira/browse/AXIS2-1795?page=all ] Davanum Srinivas resolved AXIS2-1795. - Resolution: Fixed Paul, Please cross check if it works for you. (1.1 branch revision 480966) thanks, dims > Wrong HTTP response code when async cal

Re: [AXIS2] Proposal for saving the message context

Hi, Sanjiva, Thanks for the comments. I have tagged your comments with text to keep the indentation from getting too deep and put my responses below your comments with the tags text. Ann > > The save/restore of a MessageContext object hierarchy attempts to > reduce the duplication of parent-chi

[jira] Commented: (AXIS2-1769) Performance tuning for Axis2

[ http://issues.apache.org/jira/browse/AXIS2-1769?page=comments#action_12454727 ] Davanum Srinivas commented on AXIS2-1769: - Added a patch for woodstox in their JIRA: http://jira.codehaus.org/browse/WSTX-90 > Performance tuning for Axis2

[jira] Created: (AXIS2-1796) Add SOAP 1.2 support for JAXWS dynamic proxies

Add SOAP 1.2 support for JAXWS dynamic proxies -- Key: AXIS2-1796 URL: http://issues.apache.org/jira/browse/AXIS2-1796 Project: Apache Axis 2.0 (Axis2) Issue Type: Improvement Components:

[jira] Created: (AXIS2-1797) JAX-WS JAXBContext is missing the @WebMethod return class

JAX-WS JAXBContext is missing the @WebMethod return class - Key: AXIS2-1797 URL: http://issues.apache.org/jira/browse/AXIS2-1797 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug

[jira] Commented: (AXIS-2284) thread hangs on org.apache.axis.utils.JavaUtils.isEnumClass

[ http://issues.apache.org/jira/browse/AXIS-2284?page=comments#action_12454757 ] Fergus Ryder commented on AXIS-2284: WHat version of the code was the fix applied to? > thread hangs on org.apache.axis.utils.JavaUtils.isEnumClass > --

[jira] Updated: (AXIS2-1797) JAX-WS JAXBContext is missing the @WebMethod return class

[ http://issues.apache.org/jira/browse/AXIS2-1797?page=all ] Rich Scheuerle updated AXIS2-1797: -- Attachment: patch.txt > JAX-WS JAXBContext is missing the @WebMethod return class > - > >

[jira] Resolved: (AXIS2-1797) JAX-WS JAXBContext is missing the @WebMethod return class

[ http://issues.apache.org/jira/browse/AXIS2-1797?page=all ] Rich Scheuerle resolved AXIS2-1797. --- Resolution: Fixed Resolved in revision 481085 > JAX-WS JAXBContext is missing the @WebMethod return class > -

[jira] Created: (AXIS2-1798) messageContext.setDoingMTOM doesn't work

messageContext.setDoingMTOM doesn't work Key: AXIS2-1798 URL: http://issues.apache.org/jira/browse/AXIS2-1798 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Reporter: Rajith Attapattu

Extra "valid" element appearing in WSDL

I am seeking information as to what is cuasing an additional 'valid' element to appear in the schema section of my WSDL - it is the one generated automatically by axis by clicking on the (WSDL) link of the deployed web service. The LogOffRequest is a custom class with it's own class file, (gener

[jira] Created: (AXIS2-1799) JAX-WS Add support for legacy Exceptions

JAX-WS Add support for legacy Exceptions Key: AXIS2-1799 URL: http://issues.apache.org/jira/browse/AXIS2-1799 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Reporter: Rich Scheuerle

[jira] Created: (AXIS2-1800) JAX-WS Cache or improve the @XMLRootElement and related annotation lookups

JAX-WS Cache or improve the @XMLRootElement and related annotation lookups -- Key: AXIS2-1800 URL: http://issues.apache.org/jira/browse/AXIS2-1800 Project: Apache Axis 2.0 (Axis2)

Re: [AXIS2] Proposal for saving the message context

Hi Ann, On 11/30/06, Ann Robinson <[EMAIL PROTECTED]> wrote: Hi, Sanjiva, Thanks for the comments. I have tagged your comments with text to keep the indentation from getting too deep and put my responses below your comments with the tags text. Ann > > The save/restore of a MessageContext o

[jira] Created: (AXIS2-1801) setOperationContext not being invoked

setOperationContext not being invoked - Key: AXIS2-1801 URL: http://issues.apache.org/jira/browse/AXIS2-1801 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Affects Versio

[jira] Created: (AXIS2-1802) Polymorphic Schema Support by WSDL Schema Parsin.

Polymorphic Schema Support by WSDL Schema Parsin. - Key: AXIS2-1802 URL: http://issues.apache.org/jira/browse/AXIS2-1802 Project: Apache Axis 2.0 (Axis2) Issue Type: New Feature Compo

[jira] Updated: (AXIS2-1802) Polymorphic Schema Support by WSDL Schema Parsin.

[ http://issues.apache.org/jira/browse/AXIS2-1802?page=all ] Nikhil Thaker updated AXIS2-1802: - Attachment: JiRA_1802_SchemaParsing.txt > Polymorphic Schema Support by WSDL Schema Parsin. > - > >

[jira] Assigned: (AXIS2-1802) Polymorphic Schema Support by WSDL Schema Parsin.

[ http://issues.apache.org/jira/browse/AXIS2-1802?page=all ] Nikhil Thaker reassigned AXIS2-1802: Assignee: Nikhil Thaker > Polymorphic Schema Support by WSDL Schema Parsin. > - > > Key:

[axis2] Question regarding MTOM

Hi Folks, If I do enableMTOM = true in the axis2.xml, does it mean that all attachments I do gets optimized with MTOM/XOP even if I do the following ? OMText binaryNode = factory.createOMText(base64Text, mimeType, false); Note the false paramter. What is the correct behaviour ?? What I see is

Re: [axis2] Question regarding MTOM

Hi Rajith, Expected behaviour is that all the optimizable OMText's needs to be serialized as XOP+attachments when MTOM is enabled. OMText binaryNode = factory.createOMText( base64Text, mimeType, false); Note the false paramter. This will go in line as base64.. But you'll still get the MIME enve