June 2007 - jboss-dev-forums - Jboss List Archives

[Design of JBoss Web Services] - Re: The JBossWS build is a joke - the project is unmaintaina

by adrian＠jboss.org

"thomas.diesler(a)jboss.com" wrote : I already updated to the new deployer architecture | | http://jbws.dyndns.org:8280/hudson/job/Core-Tests-AS-5.0/57/changes :-) Ok, but my other concerns still stand. 1) Fix the build so it is reproducable 2) Don't reinvent the deployers framework 3) Fix the error handling 4) Reuse the already developed code instead of re-inventing it and introducing alternate bugs. If it is doesn't quite do do what you want then add some new callbacks like the accepts() I added to the parsing deployers so EJB3 can do its hacks. :-) One example of (2) is how do I modify the webserivices metadata with a new deployer? I can't. I have to use a different api, the DeployersHook to do this. This is just stupid. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059201#4059201 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059201

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: The JBossWS build is a joke - the project is unmaintaina

by adrian＠jboss.org

I'm going to go back to the jbossws codebase instead of the varia strategy and try to fix the build so at least it becomes reproducable. Once that is done, I'll do the updates for the new deployers. Then we can finally do a release and get webservices working again in the appserver. Even after this, there are lots of issues about whether webservices should be depending on things like ejb3 at all. It should certainly have access to its metadata for deployment purposes, which is one of the reasons we have started a "metadata" project so projects can share each others models. Webservices seems to have one (WebservicesMetaData) which should be moved there. I don't understand why you wrote your own parsing routines instead of using the ObjectModelParsing deployer. Well, actually I do, its because you're doing some stupid double parse where you first parse to DOM to check the namespace then parse again using JBossXB????? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059197#4059197 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059197

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: The JBossWS build is a joke - the project is unmaintaina

by thomas.diesler＠jboss.com

I already updated to the new deployer architecture http://jbws.dyndns.org:8280/hudson/job/Core-Tests-AS-5.0/57/changes View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059195#4059195 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059195

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: The JBossWS build is a joke - the project is unmaintaina

by adrian＠jboss.org

Anyway, back to the reason why I want to modify the jbossws project. I'm trying to integrate the new deployer updates: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=112181 I started to copy the code into varia as a temporary measure so at least I know what versions I'm compiling over and the integration gets maintained in step with the JBossAS code, like EJB3. What do I find, you've reinvented the wheel again (the deployers framework) with something called DeployerHooks. Why?????? I also started commenting a number of other stupidities like using the Thread Context Classloader instead of the DeploymentUnit.getClassLoader() and the ever handling is the usual mess. e.g. aop has the same problem: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058739#4058739 But more importantly, the DeploymentContext is used everywhere! Even though this has been deprecated method from the start with a comment on getDeploymentContext() saying "think about it before using this method". Not only that it is referenced inside JBossWS itself, so I can't even just rewrite the deployers inside JBossAS (as a temporary measure) because the api is broken in jbossws-spi.jar I can understand you having your own abstraction for deployment that is a good thing. But not when you are just munging http://en.wikipedia.org/wiki/Munging somebody else's api and exposing implementation details that should never have been exposed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059193#4059193 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059193

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - The JBossWS build is a joke - the project is unmaintainable

by adrian＠jboss.org

To update jbossws to the new deployers, I must have had to modify at least three files that organise thirdparty dependencies. But even having done that, it didn't build the jboss50 integeration. So I went to that directory and did a build there, and I got this: | [ejort@warjort jboss50]$ ant | Buildfile: build.xml | | prepare: | | thirdparty-init: | | thirdparty-get: | | thirdparty-classpath: | | thirdparty: | | init: | | BUILD FAILED | /home/ejort/jbossws/integration/jboss50/build.xml:41: Not available: ${jboss50.home}/client/jboss-ejb3-client.jar | Why is it compiling over non-versioned jars??????!!!!!!! This makes the whole build unreproducable. How do I know which version of jboss-ejb3-client.jar I need to reproduce a customer problem from source? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059190#4059190 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059190

17 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Thinking about transition attrs

by kukeltje

and please file a jira issue for making this exception more clear View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059167#4059167 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059167

17 years, 3 months

1
0
0 / 0

[JBoss Portal Documentation] - Docs 2.6 GA have been frozen

by julien＠jboss.com

No more updates, thanks for all the hard work you all did during the last 3 days. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059162#4059162 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059162

17 years, 3 months

1
0
0 / 0

[JBoss Portal Documentation] - Re: Reference Guide 2.6 update

by thomas.heute＠jboss.com

Everything looks fine to me, i fixed what i found and synced with 2.6. There are still a bit of content overflow i think though. Thanks a lot Sohil and Bolek ! Julien... Thanks for fixing the JSF+bridge+Facelet last minute bug ;) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059151#4059151 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059151

17 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Maven2 Repository

by kukeltje

not sure who did this. It is an old version with a recent date on it. Normally jbpm releases are on http://repository.jboss.com/jbpm/. But don't follow the releasenumbers folder at the higest level. Things changed with jbpm 3.2 so go in jpdl first View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059147#4059147 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059147

17 years, 3 months

1
0
0 / 0

[JBoss Portal Documentation] - Re: User Guide 2.6 Update

by thomas.heute＠jboss.com

Everything looks fine to me, i fixed what i found and synced with 2.6. Thanks a lot Chris, it was a lot of work to redo all the management part ! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059146#4059146 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059146

17 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

jboss-dev-forums June 2007