From: <ad...@jb...> - 2005-05-05 00:45:53
|
Just to clear in case you think I'm being arbitrary... If you examine the use case for EJB3 standalone and these services it fails the 5%/95% rule for the first release. Security junit: you aren't going to run your tests against the corporate ldap server tomcat: you'd use their native realm abstraction swing: it would only be useful if you are also operating in client/server mode and want single sign-on JMS If you want *co-located* jms and EJB3 you can use JBossAS/EJB3, otherwise you just need the jndi config for the remote jms. Remoting All you need is to marshall the invocation to simulate call-by-value and that is only so you can test remote access properly in junit. You aren't going to expose standalone EJB3 sessions remotely from Tomcat or Swing. etc. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876541#3876541 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876541 |