December 2006 - jbossws-dev - Jboss List Archives

[Design of JBoss Web Services] - Re: JBWS-1260 - Unwrapping and complex types with attributes

by darran.lofthouse＠jboss.com

Actually just found this from the examples in the JAX-RPC 1.1 spec: - anonymous wrote : The JAX-RPC specification does not specify a standard Java mapping for a | xsd:complexType with the xsd:anyAttribute. So the message part in the | DoAnotherExample message is mapped as a SOAPElement. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993634#3993634 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993634

18 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - JBWS-1260 - Unwrapping and complex types with attributes.

by darran.lofthouse＠jboss.com

I am currently working on JBWS-1260, I have a set of 27 different WSDLs that I have put through wscompile and I am then putting through wstools to compare the generated artifacts. If the complex type is defined as having a sequence and attribtes: - | <complexType name='Person'> | <sequence> | <element name='surname' nillable='true' type='string'/> | </sequence> | <attribute name='postcode' type='string'/> | </complexType> | wscompile creates the following SEI method: - public org.jboss.test.ws.jbws1260.TelephoneNumber lookup(java.lang.String postcode, java.lang.String surname) throws java.rmi.RemoteException; However according to the JAX-RPC 1.1 specification to qualify as using the "wrapper" style the third requirement says: - anonymous wrote : such an element (a wrapper) must be of a complex type defined using the | xsd:sequence compositor and containing only elements declarations. JAX-WS 2.0 expands on this to explicitly prevent the use of attributes. How should we interpret this? Is wscompile unwrapping the complex type incorrectly or is this how it should be unwrapped? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993629#3993629 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993629

18 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1260 and WSDL to Java Array Mappings

by jason.greene＠jboss.com

They aren't needed because they don't provide any information that isn't already in the WSDL file. The only reason why we would want to add them is if we wanted to ensure compatibility with a stack that does require them. This really isn't a goal, since our tools are only intended to be ran used against our stack. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993628#3993628 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993628

18 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - JBWS-1260 and WSDL to Java Array Mappings

by darran.lofthouse＠jboss.com

I am currently working on JBWS-1260, I have a set of 27 different WSDLs that I have put through wscompile and I am then putting through wstools to compare the generated artifacts. Whenever wscompile encounters an element with a maxOccurs greater than '0' e.g. | <complexType name='TelephoneNumber'> | <sequence> | <element name='number' nillable='true' type='string' maxOccurs='unbounded'/> | </sequence> | </complexType> | The generated jaxrpc mapping has it mapped as: - | <java-xml-type-mapping> | <java-type>java.lang.String[]</java-type> | <anonymous-type-qname>http://test.jboss.org/ws/jbws1260/types:TelephoneNumber>number[1,unbounded]</anonymous-type-qname> | <qname-scope>complexType</qname-scope> | </java-xml-type-mapping> | This apears to be because of the following from the Web Services for J2EE 1.1 specification: -anonymous wrote : | | 3. If element E has a maxOccurs attribute greater than 1, then it also has a 'hidden' anonymous type called A. A is an array of the enclosed type. The qname-scope of A is complexType and the name of A is... | a. If E has a name attribute, then the name of A is "E[,]" where E is the value of E?s name attribute. The name is entered as an anonymous-type-qname. | b. If E has no name attribute, then the name of A is "R[,]" where R is the name of the referent element. The name is entered as an anonymous-type-qname. And the examples in the specification apear to confirm this. Is there any reason why we do no generate these mappings at all? Or should this be added? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993625#3993625 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993625

18 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - Re: jbossws deployer on JBoss AS 5

by jason.greene＠jboss.com

As of last week its split into two parts a sar and a deployer. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993495#3993495 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993495

18 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - WS-SecurityPolicy 1.2

by scott.stark＠jboss.org

anonymous wrote : | To OASIS members, Public Announce Lists: | | The OASIS Web Services Secure Exchange TC has recently approved the following | specification as a Committee Draft and approved the package for public review: | | WS-SecurityPolicy 1.2 | | The public review starts today, 12 December 2006, and ends 10 February 2007. | This is an open invitation to comment. We strongly encourage feedback from | potential users, developers and others, whether OASIS members or not, for the | sake of improving the interoperability and quality of OASIS work. Please feel | free to distribute this announcement within your organization and to other | appropriate mail lists. | | More non-normative information about the specification and the technical | committee may be found at the public home page of the TC at | http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ws-sx. Comments may | be submitted to the TC by any person through the use of the OASIS TC Comment | Facility which can be located via the button marked "Send A Comment" at the top | of that page, or directly at | http://www.oasis-open.org/committees/comments/index.php?wg_abbrev=ws-sx. | | Submitted comments (for this work as well as other works of that TC) are | publicly archived and can be viewed at | http://lists.oasis-open.org/archives/ws-sx-comment/. All comments submitted to | OASIS are subject to the OASIS Feedback License, which ensures that the feedback | you provide carries the same obligations at least as the obligations of the TC | members. | | The specification document and related files are available here: | | Editable Source: | http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200512/ws-securitypoli... | | PDF: | http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200512/ws-securitypoli... | | HTML: | http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200512/ws-securitypoli... | | The schema files, that are included normatively in the specification document, | are available as separate files at: | | Schema: | http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200512/ws-securitypoli... | | OASIS and the WS-SX TC welcome your comments. | | | --------------------------------------------------- | Mary P McRae | Manager of TC Administration, OASIS | email: mary.mcrae(a)oasis-open.org | web: www.oasis-open.org | --------------------------------------------------------------------- | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993489#3993489 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993489

18 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - Re: jbossws deployer on JBoss AS 5

by scott.stark＠jboss.org

No reason why it should not be other than dependencies on other deployers. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993486#3993486 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993486

18 years, 1 month

1
0
0 / 0

RE: Using VFS for locating wsdl resources

by Jason T. Greene

I posted instructions in the forum topic. The API is very simple (one line of code to get a file from a deployment). Also, the whole reason for it is so that support for arbitrary deployment types (jar, filesystem directory, network location, etc) can be added and maintained in one location (the mc). > -----Original Message----- > From: Thomas Diesler [mailto:thomas.diesler@redhat.com] > Sent: Wednesday, December 13, 2006 8:45 AM > To: Jason T. Greene > Cc: Thomas Diesler; jbossws-dev(a)lists.jboss.org > Subject: Using VFS for locating wsdl resources > > > Jason, > > please see > > Using the VFS to read a resource from nested jars > http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993404#3993404 > > Why should I waste my time with a project that is so poorly documented > if I don't absolutely have to? > > Yes, in future we should use the VFS. > > Then I update > > public void EarTestCase.testResourceURL() throws Exception > { > File earFile = new File("libs/jaxws-eardeployment.ear"); > assertTrue(earFile.exists()); > > URL warURL = new URL("jar:" + earFile.toURL() + > "!/jaxws-eardeployment.war!/"); > URL wsdlURL = new URL(warURL, "WEB-INF/wsdl/TestEndpoint.wsdl"); > > Element root = DOMUtils.parse(new > ResourceURL(wsdlURL).openStream()); > assertNotNull(root); > } > > > cheers > -thomas > > Jason T. Greene wrote: > > Thomas, > > > > I took a look at your solution to JBCTS-422. Why didn't you use the VFS > > as mentioned in the jira issue? With JBoss 5 all deployment resource > > access is support to go through the VFS. > > > > I have created a new issue for this: > > http://jira.jboss.com/jira/browse/JBWS-1421 > > > > xxxxxxxxxxxxxxxxxxxxxxxxxxxx > > Jason T. Greene > > Senior Software Engineer > > JBoss, a division of Red Hat > > xxxxxxxxxxxxxxxxxxxxxxxxxxxx > > > > > > -- > xxxxxxxxxxxxxxxxxxxxxxxxxxxx > Thomas Diesler > Web Service Lead > JBoss, a division of Red Hat > xxxxxxxxxxxxxxxxxxxxxxxxxxxx

18 years, 1 month

1
0
0 / 0

Using VFS for locating wsdl resources

by Thomas Diesler

Jason, please see Using the VFS to read a resource from nested jars http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993404#3993404 Why should I waste my time with a project that is so poorly documented if I don't absolutely have to? Yes, in future we should use the VFS. Then I update public void EarTestCase.testResourceURL() throws Exception { File earFile = new File("libs/jaxws-eardeployment.ear"); assertTrue(earFile.exists()); URL warURL = new URL("jar:" + earFile.toURL() + "!/jaxws-eardeployment.war!/"); URL wsdlURL = new URL(warURL, "WEB-INF/wsdl/TestEndpoint.wsdl"); Element root = DOMUtils.parse(new ResourceURL(wsdlURL).openStream()); assertNotNull(root); } cheers -thomas Jason T. Greene wrote: > Thomas, > > I took a look at your solution to JBCTS-422. Why didn't you use the VFS > as mentioned in the jira issue? With JBoss 5 all deployment resource > access is support to go through the VFS. > > I have created a new issue for this: > http://jira.jboss.com/jira/browse/JBWS-1421 > > xxxxxxxxxxxxxxxxxxxxxxxxxxxx > Jason T. Greene > Senior Software Engineer > JBoss, a division of Red Hat > xxxxxxxxxxxxxxxxxxxxxxxxxxxx > > -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

18 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - jbossws deployer on JBoss AS 5

by thejavafreak

Dear all, Would it be a great idea if jbossws.sar under deploy directory located under deployers directory like ejb3.deployer, aop.deployer and jbossweb.deployer ? Just a two cents. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993259#3993259 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993259

18 years, 1 month

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 December 2006