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

[JBoss Portal Documentation] - Re: Quickstart 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 Simon and Chris ! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059145#4059145 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059145

16 years, 10 months

1
0
0 / 0

[Design of EJB 3.0] - Re: JBossEjbParsingDeployer can't handle EJB3 jboss.xml

by wolfc

As for the order: at one point we must have a full set of meta data attached for use in the SecurityDeployer & WebServices. Either we do parse & scan = complete or scan & parse = complete. Since xml overrides annotations my vote is for: scan then parse. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059133#4059133 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059133

16 years, 10 months

1
0
0 / 0

[Design of JBoss jBPM] - Maven2 Repository

by camunda

Hi! I wanted to set up a new project on maven2 today, but I haven't found too much versions there: http://repository.jboss.com/maven2/jboss/jbpm/ It would be nice to have the released versions available there. This should be part of release process I think. Currently I want to start with jbpm 3.2, but this is not available to maven :-( Any plans to add it there in the very near future? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059127#4059127 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059127

16 years, 10 months

1
0
0 / 0

[Design of EJB 3.0] - Re: JBossEjbParsingDeployer can't handle EJB3 jboss.xml

by adrian＠jboss.org

"bill.burke(a)jboss.com" wrote : IIRC, can't you just programmatically define your own order? Also, an annotation parsing deployer does not necessarily need to happen after classloader deployment so long as you have access to the .class file resources. (Javaassist). | Yes it does. How do you know that the related classes (e.g. the annotations themselves) have been deployed yet? That is something that I'm currently working on where you can have real classloading/deployment dependencies with the new VFS based classloader. Also, you need to know what .class files are actually in the classpath. e.g. maybe there is a filter in what will be the new META-INF/jboss-classloader.xml | <jboss-classloader> | <ignore-package>com.acme.notused</ignore-package> | </jboss-classloader> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059115#4059115 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059115

16 years, 10 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Deployer Documentation

by alesj

Yup, waiting for you to start a new thread. But I _had_ to reply to Bill and his not OO approach. :-) On Monday I can start with Reference Manual (and a simple example addition to existing User Guide) on the Deployers, since I think the changes that we (Adrian) will make will not be that drastic for me not to be able to fit them back in. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059112#4059112 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059112

16 years, 10 months

1
0
0 / 0

[Design of JBoss Profiler] - Repository jars + dlls

by kabir.khan＠jboss.com

I can only find jboss-profiler-jvmti.jar in repository.jboss.org. Can everything needed for my tests be added, so I don't have to install it manually? This would include the native stuff. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059111#4059111 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059111

16 years, 10 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: New Deployer changes - overview

by adrian＠jboss.org

DON'T POST HERE! This is an overview thread. Start new threads to discuss the issues raised here. Let's not have another 50 post tangled mess! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059109#4059109 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059109

16 years, 10 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Deployer Documentation

by adrian＠jboss.org

Ales wrote: anonymous wrote : | "bill.burke(a)jboss.com" wrote: | | IMO, there's just too much implicity in both the old and new deployment architecture. My experience writing the first deployer in this new architecture was that I had to dive through a lot of internal code to figure out what the hell was going on. It seems like this is getting worse with the new refactoring you did. I honestly don't care about saving one line of if attachment exists code. It actually makes the code more readable and more importantly, more understandable for people using your deployer as an example for writing their own. | | | I disagree with you. | If we can have a lot of stuff pre-written, to help and 'guide' the devs, than that's what we should do. And the new Deployers do exactly that. | | But then we should have a good documentation. :-) | I can start the MC RefManual with the Deployers if you guys need that asap. | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059108#4059108 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059108

16 years, 10 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Deployer Documentation

by adrian＠jboss.org

"adrian(a)jboss.org" wrote: As an aside, with those classes, it will also know that you don't want to be invoked for deploy/undeploy if there is no such attachment. i.e. no longer any need for the boiler place Code: if (unit.getAttachment(MyMetaData.class) == null) return; If you don't want this filtering, you can turn it off with Code: public MyDeployer() { super(MyMetaData.class); setAllInputs(true); } IMO, there's just too much implicity in both the old and new deployment architecture. My experience writing the first deployer in this new architecture was that I had to dive through a lot of internal code to figure out what the hell was going on. That's because there's never been documatation. The old framework was only ever a prototype so we could flush out requirements, its not surprising people did it wrong. | It seems like this is getting worse with the new refactoring you did. I honestly don't care about saving one line of if attachment exists code. It actually makes the code more readable and more importantly, more understandable for people using your deployer as an example for writing their own. | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059106#4059106 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059106

16 years, 10 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Too much implicity

by alesj

"bill.burke(a)jboss.com" wrote : | IMO, there's just too much implicity in both the old and new deployment architecture. My experience writing the first deployer in this new architecture was that I had to dive through a lot of internal code to figure out what the hell was going on. It seems like this is getting worse with the new refactoring you did. I honestly don't care about saving one line of if attachment exists code. It actually makes the code more readable and more importantly, more understandable for people using your deployer as an example for writing their own. | I disagree with you. If we can have a lot of stuff pre-written, to help and 'guide' the devs, than that's what we should do. And the new Deployers do exactly that. But then we should have a good documentation. :-) I can start the MC RefManual with the Deployers if you guys need that asap. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059102#4059102 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059102

16 years, 10 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