Re: [JBoss JIRA] Reopened: (JBWS-1609) Address in WSDL - Port value is -1 when server is requested with default port 80
by Thomas Diesler
Hi Magesh,
> Would this affect http://jira.jboss.com/jira/browse/JBWS-1472 too?
I don't know because there is no test case for JBWS-1472 AFAICS. Could
you please create one that documents and tests the intended behavior. I
reopend the issue.
It should be possible to keep the original behaviour which allowed the
address to be set in the WSDL and this address would always be returned
so the three required scenarios are: -
1 - Use the hostname specified in the -beans.xml.
2 - Use the hostname already in the WSDL.
3 - Use the hostname of the calling client.
On Wed, 2007-06-20 at 17:42 +0530, Magesh Kumar Bojan wrote:
> Would this affect http://jira.jboss.com/jira/browse/JBWS-1472 too?
>
> Thomas Diesler (JIRA) wrote:
> > [ http://jira.jboss.com/jira/browse/JBWS-1609?page=all ]
> >
> > Thomas Diesler reopened JBWS-1609:
> > ----------------------------------
> >
> >
> > The proposed solution binds concepts from the jbossws native stack to the general server config
> >
> >
> >> Address in WSDL - Port value is -1 when server is requested with default port 80
> >> --------------------------------------------------------------------------------
> >>
> >> Key: JBWS-1609
> >> URL: http://jira.jboss.com/jira/browse/JBWS-1609
> >> Project: JBoss Web Services
> >> Issue Type: Bug
> >> Security Level: Public(Everyone can see)
> >> Components: jbossws-jaxws
> >> Affects Versions: jbossws-1.2.0.SP1
> >> Environment: JBoss AS 4.0.5 running in port 80 and SSL port 443
> >> Reporter: Magesh Kumar B
> >> Assigned To: Magesh Kumar B
> >> Fix For: jbossws-2.0.0
> >>
> >> Time Spent: 2 days, 7 hours
> >> Remaining Estimate: 0 minutes
> >>
> >> When the server is running on default ports 80 the Webservices list and the WSDL URL shows the port as "-1" and when the SSL port 443 is used the Webservice list shows as "-1" and the WSDL URL shows as "http://jbossws.undefined.host:80"
> >>
> >
> >
>
>
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
17 years, 6 months
Re: Assigned jira issues
by Thomas Diesler
On Thu, 2007-06-14 at 16:29 -0400, David Boeren wrote:
> I've been working on the 1653 issue but without much success. I think I
> will need to transfer that case to you to have a look. I have the list
> of failed test cases down fairly low but each change I have tried either
> has no effect or creates new problems. I've been testing manually
> though as I have not figured out how to create a junit test which alters
> the default handler settings but does not impact other tests. Do you
> know of a way to accomplish this?
This can probably be done with a class loading trick.
>
> I will get on creating a test for the 1665 case as you requested. I
> thought the attached files which reproduced the error were sufficient
> for it to be worked on, but it this is not so I'll add it to junit.
It helps a great deal if you create the test yourself. You understand
the issue best. Hence you would be able to create a test case that
isolates the issue well. The test does not have to pass, instead it can
be disable with a FIXME.
When we have a test case (that documents itself well) it will be a lot
easier for us to help you out in case you get stuck.
cheers
-thomas
>
> Thomas Diesler wrote:
> > Hi David,
> >
> > currently there are two issus assigned to you for jbossws-2.0.0
> >
> > http://jira.jboss.org/jira/browse/JBWS-1653
> > http://jira.jboss.org/jira/browse/JBWS-1665
> >
> > Is this on your monitor?
> >
> > Code freeze is Fri,22-Jun-2007 at the latest.
> >
> > cheers
> > -thomas
> >
> >
>
17 years, 7 months
Re: Setting a property on the SerializationContext??
by Thomas Diesler
Please take this to the jbossws-dev forum. We will probably need more
context to give you a qualified answer
On Thu, 2007-06-14 at 16:05 +0100, Tom Fennelly wrote:
> Hi Thomas.
>
> Was just wondering was there a way to set an object on the
> SerializationContext before calling RequestHandler.handleRequest()? I
> don't see any reference to the SerializationContext on the
> InvocationContext, but perhaps there's a different way to get at it.
>
> Tom.
>
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
17 years, 7 months
Re: help with Seam integration
by Thomas Diesler
Hi Mark,
he would want to go to jbossws-dev(a)lists.jboss.org and/or create JIRA
issues for whatever issues there are. These are our high priority
support channels.
cheers
-thomas
On Thu, 2007-06-14 at 07:48 +0100, Mark Little wrote:
> Thomas, I think Shane is still having some problems generating EPRs
> with the necessary information in them for Seam sessions. We're always
> talking about getting more community to use JBossWS and Seam's use of
> JBossWS could well do that. Plus, if they do eventually move to
> JBossWS 2.1.0 then this would be an excellent point to use in any
> negotiations around the Sun RI or CXF. Could you find some time today
> to help Shane, or is there someone else on the team who could?
>
>
> Thanks,
>
>
> Mark.
>
> ----
>
>
> Mark Little
> mlittle(a)redhat.com
>
>
> JBoss, a Division of Red Hat
> Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
> Street, Windsor, Berkshire,
> SI4 1TE, United Kingdom.
> Registered in UK and Wales under Company Registration No. 3798903
> Directors: Michael Cunningham (USA), Charlie Peters (USA) and David
> Owens (Ireland)
>
>
>
>
>
>
>
>
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
17 years, 7 months
jmxconnector already bound in AS50
by Thomas Diesler
Folks,
There seems to be a problem with jmxconnector JNDI binding when two AS50
instances are bound to two differnt interfaces.
This is critical to us because our QA box cannot run two AS50 instances
any more (i.e. we can only do QA on one branch at a time)
cheers
-thomas
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
17 years, 7 months
[Design of JBoss Web Services] - wstools error in wsdl2java
by johnefranklin＠yahoo.com
Hi,
I am attaching a wsdl that used to work nicely with JBoss 4.0.5. But when I try to generate the java files from the wsdl using the wstools shipped along with JBoss 4.2, it keeps giving me this error.
Exception in thread "main" org.jboss.ws.WSException: [JAX-RPC 2.3.1.2] Unable to unwrap model group with multiple particles.
at org.jboss.ws.tools.helpers.ReturnTypeUnwrapper.unwrapModelGroup(ReturnTypeUnwrapper.java:120)
at org.jboss.ws.tools.helpers.ReturnTypeUnwrapper.unwrap(ReturnTypeUnwrapper.java:87)
at org.jboss.ws.tools.WSDLToJava.getReturnType(WSDLToJava.java:632)
at org.jboss.ws.tools.WSDLToJava.appendDocParameters(WSDLToJava.java:395)
at org.jboss.ws.tools.WSDLToJava.appendMethods(WSDLToJava.java:290)
at org.jboss.ws.tools.WSDLToJava.createSEIFile(WSDLToJava.java:588)
at org.jboss.ws.tools.WSDLToJava.createSEI(WSDLToJava.java:618)
at org.jboss.ws.tools.WSDLToJava.generateSEI(WSDLToJava.java:186)
at org.jboss.ws.tools.helpers.ToolsHelper.handleWSDLToJavaGeneration(ToolsHelper.java:303)
at org.jboss.ws.tools.WSTools.process(WSTools.java:137)
at org.jboss.ws.tools.WSTools.generate(WSTools.java:69)
at org.jboss.ws.tools.WSTools.generate(WSTools.java:119)
at org.jboss.ws.tools.WSTools.main(WSTools.java:58)
Can someone please look at the wsdl and point me the problem in the wsdl?
regards,
johnf
|
| <definitions name="EventMonitoringService" targetNamespace="http://com.ws.test/sample"
| xmlns="http://schemas.xmlsoap.org/wsdl/"
| xmlns:ns2="http://com.ws.test/sample"
| xmlns:tns="http://com.ws.test/sample/types"
| xmlns:xsd="http://www.w3.org/2001/XMLSchema"
| xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
| xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
| xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/">
| <types>
| <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
| targetNamespace="http://com.ws.test/sample/types"
| xmlns:tns="http://com.ws.test/sample/types">
|
| <xsd:simpleType name="DeviceID">
| <xsd:restriction base="xsd:string">
| <xsd:minLength value="0"/>
| </xsd:restriction>
| </xsd:simpleType>
|
| <xsd:complexType name="LogicalEvents">
| <xsd:sequence>
| <xsd:element name="logicalVar1" type="xsd:boolean" minOccurs="0"/>
| <xsd:element name="logicalVar2" type="xsd:boolean" minOccurs="0"/>
| </xsd:sequence>
| </xsd:complexType>
|
| <xsd:complexType name="PhysicalEvents">
| <xsd:sequence>
| <xsd:element name="physicalVar1" type="xsd:boolean" minOccurs="0"/>
| <xsd:element name="physicalVar2" type="xsd:boolean" minOccurs="0"/>
| </xsd:sequence>
| </xsd:complexType>
|
| <xsd:complexType name="FilterEvents">
| <xsd:sequence>
| <xsd:element name="physical" type="tns:PhysicalEvents" minOccurs="0"/>
| <xsd:element name="logical" type="tns:LogicalEvents" minOccurs="0"/>
| </xsd:sequence>
| </xsd:complexType>
|
| <xsd:simpleType name="ErrorValue">
| <xsd:restriction base="xsd:string">
| <xsd:minLength value="0"/>
| </xsd:restriction>
| </xsd:simpleType>
|
| <xsd:complexType name="TestException">
| <xsd:sequence>
| <xsd:element name="errorValue" type="tns:ErrorValue"/>
| <xsd:element name="errorMessage" type="xsd:string" nillable="true"/>
| </xsd:sequence>
| </xsd:complexType>
|
| <xsd:element name="ErrorValue" type="tns:ErrorValue"/>
| <xsd:element name="TestException" type="tns:TestException"/>
|
| <xsd:element name="MonitorEventsRequest">
| <xsd:complexType>
| <xsd:sequence>
| <xsd:element name="deviceID" type="tns:DeviceID"/>
| <xsd:element name="requestFilter" type="tns:FilterEvents" minOccurs="0"/>
| </xsd:sequence>
| </xsd:complexType>
| </xsd:element>
|
| <xsd:element name="MonitorEventsResponse">
| <xsd:complexType>
| <xsd:sequence>
| <xsd:element name="deviceID" type="tns:DeviceID"/>
| <xsd:element name="allotedFilter" type="tns:FilterEvents" minOccurs="0"/>
| </xsd:sequence>
| </xsd:complexType>
| </xsd:element>
| </xsd:schema>
| </types>
|
| <message name="MonitorEventsRequest">
| <part name="parameters" element="tns:MonitorEventsRequest"/>
| </message>
|
| <message name="MonitorEventsResponse">
| <part name="result" element="tns:MonitorEventsResponse"/>
| </message>
|
| <message name="TestException">
| <part name="exception" element="tns:TestException"/>
| </message>
|
| <portType name="EventMonitoringService">
| <operation name="MonitorEventsRequest">
| <input message="ns2:MonitorEventsRequest"/>
| <output message="ns2:MonitorEventsResponse"/>
| <fault name="FaultName" message="ns2:TestException"/>
| </operation>
| </portType>
|
|
| <binding name="EventMonitoringServiceBinding" type="ns2:EventMonitoringService">
| <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
| <operation name="MonitorEventsRequest">
| <soap:operation soapAction=""/>
| <input>
| <soap:body use="literal"/>
| </input>
| <output>
| <soap:body use="literal"/>
| </output>
| <fault name="FaultName">
| <soap:fault name="FaultName" use="literal"/>
| </fault>
| </operation>
|
| </binding>
| <service name="EventMonitoringService">
| <port name="EventMonitoringServicePort" binding="ns2:EventMonitoringServiceBinding">
| <soap:address location="http://localhost/test/EventMonitoringService"/>
| </port>
| </service>
|
| </definitions>
|
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052557#4052557
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052557
17 years, 7 months