[
http://jira.jboss.com/jira/browse/JBSEAM-1304?page=comments#action_12414703 ]
Chris Simons commented on JBSEAM-1304:
--------------------------------------
As per the forum reference in the original issue, I am using OC4J 10.1.3.3 (latest build
with "full" EJB 3.0 support) and am running into the exact same issue deploying
the Booking example. Case in point, the Booking example did deploy to OC4J 11.1.1.0
(Technology Preview 4) properly.
2008-05-28 16:45:42.059 ERROR J2EE EJB-03027 [jboss-seam-jee5] An error occured deploying
EJB module: com.evermind.server.ejb.exception.DeploymentException:
[jboss-seam-jee5:jboss-seam-jee5] - No <around-invoke
or lifecycle callbacks were specified for interceptor
org.jboss.seam.ejb.SeamInterceptor.
08/05/28 16:45:42 WARNING: Application.setConfig Application: jboss-seam-jee5 is in failed
state as initialization failed.
java.lang.InstantiationException: Error initializing ejb-modules:
[jboss-seam-jee5:jboss-seam-jee5] - No <around-invoke
or lifecycle
callbacks were specified for interceptor org.jboss.seam.ejb.SeamInterceptor.
OC4J showing a blank page when deploying Glassfish example
----------------------------------------------------------
Key: JBSEAM-1304
URL:
http://jira.jboss.com/jira/browse/JBSEAM-1304
Project: Seam
Issue Type: Feature Request
Reporter: Richard Hoffman
We are trying to get a Seam project deployed to OC4J. So far, the recommendation is to
use the Glassfish example and deploy that to OC4J, but there are no instructions as to how
to do this...so far, myself and a few others on the forums have only managed to get OC4J
to show a blank screen. (I'm personally deploying via JDeveloper.)
See
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=100418 for
petemuir's request to make this a Jira ticket.
On a personal note, I don't have a preference as to who's EJB3 implementation to
use (if any...Hibernate is fine, too). I just need to prove Seam works on OC4J...my
client is making me use OC4J, despite my insistence that it's crap. :-/
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira