If not in the same application it is the easiest yes because arguments will
be copied between classloaders to allow you to provide the same API in both
webapps. If your bean is not remote then it is avoided IIRC but parameters
need to be shared.


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com>

2016-02-12 6:39 GMT+01:00 Rentius <[email protected]>:

> Thank you Romain
> The global lookup is working.
>
> When using either the global or LocalInitialContextFactory must one always
> send serializable data types as parameters? It is running on the same TomEE
> server so in the same JVM.
>
> /Caused by: java.io.NotSerializableException: java.util.HashMap$EntrySet :
> The EJB specification restricts remote interfaces to only serializable data
> types./
>
> I have changed the interface to @Local but still the error persists.
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Calling-separate-EJB-from-Web-project-deployed-on-same-server-tp4677588p4677599.html
> Sent from the TomEE Users mailing list archive at Nabble.com.
>

Reply via email to