January 2008 - jbossws-users - Jboss List Archives

by opuce

Hi there I've got a little Problem or you could even say a bigger one. I'm not able to deploy JBossWS. When I run "ant deploy-jboss42" Ant tells me, that there is no target with that name. Else when I run "ant" I get the Following Error Message: BUILD FAILED /opt/opuce/jbossws/jbossws-native-2.0.2.GA/build.xml:141: The following error occurred while executing this line: /opt/opuce/jbossws/jbossws-native-2.0.2.GA/tests/ant-import/build-testsuite.xml:340: Compile failed; see the compiler error output for details. What can I do any suggestions? thomas View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4121805#4121805 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4121805

16 years, 11 months

1
0
0 / 0

[JBossWS] - Re: WSSE UsernameToken without HTTP basic auth?

by alessio.soldano＠jboss.com

"mikaeljl" wrote : I do not think WSSE UsernameToken authentication is working for POJO endpoints without enabling some form of http level authentication like basic auth? Can you confirm this? | There's the issue of the principal you described in the previous posts. Btw this also is related to what we're discussing here: http://jira.jboss.org/jira/browse/JBWS-1136 anonymous wrote : I will look into converting my pojo endpoints into ejb3 endpoints because that seems to be the easiest solution right now. I guess it is just a matter of adding @Stateless to my pojo class and packaging/deploying the thing as a jar instead of a war... kind of... | Almost yes, I shouldn't be difficult. anonymous wrote : Are there any plans for supporting WSSE UsernameToken based authentication for POJO endpoints (without the requirement of any additional http level authentication? | I don't have a reliable answer for this, sorry. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4121793#4121793 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4121793

16 years, 11 months

1
0
0 / 0

[JBossWS] - Re: Problem importing multiple schema from the same namespac

by Didi1976

Is there any solution till now? We ran in a similar problem: A SLSB calls a WebService on a Bea WLI to trigger there some processing. The generated WSDL from the WLI looks like: | <?xml version="1.0" encoding="utf-8"?> | <wsdl:definitions | xmlns:conv="http://www.openuri.org/2002/04/soap/conversation/" | xmlns:cw="http://www.openuri.org/2002/04/wsdl/conversation/" | xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" | xmlns:jms="http://www.openuri.org/2002/04/wsdl/jms/" | xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" | xmlns:s="http://www.w3.org/2001/XMLSchema" | xmlns:s0="http://www.openuri.org/" | xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" | xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" | xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" | targetNamespace="http://www.openuri.org/"> | <wsdl:types> | <s:schema xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:test="http://test.softsolution.at" elementFormDefault="qualified" targetNamespace="http://www.openuri.org/"> | <s:import namespace="http://test.softsolution.at"/> | <s:element name="clientRequest"> | <s:complexType> | <s:sequence> | <s:element ref="test:AllParts"/> | </s:sequence> | </s:complexType> | </s:element> | <s:element name="clientRequestResponse"> | <s:complexType> | <s:sequence/> | </s:complexType> | </s:element> | </s:schema> | <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://test.softsolution.at" targetNamespace="http://test.softsolution.at" elementFormDefault="qualified" attributeFormDefault="unqualified"> | <xs:element name="AllParts"> | <xs:annotation> | <xs:documentation>Combine PartA and PartB</xs:documentation> | </xs:annotation> | <xs:complexType> | <xs:sequence> | <xs:element ref="tns:PartA"/> | <xs:element ref="tns:PartB"/> | </xs:sequence> | </xs:complexType> | </xs:element> | </xs:schema> | <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://test.softsolution.at" targetNamespace="http://test.softsolution.at" elementFormDefault="qualified" attributeFormDefault="unqualified"> | <xs:element name="PartA"> | <xs:annotation> | <xs:documentation>First Part of the Test</xs:documentation> | </xs:annotation> | <xs:complexType> | <xs:sequence> | <xs:element name="ElementA" type="xs:string"/> | <xs:element name="ElementB" type="xs:long"/> | </xs:sequence> | </xs:complexType> | </xs:element> | </xs:schema> | <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://test.softsolution.at" targetNamespace="http://test.softsolution.at" elementFormDefault="qualified" attributeFormDefault="unqualified"> | <xs:element name="PartB"> | <xs:annotation> | <xs:documentation>Second Part of the Test</xs:documentation> | </xs:annotation> | <xs:complexType> | <xs:sequence> | <xs:element name="ElementC" type="xs:string"/> | <xs:element name="ElementD" type="xs:long"/> | </xs:sequence> | </xs:complexType> | </xs:element> | </xs:schema> | | </wsdl:types> | <wsdl:message name="clientRequestSoapIn"> | <wsdl:part name="parameters" element="s0:clientRequest"/> | </wsdl:message> | <wsdl:message name="clientRequestSoapOut"> | <wsdl:part name="parameters" element="s0:clientRequestResponse"/> | </wsdl:message> | <wsdl:portType name="testAllPartsSoap"> | <wsdl:operation name="clientRequest"> | <wsdl:input message="s0:clientRequestSoapIn"/> | <wsdl:output message="s0:clientRequestSoapOut"/> | </wsdl:operation> | </wsdl:portType> | <wsdl:binding name="testAllPartsSoap" type="s0:testAllPartsSoap"> | <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/> | <wsdl:operation name="clientRequest"> | <soap:operation soapAction="http://www.openuri.org/clientRequest" style="document"/> | <wsdl:input> | <soap:body use="literal"/> | </wsdl:input> | <wsdl:output> | <soap:body use="literal"/> | </wsdl:output> | </wsdl:operation> | </wsdl:binding> | <wsdl:service name="testAllParts"> | <wsdl:port name="testAllPartsSoap" binding="s0:testAllPartsSoap"> | <soap:address location="http://xpscd:7001/TestWeb/testAllParts.jpd"/> | </wsdl:port> | </wsdl:service> | </wsdl:definitions> | The following error is logged by the JBoss Server (4.2.2.GA): | 2008-01-21 11:08:04,342 ERROR [org.jboss.ws.metadata.wsdl.xmlschema.JBossXSErrorHandler] JBossWS_www.openuri.org_23041.xsd[domain:http://www.w3.org/TR/xml-schema-...: Cannot resolve the name 'test:AllParts' to a(n) 'element declaration' component. | It seems that there is a problem in handling multiple schemas mapped to the same targetNamespace. The ws-client classes are generated and work correctly without any error if used directly with jax-ws. The error does not prevent the WebService from being called. So the error can be ignored (should it be ignored?). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4121761#4121761 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4121761

16 years, 11 months

1
0
0 / 0

[JBossWS] - Re: WSSE UsernameToken without HTTP basic auth?

by mikaeljl

Hi Alessio! Thank you for investigating this, much appreciated ! Unfortunately I do not have an EJB3 endpoint, I'm starting with a WSDL file so I have a POJO endpoint (using wsconsume to do wsdl -2-java). I do not think WSSE UsernameToken authentication is working for POJO endpoints without enabling some form of http level authentication like basic auth? Can you confirm this? I will look into converting my pojo endpoints into ejb3 endpoints because that seems to be the easiest solution right now. I guess it is just a matter of adding @Stateless to my pojo class and packaging/deploying the thing as a jar instead of a war... kind of... Are there any plans for supporting WSSE UsernameToken based authentication for POJO endpoints (without the requirement of any additional http level authentication? /MIkael View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4121726#4121726 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4121726

16 years, 11 months

1
0
0 / 0

[JBossWS] - Re: Reg : Jboss migration from apache axis

by extasy

hi , will any workaround on jboss4.2 help us on supporting rpc/enc format. As there is high necessity to do this operation am raising this query. Thanks Babu View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4121707#4121707 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4121707

16 years, 11 months

1
0
0 / 0

[JBossWS] - Re: url mapping schemalocation

by AJanz

many thanks!!! editing jboss-beans.xml and commenting webservicehost solved my problem. now the ip or url from the get request is then used as url prefix for the schemalocation. greetings sascha View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4121507#4121507 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4121507

16 years, 11 months

1
0
0 / 0

[JBossWS] - Re: url mapping schemalocation

by alessio.soldano＠jboss.com

"AJanz" wrote : | http://ip-adress:8080/WebService/project?wsdl | | gives an error | What error? anonymous wrote : | how can i publish a web service under a differen url? | What exactly do you mean? Take a look at this: http://jbws.dyndns.org/mediawiki/index.php?title=FAQ#How_does_rewriting_o... and read my reply here: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=126138 I guess it's what you're looking for. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4121492#4121492 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4121492

16 years, 11 months

1
0
0 / 0

[JBossWS] - Re: url mapping schemalocation

by alessio.soldano＠jboss.com

"AJanz" wrote : something i must do wrong. | | i edited the wsdl file, but then could no longer build the project because | | <xsd:import namespace="mynamespace" | schemaLocation="http:/myalias:8080/project/Service?wsdl&resource=myschema.xsd"/> | While editing the local copy of the wsdl, also change the import url with something like <xsd:import namespace="mynamespace" | schemaLocation="myschema.xsd"/> and add the myschema.xsd to the archive you deploy, along with the wsdl file. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4121491#4121491 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4121491

16 years, 11 months

1
0
0 / 0

[JBossWS] - Re: url mapping schemalocation

by AJanz

i managed to build the project with <xsd:import namespace="mynamespace" schemaLocation="http:/myalias:8080/project/Service?wsdl&resource=myschema.xsd"/> but http://ip-adress:8080/WebService/project?wsdl gives an error how can i publish a web service under a differen url? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4121466#4121466 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4121466

16 years, 11 months

1
0
0 / 0

[JBossWS] - Re: How can I see the SoapResponse

by alessio.soldano＠jboss.com

It's here, added recently :-) : http://jbws.dyndns.org/mediawiki/index.php?title=Log4J View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4121460#4121460 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4121460

16 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-users January 2008