Hello Seam community,
I am just starting a new project and want to use the seam framework. The system architecture demands that parts of the application are on a different machine than the main web-system. How can I inject (with @EJB annotation) remote EJBs into Beans located on the main machine. I guess I have to give the address of the remote machine somewhere, maybe jndi.properties? Or am I heading in the completely wrong direction. I looked through a lot of EJB tutorials, docs and books but they only describe injection in simple java clients or plain local injection.
Thanks in advance,
Martin
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117478#4117478
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117478
Owning a copy of Alur, Crupi & Malks "Core J2EE Patterns" myself, I was at first surprised by Seams heretic ways but I then started to realize the many of the patterns are trying to solve problems that really aren't there anymore.
Sure, you can look up your abstract factory through a service locator but what's the *real* use in that? Enjoy your classes, the time for interfaces and factories are when you really have two or more implementations of the same logic etc.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117475#4117475
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117475
"Mussie" wrote : Can't I use HSQL DB why mysql?
Yes, just configure a HSQL in persistent mode in -ds.xml
anonymous wrote : And whats the sence of update if I have to validate the database?
| I thought hibernate generates the db relations out of my entities?
Then use create-drop, but loose your data, or use update.
anonymous wrote : And why are all the examples with in memory based persistence I can't picture any use-case for that.
Because it's great for examples. Read the hsql docs, its a 2 line change to make it persistent, and without the tables being create-droped.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117474#4117474
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117474
Serializing and deserializing (and transforming the reference to something that can be transmitted via a web service) works for me also (serializing and deserializing the remote interface). When deserializing, the remote interface points to the original bean.
However if the serialized object is returned through a web service and then reused in a later web service call (by passing the serialized object to the service), the serialized object points to a new bean instance instead of the original one.
Is there an obvious explanation for this that i have missed?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117469#4117469
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117469