[Deployers on JBoss (Deployers/JBoss)] - Re: jee module's alt-dd
by adrian＠jboss.org
"scott.stark(a)jboss.org" wrote :
| Good point, the EarStructure is where this should be done. The AltDD interface would need to be in the deployer project so that the general handling of the alt path can be handled in AbstractVFSParsingDeployer.
|
| If were using the AltDD interface as the typed path/key, wouldn't the programtic usage be:
|
| | addAttachment(Class<T> type, T attachment);
| | VFSDeployment d = new VFSDeployment(ejbjar);
| | AltDD altDD = ...("al.ternatelocation");
| | d.addAttachment(AltDD.class, altDD);
| |
|
You could use a class rather than a String to recognise the AltDD,
but you'd need more than one.
Remember a deployment can be both an EJB and a Web Deployment,
e.g. webservices where the web metadata is constructed programmatically
by the ws deployers
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139623#4139623
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139623
16 years, 2 months
[Design of JBoss ESB] - Re: Features of JBoss Messaaging Message Bridge present in E
by Kevin.Conner＠jboss.com
Yep, I agree that this is not a QoS setting and is purely the JMS acknowledge mode. I obviously misunderstood the question as I thought that was what you were asking for, apologies for this. :)
We have been holding a face 2 face this week in Newcastle (UK) and have the development team and other parties involved. Part of this meeting has focussed on a new transport architecture which will centralise all of these aspects, providing the ability for us to enforce policies (such as QoS) in a more generic manner. This development stream will occur in parallel with the current trunk and will be a big leap forward in the capabilities of the ESB.
At present we may not be quite there to satisfy your requirements but I can promise you that it is coming down the pipeline. Any input you wish to make into this process would be greatly appreciated.
Kev
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139593#4139593
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139593
16 years, 2 months
[Design of JBoss jBPM] - Re: New jBPM Console
by tom.baeyens＠jboss.com
"mark.proctor(a)jboss.com" wrote : "fady.matar" wrote : The application will be built on top of JBoss Seam + Richfaces
|
| I've made this point before. The web technologies used for jBPM should be aligned with what we are doing with Drools. Mic has proven his stack works and has had great success. I really would recommend you don't go down the RichFaces route.
Similarly I asked the rethoric question: "Why can't drools console be build in JSF and so be aligned with jBPM ?"
You ignore the fact that JSF knowledge is much wider spread. Which means that buiding the site in JSF makes it easer for us to deliver JSF components which will be an interesting asset for our project. Also JSF related expertise is easier to find/get/manage.
Apart from that, I don't see GWT being the strategic direction for JBoss. I only see drools using it within JBoss. I see JBoss in general as somewhat neutral (seam supporting many UI techs) but a big tendency towards JSF related technologies.
>From my perspective, all in conclusion, the drools GWT route currently doesn't have enough weight to make it an easy decision.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139572#4139572
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139572
16 years, 2 months