"dimitris(a)jboss.org" wrote :
| Ron, and yet another question is could this be made to work with the existing classloading service at port 8083?
|
| More so that fixes/features to the classloading service go into one place.
|
Dimitris, I was looking at a parallel thread on the Remoting users forum when I was working on this issue, and I forgot about your question. I don't know about the JBossAS RMI classloading facility, but Remoting uses a special Remoting Connector, so it might have an independent origin.
In any case, I started a "Remoting and remote classloading" thread on the "Design of JBoss Remoting, Unified Invokers" forum (http://www.jboss.com/index.html?module=bb&op=viewtopic&t=138067) so that we keep the question in mind in Remoting 3.
-Ron
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160384#4160384
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160384
If I understand correctly, what you're asking for isn't going to be solved in Remoting. The Remoting remote classloading facility is used only to unmarshal classes coming from the server.
But you're up against Java typing. To be able to use an interface, you would need to refer to it in your client code. That means that the interface would have to be available to the classloader that loads your client. In your case, the client is an EJB3, and by doing scoping you're specifically preventing your client code from seeing the other EJB3's repository.
So, as I understand the situation, I don't think you could do what you want to do. Of course, someone who knows more about this subject might have a better answer. You could try posing the question on the "Installation, Configuration & DEPLOYMENT" forum (http://www.jboss.com/index.html?module=bb&op=viewforum&f=61).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160382#4160382
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160382
Not sure if this will work, but stop JBossAS and delete the server/xxx/data, server/xxx/tmp and server/xxx/work directories and restart JBossAS.
If the problem still persists, then the old IP address is not being cached by JBossAS, in which case either the JVM or the operating system is caching the name. Given that you can ping correctly (I assume you did the ping from the same machine running JBossAS), you can probably rule out the OS, which leaves you with the JVM as the culprit.
Let me know how it goes.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160378#4160378
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160378
I have tried multiple ways to create a Seam 2.0 Project as EAR but it fails everytime.
I have reinstalled a clean install of eclipse-jee-europa-winter and used the JBoss Tools update site to get the latest version of JBoss Tools. I'm using jboss-4.2.2.GA runtime, jboss-seam-2.0.3.CR1 and a MySQL 5.1 datasource.
I have tried with jdk1.5.0_08 and jdk1.6.0_02 jdk runtime.
I'm getting this error mesage when creating the Seam Project as an EAR.
Failed while installing Seam 2.0
String index out of range: -2
Is there a way to fix it? Or what am I doing wrong?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160375#4160375
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160375