I see that the latest snapshot is out, is the change that I need:
XFIRE-964 Support for accessing MessageContext from within service implementation How do I get to the AbstractInvoker? Here is the sample code I am using... HelloServiceClient service = *new* HelloServiceClient(); HelloServiceSoap client = service.getHelloServiceSoap(); thanks On 4/25/07, Tomek Sztelak <[EMAIL PROTECTED]> wrote:
Hi Currently we are preparing for next XFire release ( 1.2.6 ), so to make sure bugs are really fixed i published today new XFire snapshot with 1.2-20070425.101013 version to snapshot repository ( http://snapshots.repository.codehaus.org ). If bug you reported or you are interested in is fixed,then plz test it and let us know in case of any problems (especially bugs related to problems with Holders and INOUT parameters). This will really help us to create better code. Also if you need any open bug to be fixed, create sample project or test case which reproduce reported bug and attach it to jira issue. Here is a list of bugs fixed for now: XFIRE-964 Support for accessing MessageContext from within service implementation XFIRE-959 NullPointerException when using custom SOAP header in oneway message XFIRE-956 Support for encrypted passwords in ws-sec configuration files XFIRE-951 Please move to jetty 6 Resolved Resolved XFIRE-942 Problem in services browsing XFIRE-936 A wsdl service with a "-" in the name is not converted to a valid java identifier using JAXWSProfile XFIRE-932 JAXWS schema generation sometimes generate two schemas with the same namespaces XFIRE-931 When auto-generating validation schemas, the schema builder may output several imports which are not resolved when the schema is parsed XFIRE-921 org.codehaus.xfire.test.XPathAssert.assertXPathEquals() does not support XFIRE-920 Http Proxy authentication not working XFIRE-915 NullPointerException with code generated from PayPal wsdl XFIRE-907 WSDL Generation Error - wsdlsoap:address location does not show correct XFIRE-814 Provide accessor to Jetty Server object from the XFireHTTPServer XFIRE-807 WebParam.mode.OUT Holder<clazz> parameters not set (null values) XFIRE-773 Bug with concurrent soap requests and aegis XFIRE-722 Parameter from header is not filled XFIRE-608 Change method name in mapping XFIRE-531 aegis NullPointerException occured when service being invoked XFIRE-480 aegis NullPointerException --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
