April 2008 - jbossws-dev - Jboss List Archives

by Thomas Diesler

Heiko, Looking at http://jira.jboss.org/jira/browse/JBAS JBossAS-5.0.0.CR1 has 151 unresolved issues. Yesterday I was under the impression that the release was imminent, but that was obviously a false assumption. I think it's therefore unlikely that CR1 will come out in time before our code freeze. I changed the target version for 3.0.2 back to Beta4 http://jbws.dyndns.org/mediawiki/index.php?title=Supported_Target_Containers cheers -thomas -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

16 years, 9 months

2
1
0 / 0

[Design of JBoss Web Services] - Re: JAXB in cxf/metro

by thomas.diesler＠jboss.com

good, I'll do that View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4143083#4143083 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4143083

16 years, 9 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JAXB in cxf/metro

by heiko.braun＠jboss.com

Agreed, We should align them across stacks and make sure the AS uses the most recent one. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4143074#4143074 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4143074

16 years, 9 months

1
0
0 / 0

Setup propper QA and wiki hosting

by Thomas Diesler

Hi Mark, with this recurring issue that I would like to make another attempt of progress. Could you please comment on http://jira.jboss.org/jira/browse/JBWS-2126 and assign appropriately to whoever needs to do the next step. cheers -thomas -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

16 years, 9 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JAXB in cxf/metro

by richard.opalka＠jboss.com

jaxb is widely used library -> it must take care of bc compatibility -> jaxb 2.1.6 is bc with jaxb 2.1.4 -> cxf works with jaxb 2.1.4 -> cxf will work with jaxb 2.1.6 -> #2 we should let the AS define the jaxb version and not deploy it Just a simple math transitivity ;) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4143070#4143070 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4143070

16 years, 9 months

1
0
0 / 0

[Design of JBoss Web Services] - JAXB in cxf/metro

by thomas.diesler＠jboss.com

Currently we have the following jaxb versions native=2.1.6 cxf=2.1.4 metro=2.1.6 That generally opens the following question: #1 Should we align the jaxb version with the respective stack and deploy it to the AS #2 Should we let the AS define the jaxb version and not deploy it views ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4143063#4143063 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4143063

16 years, 9 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: http://org.jboss.ws/http#chunksize

by thomas.diesler＠jboss.com

I moved this to the dev forum and here is your jira for it http://jira.jboss.org/jira/browse/JBWS-2124 good work, btw View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4143061#4143061 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4143061

16 years, 9 months

1
0
0 / 0

Re: Running the jbossws testsuite against cxf-2.0.5

by Thomas Diesler

... sure. Here you go http://jbws.dyndns.org/mediawiki/index.php?title=Building_From_Source#Che... Daniel Kulp wrote: > Thomas, > > When logging the jira issues with CXF, it would help if you could put a > link to the instructions on how to checkout and run the given test into > the issue. Very few of us (possibly only me) have even tried to run the > JBoss tests so there isn't much (any) familiarity. > > Thanks! > Dan > > > > On Tuesday 08 April 2008, Thomas Diesler wrote: >> Hi Folks, >> >> we (jboss) are in the process of migration our jbossws-native tests to >> a common testsuite that will run against all supported stacks. >> >> http://jbws.dyndns.org/mediawiki/index.php?title=JBossWSSupportedStack >> Comparison >> >> We expect to see a number of failures with the respective stacks for >> which I plan to create individual jira issues. All failing tests will >> get listed in our exclude file and hance will make it into the next >> jbossws-cxf release notes. >> >> Over the course of the next few releases we can then work to reduce >> these failures if needed. >> >> cheers >> -thomas > > > -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

16 years, 9 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Web Service Transactions Implementation: Configuring WS

by mark.little＠jboss.com

And the answer is that my network connection died ;-) WS-A talks in terms of EPRs with extensible header information and ReferenceProperties (WS-A 2004) and ReferenceParameters. Only the latter two (or one, depending on your version) are meant to be opaque to the consumer and used only by the EPR minter. The EPR isn't opaque though. Like all WS-* specifications and standards, we didn't say anything about language bindings: we are implementation language agnostic. However, I do find it strange that information like To, RelatesTo and MessageId aren't available through the Java API. I don't recall that being part of JSR 261 (before it died), so maybe this is something that is under specified in JAX-WS? But the conclusion is: it's not a problem with WS-A :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142843#4142843 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142843

16 years, 9 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: jbossws-common vs. jbossws-framework

by heiko.braun＠jboss.com

Let's put it another way: It's depency issue. Currently stacks do have a dependency on SPI and Common, but not on framework. And that's the way it needs to be. If we throw common and framework together, stacks (container as well) start having a dependency on the framework.jar which would leak SPI implementation details to the dependee. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142707#4142707 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142707

16 years, 9 months

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 April 2008