October 2007 - jbossws-users - Jboss List Archives

by abdujaparov

Hi, I've modified my war file in this way: In META-INF directory there is the file: jboss-aop.xml, this file is only in this place; In WEB-INF: directory WEB-INF: -file web.xml; +directory classes: +directory xml: -XMLJDomWriterStat.class -XMLSaxReaderStat.class +directory services: -ServiceAOP.class; -ServiceAOPAspect.class; -ServiceAOP$fattoriale_9086071828619756113.class (this class was generated by jboss aop ide with eclipse automatically). When I try to invoke a method of the web service, also a method whitout a binding with the aspect I receive this error: | Exception in thread "main" AxisFault | faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException | faultSubcode: | faultString: org.xml.sax.SAXParseException: Premature end of file. | faultActor: | faultNode: | faultDetail: | {http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXParseException: Premature end of file. | at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236) | at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:215) | at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:386) | at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316) | at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVersionDetector.java:230) | at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:798) | at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) | at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148) | at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242) | at javax.xml.parsers.SAXParser.parse(SAXParser.java:375) | at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227) | at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696) | at org.apache.axis.Message.getSOAPEnvelope(Message.java:435) | at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62) | at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206) | at org.apache.axis.client.Call.invokeEngine(Call.java:2784) | at org.apache.axis.client.Call.invoke(Call.java:2767) | at org.apache.axis.client.Call.invoke(Call.java:2443) | at org.apache.axis.client.Call.invoke(Call.java:2366) | at org.apache.axis.client.Call.invoke(Call.java:1812) | at clientLett.ServiceLettBindingStub.fattoriale(ServiceLettBindingStub.java:117) | at Test.main(Test.java:38) | | {http://xml.apache.org/axis/}hostname:angelinux | | org.xml.sax.SAXParseException: Premature end of file. | at org.apache.axis.AxisFault.makeFault(AxisFault.java:101) | at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:701) | at org.apache.axis.Message.getSOAPEnvelope(Message.java:435) | at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62) | at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206) | at org.apache.axis.client.Call.invokeEngine(Call.java:2784) | at org.apache.axis.client.Call.invoke(Call.java:2767) | at org.apache.axis.client.Call.invoke(Call.java:2443) | at org.apache.axis.client.Call.invoke(Call.java:2366) | at org.apache.axis.client.Call.invoke(Call.java:1812) | at clientLett.ServiceLettBindingStub.fattoriale(ServiceLettBindingStub.java:117) | at Test.main(Test.java:38) | Caused by: org.xml.sax.SAXParseException: Premature end of file. | at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236) | at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:215) | at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:386) | at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316) | at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVersionDetector.java:230) | at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:798) | at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) | at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148) | at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242) | at javax.xml.parsers.SAXParser.parse(SAXParser.java:375) | at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227) | at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696) | ... 10 more | Why? How can I resolve? Thanks, bye bye. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097730#4097730 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097730

18 years

1
0
0 / 0

[JBossWS] - Re: JBoss and Apache Axis compatibility

by oskar.carlstedt

Hi! If you are creating "contract first" web services, there should be no problem at all. If you are generating your contract you can get into trouble. So stick to contract first and generate booth service implementation and client usage from the contract to be on the "safe" side. Regards Oskar View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097706#4097706 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097706

18 years

1
0
0 / 0

[JBossWS] - Re: JBoss and Apache Axis compatibility

by sarunb4u

Hi ppl I need your help here. I'll really appreciate any kind of help as i'm new to this web service stuff. --Arun View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097693#4097693 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097693

18 years

1
0
0 / 0

[JBossWS] - Re: web service not found

by robert_trudel

there is no error View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097589#4097589 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097589

18 years

1
0
0 / 0

[JBossWS] - Re: Jboss Annotation: WebContext package and JAR location.

by richard.opalka＠jboss.com

Yes, it should be the same (but refactored) annotation ;-) Richard View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097550#4097550 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097550

18 years

1
0
0 / 0

[JBossWS] - Re: Deployed service statistics

by abdujaparov

Hi! I begin to study jmx, I hope to understand something, the code posted by oskar permits to take the list of web service deployed on jboss? A question, has jbossws statistics about each operation (ex: number of request of operation echo(String) of service Pippo) of the service or only the general statistics of a service (ex: number of request of service Pippo)? Thanks! Bye Bye. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097532#4097532 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097532

18 years

1
0
0 / 0

[JBossWS] - Newbie with JbossWS

by AnisBM

Hi all, Do the WSTools generate web services conform to Seam 2.0 web services ? PS : I'm using those integrated in JBoss 4.2.1. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097476#4097476 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097476

18 years

1
0
0 / 0

[JBossWS] - JBoss and Apache Axis compatibility

by sarunb4u

I'm in the midst of integrating two components, one runs in JBoss and other components exposes some web services deployed in Axis. When i integrate them, there will be a communication between component deployed in JBOSS and Web services exposed via Axis. If i understand correctly, AXIS by default uses RPC service style and JBOSS uses document/literal encoding format. So there is a notion of soap-wsdl encoding format change required here. All i wanted to know is that, 1.Is there any compatibility issues (if any) between JBOSS and Axis ? 2.JBOSS-Axis interaction with respect to the soap encoding format ? 3.Some explanation on SOAP encodingStyle ? Regards Arun View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097465#4097465 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097465

18 years

1
0
0 / 0

[JBossWS] - Re: org.jboss.ws.WSException: Cannot find java method

by ZazzaZ

I just modified my WSDL like this | | <?xml version="1.0" encoding="UTF-8"?> | <definitions name="ControlloAccesso" targetNamespace="http://j2ee.netbeans.org/wsdl/ControlloAccesso" | xmlns="http://schemas.xmlsoap.org/wsdl/" | xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" | xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" | xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://j2ee.netbeans.org/wsdl/ControlloAccesso" xmlns:ns="http://xml.netbeans.org/schema/LoginTypes"> | <types> | <xsd:schema targetNamespace="http://j2ee.netbeans.org/wsdl/ControlloAccesso"> | <xsd:import namespace="http://xml.netbeans.org/schema/LoginTypes" schemaLocation="types.xsd"/> | </xsd:schema> | </types> | <message name="ControlloAccessoOperationRequest"> | <part name="cred" type="ns:Credenziali"/> | </message> | <message name="ControlloAccessoOperationReply"> | <part name="iden" type="ns:Identificato"/> | </message> | <portType name="ControlloAccessoPortType"> | <operation name="controlloAccessoOperation"> | <input message="tns:ControlloAccessoOperationRequest"/> | <output message="tns:ControlloAccessoOperationReply"/> | </operation> | </portType> | <binding name="ControlloAccessoBinding" type="tns:ControlloAccessoPortType"> | <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/> | <operation name="controlloAccessoOperation"> | <soap:operation/> | <input> | <soap:body use="literal" namespace="http://j2ee.netbeans.org/wsdl/ControlloAccesso"/> | </input> | <output> | <soap:body use="literal" namespace="http://j2ee.netbeans.org/wsdl/ControlloAccesso"/> | </output> | </operation> | </binding> | <service name="ControlloAccessoService"> | <port name="ControlloAccessoPort" binding="tns:ControlloAccessoBinding"> | <soap:address location="http://localhost:8080/ControlloAccesso/controllo"/> | </port> | </service> | | </definitions> | | ant regenerating the service went OK. I dunno if the problem was in the attribute name of binding operation or message part but now it works! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097444#4097444 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097444

18 years

1
0
0 / 0

[JBossWS] - Jboss Annotation: WebContext package and JAR location.

by ptenn10

Hi All, Quick question: I would like to use WebContext for EJB3. However, it seems like the packaging has changed on this annotation. Under the examples for jbossws-1.2.1GA, I saw the annotation being imported as: org.jboss.ws.annotation.WebContext However, I could not find this anywhere in jbossws-2.0.1GA (I checked through all the JARs). I did find: org.jboss.wsf.spi.annotation.WebContext Is this the same annotation? Can I rely on this to work as the WebContext annotation that was described in the examples? Thanks, Philip Tenn View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097437#4097437 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097437

18 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-users October 2007