January 2007 - jbossws-dev - Jboss List Archives

[Design of JBoss Web Services] - Re: JBWS-1260 - such a part must refer to an element named a

by jason.greene＠jboss.com

"thomas.diesler(a)jboss.com" wrote : In that case a wsdl like this | | should work and the generated java method name should be paraList2 instead of invokeAttach. | Thats incorrect. The generated java method name (unless customized) always matches the operation name, it never matches the element name. Also it does not adhere to the wrapped convention so it must be treated as a bare parameter style service. Also, this WSDL violates BP 1.0 because it uses "type" on the part definition for a document/literal web service. It must be element. | <part name="attachmentContents" type="xsd:string"/> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4001040#4001040 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4001040

18 years

1
0
0 / 0

WS-MTOM Policy submitted to W3C

by Heiko Braun

"This specification describes a domain-specific policy assertion that indicates endpoint support of the optimized MIME multipart/ related serialization of SOAP messages defined in section 3 of the SOAP Message Transmission Optimization Mechanism specification. This policy assertion can be specified within a policy alternative as defined in WS-Policy Framework and attached to a WSDL description as defined in WS-PolicyAttachment." http://www.w3.org/Submission/2006/SUBM-WS-MTOMPolicy-20061101/ -- Heiko Braun JBoss, a division of Red Hat T: +49 89 52350383 M: +49 178 1496854

18 years

1
0
0 / 0

Using JAXB2: A few tips to write efficient code

by Heiko Braun

See https://wsit.dev.java.net/servlets/ReadMsg?list=dev&msgNo=66 -- Heiko Braun JBoss, a division of Red Hat T: +49 89 52350383 M: +49 178 1496854

18 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1260 - such a part must refer to an element named a

by darran.lofthouse＠jboss.com

I can't reproduce the error you are seeing if my WSDL contains messages with 2 parts, instead I get the following error reported: - anonymous wrote : | [junit] org.jboss.ws.WSException: Only Request-Only and Request-Response MEPs are allowed | [junit] at org.jboss.ws.metadata.wsdl.WSDLUtils.getWsdl11Input(WSDLUtils.java:885) | [junit] at org.jboss.ws.tools.WSDLToJava.appendMethods(WSDLToJava.java:287) | [junit] at org.jboss.ws.tools.WSDLToJava.createSEIFile(WSDLToJava.java:588) | [junit] at org.jboss.ws.tools.WSDLToJava.createSEI(WSDLToJava.java:618) | [junit] at org.jboss.ws.tools.WSDLToJava.generateSEI(WSDLToJava.java:187) | [junit] at org.jboss.ws.tools.helpers.ToolsHelper.handleWSDLToJavaGeneration(ToolsHelper.java:304) | [junit] at org.jboss.ws.tools.WSTools.process(WSTools.java:138) | I think this check was part of some refactoring that happened on trunk. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4000953#4000953 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4000953

18 years

1
0
0 / 0

[Fwd: FW: JBoss WS Doc checkin for Wed 1-11-2006]

by Thomas Diesler

Folks, here is the latest jbossws tutorial. Please provide feedback. cheers -thomas -----Original Message----- From: Sam Griffith Sent: Thursday, January 11, 2007 10:49 AM To: Thomas Diesler; Burr Sutter; Jason T. Greene Cc: Shaun Connolly Subject: JBoss WS Doc checkin for Wed 1-11-2006 Hello all, I've checked in the Tutorial #1 docs. They can be found in the WS trunk here: /jbossws_head/jbossws-docs/online/tutorial-doc If you go in there and do a ant build, you'll end up with this one doc. After ant is done building, go into the build directory, then into the en dir, then into the pdf dir. Open the pdf file. This file contains a quick intro to our WS stuff, a install instruction (very simple b/c AS 5 includes our stuff) and then a tutorial covering getting up a simple web service, it's parts, it's ant build file, etc., then seeing it in AS Console, WS Console, then testing it in Oxygen to see the request and response. Let me know your feedback. Also, I'm going to add a few more screenshots I think as well, but they are not required. I just think it makes the tutorial nicer. I've also attached the file in case you don't want to go build it. -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

18 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1260 - such a part must refer to an element named a

by darran.lofthouse＠jboss.com

I am not sure if that is the case, this requirement is described within chapter 2 of the JAX-RPC specification and the purpose of this chapter is to describe how to generate the service endpoint interface from the WSDL. Also the terminology used is WSDL terminology, they are saying the element must be named after the operation not that the parameter must be named after the method. When refering to java methods and parameters they do refer to them as methods and parameters. So I am interpreting it as: - When you are generating a SEI from a WSDL If the operation meets these requirements you can treat it as wrapped an unwrap it. Having said that this check was one of the last checks I added just to be complete with the list of requirements in the spec so there shouldn't be a problem if it is removed. Looking at your WSDL your message 'attachRequest' contains two message parts so based on the first requirement for a message to contain only a single part this should also be rejected so I am surprised you are not seeing that - I will have a look and see what happened to that check. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4000916#4000916 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4000916

18 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1260 - such a part must refer to an element named a

by thomas.diesler＠jboss.com

18 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1260 - such a part must refer to an element named a

by darran.lofthouse＠jboss.com

BP only mentions a naming requirement for the wrappers for RPC, for document it just says that each operation must have a unique signature so that they can be identified. It is the JAX-RPC spec and JAX-WS spec that specified requirements that must be met for an operation to be considered a wrapped operation. >From JAX-RPC 6.4.1: - anonymous wrote : In order to qualify as using the ?wrapper? style, an operation must fulfill the following | conditions: | ? its input and output messages (if present) must contain exactly one part; | ? such a part must refer to an element named after the operation; | ? such an element (a wrapper) must be of a complex type defined using the | xsd:sequence compositor and containing only elements declarations. >From JAX-WS 2.3.1.2 this is refined slightly: - anonymous wrote : A WSDL operation qualifies for wrapper style mapping only if the following criteria are met: | (i) The operation?s input and output messages (if present) each contain only a single part | (ii) The input message part refers to a global element declaration whose localname is equal to the operation | name | (iii) The output message part refers to a global element declaration | (iv) The elements referred to by the input and output message parts (henceforth referred to as wrapper | elements) are both complex types defined using the xsd:sequence compositor | (v) The wrapper elements only contain child elements, they must not contain other structures such as | wildcards (element or attribute), xsd:choice, substitution groups (element references are not permitted) | or attributes; furthermore, they must not be nillable. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4000882#4000882 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4000882

18 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1260 - such a part must refer to an element named a

by thomas.diesler＠jboss.com

This also relates to http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4000809#4000809 Is request message element to operation name equivalents a general requirement for doc/lit? Does the BP say anything about it? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4000863#4000863 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4000863

18 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: doclit request message element name not equal to operati

by darran.lofthouse＠jboss.com

I will add the section number from the spec to the message, the following post is where I raised the actual validation requrements: - http://www.jboss.com/index.html?module=bb&op=viewtopic&t=97638 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4000812#4000812 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4000812

18 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-dev January 2007