dev  

Messages by Thread

• [xfire-dev] [jira] Created: (XFIRE-759) This WSDL fails the Xfire WsGenTask James Lorenzen (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-759) This WSDL fails the Xfire WsGenTask Tomasz Sztelak (JIRA)
  • [xfire-dev] [jira] Updated: (XFIRE-759) This WSDL fails the Xfire WsGenTask Dan Diephouse (JIRA)
  • [xfire-dev] [jira] Closed: (XFIRE-759) This WSDL fails the Xfire WsGenTask Dan Diephouse (JIRA)
• [xfire-dev] [jira] Commented: (XFIRE-703) UnsupportedOperationException Jan Saner (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-703) UnsupportedOperationException Bob Bueckers (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-703) UnsupportedOperationException Dan Diephouse (JIRA)
• [xfire-dev] [jira] Closed: (XFIRE-593) Problems connecting with Spring to a non-XFire Web Service Tomasz Sztelak (JIRA)
• [xfire-dev] [jira] Updated: (XFIRE-568) JAXB 2.0 with Annotations generates invalid schema imports Dan Diephouse (JIRA)
• [xfire-dev] [jira] Commented: (XFIRE-568) JAXB 2.0 with Annotations generates invalid schema imports Pradeep Bhat (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-568) JAXB 2.0 with Annotations generates invalid schema imports Pradeep Bhat (JIRA)
• Re: [xfire-dev] schemaLocation imports of auto generated xsd files pradeep
  • Re: [xfire-dev] schemaLocation imports of auto generated xsd files pradeep
  • Re: [xfire-dev] schemaLocation imports of auto generated xsd files butterdave
• [xfire-dev] [jira] Created: (XFIRE-758) NPE when generating stubs from WSDL Neeme Praks (JIRA)
  • [xfire-dev] [jira] Updated: (XFIRE-758) NPE when generating stubs from WSDL Neeme Praks (JIRA)
  • [xfire-dev] [jira] Updated: (XFIRE-758) NPE when generating stubs from WSDL Neeme Praks (JIRA)
  • [xfire-dev] [jira] Updated: (XFIRE-758) NPE when generating stubs from WSDL Neeme Praks (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-758) NPE when generating stubs from WSDL Neeme Praks (JIRA)
  • [xfire-dev] [jira] Assigned: (XFIRE-758) NPE when generating stubs from WSDL Tomasz Sztelak (JIRA)
  • [xfire-dev] [jira] Closed: (XFIRE-758) NPE when generating stubs from WSDL Dan Diephouse (JIRA)
• [xfire-dev] [jira] Created: (XFIRE-757) Invoking a Axis WebService from Xfire Client fails Mukesh Mediratta (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-757) Invoking a Axis WebService from Xfire Client fails Tomasz Sztelak (JIRA)
• [xfire-dev] [jira] Created: (XFIRE-756) XFireFactory singleton code not correct Matthew (JIRA)
  • [xfire-dev] [jira] Assigned: (XFIRE-756) XFireFactory singleton code not correct Tomasz Sztelak (JIRA)
• [xfire-dev] [jira] Commented: (XFIRE-702) jaxws xsd namespace declaration is not created on root elements of dispatched soap body content when ns prefix xsd is use INSIDE attribute value, eg xsi:type="xsd:int" chris thatcher (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-702) jaxws xsd namespace declaration is not created on root elements of dispatched soap body content when ns prefix xsd is use INSIDE attribute value, eg xsi:type="xsd:int" chris thatcher (JIRA)
• [xfire-dev] [jira] Created: (XFIRE-755) Support for headers that are handled by Handlers in wsdl binding. Hila Noga (JIRA)
  • [xfire-dev] [jira] Assigned: (XFIRE-755) Support for headers that are handled by Handlers in wsdl binding. Tomasz Sztelak (JIRA)
• [xfire-dev] [jira] Commented: (XFIRE-705) NullPointerException when accessing an interface method and the property was not set in the WSDL. Dan Diephouse (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-705) NullPointerException when accessing an interface method and the property was not set in the WSDL. Pascal Lalonde (JIRA)
• [xfire-dev] [jira] Closed: (XFIRE-653) Allow empty elements for schema types: int long double float Dan Diephouse (JIRA)
• [xfire-dev] [jira] Closed: (XFIRE-704) inheritance namespace problem with xfire 1.2 or 1.2.2 Dan Diephouse (JIRA)
• [xfire-dev] [jira] Closed: (XFIRE-175) If services.xml doesn't exist, the world should move on Dan Diephouse (JIRA)
• [xfire-dev] [jira] Updated: (XFIRE-631) Exception caused by NamespaceHelper class when no targetNamespace is defined. Dan Diephouse (JIRA)
  • [xfire-dev] [jira] Updated: (XFIRE-631) Exception caused by NamespaceHelper class when no targetNamespace is defined. Dan Diephouse (JIRA)
  • [xfire-dev] [jira] Updated: (XFIRE-631) Exception caused by NamespaceHelper class when no targetNamespace is defined. Dan Diephouse (JIRA)
  • [xfire-dev] [jira] Updated: (XFIRE-631) Exception caused by NamespaceHelper class when no targetNamespace is defined. Dan Diephouse (JIRA)
• [xfire-dev] [jira] Updated: (XFIRE-609) Missing targetNamespace in source schema causes NullPointerException in XmlBeansWSDLBuilder Dan Diephouse (JIRA)
  • [xfire-dev] [jira] Updated: (XFIRE-609) Missing targetNamespace in source schema causes NullPointerException in XmlBeansWSDLBuilder Chris Mathrusse (JIRA)
  • [xfire-dev] [jira] Updated: (XFIRE-609) Missing targetNamespace in source schema causes NullPointerException in XmlBeansWSDLBuilder Dan Diephouse (JIRA)
  • [xfire-dev] [jira] Updated: (XFIRE-609) Missing targetNamespace in source schema causes NullPointerException in XmlBeansWSDLBuilder Dan Diephouse (JIRA)
  • [xfire-dev] [jira] Updated: (XFIRE-609) Missing targetNamespace in source schema causes NullPointerException in XmlBeansWSDLBuilder Dan Diephouse (JIRA)
• [xfire-dev] [jira] Updated: (XFIRE-712) XFireClientFactoryBean should cast java.net.ConnectExcept to XFireRuntimeException Dan Diephouse (JIRA)
  • [xfire-dev] [jira] Updated: (XFIRE-712) XFireClientFactoryBean should cast java.net.ConnectExcept to XFireRuntimeException Dan Diephouse (JIRA)
  • [xfire-dev] [jira] Updated: (XFIRE-712) XFireClientFactoryBean should cast java.net.ConnectExcept to XFireRuntimeException Dan Diephouse (JIRA)
  • [xfire-dev] [jira] Updated: (XFIRE-712) XFireClientFactoryBean should cast java.net.ConnectExcept to XFireRuntimeException Dan Diephouse (JIRA)
• [xfire-dev] [jira] Updated: (XFIRE-691) Invalid XML elements are ignored but should throw error Dan Diephouse (JIRA)
  • [xfire-dev] [jira] Updated: (XFIRE-691) Invalid XML elements are ignored but should throw error Dan Diephouse (JIRA)
  • [xfire-dev] [jira] Updated: (XFIRE-691) Invalid XML elements are ignored but should throw error Dan Diephouse (JIRA)
  • [xfire-dev] [jira] Updated: (XFIRE-691) Invalid XML elements are ignored but should throw error Dan Diephouse (JIRA)
• [xfire-dev] [jira] Updated: (XFIRE-589) Change Aegis to serialize properties in the order defined in the mappig file. Dan Diephouse (JIRA)
  • [xfire-dev] [jira] Updated: (XFIRE-589) Change Aegis to serialize properties in the order defined in the mappig file. Dan Diephouse (JIRA)
  • [xfire-dev] [jira] Updated: (XFIRE-589) Change Aegis to serialize properties in the order defined in the mappig file. Dan Diephouse (JIRA)
  • [xfire-dev] [jira] Updated: (XFIRE-589) Change Aegis to serialize properties in the order defined in the mappig file. Dan Diephouse (JIRA)
• [xfire-dev] [jira] Updated: (XFIRE-608) Change method name in mapping Dan Diephouse (JIRA)
  • [xfire-dev] [jira] Updated: (XFIRE-608) Change method name in mapping Dan Diephouse (JIRA)
• [xfire-dev] [jira] Updated: (XFIRE-702) jaxws xsd namespace declaration is not created on root elements of dispatched soap body content when ns prefix xsd is use INSIDE attribute value, eg xsi:type="xsd:int" Dan Diephouse (JIRA)
• [xfire-dev] [jira] Closed: (XFIRE-351) Exception when enabling DomInHandler Dan Diephouse (JIRA)
• [xfire-dev] [jira] Reopened: (XFIRE-351) Exception when enabling DomInHandler Dan Diephouse (JIRA)
• [xfire-dev] [jira] Updated: (XFIRE-351) Exception when enabling DomInHandler Dan Diephouse (JIRA)
• [xfire-dev] [jira] Created: (XFIRE-754) Not converting header element into function argument Matthew (JIRA)
  • [xfire-dev] [jira] Assigned: (XFIRE-754) Not converting header element into function argument Tomasz Sztelak (JIRA)
  • [xfire-dev] [jira] Resolved: (XFIRE-754) Not converting header element into function argument Tomasz Sztelak (JIRA)
  • [xfire-dev] [jira] Resolved: (XFIRE-754) Not converting header element into function argument Tomasz Sztelak (JIRA)
• [xfire-dev] [jira] Created: (XFIRE-753) "java.lang.IllegalArgumentException: argument type mismatch" when an invalid xsi:type is specified in soap request. Karthikeyan M. (JIRA)
  • [xfire-dev] [jira] Updated: (XFIRE-753) "java.lang.IllegalArgumentException: argument type mismatch" when an invalid xsi:type is specified in soap request. Dan Diephouse (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-753) "java.lang.IllegalArgumentException: argument type mismatch" when an invalid xsi:type is specified in soap request. Karthikeyan M. (JIRA)
  • [xfire-dev] [jira] Closed: (XFIRE-753) "java.lang.IllegalArgumentException: argument type mismatch" when an invalid xsi:type is specified in soap request. Dan Diephouse (JIRA)
• [xfire-dev] [jira] Created: (XFIRE-752) WSS4JInHandler.checkReceiverResults(Vector, Vector), requires that Vector params are in the same order Nick West (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-752) WSS4JInHandler.checkReceiverResults(Vector, Vector), requires that Vector params are in the same order Nick West (JIRA)
  • [xfire-dev] [jira] Assigned: (XFIRE-752) WSS4JInHandler.checkReceiverResults(Vector, Vector), requires that Vector params are in the same order Tomasz Sztelak (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-752) WSS4JInHandler.checkReceiverResults(Vector, Vector), requires that Vector params are in the same order Tomasz Sztelak (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-752) WSS4JInHandler.checkReceiverResults(Vector, Vector), requires that Vector params are in the same order Rodrigo Urubatan (JIRA)
  • [xfire-dev] [jira] Updated: (XFIRE-752) WSS4JInHandler.checkReceiverResults(Vector, Vector), requires that Vector params are in the same order Rodrigo Urubatan (JIRA)
  • [xfire-dev] [jira] Closed: (XFIRE-752) WSS4JInHandler.checkReceiverResults(Vector, Vector), requires that Vector params are in the same order Tomasz Sztelak (JIRA)
• [xfire-dev] [jira] Commented: (XFIRE-706) SoapSerializerHandler doesn't consult the binding to set the serializer on the OutMessage Dan Diephouse (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-706) SoapSerializerHandler doesn't consult the binding to set the serializer on the OutMessage Ryan Heaton (JIRA)
• [xfire-dev] [jira] Created: (XFIRE-751) It is not possible to serialize an org.w3c.dom.Element object on a web service deployed by XFire Enrico Consiglio (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-751) It is not possible to serialize an org.w3c.dom.Element object on a web service deployed by XFire Tomasz Sztelak (JIRA)
  • [xfire-dev] [jira] Assigned: (XFIRE-751) It is not possible to serialize an org.w3c.dom.Element object on a web service deployed by XFire Tomasz Sztelak (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-751) It is not possible to serialize an org.w3c.dom.Element object on a web service deployed by XFire Tomasz Sztelak (JIRA)
  • [xfire-dev] [jira] Closed: (XFIRE-751) It is not possible to serialize an org.w3c.dom.Element object on a web service deployed by XFire Tomasz Sztelak (JIRA)
• [xfire-dev] [jira] Commented: (XFIRE-546) @WebMethod ignored - all methods is visible from webservice Cliff Meyers (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-546) @WebMethod ignored - all methods is visible from webservice Jara Cesnek (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-546) @WebMethod ignored - all methods is visible from webservice Cliff Meyers (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-546) @WebMethod ignored - all methods is visible from webservice tahura chaudhry (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-546) @WebMethod ignored - all methods is visible from webservice tahura chaudhry (JIRA)
  • [xfire-dev] Distributed Transactions with XFire suzo
• [xfire-dev] [jira] Created: (XFIRE-750) XFire Context behaves differently than Spring Context - MethodInvokingFactoryBean throws a NoSuchMethodException Franz Garsombke (JIRA)
  • [xfire-dev] [jira] Assigned: (XFIRE-750) XFire Context behaves differently than Spring Context - MethodInvokingFactoryBean throws a NoSuchMethodException Tomasz Sztelak (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-750) XFire Context behaves differently than Spring Context - MethodInvokingFactoryBean throws a NoSuchMethodException Tomasz Sztelak (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-750) XFire Context behaves differently than Spring Context - MethodInvokingFactoryBean throws a NoSuchMethodException Franz Garsombke (JIRA)
• RE: [xfire-dev] [jira] Commented: (XFIRE-715) generated wsdl schema does not include the definitions of all types Chris Thatcher
• [xfire-dev] [jira] Created: (XFIRE-749) Code Generation Error Ramesh Narayanan (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-749) Code Generation Error Tomasz Sztelak (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-749) Code Generation Error Ramesh Narayanan (JIRA)
  • [xfire-dev] [jira] Assigned: (XFIRE-749) Code Generation Error Tomasz Sztelak (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-749) Code Generation Error Tomasz Sztelak (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-749) Code Generation Error Margarita (JIRA)
  • [xfire-dev] [jira] Closed: (XFIRE-749) Code Generation Error Tomasz Sztelak (JIRA)
• [xfire-dev] [jira] Commented: (XFIRE-491) Xifre giving an exception during wsdl generation for 5.0 type like List<long[]> Ram (JIRA)
• [xfire-dev] [jira] Created: (XFIRE-748) Generation problem with mixed operation patterns in same WSDL JIRA
  • [xfire-dev] [jira] Commented: (XFIRE-748) Generation problem with mixed operation patterns in same WSDL JIRA
  • [xfire-dev] [jira] Commented: (XFIRE-748) Generation problem with mixed operation patterns in same WSDL Tom Lambrechts (JIRA)
  • [xfire-dev] [jira] Updated: (XFIRE-748) Generation problem with mixed operation patterns in same WSDL Tom Lambrechts (JIRA)
  • [xfire-dev] [jira] Updated: (XFIRE-748) Generation problem with mixed operation patterns in same WSDL Dan Diephouse (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-748) Generation problem with mixed operation patterns in same WSDL Tom Lambrechts (JIRA)
  • [xfire-dev] [jira] Closed: (XFIRE-748) Generation problem with mixed operation patterns in same WSDL Dan Diephouse (JIRA)
  • [xfire-dev] [jira] Closed: (XFIRE-748) Generation problem with mixed operation patterns in same WSDL Dan Diephouse (JIRA)
• [xfire-dev] [jira] Created: (XFIRE-747) Out handlers called twice PJ (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-747) Out handlers called twice Tomasz Sztelak (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-747) Out handlers called twice PJ (JIRA)
  • [xfire-dev] [jira] Closed: (XFIRE-747) Out handlers called twice Tomasz Sztelak (JIRA)
• [xfire-dev] [jira] Created: (XFIRE-746) allow wsgen to work with wsdl from https James Burton (JIRA)
  • [xfire-dev] [jira] Assigned: (XFIRE-746) allow wsgen to work with wsdl from https Tomasz Sztelak (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-746) allow wsgen to work with wsdl from https Tomasz Sztelak (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-746) allow wsgen to work with wsdl from https James Burton (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-746) allow wsgen to work with wsdl from https Tomasz Sztelak (JIRA)
  • [xfire-dev] [jira] Resolved: (XFIRE-746) allow wsgen to work with wsdl from https Tomasz Sztelak (JIRA)
  • [xfire-dev] [jira] Updated: (XFIRE-746) allow wsgen to work with wsdl from https Tomasz Sztelak (JIRA)
• [xfire-dev] [jira] Created: (XFIRE-745) Introduce a clean-up phase after SEND Greg Kohring (JIRA)
  • [xfire-dev] [jira] Closed: (XFIRE-745) Introduce a clean-up phase after SEND Tomasz Sztelak (JIRA)
  • [xfire-dev] [jira] Closed: (XFIRE-745) Introduce a clean-up phase after SEND Tomasz Sztelak (JIRA)
• [xfire-dev] [jira] Closed: (XFIRE-688) HashMap access in CustomTypeMapping causes Thread-lock issues under high load Dan Diephouse (JIRA)
• [xfire-dev] [jira] Commented: (XFIRE-688) HashMap access in CustomTypeMapping causes Thread-lock issues under high load Dan Diephouse (JIRA)
• [xfire-dev] [jira] Created: (XFIRE-744) Adding handlers via annotations Tomasz Sztelak (JIRA)
  • [xfire-dev] [jira] Resolved: (XFIRE-744) Adding handlers via annotations Tomasz Sztelak (JIRA)
• [xfire-dev] [jira] Created: (XFIRE-743) HttpClient only does 2 connections by default Dan Diephouse (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-743) HttpClient only does 2 connections by default Andres Bernasconi (JIRA)
  • [xfire-dev] [jira] Assigned: (XFIRE-743) HttpClient only does 2 connections by default Tomasz Sztelak (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-743) HttpClient only does 2 connections by default Tomasz Sztelak (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-743) HttpClient only does 2 connections by default JIRA
  • [xfire-dev] [jira] Resolved: (XFIRE-743) HttpClient only does 2 connections by default Tomasz Sztelak (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-743) HttpClient only does 2 connections by default Andres Bernasconi (JIRA)
• [xfire-dev] [jira] Created: (XFIRE-742) WsGenTask creates Service Impl with void output parameters and no input parameters. JAXB is the binding mechanism. Franz Garsombke (JIRA)
  • [xfire-dev] [jira] Updated: (XFIRE-742) WsGenTask creates Service Impl with void output parameters and no input parameters. JAXB is the binding mechanism. Dan Diephouse (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-742) WsGenTask creates Service Impl with void output parameters and no input parameters. JAXB is the binding mechanism. Franz Garsombke (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-742) WsGenTask creates Service Impl with void output parameters and no input parameters. JAXB is the binding mechanism. Dan Diephouse (JIRA)
  • [xfire-dev] [jira] Closed: (XFIRE-742) WsGenTask creates Service Impl with void output parameters and no input parameters. JAXB is the binding mechanism. Dan Diephouse (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-742) WsGenTask creates Service Impl with void output parameters and no input parameters. JAXB is the binding mechanism. Franz Garsombke (JIRA)
• [xfire-dev] [jira] Created: (XFIRE-741) deploy to weblogic813 problem wangyi (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-741) deploy to weblogic813 problem Tomasz Sztelak (JIRA)
  • [xfire-dev] [jira] Updated: (XFIRE-741) deploy to weblogic813 problem wangyi (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-741) deploy to weblogic813 problem wangyi (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-741) deploy to weblogic813 problem Tomasz Sztelak (JIRA)
  • [xfire-dev] [jira] Assigned: (XFIRE-741) deploy to weblogic813 problem Tomasz Sztelak (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-741) deploy to weblogic813 problem wangyi (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-741) deploy to weblogic813 problem Tomasz Sztelak (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-741) deploy to weblogic813 problem wangyi (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-741) deploy to weblogic813 problem wangyi (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-741) deploy to weblogic813 problem wangyi (JIRA)
  • [xfire-dev] [jira] Closed: (XFIRE-741) deploy to weblogic813 problem Tomasz Sztelak (JIRA)
• [xfire-dev] [jira] Resolved: (XFIRE-648) Bundle source and javadocs as m2 artifacts Tomasz Sztelak (JIRA)
• [xfire-dev] How to see the complete Handler Chain in any particular invocation Sarkar, Abanindra
  • Re: [xfire-dev] How to see the complete Handler Chain in any particular invocation Tomek Sztelak
  • [xfire-dev] Bug!!! Christian Jensen
  • Re: [xfire-dev] Bug!!! Tomek Sztelak
• [xfire-dev] [jira] Created: (XFIRE-740) client generation from wsdl: support java 1.4 JIRA
  • Re: [xfire-dev] [jira] Created: (XFIRE-740) client generation from wsdl: support java 1.4 Skyloper Dan
• [xfire-dev] [jira] Created: (XFIRE-739) wsdl: doesn't describe pojos in xsd charllie hardt (JIRA)
  • [xfire-dev] [jira] Updated: (XFIRE-739) wsdl: doesn't describe pojos in xsd Dan Diephouse (JIRA)
  • [xfire-dev] [jira] Updated: (XFIRE-739) wsdl: doesn't describe pojos in xsd Tom Lambrechts (JIRA)
  • [xfire-dev] [jira] Updated: (XFIRE-739) wsdl: doesn't describe pojos in xsd Tom Lambrechts (JIRA)
  • [xfire-dev] [jira] Updated: (XFIRE-739) wsdl: doesn't describe pojos in xsd Dan Diephouse (JIRA)
  • [xfire-dev] [jira] Updated: (XFIRE-739) wsdl: doesn't describe pojos in xsd Dan Diephouse (JIRA)
• [xfire-dev] [jira] Closed: (XFIRE-602) content-length response header is not set Tomasz Sztelak (JIRA)
• [xfire-dev] [jira] Closed: (XFIRE-638) CLONE -JDK 1,3 compatible Tomasz Sztelak (JIRA)
• [xfire-dev] [jira] Resolved: (XFIRE-699) XFire 1.2.2 and Spring 2.0 seem to be incompatible Tomasz Sztelak (JIRA)
• [xfire-dev] [jira] Assigned: (XFIRE-696) Using Spring 2.0 causes initialization failures Tomasz Sztelak (JIRA)
• [xfire-dev] [jira] Created: (XFIRE-738) xFire cannot handle namespaces including the word "public" Phil Hewitt (JIRA)
• [xfire-dev] [jira] Created: (XFIRE-736) It's not possible to compile client-side artifacts with Axis 1.4 on a web service deployed with XFire 1.2.2: compiling the AnyType2AnyTypeMapEntry.java (when a type oh HashMap ) Enrico Consiglio (JIRA)
• [xfire-dev] [jira] Assigned: (XFIRE-699) XFire 1.2.2 and Spring 2.0 seem to be incompatible Tomasz Sztelak (JIRA)
• [xfire-dev] [jira] Created: (XFIRE-737) It's not possible to compile client-side artifacts with Axis 1.4 over a web service deployed with XFire 1.2.2. Enrico Consiglio (JIRA)
  • [xfire-dev] [jira] Updated: (XFIRE-737) It's not possible to compile client-side artifacts with Axis 1.4 over a web service deployed with XFire 1.2.2. Enrico Consiglio (JIRA)
• [xfire-dev] Spring 2.0 Progress [email protected]
  • Re: [xfire-dev] Spring 2.0 Progress Guillaume Nodet
  • Re: [xfire-dev] Spring 2.0 Progress Tomek Sztelak
  • Re: [xfire-dev] Spring 2.0 Progress [email protected]
  • Re: [xfire-dev] Spring 2.0 Progress Tomek Sztelak
• [xfire-dev] [jira] Updated: (XFIRE-703) UnsupportedOperationException Dan Diephouse (JIRA)
• [xfire-dev] [jira] Assigned: (XFIRE-713) JDOMStreamWriter needs a method to retrieve the Document created. Tomasz Sztelak (JIRA)
• [xfire-dev] [jira] Commented: (XFIRE-608) Change method name in mapping Dan Diephouse (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-608) Change method name in mapping Paul Austin (JIRA)
• [xfire-dev] [jira] Closed: (XFIRE-635) Parse exception on empty elements of type java.lang.Integer Dan Diephouse (JIRA)
• [xfire-dev] [jira] Commented: (XFIRE-712) XFireClientFactoryBean should cast java.net.ConnectExcept to XFireRuntimeException Dan Diephouse (JIRA)
• [xfire-dev] [jira] Resolved: (XFIRE-713) JDOMStreamWriter needs a method to retrieve the Document created. Tomasz Sztelak (JIRA)
• [xfire-dev] [jira] Updated: (XFIRE-175) If services.xml doesn't exist, the world should move on Dan Diephouse (JIRA)
• [xfire-dev] [jira] Reopened: (XFIRE-175) If services.xml doesn't exist, the world should move on Dan Diephouse (JIRA)
• [xfire-dev] .NET Interop with Base64 Christian Jensen
• [xfire-dev] change default "in" and "out" parameters into proper names Elaine Strand
  • Re: [xfire-dev] change default "in" and "out" parameters into proper names Tomek Sztelak
• [xfire-dev] [jira] Created: (XFIRE-735) XFireRuntimeException - XFireFault: Index: 0, Size: 0 when dealing with HL7v3 schemas Constantin Ilea (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-735) XFireRuntimeException - XFireFault: Index: 0, Size: 0 when dealing with HL7v3 schemas Dan Diephouse (JIRA)
  • [xfire-dev] [jira] Closed: (XFIRE-735) XFireRuntimeException - XFireFault: Index: 0, Size: 0 when dealing with HL7v3 schemas Tomasz Sztelak (JIRA)
• [xfire-dev] [jira] Created: (XFIRE-734) sample application wsgen-jaxws-spring-1.2.2 fails to deploy ran zilber (JIRA)
  • [xfire-dev] [jira] Closed: (XFIRE-734) sample application wsgen-jaxws-spring-1.2.2 fails to deploy Dan Diephouse (JIRA)
  • [xfire-dev] [jira] Commented: (XFIRE-734) sample application wsgen-jaxws-spring-1.2.2 fails to deploy ran zilber (JIRA)
• [xfire-dev] [jira] Created: (XFIRE-733) sample application jsr181-example-1.2.2 fails to run ran zilber (JIRA)
  • [xfire-dev] [jira] Closed: (XFIRE-733) sample application jsr181-example-1.2.2 fails to run Dan Diephouse (JIRA)

• Earlier messages
• Later messages