JBAS-1841 - There is no spoon
by Adrian Brock
In another attempt to weed MCF code from codebase :-)
the JMX ServiceController has now been replaced by a
Microcontainer facade.
A more complete description of the status can be found here:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=88071
Please report problems as either subtasks on the JIRA issue:
http://jira.jboss.com/jira/browse/JBAS-1841
or create a thread in the POJO forum
http://www.jboss.com/index.html?module=bb&op=viewforum&f=208
FAQ:
Q: Does this mean JMX is no longer supported?
A: No, JMX is another context type in the generic dependency
controller. There are now two types, JMX and POJO
that will be able to cross inject dependencies amongst
themselves.
Q: Do I need to convert my MBeans to POJOs?
A: No the whole of this is to support in the new POJO
environment both JBoss developers and users who have written MBeans
as integration into JBossAS. This provides backwards
compatibility.
Q: My MBean no longer works properly?
A: Assuming you didn't break it :-), use one of the
links above.
Q: Is this documentated anywhere?
A: You're kidding right? I will write up a description
of how it works shortly. Those famailiar with the POJO
microcontainer will understand the basics if you
do the following "pseudo" replacements:
POJO -> JMX
Instantiate: new() -> createMBean();
Configure: setX() -> setAttribute("X");
etc.
Q: Why are the ServiceCreator/Configurator deprecated?
A: These were never intended to be used externally.
They are implementation details of the ServiceController
(as the javadoc describes "A helper class for the ServiceController")
In fact, if you use the ServiceConfigurator directly,
you are almost certainly leaking memory nor will it work
properly unless you are very lucky. :-)
--
xxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxx
18 years, 5 months
RE: [JBoss-dev] Microcontainer/Breakout Strategy
by Scott M Stark
I was not seeing the xsl related errors, but I have switched to using
jrockit1.5.0_6 so that could behave differently.
> -----Original Message-----
> From: jboss-development-bounces(a)lists.jboss.org
> [mailto:jboss-development-bounces@lists.jboss.org] On Behalf
> Of Adrian Brock
> Sent: Thursday, August 03, 2006 4:43 AM
> To: JBoss.org development list
> Subject: Re: [JBoss-dev] Microcontainer/Breakout Strategy
>
>
> Thanks, I now have a working build, 24 hours after I started
> this task. :-)
>
> I ended up started again with eclipse-3.2, subeclipse-1.0.3,
> giving eclipse more memory and turning off decorations to
> make it work.
>
> I also fixed the xalan problem by reincluding it in endorsed.
18 years, 5 months
RE: [JBoss-dev] Missing jars (javax.persistence)
by Scott M Stark
I would say they should be in the server lib dir as part of the JPA
project. The only question is whether there are potential conflicts in
terms of deployment isolation if both JPA and EJB3 are being used. In
that case, we might need to obfuscate the non-javax.* classes and make
them part of the ejb3.deployer.
-----Original Message-----
From: jboss-development-bounces(a)lists.jboss.org
[mailto:jboss-development-bounces@lists.jboss.org] On Behalf Of Carlo de
Wolf
Sent: Thursday, August 03, 2006 3:02 AM
To: jboss-development(a)lists.jboss.org
Subject: [JBoss-dev] Missing jars (javax.persistence)
Hi all,
I saw that ejb3.deployer no longer contains a lot of jar files.
But I need these three:
<fileset dir="${hibernate.entitymanager.lib}">
<include name="ejb3-persistence.jar"/>
<include name="hibernate-entitymanager.jar"/>
</fileset>
<fileset dir="${hibernate.annotations.lib}">
<include name="hibernate-annotations.jar"/>
</fileset>
(Basicly the javax.persistence stuff.)
They are not in the <server>/lib directory, but they are in the client
directory.
Is another project going to deploy these artifacts or can I add them
back to the build.xml of ejb3.deployer?
IMHO they're part of a separate product (javax.persistence) on which
ejb3 is dependant.
Carlo
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
18 years, 5 months
RE: [JBoss-dev] Microcontainer/Breakout Strategy
by Scott M Stark
If I revert to the current hread, I'm seeing failures in the tomcat
layer:
2006-08-02 23:22:55,797 WARN [org.apache.catalina.core.StandardContext]
Error creating ContextConfig for jboss.web:type=Host,host=localhost
java.lang.NullPointerException
at
org.apache.catalina.core.StandardContext.init(StandardContext.java:5249)
at
jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Lja
va
.lang.Object;)Ljava.lang.Object;(Unknown Source)
at
java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)L
ja
va.lang.Object;(Unknown Source)
at
org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503
)
at
org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.web.tomcat.tc6.TomcatDeployer.performDeployInternal(TomcatDepl
oyer.java:307)
This code is not matching the current
https://svn.jboss.org/repos/jbossweb/trunk/ code so where is the tomcat6
build coming from?
-----Original Message-----
From: jboss-development-bounces(a)lists.jboss.org
[mailto:jboss-development-bounces@lists.jboss.org] On Behalf Of Adrian
Brock
Sent: Wednesday, August 02, 2006 10:09 PM
To: JBoss.org development list
Subject: RE: [JBoss-dev] Microcontainer/Breakout Strategy
I was really talking about JBossAS.
I'm still trying to get a clean build and boot
that I can apply the JMX/MC integratrion changes to.
18 years, 5 months
