From axis-dev-return-17411-apmail-xml-axis-dev-archive=xml.apache.org@xml.apache.org Tue Dec 10 11:09:44 2002 Return-Path: Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org Received: (qmail 46681 invoked by uid 500); 10 Dec 2002 11:09:44 -0000 Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@xml.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@xml.apache.org Received: (qmail 46572 invoked from network); 10 Dec 2002 11:09:43 -0000 Importance: Normal Sensitivity: Subject: Re: [wsif] dependency of AXIS provider on xerces serializer To: axis-dev@xml.apache.org X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Anthony Elder" Date: Tue, 10 Dec 2002 11:09:22 +0000 X-MIMETrack: Serialize by Router on D06ML038/06/M/IBM(Release 5.0.9a |January 7, 2002) at 10/12/2002 11:09:24 MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I agree that we shouldn't really be doing this. I don't think this was recently introduced though, the JMSMessage class has been doing this for ages. Why don't you open a bugzilla so we have a record of it and we can talk about it at the next bugzilla review (oh, I'd like to have a bugzilla review on IRC soon). I'm not sure if we can fix this for this release though. ...ant Anthony Elder ant.elder@uk.ibm.com Web Services Development IBM UK Laboratories, Hursley Park (+44) 01962 818320, x248320, MP208. Aleksander Slominski on 07/12/2002 15:56:47 Please respond to axis-dev@xml.apache.org To: "axis-dev@xml.apache.org" cc: Subject: [wsif] dependency of AXIS provider on xerces serializer hi, it seems that it was just introduced and i do not think it is good idea - it takes away from users freedom to use any JAXP compliant parser when using SOAP ... i am really concerned that providers in WSIF are now getting more and more both inter dependent and dependent on lots of other libraries taking away one of the most attractive aspects of WSIF in my opinion: ability to mix and match providers based on user needs. i would like for example to make it easy to use just SOAP provider without anything but WSDL4J, JAXP parser (and there are fast and small SAX2 parsers) and AXIS jars ... here are errors i get: dynamic: [mkdir] Created dir: C:\Forge\xml-axis-wsif\java\build\classes [javac] Compiling 129 source files to C:\Forge\xml-axis-wsif\java\build\classes [javac] Note: sun.tools.javac.Main has been deprecated. [javac] C: \Forge\xml-axis-wsif\java\src\org\apache\wsif\providers\jms\JMSMessage.java:244: Class org.apache.xml.serialize.OutputFormat not found. [javac] org.apache.xml.serialize.OutputFormat format = [javac] ^ [javac] C: \Forge\xml-axis-wsif\java\src\org\apache\wsif\providers\jms\JMSMessage.java:245: Class org.apache.xml.serialize.OutputFormat not found. [javac] new org.apache.xml.serialize.OutputFormat (); [javac] ^ [javac] C: \Forge\xml-axis-wsif\java\src\org\apache\wsif\providers\jms\JMSMessage.java:246: Class org.apache.xml.serialize.XMLSerializer not found. [javac] org.apache.xml.serialize.XMLSerializer serializer = [javac] ^ [javac] C: \Forge\xml-axis-wsif\java\src\org\apache\wsif\providers\jms\JMSMessage.java:247: Class org.apache.xml.serialize.XMLSerializer not found. [javac] new org.apache.xml.serialize.XMLSerializer(writer, format); [javac] ^ [javac] C: \Forge\xml-axis-wsif\java\src\org\apache\wsif\providers\jms\JMSMessage.java:322: Excep tion org.xml.sax.SAXException is never thrown in the body of the corresponding try statement. [javac] } catch (org.xml.sax.SAXException e) { [javac] ^ [javac] C: \Forge\xml-axis-wsif\java\src\org\apache\wsif\providers\jms\JMSMessage.java:491: Class org.apache.xml.serialize.OutputFormat not found. [javac] org.apache.xml.serialize.OutputFormat format = [javac] ^ [javac] C: \Forge\xml-axis-wsif\java\src\org\apache\wsif\providers\jms\JMSMessage.java:492: Class org.apache.xml.serialize.OutputFormat not found. [javac] new org.apache.xml.serialize.OutputFormat(); [javac] ^ [javac] C: \Forge\xml-axis-wsif\java\src\org\apache\wsif\providers\jms\JMSMessage.java:493: Class org.apache.xml.serialize.TextSerializer not found. [javac] org.apache.xml.serialize.TextSerializer serializer = [javac] ^ [javac] C: \Forge\xml-axis-wsif\java\src\org\apache\wsif\providers\jms\JMSMessage.java:494: Class org.apache.xml.serialize.TextSerializer not found. [javac] new org.apache.xml.serialize.TextSerializer(); [javac] ^ [javac] Note: C: \Forge\xml-axis-wsif\java\src\org\apache\wsif\compiler\schema\tools\Conventions. java uses or overrides a deprecated API. Recompile with "-deprecation" for details. [javac] 9 errors, 2 warnings BUILD FAILED maybe in this case it would make sense to separate org.apache.xml.serialize.* and check it in as a separate set of source files or use JAR file from Xerces 2 is they allow building just serializer? thanks, alek -- The ancestor of every action is a thought. - Ralph Waldo Emerson