August 2006 - jboss-dev-forums - Jboss List Archives

[Design the new POJO MicroContainer] - Re: JBMICROCONT-100, lifecycle dispatch thread context class

by adrian＠jboss.org

Why? When you can do: | BeanMetaData metaData = context.getBeanMetaData(); | ClassLoader cl = Configurator.getClassLoader(metaData); | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964479#3964479 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964479

19 years, 8 months

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - Re: Ordering of .ear subdeployments

by bstansberry＠jboss.com

This change has broken the use case where a datasource is packaged in an ear with an ejb jar that use the datasource. See http://jira.jboss.com/jira/browse/JBAS-3503 for the problem. The testcase deploys test-cif.ear. The ear includes an ejb jar and a -ds.xml file for the datasource. The ejbs fail to deploy due to the inability to find java:/CIFTestDS in JNDI. Looking at the log, service jboss.jca:service=DataSourceBinding,name=CIFTestDS and the other datasource related services are started *after* the ejbs, which explains the failure. My *guess* as to what is going on is the services are ordered based on their ordering within the deployment descriptors. A side affect is those listed in application.xml come before those listed in jboss-app.xml. The ds can only be listed in jboss-app.xml, so it comes later. The JBAS-2904 work removed the subsequent comparator-based sorting that would have put the ds before the ejb jar. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964478#3964478 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964478

19 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: JBMICROCONT-100, lifecycle dispatch thread context class

by scott.stark＠jboss.org

Then shouldn't that protected method have its signature changed to accept the target ClassLoader? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964475#3964475 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964475

19 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: JBMICROCONT-101, circular dependency reporting

by scott.stark＠jboss.org

Ok, its all yours then. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964472#3964472 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964472

19 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: JBMICROCONT-101, circular dependency reporting

by adrian＠jboss.org

That isn't a feature request, it is a bug in the error reporting. :-) The demand is unresolved so IDepend is null. The code should be checking for that before asking for the context and using something like "**UNRESOLVED**" as the description. I'm going to rewrite this anyway. This code needs to move to the AbstractController rather than the deployer so it can check both JMX and bean dependencies together. The error thrown also needs to be "augmentable" with the "deployments missing deployers", etc. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964471#3964471 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964471

19 years, 8 months

1
0
0 / 0

[Design of POJO Server] - Re: JBAS-1841 - ServiceController/Microcontainer integration

by adrian＠jboss.org

I forget to mention that the POJO/JMX sides can now do dependencies on each other (which was the whole point of writing this thing in the first place :-) JMX injected into POJO | <bean> | <property name="Blah"><inject bean="test:type=MBean"/></property> | POJO injected into JMX | <mbean> | <attribute name="Blah"><inject bean="POJO"/></property> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964469#3964469 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964469

19 years, 8 months

1
0
0 / 0

[Design of POJO Server] - Re: JBAS-1841 - ServiceController/Microcontainer integration

by adrian＠jboss.org

I've nearly finished this, so I can soon start working on the new deployers. :-) * Things that need doing immediately: 1) Make the synchronization inside AbstractController only for state, like the old ServiceController. Currently when you do install() or change() it synchronizes to avoid concurrent access. This means that shutdown will hang if one of these operations hangs. e.g. an MBean is broken The shutdown thread can't enter the synchronized method. 2) There are a couple of things I found that need fixing in the old ServiceController during testing. These need to be backported to JBoss4. Most are just NPEs where errors/invalid configuration are not handled correctly. One however causes a broken state machine when the parsing of an invalid object name in a dependency leaves the MBean registered but not under the control of the ServiceController. The fix is trivial, it needs to catch Throwable instead of Exception to do the tidyup. Also, the use of ObjectNameFactory.create() is spurious in this code (that method factory is a helper for known valid ObjectNames), since this will throw java.lang.Error instead of the real MalformedObjectNameException * Things that need doing for the new deployers: 1) Rewrite the IncompleteDeploymentException to include pojo contexts. * Things that need doing longer term: 1) Test the trim/replace attributes in the ServiceController I think this will probably open a can of worms. :-) 2) Test XMBean 3) Add extra metadata options to -service.xml like constructor dependencies/injection | <server> | <constructor> | <arg type="SomeClass"><inject bean="Blah"/> | ... | 4) Make MBeanProxy injection be a CONFIGURED dependency as well as a CREATE/START injection. This is trivial and just needs testing. e.g. | <server> | <mbean> | <depends optional-attribute-name="Attribute" | proxy-type="SomeInterface">test:type=Depends</depends> | Currently if test:type=Depends is not installed it will fail when trying to use the proxy. The MBean should not reach the CONFIGURED stage until test:type=Depends is installed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964468#3964468 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964468

19 years, 8 months

1
0
0 / 0

[Design of POJO Server] - Re: First real SARDeployer porting issue

by scott.stark＠jboss.org

Ok, maybe that is what is needed. An alternative would be to allow the ClassLoadingDeployer to run last during the structural phase, and first during the deployment phase. Don't know if other deployers/aspects would benefit from similar alternate orderings. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964466#3964466 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964466

19 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - JBMICROCONT-101, circular dependency reporting

by scott.stark＠jboss.org

http://jira.jboss.com/jira/browse/JBMICROCONT-101 I have run into NPE type of failures a couple of times now when there is a circular dependency and want to improve this error reporting. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964465#3964465 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964465

19 years, 8 months

1
0
0 / 0

[Design of POJO Server] - New JMX Integration features.

by adrian＠jboss.org

I've added the following features to JMX deployments. 1) The ability to inject either a JMX object or a POJO object or one of its properties (and to be able to specify the dependent state so you can break circular dependecies). This works the same way as the MC inject. e.g. <mbean ... | <attribute name="Link"><inject bean="Something" property="whatever" state="Instantiated"/> 2) The ability to define an MBean as "On Demand" <mbean ... mode="On Demand"> or the whole deployment <server mode="On Demand"> | <mbean ...> | <mbean ...> | <mbean ...> | </server> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964463#3964463 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964463

19 years, 8 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 August 2006