If the lookup takes place outside of the ejb container, i.e. in an unit test,
the lookup succeeds and the unknown remote interface gets loaded by the rmi
class loader.
21:28:30,859 DEBUG [ClassByteClassLoader] attempting to load from network:
Hi
is that really true:
anonymous wrote : and this CL does not support loading bytes from a remote
location (which would be required for this use case).
I tried to lookup an session bean from which i only have one @Remote interface
in my class loader (ie. in the ear or in the unit test
Im looking desperately for a solution to my problem:
I tried to lookup an session bean - named ServiceEjb - from which i only have
one @Remote interface in my class loader (ie. in the ear or in the unit test
runner) from within another session bean, say the SessionBeanFactory.
That session
Hi,
JBoss forces me to annotate some of my session beans with a @Depends
annotation. I deploy ejbs in several ears at the same time with @EJB injection
dependencies in between them. Deployment at server startup only works when i
tell ejb container to ignore some @EJB dep for the moment and
it does not work as expected. i'm still looking for the same.
http://www.jboss.com/index.html?module=bbop=viewtopict=133367
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4175992#4175992
Reply to the post :
The exception occurs right during the lookup. Not before.
I had a look at my exception. It states that the RMIClassLoader tries to
loadProxy classes. It tries to load the interfaces that i dont have in my ear.
I had enabled the WebService (DownloadServerClasses=true).
I have a
let me explain my situation:
i'd like to have ejb behave polymorphic like with plain java classes. I know
ONE interface of my ejbs but not ALL - and i don't need to know them all.
All my ejbs implement one common remote interface. I create ejb instances with
a lookup and assign the ejb proxy
Thank you, Ron.
Yet, one thing remains, perhaps based on my missconception:
I took your ScopedTest and changed according to my use case:
TravelAgentBean now implements another @Remote interface, namely
SpecialTravelAgent. This interface is not available in the clients class loader.
When the
Yet loading of remote interfaces fails. See :
[URL]http://www.jboss.com/index.html?module=bbop=viewtopicp=4160112#4160112[/URL]
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4160139#4160139
Reply to the post :
Ok, i found that the reason actually was my using isolated ears with dedicated
loader repositores, enabled in the jboss-app.xml
!DOCTYPE jboss-app
| PUBLIC -//JBoss//DTD J2EE Application 1.4//EN
| http://www.jboss.org/j2ee/dtd/jboss-app_4_2.dtd;
| jboss-app
|
Ok, i enabled trace logging (described here:
http://www.jboss.com/index.html?module=bbop=viewtopict=126382 ).
I'm using a standalone client application. The log says:
| 12:03:06,794 DEBUG [SocketWrapper]
ServerSocketWrapper[Socket[addr=/127.0.0.1,port=1222,localport=4873].12a5dd1]
closing
Ok, that is the problem:
once i emptied the jboss-app.xml, the example works.
Please, somebody tell me, that it is somehow possible to have isolated loader
repositories per ear and still allow for remote class loading...
View the original post :
Is there a solution for scoped class loaders? Is it really the problem?
The configuration is not working for me, I wonder wether that is because of
the scoped class loaders i am using for each ear (EJBs calling each other
across ear boundaries).
View the original post :
Using JBoss Portal 2.6.4 with JDK1.5.0
It seems to me that RMI class loading does not work with my configuration
I gave a security policy to the jboss to allow for RMI class loading.
And i gave the loaderport parameter to the DefaultEjb3Connector as described
here
Let me try to make that question short:
I get
| Caused by: java.lang.ClassNotFoundException: No ClassLoaders found for:
palmyra.baustein.geschaeftsverwaltung.antrag.ProtokollVBeanEjb (no security
manager: RMI class loader disabled)
|
WAIT, I resolved that by enabling security policy that
Have a portal for every user logged in?
That way we allow each user to have a portal application that has a dynamic set
of portlets assembled like dialogs.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4135835#4135835
Reply to the post :
I get the following exception with the new portletbridge 1.0.0.B
16:18:50,797 ERROR [STDERR] java.lang.IllegalStateException: sendRedirect
cannot be called after setPortletMode/setWindowState/set
| RenderParameter/setRenderParameters has been called previously
| 16:18:50,797 ERROR [STDERR]
You can create portal pages programmatically. Look at the code of the admin
portlets, its done there. Of course you are entering portal development domain
and will be using APIs that are possible to be changed with the next portal.
The org.jboss.portal.core.model.portal.PortalObjectContainer
We consider a design of uniform building blocks for an enterprise application
portal, were the building blocks are EAR files that deliver UI as well as
busines logic in one deployment. I'm interested in your opinion on this. Let me
explain that:
- we want to build up on the best practices and
What happens if you use a @Stateless EJB?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4112077#4112077
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4112077
___
jboss-user
20 matches
Mail list logo
