[Design of EJB 3.0] - Re: Unique JNDI Names
by jaikiran
"ALRubinger" wrote :
| Have we been wrong in this all along? Looks like non-unique EJB names are legal so long as they're in different JARs.
|
|
Yeah, although i did start a discussion about this a few months back in our user forum, i never pushed it to a logical end http://www.jboss.org/index.html?module=bb&op=viewtopic&t=143237
"ALRubinger" wrote :
| @see https://jira.jboss.org/jira/browse/JBPAPP-2124
|
That exception shows:anonymous wrote :
|
| 16:22:33,539 WARN [AbstractDeploymentContext] Unable to register deployment mbean refspath.ear-EJB-metrics-instance
| javax.management.InstanceAlreadyExistsException: jboss.deployment:id="refspath.ear-EJB-metrics-instance",type=Component already registered.
| at org.jboss.mx.server.registry.BasicMBeanRegistry.add(BasicMBeanRegistry.java:756)
| at org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean(BasicMBeanRegistry.java:233)
| Caused by:
| java.lang.IllegalStateException: refspath.ear-EJB-metrics-instance is already installed.
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:716)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:540)
| at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:121)
| at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:51)
| at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
| at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
| at <unknown class>.<unknown method>(Unknown Source)
| ... 26 more
| 16:22:34,265 WARN [HDScanner] Failed to process changes
which actually is a MC thing and our lack of understanding/control of what a component name's scope is http://www.jboss.org/index.html?module=bb&op=viewtopic&t=154305
And furthermore, the MBean that MC is trying to register:
jboss.deployment:id="refspath.ear-EJB-metrics-instance",type=Component
is an debug level MBean which is now disabled by default in AS trunk https://jira.jboss.org/jira/browse/JBAS-6987. Probably we need to do this in EAP branch (and maybe AS 5_x branch) too?
However, the real solution for JNDI names would be to fix our default JNDI naming scheme (and still be backward compatible).
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238672#4238672
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238672
16 years, 9 months
[Design of JBoss jBPM] - Re: JBPM4 - org.jbpm.pvm.internal.session.DbSession & org.hi
by galanfish
thanks, shekharv
yes, org.jbpm.pvm.internal.hibernate.DbSessionImpl is an implementation of org.jbpm.pvm.internal.session.DbSession, but maybe you don't understand me(my english is so poor).
what I don't understand is that:
the methods #svae/#delete/#flush/... in DbSessionImpl are delegated forward to the corresponding method(same method name) call of org.hibernate.Session, it seems the author would like to see DbSession rather than org.hibernate.Session in this program, but why make it internal? and, in modules like pvm/jpdl/enterprise, I found lots of references to org.hibernate.Session directory(in some commands, activities, etc.), which are retrived from the Environment, why not using DbSession instead?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238659#4238659
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238659
16 years, 9 months
[Design of Embedded JBoss] - Re: External Contribution to AS Embedded
by ALRubinger
"Josh Davis" wrote : I tried my hand at making the test for https://jira.jboss.org/jira/browse/JBBOOT-56
|
| Check the patch attached to the issue and let me know if that's what you meant.
Great code in general. I appreciated your commitment to documentation and cleanup/centralization as you go along.
In ripping jboss-bootstrap out of the Application Server, I've been especially sensitive to violation of scope and extending a component's concerns outside its domain. In this case, startup/shutdown of bootstraps is provided by impl-base, and the attached patch addresses test cases in impl-mc. This makes it more of a compliance/acceptance test where impl-mc validates it's getting a good impl-base.
So I've attached an alternate way of tackling the issue in "JBBOOT-56.v2.ALR.patch" on the JIRA. Have a look and let me know what you think.
Some misc minor notes:
* You don't need AtomicInteger in LifecycleOrderPojo (as you hint); this is all single-threaded.
* We need to get you set up w/ JBoss licence headers and preferably with a formatter (if you're in Eclipse I have code templates).
I'm impressed that you've picked up the Bootstrap Server API and MC jboss-beans.xml deployments so quickly. This was a good, working patch you've provided. So let's just address the scope issue and move forward on something else? ;)
Outstanding questions:
* Do you have an account on jboss.org? This enables posting to the forums, JIRA assignments, etc.
* Have you yet signed a contributor's agreement? Once done I can commit on your behalf, and after a few patches, get you commit access.
http://jboss.org/contributor
S,
ALR
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238639#4238639
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238639
16 years, 9 months