March 2009 - jbossws-dev - Jboss List Archives

[Design of JBoss Web Services] - Re: JBossWS Test Approach

by alessio.soldano＠jboss.com

A side note to make this clear to anybody not familiar with the jbossws testsuite. The classpath being dicussed here is of course the one used on client side in an integration test. Most of those tests deploy an endpoint on the current jboss instance; the endpoint thus actually uses the right classpath. It's just a matter of client classpath. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215774#4215774 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215774

15 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBossWS Test Approach

by alessio.soldano＠jboss.com

My point of view here is that we're evaluating this still a bit early. Let me explain, the problem here is that the AS is not completely mavenized yet. In particular the AS testsuite is not run against maven artifacts yet and that's IMHO one of the reasons why almost nobody besides us cares about updoading snapshots of the org.jboss.jbossas artifacts to the repo. Once the process will be completed (don't know when, but the work is being done even while we discuss this here now), I think we will be pretty sure we're testing against the right artifacts. This said, the specific failures that made us to stop and think about our testing approach were caused by some mistakes we actually did in the webservice module pom.xml in the AS. IOW it didn't have the right dependencies which were instead specified in the container integration pom.xml files. Of course this caused the trunk and 5_x branch only to fail, but I fixed that. The whole "exclusion game" in the stacks' testsuite pom.xml is not required anymore, there're few dependencies still specified there and they're quite straightforward. Finally, considering we're using maven for the project, I think it's important to run tests using surefire. IOW my point of view is that either we use this tool (maven) completely or we don't use it (which currently is not an option given the direction taken 1 year ago by the whole AS development). Basing the tests on maven dependencies was the most natural solution when the mavenization took place, what would you suggest instead of that? I don't like that much the idea of specifying the surefire additionalClasspath with a list of jar from the curent AS... any other idea? After all, we also get advantages from using maven dependencies to build test classpath, otherwise we need keep track of jar changes (names, position), addition of jars (while we simply get the new dependency for free when somebody updates the dependency in an artifact we include), etc. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215771#4215771 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215771

15 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBossWS Test Approach

by richard.opalka＠jboss.com

Please, let me know your opinion on this problem. I'd like to start how to solve it discussion soon ;) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215225#4215225 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215225

15 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBossWS Test Approach

by richard.opalka＠jboss.com

"richard.opalka(a)jboss.com" wrote : it wastes our development time Because: we have to review and fix dependencies (usually exclusions) each time some tests start failing because of classpath inconsistency (applies to moving AS version only) we have to upload maven artifacts to the repo if there's no other option available (AS upload to maven repo takes ~1 hour and it fails sometimes lately). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215221#4215221 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215221

15 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBossWS Test Approach

by richard.opalka＠jboss.com

"richard.opalka(a)jboss.com" wrote : we don't test against AS distributions but against local maven repository This is fundamental problem for me. There are two types of AS we're testing against to consider here: released AS GAs - current testing approach works properly for it moving AS branches/trunks - current testing approach is highly error prone for it And because our testing approach is identical for released AS GAs and moving AS branches/trunks we should use AS distributions jars only to prevent this problem. In that case you'd be always up2date with jars in the distribution and there'd be no overhead to exclude dependencies on regular basis, upload maven artifacts, ... etc. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215211#4215211 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215211

15 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBossWS Test Approach

by richard.opalka＠jboss.com

"richard.opalka(a)jboss.com" wrote : it's error prone approach We're using maven surefire plugin to invoke our junit integration tests. The problem is our tests are not just java component tests but they test whole JBossWS integration to JBossAS. The concrete problem is we're using maven dependencies mechanism to configure our tests classpath. Unfortunately this introduces many defects to our tests: We're not testing AS using AS provided libraries in distribution We're using libraries from local maven repository where many of these libraries has wrong version (because of outdated dependency exclusions) we don't have control over which version of particular component jar will be used for testing when there are two libraries of the same component with different version. The only way to achieve it is to use maven dependency exclusions (a lot of work without any evident added value). These exclusions should be updated on daily basis when testing AS moving branches/trunks. we're using out of date libraries for moving AS versions - many updates of the required dependencies are not released to the maven repository To solve this AS maven artifacts (SNAPSHOTS) should be uploaded to maven repo on daily basis. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215196#4215196 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215196

15 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBossWS Test Approach

by richard.opalka＠jboss.com

I'd like to start discussion about above JIRA issue. I don't like our current testing approach because: it's error prone approach we don't test against AS distributions but against local maven repository it wastes our development time I'll explain each point in next posts. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215183#4215183 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215183

15 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - JBossWS Test Approach

by richard.opalka＠jboss.com

This thread is related to JBWS-2530. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215179#4215179 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215179

15 years, 3 months

1
0
0 / 0

JBossWS 3.1.1 dates

by Alessio Soldano

Hi, now that JBossWS 3.1.0.GA is out, here is the schedule for the next release: JIRA freeze: 13-March-2009 Code freeze: 11-April-2009 Expected release: 24-April-2009 Cheers Alessio -- Alessio Soldano Web Service Lead JBoss, a division of Red Hat

15 years, 3 months

2
1
0 / 0

[Design of JBoss Web Services] - JBossWS CZJUG Presentation

by richard.opalka＠jboss.com

Downloads available at: http://mediacast.sun.com/users/jakub.podlesak/media/CZJUG2009.01-jboss-ws... Enjoy ;) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214496#4214496 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214496

15 years, 3 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 March 2009