Mudi Appu

I want to load a class on-the-fly to web service application runs on Jboss. The class to be loaded is an implementation of an interface class which is already bundled with web service deployment archive (war file)
My code is
obj = Class.forName(classString,false,ClassLoader.getSystemClassLoader()); logicClass = (SpecialLogic)obj.newInstance();

But the execution stops at the second line when class given by �classString� is present in the class path.
Please help

If I understood correctly, onMessge() method of your MDB invokes the sessioBean method and it returns the response back. Now what you have to do is push the response into the outbound queue. In order to do this you don�t need a session bean because of you are not going to expose a method (entry point) to outside the container here. Push the message to outbound queue directly by your onMessage().

1) weblogic.management.console.applets.Navapplet class comes with weblogic.jar. can you check whether your weblogic.jar file contains with that class or not.
2) Both of this can happen because of your machine environment is unable to run java applets. Configure your java runtime for that.

Add weblogic.jar into your clients class path ........

++j is equitant to j=j+1
So j is incrementing in each evaluation time of while loop condition (++j < 5)

Though both ejbPassivate and ejbRemove are releasing resources they are not same by any means. When passivating the EJB container store/ persists the state of EJB and release resources. But removing is just like assign null into the reference. Meaning of removing passive EJB is removing the stored state of the EJB from the storage.
Hope this helps

You can rollback database transactions. But I am wondering what is message rollback.
What do mean by message rollback? Please explain bit.

Because of you have deployed session beans and entity beans in separate jar files; classes of entity bean are not available to session beans and vise visa. The easy solution fro this is put entity.jar into the server class path. Other solution is package all EJBs (entity and session beans) together in one single EJB jar file. There are many more solutions�. Try this first.

It should be something like connection pool. J2EE server implementation is done in order to store live references of EJB objects in somewhere and passing it when it is required. This is not an impossible task. And also we don�t need to worry about this as far as we are not going to implement a J2EE server.

Georg,
It is depending on your business requirements. If you only needs to get the list of names of participants (and you do not need to do anything more with participants objects) EJB-QL may be the better option. But keep in mind that; EJB_QL is not good in performance as SQL.

Please be kind enough to post your solution here. It may helpful for others.
Cheers

OK. So as far as your world is hardly bound into that book EJB server and EJB container are synonymous for you. Enjoy your own world!

Do you needs to print it by java program? What is the purpose of printing it? Can you explain this little more?

What is the need of separate thread to run this?
Can�t you have simple main method without thread?
Run it without thread and see.

store "bold","italic" infomation seperatly in the DB and retrive them when you desplaying them and show them accordingly.