javaee / metro-jax-ws Goto Github PK
View Code? Open in Web Editor NEWHome Page: https://javaee.github.io/metro-jax-ws/
License: Other
Home Page: https://javaee.github.io/metro-jax-ws/
License: Other
I am trying to build a web service with notification function using JAX-WS2.0,
and I use the wsimport to generate the artifacts.
In the WSDL, I import
http://schemas.xmlsoap.org/ws/2004/08/eventing/eventing.wsdl file.
( <wsdl:import location="eventing.wsdl"
namespace="http://schemas.xmlsoap.org/ws/2004/08/eventing"/> )
When I checked the SOAP response message in the SOAP Envelope and I found the
prefix ns3 is pointed to namespace http://www.w3.org/XML/1998/namespace, but if
you go to http://www.w3.org/XML/1998/namespace link
And you will see:
The namespace whose name is http://www.w3.org/XML/1998/namespace is bound by
definition to the prefix xml: according to Namespaces in XML, W3C
Recommendation 14 Jan 1999 (and by Namespaces in XML 1.1). Note that unlike all
other XML namespaces, both the name and the prefix are specified; i.e., if you
want XML 1.0 processors to recognize this namespace, you must use the reserved
prefix xml:.
So I always got exception when tried to parse the following Soap Return,
because of the wrong prefix –ns3 for this namespace.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:ns1="http://schemas.xmlsoap.org/ws/2004/08/addressing"
xmlns:ns2="http://schemas.xmlsoap.org/ws/2004/08/eventing"
xmlns:ns3="http://www.w3.org/XML/1998/namespace">
You will find the eventing.xsd schema at :
http://schemas.xmlsoap.org/ws/2004/08/eventing/eventing.xsd , and in this
schema there is also a bug there,
The schemaLocation=http://schemas.xmlsoap.org/ws/2004/08/addressing for
addressing should be changed to
I am using IDE NetBeans 5.5 with JAX-WS 2.0 lib.(FCS) with Sun's Java System
application Server PE 9 FCS and TomCat server.
And I also got the same problem when using JAX -WS (RI) Version: 2.0 ea3.
Now seems I cannot find a way to change the prefix to "xml" for the
namespace: "http://www.w3.org/XML/1998/namespace", because I always got
exception when tried to run the following code:
SOAPPart sp = message.getSOAPPart();
SOAPEnvelope ev = sp.getEnvelope();
Or doing some type casting.
It indicates Wrong prefix problem.
Operating System: All
Platform: All
[2.0 FCS]
Entering the issue posted in the JAX-WS forum (
http://forums.java.net/jive/thread.jspa?threadID=16597&tstart=0 )
I created the WSDL with the wsgen-tool out of the Impl-Class with the following code
@webmethod(operationName="request",
action="urn:Request"
)
public String[][] request(String testCall)
{...}
Then I compiled all classes and put them into a WAR.
But if the tomcat expands the WAR this error is thrown:
'JAXRPCSERVLET11: failed to parse runtime descriptor: no parameter found for
index: -1 in wrapper bean :org.test.arrays.jaxws.RequestResponse of method: request'
A Web Service with an one dimensional String array throws
the same error.
Operating System: All
Platform: All
[2.0 FCS]
this enhancment is tied with tcp binding, which should present in generated wsdl.
currently we have in wsit.xml policy specified, that certain port is supporting
tcp transport.
When this policy assertion will be processed by wsdl generator extension - i
need possibility to take as base binding and service description generated for
http, copy them, just rename, and change transport in binding.
Currently generator extensions are called before WSDLGenerator, so i will need
extension to be called probably after WSDLGenerator with possibility to use just
generated model.
Operating System: All
Platform: All
[2.0.1 Early Access]
Hi,
I am tring to use JAX-WS 2.0.1 implementation to test RESTful Web Service.
Under testing, I got the following exception stack trace.
java.lang.NullPointerException
at com.sun.xml.ws.encoding.XMLHTTPBindingCodec.compareStrings
(XMLHTTPBindingCodec.java:227)
at com.sun.xml.ws.encoding.XMLHTTPBindingCodec.isMultipartRelated
(XMLHTTPBindingCodec.java:210)
at com.sun.xml.ws.encoding.XMLHTTPBindingCodec.decode
(XMLHTTPBindingCodec.java:180)
I think this reason is why GET operation may have no Content-Type header.
Therefore, a 'src/com/sun/xml/ws/encoding/XMLHTTPBindingCodec#compareStrings()'
method need NULL Checking.
In my case, I tried the following code and resolved my problem.
private boolean compareStrings(String a, String b) {
Operating System: All
Platform: All
[current]
Weekly build 20th of October.
I am using SE HttpServer + BasicAuthFilter + HTTP Binding.
The following scenario works properly when using SOAP binding.
The client send an Authenticated request.
The server Filter is not called.
The client receives an exception :
Caused by: javax.xml.ws.WebServiceException: request requires HTTP
authentication: Unauthorized
at
com.sun.xml.ws.util.XMLConnectionUtil.getXMLMessage(XMLConnectionUtil.java:66)
at
com.sun.xml.ws.protocol.xml.client.XMLMessageDispatcher.getXMLMessage(XMLMessageDispatcher.java:711)
at
com.sun.xml.ws.protocol.xml.client.XMLMessageDispatcher.receive(XMLMessageDispatcher.java:310)
at
com.sun.xml.ws.protocol.xml.client.XMLMessageDispatcher.doSend(XMLMessageDispatcher.java:187)
at
com.sun.xml.ws.protocol.xml.client.XMLMessageDispatcher.send(XMLMessageDispatcher.java:100)
at
com.sun.xml.ws.client.dispatch.impl.DispatchDelegate.send(DispatchDelegate.java:75)
at
com.sun.xml.ws.client.dispatch.DispatchBase.sendAndReceive(DispatchBase.java:305)
... 7 more
Operating System: All
Platform: Sun
[current]
In case that only "className" property of javax.xml.ws.RequestWrapper annotation
is present, it is not reflected in the wsdl file generated by wsgen command.
The same is true of javax.xml.ws.ResponseWrapper annotation.
It is true that RequestWrapper or ResponseWrapper class is generated according
to the annotation, but the wsdl file is not.
I believe that value of "name" attribute of "xs:complexType" element in "types"
element in the wsdl file or external schema file (.xsd) should be the same with
value of "className" property in RequestWrapper or ResponseWrapper annotation if
it is present.
Actually, in reverse case, "className" value of RequestWrapper or
ResponseWrapper annotation in stub class generated by wsimport command is the
same with "name" value of "xs:complexType" element.
Developers at the client side can get informations about Web Service only from
wsdl, therefore all informations should be represented in wsdl file.
Operating System: All
Platform: All
[current]
I've written a simple webservice and implemented the client and the server (J2SE
Client) with JAX-WS (nightly 20060504). When I call the service, at the
serverside the following exception is thrown during parsing the soap message:
08.05.2006 17:50:18 com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher
toMessageInfo
SCHWERWIEGEND: Error in decoding SOAP Message
Error in decoding SOAP Message
at
com.sun.xml.ws.encoding.soap.server.SOAPXMLDecoder.toInternalMessage(SOAPXMLDecoder.java:89)
at
com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher.toMessageInfo(SOAPMessageDispatcher.java:187)
...
and more interesting below:
Caused by: javax.xml.ws.soap.SOAPFaultException: Cannot find the dispatch method
I had a short look at the source and there seems to be a problem mapping the
soap "method"-name:
The problem raises in SOAPXmlDecoder.decodeDispatchMethod:
JavaMethod javaMethod = rtModel.getJavaMethod(name);
It seems that jax-ws uses a wrong namespace to do the lookup of the correct java
method.
See below the wsdl:
<wsdl:definitions 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://fss.o2.com/portal/services"
targetNamespace="http://fss.o2.com/portal/services"
xmlns:transport="http://fss.o2.com/portal/transport">
wsdl:types
</wsdl:types>
<wsdl:message name="checkAddressRequestMsg">
<wsdl:part name="checkAddressRequestPart" type="xsd:string"/>
</wsdl:message>
<wsdl:message name="checkAddressResultMsg">
<wsdl:part name="checkAddressResultPart" type="xsd:string"/>
</wsdl:message>
<wsdl:message name="GenericException">
<wsdl:part name="errorPart" element="xsd:string"/>
</wsdl:message>
<wsdl:portType name="PortalEaiPortType">
<wsdl:operation name="checkAddress">
<wsdl:input message="tns:checkAddressRequestMsg"/>
<wsdl:output message="tns:checkAddressResultMsg"/>
<wsdl:fault name="GenericException" message="tns:GenericException"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="PortalEaiBinding" type="tns:PortalEaiPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="checkAddress">
wsdl:documentationThe operation has no documentation</wsdl:documentation>
<soap:operation style="rpc" soapAction="Portal_Portal2BPM_checkAddress"/>
wsdl:input
<soap:body parts="checkAddressRequestPart" use="literal"
namespace="http://fss.o2.com/portal/input"/>
</wsdl:input>
wsdl:output
<soap:body parts="checkAddressResultPart" use="literal"
namespace="http://fss.o2.com/portal/output"/>
</wsdl:output>
<wsdl:fault name="GenericException">
<soap:fault name="GenericException" use="literal"/>
</wsdl:fault>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="PortalEaiService">
<wsdl:port name="PortalEaiHttpPort" binding="tns:PortalEaiBinding">
<soap:address
location="http://tibco13413008:2020/Business__Processes/Adapters/Portal/Inbound/portalEai"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
My Testcase:
public class ServerTestBugRep extends TestCase
{
public void testWSCall() throws MalformedURLException
{
// Server
PortalEaiPortBugRepImpl portalEaiPortImpl = new PortalEaiPortBugRepImpl();
Endpoint portalEaiEndpoint = Endpoint.publish(
"http://localhost:8080/jaxws-test/portalEai", portalEaiPortImpl);
// Client Start
PortalEaiService portalEaiService = new PortalEaiService();
PortalEaiPortType portalEaiPortType =
portalEaiService.getPortalEaiHttpPort();
Map requestContext = ((BindingProvider)
portalEaiPortType).getRequestContext();
requestContext.put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY,
"http://localhost:82/jaxws-test/portalEai");
try
{ String checkAddressResult = portalEaiPortType .checkAddress("TestRequestString"); assertEquals("checkAddressResult.getOverallRemark()", "OverallRemark response", checkAddressResult); }
catch (GenericException e)
{ fail(e.getMessage()); }
// Client end
// Server stop
portalEaiEndpoint.stop();
}
}
The server dummy implementation:
@webservice(endpointInterface =
"com.o2.portal.fss.connector.jaxws.PortalEaiPortType")
public class PortalEaiPortBugRepImpl implements PortalEaiPortType
{
public String checkAddress(String checkAddressRequest)
throws GenericException
{ return "Response test string"; }
}
Chris Wewerka
Operating System: All
Platform: All
[current]
Hi,
I am tring to use JAX-WS 2.0.1 implemention.
Under testing, I got the following exception stack strace.
java.lang.NullPointerException
at
com.sun.xml.ws.encoding.MtomCodec$MtomXMLStreamReaderEx.next(MtomCodec.java:409)
at
com.sun.xml.bind.v2.runtime.unmarshaller.StAXStreamConnector.bridge(StAXStreamConnector.java:150)
at
com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:332)
at com.sun.xml.bind.v2.runtime.BridgeImpl.unmarshal(BridgeImpl.java:84)
at com.sun.xml.bind.api.Bridge.unmarshal(Bridge.java:188)
at
com.sun.xml.ws.message.stream.StreamMessage.readPayloadAsJAXB(StreamMessage.java:205)
at
com.sun.xml.ws.server.sei.EndpointArgumentsBuilder$Body.readRequest(EndpointArgumentsBuilder.java:406)
at
com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:239)
at com.sun.xml.ws.server.sei.SEIInvokerPipe.process(SEIInvokerPipe.java:97)
at com.sun.xml.ws.protocol.soap.ServerMUPipe.process(ServerMUPipe.java:62)
at com.sun.xml.ws.server.WSEndpointImpl$1.process(WSEndpointImpl.java:139)
I think this reason is why a content id decided from [Extract 1] mismatched a
content id changed from [Extract 2].
[Extract 1] From com.sun.xml.ws.encoding.MtomCodec#decodeCid() (revision 1.1.2.7)
private String decodeCid(String cid) {
if (cid.startsWith("cid:"))
cid = cid.substring(4, cid.length());
try
{ return "<" + URLDecoder.decode(cid, "UTF-8") + ">"; }
catch (UnsupportedEncodingException e)
{ throw new WebServiceException(e); }
}
[Extract 2] From com.sun.xml.ws.encoding.MimeMultipartParser#getNextPart()
(revision 1.1.2.6)
private StreamAttachment getNextPart() {
...
if(contentId!=null && contentId.length()>2)
{ if(contentId.charAt(0)=='<') contentId=contentId.substring(1,contentId.length()-1); }
...
}
Thanks.
Operating System: All
Platform: All
[2.0.1 Early Access]
Hi,
Just noticed that the documentation on handlers is incrorect:
https://jax-ws.dev.java.net/jax-ws-20-fcs/docs/handlers.html
In the seciton "Programmatic Case" it gives the example code:
// given proxy interface HelloPortType
HelloPortType myProxy = // create proxy
Binding binding = myProxy.getBinding();
However, this should read:
// given proxy interface HelloPortType
HelloPortType myProxy = // create proxy
Binding binding = (((BindingProvider)myProxy).getBinding();
thanks,
Martin
Operating System: All
Platform: All
URL: https://jax-ws.dev.java.net/jax-ws-20-fcs/docs/handlers.html
[2.0 FCS]
I'm trying to use a header out param in my web service, which must be used with
a .Net client. For some reason (don't ask me why), the wsdl.exe web service
client proxy generator shipped with Visual Studio 2005 really wants the message
part for the result in the response named "parameters" when using a header out
param as well. JAX-WS defaults to naming the message part "result", which
causes wsdl.exe to generate wrapper objects for the response and parameters.
Anyways, I tried to work around .Net by using this:
package com.foo;import javax.jws.WebParam;import javax.jws.WebResult;import
javax.jws.WebService;import javax.xml.ws.Holder;@webservice
(serviceName="TestService")public class TestEndPoint { @webresult
(name="parameters") public String method1(@WebParam(mode=WebParam.Mode.OUT,
header=true) Holder
{ header.value = new Header(); header.value.setHeaderValue("Header Value"); return "method1 Return"; }
}
but it appears that when using the WebParam annotation with header=true, the
WebResult annotation gets ignored. If I remove the header=true from the
WebParam annotation, the message part is called "parameters", but with
header=true, the message part is called "result":
I noticed that the @webresult(name="parameters") causes the apt-generated
com.foo.jaxws.Method1Response to include an @xmlelement(name="parameters")
on the _result member. This happens with or without the @WebParam(...,
header=true). It appears that it's not a problem with apt, it's a runtime
problem with JAX-WS that causes the @xmlelement annotation in
Method1Response to be ignored when there's a header param
The default value for this customization is WRAPPED, which means the output
wsdl:message has only one part (according to jaxws 2.0 spec rules), however
while building internal model and generating there is some bug that tries to
work on it as WRAPPED and latter on finds that there are two parameters and
generates the wsdl as non-wrapped style.
Operating System: All
Platform: All
URL: http://forums.java.net/jive/thread.jspa?threadID=17469&tstart=0
[current]
Here's my source schema snippet:
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element name="Telephone" type="xs:string"/>
<xs:element name="Fax" type="xs:string"/>
<xs:element name="X400" type="xs:string"/>
<xs:element name="URI" type="xs:anyURI"/>
<xs:element name="Email" type="xs:string"/>
</xs:choice>
Here's the generated java code:
public List<JAXBElement> getTelephoneOrFaxOrX400() {
if (telephoneOrFaxOrX400 == null) {
telephoneOrFaxOrX400 = new ArrayList<JAXBElement>();
}
return this.telephoneOrFaxOrX400;
}
Here's the INVALID generated schema that the jax-ws web service produces:
<xs:choice maxOccurs="unbounded">
<xs:element ref="ns12:Email"/>
<xs:element ref="ns13:Fax"/>
<xs:element ref="ns14:X400"/>
<xs:element ref="ns15:URI"/>
<xs:element ref="ns16:Telephone"/>
</xs:choice>
The references are to nonexistant elements in undefined namespaces.
Looks like a bug to me.
Operating System: All
Platform: All
URL: http://forums.java.net/jive/thread.jspa?threadID=13386&tstart=0
[current]
When I implementing RESTful Web Service. I found a strange behavior of
QUERY_STRING in RequestContext.
1. This program works fine.
Source:
s.addPort(portName, HTTPBinding.HTTP_BINDING, uri + "?%E5%B2%A1%E5%B4%8E");
Dispatch
Source.class, Service.Mode.PAYLOAD);
Map<String, Object> reqContext = d.getRequestContext();
reqContext.put(MessageContext.HTTP_REQUEST_METHOD, "GET");
Source result = d.invoke(null);
Request:
GET http://localhost:9090/hello?%E5%B2%A1%E5%B4%8E HTTP/1.1
Accept: text/xml, application/xop+xml, text/html, image/gif, image/jpeg, *;
q=.2, /; q=.2
Content-Type: text/xml
User-Agent: Java/1.6.0-dp
Host: localhost
Proxy-Connection: keep-alive
2. By using this program, send a query string through requestContext,
QUERY_STRING was decoded before invoke.
Source:
s.addPort(portName, HTTPBinding.HTTP_BINDING, uri);
Dispatch
Source.class, Service.Mode.PAYLOAD);
Map<String, Object> reqContext = d.getRequestContext();
reqContext.put(MessageContext.HTTP_REQUEST_METHOD, "GET");
reqContext.put(MessageContext.QUERY_STRING, "%E5%B2%A1%E5%B4%8E");
Source result = d.invoke(null);
Request:
GET http://localhost:9090/hello?岡崎 HTTP/1.1
Accept: text/xml, application/xop+xml, text/html, image/gif, image/jpeg, *;
q=.2, /; q=.2
Content-Type: text/xml
User-Agent: Java/1.6.0-dp
Host: localhost
Proxy-Connection: keep-alive
Operating System: All
Platform: All
[2.0 FCS]
I work in Netbeans.When I created ws client on glassfish in module with spaces
in path, I get error message :
"error: Unable to parse - Illegal character in path at index
18:file:/C:/Documents and Settings/..."
Attaching whole output from ws client creation in text file.
Operating System: Windows XP
Platform: PC
[JAXWS 2.0 EA2]
Plugins can be written for the JAXB2 compiler by implementing
com.sun.tools.xjc.Plugin. See here:
http://java.sun.com/webservices/docs/2.0/jaxb/developPlugins.html.
Currently, there is now way to specify such plugins when running wsimport. Since
wsimport invokes xjc, it's logical to have this capability.
Operating System: All
Platform: All
[current]
When the SOAPAction is set using :
reqcontext.put(BindingProvider.SOAPACTION_URI_PROPERTY,
"http://example.com/mismatch");
reqcontext.put(BindingProvider.SOAPACTION_USE_PROPERTY, Boolean.valueOf(true));
it does not get propagated to the SOAP message. This case is true for both
dispatch as well as proxy client. Also this holds true irrespective of whether
the 'soapAction' property is set or not(in the WSDL).
Operating System: All
Platform: All
[2.0.1 Early Access]
@XmlRootElement
@XmlAccessorType(XmlAccessType.FIELD)
@XmlType(name = "sessionRequest", propOrder = {
"clientCredentials",
"clientInformation"
})
public class SessionRequest {
@XmlJavaTypeAdapter(CredentialsAdapter.class)
protected Credentials clientCredentials;
protected ClientInfo clientInformation;
And one of implementations of Credentials interface is class:
—
@XmlAccessorType(XmlAccessType.FIELD)
@XmlType(name = "userPasswordCredentials", propOrder = {
"password",
"username"
})
public class UserPasswordCredentials implements Credentials{
protected String password;
protected String username;
I have an webservice which accepts SessionRequest as parameter. (WSDL file is
attached to the issue).
in my test program I do call to that webservice:
public void testWS() throws JAXBException, MalformedURLException
{ //JAXBContext context = JAXBContext.newInstance("be.certipost.jc.accesspoint.server"); URL url = new URL("http://localhost:8081/comms/CertiOneAccessPoint?wsdl"); QName qname = new QName("http://accesspoint.jc.certipost.be/server", "ServerService"); ServerService se = new ServerService(url,qname); CertiOneAccessPoint port = se.getCertiOneAccessPointPort(); SOAPBinding binding = (SOAPBinding)((BindingProvider)port).getBinding (); binding.setMTOMEnabled (true); // ObjectFactory factory = new ObjectFactory(); SessionRequest sreq = new SessionRequest(); UserPasswordCredentials credentials =new UserPasswordCredentials(); credentials.setUsername("user"); credentials.setPassword("password"); sreq.setClientCredentials(credentials ); SessionResponse resp = port.createSession(sreq ); Date date = new Date(resp.getSessionId()); System.out.println(date); }
And I got exception:
Exception in thread "main" javax.xml.ws.WebServiceException:
com.sun.xml.ws.util.exception.XMLStreamException2
at com.sun.xml.ws.encoding.MtomCodec.encode(MtomCodec.java:155)
at com.sun.xml.ws.encoding.CodecFacade.encode(CodecFacade.java:69)
at
com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:100)
at com.sun.xml.ws.protocol.soap.ClientMUPipe.process(ClientMUPipe.java:58)
at com.sun.xml.ws.handler.HandlerPipe.process(HandlerPipe.java:91)
at com.sun.xml.ws.handler.HandlerPipe.process(HandlerPipe.java:91)
at com.sun.xml.ws.client.Stub.process(Stub.java:121)
at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:122)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:238)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:212)
at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:105)
at $Proxy22.createSession(Unknown Source)
at testClient.testWS(testClient.java:48)
at testClient.main(testClient.java:30)
Caused by: com.sun.xml.ws.util.exception.XMLStreamException2
at com.sun.xml.ws.message.jaxb.JAXBMessage.writePayloadTo(JAXBMessage.java:244)
at com.sun.xml.ws.message.AbstractMessageImpl.writeTo(AbstractMessageImpl.java:117)
at com.sun.xml.ws.encoding.MtomCodec.encode(MtomCodec.java:130)
... 13 more
Caused by: javax.xml.bind.MarshalException
I included all files with @xmltype annotation to jaxb.index file in the same
package:
ClientInfo
CloseSession
CloseSessionResponse
CreateSession
CreateSessionResponse
DataInstructions
DataType
ExecuteSessionCommand
ExecuteSessionCommandResponse
ListUnfinishedSessions
ListUnfinishedSessionsResponse
ReopenSession
ReopenSessionResponse
Request
Response
SessionRequest
SessionResponse
UserPasswordCredentials
If I do test with marshalling in JAXB it works perfect:
–
public void testJAXB() throws JAXBException
{ JAXBContext context = JAXBContext.newInstance("be.certipost.jc.accesspoint.server"); Marshaller m = context.createMarshaller(); SessionRequest sreq = new SessionRequest(); UserPasswordCredentials credentials =new UserPasswordCredentials(); credentials.setUsername("user"); credentials.setPassword("password"); sreq.setClientCredentials(credentials ); m.marshal(sreq,System.out); }
I got as result correct xml:
–
Strange thing that if I use directly UserPasswordCredentials as field in
SessionRequest (instead of Credentials interface) then webservice work perfectly.
I tried it with release version of JAX-WS and with snapshot JAXWS2.0.1ea_39.jar.
But it is problem for both versions
What causes problem with interfaces ?
Operating System: All
Platform: All
[current]
package test;
//... imports
@webservice(name = "TestManagerPortType", targetNamespace = "http://
www.test.com/services/test", serviceName = "TestManager")
@SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL,
parameterStyle = SOAPBinding.ParameterStyle.WRAPPED)
public class TestManager {
public TestManager()
{ super(); }
@webmethod
@Oneway
public void deployXSD(String xsdContent)
{ //.... }
}
If I set the @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use =
SOAPBinding.Use.LITERAL, parameterStyle = SOAPBinding.ParameterStyle.WRAPPED)
annotations to my service class then I get an deployment exception:
class: test.jaxws.DeployXSD could not be found
at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
at
com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
at
com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
at
com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
at
com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
at
com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:229)
at
com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:161)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:291)
at
com.sun.xml.ws.transport.http.DeploymentDescriptorParser.parseAdapters(DeploymentDescriptorParser.java:237)
at
com.sun.xml.ws.transport.http.DeploymentDescriptorParser.parse(DeploymentDescriptorParser.java:131)
at
com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized(WSServletContextListener.java:90)
...
The reason is in doc/literal wrapped stype the WSDL XSD element name must equal
the operation name so the system try to generate deployXSD element and try to
found the class DeployXSD as the wrapped type for the method params.
So the generating doc/literal wrapped style of WSDL is not supported. To obtain
the doc/literal wrapped style of WSDL I should to use the workaround: set
SOAPBinding.ParameterStyle.BARE and create such classes as DeployXSD manually.
Operating System: All
Platform: All
[current]
If SEI is in default package, the wsgen looks for wrapper beans in ".jaxws."
package instead of "jaxws." package (extra period at the beginning of first
package name). Here is the error that I'm getting:
D:\workspaces\mr-21\jaxws-rearch\build\bin>"d:/testbed/jdk1.5.0\bin\java" -cp
".;d:/testbed/jdk1.5.0\lib\tools.jar;D:/
workspaces/mr-21/jaxws-rearch/build\lib\jaxws-tools.jar" com.sun.tools.ws.WsGen
-wsdl -cp . AddNumbersImpl
class: .jaxws.AddNumbersExceptionBean could not be found
class: .jaxws.AddNumbersExceptionBean could not be found
at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
at
com.sun.xml.ws.model.RuntimeModeler.processExceptions(RuntimeModeler.java:971)
at
com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:716)
at
com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
at
com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
at com.sun.tools.ws.wscompile.CompileTool.buildModel(CompileTool.java:653)
If SEI is in a non-default package, then wsgen generates the WSDL correctly.
Operating System: All
Platform: All
[2.0.1 Early Access]
Doing wsImport on the attached WSDL (which doesnt have a SOAP binding) fails.
<<< e-mail discussion >>>
Hi Binod,
I see you're using wsomcpile, that means jaxrpc. wscompile only worked with the
wsdl with SOAPBinding. It didn't support any other binding.
I tried with jaxws, wsimport tool. At present wsimport also only supports
SOAPBinding. We can try to add a feature where such wsdls can be supported. Can
you file an issue at jax-ws http://jax-ws.dev.java.net/servlets/ProjectIssues
and we can try to add this feature in wsimport in the upcoming version of jaxws.
If you can use jaxws, as a work around, you can work with Dispatch and Provider
endpoint?
-vivek.
Binod wrote:
Hi Vivek,
Can you answer this question? Please let us know, if you are not the right person
to answer this?thanks,
Binod.Hi Vivek,
Please see the attached WSDL. It does not contain any SOAP binding.
Would it be possible to generate ws client stubs from this WSDL?If it cannot, what is the recommended way for non-http bindings to creata WSDL?
thanks for your time,
Binod.Hi Binod,
When I try to call wscompile to generate client stub on the
OutputFileService.wsdl, I got the following warning:
C:\Alaska\MyProjects\EchoProject\EchoEJBModule\bindings\fileout>c:\Alaska\sun\appserver\bin\wscompile
-import config.xml -verbose -Xprintstacktrace
warning: ignoring port "FileOut": no SOAP address specified
warning: Service "MyFileService" does not contain any usable ports
[ServiceInterfaceGenerator: creating service interface:
com.sun.ejbtofile.MyFileService]
C:\Alaska\MyProjects\EchoProject\EchoEJBModule\bindings\fileout>c:\Alaska\sun\appserver\bin\wscompile
-gen config.xml
warning: ignoring port "FileOut": no SOAP address specified
warning: Service "MyFileService" does not contain any usable portsIt only created the service interface and there is no corresponding porttype
classes created. Do you know how to create ws client stubs for an internal WSDL
such as File BC or JMS BC? I am trying to call the File BC from an EJB.Thanks
Venu
Operating System: All
Platform: Sun
[current]
Using JAX-WS to generate Web Service artifacts from an EJB 3.0, I get a wsdl and
xsd files that works but are not valide (just warnings). Problem is relating to
a targetnamespace (I did not customize targetnamespaces).
I saw this by running wsimport from a Web Service client, the output of the
wsimport gives warnings. Validation of the xsd files gives also errors.
However, the exposed Web Service is working.
I have attached wsdl and xsd files. Here are outputs :
Part of wsimport ouput (from client) :
generate-client-artifacts:
E:/Env/Sun/AppServer/bin/wsimport.bat -keep -d build/jar/client
http://localhost:8080JVTTroubleTicketServantService/JVTTroubleTicketServant?WSDL
warning: s4s-att-invalid-value: Invalid attribute value for 'type' in element
'element'. Recorded reason: UndeclaredPrefix: Cannot resolve
'ns3:personReachImpl' as a QName: the prefix 'ns3' is not declared.
line 16 of
http://129.157.211.56:8080/JVTTroubleTicketServantService/JVTTroubleTicketServant/__container$publishing$subctx/META-INF/wsdl/JVTTroubleTicketServantService_schema1.xsd
warning: s4s-att-invalid-value: Invalid attribute value for 'type' in element
'element'. Recorded reason: UndeclaredPrefix: Cannot resolve
'ns3:activityDurationListImpl' as a QName: the prefix 'ns3' is not declared.
line 17 of
http://129.157.211.56:8080/JVTTroubleTicketServantService/JVTTroubleTicketServant/__container$publishing$subctx/META-INF/wsdl/JVTTroubleTicketServantService_schema1.xsd
Part of the xsd validation output :
XML validation started.
s4s-att-invalid-value: Invalid attribute value for 'type' in element 'element'.
Recorded reason: UndeclaredPrefix: Cannot resolve 'ns3:personReachImpl' as a
QName: the prefix 'ns3' is not declared. [16]
s4s-att-invalid-value: Invalid attribute value for 'type' in element 'element'.
Recorded reason: UndeclaredPrefix: Cannot resolve 'ns3:activityDurationListImpl'
as a QName: the prefix 'ns3' is not declared. [17]
...
Operating System: Windows XP
Platform: PC
[current]
According to the blog in the URL field, the RI is supposed to allow the JAXB
@XmlMimeType annotation to be placed on a web method parameer of an SEI. In all
binding styles this does not work:
With document/literal wrapped, jaxb annotations are not copied from the SEI to
the generated wrapper beans.
All other styles don't work because the JAXB-RI does not look for that
particular annotaiton when inspecting a TypeReference. So really this is a JAXB
issue, I just included the information here for completeness.
Operating System: All
Platform: All
URL: http://weblogs.java.net/blog/vivekp/archive/2006/05/mtom_in_jaxws_r.html
[current]
Hi,
I am tring to use the JAX-WS 2.0.1 implementation.
A com.sun.xml.ws.handler.ClientSOAPHandlerPipe's close() method is not
implemented yet.
And so, a SOAPHandler's close() method is not called.
Thanks
Operating System: All
Platform: All
[2.0.1 Early Access]
The current dispatching mechanism on the server-side is based upon QName of the
first child in Body. However WS-Addressing requires dispatching based upon
wsa:Action. The current dispatching mechanism currently ignores wsa:Action. A
pluggable dispatching mechanism will enable wsa:Action-based dispatching.
Operating System: All
Platform: All
[current]
Hello,
I am trying to upload large files with MTOM. I have played around with -Xms and
-Xmx options but this didn't solve the problem. The test file I try to transfer
is around 690MB.
I am working on a centrino duo with 2GB ram, so hardware shouldn't be a problem.
Even if I would set a higher Xms which can handle the one large file, that would
still not be the solution for the real world with multiple downloads/uploads.
Thanks
Operating System: Windows XP
Platform: All
[current]
Having multiple wsdl:imports in a file with the same namespace, but different
locations produces an erroneous 'error: duplicate "import" entity: x' message.
Example:
<definitions ...>
<wsdl:import namespace=�x� location=�messages_and_porttypes.wsdl�/>
<wsdl:import namespace=�x� location=�portbinding_one.wsdl�/>
<wsdl:import namespace=�x� location=�portbinding_two.wsdl�/>
I have a problem with the schema generation feature for a webservice java class.
See the following test service class:
@webservice
@SOAPBinding(style = Style.RPC)
public class CollectionAsParamTestService
{
public void testCollections(ArrayList stringList)
{
}
}
If I generate the wsdl and the corresponding schema with wsgen, the wsdl is
generated with the following message fragment:
So far so good. Now the generated schema:
<xs:schema version="1.0"
targetNamespace="http://impl.service.webservice.fss.portal.o2.com/"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:complexType name="arrayList">
xs:complexContent
<xs:extension base="ns1:abstractList"
xmlns:ns1="http://impl.service.webservice.fss.portal.o2.com/">
xs:sequence/
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="abstractList" abstract="true">
xs:complexContent
<xs:extension base="ns2:abstractCollection"
xmlns:ns2="http://impl.service.webservice.fss.portal.o2.com/">
xs:sequence/
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="abstractCollection" abstract="true"/>
</xs:schema>
Not to mention the little too complex structure, I'm missing the xsd:string
inside the xs:sequence from the service call.
Greets,
Chris
Operating System: All
Platform: All
[current]
Although mentioned elsewhere
http://forums.java.net/jive/thread.jspa?threadID=1706&tstart=255 I haven't
managed to discover exactly why type substitution is supported by JAXB 2.0 using
the artifacts generated by wsimport, but not when using JAXWS generated
service/port stubs.
My WSDL defines two complexTypes, MyBaseType and MyDerivedType which extends
MyBaseType by restriction. A method takes an element of type="MyBaseType" which
I want to specialize each on each call.
Using classes generated by wsimport, JAXB adds the xsi:type="MyDerivedType" tag
to my specialized calls, where JAXWS does not - and only marshalls the
MyBaseType properties; ignoring the additional properties defined in MyDerivedType.
Is this a bug with JAXWS or an issue introduced when introducing the SOAP
bindings? I can supply examples if neccessary.
Operating System: All
Platform: All
[current]
Hi,
im getting NPE in WS implementation.
@resource
private WebServiceContext wsContext;
public void serv()
{ for(String s : wsContext.getMessageContext().keySet()) System.out.println(s); }
this WS method, when called will throw NPE:
[java] java.lang.NullPointerException
[java] at java.util.AbstractMap$1$1.hasNext(AbstractMap.java:379)
WBR,
Alexey.
Operating System: All
Platform: All
[2.0.1 Early Access]
We have the following situation:
The problem:
wsimport makes several rounds creating the java value and service classes. This
takes a lot of time and needs a lot of memory in case of a larger wsdl/xsd
In our case, we have currently 50 services in one wsdl. The wsimport takes about
5 to ten minutes, and causes an OutOfMemoryException if we don't raise the heap
size with -Xmx to 512m. The exception is raised after dozens of rounds.
I've attached a smaller example with two services both using the type "myType"
from the schema in their response messages.
The verbose output from wsimport shows that 4 rounds are made
org\example\multiparse\Multiparse.java
org\example\multiparse\Multiparse_Service.java
org\example\multiparse_schema\MyType.java
org\example\multiparse_schema\ObjectFactory.java
org\example\multiparse_schema\package-info.java
org\example\multiparse\Multiparse.java
org\example\multiparse\Multiparse2.java
org\example\multiparse\Multiparse2_Service.java
org\example\multiparse\Multiparse_Service.java
org\example\multiparse_schema\MyType.java
org\example\multiparse_schema\ObjectFactory.java
org\example\multiparse_schema\package-info.java
org\example\multiparse\Multiparse.java
org\example\multiparse\Multiparse2.java
org\example\multiparse\Multiparse2_Service.java
org\example\multiparse\Multiparse_Service.java
org\example\multiparse_schema\MyType.java
org\example\multiparse_schema\ObjectFactory.java
org\example\multiparse_schema\package-info.java
org\example\multiparse\Multiparse.java
org\example\multiparse\Multiparse2.java
org\example\multiparse\Multiparse2_Service.java
org\example\multiparse\Multiparse_Service.java
org\example\multiparse_schema\MyType.java
org\example\multiparse_schema\ObjectFactory.java
org\example\multiparse_schema\package-info.java
Operating System: All
Platform: All
[current]
At least annotations, async, but maybe all other samples contains invalid
web.xml. See attached diff for difference between valid and invalid web.xml for
annotations sample.
Operating System: All
Platform: All
[2.0 FCS]
During extending JAX-WS SI, I found that the following patches were extremely helpful (and actually
necessary for my work). Could you consider adopting them?
Thanks,
Ias
====
RCS file: /cvs/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/handler/HandlerChainsModel.java,v
retrieving revision 1.4
diff -u -r1.4 HandlerChainsModel.java
— rt/src/com/sun/xml/ws/handler/HandlerChainsModel.java
29 Mar 2006 03:07:34 -0000 1.4
+++ rt/src/com/sun/xml/ws/handler/HandlerChainsModel.java
4 Apr 2006 11:22:08 -0000
@@ -334,7 +334,7 @@
}
static Class loadClass(ClassLoader loader, String name) {
static void callHandlerPostConstruct(Object handlerClass) {
static void skipChain(XMLStreamReader reader) {
static void skipTextElement(XMLStreamReader reader) {
static void skipInitParamElement(XMLStreamReader reader) {
static void ensureProperName(XMLStreamReader reader,
if (!reader.getName().equals(expectedName)) {
@@ -438,7 +438,7 @@
new QName(NS_109, "soap-header");
public static final QName QNAME_HANDLER_ROLE =
new QName(NS_109, "soap-role");
protected static final Map<String,String> tokenBindingMap;
static class HandlerChainTypeUnknown macro: {+ public static class HandlerChainType { //constraints protected QName serviceNamePattern; protected QName portNamePattern; @@ -518,7 +518,7 @@ } }
static class HandlerTypeUnknown macro: {+ public static class HandlerType { protected String handlerName; protected String handlerClass; protected List soapRoles; @@ -559,5 +559,9 @@ } return this.soapRoles; }
{ + return annotatedClass; }
====
RCS file: /cvs/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/server/RuntimeEndpointInfo.java,v
retrieving revision 1.80
diff -u -r1.80 RuntimeEndpointInfo.java
Provider endpoint validation
*/
private void checkProvider() {
);
@@ -835,6 +835,10 @@
public ProviderModel getProviderModel()
{ return providerModel; + }
{ + this.deployed = deployed; }
====
RCS file: /cvs/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/util/
HandlerAnnotationProcessor.java,v
retrieving revision 1.23
diff -u -r1.23 HandlerAnnotationProcessor.java
— rt/src/com/sun/xml/ws/util/HandlerAnnotationProcessor.java
18 Mar 2006 00:40:41 -0000 1.23
+++ rt/src/com/sun/xml/ws/util/HandlerAnnotationProcessor.java
4 Apr 2006 11:22:08 -0000
@@ -130,7 +130,7 @@
}
}
static Class getSEI(Class clazz) {
static InputStream getFileAsStream(Class clazz, HandlerChain chain) {
Operating System: All
Platform: All
[current]
Hi,
i need some mechanism to resolve WSDL's endpoint address (URI) for non-http port.
Currently i can propose following solution.
As WSDL is being retrieved by client via HTTP and taking in to account specific
of custom transport Adapter creating at runtime (currently in JBI and SOAP/TCP
custom transport Adapter is created on base of HttpAdapter). Seems it make sense
to register custom endpoint address resolvers in HttpAdapter.
can propose following interface in HttpAdapter:
void register(QName bindingTransport, CustomAddressResolver resolver);
void release(QName bindingTransport);
interface CustomAddressResolver could have one method:
String resolve(com.sun.xml.ws.api.model.wsdl.WSDLPort port);
which will return full URI address of endpoint.
Operating System: All
Platform: All
[2.0.1 Early Access]
Cannot import WSDL with array types defined.
Environment:
JAX-WS RI 2.0_01-b59-fcs
java version "1.5.0_06"
Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode, sharing)
Bug description:
When trying to import (wsimport.bat command) WSDL that makes use of
soapenc:Array (see attached file: PriceListService.wsdl) the following error is
produced:
warning: src-resolve.4.2: Error resolving component 'soapenc:Array'. It was
detected that 'soapenc:Array' is in namespace
'http://schemas.xmlsoap.org/soap/encoding/', but components from this namespace
are not referenceable from schema document
'file:/C:/jdk5/jaxws-ri/bin/PriceListService.wsdl#types?schema1'. If this is the
incorrect namespace, perhaps the prefix of 'soapenc:Array' needs to be changed.
If this is the correct namespace, then an appropriate 'import' tag should
be added to 'file:/C:/jdk5/jaxws-ri/bin/PriceListService.wsdl#types?schema1'.
line ? of file:/C:/jdk5/jaxws-ri/bin/PriceListService.wsdl#types?schema1
error: undefined simple or complex type 'soapenc:Array'
line 0 of file:/C:/jdk5/jaxws-ri/bin/PriceListService.wsdl#types?schema1
error: undefined attribute 'soapenc:arrayType'
line 0 of file:/C:/jdk5/jaxws-ri/bin/PriceListService.wsdl#types?schema1
error: undefined simple or complex type 'soapenc:Array'
line 0 of file:/C:/jdk5/jaxws-ri/bin/PriceListService.wsdl#types?schema1
error: undefined attribute 'soapenc:arrayType'
line 0 of file:/C:/jdk5/jaxws-ri/bin/PriceListService.wsdl#types?schema1
Steps to reproduce the error:
1. Save attached file PriceListService.wsdl localy
2. run:
wsimport.bat PriceListService.wsdl
Adding
does not resolve the problem. Nor does local XSD file put via catalog feature.
Please note that e.g. Apache Axis 1.4 properly imports this WSDL, producing the
following code entry:
public double[] getPriceList(String[] sku_list)
Operating System: All
Platform: All
[current]
Download of JAXWS_SI_20051114.jar
Deployment of a WebService in bundled HttpServer (com.sun.httpserver).
Basic Authentication enabled thanks to BasicAuthFilter.
WebServiceContext.getPrincipal returns null
Operating System: All
Platform: Sun
[current]
Hi,
I am tring to use JAX-WS 2.0.1 implementation to test RESTful Web Service.
In spite of using the following client code, JAX-WS 2.0.1 always makes a POST
request.
Dispatch
Service.Mode.MESSAGE);
Map<String, Object> requestContext = dispatcher.getRequestContext();
requestContext.put(MessageContext.HTTP_REQUEST_METHOD, "GET");
Source result = dispatcher.invoke(null);
I got the client code
from "http://java.sun.com/developer/technicalArticles/WebServices/restful/".
Besides, this reqeust cause XMLStreamException in server-side because a GET
request has no body content,
that is, the number of bytes that can be read from request input stream is 0.
XML reader error: javax.xml.stream.XMLStreamException: ParseError at [row,col]:
[1,1]
Message: Premature end of file.
at com.sun.xml.ws.streaming.XMLStreamReaderUtil.wrapException
(XMLStreamReaderUtil.java:246)
at com.sun.xml.ws.streaming.XMLStreamReaderUtil.next
(XMLStreamReaderUtil.java:70)
at com.sun.xml.ws.message.source.PayloadSourceMessage.
(PayloadSourceMessage.java:58)
at com.sun.xml.ws.message.source.PayloadSourceMessage.
(PayloadSourceMessage.java:63)
at com.sun.xml.ws.api.message.Messages.createUsingPayload
(Messages.java:137)
at com.sun.xml.ws.encoding.xml.XMLCodec.decode(XMLCodec.java:57)
at com.sun.xml.ws.encoding.XMLHTTPBindingCodec.decode
(XMLHTTPBindingCodec.java:191)
Thanks.
Operating System: All
Platform: All
[2.0.1 Early Access]
Using JAXWS_SI_20051213.jar, JDK 1.5.0_06-b05, Solaris 9.
I have a jaxws 2.0 client sending requests to a jaxws 2.0 server. Iam using
bundled HTTP server.
In a random way, some requests are failing. It seems that the server is faulting
(see stacks attached).
The client is sending a request but never receives a result. It throws an
exception (HTTP Status-Code 400: Bad Request) when checking the result code. I
think that the client is doing the right job.
The server, when receiving the request :
[java] FINER:
[java] Dec 14, 2005 3:01:12 PM
com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher receive
[java] SEVERE: null
[java] java.lang.NullPointerException
[java] at
sun.net.httpserver.ChunkedOutputStream.close(ChunkedOutputStream.java:116)
[java] at
sun.net.httpserver.PlaceholderOutputStream.close(ExchangeImpl.java:333)
[java] at
com.sun.xml.ws.transport.http.server.ServerConnectionImpl.closeOutput(ServerConnectionImpl.java:126)
[java] at
com.sun.xml.ws.util.SOAPConnectionUtil.sendKnownError(SOAPConnectionUtil.java:120)
[java] at
com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher.receive(SOAPMessageDispatcher.java:102)
[java] at com.sun.xml.ws.server.Tie.handle(Tie.java:88)
[java] at
com.sun.xml.ws.transport.http.server.WSHttpHandler.process(WSHttpHandler.java:129)
[java] at
com.sun.xml.ws.transport.http.server.WSHttpHandler.handle(WSHttpHandler.java:92)
[java] at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:65)
[java] at sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:459)
[java] at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
[java] at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
[java] at java.lang.Thread.run(Thread.java:595)
[java] java.lang.NullPointerException
[java] at
sun.net.httpserver.ChunkedOutputStream.close(ChunkedOutputStream.java:116)
[java] at
sun.net.httpserver.PlaceholderOutputStream.close(ExchangeImpl.java:333)
[java] at
com.sun.xml.ws.transport.http.server.ServerConnectionImpl.closeOutput(ServerConnectionImpl.java:126)
[java] at
com.sun.xml.ws.util.SOAPConnectionUtil.sendKnownError(SOAPConnectionUtil.java:120)
[java] at
com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher.receive(SOAPMessageDispatcher.java:102)
[java] at com.sun.xml.ws.server.Tie.handle(Tie.java:88)
[java] at
com.sun.xml.ws.transport.http.server.WSHttpHandler.process(WSHttpHandler.java:129)
[java] at
com.sun.xml.ws.transport.http.server.WSHttpHandler.handle(WSHttpHandler.java:92)
[java] at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:65)
[java] at sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:459)
[java] at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
[java] at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
[java] at java.lang.Thread.run(Thread.java:595)
[java] javax.xml.ws.WebServiceException: javax.xml.ws.WebServiceException:
sun.net.httpserver.StreamClosedException
[java] at
com.sun.xml.ws.util.SOAPConnectionUtil.sendResponseError(SOAPConnectionUtil.java:169)
[java] at
com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher.sendResponseError(SOAPMessageDispatcher.java:340)
[java] at
com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher.receive(SOAPMessageDispatcher.java:156)
[java] at com.sun.xml.ws.server.Tie.handle(Tie.java:88)
[java] at
com.sun.xml.ws.transport.http.server.WSHttpHandler.process(WSHttpHandler.java:129)
[java] at
com.sun.xml.ws.transport.http.server.WSHttpHandler.handle(WSHttpHandler.java:92)
[java] at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:65)
[java] at sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:459)
[java] at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
[java] at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
[java] at java.lang.Thread.run(Thread.java:595)
[java] Caused by: javax.xml.ws.WebServiceException:
sun.net.httpserver.StreamClosedException
[java] at
com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:107)
[java] at
com.sun.xml.ws.util.SOAPConnectionUtil.sendResponseError(SOAPConnectionUtil.java:167)
[java] ... 10 more
[java] Caused by: sun.net.httpserver.StreamClosedException
[java] at
sun.net.httpserver.ChunkedOutputStream.write(ChunkedOutputStream.java:62)
[java] at
sun.net.httpserver.PlaceholderOutputStream.write(ExchangeImpl.java:323)
[java] at
com.sun.xml.ws.transport.http.server.ServerConnectionImpl$NoCloseOutputStream.write(ServerConnectionImpl.java:256)
[java] at
com.sun.xml.messaging.saaj.soap.MessageImpl.writeTo(MessageImpl.java:1196)
[java] at
com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:104)
[java] ... 11 more
[java] java.nio.channels.ClosedChannelException
[java] at
sun.nio.ch.SocketChannelImpl.ensureReadOpen(SocketChannelImpl.java:112)
[java] at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:139)
[java] at sun.net.httpserver.Request$ReadStream.available(Request.java:270)
[java] at sun.net.httpserver.Request$ReadStream.read(Request.java:237)
[java] at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
[java] at java.io.BufferedInputStream.read1(BufferedInputStream.java:256)
[java] at java.io.BufferedInputStream.read(BufferedInputStream.java:313)
[java] at
sun.net.httpserver.FixedLengthInputStream.readImpl(FixedLengthInputStream.java:40)
[java] at
sun.net.httpserver.LeftOverInputStream.read(LeftOverInputStream.java:78)
[java] at java.io.FilterInputStream.read(FilterInputStream.java:90)
[java] at
com.sun.xml.ws.transport.http.server.ServerConnectionImpl$NoCloseInputStream.read(ServerConnectionImpl.java:197)
[java] at
com.sun.xml.ws.transport.http.server.ServerConnectionImpl.closeInput(ServerConnectionImpl.java:140)
[java] at
com.sun.xml.ws.transport.http.server.ServerConnectionImpl.close(ServerConnectionImpl.java:157)
[java] at
com.sun.xml.ws.transport.http.server.WSHttpHandler.process(WSHttpHandler.java:133)
[java] at
com.sun.xml.ws.transport.http.server.WSHttpHandler.handle(WSHttpHandler.java:92)
[java] at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:65)
[java] at sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:459)
[java] at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
[java] at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
[java] at java.lang.Thread.run(Thread.java:595)
[java] sun.net.httpserver.StreamClosedException
[java] at
sun.net.httpserver.ChunkedOutputStream.flush(ChunkedOutputStream.java:128)
[java] at
sun.net.httpserver.ChunkedOutputStream.close(ChunkedOutputStream.java:110)
[java] at
sun.net.httpserver.PlaceholderOutputStream.close(ExchangeImpl.java:333)
[java] at
com.sun.xml.ws.transport.http.server.ServerConnectionImpl.closeOutput(ServerConnectionImpl.java:126)
[java] at
com.sun.xml.ws.transport.http.server.ServerConnectionImpl.close(ServerConnectionImpl.java:163)
[java] at
com.sun.xml.ws.transport.http.server.WSHttpHandler.process(WSHttpHandler.java:133)
[java] at
com.sun.xml.ws.transport.http.server.WSHttpHandler.handle(WSHttpHandler.java:92)
[java] at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:65)
[java] at sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:459)
[java] at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
[java] at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
[java] at java.lang.Thread.run(Thread.java:595)
[java] java.io.IOException: Stream is closed
[java] at
sun.net.httpserver.FixedLengthInputStream.readImpl(FixedLengthInputStream.java:31)
[java] at
sun.net.httpserver.LeftOverInputStream.drain(LeftOverInputStream.java:91)
[java] at
sun.net.httpserver.LeftOverInputStream.close(LeftOverInputStream.java:48)
[java] at sun.net.httpserver.ExchangeImpl.close(ExchangeImpl.java:85)
[java] at
sun.net.httpserver.HttpExchangeImpl.close(HttpExchangeImpl.java:49)
[java] at
com.sun.xml.ws.transport.http.server.ServerConnectionImpl.close(ServerConnectionImpl.java:167)
[java] at
com.sun.xml.ws.transport.http.server.WSHttpHandler.process(WSHttpHandler.java:133)
[java] at
com.sun.xml.ws.transport.http.server.WSHttpHandler.handle(WSHttpHandler.java:92)
[java] at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:65)
[java] at sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:459)
[java] at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
[java] at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
[java] at java.lang.Thread.run(Thread.java:595)
[java] Dec 14, 2005 3:10:08 PM
com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher receive
[java] SEVERE: java.io.IOException: Broken pipe
[java] javax.xml.ws.WebServiceException: java.io.IOException: Broken pipe
[java] at
com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:107)
[java] at
com.sun.xml.ws.util.SOAPConnectionUtil.sendResponse(SOAPConnectionUtil.java:113)
[java] at
com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher.sendResponse(SOAPMessageDispatcher.java:328)
[java] at
com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher.receive(SOAPMessageDispatcher.java:152)
[java] at com.sun.xml.ws.server.Tie.handle(Tie.java:88)
[java] at
com.sun.xml.ws.transport.http.server.WSHttpHandler.process(WSHttpHandler.java:129)
[java] at
com.sun.xml.ws.transport.http.server.WSHttpHandler.handle(WSHttpHandler.java:92)
[java] at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:65)
[java] at sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:459)
[java] at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
[java] at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
[java] at java.lang.Thread.run(Thread.java:595)
[java] Caused by: java.io.IOException: Broken pipe
[java] at sun.nio.ch.FileDispatcher.write0(Native Method)
[java] at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:29)
[java] at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:104)
[java] at sun.nio.ch.IOUtil.write(IOUtil.java:75)
[java] at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:302)
[java] at sun.net.httpserver.Request$WriteStream.write(Request.java:374)
[java] at
sun.net.httpserver.FixedLengthOutputStream.write(FixedLengthOutputStream.java:53)
[java] at
sun.net.httpserver.PlaceholderOutputStream.write(ExchangeImpl.java:323)
[java] at
com.sun.xml.ws.transport.http.server.ServerConnectionImpl$NoCloseOutputStream.write(ServerConnectionImpl.java:256)
[java] at
com.sun.xml.messaging.saaj.soap.MessageImpl.writeTo(MessageImpl.java:1196)
[java] at
com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:104)
[java] ... 11 more
[java] javax.xml.ws.WebServiceException: java.io.IOException: Broken pipe
[java] at
com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:107)
[java] at
com.sun.xml.ws.util.SOAPConnectionUtil.sendResponse(SOAPConnectionUtil.java:113)
[java] at
com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher.sendResponse(SOAPMessageDispatcher.java:328)
[java] at
com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher.receive(SOAPMessageDispatcher.java:152)
[java] at com.sun.xml.ws.server.Tie.handle(Tie.java:88)
[java] at
com.sun.xml.ws.transport.http.server.WSHttpHandler.process(WSHttpHandler.java:129)
[java] at
com.sun.xml.ws.transport.http.server.WSHttpHandler.handle(WSHttpHandler.java:92)
[java] at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:65)
[java] at sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:459)
[java] at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
[java] at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
[java] at java.lang.Thread.run(Thread.java:595)
[java] Caused by: java.io.IOException: Broken pipe
[java] at sun.nio.ch.FileDispatcher.write0(Native Method)
[java] at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:29)
[java] at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:104)
[java] at sun.nio.ch.IOUtil.write(IOUtil.java:75)
[java] at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:302)
[java] at sun.net.httpserver.Request$WriteStream.write(Request.java:374)
[java] at
sun.net.httpserver.FixedLengthOutputStream.write(FixedLengthOutputStream.java:53)
[java] at
sun.net.httpserver.PlaceholderOutputStream.write(ExchangeImpl.java:323)
[java] at
com.sun.xml.ws.transport.http.server.ServerConnectionImpl$NoCloseOutputStream.write(ServerConnectionImpl.java:256)
[java] at
com.sun.xml.messaging.saaj.soap.MessageImpl.writeTo(MessageImpl.java:1196)
[java] at
com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:104)
[java] ... 11 more
[java] javax.xml.ws.WebServiceException: javax.xml.ws.WebServiceException:
java.io.IOException: Broken pipe
[java] at
com.sun.xml.ws.util.SOAPConnectionUtil.sendResponseError(SOAPConnectionUtil.java:169)
[java] at
com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher.sendResponseError(SOAPMessageDispatcher.java:340)
[java] at
com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher.receive(SOAPMessageDispatcher.java:156)
[java] at com.sun.xml.ws.server.Tie.handle(Tie.java:88)
[java] at
com.sun.xml.ws.transport.http.server.WSHttpHandler.process(WSHttpHandler.java:129)
[java] at
com.sun.xml.ws.transport.http.server.WSHttpHandler.handle(WSHttpHandler.java:92)
[java] at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:65)
[java] at sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:459)
[java] at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
[java] at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
[java] at java.lang.Thread.run(Thread.java:595)
[java] Caused by: javax.xml.ws.WebServiceException: java.io.IOException:
Broken pipe
[java] at
com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:107)
[java] at
com.sun.xml.ws.util.SOAPConnectionUtil.sendResponseError(SOAPConnectionUtil.java:167)
[java] ... 10 more
[java] Caused by: java.io.IOException: Broken pipe
[java] at sun.nio.ch.FileDispatcher.write0(Native Method)
[java] at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:29)
[java] at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:104)
[java] at sun.nio.ch.IOUtil.write(IOUtil.java:75)
[java] at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:302)
[java] at sun.net.httpserver.Request$WriteStream.write(Request.java:374)
[java] at
sun.net.httpserver.FixedLengthOutputStream.write(FixedLengthOutputStream.java:53)
[java] at
sun.net.httpserver.PlaceholderOutputStream.write(ExchangeImpl.java:323)
[java] at
com.sun.xml.ws.transport.http.server.ServerConnectionImpl$NoCloseOutputStream.write(ServerConnectionImpl.java:256)
[java] at
com.sun.xml.messaging.saaj.soap.MessageImpl.writeTo(MessageImpl.java:1196)
[java] at
com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:104)
[java] ... 11 more
[java] java.io.IOException: insufficient bytes written to stream
[java] at
sun.net.httpserver.FixedLengthOutputStream.close(FixedLengthOutputStream.java:60)
[java] at
sun.net.httpserver.PlaceholderOutputStream.close(ExchangeImpl.java:333)
[java] at
com.sun.xml.ws.transport.http.server.ServerConnectionImpl.closeOutput(ServerConnectionImpl.java:126)
[java] at
com.sun.xml.ws.transport.http.server.ServerConnectionImpl.close(ServerConnectionImpl.java:163)
[java] at
com.sun.xml.ws.transport.http.server.WSHttpHandler.process(WSHttpHandler.java:133)
[java] at
com.sun.xml.ws.transport.http.server.WSHttpHandler.handle(WSHttpHandler.java:92)
[java] at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:65)
[java] at sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:459)
[java] at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
[java] at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
[java] at java.lang.Thread.run(Thread.java:595)
[java] java.io.IOException: insufficient bytes written to stream
[java] at
sun.net.httpserver.FixedLengthOutputStream.close(FixedLengthOutputStream.java:60)
[java] at
sun.net.httpserver.PlaceholderOutputStream.close(ExchangeImpl.java:333)
[java] at sun.net.httpserver.ExchangeImpl.close(ExchangeImpl.java:88)
[java] at
sun.net.httpserver.HttpExchangeImpl.close(HttpExchangeImpl.java:49)
[java] at
com.sun.xml.ws.transport.http.server.ServerConnectionImpl.close(ServerConnectionImpl.java:167)
[java] at
com.sun.xml.ws.transport.http.server.WSHttpHandler.process(WSHttpHandler.java:133)
[java] at
com.sun.xml.ws.transport.http.server.WSHttpHandler.handle(WSHttpHandler.java:92)
[java] at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:65)
[java] at sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:459)
[java] at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
[java] at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
[java] at java.lang.Thread.run(Thread.java:595)
Operating System: All
Platform: Sun
[current]
"wsgen helloservice.endpoint.Hello" (or using the ant task with keep="false")
leaves source files in the jaxws subfolder regardless of whether or not you
specify "-keep". It seems generated source files are never added to the
generatedFiles List in ProcessorEnvironment.
see also: http://forums.java.net/jive/thread.jspa?forumID=46&threadID=16150
Operating System: All
Platform: All
[current]
vivekp imported this issue from https://jax-ws-sources.dev.java.net/issues/show_bug.cgi?id=1
Issue state when exported:
Assigned to: issues@jax-ws-sources
Component: jax-ws-sources
[Issue creation]: 2005-07-20 08:15:48
Last changed date: 20050808141358
URL:
Issue #: 1
Status: NEW
Issue type: DEFECT
Keywords:
OS/Version: All
Priority: P3
QA contact: issues@jax-ws-sources
Platform: All
Reported by: arungupta
Resolution:
Summary: missing cvs email notifications
Status whiteboard:
Subcomponent: www
Target milestone: milestone 1
Version: current
Votes:
------- Additional comments from [email protected] Wed Jul 20 15:15:48 +0000 2005 -------
jax-ws-sources developers have been experiencing missing cvs email notifications
when commits are made. This issue is created to better collect the data need to
solve the problem.
Please copy below and add comment with answers.
------- Additional comments from [email protected] Wed Jul 20 15:16:52 +0000 2005 -------
glassfish is also experiencing similar problems. See
https://glassfish.dev.java.net/issues/show_bug.cgi?id=10 for details.
------- Additional comments from [email protected] Wed Jul 20 15:26:06 +0000 2005 -------
User
arungupta
date/time of incident
Jul 19, 2005, 1:30pm
list of files checked in and not notified or just link to the cvs mail
message in archive
https://jax-ws-sources.dev.java.net/servlets/ReadMsg?list=cvs&msgNo=614
file sizes
multiple files
cvs client used
WinCVS 1.2
does this happen every time you commit?
No, intermittently
are there any error messages generated (check your junk filters to ensure
there are no bounced messages or probes sent)
No
------- Additional comments from [email protected] Wed Jul 20 15:28:25 +0000 2005 -------
User
arungupta
date/time of incident
Jul 18, approx 6:00pm
list of files checked in and not notified or just link to the cvs mail
message in archive
https://jax-ws-sources.dev.java.net/servlets/ReadMsg?list=cvs&msgNo=611
file sizes
multiple files
cvs client used
WinCVS 1.2
does this happen every time you commit?
No, intermittently
are there any error messages generated (check your junk filters to ensure
there are no bounced messages or probes sent)
No
------- Additional comments from [email protected] Wed Jul 20 19:00:17 +0000 2005 -------
I'm on the team with Arun. In case it helps, I did receive a commit email for
version 1.4 of this putback:
But not for his other commits, including v1.5 of the same file. So I did receive
an email for the commit at 2005-07-19 18:18:05+0000 but not the same file at
20:41:25+0000.
------- Additional comments from [email protected] Fri Jul 22 23:43:22 +0000 2005 -------
User
arungupta
date/time of incident
Jul 22, 2005, 4:00pm
list of files checked in and not notified or just link to the cvs mail
message in archive
Does not exist yet, but if it does make it to archive then would be
https://jax-ws-sources.dev.java.net/servlets/ReadMsg?list=cvs&msgNo=677
file sizes
multiple files
cvs client used
WinCVS 1.2
does this happen every time you commit?
No, intermittently
are there any error messages generated (check your junk filters to ensure
there are no bounced messages or probes sent)
No
------- Additional comments from [email protected] Mon Jul 25 12:57:39 +0000 2005 -------
I am also on the team with Arun gupta and bbissett and have experienced the same
issues as they have- with the same details. In addition, I have made updates and
checked in code changes to the jax-ws-sources repository, committed them,but the
changes never made it into the jax-ws-sources code base. The latest incidence of
this occuring is:
— SOAPMessageDispatcher.java 22 Jul 2005 01:11:38 -0000 1.8
+++ SOAPMessageDispatcher.java 22 Jul 2005 21:26:22 -0000 1.9
@@ -1,5 +1,5 @@
/**
/*
@@ -413,7 +413,6 @@
decoder.toMessageInfo(im, messageInfo);
if (messageInfo.getMetaData(DispatchContext.DISPATCH_MESSAGE_MODE) ==
Service.Mode.MESSAGE)
{ - sm = decoder.toSOAPMessage(messageInfo); messageInfo.setResponse(sm); postReceiveAndDecodeHook(messageInfo); }
------- Additional comments from [email protected] Tue Jul 26 14:48:52 +0000 2005 -------
Received the email below today. We need to figure out
why the emails are bouncing – it looks like they are
at least being sent by java.net.
— begin —
Hi! This is the ezmlm program. I'm managing the
[email protected] mailing list.
Messages to you from the cvs mailing list seem to
have been bouncing. I've attached a copy of the first bounce
message I received.
If this message bounces too, I will send you a probe. If the probe bounces,
I will remove your address from the cvs mailing list,
without further notice.
I've kept a list of which messages from the cvs mailing list have
bounced from your address.
Copies of these messages may be in the archive.
To retrieve a set of messages 123-145 (a maximum of 100 per request),
send an empty message to:
[email protected]
To receive a subject and author list for the last 100 or so messages,
send an empty message to:
[email protected]
Here are the message numbers:
576
611
624
667
— Enclosed is a copy of the bounce message I received.
Return-Path: <>
Received: (qmail 23187 invoked from network); 14 Jul 2005 02:01:42 -0000
Received: from asmx1.sfo.collab.net (64.125.133.81)
by s006.sfo.collab.net with SMTP; 14 Jul 2005 02:01:42 -0000
Received: from brmea-mail-3.sun.com (brmea-mail-3.Sun.COM [192.18.98.34])
by asmx1.sfo.collab.net (8.12.8/8.12.8) with ESMTP id j6E21d1h016864
for cvs-return-576-robert.bissett=sun.com@jax-ws-sources.dev.java.net; Wed,
13 Jul 2005 19:01:39 -0700
Received: from sunmail2.sfbay.sun.com ([129.149.246.180])
by brmea-mail-3.sun.com (8.12.10/8.12.9) with ESMTP id j6E21dvU015392
for cvs-return-576-robert.bissett=sun.com@jax-ws-sources.dev.java.net; Wed,
13 Jul 2005 20:01:39 -0600 (MDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM
[129.149.246.28])
by sunmail2.sfbay.sun.com (8.11.7p1+Sun/8.11.7/ENSMAIL,v2.2) with ESMTP id
j6E21dq00707
for cvs-return-576-robert.bissett=sun.com@jax-ws-sources.dev.java.net; Wed,
13 Jul 2005 19:01:39 -0700 (PDT)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
nwk-avmta-1.sfbay.Sun.COM
(Sun Java System Messaging Server 6.2 (built Dec 2 2004))
id [email protected] for
cvs-return-576-robert.bissett=[email protected]; Wed,
13 Jul 2005 19:01:38 -0700 (PDT)
Received: from process-daemon.nwk-avmta-1.sfbay.Sun.COM by
nwk-avmta-1.sfbay.Sun.COM
(Sun Java System Messaging Server 6.2 (built Dec 2 2004))
id [email protected] for
cvs-return-576-robert.bissett=[email protected]; Wed,
13 Jul 2005 19:01:37 -0700 (PDT)
Received: from nwk-avmta-1.sfbay.Sun.COM
(Sun Java System Messaging Server 6.2 (built Dec 2 2004))
id [email protected]; Wed,
13 Jul 2005 19:01:37 -0700 (PDT)
Date: Wed, 13 Jul 2005 19:01:37 -0700 (PDT)
From: Internet Mail Delivery [email protected]
Subject: Delivery Notification: Delivery has failed
To: cvs-return-576-robert.bissett=[email protected]
Message-id: [email protected]
MIME-version: 1.0
Content-type: multipart/report;
boundary="Boundary_(ID_Qsb3tK+Hkb181gjC6YwRXw)"; report-type=delivery-status
X-PMX-Version: 5.0.1.144180
--Boundary_(ID_Qsb3tK+Hkb181gjC6YwRXw)
Content-type: text/plain; charset=us-ascii
Content-language: en-US
Content-transfer-encoding: 7BIT
This report relates to a message you sent with the following header fields:
Message-id: [email protected]
Date: Thu, 14 Jul 2005 02:01:31 +0000
From: [email protected]
To: [email protected]
Subject: CVS update:
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/binding/soap/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/client/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/client/dispatch/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/client/dispatch/impl/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/client/dispatch/impl/protocol/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/encoding/soap/internal/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/protocol/soap/client/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/protocol/soap/server/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/server/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/server/provider/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/transport/http/servlet/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/transport/local/client/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/util/
Your message cannot be delivered to the following recipients:
Recipient address: @sunmail2.sfbay.sun.com:[email protected]
Original address: [email protected]
Reason: SMTP transmission failure has occurred
Diagnostic code: smtp;554 5.3.5 Infinite loop in ruleset SubjectCheck, rule 2
Remote system: dns;sunmail2.sfbay.sun.com
(TCP|129.149.246.28|47922|129.149.246.180|25)
--Boundary_(ID_Qsb3tK+Hkb181gjC6YwRXw)
Content-type: message/delivery-status
Original-envelope-id: [email protected]
Reporting-MTA: dns;nwk-avmta-1.sfbay.Sun.COM (tcp-daemon)
Original-recipient: rfc822;[email protected]
Final-recipient: rfc822;@sunmail2.sfbay.sun.com:[email protected]
Action: failed
Status: 5.3.5 (SMTP transmission failure has occurred)
Remote-MTA: dns;sunmail2.sfbay.sun.com
(TCP|129.149.246.28|47922|129.149.246.180|25)
Diagnostic-code: smtp;554 5.3.5 Infinite loop in ruleset SubjectCheck, rule 2
--Boundary_(ID_Qsb3tK+Hkb181gjC6YwRXw)
Content-type: message/rfc822
Return-path: cvs-return-576-robert.bissett=sun.com@jax-ws-sources.dev.java.net
Received: from tcp-daemon.nwk-avmta-1.sfbay.Sun.COM by
nwk-avmta-1.sfbay.Sun.COM
(Sun Java System Messaging Server 6.2 (built Dec 2 2004))
id [email protected]; Wed,
13 Jul 2005 19:01:37 -0700 (PDT)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
nwk-avmta-1.sfbay.Sun.COM
(Sun Java System Messaging Server 6.2 (built Dec 2 2004))
id [email protected] for [email protected]
(ORCPT [email protected]); Wed, 13 Jul 2005 19:01:37 -0700 (PDT)
Received: from brmea-mail-1.sun.com ([129.147.5.31])
by nwk-avmta-1.sfbay.Sun.COM
(Sun Java System Messaging Server 6.2 (built Dec 2 2004))
with ESMTP id [email protected] for
[email protected] (ORCPT [email protected]); Wed,
13 Jul 2005 19:01:35 -0700 (PDT)
Received: from relay12.sun.com ([217.140.40.34])
by brmea-mail-1.sun.com (8.12.10/8.12.9) with ESMTP id j6E21YOW001892 for
[email protected]; Wed, 13 Jul 2005 20:01:34 -0600 (MDT)
Received: from mms11es.sun.com (mms11es.sun.com [160.41.223.14])
by relay12i.sun.com with ESMTP for [email protected]; Thu,
14 Jul 2005 02:01:34 +0000 (Z)
Received: from mms11bas.mms.eu.btsyntegra.com
(mms11bas.mms.eu.btsyntegra.com [217.140.40.10]) by mms11es.sun.com with ESMTP
for [email protected]; Thu, 14 Jul 2005 02:01:33 +0000 (Z)
Received: from dev.java.net (dev.java.net [64.125.133.206])
by relay11.sun.com for [email protected]; Thu,
14 Jul 2005 02:01:33 +0000 (Z)
Received: (qmail 22916 invoked by uid 5000); Thu, 14 Jul 2005 02:01:32 +0000
Received: (qmail 22903 invoked by uid 5000); Thu, 14 Jul 2005 02:01:31 +0000
Date: Thu, 14 Jul 2005 02:01:31 +0000
From: [email protected]
Subject: CVS update:
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/binding/soap/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/client/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/client/dispatch/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/client/dispatch/impl/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/client/dispatch/impl/protocol/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/encoding/soap/internal/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/protocol/soap/client/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/protocol/soap/server/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/server/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/server/provider/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/transport/http/servlet/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/transport/local/client/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/util/
Sender: cvs-return-576-robert.bissett=[email protected]
To: [email protected]
Reply-to: [email protected]
Message-id: [email protected]
MIME-version: 1.0
Content-type: TEXT/PLAIN
Content-transfer-encoding: 7BIT
Precedence: bulk
Delivered-to: mailing list [email protected]
X-PMX-Version: 5.0.1.144180
List-Post: <[email protected]>
List-Unsubscribe: <[email protected]>
List-Help: <[email protected]>
X-No-Archive: yes
User: arungupta
Date: 2005/07/13 19:01:31
Log:
[....]
— end —
------- Additional comments from [email protected] Mon Aug 1 17:00:27 +0000 2005 -------
Got this email today.
– start here –
Hi! This is the ezmlm program. I'm managing the
[email protected] mailing list.
Messages to you from the cvs mailing list seem to
have been bouncing. I've attached a copy of the first bounce
message I received.
If this message bounces too, I will send you a probe. If the probe bounces,
I will remove your address from the cvs mailing list,
without further notice.
I've kept a list of which messages from the cvs mailing list have
bounced from your address.
Copies of these messages may be in the archive.
To retrieve a set of messages 123-145 (a maximum of 100 per request),
send an empty message to:
[email protected]
To receive a subject and author list for the last 100 or so messages,
send an empty message to:
[email protected]
Here are the message numbers:
611
667
— Enclosed is a copy of the bounce message I received.
Return-Path: <>
Received: (qmail 18376 invoked from network); 19 Jul 2005 18:10:24 -0000
Received: from asmx1.sfo.collab.net (64.125.133.81)
by s006.sfo.collab.net with SMTP; 19 Jul 2005 18:10:24 -0000
Received: from brmea-mail-4.sun.com (brmea-mail-4.Sun.COM [192.18.98.36])
by asmx1.sfo.collab.net (8.12.8/8.12.8) with ESMTP id j6JIAMAi032567
for [email protected]; Tue, 19
Jul 2005 11:10:22 -0700
Received: from sunmail2.sfbay.sun.com ([129.149.246.180])
by brmea-mail-4.sun.com (8.12.10/8.12.9) with ESMTP id j6JIALr3012317
for [email protected]; Tue, 19
Jul 2005 12:10:21 -0600 (MDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM
[129.149.246.28])
by sunmail2.sfbay.sun.com (8.11.7p1+Sun/8.11.7/ENSMAIL,v2.2) with ESMTP id
j6JIALq25460
for [email protected]; Tue, 19
Jul 2005 11:10:21 -0700 (PDT)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
nwk-avmta-1.sfbay.Sun.COM
(Sun Java System Messaging Server 6.2 (built Dec 2 2004))
id [email protected] for
cvs-return-611-arun.gupta=[email protected]; Tue,
19 Jul 2005 11:10:21 -0700 (PDT)
Received: from process-daemon.nwk-avmta-1.sfbay.Sun.COM by
nwk-avmta-1.sfbay.Sun.COM
(Sun Java System Messaging Server 6.2 (built Dec 2 2004))
id [email protected] for
cvs-return-611-arun.gupta=[email protected]; Tue,
19 Jul 2005 11:10:19 -0700 (PDT)
Received: from nwk-avmta-1.sfbay.Sun.COM
(Sun Java System Messaging Server 6.2 (built Dec 2 2004))
id [email protected]; Tue,
19 Jul 2005 11:10:19 -0700 (PDT)
Date: Tue, 19 Jul 2005 11:10:19 -0700 (PDT)
From: Internet Mail Delivery [email protected]
Subject: Delivery Notification: Delivery has failed
To: cvs-return-611-arun.gupta=[email protected]
Message-id: [email protected]
MIME-version: 1.0
Content-type: multipart/report;
boundary="Boundary_(ID_y04stgDuPbZIdBdca+P4Iw)"; report-type=delivery-status
X-PMX-Version: 5.0.1.144180
--Boundary_(ID_y04stgDuPbZIdBdca+P4Iw)
Content-type: text/plain; charset=us-ascii
Content-language: en-US
Content-transfer-encoding: 7BIT
This report relates to a message you sent with the following header fields:
Message-id: [email protected]
Date: Tue, 19 Jul 2005 18:10:10 +0000
From: [email protected]
To: [email protected]
Subject: CVS update: /jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/client/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/encoding/soap/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/protocol/soap/client/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/spi/runtime/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/transport/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/transport/http/client/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/transport/http/server/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/transport/http/servlet/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/transport/local/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/transport/local/client/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/transport/local/server/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/util/
Your message cannot be delivered to the following recipients:
Recipient address: @sunmail2.sfbay.sun.com:[email protected]
Original address: [email protected]
Reason: SMTP transmission failure has occurred
Diagnostic code: smtp;554 5.3.5 Infinite loop in ruleset SubjectCheck, rule 2
Remote system: dns;sunmail2.sfbay.sun.com
(TCP|129.149.246.28|44431|129.149.246.180|25)
--Boundary_(ID_y04stgDuPbZIdBdca+P4Iw)
Content-type: message/delivery-status
Original-envelope-id: [email protected]
Reporting-MTA: dns;nwk-avmta-1.sfbay.Sun.COM (tcp-daemon)
Original-recipient: rfc822;[email protected]
Final-recipient: rfc822;@sunmail2.sfbay.sun.com:[email protected]
Action: failed
Status: 5.3.5 (SMTP transmission failure has occurred)
Remote-MTA: dns;sunmail2.sfbay.sun.com
(TCP|129.149.246.28|44431|129.149.246.180|25)
Diagnostic-code: smtp;554 5.3.5 Infinite loop in ruleset SubjectCheck, rule 2
--Boundary_(ID_y04stgDuPbZIdBdca+P4Iw)
Content-type: message/rfc822
Return-path: [email protected]
Received: from tcp-daemon.nwk-avmta-1.sfbay.Sun.COM by
nwk-avmta-1.sfbay.Sun.COM
(Sun Java System Messaging Server 6.2 (built Dec 2 2004))
id [email protected]; Tue,
19 Jul 2005 11:10:19 -0700 (PDT)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
nwk-avmta-1.sfbay.Sun.COM
(Sun Java System Messaging Server 6.2 (built Dec 2 2004))
id [email protected] for [email protected]
(ORCPT [email protected]); Tue, 19 Jul 2005 11:10:18 -0700 (PDT)
Received: from brmea-mail-2.sun.com ([129.147.5.43])
by nwk-avmta-1.sfbay.Sun.COM
(Sun Java System Messaging Server 6.2 (built Dec 2 2004))
with ESMTP id [email protected] for
[email protected] (ORCPT [email protected]); Tue,
19 Jul 2005 11:10:17 -0700 (PDT)
Received: from relay13.sun.com ([217.140.40.54])
by brmea-mail-2.sun.com (8.12.10/8.12.9) with ESMTP id j6JIAFpO011463 for
[email protected]; Tue, 19 Jul 2005 12:10:15 -0600 (MDT)
Received: from mms13es.sun.com (mms13es.sun.com [160.41.223.54])
by relay13i.sun.com with ESMTP for [email protected]; Tue,
19 Jul 2005 18:10:14 +0000 (Z)
Received: from mms12bas.mms.eu.btsyntegra.com
(mms12bas.mms.eu.btsyntegra.com [217.140.40.30]) by mms13es.sun.com with ESMTP
for [email protected]; Tue, 19 Jul 2005 18:10:14 +0000 (Z)
Received: from dev.java.net (dev.java.net [64.125.133.206])
by relay12.sun.com for [email protected]; Tue, 19 Jul 2005 18:10:12 +0000 (Z)
Received: (qmail 18287 invoked by uid 5000); Tue, 19 Jul 2005 18:10:11 +0000
Received: (qmail 18274 invoked by uid 5000); Tue, 19 Jul 2005 18:10:10 +0000
Date: Tue, 19 Jul 2005 18:10:10 +0000
From: [email protected]
Subject: CVS update: /jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/client/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/encoding/soap/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/protocol/soap/client/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/spi/runtime/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/transport/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/transport/http/client/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/transport/http/server/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/transport/http/servlet/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/transport/local/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/transport/local/client/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/transport/local/server/,
/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/util/
Sender: cvs-return-611-arun.gupta=[email protected]
To: [email protected]
Reply-to: [email protected]
Message-id: [email protected]
MIME-version: 1.0
Content-type: TEXT/PLAIN
Content-transfer-encoding: 7BIT
Precedence: bulk
Delivered-to: mailing list [email protected]
X-PMX-Version: 5.0.1.144180
List-Post: <[email protected]>
List-Unsubscribe: <[email protected]>
List-Help: <[email protected]>
X-No-Archive: yes
User: arungupta
Date: 2005/07/19 11:10:10
Log:
Now SOAPMessageDispatcher uses WSConnection to get the OutputStream to write
...
------- Additional comments from [email protected] Mon Aug 8 21:13:58 +0000 2005 -------
Lost another putback, archive notification and details at
https://jax-ws-sources.dev.java.net/servlets/ReadMsg?list=cvs&msgNo=803.
Operating System: All
Platform: All
[2.0 FCS]
[I've also posted this in the jwsdp issues list - apologies for the duplicate
but I'm not sure which level is the correct place]
I am unable to get a WS client built with JWSDP 2 to run in an applet. The
problem seems to be with the RuntimeModeler class loader, which I suspect is
falling foul of applet security constraints.
My service connector stub (as generated by wsimport) is
com.sage.cpd.uhb.SvcTest, and it fails calling the constructor - here's the
stack trace:
class: com.sage.cpd.uhb.Standard could not be found
at com.sun.xml.ws.modeler.RuntimeModeler.getClass(RuntimeModeler.java:269)
at com.sun.xml.ws.modeler.RuntimeModeler.processDocWrappedMethod
(RuntimeModeler.java:558)
at com.sun.xml.ws.modeler.RuntimeModeler.processMethod(RuntimeModeler.java:505)
at com.sun.xml.ws.modeler.RuntimeModeler.processClass(RuntimeModeler.java:353)
at com.sun.xml.ws.modeler.RuntimeModeler.buildRuntimeModel
(RuntimeModeler.java:249)
at com.sun.xml.ws.client.ServiceContextBuilder.processAnnotations
(ServiceContextBuilder.java:169)
at com.sun.xml.ws.client.ServiceContextBuilder.build
(ServiceContextBuilder.java:82)
at com.sun.xml.ws.client.WSServiceDelegate.(WSServiceDelegate.java:117)
at com.sun.xml.ws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:50)
at javax.xml.ws.Service.(Service.java:58)
at com.sage.cpd.uhb.SvcTest.(SvcTest.java:40)
at com.sage.cpd.Client.onLoad(Client.java:59)
...
"Standard" is one of the web service methods, and it clearly can't create its
corresponding class object. However, "new Standard()" works, so does
Class.forName("com.sage.cpd.uhb.Standard"), so it appears to be a constraint
applied to RuntimeModeler.
The applet jar is signed, as are all the other WS library jars loaded by the
applet. I had to sign all the jars to overcome an earlier problem, but this
problem remains.
Exactly the same code runs in a stand-alone application, so I assume it is an
applet security issue.
I believe this is a defect, I can't see that I'm doing anything wrong.
Operating System: Windows XP
Platform: All
[current]
HTTP Compression support is needed for content codings "gzip" and "deflate".
Operating System: All
Platform: All
[current]
I am using mtom with soap 1.1. When the server decodes an incoming message which
has been encoded with mtom, it throws an exception when unmarshalling the mime
subparts which where were created as part of the mtom encoding. See the stack
trace below.
Error in decoding SOAP Message
at
com.sun.xml.ws.encoding.soap.server.SOAPXMLDecoder.toInternalMessage(SOAPXMLDecoder.java:86)
at
com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher.toMessageInfo(SOAPMessageDispatcher.java:168)
at
com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher$SoapInvoker.invoke(SOAPMessageDispatcher.java:533)
at
com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher.receive(SOAPMessageDispatcher.java:140)
at com.sun.xml.ws.server.Tie.handle(Tie.java:88)
at
com.sun.xml.ws.transport.http.servlet.WSServletDelegate.handle(WSServletDelegate.java:279)
at
com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doPost(WSServletDelegate.java:232)
at com.sun.xml.ws.transport.http.servlet.WSServlet.doPost(WSServlet.java:77)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:667)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.IllegalArgumentException: Attachment corresponding to
cid:6c88999f-35ff-403b-83a4-afd86c2a5ac6@urn%3Aws.ssa.gov%2Fewr%2Fv1%2FWageFileServices
not found!
at
com.sun.xml.ws.encoding.JAXWSAttachmentUnmarshaller.getAttachmentAsDataHandler(JAXWSAttachmentUnmarshaller.java:58)
at
com.sun.xml.bind.v2.runtime.unmarshaller.MTOMDecorator.startElement(MTOMDecorator.java:60)
at
com.sun.xml.bind.v2.runtime.unmarshaller.StAXStreamConnector.handleStartElement(StAXStreamConnector.java:189)
at
com.sun.xml.bind.v2.runtime.unmarshaller.StAXStreamConnector.bridge(StAXStreamConnector.java:123)
at
com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:332)
at com.sun.xml.bind.v2.runtime.BridgeImpl.unmarshal(BridgeImpl.java:66)
at com.sun.xml.ws.encoding.jaxb.JAXBBridgeInfo.deserialize(JAXBBridgeInfo.java:137)
at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeBodyContent(SOAPDecoder.java:348)
at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeBody(SOAPDecoder.java:325)
at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeEnvelope(SOAPDecoder.java:248)
at
com.sun.xml.ws.encoding.soap.server.SOAPXMLDecoder.toInternalMessage(SOAPXMLDecoder.java:78)
... 23 more
I think I have tracked down the bug in the source code. Basically, the key used
to lookup the attachments is a String which is URL encoded but the attachments
map stores the keys in raw undecoded form.
com.sun.xml.ws.util.ASCIIUtility.JAXWSAttachmentUnmarshaller.getAttachmentAsDataHandler
Here is raw form of hte message that got sent from the jax-ws client:
POST /simulator-ssa/ssa HTTP/1.1
Content-Length: 971
SOAPAction: "submitWageFile"
Content-Type: Multipart/Related; type="application/xop+xml";
boundary="----=_Part_0_30284778.1152568700940"; start-info="text/xml"
Accept: text/xml, application/xop+xml, text/html, image/gif, image/jpeg, *;
q=.2, /; q=.2
User-Agent: Java/1.5.0_04
Host: localhost:8182
Connection: keep-alive
------=_Part_0_30284778.1152568700940
Content-Type: application/xop+xml; type="text/xml"; charset=utf-8
1234
-----=_Part_0_30284778.1152568700940-
The message I get back is:
HTTP/1.1 500 Internal Server Error
Server: Apache-Coyote/1.1
Set-Cookie: JSESSIONID=07F688459143BE853E928D342FE561B7; Path=/simulator-ssa
Content-Type: text/xml;charset=utf-8
Content-Length: 521
Date: Mon, 10 Jul 2006 22:01:28 GMT
Connection: close
Operating System: All
Platform: All
[2.0 FCS]
I have a method that takes an returns the same class.
@webresult(name="RI", targetNamespace="http://RI")
public RIType process(@WebParam(name="RI", targetNamespace="http://RI") RIType
input)
{ ... }
The problem is that an invalid WSDL is generated that repeats the element
declaration in the same schema file:
<xs:element xmlns:ns3="http://RI" type="ns3:RI" name="RI"></xs:element>
<xs:element xmlns:ns4="http://RI" type="ns4:RI" name="RI"></xs:element>
Operating System: All
Platform: All
[2.0 FCS]
In case a Port name (according to WSDL Spec Section 2.6) is the same as the
enclosing Service name (according to WSDL Spec Section 2.7) the error occurs:
"trying to create the same field twice"
How to reproduce:
In JAX-WS RI 2.0-b26-ea3 edit the following file:
jwsdp-2.0/jaxws/samples/wsimport_catalog/HelloService.wsdl
so that line 29 be:
and run wsimport tool:
wsimport.bat HelloService.wsdl -catalog wsdlcatalog.xml -verbose
You'll receive:
java.lang.IllegalArgumentException: trying to create the same field twice:
HELLOSERVICE
at com.sun.codemodel.JDefinedClass.field(JDefinedClass.java:388)
at com.sun.codemodel.JDefinedClass.field(JDefinedClass.java:460)
at
com.sun.tools.ws.processor.generator.ServiceGenerator.visitService(ServiceGenerator.java:152)
at
com.sun.tools.ws.processor.generator.GeneratorBase.visit(GeneratorBase.java:181)
at com.sun.tools.ws.processor.model.Service.accept(Service.java:109)
at
com.sun.tools.ws.processor.generator.GeneratorBase.visitModel(GeneratorBase.java:172)
at
com.sun.tools.ws.processor.generator.GeneratorBase.visit(GeneratorBase.java:162)
at com.sun.tools.ws.processor.model.Model.accept(Model.java:126)
at
com.sun.tools.ws.processor.generator.GeneratorBase.doGeneration(GeneratorBase.java:152)
at
com.sun.tools.ws.processor.generator.GeneratorBase.perform(GeneratorBase.java:102)
at com.sun.tools.ws.processor.Processor.runActions(Processor.java:97)
at com.sun.tools.ws.wscompile.CompileTool.run(CompileTool.java:500)
at com.sun.tools.ws.util.ToolBase.run(ToolBase.java:54)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sun.tools.ws.Invoker.main(Invoker.java:41)
at com.sun.tools.ws.WsImport.main(WsImport.java:28)
Another way to reproduce it (in real life example) is:
wsimport.bat "https://api.betfair.com/betex-api-public-ws/v2/BFService.wsdl"
The same problem occurs with wsimport in JDK1.6.0beta (build 1.6.0-beta-b59g)
Operating System: Windows XP
Platform: All
[JAXWS 2.0 EA2]
Recategorizing this issue.
Operating System: All
Platform: All
[2.0 FCS]
When invoking RESTful web service by using Dispatcher, implementation below
works well on 2.0FCS, but 2.0.1EA ignores QUERY_STRING.
Dispatch
Service.Mode.PAYLOAD);
Map<String, Object> reqContext = d.getRequestContext();
reqContext.put(MessageContext.HTTP_REQUEST_METHOD, "GET");
reqContext.put(MessageContext.QUERY_STRING, "myparam");
Source result = d.invoke(null);
Operating System: All
Platform: All
[2.0.1 Early Access]
Having custom transport i need to participate in wsdl generation process:
generate transport specific bindings, form correct endpoint address.
Current implementation lets just add custom elements additionaly to standard
ones. to wsdl, but will not let to completely replace for ex. standard binding
generator with custom one.
Alexey.
Operating System: All
Platform: All
[2.0.1 Early Access]
'm trying to create a client-application using jax-ws for .Net based webservice
and have found some problems in the errorhandling.
This is the error message:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
soap:Body
soap:Fault
soap:Server
Server was unable to process request. ---> Not a valid account
number.
</soap:Fault>
</soap:Body>
</soap:Envelope>
Which causes the following exception:
Exception in thread "main" javax.xml.ws.WebServiceException: unexpected XML
reader state. expected: END_ELEMENT but found: CHARACTERS
The problem is as far I can see a bug in:
com.sun.xml.ws.encoding.soap.client.SOAPXMLDecoder.decodeFault
In the following section of the code:
String faultstring = null;
if (reader.getEventType() == CHARACTERS) {
faultstring = reader.getText();
XMLStreamReaderUtil.next(reader);
}
XMLStreamReaderUtil.verifyReaderState(reader, END_ELEMENT);
The last row generates an error because the XMLStreamReaderUtil treats the
escaped character (> as a new content.
I think the code should look like this:
String faultstring = null;
if (reader.getEventType() == CHARACTERS) {
faultstring = "";
while (reader.getEventType() == CHARACTERS)
{ faultstring += reader.getText(); XMLStreamReaderUtil.next(reader); } } XMLStreamReaderUtil.verifyReaderState(reader, END_ELEMENT); If I change the code to that there is another exception generated because of the empty Detail-tag: Caused by: unexpected XML tag. expected: {http://schemas.xmlsoap.org/soap/envelope/}
Fault but found:
{http://schemas.xmlsoap.org/soap/envelope/}
Body
at
com.sun.xml.ws.streaming.XMLStreamReaderUtil.verifyTag(XMLStreamReaderUtil.java:202)
Here I think that the error lies in:
com.sun.xml.ws.encoding.soap.client.SOAPXMLDecoder.decodeFaultDetail
in this part:
while (XMLStreamReaderUtil.nextContent(reader) == START_ELEMENT) {
trans.transform(new StAXSource(reader, true), new DOMResult(detail));
}
Since this automaticly moves the reader forward at least 1 step it will cause
the decoder to skip the end fault tag.
This code does however work for me:
if(reader.getEventType() != END_ELEMENT){
while (XMLStreamReaderUtil.nextContent(reader) == START_ELEMENT) {
trans.transform(new StAXSource(reader, true), new DOMResult(detail));
}
}
I'm rather new with using this component so I have don't know if those fixes
will cause other problems.
Kind Regards,
Rikard
Operating System: Windows XP
Platform: PC
[JAXWS 2.0 EA2]
When importing an external schema into a WSDL file using <xs:import
namespace="http://x/"/>, the namespace is not being resolved by the xml catalog.
See forum thread
http://forums.java.net/jive/thread.jspa?forumID=46&threadID=14088 for details.
Operating System: Windows XP
Platform: PC
[current]
I just wanted to alert everyone of some issues I ran into porting a JAX-WS web
application into Tomcat version 5.5.16 running on IBM's Java 5 VM on the AIX
o/s whose details are given below:
java version "1.5.0"
Java(TM) 2 Runtime Environment, Standard Edition (build pap32dev-20051104)
IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 AIX ppc-32 j9vmap3223-20051103 (JIT
enabled)
J9VM - 20051027_03723_bHdSMR
JIT - 20051027_1437_r8
GC - 20051020_AA)
JCL - 2005110
AIX Version (via uname -a command): AIX myAIX 2 5 00CA7ACE4C00
Porting Issues:
Workaround: I extracted Sun's implementation of Xerces from their rt.jar into
a new jar that I named sun-xerces.jar. I then placed this jar in my JAX-WS
application classpath (in this case via Tomcat's shared library directory) and
Sun's SAAJ implementation was then able to successfully parse and bind the SOAP
messages traversing the wire.
I hope everyone out there finds this post worthwhile. I have enjoyed the
fruits of the JAX-WS team's efforts and look forward to making it a key
architectural component of my web service solutions.
Sincerely,
Gene
Operating System: AIX
Platform: Other
[current]
Related to the following thread:
http://forums.java.net/jive/thread.jspa?messageID=132358𠔆
If I have a web service:
@webservice()
public class Foo {
private Bar bar=new Bar();
public Bar getBar()
{ return bar; }
}
where Bar=
public class Bar {
private List numbers=new ArrayList();
public Bar() {
}
public List getNumbers()
{ return numbers; }
public void setNumbers(List numbers)
{ this.numbers = numbers; }
}
Then wsgen fails to process Bar with the following error:
error: The type of the getter is java.util.List<java.lang.Integer> but that of
the setter is java.util.List. They have to be the same.
this problem is related to the following location:
at wsgenproblem.Bar.getNumbers (Unknown Source)
at wsgenproblem.Bar (Unknown Source)
at wsgenproblem.jaxws.GetBarResponse._return(GetBarResponse.java:17)
at wsgenproblem.jaxws.GetBarResponse(GetBarResponse.java:14)
this problem is related to the following location:
at wsgenproblem.Bar.setNumbers (Unknown Source)
at wsgenproblem.Bar (Unknown Source)
at wsgenproblem.jaxws.GetBarResponse._return(GetBarResponse.java:17)
at wsgenproblem.jaxws.GetBarResponse(GetBarResponse.java:14)
Operating System: All
Platform: All
[current]
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.