November 2007 - jbossws-dev - Jboss List Archives

'port-component' not found as a child of 'ejb'

by Thomas Diesler

Hi Alex, could you please have a look at http://jira.jboss.org/jira/browse/JBAS-4989 According to the jboss_5_0.xsd schema, <port-component> is allowed as child of the generic <ejb> element. cheers -thoams -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

16 years, 6 months

1
0
0 / 0

Re: Using JMS Transport with JAX-WS?

by Thomas Diesler

AFAIK, the jms samples have not yet been ported - have a go if you like cheers -thomas On Fri, 2007-11-16 at 10:27 -0500, David Boeren wrote: > Is it possible to use JMS as a transport for a JAX-WS service? If so, > where can I find documentation or examples on this? In searching the > wiki I could only find references to doing so with JAX-RPC. > > Thanks! -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

16 years, 6 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Integrating ws spi into jboss-javaee

by heiko.braun＠jboss.com

yes, of course ... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105637#4105637 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4105637

16 years, 6 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Integrating ws spi into jboss-javaee

by scott.stark＠jboss.org

"heiko.braun(a)jboss.com" wrote : We are talking about the STAX and the JAX-WS API, right? | The later will ship with jbossws 2.0.2 that's going to be released anytime soon. AS 5 currently uses a snapshot. If you give me access to the jboss-jaxs-api repo, I'll fix the existing API and update JBossWS to use the jboss-jaxs one instead of the codehaus lib. Yes. You already have access since this is part of the jbossas repository: https://svn.jboss.org/repos/jbossas/projects/javaee/trunk/jboss-jaxs-api/ View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105516#4105516 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4105516

16 years, 6 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JSR224

by heiko.braun＠jboss.com

JBossWS doesn't implement the JAX-WS 2.1 specs. Especially these bits have been removed just recently. They did pop up in the API but have not been implemented. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105340#4105340 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4105340

16 years, 6 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Integrating ws spi into jboss-javaee

by heiko.braun＠jboss.com

We are talking about the STAX and the JAX-WS API, right? The later will ship with jbossws 2.0.2 that's going to be released anytime soon. AS 5 currently uses a snapshot. If you give me access to the jboss-jaxs-api repo, I'll fix the existing API and update JBossWS to use the jboss-jaxs one instead of the codehaus lib. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105336#4105336 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4105336

16 years, 6 months

1
0
0 / 0

[Design of JBoss Web Services] - Integrating ws spi into jboss-javaee

by scott.stark＠jboss.org

The jboss-jaxws.jar spis are missing from the current jboss-javaee.jar assembly artifact, and the stax api in the https://svn.jboss.org/repos/jbossas/projects/javaee/trunk/jboss-jaxs-api/ project are not what is being used by the webservice project. We need to get the correct javaee 5 artifacts into maven so they can be incorporated into the jboss-javaee.jar assembly. Where should this be coming from? I guess I'll put out a 2.0.1.GA version of jboss-jaxws.jar to the maven2 repo, and take this from the jboss/jbossws/2.0.1.GA repo contents so I can finish up the annotation to metadata work in the metadata project. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105198#4105198 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4105198

16 years, 6 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: [Productivity] Level 4 - Production

by alessio.soldano＠jboss.com

"alessio.soldano(a)jboss.com" wrote : Anyway, generally speaking, I think the idea of having something like a WS log repository to query with different filters for getting information on both pre-defined and custom (the admin decides through the jmx-console) time period is definitively interesting. Some further thoughts on the ws log repository idea; this could be directly linked to what is written here http://www.jboss.com/index.html?module=bb&op=viewtopic&t=115661, that is in/out messages are captured by a RequestHandler as long as information about processing time, client IP and the receiving host. This data is then persisted (no data loss with server shutdown and/or redeployment, eventual support for cluster...). JMX-console allows to query those data and to start/stop log recording as long as setting how much info is to be saved. Query could even be based on the soap body, depending on how it is stored. Converter to stardard log formats could perhaps be added to allow eventual batch analysis and creation of graphical statistics / table, etc. Up to this, logs would be stack independent (Native, Metro, CXF). As far as I can see, adding more specific and interesting data (operation statistics, ws-security related info, etc.) could be possible with native stack, since it will require at least access to the metadata model. However this could be further investigated. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105136#4105136 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4105136

16 years, 6 months

1
0
0 / 0

[Design of JBoss Web Services] - JSR224

by scott.stark＠jboss.org

So I go to download the http://jcp.org/aboutJava/communityprocess/mrel/jsr224/ spec to get the details of @WebServiceRef, and find there is no spec. Rather there is this: anonymous wrote : | STOP - PLEASE READ | The JAX-WS 2.1 final specification uses and references the W3C WSDL Binding specification which was being defined in the WS-Addressing Working Group. The Binding spec was in the Candidate Recommendation stage ( and expected to go to Final Recommendation) when we did the final release of the JAX-WS specification, RI and TCK. Since then it has come to our attention that the Binding spec is not going to be made a Final Recommendation and will instead be replaced with an alternative specification. We believe we need to take corrective action to address this issue. Hence, we are temporarily removing access to the specification, RI and TCK to prevent any use of these until the specification issue is resolved. We apologize for any inconvenience caused. | | We plan to remove the dependence of the JAX-WS 2.1 spec on this "orphan" W3C spec asap and republish the specification along with the Reference Implementation and TCK as soon as possible. | How does this affect the metadata model? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105123#4105123 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4105123

16 years, 6 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: jUDDI tables dropped at server shutdown

by thomas.diesler＠jboss.com

I don't really understand why there is a need for two juddi implementations. If juddi.sar is no good we should fix that Specifically, I need to understand better why anonymous wrote : | we should deploy our juddi.war by default | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104911#4104911 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104911

16 years, 6 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 November 2007