December 2006 - jbossws-dev - Jboss List Archives

RE: [jbossws-dev] Document/Wrapped can not be a message type

by Jason T. Greene

> -----Original Message----- > From: Thomas Diesler [mailto:thomas.diesler@redhat.com] > Sent: Thursday, December 07, 2006 12:42 PM > To: Jason T. Greene > Cc: jbossws-dev(a)lists.jboss.org > Subject: Re: [jbossws-dev] Document/Wrapped can not be a message type > > This is saying: > > if document/wrapped and the endpoint is not a SOAPElement endpoint do > the wrapping. > > There are occasions where a message type endpoint registers as > document/wrapped > We should fix this then. As I was saying, it's illegal for a wrapped type to be a message style service. A message style service is simply a bare service with a SOAPElement or DOM Element for a parameter. I have created a jira issue for this: http://jira.jboss.com/jira/browse/JBWS-1414 -Jason

17 years, 5 months

2
1
0 / 0

Document/Wrapped can not be a message type

by Jason T. Greene

I noticed this change in ParameterMetaData *** if (getOperationMetaData().isDocumentWrapped() && isMessageType() == false) { new DynamicWrapperGenerator(getClassLoader()).generate(this); // Initialize accessors AccessorFactory factory = accessorFactoryCreator.create(this); for (WrappedParameter wrapped : wrappedParameters) wrapped.setAccessor(factory.create(wrapped)); } Document/wrapped is not a valid message type. The only valid message type is bare. -Jason

17 years, 5 months

2
1
0 / 0

[Design of JBoss Web Services] - Re: ws-eventing clustering problem

by maeste

I think we can't. We haven't privileges on Jira to assign issues. Of course we would like you assign it to us (use either my account "maeste" on jira, or Alessio's account "palin", it's the same for us). Do you receive my answer in private E-mail? Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991960#3991960 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991960

17 years, 5 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: ws-eventing clustering problem

by heiko.braun＠jboss.com

Hi, i created a JIRA for this feature. Could you assign this to you? http://jira.jboss.org/jira/browse/JBWS-1412 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991944#3991944 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991944

17 years, 5 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Switching to JAX-WS 2.1

by heiko.braun＠jboss.com

Looks like you are right. At least with regard to the SOAPBinding. Anyway we do have a stale jaxws source tree in trunk that doesn't reflect the final JAX-WS 2.0 API. Am i missing something here? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991919#3991919 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991919

17 years, 5 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Proposed new package structure

by thomas.diesler＠jboss.com

We agreed on the following plan 1) Thomas commits changes to package structure in trunk 2) Jason synchronises meta data and tools code base accross branches 3) for now, there will be no seperate module 4) after CTS completion we get together for a tools/core design session that should produce a migration path towards a better maintainable tools code base View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991796#3991796 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991796

17 years, 5 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Proposed new package structure

by thomas.diesler＠jboss.com

I don't care about where the code lives. If we have virtually identiacal code in trunk and branch(es) thats fine with me. This is the methodology that we use for the jaxrpc testsuite. Consolidation is my concern. If we do not consolidate the tools,metadata, raxrpc codebase to a degree where I can more or less brainlessly merge stuff, I don't see a chance (for myself) to get future releases off the ground in a timely manner. The UMDM might be in flux it is still part of the contract. The curernt issue is that we have multiple code bases that work off diffent UMDMs which is unneccessary and MUST be fixed. Lets, take this discussion off-line - this will be more productive. The aim is to decide upon a clear migration path towards a maintainable code base, which we currently do not have. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991760#3991760 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991760

17 years, 5 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Proposed new package structure

by jason.greene＠jboss.com

Also, isn't the purpose of the integration API to support not only multiple containers, but also multiple versions of JBossAS? I think this is the proper abstraction to use (rather than dividing our stack in the middle), and we can reduce our workload by not introducing new branches for every AS release, and instead just adding a new integration module. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991702#3991702 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991702

17 years, 5 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Switching to JAX-WS 2.1

by jason.greene＠jboss.com

"heiko.braun(a)jboss.com" wrote : The latest spec and API for JAX-WS include significant changes that we need to implement. I realized it when i was looking at the MTOM impl. for JAX-WS. | | I.e. there are new Binding URI's that indicate the use of MTOM: | | | | Enable using @BindingType on the endpoint (SEI) implementation class | | | | * @BindingType(value=javax.xml.ws.SOAPBinding.SOAP11HTTP_MTOM_BINDING) will enable MTOM on the deployed endpoint for SOAP 1.1 binding | | | | | | Is there any reason to stick to the current version? I.e. with regard to CTS? These aren't new, they are part of the 2.0 spec. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991696#3991696 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991696

17 years, 5 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Switching to JAX-WS 2.1

by scott.stark＠jboss.org

It depends on what the signature tests require. If they restrict what methods can show up in jaxws signatures, we can't have this in a certified release unless a challenge allows the updated api. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991694#3991694 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991694

17 years, 5 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 December 2006