[JBoss JIRA] Created: (JBWS-1943) NPE when com.sun.management.jmxremote.port is changed, preventing correct publication of WSDL
by Chris Laprun (JIRA)
NPE when com.sun.management.jmxremote.port is changed, preventing correct publication of WSDL
---------------------------------------------------------------------------------------------
Key: JBWS-1943
URL: http://jira.jboss.com/jira/browse/JBWS-1943
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jbossws-2.0.1.SP2
Reporter: Chris Laprun
Changing the com.sun.management.jmxremote.port value results in WSDLFilePublisher not being to publish the WSDL file:
java.lang.NullPointerException
at org.jboss.wsf.stack.jbws.WSDLFilePublisher.getPublishLocation(WSDLFilePublisher.java:303)
at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:103)
at org.jboss.wsf.stack.jbws.PublishContractDeploymentAspect.create(PublishContractDeploymentAspect.java:52)
at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115)
at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:97)
at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:90)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy158.start(Unknown Source)
Looks like the root of the error is an issue with AbstractServerConfig.getConnectorPort failing from called from getWebServicePort. A warning is issued on the console: "Unable to calculate 'WebServicePort', using default '8080'".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 2 months
[JBoss JIRA] Created: (JBWS-1924) Verify installation script for jboss-4.2.1.GA
by Alessio Soldano (JIRA)
Verify installation script for jboss-4.2.1.GA
---------------------------------------------
Key: JBWS-1924
URL: http://jira.jboss.com/jira/browse/JBWS-1924
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jbossws-2.0.2
Reporter: Alessio Soldano
Installing JBossWS 2.0.2.GA on JBoss 4.2.1.GA without having a JBossWS 2.0.1.GA installed result in a broken installation due to jbossws-jboss42.jar/jbossws-jboss421.jar missing in client libs.
The 2.0.2 installation script does not remove that lib, thus installing 2.0.1 and then 2.0.2 seems to be a workaround. This has to be verified as well as the 2.0.2 installation script / hudson conf for the 4.2.1.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 2 months
[JBoss JIRA] Created: (JBWS-1816) JAXWS SOAPFault inheritance
by Thomas Diesler (JIRA)
JAXWS SOAPFault inheritance
---------------------------
Key: JBWS-1816
URL: http://jira.jboss.com/jira/browse/JBWS-1816
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Thomas Diesler
Fix For: jbossws-2.0.2
I'm using wsprovide (an ant task in maven on windows) to generate my wsdl and then wsconsume to generate my client classes. My web service method throws multiple exceptions, some of which extend from each other.
Unfortunately that inheritance relationship is lost in the generated wsdl (no < extension base...) and of course in the client classes.
Is there some way to get the wsprovide task to do what I'm asking for? Maybe with an annotation or something specific passed in when I call the task?
Thanks in advance.
BTW - there are multiple JIRA items (like: http://jira.jboss.com/jira/browse/JBWS-251) that refer to this issue issue. However it doesn't appear that it ever valid or addressed. So I'm wondering if there's something basic that I should be doing? Like digging into the documentation on javaToWSDL which I believe is being used by wsprovide.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 3 months
[JBoss JIRA] Created: (JBWS-1944) jbossws-native ignores @XmlSchema annotation on package-info.java
by Artur Karazniewicz (JIRA)
jbossws-native ignores @XmlSchema annotation on package-info.java
-----------------------------------------------------------------
Key: JBWS-1944
URL: http://jira.jboss.com/jira/browse/JBWS-1944
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-jaxws
Affects Versions: jbossws-2.0.2, jbossws-2.0.1.SP2, jbossws-2.0.1.SP1, jbossws-2.0.1
Environment: Microsoft Windows XP Home SP2, x86
java version "1.5.0_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)
Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode)
Reporter: Artur Karazniewicz
Seems that current implementations of jbossws-native ignores @XmlSchema annotation on package in package-info.java.
Please find my test case attached.
Generated Schema is as follows:
{code:title=TestWebService.java endpoint}
package org.acme.service;
import javax.jws.WebService;
import javax.ejb.Stateless;
@WebService()
@Stateless()
public class TestWebSevice {
public void perform(Parms params) {
}
}
{code}
{code:title=Params.java payload}
package org.acme.service;
public class Parms {
public String val;
}
{code}
{code:title=package-info.java}
@XmlSchema(namespace="http://www.acme.org/service", elementFormDefault=XmlNsForm.QUALIFIED)
package org.acme.service;
import javax.xml.bind.annotation.XmlNsForm;
import javax.xml.bind.annotation.XmlSchema;
{code}
generated WSDL:
{code:title=TestWebService WSDL}
<definitions name='TestWebSeviceService' targetNamespace='http://service.acme.org/' xmlns='http://schemas.xmlsoap.org/wsdl/' xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' xmlns:tns='http://service.acme.org/' xmlns:xsd='http://www.w3.org/2001/XMLSchema'>
<types>
<xs:schema targetNamespace='http://service.acme.org/' version='1.0' xmlns:tns='http://service.acme.org/' xmlns:xs='http://www.w3.org/2001/XMLSchema'>
<xs:element name='perform' type='tns:perform'/>
<xs:element name='performResponse' type='tns:performResponse'/>
<xs:complexType name='perform'>
<xs:sequence>
<xs:element minOccurs='0' name='arg0' type='tns:parms'/>
</xs:sequence>
</xs:complexType>
<xs:complexType name='parms'>
<xs:sequence>
<xs:element minOccurs='0' name='val' type='xs:string'/>
</xs:sequence>
</xs:complexType>
<xs:complexType name='performResponse'>
<xs:sequence/>
</xs:complexType>
</xs:schema>
</types>
<message name='TestWebSevice_perform'>
<part element='tns:perform' name='perform'></part>
</message>
<message name='TestWebSevice_performResponse'>
<part element='tns:performResponse' name='performResponse'></part>
</message>
<portType name='TestWebSevice'>
<operation name='perform' parameterOrder='perform'>
<input message='tns:TestWebSevice_perform'></input>
<output message='tns:TestWebSevice_performResponse'></output>
</operation>
</portType>
<binding name='TestWebSeviceBinding' type='tns:TestWebSevice'>
<soap:binding style='document' transport='http://schemas.xmlsoap.org/soap/http'/>
<operation name='perform'>
<soap:operation soapAction=''/>
<input>
<soap:body use='literal'/>
</input>
<output>
<soap:body use='literal'/>
</output>
</operation>
</binding>
<service name='TestWebSeviceService'>
<port binding='tns:TestWebSeviceBinding' name='TestWebSevicePort'>
<soap:address location='http://127.0.0.1:8080/test/TestWebSevice'/>
</port>
</service>
</definitions>
{code}
I have checked the same codebase against glassfish v2 with metro, and relevant part of WSDL (i.e. XSD) looks like below. Note *elementFormDefault="qualified"* and *targetNamespace="http://www.acme.org/service"*
{code:title=TestWebService XSD from GlassFish v2 and Metro}
<?xml version="1.0" encoding="UTF-8"?>
<!-- Published by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.2-hudson-182-RC1. -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" version="1.0" targetNamespace="http://www.acme.org/service">
<xs:complexType name="parms">
<xs:sequence>
<xs:element name="val" type="xs:string" minOccurs="0"></xs:element>
</xs:sequence>
</xs:complexType>
</xs:schema>
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 3 months
[JBoss JIRA] Commented: (JBWS-1136) Allow username to be specified in the requires list
by Karl de Boer (JIRA)
[ http://jira.jboss.com/jira/browse/JBWS-1136?page=comments#action_12393187 ]
Karl de Boer commented on JBWS-1136:
------------------------------------
It is a bit sad that this feature is still not supported.
If you start with a WSDL you end up haveing a JSE endpoint. I wonder why the EJB endpoints do have JAAS Authentication and JSE Endpoints don't while it sbest to start with a proper WS Interface (the WSDL)
I wrote already an implementation for this two years ago but dropped it because it should be intergrated in the JAXWS WSSecurity Handler stack.
EJB Endpoints and JSE Endpoints should really have the same behaviour and functionality.
Reading from the release notes i thought this was fixed in 2.02GA at last.
I will see what i can do myself
> Allow username to be specified in the requires list
> ---------------------------------------------------
>
> Key: JBWS-1136
> URL: http://jira.jboss.com/jira/browse/JBWS-1136
> Project: JBoss Web Services
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: ws-security
> Affects Versions: jbossws-1.0.1
> Reporter: Darran Lofthouse
> Assigned To: Darran Lofthouse
> Fix For: jbossws-2.1.1
>
>
> Allow username to be specified in the requires list for endpoints so that messages without the username can be rejected.
> At the moment for EJB endpoints they can be configured using standard J2EE security so if there is no authenticated user the request is rejected, however this can't be done for the POJO endpoints.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 3 months