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

[Design of POJO Server] - Re: Implicit container dependencies

by scott.stark＠jboss.org

This seems to be effectively pushing the mechanism for configuring the mc component providing the admin object to the jca layer. That's fine and makes sense. So if given an admin object (type, name) pair, there is a stable jca component containers can declare a dependency on, we are good. The details will fall to the admin object deployment. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032443#4032443 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032443

19 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: Implicit container dependencies

by weston.price＠jboss.com

In other words, the JmsJNDIProvider effectively provides 'AdminObject' like behavior today. This is currently how we do JMS provider integration. These facilities should be moved to the JCA/JMS adapter to be more in line with the JCA specfication. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032441#4032441 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032441

19 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: Implicit container dependencies

by bill.burke＠jboss.com

The problem with implicit dependencies is that MDB's, traditionally, will create the topic/queue by default if it does not already exist. Please add the nested first deployment ordering. BTW, I don't understand why the ordering matters. It works like this right? | for (Deployer deployer : deployers) | { | for (Deployments deployment: deployments) deployer.process(deployment) | } | Why doesn't the Queue/Topic get deployed before the MDB anyways? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032438#4032438 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032438

19 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: Implicit container dependencies

by weston.price＠jboss.com

Feasibly those admin objects that are hosted remotely should be bound into our local JNDI tree with a proxy/wrapper for the remote admin object. The generic jms project is a good example of this integration approach. Note, this is effectively what the JmsJNDIProvider does today, or at least it can do. What we do in the case of a remote destination is bind to JNDI tree of the remote resource directly, or we force some sort of bridge layer (ie the WASMQ integration stuff on the Wiki). While this works, it effectively removes any dependency control we might have until the actual point of activation where we attempt the lookup on the destination. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032436#4032436 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032436

19 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: Implicit container dependencies

by scott.stark＠jboss.org

How does this apply to an mdb accessing a remote destination though? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032432#4032432 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032432

19 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: Implicit container dependencies

by weston.price＠jboss.com

Technically we should be integrating destinations, connection factories etc via the AdminObject facility of JCA and establishing the dependencies in this manner. At the very least, we need to consider reworking some of this. By all rights, the JmsLookupProvider should dissapear as it is JBoss specific and prohibts using the JCA/JMS adapter in other app server environments. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032430#4032430 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032430

19 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: Implicit container dependencies

by scott.stark＠jboss.org

To ease this compatibility issue, and address a long outstanding issue with not being able to specify deployment module level dependencies (mdb.jar depends on test-destinations-service.xml), I think a feature of the structure parse should be to order the DeploymentContexts. This would be a superset of the old Russian doll ordering. One should be able to declare the directed graph of DeploymentContexts such that a BFS traversal from the deployment root runs the deployment through the deployers in the declared order. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032429#4032429 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032429

19 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Implicit container dependencies

by scott.stark＠jboss.org

One problem showing up in the mdb tests is that since we don't order deployments using packaging depth (Russian doll thing), tests that include jms destinations in the deployment are failing because the mdb container is not specifying a dependency on the jms destination. Since the actual jmx name/kernel name of the component that supplies the destination is arbitrary, one way to address this would be for the mdb container to declare a dependency on the supplier of the jndi name for the destination. Alternatively, and more correctly, we need the jms destination injected into the container. The issue with this is that we need a policy plugin for resolving the source of the destination provider. There could be a JndiLookupProvider, or jms specific providers that map the destination name onto the mc component name/property to inject. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032425#4032425 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032425

19 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: error message suck, but where to commit?

by scott.stark＠jboss.org

https://svn.jboss.org/repos/jbossas/projects/microcontainer/branches/2_0/ View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032421#4032421 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032421

19 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - error message suck, but where to commit?

by bill.burke＠jboss.com

I want to clean up the error message from IncompleteDeploymentException. Its completely incomprehensible unless you've worked with the Microcontainer. The quest is, where do I commit these changes? 2_0 branch? and/or trunk? What MC branch is being developed for AS HEad? Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032418#4032418 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032418

19 years, 1 month

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 March 2007