[Microcontainer] - Re: Towards remoting-jboss-beans.xml
by alesj
"ron.sigal(a)jboss.com" wrote :
| 1. Are there any hidden gotcha's I'm missing?
|
Dunno.
You tell me, when you hit them. ;-)
"ron.sigal(a)jboss.com" wrote :
| 2. Are there any conventions, e.g. naming conventions, I should be aware of?
|
Not that I'm aware of.
Perhaps keeping old MBeans, that are now plain POJOs,
still in the MBean server with the help of @JMX.
"ron.sigal(a)jboss.com" wrote :
| 3. Am I correct in understanding that setting "registerDirectly=false" in org.jboss.aop.microcontainer.aspects.jmx.JMX supports hot deployment?
|
Dunno, check ServiceControllerRegistrationLifecycleCallback for more details. It's a JMX issue / question.
"ron.sigal(a)jboss.com" wrote :
| 4. JBAS-3926 is "Move remoting transports out of conf/jboss-service.xml to a remoting-beans.xml", but I see that all the *-beans.xml files in AS 5 are named *-jboss-beans.xml. Is the latter form just a convention for *-beans.xml files that come with the AS?
|
Yes, they were renamed to be more JBoss specific.
Since we do file --> metadata matching mostly based on suffix,
we would also pick some Spring -beans.xml named files,
which were only meant to be used by strict Spring core lib.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187017#4187017
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187017
17 years, 5 months
[EJB 3.0] - Re: EJB2 Client calling EJB3 Bean
by tom.iten＠gmx.net
Hi jaikiran
- I changed the remote interface according the Error Message
- Removed the "implements EJB3Remote" clause from the Bean
(so i do not have to implement all the callbacks in EJB2.x manner)
After this changes i got a Exception during the deploy:
13:13:33,564 ERROR [AbstractKernelController] Error installing to Start: name=jboss.j2ee:ear=ejb2clienttoejb3.ear,jar=ejb2clienttoejb3-ejb.jar,name=EJB3Bean,ser
vice=EJB3 state=Create
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.RangeCheck(ArrayList.java:546)
at java.util.ArrayList.get(ArrayList.java:321)
at org.jboss.ejb3.proxy.jndiregistrar.JndiSessionRegistrarBase.createJndiReferenceBindingSet(JndiSessionRegistrarBase.java:222)
at org.jboss.ejb3.proxy.jndiregistrar.JndiSessionRegistrarBase.bindEjb(JndiSessionRegistrarBase.java:162)
By delivering a jboss.xml descriptor file with the jndi home interface name
i could run the sample. Thanks!
best regards
Tom
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186998#4186998
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186998
17 years, 5 months
[Beginners Corner] - ComponentBean cannot be cast to ComponentBean
by dado0583
I am receiving the following error message when trying to deploy my application on jboss:
javax.faces.FacesException: Can't parse configuration file: jar:file:/C:/jboss-4.2.2-1-jsf/server/default/deploy/pims.ear/lib/jsf-facelets.jar!/META-INF/faces-config.xml: Error at line 8 column 16: Error at (8, 16: com.sun.faces.config.beans.ComponentBean cannot be cast to com.sun.faces.config.beans.ComponentBean
After much reading about JBoss classloading I suspect that its because the class is being loaded by two classloaders and is then causing problems.. I believe this class is located in jsf-impl.jar. Looking at the loader repository for the ear for my jsf web app, there are two references to jsf-impl.jar. The unexpected on being in the tmp folder.
file:/C:/jboss-4.2.2-1-jsf/server/default/deploy/pims.ear/lib/jsf-impl.jar
file:/C:/jboss-4.2.2-1-jsf/server/default/tmp/deploy/tmp25412jsf-impl.jar
Any ideas how I can solve this problem? It´s driving me nuts...
Thanks,
David
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186996#4186996
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186996
17 years, 5 months