Re: Error with XMLBeanUtil and ValidateDD when upgrading to RichFaces 3.2
Hi Jarek, Thanks very much for your quick reply. This issue has really got me stumped! Is there some Geronimo jar file that needs to be updated? Not sure... I will upload my geronimo.log. http://www.nabble.com/file/p17765890/geronimo.log geronimo.log Thanks very much for your help! .Burt Jarek Gawor-2 wrote: > > Burt, > > Can you sends us the geronimo.log file somehow? > > Jarek > > On Tue, Jun 10, 2008 at 4:58 PM, Burt Prior <[EMAIL PROTECTED]> wrote: >> >> Hi Geronimo Team, >> >> I need a bit of help here. Our team is using Facelets/JSF/RichFaces 3.1 >> on >> Geronimo 2.1.0. >> >> We attempted to upgrade to the latest version of RichFaces (3.2.1), and >> on >> deployment of our app, the console and logs filled with a tremendous >> amount >> of errors and xml; I tailed a snippet below: >> >> ... >> var >> >>java.lang.String >> >> >> >> Virtual earth version, Default value is >> "6". >> version >> >>java.lang.String >> >> >> >> Initial zoom level as a number between 1 and 18. >> Default >> value is "17". >> zoom >> >>java.lang.String >> >> >> >> >> >> >>at >> org.apache.geronimo.deployment.xmlbeans.XmlBeansUtil.validateDD(XmlBeansUtil.java:187) >>at >> org.apache.geronimo.jasper.deployment.JspModuleBuilderExtension.convertToTaglibSchema(JspModuleBuilderExtension.java:674) >>at >> org.apache.geronimo.jasper.deployment.JspModuleBuilderExtension.parseTldFile(JspModuleBuilderExtension.java:439) >>at >> org.apache.geronimo.jasper.deployment.JspModuleBuilderExtension.getListenerClasses(JspModuleBuilderExtension.java:424) >>at >> org.apache.geronimo.jasper.deployment.JspModuleBuilderExtension.createJspClassFinder(JspModuleBuilderExtension.java:180) >>at >> org.apache.geronimo.jasper.deployment.JspModuleBuilderExtension.addGBeans(JspModuleBuilderExtension.java:149) >>at >> org.apache.geronimo.jetty6.deployment.JettyModuleBuilder.addGBeans(JettyModuleBuilder.java:518) >>at >> org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.addGBeans(SwitchingModuleBuilder.java:165) >>at >> org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:647) >>at >> org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:254) >>at >> org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:133) >>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) >>at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) >>at java.lang.reflect.Method.invoke(Unknown Source) >>at >> org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) >>at >> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) >>at >> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:867) >>at >> org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) >>at >> org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:342) >>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) >>at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) >>at java.lang.reflect.Method.invoke(Unknown Source) >>at >> org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) >>at >> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) >>at >> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:867) >>at >> org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) >>at >> org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:172) >>at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(Unknown >> Source) >>at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(Unknown Source) >>at >> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(Unknown >> Source) >>at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(Unknown Source) &
Error with XMLBeanUtil and ValidateDD when upgrading to RichFaces 3.2
Hi Geronimo Team, I need a bit of help here. Our team is using Facelets/JSF/RichFaces 3.1 on Geronimo 2.1.0. We attempted to upgrade to the latest version of RichFaces (3.2.1), and on deployment of our app, the console and logs filled with a tremendous amount of errors and xml; I tailed a snippet below: ... var java.lang.String Virtual earth version, Default value is "6". version java.lang.String Initial zoom level as a number between 1 and 18. Default value is "17". zoom java.lang.String at org.apache.geronimo.deployment.xmlbeans.XmlBeansUtil.validateDD(XmlBeansUtil.java:187) at org.apache.geronimo.jasper.deployment.JspModuleBuilderExtension.convertToTaglibSchema(JspModuleBuilderExtension.java:674) at org.apache.geronimo.jasper.deployment.JspModuleBuilderExtension.parseTldFile(JspModuleBuilderExtension.java:439) at org.apache.geronimo.jasper.deployment.JspModuleBuilderExtension.getListenerClasses(JspModuleBuilderExtension.java:424) at org.apache.geronimo.jasper.deployment.JspModuleBuilderExtension.createJspClassFinder(JspModuleBuilderExtension.java:180) at org.apache.geronimo.jasper.deployment.JspModuleBuilderExtension.addGBeans(JspModuleBuilderExtension.java:149) at org.apache.geronimo.jetty6.deployment.JettyModuleBuilder.addGBeans(JettyModuleBuilder.java:518) at org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.addGBeans(SwitchingModuleBuilder.java:165) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:647) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:254) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:133) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:867) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:342) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:867) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) at org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:172) at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(Unknown Source) at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(Unknown Source) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(Unknown Source) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.access$100(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.invoke(Unknown Source) at sun.reflect.GeneratedMethodAccessor77.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source) at sun.rmi.transport.Transport$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Unknown Source) at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Jun 10, 2008 1:34:29 PM com.sun.facelets.compiler.TagLibraryConfig loadImplicit INFO: Added Library from: jar:file:/C:/geronimo-jetty6-javaee5-2.1/repository/defa
Re: Geronimo 2.1 and Seam
Hi David, That's great news about your work with OpenEJB 3.0 and G2.1.1. I have a request. Hurry! :-) > we use JPA to run your CMPs. I'm not familiar with why Jacek had you add > that, so I'm not sure what to advise. We generate the cmp peristence unit > for you as well, so I'm not too sure on any reason you'd need to > explicitly create it. Ok. We are using EJB 3 JPA Entities, so I don't think we are running any CMP's at all. Also, I don't think this is a Seam issue at all. When I take out that 'duplicate' 'cmp' PU, it generates an error, so for some reason it's needed. I guess its because we are using the latest JEE5 stack to develop our Seam app on G2.1. Is this 'cmp' a legacy support feature? I don't understand it's purpose under JEE5. Thanks again, .Burt David Blevins wrote: > > > On Mar 11, 2008, at 5:09 PM, Burt Prior wrote: > >> >> Hi David, >> >> Got it! Applied the patch and everything works great with no >> errors! Hello >> Geronimo and Seam! (with not a single error!). Our team is >> celebrating! > > Great! We're trying very hard to get OpenEJB 3.0 out the door and > tested for potential inclusion in G 2.1.1. With a bit more luck you > won't have to use that patched jar for much longer. > >> Question 1: >> >> Is following snippet in needed anymore? What does >> 'cmp' do? >> I think Jacek initially used this for some reason I don't >> understand. Do I >> have to include this in every Geronimo/Seam project? Do I always >> have to >> create 2 PU's like this replicating the 's in a 'cmp' PU? >> >> ... >> >> >> org.jboss.seam.example.booking.Booking >> org.jboss.seam.example.booking.Hotel >> org.jboss.seam.example.booking.User >> true >> >> >> ... > > I don't know Seam at all, so hopefully we don't confuse each other, > but I can tell you that the cmp persistence unit is dedicated our > generated CMP 2.x and 1.1 classes -- we use JPA to run your CMPs. I'm > not familiar with why Jacek had you add that, so I'm not sure what to > advise. We generate the cmp peristence unit for you as well, so I'm > not too sure on any reason you'd need to explicitly create it. > > If you can get by without it and things work, I'd definitely get rid > of it. > >> Question 2: >> >> I added the concurrency lib to Geronimo's repository as in a prevously >> mentioned thread. >> >> Do I need the following anymore? Do I have to include this in every >> Geronimo/Seam project plan? >> >> ... >> >> >> >>concurrent >>concurrent >>jar >> >> ... >> > > Maybe David J. could comment on that one. > > > -David > > > -- View this message in context: http://www.nabble.com/Geronimo-2.1-and-Seam-tp15621154s134p16103408.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Geronimo 2.1 and Seam
Hi David, Got it! Applied the patch and everything works great with no errors! Hello Geronimo and Seam! (with not a single error!). Our team is celebrating! Since we hit this milestone, we would like to now turn our attention back to our Geronimo/Seam app instead of the booking example. (they are very similar) Could I again ask you a question about the geronimo 'booking' deployment descriptor? What we want to do is create a simple Eclipse/Geronimo/Seam/EJB3 project. What we would like to do is to use our experience from the 'booking' example and 'fold in' the external deployment descriptor into our regular Eclipse/Geronimo/Seam project(s). Below is the complete and working 'booking' app deployment descriptor that you previously helped us with, that we successfully 'deploy' from the command line. Question 1: Is following snippet in needed anymore? What does 'cmp' do? I think Jacek initially used this for some reason I don't understand. Do I have to include this in every Geronimo/Seam project? Do I always have to create 2 PU's like this replicating the 's in a 'cmp' PU? ... org.jboss.seam.example.booking.Booking org.jboss.seam.example.booking.Hotel org.jboss.seam.example.booking.User true ... Question 2: I added the concurrency lib to Geronimo's repository as in a prevously mentioned thread. Do I need the following anymore? Do I have to include this in every Geronimo/Seam project plan? ... concurrent concurrent jar ... Thanks again for you and your team's help. My working 'booking' plan is below: .Burt http://geronimo.apache.org/xml/ns/j2ee/application-2.0";> http://geronimo.apache.org/xml/ns/deployment-1.2";> org.jboss.seam.examples.jee5 jboss-seam-jee5 2.1.0.A1 ear org.apache.geronimo.hibernate geronimo-hibernate-transaction-manager-lookup jar console.dbpool ElvisPool 1.0 rar concurrent concurrent jar jboss-seam-jee5.war http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1";> http://geronimo.apache.org/xml/ns/deployment-1.2";> org.jboss.seam.examples.jee5 jboss-seam-jee5 2.1.0.A1 war /seam-jee5 jboss-seam-jee5.jar http://www.openejb.org/xml/ns/openejb-jar-2.1";> http://geronimo.apache.org/xml/ns/deployment-1.2";> org.jboss.seam.examples.jee5 jboss-seam-jee5 2.1.0.A1 jar http://java.sun.com/xml/ns/persistence";> org.hibernate.ejb.HibernatePersistence ElvisPool ElvisPool org.jboss.seam.example.booking.Booking org.jboss.seam.example.booking.Hotel org.jboss.seam.example.booking.User true org.jboss.seam.example.booking.Booking org.jboss.seam.example.booking.Hotel org.jboss.seam.example.booking.User true David Blevins wrote: > > On Mar 11, 2008, at 10:19 AM, Burt Prior wrote: > >> Hi David, >> >> Wow! This is awesome news. Very exciting. >> >> Ok, we are ready to apply this patch to our 2.1. >> >> Sorry to ask; could you be a bit more specific on what I need to do >> to apply >> this patch? >> >>> If you grab the org.apache.openejb.core.Operation class from the >>> latest >>> snapshot[1] and put it into your openejb-core-3.0-beta-2.jar >>> replacing the >>> existing Operation.class, things should work. >> >> I'm not sure how to do this exactly. Could I ask for your help? > > Sure. You'll want to make sure your server is shutdown, then extract > this jar into a clean temp directory: > >repository/org/apache/openejb/openejb-core/3.0-beta-2/openejb- > core-3.0-beta-2.jar > > Then delete the file: org/apache/openejb/core/Operation.class > > Now you want to grab the openejb-core-3.0-SNAPSHOT jar I pointed you > at and extract it into it's own clean temp directory. Then move th
Re: Geronimo 2.1 and Seam
Hi David, Wow! This is awesome news. Very exciting. Ok, we are ready to apply this patch to our 2.1. Sorry to ask; could you be a bit more specific on what I need to do to apply this patch? > If you grab the org.apache.openejb.core.Operation class from the latest > snapshot[1] and put it into your openejb-core-3.0-beta-2.jar replacing the > existing Operation.class, things should work. I'm not sure how to do this exactly. Could I ask for your help? Thanks again for your excellent work with our team and Gavin. .Burt David Blevins wrote: > > Ok, I've been digging around in the TCK and chatting with Gavin offline. > > Looks like this is an issue on our end after all. I had originally > thought @Destroy mapped to @PreDestroy, which would definitely result > in the IllegalStateException, but @Remove is very different. I've > done a check with the TCK to verify that relaxing the get/setParameter > restriction in reference to @Remove is ok and things looked good, so > I've gone ahead and checked in that change. > > Now, dealing with your existing build might be a bit trickier, but if > you're willing to crack open the openejb-core-3.0-beta-2.jar and patch > one class, we should be able to get things working for you. > > Here was the change: > http://svn.apache.org/viewvc/openejb/trunk/openejb3/container/openejb-core/src/main/java/org/apache/openejb/core/Operation.java?r1=635766&r2=635767&pathrev=635767&view=patch > > If you grab the org.apache.openejb.core.Operation class from the > latest snapshot[1] and put it into your openejb-core-3.0-beta-2.jar > replacing the existing Operation.class, things should work. > > -David > > [1] > http://people.apache.org/repo/m2-snapshot-repository/org/apache/openejb/openejb-core/3.0-SNAPSHOT/openejb-core-3.0-20080311.012606-8.jar > > > On Mar 10, 2008, at 10:31 AM, Burt Prior wrote: > >> >> Hi David, >> >> Gavin King just responded with an interesting comment about a possible >> Geronimo/TCK bug and Seam: >> >> http://seamframework.org/Community/Seam2JEE5CompliantWithTheTCKRequirements >> http://seamframework.org/Community/Seam2JEE5CompliantWithTheTCKRequirements >> >> I was wondering if you had a moment, could you add your $0.02? It >> appears >> he and his team will be looking into this issue. >> >> Thanks very much, >> .Burt >> >> >> >> djencks wrote: >>> >>> I talked with david blevins about this a little more. From the >>> evidence available so far we think that seam is not jee5 compliant >>> with the tck requirements. If openejb did not throw this exception >>> in these circumstances it would fail the tck. Recall that seam is >>> developed on a non-jee5-certified platform. Under these >>> circumstances we'd have a hard time changing openejb to not throw the >>> exception. Do you have any evidence that seam runs with a bean with a >>> @Destroy annotated method on any certified platform? >>> >>> On the other hand the requirement appears to be only in tck code and >>> not stated in the spec. Also, it doesn't make much sense. Thus it >>> might be worth pursuing a challenge to the tck. I would think the >>> jboss/seam developers would be the ones to start this although we >>> might challenge it also. The challenge process typically takes a >>> while. >>> >>> Seeing the entire stack trace from your bean's @Destroy method to the >>> original exception might possibly shed more light on the subject. >>> >>> Other than filling up your logs what problems is this causing? If it >>> does not cause functional problems perhaps pursuing a challenge would >>> be the best solution. >>> >>> thanks >>> david jencks >>> >>> On Mar 7, 2008, at 10:06 AM, Burt Prior wrote: >>> >>>> >>>> Hi David, >>>> >>>> Thanks for the reply. Our team really needs some help in solving >>>> this last >>>> issue with Geronimo and Seam. There must be some way to resolve >>>> this. >>>> >>>> As I exercise Seam's booking app, I monitor the Geronimo log very >>>> closely. >>>> As I mentioned, the app works fine. You can see the entities and >>>> ejb3 >>>> (stateful) session beans are found (jndi) and loaded correctly. >>>> The only >>>> error we see is the one mentioned in my last post. >>>> >>>> The error is thrown, and the app cont
Re: Geronimo 2.1 and Seam
Hi David,
Gavin King just responded with an interesting comment about a possible
Geronimo/TCK bug and Seam:
http://seamframework.org/Community/Seam2JEE5CompliantWithTheTCKRequirements
http://seamframework.org/Community/Seam2JEE5CompliantWithTheTCKRequirements
I was wondering if you had a moment, could you add your $0.02? It appears
he and his team will be looking into this issue.
Thanks very much,
.Burt
djencks wrote:
>
> I talked with david blevins about this a little more. From the
> evidence available so far we think that seam is not jee5 compliant
> with the tck requirements. If openejb did not throw this exception
> in these circumstances it would fail the tck. Recall that seam is
> developed on a non-jee5-certified platform. Under these
> circumstances we'd have a hard time changing openejb to not throw the
> exception. Do you have any evidence that seam runs with a bean with a
> @Destroy annotated method on any certified platform?
>
> On the other hand the requirement appears to be only in tck code and
> not stated in the spec. Also, it doesn't make much sense. Thus it
> might be worth pursuing a challenge to the tck. I would think the
> jboss/seam developers would be the ones to start this although we
> might challenge it also. The challenge process typically takes a while.
>
> Seeing the entire stack trace from your bean's @Destroy method to the
> original exception might possibly shed more light on the subject.
>
> Other than filling up your logs what problems is this causing? If it
> does not cause functional problems perhaps pursuing a challenge would
> be the best solution.
>
> thanks
> david jencks
>
> On Mar 7, 2008, at 10:06 AM, Burt Prior wrote:
>
>>
>> Hi David,
>>
>> Thanks for the reply. Our team really needs some help in solving
>> this last
>> issue with Geronimo and Seam. There must be some way to resolve this.
>>
>> As I exercise Seam's booking app, I monitor the Geronimo log very
>> closely.
>> As I mentioned, the app works fine. You can see the entities and ejb3
>> (stateful) session beans are found (jndi) and loaded correctly.
>> The only
>> error we see is the one mentioned in my last post.
>>
>> The error is thrown, and the app continues on.
>>
>> Data is saved correctly in the DB, and the business logic in the
>> session
>> beans are executed in the container fine.
>>
>> After closer inspection of the log, the error appears every time
>> any session
>> bean is invoked, for example, 'BookingListAction' -> 'bookingList',
>> 'HotelSearchingAction' -> 'hostSearch'. I've went over the source
>> code for
>> these beans; they are simple and easy to understand, and I don't see
>> anything that would cause this error.
>>
>> What every session bean shares is the following method and annotation:
>>
>> ...
>> @Destroy @Remove
>> public void destroy() {}
>> ...
>>
>> I think this is related to the error, but I'm not sure. I'm
>> looking for
>> something to change in any bean code, but I don't see a thing.
>>
>> The Seam 'booking' example is important to our team to work with no
>> errors
>> because this is exactly how we are building our current production
>> app;
>> (Geronimo 2.1, Seam 2.1, JSF (facelets), EJB3 Session Beans, JPA
>> Entities).
>>
>> And everything works, except for this error!
>>
>> It appears to us that any 'Seam app' running on Geronimo 2.1 would
>> experience this issue.
>>
>> Could we ask for you and your team's help to work with us in
>> resolving this,
>> and how we can move forward?
>>
>> Thanks very much for your time and help,
>> .Burt
>>
>>
>>
>>
>> David Blevins wrote:
>>>
>>>
>>> On Mar 6, 2008, at 1:30 PM, Burt Prior wrote:
>>>
>>>> ...
>>>> 13:16:36,385 INFO [OpenEJB] invoking method create on
>>>> jboss-seam.jar/EjbSynchronizations
>>>> 13:16:36,385 INFO [OpenEJB] finished invoking method create
>>>> 13:16:36,495 INFO [Transaction] TX Required: Started transaction
>>>> [EMAIL PROTECTED]
>>>> 13:16:36,495 ERROR [OpenEJB] The bean instance business method
>>>> encountered a
>>>> system exception: Callback methods cannot access parameters
>>>> java.lang.IllegalStateException: Callback methods cannot access
>>>> parameters
>>>>
Re: Geronimo 2.1 and Seam
Hi All, I've submitted the following Seam Bug: http://jira.jboss.com/jira/browse/JBSEAM-2713 Seam Bug Report I hope I captured all of your excellent analysis and suggestions. Please check it out when you get a chance, and feel free add any comments. I'm hoping for a quick resolution after Gavin and his team has look at this. Thanks, .Burt Burt Prior wrote: > > Hi Jay, (and David^2) > > Thanks for checking that. I didn't have time to experiment with it on > Friday. Darn. Ok, well. > > I just now checked my Seam users group posting on this. It looks like > Gavin King replied. > > Please check it out, and don't hesitate to respond as well. > > http://www.seamframework.org/Community/Seam2JEE5CompliantWithTheTCKRequirements > Geronimo and Seam and TCK > > Gavin mentioned to fill out a bug report. Any suggestions? > > Thanks everyone. This is really excellent. I wonder if we could get some > kinda patch for Seam on Geronimo? > .Burt > > > > > > Jay D. McHugh-3 wrote: >> >> Hey Burt, >> >> I just tried removing the @Destroy annotations in the booking example >> but the errors still pop up. >> >> Jay >> >> Burt Prior wrote: >>> Hi David, >>> >>> I just posted on SeamFramework.org: >>> >>> http://www.seamframework.org/Community/Seam2JEE5CompliantWithTheTCKRequirements >>> Seam Posting >>> >>> I'm hoping to get some way to resolve this issue soon. >>> >>> Perhaps its as you mentioned: Can't I just safely remove @Destroy? >>> >>> Thanks, >>> .Burt >>> >>> >>> >>> >>> djencks wrote: >>>> >>>> On Mar 7, 2008, at 2:51 PM, Burt Prior wrote: >>>> >>>>> Hi David and David, >>>>> >>>>> First, thank you both for helping us. Our team has been hanging on >>>>> your >>>>> every post! >>>>> >>>>>> Do you have any evidence that seam runs with a bean with a @Destroy >>>>>> annotated method on any certified platform? >>>>> I sure don't, other than latest Seam doc/articles i've went thru here: >>>>> http://seamframework.org/Documentation/GettingStarted Getting >>>>> Started with >>>>> Seam >>>>> >>>>> Also, this booking example is the 'jee5' booking example; there is >>>>> a 'non >>>>> jee5' booking example as well in every Seam download. I think the >>>>> 'non >>>>> jee5' uses plain JavaBean and Hibernate instead of EJB3 and JPA. >>>>> >>>>> The only other JEE5 certified platform I know of that works with >>>>> Seam is >>>>> GlassFish. Not from personal exerience but from articles from Sun >>>>> and Seam. >>>>> http://weblogs.java.net/blog/caroljmcdonald/archive/2007/07/ >>>>> sample_applicat_1.html >>>>> GlassFish and Seam >>>>> >>>>> I was just wondering. Anyone running Seam on a JEE5 compliant >>>>> server such >>>>> Geronimo or GlassFish must get the same error? >>>> Well, if they have an ejb with a @Destroy method we think they will >>>> get this error. The glassfish example for v2 does have one @Destroy >>>> method in CatalogBean but my experience trying to extract information >>>> from Glassfish has not been a happy one so I haven't tried anything >>>> on it. >>>> >>>>>> Also, it doesn't make much sense. >>>>> Yes, i agree. All the errors we solved to get to this point 'made >>>>> sense'. >>>>> But when I saw this error, and read David's response, i thought we >>>>> were in >>>>> trouble; If I'm hitting up against the spec, and I can't change my >>>>> code, >>>>> where does that leave my architecture? (Geronimo, EJB3, Seam, >>>>> Oracle, JPA, >>>>> JSF). >>>>> >>>>>> I would think the jboss/seam developers would be the ones to start >>>>>> this >>>>>> although we might challenge it also. >>>>> Yes, I will post on the appropriate Seam list today. I guess the >>>>> question >>>>> is to focus on @Destroy? How would you phrase
Re: Geronimo 2.1 and Seam
Hi Jay, (and David^2) Thanks for checking that. I didn't have time to experiment with it on Friday. Darn. Ok, well. I just now checked my Seam users group posting on this. It looks like Gavin King replied. Please check it out, and don't hesitate to respond as well. http://www.seamframework.org/Community/Seam2JEE5CompliantWithTheTCKRequirements Geronimo and Seam and TCK Gavin mentioned to fill out a bug report. Any suggestions? Thanks everyone. This is really excellent. I wonder if we could get some kinda patch for Seam on Geronimo? .Burt Jay D. McHugh-3 wrote: > > Hey Burt, > > I just tried removing the @Destroy annotations in the booking example > but the errors still pop up. > > Jay > > Burt Prior wrote: >> Hi David, >> >> I just posted on SeamFramework.org: >> >> http://www.seamframework.org/Community/Seam2JEE5CompliantWithTheTCKRequirements >> Seam Posting >> >> I'm hoping to get some way to resolve this issue soon. >> >> Perhaps its as you mentioned: Can't I just safely remove @Destroy? >> >> Thanks, >> .Burt >> >> >> >> >> djencks wrote: >>> >>> On Mar 7, 2008, at 2:51 PM, Burt Prior wrote: >>> >>>> Hi David and David, >>>> >>>> First, thank you both for helping us. Our team has been hanging on >>>> your >>>> every post! >>>> >>>>> Do you have any evidence that seam runs with a bean with a @Destroy >>>>> annotated method on any certified platform? >>>> I sure don't, other than latest Seam doc/articles i've went thru here: >>>> http://seamframework.org/Documentation/GettingStarted Getting >>>> Started with >>>> Seam >>>> >>>> Also, this booking example is the 'jee5' booking example; there is >>>> a 'non >>>> jee5' booking example as well in every Seam download. I think the >>>> 'non >>>> jee5' uses plain JavaBean and Hibernate instead of EJB3 and JPA. >>>> >>>> The only other JEE5 certified platform I know of that works with >>>> Seam is >>>> GlassFish. Not from personal exerience but from articles from Sun >>>> and Seam. >>>> http://weblogs.java.net/blog/caroljmcdonald/archive/2007/07/ >>>> sample_applicat_1.html >>>> GlassFish and Seam >>>> >>>> I was just wondering. Anyone running Seam on a JEE5 compliant >>>> server such >>>> Geronimo or GlassFish must get the same error? >>> Well, if they have an ejb with a @Destroy method we think they will >>> get this error. The glassfish example for v2 does have one @Destroy >>> method in CatalogBean but my experience trying to extract information >>> from Glassfish has not been a happy one so I haven't tried anything >>> on it. >>> >>>>> Also, it doesn't make much sense. >>>> Yes, i agree. All the errors we solved to get to this point 'made >>>> sense'. >>>> But when I saw this error, and read David's response, i thought we >>>> were in >>>> trouble; If I'm hitting up against the spec, and I can't change my >>>> code, >>>> where does that leave my architecture? (Geronimo, EJB3, Seam, >>>> Oracle, JPA, >>>> JSF). >>>> >>>>> I would think the jboss/seam developers would be the ones to start >>>>> this >>>>> although we might challenge it also. >>>> Yes, I will post on the appropriate Seam list today. I guess the >>>> question >>>> is to focus on @Destroy? How would you phrase it? >>>> >>>> What also doesn't make sense is the Seam doc for @Destroy. Why do >>>> we see >>>> any issue at all? >>>> http://docs.jboss.com/seam/2.1.0.A1/reference/en/html/ >>>> annotations.html#d0e19563 >>>> Seam @Destroy Annotation >>>> >>>> >>>>> The challenge process typically takes a while. >>>> Yes. Not really an option for us. We are trying get our Geronimo >>>> app out >>>> now. >>>> >>>>> Other than filling up your logs what problems is this causing? >>>> There appears to be no other errors or problems. I've been >>>> exercising the >>>> app, watching the console log in real time in
Re: Geronimo 2.1 and Seam
Hi David, I just posted on SeamFramework.org: http://www.seamframework.org/Community/Seam2JEE5CompliantWithTheTCKRequirements Seam Posting I'm hoping to get some way to resolve this issue soon. Perhaps its as you mentioned: Can't I just safely remove @Destroy? Thanks, .Burt djencks wrote: > > > On Mar 7, 2008, at 2:51 PM, Burt Prior wrote: > >> >> Hi David and David, >> >> First, thank you both for helping us. Our team has been hanging on >> your >> every post! >> >>> Do you have any evidence that seam runs with a bean with a @Destroy >>> annotated method on any certified platform? >> >> I sure don't, other than latest Seam doc/articles i've went thru here: >> http://seamframework.org/Documentation/GettingStarted Getting >> Started with >> Seam >> >> Also, this booking example is the 'jee5' booking example; there is >> a 'non >> jee5' booking example as well in every Seam download. I think the >> 'non >> jee5' uses plain JavaBean and Hibernate instead of EJB3 and JPA. >> >> The only other JEE5 certified platform I know of that works with >> Seam is >> GlassFish. Not from personal exerience but from articles from Sun >> and Seam. >> http://weblogs.java.net/blog/caroljmcdonald/archive/2007/07/ >> sample_applicat_1.html >> GlassFish and Seam >> >> I was just wondering. Anyone running Seam on a JEE5 compliant >> server such >> Geronimo or GlassFish must get the same error? > > Well, if they have an ejb with a @Destroy method we think they will > get this error. The glassfish example for v2 does have one @Destroy > method in CatalogBean but my experience trying to extract information > from Glassfish has not been a happy one so I haven't tried anything > on it. > >> >>> Also, it doesn't make much sense. >> >> Yes, i agree. All the errors we solved to get to this point 'made >> sense'. >> But when I saw this error, and read David's response, i thought we >> were in >> trouble; If I'm hitting up against the spec, and I can't change my >> code, >> where does that leave my architecture? (Geronimo, EJB3, Seam, >> Oracle, JPA, >> JSF). >> >>> I would think the jboss/seam developers would be the ones to start >>> this >>> although we might challenge it also. >> >> Yes, I will post on the appropriate Seam list today. I guess the >> question >> is to focus on @Destroy? How would you phrase it? >> >> What also doesn't make sense is the Seam doc for @Destroy. Why do >> we see >> any issue at all? >> http://docs.jboss.com/seam/2.1.0.A1/reference/en/html/ >> annotations.html#d0e19563 >> Seam @Destroy Annotation >> >> >>> The challenge process typically takes a while. >> >> Yes. Not really an option for us. We are trying get our Geronimo >> app out >> now. >> >>> Other than filling up your logs what problems is this causing? >> >> There appears to be no other errors or problems. I've been >> exercising the >> app, watching the console log in real time in the eclipse console, >> then >> checking the db. It appears to work fine. It throws the >> exceptions, then >> recovers. It's always the same error: 'Callback methods cannot access >> parameters'. >> >>> Seeing the entire stack trace from your bean's @Destroy method to the >>> original exception might possibly shed more light on the subject. > > Does the destroy method on your beans actually do anything? If, like > the samples, it does nothing, the simplest solution is to leave it > out. If if does do something, does it get called? My belief from > the stack trace is that it does not due to the exception. > > As for wording... that's tricky. I guess I'd say that running the > app on the geronimo/openejb javaee5 certified container results in > the stack trace and that allowing the InvocationContext to supply the > parameters during a lifecycle call results in tck failures. I'd ask > if they can run the sample with the @Destroy method getting called on > a certified container without getting an exception and perhaps > mention that we aren't aware of any support in the spec itself for > this requirement. > > I'd include this part of the stack trace: > > 11:25:05,179 ERROR [OpenEJB] The bean instance business m
Re: Geronimo 2.1 and Seam
Hi David,
Thanks for the reply. Our team really needs some help in solving this last
issue with Geronimo and Seam. There must be some way to resolve this.
As I exercise Seam's booking app, I monitor the Geronimo log very closely.
As I mentioned, the app works fine. You can see the entities and ejb3
(stateful) session beans are found (jndi) and loaded correctly. The only
error we see is the one mentioned in my last post.
The error is thrown, and the app continues on.
Data is saved correctly in the DB, and the business logic in the session
beans are executed in the container fine.
After closer inspection of the log, the error appears every time any session
bean is invoked, for example, 'BookingListAction' -> 'bookingList',
'HotelSearchingAction' -> 'hostSearch'. I've went over the source code for
these beans; they are simple and easy to understand, and I don't see
anything that would cause this error.
What every session bean shares is the following method and annotation:
...
@Destroy @Remove
public void destroy() {}
...
I think this is related to the error, but I'm not sure. I'm looking for
something to change in any bean code, but I don't see a thing.
The Seam 'booking' example is important to our team to work with no errors
because this is exactly how we are building our current production app;
(Geronimo 2.1, Seam 2.1, JSF (facelets), EJB3 Session Beans, JPA Entities).
And everything works, except for this error!
It appears to us that any 'Seam app' running on Geronimo 2.1 would
experience this issue.
Could we ask for you and your team's help to work with us in resolving this,
and how we can move forward?
Thanks very much for your time and help,
.Burt
David Blevins wrote:
>
>
> On Mar 6, 2008, at 1:30 PM, Burt Prior wrote:
>
>> ...
>> 13:16:36,385 INFO [OpenEJB] invoking method create on
>> jboss-seam.jar/EjbSynchronizations
>> 13:16:36,385 INFO [OpenEJB] finished invoking method create
>> 13:16:36,495 INFO [Transaction] TX Required: Started transaction
>> [EMAIL PROTECTED]
>> 13:16:36,495 ERROR [OpenEJB] The bean instance business method
>> encountered a
>> system exception: Callback methods cannot access parameters
>> java.lang.IllegalStateException: Callback methods cannot access
>> parameters
>> at
>> org
>> .apache
>> .openejb
>> .core
>> .interceptor
>> .ReflectionInvocationContext
>> .getParameters(ReflectionInvocationContext.java:71)
>> at
>> org
>> .jboss
>> .seam
>> .intercept
>> .EJBInvocationContext.getParameters(EJBInvocationContext.java:34)
>> at
>> org
>> .jboss
>> .seam
>> .intercept
>> .SeamInvocationContext.getParameters(SeamInvocationContext.java:49)
>> ...
>> 13:16:36,495 WARN [Component] Exception calling component @Destroy
>> method:
>> hotelBooking
>> javax.ejb.EJBException: The bean encountered a non-application
>> exception.;
>> nested exception is:
>> java.lang.IllegalStateException: Callback methods cannot access
>> parameters
>> at
>> org
>> .apache
>> .openejb
>> .core
>> .ivm.BaseEjbProxyHandler.convertException(BaseEjbProxyHandler.java:
>> 366)
>> at
>> org
>> .apache
>> .openejb
>> .core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:323)
>> at
>> org
>> .apache
>> .openejb
>> .util
>> .proxy.Jdk13InvocationHandler.invoke(Jdk13InvocationHandler.java:49)
>> at $Proxy77.destroy(Unknown Source)
>> ...
>>
>> I'm really stuck on this. Any idea's on how I can resolve this last
>> error?
>
> This it seems like some code is trying to call
> InvocationContext.getParameters() from inside a lifecycle method.
>
> I can't find a reference to this in the spec, but the TCK definitely
> says this must throw an IllegalStateException.
>
> -David
>
>> djencks wrote:
>>>
>>> I don't have oracle set up here which makes it hard to test much.
>>>
>>> Right now you have the persistence element in your geronimo plan set
>>> up so that it's using the jdbc/ElvisPool configured later on in the
>>> same plan. While it was my idea originally to introduce the "ext-
>>> module" stuff I now think its usually a bad idea. In this case there
>>> are no config-properties specified in the plan for the pool, so it's
>>> not surprising that oracle can't figure out where the db is.
>>>
>>> From the end of your po
Re: Geronimo 2.1 and Seam
Hi David, I've been trying (unsuccessfully) to figure out the OpenEJB error that I mentioned in my last post. What I did just now is to 'swap out' the hibernate persistence provider with the Geronimo's default OpenJPA PP, in that part of the deployment plan. replaced: org.hibernate.ejb.HibernatePersistence with: org.apache.openjpa.persistence.PersistenceProviderImpl and commented out the hibernate 'properties'. In general, it appears to work (there are some WARN's) but most interesting is that the same error I mentioned in my previous post occurs as well under the same conditions: ... 13:16:36,385 INFO [OpenEJB] invoking method create on jboss-seam.jar/EjbSynchronizations 13:16:36,385 INFO [OpenEJB] finished invoking method create 13:16:36,495 INFO [Transaction] TX Required: Started transaction [EMAIL PROTECTED] 13:16:36,495 ERROR [OpenEJB] The bean instance business method encountered a system exception: Callback methods cannot access parameters java.lang.IllegalStateException: Callback methods cannot access parameters at org.apache.openejb.core.interceptor.ReflectionInvocationContext.getParameters(ReflectionInvocationContext.java:71) at org.jboss.seam.intercept.EJBInvocationContext.getParameters(EJBInvocationContext.java:34) at org.jboss.seam.intercept.SeamInvocationContext.getParameters(SeamInvocationContext.java:49) ... 13:16:36,495 WARN [Component] Exception calling component @Destroy method: hotelBooking javax.ejb.EJBException: The bean encountered a non-application exception.; nested exception is: java.lang.IllegalStateException: Callback methods cannot access parameters at org.apache.openejb.core.ivm.BaseEjbProxyHandler.convertException(BaseEjbProxyHandler.java:366) at org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:323) at org.apache.openejb.util.proxy.Jdk13InvocationHandler.invoke(Jdk13InvocationHandler.java:49) at $Proxy77.destroy(Unknown Source) ... I'm really stuck on this. Any idea's on how I can resolve this last error? Thanks again, .Burt djencks wrote: > > I don't have oracle set up here which makes it hard to test much. > > Right now you have the persistence element in your geronimo plan set > up so that it's using the jdbc/ElvisPool configured later on in the > same plan. While it was my idea originally to introduce the "ext- > module" stuff I now think its usually a bad idea. In this case there > are no config-properties specified in the plan for the pool, so it's > not surprising that oracle can't figure out where the db is. > > From the end of your post it looks like you've set up a pool using > the wizard. I'd recommend using that one. So > - remove the entire ext-module section from your plan. > - Change the persistence element so the jta-datasource is whatever > you named the datasource in the wizard-created pool. > - Remove the oracle dependency from the plan and replace it with a > dependency on the wizard-created pool. > - I don't know if you'll need the non-jta-datasource. I strongly > recommend removing it until you find out you need it. If present, it > absolutely needs to be a different datasource, with no-transaction > configured. > > hope this helps > david jencks > > > > On Mar 4, 2008, at 5:07 PM, Burt Prior wrote: > >> >> Hi Jacek and David, >> >> Here is the stack trace of when I try to 'register' myself in the >> booking >> application: >> >> and here is my 'jboss-seam-jee5-geronimo-plan.xml': >> >> >> http://geronimo.apache.org/xml/ns/j2ee/ >> application-2.0"> >> >> http://geronimo.apache.org/xml/ns/ >> deployment-1.2"> >> >> org.jboss.seam.examples.jee5 >> jboss-seam-jee5 >> 2.1.0.A1 >> ear >> >> >> >> org.apache.geronimo.hibernate >> >> geronimo-hibernate-transaction-manager-lookup >> jar >> >> >> >> >> oracle >> jdbc >> 10.2 >> jar >> >> >> >> >> >> concurrent >> concurrent >> jar >> >> >> >> >> >> >> jboss-seam-jee5.war >> http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1";> >> http://geronimo.apache.org/xml/ns/ >> deployment-1.2"> >> >> org.jboss.seam.examples.jee5 >>
Re: Geronimo 2.1 and Seam
pendency on the wizard-created pool. > - I don't know if you'll need the non-jta-datasource. I strongly > recommend removing it until you find out you need it. If present, it > absolutely needs to be a different datasource, with no-transaction > configured. > > hope this helps > david jencks > > > > On Mar 4, 2008, at 5:07 PM, Burt Prior wrote: > >> >> Hi Jacek and David, >> >> Here is the stack trace of when I try to 'register' myself in the >> booking >> application: >> >> and here is my 'jboss-seam-jee5-geronimo-plan.xml': >> >> >> http://geronimo.apache.org/xml/ns/j2ee/ >> application-2.0"> >> >> http://geronimo.apache.org/xml/ns/ >> deployment-1.2"> >> >> org.jboss.seam.examples.jee5 >> jboss-seam-jee5 >> 2.1.0.A1 >> ear >> >> >> >> org.apache.geronimo.hibernate >> >> geronimo-hibernate-transaction-manager-lookup >> jar >> >> >> >> >> oracle >> jdbc >> 10.2 >> jar >> >> >> >> >> >> concurrent >> concurrent >> jar >> >> >> >> >> >> >> jboss-seam-jee5.war >> http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1";> >> http://geronimo.apache.org/xml/ns/ >> deployment-1.2"> >> >> org.jboss.seam.examples.jee5 >> jboss-seam-jee5 >> 2.1.0.A1 >> war >> >> >> /seam-jee5 >> >> >> >> >> jboss-seam-jee5.jar >> http://www.openejb.org/xml/ns/openejb- >> jar-2.1"> >> >> http://geronimo.apache.org/xml/ns/ >> deployment-1.2"> >> >> org.jboss.seam.examples.jee5 >> jboss-seam-jee5 >> 2.1.0.A1 >> jar >> >> >> >> >> >> http://java.sun.com/xml/ns/persistence";> >> >> org.hibernate.ejb.HibernatePersistence >> jdbc/ElvisPool >> jdbc/ElvisPool >> org.jboss.seam.example.booking.Booking >> org.jboss.seam.example.booking.Hotel >> org.jboss.seam.example.booking.User >> true >> >> >> > value="org.hibernate.dialect.OracleDialect"/> >> > name="hibernate.transaction.manager_lookup_class" >> >> value="org.apache.geronimo.hibernate.transaction.GeronimoTransactionMa >> nagerLookup" >> /> >> >> >> >> > name="hibernate.transaction.flush_before_completion" >> value="true"/> >> > value="org.hibernate.cache.HashtableCacheProvider"/> >> >> >> >> >> >> >> org.jboss.seam.example.booking.Booking >> org.jboss.seam.example.booking.Hotel >> org.jboss.seam.example.booking.User >> true >> >> >> >> >> >> >> >> >> seam-jee5-dbpool >> > xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2";> >> org.tranql >> tranql-connector-oracle-local >> rar >> >> http://geronimo.apache.org/xml/ns/j2ee/ >> connector-1.2"> >> http://geronimo.apache.org/xml/ns/ >> deployment-1.2"> >> >> org.jboss.seam.examples.jee5 >> booking-dbpool >> 2.1.0.A1 >> rar >> >> >> >> org.apache.geronimo.configs >> system-database >> car >> >> >> >> >> >> >> >> >> >> javax.sql.DataSource> connectionfactory-interface> >> >> >> jdbc/ElvisPool >> >> >> >> >> >> >> >> >>
Re: Geronimo 2.1 and Seam
I think the 'jta-data-source' is incorrect, but I've tried every example I could find with no luck. I have my Geronimo database pool configured correctly with the usual Oracle thin driver; console.dbpool ElvisPool 1.0 rar Could I ask for your help in this? I'm just not able to connect to the geronimo's database pool, and I'm not sure why. Thanks again, .Burt Jacek Laskowski wrote: > > On Mon, Mar 3, 2008 at 10:16 AM, Burt Prior <[EMAIL PROTECTED]> wrote: > >> 'java.sql.SQLException - invalid oracle url specified: >> OracleDataSource.makeURL'. > > Show the plan for the database pool and the entire stack trace. If > oracle thin driver class barfs it could mean that the url is incorrect > which might be easy to fix. In the meantime write a sample jdbc > program to connect to the database to make sure it can be connected > from outside. > > Jacek > > -- > Jacek Laskowski > http://www.JacekLaskowski.pl > > -- View this message in context: http://www.nabble.com/Geronimo-2.1-and-Seam-tp15621154s134p15840865.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Geronimo 2.1 and Seam
Hi Jay, I downloaded the jar you referenced, and replaced the one that was previously in the repository. Thanks to you, David, and Jacek, I'm able to see the booking example homepage! Yes! I'm working on now getting access to my Oracle database pool that I set up. When I go to the next page in the booking example (so save some data; user?) I get the error... 'java.sql.SQLException - invalid oracle url specified: OracleDataSource.makeURL'. Not sure what's causing this... I was wondering if anyone has seen this before? Thanks again, .Burt Jay D. McHugh-3 wrote: > > Burt, > > Grab a new copy of the geronimo-hibernate-transaction-manager-lookup jar > (later referred to as 'ghtml.jar') from > http://people.apache.org/~jaydm/hibernate and replace the file already > in your Geronimo repo. > > Using a fresh trunk build and that recompiled jar file, I was able to > deploy the Seam jee5 booking example. > > The old ghtml.jar was giving me unresolved import errors when I tried to > deploy (I don't know why). > > But now I am looking at the booking example (ooh pretty!). > > Are you able to get the sample running? > > > Jay > > David Jencks wrote: >> >> On Feb 28, 2008, at 10:01 PM, David Jencks wrote: >> >>> >>> On Feb 28, 2008, at 4:42 PM, Burt Prior wrote: >>> >>>> >>>> Hi Jacek, >>>> >>>> I just noticed something in my last posting to David. In my error log I >>>> posted: >>>> >>>> ... >>>> 14:00:28,084 INFO [Ejb3Configuration] Processing PersistenceUnitInfo [ >>>> name: bookingDatabase >>>> ...] >>>> 14:00:28,084 ERROR [Ejb3Configuration] Container is providing a null >>>> PersistenceUnitRootUrl: discovery impossible >>>> ... >>>> >>>> I noticed that in your "Running JBoss Seam 2 on Geronimo 2.1" >>>> article, when >>>> you show the log, it has the same error as well. >>>> >>>> The difference appears to be, your example continues to load the >>>> booking >>>> application, and mine throws an exception on the next line: >>>> >>>> 14:00:28,115 ERROR [GBeanInstanceState] Error while starting; GBean >>>> is now >>>> in the FAILED state: >>>> abstractName="org.jboss.seam.examples.jee5/jboss-seam-jee5/2.1.0.A1/ear?EJBModule=jboss-seam-jee5.jar,J2EEApplication=org.jboss.seam.examples.jee5/jboss-seam-jee5/2.1.0.A1/ear,PersistenceUnitModule=jboss-seam-jee5.jar,j2eeType=PersistenceUnit,name=bookingDatabase" >>>> >>>> >>>> java.lang.NullPointerException >>>> at >>>> org.jboss.util.file.ArchiveBrowser.getBrowser(ArchiveBrowser.java:62) >>>> at >>>> org.hibernate.ejb.Ejb3Configuration.scanForXmlFiles(Ejb3Configuration.java:606) >>>> >>>> >>>> at >>>> org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:351) >>>> >>>> at >>>> org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:126) >>>> >>>> >>>> at >>>> org.apache.geronimo.persistence.PersistenceUnitGBean.(PersistenceUnitGBean.java:119) >>>> >>>> >>>> >>>> ... >>>> >>>> I thought it was interesting that although we recieved the same >>>> error, your >>>> example continued to deploy and run, and mine stopped the deploy with >>>> those >>>> exceptions. >>> >>> I browsed the hibernate code a bit and think that maybe you are using >>> different versions of hibernate? In >>> >>> http://fisheye.jboss.com/browse/Hibernate/entitymanager/trunk/src/java/org/hibernate/ejb/Ejb3Configuration.java?r=11344 >>> >>> >>> >>> the error message is right before some code that uses the >>> PersistenceUnitRootUrl whereas in a later version of the code the >>> message is immediately followed by "return". >>> >>> I looked in the geronimo code a bit more and haven't figured out how >>> this can be null. >> >> Further investigation after some sleep revealed a bug right next to the >> previous one. I've fixed it and pushed a new snapshot of >> geronimo-persistence-jpa10-2.2-20080229.155614-3.jar. If you get this >> one in your g. repo just like y
Re: Geronimo 2.1 and Seam
Hi David, Jay, and Jacek, Ok! Got the booking example working! Wow! It was very exciting to see the booking example homepage on Geronimo 2.1 after deploying. I can't save anything to my (Oracle thin driver) database using the 'pool' I set up thru Geronimo, but I guess I'll just have to work on that as a separate issue. Perhaps my deployment plan is incorrect; i'm not sure. Just getting to this point with Geronimo and Seam has our team very energized to deliver and showcase our first Geronimo and Seam application! Just a note of thanks for sticking with us thru all the issues. Thank You. Ok, on that making Geronimo and Seam work with our Oracle database pool. Thanks, .Burt Jay D. McHugh-3 wrote: > > False alarm. > > It does deploy from the command line also. > > I made the mistake of trying to deploy as a non-root user when Geronimo > is installed into a directory owned by root. > > It is working from the command line also. > > I'll try using the patched Geronimo 2.1 to make sure that works too. > > Jay > > Jay D. McHugh wrote: >> Actually, it is working if I deploy from the web console. >> >> When I try to deploy from the command line, it chokes. >> >> So try using the console to deploy and see if that gets you there. >> >> Jay >> >> Jay D. McHugh wrote: >>> Burt, >>> >>> Grab a new copy of the geronimo-hibernate-transaction-manager-lookup >>> jar (later referred to as 'ghtml.jar') from >>> http://people.apache.org/~jaydm/hibernate and replace the file already >>> in your Geronimo repo. >>> >>> Using a fresh trunk build and that recompiled jar file, I was able to >>> deploy the Seam jee5 booking example. >>> >>> The old ghtml.jar was giving me unresolved import errors when I tried >>> to deploy (I don't know why). >>> >>> But now I am looking at the booking example (ooh pretty!). >>> >>> Are you able to get the sample running? >>> >>> >>> Jay >>> >>> David Jencks wrote: >>>> >>>> On Feb 28, 2008, at 10:01 PM, David Jencks wrote: >>>> >>>>> >>>>> On Feb 28, 2008, at 4:42 PM, Burt Prior wrote: >>>>> >>>>>> >>>>>> Hi Jacek, >>>>>> >>>>>> I just noticed something in my last posting to David. In my error >>>>>> log I >>>>>> posted: >>>>>> >>>>>> ... >>>>>> 14:00:28,084 INFO [Ejb3Configuration] Processing >>>>>> PersistenceUnitInfo [ >>>>>> name: bookingDatabase >>>>>> ...] >>>>>> 14:00:28,084 ERROR [Ejb3Configuration] Container is providing a null >>>>>> PersistenceUnitRootUrl: discovery impossible >>>>>> ... >>>>>> >>>>>> I noticed that in your "Running JBoss Seam 2 on Geronimo 2.1" >>>>>> article, when >>>>>> you show the log, it has the same error as well. >>>>>> >>>>>> The difference appears to be, your example continues to load the >>>>>> booking >>>>>> application, and mine throws an exception on the next line: >>>>>> >>>>>> 14:00:28,115 ERROR [GBeanInstanceState] Error while starting; GBean >>>>>> is now >>>>>> in the FAILED state: >>>>>> abstractName="org.jboss.seam.examples.jee5/jboss-seam-jee5/2.1.0.A1/ear?EJBModule=jboss-seam-jee5.jar,J2EEApplication=org.jboss.seam.examples.jee5/jboss-seam-jee5/2.1.0.A1/ear,PersistenceUnitModule=jboss-seam-jee5.jar,j2eeType=PersistenceUnit,name=bookingDatabase" >>>>>> >>>>>> >>>>>> java.lang.NullPointerException >>>>>> at >>>>>> org.jboss.util.file.ArchiveBrowser.getBrowser(ArchiveBrowser.java:62) >>>>>> at >>>>>> org.hibernate.ejb.Ejb3Configuration.scanForXmlFiles(Ejb3Configuration.java:606) >>>>>> >>>>>> >>>>>> at >>>>>> org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:351) >>>>>> >>>>>> >>>>>> at >>>>>> org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:126) >>>>>> >>>>>> >&
Re: Geronimo 2.1 and Seam
Hi Jacek, I just noticed something in my last posting to David. In my error log I posted: ... 14:00:28,084 INFO [Ejb3Configuration] Processing PersistenceUnitInfo [ name: bookingDatabase ...] 14:00:28,084 ERROR [Ejb3Configuration] Container is providing a null PersistenceUnitRootUrl: discovery impossible ... I noticed that in your "Running JBoss Seam 2 on Geronimo 2.1" article, when you show the log, it has the same error as well. The difference appears to be, your example continues to load the booking application, and mine throws an exception on the next line: 14:00:28,115 ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED state: abstractName="org.jboss.seam.examples.jee5/jboss-seam-jee5/2.1.0.A1/ear?EJBModule=jboss-seam-jee5.jar,J2EEApplication=org.jboss.seam.examples.jee5/jboss-seam-jee5/2.1.0.A1/ear,PersistenceUnitModule=jboss-seam-jee5.jar,j2eeType=PersistenceUnit,name=bookingDatabase" java.lang.NullPointerException at org.jboss.util.file.ArchiveBrowser.getBrowser(ArchiveBrowser.java:62) at org.hibernate.ejb.Ejb3Configuration.scanForXmlFiles(Ejb3Configuration.java:606) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:351) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:126) at org.apache.geronimo.persistence.PersistenceUnitGBean.(PersistenceUnitGBean.java:119) ... I thought it was interesting that although we recieved the same error, your example continued to deploy and run, and mine stopped the deploy with those exceptions. Thanks, .Burt Jacek Laskowski wrote: > > On Wed, Feb 27, 2008 at 5:51 PM, David Jencks <[EMAIL PROTECTED]> > wrote: > >> did you complain about this on the lists when you found the problem? > > Complain? No, not at all. Just put a note with other stuff and it > might not get enough attention. See > http://www.nabble.com/forum/ViewPost.jtp?post=13785778. > > Jacek > > -- > Jacek Laskowski > http://www.JacekLaskowski.pl > > -- View this message in context: http://www.nabble.com/Geronimo-2.1-and-Seam-tp15621154s134p15749616.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Geronimo 2.1 and Seam
ce.createInstance(GBeanInstance.java:998) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:268) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:555) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379) at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:456) at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:534) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:515) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:867) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:342) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:867) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) at org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:172) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1426) at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1264) at java.security.AccessController.doPrivileged(Native Method) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1366) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305) at sun.rmi.transport.Transport$1.run(Transport.java:159) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:155) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) Caused by: org.apache.openejb.OpenEJBException: Error building bean 'HotelBookingAction'. Exception: class org.apache.openejb.OpenEJBException: PersistenceUnit 'bookingDatabase 91456273' not found for EXTENDED ref 'org.jboss.seam.example.booking.HotelBookingAction/em': PersistenceUnit 'bookingDatabase 91456273' not found for EXTENDED ref 'org.jboss.seam.example.booking.HotelBookingAction/em' at org.apache.openejb.assembler.classic.EjbJarBuilder.build(EjbJarBuilder.java:64) at org.apache.openejb.assemb
Re: Geronimo 2.1 and Seam
at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305) at sun.rmi.transport.Transport$1.run(Transport.java:159) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:155) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) 10:40:45,381 WARN [BasicLifecycleMonitor] Exception occured while notifying listener java.lang.NoClassDefFoundError: EDU/oswego/cs/dl/util/concurrent/ConcurrentReaderHashMap at org.jboss.util.file.ArchiveBrowser.(ArchiveBrowser.java:52) ... I think this is good progress! Could you let me know what I need to do next? Thanks very much, .Burt djencks wrote: > > > On Feb 28, 2008, at 9:47 AM, Burt Prior wrote: > >> >> Hi David and Jacek, >> >>> If you install this in your geronimo repo you should be able to >>> get past >>> this problem. >> >> Excellent. Could you point me to what I need to install? Is it in >> subversion repo? > > cd > mkdir -p repository/org/apache/geronimo/modules/geronimo-persistence- > jpa10/2.2-SNAPSHOT > wget http://people.apache.org/repo/m2-snapshot-repository/org/apache/ > geronimo/modules/geronimo-persistence-jpa10/2.2-SNAPSHOT/geronimo- > persistence-jpa10-2.2-20080228.021634-2.jar > mv geronimo-persistence-jpa10-2.2-20080228.021634-2.jarrepository/ > org/apache/geronimo/modules/geronimo-persistence-jpa10/2.2-SNAPSHOT/ > geronimo-persistence-jpa10-2.2-SNAPSHOT.jar > > then edit var/config/artifact_aliases.properties > > add lines > > org.apache.geronimo.modules/geronimo-persistence-jpa10// > jar=org.apache.geronimo.modules/geronimo-persistence-jpa10/2.2- > SNAPSHOT/jar > org.apache.geronimo.modules/geronimo-persistence-jpa10/2.1/ > jar=org.apache.geronimo.modules/geronimo-persistence-jpa10/2.2- > SNAPSHOT/jar > > I have a lot of trouble writing directions that can be followed, so > don't be shy about complaining :-) > hmmm we need console and gshell actions to upgrade an artifact > from a known handy repo such as the apache snapshot repo... > > GERONIMO-3884 > > thanks > david jencks > >> >> Do I still need to have Hibernate patched (correctly) to avoid the >> NPE? >> >> I'm trying to run thru the exact setup steps I need to do on >> Geronimo to get >> it working. >> >> Thanks, >> .Burt >> >> >> >> djencks wrote: >>> >>> >>> On Feb 27, 2008, at 6:01 PM, Jacek Laskowski wrote: >>> >>>> On Wed, Feb 27, 2008 at 5:51 PM, David Jencks >>>> <[EMAIL PROTECTED]> wrote: >>>> >>>>> did you complain about this on the lists when you found the >>>>> problem? >>>> >>>> Complain? No, not at all. Just put a note with other stuff and it >>>> might not get enough attention. See >>>> http://www.nabble.com/forum/ViewPost.jtp?post=13785778. >>> >>> I even remember reading that post :-( >>> >>> Anyway I think it's fixed now and I pushed the jar for trunk >>> org/apache/geronimo/modules/geronimo-persistence-jpa10/2.2-SNAPSHOT/ >>> geronimo-persistence-jpa10-2.2-20080228.021634-2.jar >>> to the apache snapshot repo. >>> >>> If you install this in your geronimo repo you should be able to get >>> past this problem. It might be simpler to name it geronimo- >>> persistence-jpa10-2.1.jar although it would be better to keep its >>> real name and put it in the right place and if necessary use an >>> artifact_alias entry to get geronimo to find it. >>> >>> entries would look like >>> org.apache.geronimo.modules/geronimo-persistence-jpa10// >>> jar=org.apache.geronimo.modules/geronimo-persistence-jpa10/2.2- >>> SNAPSHOT
Re: Geronimo 2.1 and Seam
Hi David and Jacek, > If you install this in your geronimo repo you should be able to get past > this problem. Excellent. Could you point me to what I need to install? Is it in subversion repo? Do I still need to have Hibernate patched (correctly) to avoid the NPE? I'm trying to run thru the exact setup steps I need to do on Geronimo to get it working. Thanks, .Burt djencks wrote: > > > On Feb 27, 2008, at 6:01 PM, Jacek Laskowski wrote: > >> On Wed, Feb 27, 2008 at 5:51 PM, David Jencks >> <[EMAIL PROTECTED]> wrote: >> >>> did you complain about this on the lists when you found the problem? >> >> Complain? No, not at all. Just put a note with other stuff and it >> might not get enough attention. See >> http://www.nabble.com/forum/ViewPost.jtp?post=13785778. > > I even remember reading that post :-( > > Anyway I think it's fixed now and I pushed the jar for trunk > org/apache/geronimo/modules/geronimo-persistence-jpa10/2.2-SNAPSHOT/ > geronimo-persistence-jpa10-2.2-20080228.021634-2.jar > to the apache snapshot repo. > > If you install this in your geronimo repo you should be able to get > past this problem. It might be simpler to name it geronimo- > persistence-jpa10-2.1.jar although it would be better to keep its > real name and put it in the right place and if necessary use an > artifact_alias entry to get geronimo to find it. > > entries would look like > org.apache.geronimo.modules/geronimo-persistence-jpa10// > jar=org.apache.geronimo.modules/geronimo-persistence-jpa10/2.2- > SNAPSHOT/jar > org.apache.geronimo.modules/geronimo-persistence-jpa10/2.1/ > jar=org.apache.geronimo.modules/geronimo-persistence-jpa10/2.2- > SNAPSHOT/jar > > hope this helps > david jencks > > >> >> Jacek >> >> -- >> Jacek Laskowski >> http://www.JacekLaskowski.pl > > > > -- View this message in context: http://www.nabble.com/Geronimo-2.1-and-Seam-tp15621154s134p15741951.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Geronimo 2.1 and Seam
Hi David,
I'm using the latest production Hibernate code from:
Hibernate Core 3.2
Hibernate Annotations 3.3.0.GA
Hibernate EntityManager 3.3.1.GA
Hibernate Tools 3.2.0.GA
Hibernate Validator 3.0.0.GA
Here was the patch i did to
C:\hibernate-entitymanager-3.3.1.GA\src\org\hibernate\ejb\Ejb3Configuration.java:
...
344: boolean[] detectArtifactForOtherJars = getDetectedArtifacts(
info.getProperties(), null, false );
345: boolean[] detectArtifactForMainJar = getDetectedArtifacts(
info.getProperties(), null, info.excludeUnlistedClasses() );
346:
347: // 022508: [EMAIL PROTECTED]: added patch to avoid NPE when running
Geronimo.
348:
349: if (info.getJarFileUrls() != null) {
350:
351: for ( URL jar : info.getJarFileUrls() ) {
352: if ( detectArtifactForOtherJars[0] ) scanForClasses( jar, packages,
entities );
353: scanForXmlFiles( jar, hbmFiles, XML_SEARCH.getType(
detectArtifactForOtherJars[1], searchForORMFiles ) );
354: }
355:
356:}
357:
358:if ( detectArtifactForMainJar[0] ) scanForClasses(
info.getPersistenceUnitRootUrl(), packages, entities );
359:scanForXmlFiles( info.getPersistenceUnitRootUrl(),
hbmFiles,
XML_SEARCH.getType( detectArtifactForMainJar[1], searchForORMFiles ) );
...
This code section is a bit different than Jacek's example in this version of
Hibernate.
Or perhaps I didn't apply the patch correctly. I did see the updated
hibernate-entitymanager.jar in:
C:\jboss-seam-2.1.0.A1\lib\hibernate-entitymanager.jar that I assume the
booking example is using instead of:
C:\hibernate-entitymanager-3.3.1.GA\hibernate-entitymanager.jar
Thanks,
.Burt
djencks wrote:
>
>
> On Feb 27, 2008, at 3:40 PM, Burt Prior wrote:
>
> Do you know what version of hibernate is in use? I looked for the
> source code that could cause this but so far it makes no sense to
> me. If you can debug here and poke around in the
> PersistenceUnitInfoImpl to see if something is null or gives an
> NPE??? that would be helpful. My best guess from http://
> fisheye.jboss.com/browse/Hibernate/entitymanager/trunk/src/java/org/
> hibernate/ejb/Ejb3Configuration.java?r=11344 is that the
> info.getJarFileURLs() is returning null but I can't see how that
> could be happening.
>
>
>> java.lang.NullPointerException
>> at
>> org.hibernate.ejb.Ejb3Configuration.configure
>> (Ejb3Configuration.java:346)
>> at
>> org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFac
>> tory(HibernatePersistence.java:126)
>> at
>> org.apache.geronimo.persistence.PersistenceUnitGBean.
>> (PersistenceUnitGBean.java:117)
>
>
> thanks
> david jencks
>
>
>
--
View this message in context:
http://www.nabble.com/Geronimo-2.1-and-Seam-tp15621154s134p15741787.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Geronimo 2.1 and Seam
Hi Jacek, Please see my responses inline... > I can't work on it much now, but perhaps we could work it out together > - me thinking aloud and you trying it out. Deal? Sounds great! I'm willing do anything to work this issue out. It's very important to us! > Do you have any idea what "bookingDatabase 91456273" came from? No idea. > Did you make any changes in the example? Not a one. I have made no changes at all to the example. I wanted to use the example as is for Seam and Hibernate on Geronimo. Thanks very much for your help. We are really stuck on this. .Burt Jacek Laskowski wrote: > > On Wed, Feb 27, 2008 at 11:33 AM, Burt Prior <[EMAIL PROTECTED]> wrote: > >> >> [C:\geronimo-jetty6-javaee5-2.1\var\temp\geronimo-deploymentUtil44832.jar]: >> Error building bean 'HotelBookingAction'. Exception: class >> org.apache.openejb.OpenEJBException: PersistenceUnit >> 'bookingDatabase 91456273' not found for EXTENDED ref >> 'org.jboss.seam.example.booking.HotelBookingAction/em': >> PersistenceUnit 'bookingDatabase 91456273' not found for EXTENDED >> ref 'org.jboss.seam.example.booking.HotelBookingAction/em' > > Hi, > > I can't work on it much now, but perhaps we could work it out together > - me thinking aloud and you trying it out. Deal? > > Do you have any idea what "bookingDatabase 91456273" came from? I'll > have to ask Dave B (openejb) about the exact error message's origins. > I think openejb know nothing about oracle without some configuration > changes and it might be working with hsql because openejb works with > it by default. Can't really figure it out right now. Did you make any > changes in the example? I vaguely remember bookingDatabase PU, but > nothing springs to my mind about the numbers. > > Jacek > > -- > Jacek Laskowski > http://www.JacekLaskowski.pl > > -- View this message in context: http://www.nabble.com/Geronimo-2.1-and-Seam-tp15621154s134p15722053.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Geronimo 2.1 and Seam
oss.seam.example.booking.HotelBookingAction/em': PersistenceUnit 'bookingDatabase 91456273' not found for EXTENDED ref 'org.jboss.seam.example.booking.HotelBookingAction/em' C:\geronimo-jetty6-javaee5-2.1> We would greatly appreciate any help on this. We feel we are almost there. Thanks again, .Burt Jacek Laskowski wrote: > > On Tue, Feb 26, 2008 at 4:29 PM, Burt Prior <[EMAIL PROTECTED]> wrote: > >> The deployment plan uses the Derby database. I'm using Oracle. I've >> successfully installed the Oracle jar in the respository and a >> configured a >> (thin driver) database pool that jar. >> >> I now successfully build the app, but when I try to deploy.bat from the >> command line using the "The Plan", I get errors such as... >> >> "Exception in Thread.. java.lang.NoClassDefFoundError: >> oracle/jdbc/pool/OracleDataSource" >> >> This class is in the oracle jar, but I think the geronimo deployment >> plan is >> incorrect. > > Hi, > > Add Oracle Thin driver as a dependency to the app in the plan and > rerun the deployment. I think you need something like: > > > > org.apache.geronimo.hibernate.transaction > > geronimo-hibernate-transaction-manager-lookup > jar > > > com.oracle.thindriver > oracle-thin-driver > jar > > > > Note the part for the oracle thin driver. Update it with correct data > and give it a go. > > When in trouble, show the plan so it's easier to help you. > > Jacek > > -- > Jacek Laskowski > http://www.JacekLaskowski.pl > > -- View this message in context: http://www.nabble.com/Geronimo-2.1-and-Seam-tp15621154s134p15721151.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Geronimo 2.1 and Seam
Hi Jay, Thanks very much for the jar file. That helped a great deal. I'm stuck... I am now *almost* able to deploy the Seam 'booking' example. I'm having real problems with the geronimo deployment plan (The Plan) listed in the article. The deployment plan uses the Derby database. I'm using Oracle. I've successfully installed the Oracle jar in the respository and a configured a (thin driver) database pool that jar. I now successfully build the app, but when I try to deploy.bat from the command line using the "The Plan", I get errors such as... "Exception in Thread.. java.lang.NoClassDefFoundError: oracle/jdbc/pool/OracleDataSource" This class is in the oracle jar, but I think the geronimo deployment plan is incorrect. Can you give me some pointers/examples of setting up a deployment plan to use hibernate and oracle? Thanks, .Burt Jay D. McHugh-3 wrote: > > Hello Burt, > > Answers inline > > Burt Prior (bprior) wrote: >> Hi Geronimo Team, >> >> I hope I'm directing this question correctly. >> >> First, thank you all for your excellent work on Geronimo 2.1. Our team >> has standardized on Geronimo at our large enterprise, and we think its >> the best app server in the industry. >> > Thanks! >> >> We are in current development of an JSF/EJB3/OpenJPA application, and we >> would very much like to use Seam (2). >> >> For the past few days we have been trying (without much luck) to >> configure Geronimo to work with Seam and Hibernate; we would prefer >> OpenJPA as the persistence provider, but it appears impossible to use >> with Seam. >> >> I've tried to work thru: >> http://cwiki.apache.org/GMOxSAMPLES/running-jboss-seam-200ga-on-geronimo >> -21.html but the maven project to download the Hibernate Transaction >> Manager appears not to work, and we are finding the instructions a bit >> hard to follow. (we don't use Maven, we are Subversion users) >> $ mvn archetype:create -DgroupId=org.apache.geronimo.hibernate >> -DartifactId=geronimo-hibernate-transaction-manager-lookup >> > I have updated the directions to correspond to the released Geronimo 2.1 > version. But, I have not made it through testing all of the directions > after creating the transaction manager jar. > > For your convenience, here is a link to the jar that I built: > http://people.apache.org/~jaydm/hibernate/geronimo-hibernate-transaction-manager-lookup-1.0-SNAPSHOT.jar >> >> Question 1: >> >> Is there a Geronimo 2.1 build that already includes everything needed to >> run Seam 2 or Hibernate that I can download, so we do not have to >> manually patch it? >> > Not that I am aware of. >> >> Question 2: >> >> Is there any advice/guidance you can give my team regarding setting up >> Geronimo 2.1 to use Seam 2? We would very much like integrate Seam into >> Geronimo for our long term application development. >> > I think that after the tutorial has been re-tested for the released > Geronimo 2.1 version - that tutorial should be all you need to set up > Geronimo for Seam. >> >> Thanks for your time and great work, >> >> Burt Prior >> IT Engineer >> [EMAIL PROTECTED] >> Office: 408.853.4199 >> >> >> > > > -- View this message in context: http://www.nabble.com/Geronimo-2.1-and-Seam-tp15621154s134p15703423.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Geronimo 2.1 and Seam
Hi Geronimo Team, I hope I'm directing this question correctly. First, thank you all for your excellent work on Geronimo 2.1. Our team has standardized on Geronimo at our large enterprise, and we think its the best app server in the industry. We are in current development of an JSF/EJB3/OpenJPA application, and we would very much like to use Seam (2). For the past few days we have been trying (without much luck) to configure Geronimo to work with Seam and Hibernate; we would prefer OpenJPA as the persistence provider, but it appears impossible to use with Seam. I've tried to work thru: http://cwiki.apache.org/GMOxSAMPLES/running-jboss-seam-200ga-on-geronimo -21.html but the maven project to download the Hibernate Transaction Manager appears not to work, and we are finding the instructions a bit hard to follow. (we don't use Maven, we are Subversion users) $ mvn archetype:create -DgroupId=org.apache.geronimo.hibernate -DartifactId=geronimo-hibernate-transaction-manager-lookup Question 1: Is there a Geronimo 2.1 build that already includes everything needed to run Seam 2 or Hibernate that I can download, so we do not have to manually patch it? Question 2: Is there any advice/guidance you can give my team regarding setting up Geronimo 2.1 to use Seam 2? We would very much like integrate Seam into Geronimo for our long term application development. Thanks for your time and great work, Burt Prior IT Engineer [EMAIL PROTECTED] Office: 408.853.4199
