>>>I have a stateful so i changed a bit the OpenEjbBean in order to look for >>>@Remove annotations. >>>I can open a JIRA and attach a patch file if you want. Great, thanks
>>>Again, i changed a bit the EjbPlugin in order to deal with that case. >>>I can provide a patch if you want. Great thanks and issue a patch with above issue >>>BTW, we definitely need to enhance the assembly task cause there is a lot of >>>unnecessary jars in the target war. May be it's only due to my environment >>>but the WEB-INF/lib now contains a lot of openejb-* modules instead of only >>>one and the openwebbeans/ directory contains openejb-* jars too. This is not happened in my war. WEB-INF/lib only contains to jars and openwebbeans/ not contains any openejb jar. >>>Gonna try to make my sample working with the web profile integration. Cool, I have tried it. And it works for me Thanks; --Gurkan 2010/4/15 Jean-Louis MONTEIRO <[email protected]> > > Right. > > I gave it a try and i'm facing some problems. > First, the TomcatThreadContextListener has changed and more specifically > /**getThreadName method in class ContextBindings*/ > protected Method method; > > The setAccessible is not set to true, yet i get an IllegalAccessException! > > I have a stateful so i changed a bit the OpenEjbBean in order to look for > @Remove annotations. > I can open a JIRA and attach a patch file if you want. > > Finally, it seems to me that the EjbPlugin only fills its internal > DeploymentInfo map once. > I didn't saw if you fulfill those maps when a new web application gets > deployed. > > Again, i changed a bit the EjbPlugin in order to deal with that case. > I can provide a patch if you want. > > BTW, we definitely need to enhance the assembly task cause there is a lot > of > unnecessary jars in the target war. May be it's only due to my environment > but the WEB-INF/lib now contains a lot of openejb-* modules instead of only > one and the openwebbeans/ directory contains openejb-* jars too. > > Gonna try to make my sample working with the web profile integration. > > Jean-Louis > > > > > Gurkan Erdogdu-2 wrote: > > > > Hello; > > > > Think is that I bundle OWB jars into openejb.war, therefore those jars > are > > added to deployed web application or cataliane classpath. > > > > There is no need to add OWB jars into deployed web applications, because > > they are added by integration at runtime. > > > > One more thing, Currently there is a problem with interceptors ordering, > I > > will attach a new code. > > > > Thanks; > > > > --Gurkan > > > > 2010/4/15 Jean-Louis MONTEIRO <[email protected]> > > > >> > >> Gurkan, > >> > >> i finally got OpenEJB and OpenWebBeans compilation working. > >> I do have some questions regarding the packaging. > >> > >> With OWB integration, the tomcat openejb webapp now depends on OWB > >> modules. > >> After assembly, we get a 30 Mo jar file instead of 20 Mo before. Yet, > >> dunno > >> if it's relevant or not to leave the standard OpenEJB webapp and create > a > >> new one for the web profile. > >> > >> Moreover, after generating the assembly i noticed some changes > preventing > >> OpenEJB startup (WEB-INF/lib contains to many openejb jar files). > >> > >> Again, dunno if it's related or not to the OWB integration. > >> > >> I'd like to get your opinion regarding the packaging. > >> Should we package an all in one webapp for web profile ? > >> Should OWB jar files be deployed with a deployed webapp ? > >> > >> Thanks in advance. > >> Jean-Louis > >> -- > >> View this message in context: > >> > http://n4.nabble.com/OWB-integration-with-OpenEJB-Tomcat-Integration-Code-tp1835872p1887364.html > >> Sent from the OpenEJB Dev mailing list archive at Nabble.com. > >> > > > > > > > > -- > > Gurkan Erdogdu > > http://gurkanerdogdu.blogspot.com > > > > > > -- > View this message in context: > http://n4.nabble.com/OWB-integration-with-OpenEJB-Tomcat-Integration-Code-tp1835872p1892626.html > Sent from the OpenEJB Dev mailing list archive at Nabble.com. > -- Gurkan Erdogdu http://gurkanerdogdu.blogspot.com
