January 2007 - jbossws-dev - Jboss List Archives

[Design of JBoss Web Services] - Re: SOAP request missing namespace

by heiko.braun＠jboss.com

Please post these questions to the user forum: http://www.jboss.org/index.html?module=bb&op=viewforum&f=200 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008944#4008944 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008944

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - SOAP request missing namespace

by yperey

Hello, I've followed step by step the http://wiki.jboss.org/wiki/Wiki.jsp?page=WS4EEDOCClientStepByStep to deploy a web service client on JBoss 4.0.2 using JWSDP 1.6. The problem is that in the SOAP request I send to the server there are attributes of a complex type with missing namespace: <?xml version="1.0" encoding="UTF-8"?> | <soapenv:Envelope | xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" | xmlns:xsd="http://www.w3.org/2001/XMLSchema" | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> | <soapenv:Header> | <jbws:username soapenv:actor="http://webservice.jboss.com/ws4ee/login" | xmlns:jbws="http://webservice.jboss.com/ws4ee">root</jbws:username> | <jbws:password soapenv:actor="http://webservice.jboss.com/ws4ee/login" | xmlns:jbws="http://webservice.jboss.com/ws4ee">cm9vdDE=</jbws:password> | </soapenv:Header> | <soapenv:Body> | <ns1:LHUB_PutIntoTargetSystemsProcessRequest | xmlns:ns1="http://xmlns.oracle.com/LHUB_PutIntoTargetSystems"> | <source>1</source> | <targets>0</targets> | </ns1:LHUB_PutIntoTargetSystemsProcessRequest> | </soapenv:Body> | </soapenv:Envelope> like for source and targets event if in the wsdl it is specified attributeFormDefault="qualified" and elementFormDefault="qualidied" as you can see: | ... | <types> | <schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://xmlns.oracle.com/LHUB_PutIntoTargetSystems" | xmlns="http://www.w3.org/2001/XMLSchema"> | <element name="LHUB_PutIntoTargetSystemsProcessRequest"> | <complexType> | <sequence> | <element name="source" type="string"/> | <element name="targets" type="string"/> | </sequence> | </complexType> | </element> | <element name="LHUB_PutIntoTargetSystemsProcessResponse"> | <complexType> | <sequence> | <element name="error" type="string"/> | <element name="description" type="string"/> | <element name="details" type="string"/> | </sequence> | </complexType> | </element> | </schema> | </types> | ... | here is my wscompile line: anonymous wrote : wscompile -gen:client -f:documentliteral -f:wsi -mapping jaxrpc-mapping-client.xml -keep config-client.xml Here is the correct SOAP envelope that I'm supposed to have: <?xml version="1.0" encoding="UTF-8"?> | <soapenv:Envelope | xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" | xmlns:xsd="http://www.w3.org/2001/XMLSchema" | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> | <soapenv:Header> | <jbws:username soapenv:actor="http://webservice.jboss.com/ws4ee/login" | xmlns:jbws="http://webservice.jboss.com/ws4ee">root</jbws:username> | <jbws:password soapenv:actor="http://webservice.jboss.com/ws4ee/login" | xmlns:jbws="http://webservice.jboss.com/ws4ee">cm9vdDE=</jbws:password> | </soapenv:Header> | <soapenv:Body> | <ns1:LHUB_PutIntoTargetSystemsProcessRequest | xmlns:ns1="http://xmlns.oracle.com/LHUB_PutIntoTargetSystems"> | <ns1:source>1</ns1:source> | <ns1:targets>0</ns1:targets> | </ns1:LHUB_PutIntoTargetSystemsProcessRequest> | </soapenv:Body> | </soapenv:Envelope> Any idea ? Yann. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008779#4008779 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008779

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: RI tools dependency

by heiko.braun＠jboss.com

In order to plugin a different tools layer it is necessary to implement an ant macro that will be used to invoke the tools codebase. See | jbossws-test/ant-import/jaxws-tools-delegate.xml | for an example. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008172#4008172 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008172

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - RI tools dependency

by heiko.braun＠jboss.com

I introduced a dependency on the RI tools in order to create the interop artifacts. The main reasons for this are: - We need to be more flexible when facing the next plug-fest - Having a pluggable tools layer within the test suite means that we can easily verify our own JAX-WS tools codebase at some later point in time - We do verify that our stack really works with the JAX-WS artifacts that the RI tools generate Currently this requires a now build property to be set | # | # JAX-WS Home | # The testsuite requires the RI tools to generate the artifacts | # NOTE: Don't use the JWSDP 2.0, it contains legacy API. | # Use the RI codebase from java.net instead: | # https://jax-ws.dev.java.net/jax-ws-20-fcs/ | # | ri.home=/home/hbraun/dev/env/jaxws-ri_2.0 | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008171#4008171 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008171

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: jar references from jaxb-impl.jar

by jason.greene＠jboss.com

Yes, we provide all of the jars that are refernced here (jsr-173 = StAX). They can for sure be ignored, although we could also remove that classpath entry. from the manifest. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4007814#4007814 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4007814

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: jar references from jaxb-impl.jar

by thomas.diesler＠jboss.com

I would say this debug warnings can be ignored. The activation.jar is the only one that we need (AFAI am aware of) and it is in fact on the classpath when its needed View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4007813#4007813 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4007813

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - jar references from jaxb-impl.jar

by thomas.diesler＠jboss.com

David reports: | 2007-01-09 10:15:29,265 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.detectDuplicateNesting=true | org.jboss.deployment.DeploymentException: url file:/C:/jboss-4.0.5.GA-ejb3/server/default/deploy/jbossws.sar/activation.jar could not be opened, does it exist? | 2007-01-09 10:15:29,281 DEBUG [org.jboss.deployment.MainDeployer] The manifest entry in file:/C:/jboss-4.0.5.GA-ejb3/server/default/deploy/jbossws.sar/jaxb-impl.jar references URL file:/C:/jboss-4.0.5.GA-ejb3/server/default/deploy/jbossws.sar/jsr173_1.0_api.jar which could not be opened, entry ignored rg.jboss.deployment.DeploymentException: url file:/C:/jboss-4.0.5.GA-ejb3/server/default/deploy/jbossws.sar/jsr173_1.0_api.jar could not be opened, does it exist? | 2007-01-09 10:15:29,281 DEBUG [org.jboss.deployment.MainDeployer] The manifest entry in file:/C:/jboss-4.0.5.GA-ejb3/server/default/deploy/jbossws.sar/jaxb-impl.jar references URL file:/C:/jboss-4.0.5.GA-ejb3/server/default/deploy/jbossws.sar/jaxb1-impl.jar which could not be opened, entry ignored | | org.jboss.deployment.DeploymentException: url file:/C:/jboss-4.0.5.GA-ejb3/server/default/deploy/jbossws.sar/jaxb1-impl.jar could not be opened, does it exist? | I tracked this down and these jars are referenced in the manifest.mf file within the jaxb-impl.jar file: | Class-Path: jaxb-api.jar activation.jar jsr173_1.0_api.jar jaxb1-impl.jar | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4007811#4007811 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4007811

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: wsgen API, SPI, command line tool, and ant task

by thomas.diesler＠jboss.com

Thanks Jason, I'll have a look at it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4007704#4007704 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4007704

17 years, 3 months

1
0
0 / 0

[Fwd: [JBoss JIRA] Reopened: (JBWS-800) ClassCastException when trying to marshal a subclass of Date]

by Alexey Loubyansky

AFAIU, whether it's going to be a single release that works on the requested versions depends on whether there going to be a single JBossMC release that works in all the requested branches. -------- Original Message -------- Subject: [JBoss JIRA] Reopened: (JBWS-800) ClassCastException when trying to marshal a subclass of Date Date: Sun, 28 Jan 2007 05:53:58 -0500 (EST) From: Thomas Diesler (JIRA) <jira-events(a)jboss.com> To: alex(a)jboss.org [ http://jira.jboss.com/jira/browse/JBWS-800?page=all ] Thomas Diesler reopened JBWS-800: --------------------------------- Assignee: Alexey Loubyansky (was: Thomas Diesler) Please create a (non-snapshot) jdk14 release that works in jboss50,42,40

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - wsgen API, SPI, command line tool, and ant task

by jason.greene＠jboss.com

As of today, I checked in a full implementation of the JAX-WS wsgen tool. This work includes a full API and SPI, as well as an ant task and command line tool. The WebServiceGenerator API is available here: http://labs.jboss.com/file-access/default/members/jbossws/downloads/api-d... The WebServiceGeneratorProvider SPI here: http://labs.jboss.com/file-access/default/members/jbossws/downloads/api-d... A custom provider can be specified using the system property "org.jboss.ws.tools.jaxws.webServiceGeneratorProvider". This property is also available as static public field on WebServiceGenerator. The command line tool documentation is available here: http://labs.jboss.com/file-access/default/members/jbossws/downloads/api-d... The ant task documentation is available here: http://labs.jboss.com/file-access/default/members/jbossws/downloads/api-d... The test case that demonstrates the API is located here: http://fisheye.jboss.com/browse/JBossWS/trunk/jbossws-tests/src/main/java... -Jason View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4007142#4007142 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4007142

17 years, 3 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-dev January 2007