Re: RMI From TomEE to Jboss

2018-07-11 Thread Howard W. Smith, Jr.
On Tue, Jul 10, 2018 at 7:23 PM, Jonathan S. Fisher wrote: > > A better way would be to wrap your legacy EJBs with RESTful services > so that way you're platform independent. > +1 I like this approach... even though I am running 2 separate TomEE's on same machine, they communicate via RESTful

Re: RMI From TomEE to Jboss

2018-07-11 Thread Jonathan Gallimore
Ah - wonder why I haven't seen that before. Thanks for the note. I'll see if I can throw an example here. On Wed, Jul 11, 2018 at 10:31 AM, Romain Manni-Bucau wrote: > The "Referencing a bean in another server" part of > http://tomee.apache.org/ejb-refs.html should already enable several cases.

Re: RMI From TomEE to Jboss

2018-07-11 Thread Romain Manni-Bucau
The "Referencing a bean in another server" part of http://tomee.apache.org/ejb-refs.html should already enable several cases. Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github

Re: RMI From TomEE to Jboss

2018-07-11 Thread Jonathan Gallimore
You can certainly make remote calls to JBoss in the same way you would do with a regular client. You'd need to include the JBoss client jars, and use the appropriate URL and context factory in your InitialContext. This should be a reasonable approach. JBoss itself has the concept of an

Re: java.lang.NoClassDefFoundError: com/mysql/jdbc/ParameterBindings

2018-07-11 Thread Matthew Broadhead
sorry i should have come back to you on this one. turns out during testing i added the mysql connector to the pom as runtime.  using your advice i changed it to test scope and the problem has gone away.  error must have been because it was in tomee/lib and in the project pom On 02/07/18