Re: [Resin-interest] pb with cxf / soap
I'm not sure how many jars/MB we are using with CXF as the same application is proof of concept for many other things and consumes 54 jars/55MB :). I chose CXF because we wanted to use some of it features that Axis did not have and I understood it was supposed to be Axis replacement, but that was a long time ago, so there is ample evidence that it has not happened ;). Fortunately for me, we haven't needed to use that in production yet, so with a bit more of luck, when we have to, things will be a little bit clearer (haha fat chance :) ). Good luck, D. El 21/07/2010 9:28, Mattias Jiderhamn escribió: I recently created a proof-of-concept service with CXF under Resin 4. Needed 12 jars/9,5 MB. Less than yours, but still a lot more than Axis 1.4. I'm hoping there was something I had misunderstood... For production we're sticking with Axis 1.4. Where we cannot use Hessian, that is ;-) /Mattias Riccardo Cohen wrote (2010-07-20 20:21): I still think that 29Mb/66jars is too much when you need only soap. Axis 2 is also very heavy, axis 1.4 is 2Mb only :) ... bad choice probably because too old. Daniel López wrote: Hi there, Not sure if it helps, but I have an application that exposes a SOAP interface using CXF 2.1.9 and I just tested it to work under Resin 3.1.5 and it fails under Resin 4.0.7 with a weird error. It's just a proof-of-concept application that I have, so I can't tell how well the combination really works, but at least I know those versions can work together. S! D. El 20/07/2010 8:29, Riccardo Cohen escribió: Thanks a lot Scott for your answer. This is the result: That looks like an error in the XML parser. You might try changing the javax.xml.stream.XMLInputFactory property to com.sun.xml.internal.stream.XMLInputFactoryImpl. When I add system-property javax.xml.stream.XMLInputFactory=com.sun.xml.internal.stream.XMLInputFactoryImpl/ in the conf of the webapp, the client seems to like it, and launches the request, but now the server has an err500 : javax.xml.stream.FactoryConfigurationError at javax.xml.stream.FactoryLoader.newClass(FactoryLoader.java:138) at javax.xml.stream.FactoryLoader.newInstance(FactoryLoader.java:76) at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:157) at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:143) at org.apache.cxf.staxutils.StaxUtils.createXMLInputFactory(StaxUtils.java:167) Also, you should avoid 3.2.x. Those are very old 4.0.x beta releases. I know but when I tried version 4.0.8 it claimed that it needs java 1.6 which is not available on my macosx leopard intel 32bits :) (I've just bought snow leopard and may move to 4 soon) Is there any other very simple way to do soap client/server with Resin ? (my customer needs soap, if not I would have used hessian...) ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] pb with cxf / soap
I found some people using org.codehaus.stax2.XMLInputFactory2 or com.sun.xml.stream.ZephyrParserFactory, and tried it, it gave the same error. As I don't see these libraries is in the libs, this suggests that FactoryConfigurationError could also mean class not found ? I tried to download jwsdp from sun site and copied all jars in lib, but it did not change. I'll try in resin v4 because it seems easyer... Thanks Scott Ferguson wrote: In this case, though, it just looks like we need to find the right classname for the XMLInputFactory, since it looks like the one I gave isn't right for the JDK. -- Scott Daniel López wrote: Hi there, Not sure if it helps, but I have an application that exposes a SOAP interface using CXF 2.1.9 and I just tested it to work under Resin 3.1.5 and it fails under Resin 4.0.7 with a weird error. It's just a proof-of-concept application that I have, so I can't tell how well the combination really works, but at least I know those versions can work together. S! D. El 20/07/2010 8:29, Riccardo Cohen escribió: Thanks a lot Scott for your answer. This is the result: That looks like an error in the XML parser. You might try changing the javax.xml.stream.XMLInputFactory property to com.sun.xml.internal.stream.XMLInputFactoryImpl. When I add system-property javax.xml.stream.XMLInputFactory=com.sun.xml.internal.stream.XMLInputFactoryImpl/ in the conf of the webapp, the client seems to like it, and launches the request, but now the server has an err500 : javax.xml.stream.FactoryConfigurationError at javax.xml.stream.FactoryLoader.newClass(FactoryLoader.java:138) at javax.xml.stream.FactoryLoader.newInstance(FactoryLoader.java:76) at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:157) at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:143) at org.apache.cxf.staxutils.StaxUtils.createXMLInputFactory(StaxUtils.java:167) Also, you should avoid 3.2.x. Those are very old 4.0.x beta releases. I know but when I tried version 4.0.8 it claimed that it needs java 1.6 which is not available on my macosx leopard intel 32bits :) (I've just bought snow leopard and may move to 4 soon) Is there any other very simple way to do soap client/server with Resin ? (my customer needs soap, if not I would have used hessian...) Thanks ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest -- Riccardo Cohen Architecte du Logiciel http://www.architectedulogiciel.fr +33 (0)6.09.83.64.49 Membre du réseau http://www.reflexe-conseil-centre.org ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] pb with cxf / soap
Thanks a lot Scott for your answer. This is the result: That looks like an error in the XML parser. You might try changing the javax.xml.stream.XMLInputFactory property to com.sun.xml.internal.stream.XMLInputFactoryImpl. When I add system-property javax.xml.stream.XMLInputFactory=com.sun.xml.internal.stream.XMLInputFactoryImpl/ in the conf of the webapp, the client seems to like it, and launches the request, but now the server has an err500 : javax.xml.stream.FactoryConfigurationError at javax.xml.stream.FactoryLoader.newClass(FactoryLoader.java:138) at javax.xml.stream.FactoryLoader.newInstance(FactoryLoader.java:76) at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:157) at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:143) at org.apache.cxf.staxutils.StaxUtils.createXMLInputFactory(StaxUtils.java:167) Also, you should avoid 3.2.x. Those are very old 4.0.x beta releases. I know but when I tried version 4.0.8 it claimed that it needs java 1.6 which is not available on my macosx leopard intel 32bits :) (I've just bought snow leopard and may move to 4 soon) Is there any other very simple way to do soap client/server with Resin ? (my customer needs soap, if not I would have used hessian...) Thanks -- Riccardo Cohen Architecte du Logiciel http://www.architectedulogiciel.fr +33 (0)6.09.83.64.49 Membre du réseau http://www.reflexe-conseil-centre.org ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] pb with cxf / soap
Hi there, Not sure if it helps, but I have an application that exposes a SOAP interface using CXF 2.1.9 and I just tested it to work under Resin 3.1.5 and it fails under Resin 4.0.7 with a weird error. It's just a proof-of-concept application that I have, so I can't tell how well the combination really works, but at least I know those versions can work together. S! D. El 20/07/2010 8:29, Riccardo Cohen escribió: Thanks a lot Scott for your answer. This is the result: That looks like an error in the XML parser. You might try changing the javax.xml.stream.XMLInputFactory property to com.sun.xml.internal.stream.XMLInputFactoryImpl. When I add system-property javax.xml.stream.XMLInputFactory=com.sun.xml.internal.stream.XMLInputFactoryImpl/ in the conf of the webapp, the client seems to like it, and launches the request, but now the server has an err500 : javax.xml.stream.FactoryConfigurationError at javax.xml.stream.FactoryLoader.newClass(FactoryLoader.java:138) at javax.xml.stream.FactoryLoader.newInstance(FactoryLoader.java:76) at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:157) at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:143) at org.apache.cxf.staxutils.StaxUtils.createXMLInputFactory(StaxUtils.java:167) Also, you should avoid 3.2.x. Those are very old 4.0.x beta releases. I know but when I tried version 4.0.8 it claimed that it needs java 1.6 which is not available on my macosx leopard intel 32bits :) (I've just bought snow leopard and may move to 4 soon) Is there any other very simple way to do soap client/server with Resin ? (my customer needs soap, if not I would have used hessian...) Thanks -- --- Daniel Lopez Janariz (d.lo...@uib.es) Web Services Centre for Information and Technology Balearic Islands University (SPAIN) --- ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] pb with cxf / soap
I still think that 29Mb/66jars is too much when you need only soap. Axis 2 is also very heavy, axis 1.4 is 2Mb only :) ... bad choice probably because too old. Daniel López wrote: Hi there, Not sure if it helps, but I have an application that exposes a SOAP interface using CXF 2.1.9 and I just tested it to work under Resin 3.1.5 and it fails under Resin 4.0.7 with a weird error. It's just a proof-of-concept application that I have, so I can't tell how well the combination really works, but at least I know those versions can work together. S! D. El 20/07/2010 8:29, Riccardo Cohen escribió: Thanks a lot Scott for your answer. This is the result: That looks like an error in the XML parser. You might try changing the javax.xml.stream.XMLInputFactory property to com.sun.xml.internal.stream.XMLInputFactoryImpl. When I add system-property javax.xml.stream.XMLInputFactory=com.sun.xml.internal.stream.XMLInputFactoryImpl/ in the conf of the webapp, the client seems to like it, and launches the request, but now the server has an err500 : javax.xml.stream.FactoryConfigurationError at javax.xml.stream.FactoryLoader.newClass(FactoryLoader.java:138) at javax.xml.stream.FactoryLoader.newInstance(FactoryLoader.java:76) at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:157) at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:143) at org.apache.cxf.staxutils.StaxUtils.createXMLInputFactory(StaxUtils.java:167) Also, you should avoid 3.2.x. Those are very old 4.0.x beta releases. I know but when I tried version 4.0.8 it claimed that it needs java 1.6 which is not available on my macosx leopard intel 32bits :) (I've just bought snow leopard and may move to 4 soon) Is there any other very simple way to do soap client/server with Resin ? (my customer needs soap, if not I would have used hessian...) Thanks -- Riccardo Cohen Architecte du Logiciel http://www.architectedulogiciel.fr +33 (0)6.09.83.64.49 Membre du réseau http://www.reflexe-conseil-centre.org ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] pb with cxf / soap
Riccardo Cohen wrote: I still think that 29Mb/66jars is too much when you need only soap. Axis 2 is also very heavy, axis 1.4 is 2Mb only :) ... bad choice probably because too old. In this case, though, it just looks like we need to find the right classname for the XMLInputFactory, since it looks like the one I gave isn't right for the JDK. -- Scott Daniel López wrote: Hi there, Not sure if it helps, but I have an application that exposes a SOAP interface using CXF 2.1.9 and I just tested it to work under Resin 3.1.5 and it fails under Resin 4.0.7 with a weird error. It's just a proof-of-concept application that I have, so I can't tell how well the combination really works, but at least I know those versions can work together. S! D. El 20/07/2010 8:29, Riccardo Cohen escribió: Thanks a lot Scott for your answer. This is the result: That looks like an error in the XML parser. You might try changing the javax.xml.stream.XMLInputFactory property to com.sun.xml.internal.stream.XMLInputFactoryImpl. When I add system-property javax.xml.stream.XMLInputFactory=com.sun.xml.internal.stream.XMLInputFactoryImpl/ in the conf of the webapp, the client seems to like it, and launches the request, but now the server has an err500 : javax.xml.stream.FactoryConfigurationError at javax.xml.stream.FactoryLoader.newClass(FactoryLoader.java:138) at javax.xml.stream.FactoryLoader.newInstance(FactoryLoader.java:76) at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:157) at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:143) at org.apache.cxf.staxutils.StaxUtils.createXMLInputFactory(StaxUtils.java:167) Also, you should avoid 3.2.x. Those are very old 4.0.x beta releases. I know but when I tried version 4.0.8 it claimed that it needs java 1.6 which is not available on my macosx leopard intel 32bits :) (I've just bought snow leopard and may move to 4 soon) Is there any other very simple way to do soap client/server with Resin ? (my customer needs soap, if not I would have used hessian...) Thanks ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] pb with cxf / soap
ok after 2 hours I found the resin-support.jar in the 3.1.9 package, why
did it disappear in 3.1.10 3.2 ?. I love resin but sometimes it is
really hard to find the good information...
I could create the web service and produce the wsdl from
http://localhost:8000/Adlinterface?wsdl . But when it comes to use the
client it fails :
java.lang.IllegalArgumentException: property
javax.xml.stream.supportDTD not supported
this is the config for the client :
remote-client interface=adlresintest.Adlinterface name=intf
uricxf:url=http://localhost:8000/Adlinterface/Adlsoap/uri
/remote-client
and this is the source class for the client :
public class Adlservice extends HttpServlet
{
private static final long serialVersionUID = -5896324971549186162L;
@In private Adlinterface intf;
//ADL
public void init() throws ServletException
{
getServletContext().setAttribute(adlservice,this);
}
//ADL
public void service(HttpServletRequest req, HttpServletResponse res)
{
req.setAttribute(answer,intf.testfunc(a string));
try{req.getRequestDispatcher(/index.jsp).forward(req,res);}catch
(Exception e){e.printStackTrace();}
}
}
I don't see my error, Can it be a compatibility problem between resin
3.2.1 and resin-support.jar found in 3.1.9 ?
thanks for any help
Riccardo Cohen wrote:
Hello
I try to setup my first soap web service with resin Pro 3.2.1 / macosx 10.5
I looked at the caucho.com doc and http://wiki.caucho.com/CXF
I copied the 66 items / 26Mb jars in WEB-INF/lib (waw huge...) and
configured the app like in the samples
I have the following error :
resin.local.xml:292: com.caucho.config.types.BeanConfig.setUri(): 'cxf'
is an unknown scheme for driver
'com.caucho.remote.server.ProtocolServletFactory'. The available
schemes are '[burlap, hessian]'
I found only this thread from Scott (oct 2008)
http://www.mail-archive.com/resin-interest@caucho.com/msg02846.html
But resin-support.jar is not in the resin distrib, my ext-webapp-lib is
empty.
Thanks for any help .
--
Riccardo Cohen
Architecte du Logiciel
http://www.architectedulogiciel.fr
+33 (0)6.09.83.64.49
Membre du réseau http://www.reflexe-conseil-centre.org
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
