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

[Deployers on JBoss (Deployers/JBoss)] - Re: Ear deployment ordering broken in trunk

by adrian＠jboss.org

The depenendencies work at the STAGE level, not the flow level. They are primarily being introduced for classloading dependencies, so one deployment that depends upon another module won't create its classloader until a dependent classloader is constructed (and vice-versa at undeployment). Similary, there is a new "INSTALL" stage, which is where the real REAL deployers :-) should be. i.e. the ones that create (it should be register) the runtime objects. So you can do things like "All or Nothing" by requiring that all deployments in a group, (e.g. an EAR) have passed their "REAL" stage successfully before they are all moved to the "INSTALL" stage. In that context, "REAL" is not such a good name anymore. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062343#4062343 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062343

18 years, 9 months

1
0
0 / 0

[Design of JBoss Wiki] - Re: Portal 2.6 support...

by thomas.heute＠jboss.com

Michael do you mind, trying the Wiki portlet on 2.6 and list the issue(s) ? Maybe Tomasz could benefit from your help on resolving those issues too. That would be great ! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062342#4062342 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062342

18 years, 9 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: TODO: Interceptors

by vickyk

Is some one still working on this ? anonymous wrote : This work has already been started in the jboss-jca prototype project (using AOP). Where can I get the jboss-jca project which contains this work? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062341#4062341 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062341

18 years, 9 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Uniquely identifying services and actions

by tfennelly

hehehe, I think we're playing word games again ;-) For sure, the names would be hierarchical and the .esb name would be beside the service name and not the action name. For what I was suggesting, yes "ESB Instance" would simply to represented by the name of the .esb. It's already unique so there's no need to invent another name - and anyway, another name (e.g. defined in the .esb jboss-esb.xml config) wouldn't help someone trying to track back from a report to the actual service/action definition. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062340#4062340 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062340

18 years, 9 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: TODO: Interceptors

by adrian＠jboss.org

This work has already been started in the jboss-jca prototype project (using AOP). There's another thread about it somewhere. It's going to be done in the old code. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062338#4062338 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062338

18 years, 9 months

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - Re: Ear deployment ordering broken in trunk

by wolfc

I still don't get it for an EAR. In this case there is: ear = client jar + ejb jar (no metadata / javaee 5) Since it's going depth first, I don't get a chance to register dependencies, because they are unresolvable without the ejb jar being deployed (/ parsed). So here we see it dive into the client jar: 2007-07-10 10:37:58,824 INFO [org.jboss.ejb3.deployers.AppClientScanningDeployer] mainClass = class com.sun.ts.tests.ejb30.bb.session.stateless.annotation.appexception.annotated.Client | 2007-07-10 10:37:58,876 DEBUG [org.jboss.ejb3.deployers.Ejb3ClientDeployer] deploy vfsfile:/home/carlo/work/jboss-head/build/output/jboss-5.0.0.Beta3/server/cts/tmp/jsr88/ejb3_stateless_appexception_annotated.ear/ejb3_stateless_appexception_annotated_client.jar | 2007-07-10 10:37:58,877 DEBUG [org.jboss.ejb3.deployers.Ejb3ClientDeployer] Creating client ENC binding under: ejb3_stateless_appexception_annotated_client | 2007-07-10 10:37:58,898 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.sun.ts.tests.ejb30.common.appexception.AppExceptionIF in application-client.xml of ejb3_stateless_appexception_annotated_clientnot used by any EJBs | 2007-07-10 10:37:58,913 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.sun.ts.tests.ejb30.common.appexception.RollbackIF in application-client.xml of ejb3_stateless_appexception_annotated_clientnot used by any EJBs View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062326#4062326 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062326

18 years, 9 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Uniquely identifying services and actions

by mark.little＠jboss.com

OK, once again and this time trying to get the formatting right ;-) | <service>:<action> | | or | | <ESB instance>:<service>:<action type>:<action instance> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062325#4062325 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062325

18 years, 9 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Uniquely identifying services and actions

by mark.little＠jboss.com

"tfennelly" wrote : "mark.little(a)jboss.com" wrote : "tfennelly" wrote : Couldn't the .esb name also be used as part of the local/global name e.g. "shopping-service.esb". We'd probably need to get the deployer to make it available somewhere, but that wouldn't be a big job. | | | | If we're looking to report on individual actions, then I'm not sure this will help. | | It would help because it's unique on a per AS/esb-service instance. It would help because it helps a reader of any report/log to narrow down to the .esb instance. Before you the service/listener/action name can mean anything, you surely need to know this (context). | | Then on a per .esb instance, the service/listener/action needs to be uniquely identified. OK, but this comes back to my question: what are we trying to identify? If it's *just* the Actions then we don't need this. If it's *just* the services then this helps. However, I think it should be *both* Actions and services (either together or individually). I'd have thought an Action should be identified within the scope of the service in some hierarchical manner. For example: : or <ESB instance>::<action type>:<action instance> The latter just in case we want to differentiate between multiple instances of the same Action within a service. If that's the case then what you mention would be the <ESB instance>, right? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062323#4062323 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062323

18 years, 9 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Uniquely identifying services and actions

by tfennelly

"mark.little(a)jboss.com" wrote : "tfennelly" wrote : Couldn't the .esb name also be used as part of the local/global name e.g. "shopping-service.esb". We'd probably need to get the deployer to make it available somewhere, but that wouldn't be a big job. | | If we're looking to report on individual actions, then I'm not sure this will help. It would help because it's unique on a per AS/esb-service instance. It would help because it helps a reader of any report/log to narrow down to the .esb instance. Before you the service/listener/action name can mean anything, you surely need to know this (context). Then on a per .esb instance, the service/listener/action needs to be uniquely identified. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062306#4062306 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062306

18 years, 9 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Uniquely identifying services and actions

by mark.little＠jboss.com

"tfennelly" wrote : Couldn't the .esb name also be used as part of the local/global name e.g. "shopping-service.esb". We'd probably need to get the deployer to make it available somewhere, but that wouldn't be a big job. If we're looking to report on individual actions, then I'm not sure this will help. However, Tom did start out asking: anonymous wrote : | "Do we have a good way of uniquely identifying a service or action?" | so maybe the first thing to agree on is what we want to identify: service, action or both. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062291#4062291 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062291

18 years, 9 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 July 2007