September 2006 - jboss-dev-forums

[Design of POJO Server] - Re: Hot deploying deployers - deployer chains

by bill.burke＠jboss.com

"scott.stark(a)jboss.org" wrote : First, I'm not in agreement that hot deployment of deployers is needed. The only post bootstrap configuration I can see are aspects on the deployers themselves, but this can be a function of an individual deployment, not neccessarily a reconfiguration of the deployer. | | Second, explain how the tree is used given a DeploymentContext representing an ear with the full contigent of javaee components, and customized aspects like security and logging. | I don't think it is important to support the redeploy and undeployment of a deployer, but generalize deployment does seem important. I like my original idea of the .deployer archive and packaging subsystems like EJB3 and AOP in deployer archives. Makes it easy for people to add/remove/patch these subsystems. Maybe the JEMS installer makes this point moot, but I think we should retain some traditions here. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973081#3973081 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973081

19 years, 6 months

1
0
0 / 0

[Design of JBoss ESB] - Registry Service Design

by kurt.stam＠jboss.com

We will soon have an embeddedable JAXR/UDDI component using Apache Scout as the JAXR implementation, a local transport implementation to support local java calls, and a slightly modified jUDDI to support these direct java calls (and soon there after hopefully RMI calls too). OK so far so good. Now the ESB has access to any kind of XML registry (it'd be ebXML or UDDI), and by default it will use embedded jUDDI. Now what if other systems want to access this registry? I see 3 scenarios of how you could do this: 1. If the registry is embedded, those systems can use JAXR and RMI (Scout with our RMI-Transport) to connect to the UDDI embedded in the JBossESB. 2. Those systems can call to their very own embedded jUDDI, which is configured to use the same database. Or use their own registry database with somekind of replication. 3. What if the client is not java based? Then you could deploy juddi.war and point it to the same registry database (or in jboss - versions newer then 4.0.2 you already have juddi build-in when running 'all'.). Now you have a soap webservice you can go to (for UDDI). Do these scenarios seem right? Does it cover all real world needs? BTW I'm not talking about clustering and/or caching, we can worry about that later. We could take it to the next level and bring up a Registry Service in the JBossESB. All clients can/should connect to this one and it can query to other registries in your business. If we do this, what kind of XML protocol should we support? Our own, or both UDDI and ebXML. Do we need something like this for the GA release? I'd love some feedback on this :). --Kurt View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973073#3973073 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973073

19 years, 6 months

1
0
0 / 0

[Design of JBoss Remoting, Unified Invokers] - Re: change to client leasing

by tom.elrod＠jboss.com

Repository binary - http://repository.jboss.com/jboss/remoting/2.2.0.Alpha1/lib/ CVS tag - remoting_2_2_0_Alpha1 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973046#3973046 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973046

19 years, 6 months

1
0
0 / 0

[Design of JBoss ESB] - Re: EPR support in 4.0 GA

by arvinder

Just a note incase anyone is trying to use it immediately, there is a slight bit of hardcoding w.r.t xsd paths to get stuff to work, I am modifiying it and working through this in order to make paths generic. Once this is done, I'll need some input for missing fields. Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973037#3973037 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973037

19 years, 6 months

1
0
0 / 0

[Design of JBoss Remoting, Unified Invokers] - Re: change to client leasing

by ovidiu.feodorov＠jboss.com

... so nothing changes, from the Messaging perspective. Great. Is everything in CVS, so I can check out a snapshot and run our functional tests? Any chance you would tag a point release, so we can used a named dependency, instead of a snapshot? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973031#3973031 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973031

19 years, 6 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Action Processing Pipelines, updated Trailblazer etc...

by daniel.brum＠jboss.com

Guys, using XStream on both sides was just a convenience, nothing more. The TB is about showing how to use the Beta of the ESB features, nothing to do with writing banks and their systems, etc. I would not bother with re-writing those aspects of the TB now. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973029#3973029 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973029

19 years, 6 months

1
0
0 / 0

[Design of JBoss Remoting, Unified Invokers] - Re: change to client leasing

by tom.elrod＠jboss.com

You're right, if a Client has different config value for lease_period, will cause a different client invoker instance to be used. So is not an issue. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973025#3973025 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973025

19 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: Hot deploying deployers - deployer chains

by scott.stark＠jboss.org

The structure of DeploymentUnits in terms of tree is something we should be exposing since there is so much behavior based on this in terms of metadata defaults. In terms of the class loader metdata, let's just define a base class path based attachment type that can be added/retrieved from the Attachments spi. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973024#3973024 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973024

19 years, 6 months

1
0
0 / 0

[Design of JBoss Admin Console] - Re: JBossMQ vs JBoss Messaging

by prabhat.jha＠jboss.com

We need to modify build-distr.xml to copy the JBossMQ to default configuration. I do not know why it was taken out in the first place. I can go ahead and make this change if we agree. Yes, currently JBossMQ is only available in all config. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973020#3973020 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973020

19 years, 6 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Rearchitecture underway

by mark.little＠jboss.com

I've just checked in the latest changes along with unit tests to keep the code coverage high in the rosetta module. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973012#3973012 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973012

19 years, 6 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 September 2006