February 2008 - jboss-dev-forums - Jboss List Archives

[Design of JBoss ESB] - Re: Eclipse template wizard plugin directory structure

by Kevin.Conner＠jboss.com

The problem with going down this route is that the generated build.xml file could easily become inconsistent with what is required to compile/execute the quickstarts. At the moment these dependencies are handled within base-build.xml for all quickstarts, including the correct base-build.xml automatically pulls in the correct dependencies. To remove this would require setting up a 'context' for every version of the ESB we release (platform and project). We could certainly look at supporting this but I would then want to see this used by the quickstarts themselves. If the plugin and quickstarts use the same mechanism then we know that the plugin will work in all those cases. Kev View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132435#4132435 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132435

17 years, 10 months

1
0
0 / 0

[Design the new POJO MicroContainer] - New deployer stages

by adrian＠jboss.org

I've added three new deployer stages. POST_PARSE Some people are still doing processing in the Parsing Deployer which doesn't get invoked if the metadata is predetermined. You can use a POST_PARSE deployer to do this extra work (regardless of where the metadata came from). PRE_DESCRIBE This is mainly just for setting the default classloading rules. PRE_REAL We discussed the possiblity of this on a different thread. It basically allows the construction of two stage real deployers like the two stage classloading. i.e. PRE_REAL determines what dependencies should be satisifed before the deployment moves to the REAL stage. In practice the PRE_REAL is just a hack, since these dependencies should be defined on the POJOs rather than the deployments if you've done it properly. But it should allow the temporary/partial fixing of some problems until it is fixed properly. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132431#4132431 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132431

17 years, 10 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Eclipse template wizard plugin directory structure

by beve

How about I create a separate plugin for this? What I'd like to see is a plugin that creates the directory structure as discussed above. And ANT targets for building and deploying the artifact generated by the project. This would only be the <project-name>.esb. Any other suggestions? /Daniel View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132430#4132430 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132430

17 years, 10 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Command facade API

by tom.baeyens＠jboss.com

"richard.opalka(a)jboss.com" wrote : "heiko.braun(a)jboss.com" wrote : | | Use well specified, strongly typed API that allows the callee to work with a blackbox JBPM. | | | +1 please indicate how you would deal with the 2 things i mentioned in case of a strongly typed session facade. i refer to the graph retrieval problem and how to prevent that you get over a hundred methods in your session API. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132426#4132426 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132426

17 years, 10 months

1
0
0 / 0

[Design of OSGi Integration] - Re: Facade Questions

by adrian＠jboss.org

What you are struggling with is that we don't expose the MC api through the deployer api. The MC is an implement detail. The DeploymentStages create extra ControllerStates that are mostly different from the POJO states. But it does this "on the fly". If you don't have the deployers installed these states don't exist. See DeployersImpl. Equally, some of the controller states don't have deployer stages, they only relate to POJO/JMX/etc. We can add a DeploymentStage DeployerClient::getDeployerStage(String deploymentName); which will probably give you what you want? I don't know what you do if a deployment moves to **ERROR** or POST_CLASSLOADER, etc? :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132423#4132423 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132423

17 years, 10 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: how crucial are exception handlers ?

by heiko.braun＠jboss.com

Thanks to both of you. Now I get an idea. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132420#4132420 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132420

17 years, 10 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Eclipse template wizard plugin directory structure

by beve

Sure, we can leave it as it is. I was under the impression that this plugin was to be something that we could use in real projects and was the reason I wanted to see a different directory structure. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132418#4132418 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132418

17 years, 10 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Eclipse template wizard plugin directory structure

by Kevin.Conner＠jboss.com

The directory structure is deliberately mirrored on the quickstarts, please do not change this. We can look again at changing the structure at a later date but this must coincide with changing *all* the quickstarts. The generated project must link into conf/base-build.xml and must demonstrate the deployment options supported by the quickstarts. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132412#4132412 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132412

17 years, 10 months

1
0
0 / 0

[Design the new POJO MicroContainer] - JBMICROCONT-243 - parsing and managed objects

by adrian＠jboss.org

http://jira.jboss.com/jira/browse/JBMICROCONT-243 I don't understand this JIRA issue? It's true that the parser may not run if the metadata is passed in programmatically, but that doesn't effect the ManagedObjectCreator call. The parser deployer doesn't care where the metadata came from, it just looks for the attachment and asks the ManagedObjectFactory to create the ManagedObject from it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132411#4132411 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132411

17 years, 10 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Command facade API

by richard.opalka＠jboss.com

"heiko.braun(a)jboss.com" wrote : | Use well specified, strongly typed API that allows the callee to work with a blackbox JBPM. | +1 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132409#4132409 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4132409

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

jboss-dev-forums February 2008