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

[Design of POJO Server] - Re: Handling more complex properties in a ManagedComponent

by bytor99999

Thanks Scott. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052158#4052158 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052158

18 years, 10 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Removing dependency on concurrent.jar

by kabir.khan＠jboss.com

Scott/Dimitris Are there any plans for a properly tagged common-core 2.2.0 release soon? I want to release aop alpha5 soon View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052153#4052153 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052153

18 years, 10 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Rework of jBPM deployment within JBoss

by david.lloyd＠jboss.com

"estaub" wrote : anonymous wrote : Though I've always disagreed with storing the process archive (especially the classes) in the database. | | Don't forget about clustering. I haven't - you'd do clustering in the exact same way you would with any other J2EE archive, like an EAR or WAR or whatever. It's a problem that has already been solved - and not by storing the archive in the DB. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052147#4052147 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052147

18 years, 10 months

1
0
0 / 0

[Design of JBoss jBPM] - what's wrong with deployment

by bill.burke＠jboss.com

Let me expand on why I don't like JBPM deployment model: * First of all, if you are deploying via an ANT script or the designer, these mechanisms need a database and knowledge how to connect to it. This requires the user to either set up a database (MYSQL/Oracle), or use JBoss's embedded Hypersonic. The user then also has to configure * I don't like the Servlet mode of configuration at all. WHy? Because its inconsistent with the way Seam deploys JBPM and inconsistent with they way every other JBoss project does deployment. There is a huge problem at JBoss.org at the moment. Every project is more interested in being portable to other non-JBoss environments than taking advantage of the JBoss platform and becoming one, integrated consistent suite. Take deployment for instance: Seam does it different than JBPM which does it different than ESB which does it different than AppServer wich does it different than Drools. I brought ESB into the JBoss deployment model, I'd like to do the same for JBPM. We need to start being consistent across JBoss.org projects. This way we can start writing generic tools and frameworks that can abstract things like deployment and write a portability layer to other application servers. JBoss 5 kernel does a lot to modularize things and the JBoss Embedded project is where I want to write this portability layer. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052146#4052146 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052146

18 years, 10 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Rework of jBPM deployment within JBoss

by kukeltje

ok, I was mislead by the -ds postfix... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052145#4052145 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052145

18 years, 10 months

1
0
0 / 0

[Design of JBoss jBPM] - RAR

by bill.burke＠jboss.com

"kukeltje" wrote : anonymous wrote : A RAR would be limited and you would still need to deploy 2 separate files, a pd-ds.xml file, to define the process instance, and the .par file (or .jpdl file). Where in a JBoss deployer, its just one file and less metadata to write. | | Not completely. It is not really a pd-ds.xml but a jbpm-ds.xml. Multiple processdefinitions can share the same jbpm database. In fact, if you have a separate ds for each process you also have to deploy the console app multiple times to connect to the different ds's. You're missing my idea. A JBoss -ds.xml file really isn't solely a datasource definition, it is an outbound adapter definition/configuration. Each process definition would be a an instance/activation of the JBPM RAR resource adapter. Just like a datasource in JBoss is an activation of the JDBC RAR. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052138#4052138 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052138

18 years, 10 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Rework of jBPM deployment within JBoss

by kukeltje

anonymous wrote : A RAR would be limited and you would still need to deploy 2 separate files, a pd-ds.xml file, to define the process instance, and the .par file (or .jpdl file). Where in a JBoss deployer, its just one file and less metadata to write. Not completely. It is not really a pd-ds.xml but a jbpm-ds.xml. Multiple processdefinitions can share the same jbpm database. In fact, if you have a separate ds for each process you also have to deploy the console app multiple times to connect to the different ds's. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052119#4052119 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052119

18 years, 10 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Quickstarts

by Kevin.Conner＠jboss.com

The spring quickstarts have now been updated and tested - spring_aop (all combinations) - spring_helloworld (all combinations) - spring_jpetstore (all combinations) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052117#4052117 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052117

18 years, 10 months

1
0
0 / 0

[Design of JBoss ESB] - Re: ESB Monitoring and Metrics : what should be monitored?

by mark.little＠jboss.com

Tom, I'd start to make progress based on this feedback. This will always be a moving target to some degree, but what's been mentioned here make a good first pass. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052113#4052113 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052113

18 years, 10 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: strategic ramblings

by bill.burke＠jboss.com

I don't think so. As I said in private emails, its just a matter initializing the appropriate contexts and triggering Seam deployment. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052112#4052112 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052112

18 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums June 2007