I went through the Enterprise Java Beans tutorial exercises.. under lesson1 is a BonusApp that has an entity bean in it ( i think ). Works for me with 3.0beta (Solaris). Give this one a shot and goto
localhost:8080/BonusRoot/bonus.html ampere jec partslists 1037> echo $JBOSS_DIST/ /homes/bell/JBoss/jboss-3.0.0beta/ 09:34:56,761 INFO [MainDeployer] Deploying: file:/homes/bell/JBoss/jboss-3.0.0beta/deploy/BonusApp.ear 09:34:56,776 INFO [EARDeployer] Init J2EE application: file:/homes/bell/JBoss/jboss-3.0.0beta/deploy/BonusApp.ear 09:34:57,739 INFO [MainDeployer] Deploying: file:/homes/bell/JBoss/jboss-3.0.0beta/tmp/deploy/87.ejb-jar-ic.jar 09:34:58,048 INFO [EJBDeployer] Deploying CalcBean 09:34:59,156 INFO [MainDeployer] Deploying: file:/homes/bell/JBoss/jboss-3.0.0beta/tmp/deploy/88.ejb-jar-ic4.jar 09:35:00,758 INFO [EJBDeployer] Deploying BonusBean 09:35:04,274 INFO [JDBCInitCommand] Table 'BonusBean' already exists 09:35:04,546 INFO [EnterpriseContextCachePolicy] Cache policy scheduler started 09:35:04,552 INFO [MainDeployer] Deploying: file:/homes/bell/JBoss/jboss-3.0.0beta/tmp/deploy/89.war-ic.war 09:35:04,639 INFO [EmbeddedCatalinaServiceSX] deploy, ctxPath=/BonusRoot, warUrl=file:/homes/bell/JBoss/jboss-3.0.0beta/tmp/deploy/89.war-ic.war 09:35:11,799 INFO [EmbeddedCatalinaServiceSX] WebappLoader[/BonusRoot]: Deploying class repositories to work directory /homes/bell/JBoss/jboss-3.0.0beta/jakarta-tomcat-4.0.2/work/localhost/BonusR oot 09:35:11,875 INFO [EmbeddedCatalinaServiceSX] WebappLoader[/BonusRoot]: Deploy class files /WEB-INF/classes to /homes/bell/JBoss/jboss-3.0.0beta/jakarta-tomcat-4.0.2/work/localhost/BonusR oot/WEB-INF/classes 09:35:12,582 INFO [EmbeddedCatalinaServiceSX] StandardManager[/BonusRoot]: Seeding random number generator class java.security.SecureRandom 09:35:12,631 INFO [EmbeddedCatalinaServiceSX] StandardManager[/BonusRoot]: Seeding of random number generator has been completed 09:35:14,819 INFO [EmbeddedCatalinaServiceSX] ContextConfig[/BonusRoot]: Added certificates -> request attribute Valve 09:35:15,724 INFO [EmbeddedCatalinaServiceSX] StandardWrapper[/BonusRoot:default]: Loading container servlet default 09:35:17,734 INFO [EmbeddedCatalinaServiceSX] default: init 09:35:17,786 INFO [EmbeddedCatalinaServiceSX] StandardWrapper[/BonusRoot:invoker]: Loading container servlet invoker 09:35:18,081 INFO [EmbeddedCatalinaServiceSX] invoker: init 09:35:19,135 INFO [EmbeddedCatalinaServiceSX] jsp: init 09:35:24,965 INFO [EARDeployer] Deploying J2EE application: file:/homes/bell/JBoss/jboss-3.0.0beta/deploy/BonusApp.ear ----- Original Message ----- From: "Eric Jain" <[EMAIL PROTECTED]> To: "Jboss-User" <[EMAIL PROTECTED]> Sent: Friday, March 01, 2002 8:58 AM Subject: [JBoss-user] Beta can't deploy my entity beans > While TestSessionEJB alone can be deployed, deployment fails if I add an > entity bean. Used to work with JBoss alpha! > > > INFO [MainDeployer] Deploying: file:/C:/Programme/JBoss/deploy/test.jar > INFO [EJBDeployer] Deploying TestEntityEJB > INFO [EJBDeployer] Deploying TestSessionEJB > ERROR [EntityContainer] Exception in service lifecyle operation: create > org.jboss.deployment.DeploymentException: expected one strategy tag > at org.jboss.metadata.MetaData.getUniqueChild(MetaData.java:95) > at org.jboss.metadata.MetaData.getUniqueChildContent(MetaData.java:202) > at > org.jboss.ejb.plugins.cmp.jdbc.metadata.JDBCReadAheadMetaData.<init>(JDBCRea > dAheadMetaData.java:91) > ... > > > -- > Eric Jain > > > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > ********************************************************************** This e-mail and any files transmitted with it are confidential and may be legally privileged or otherwise exempt from disclosure under applicable law. This e-mail and its files are intended solely for the individual or entity to whom they are addressed and their content is the property of Smiths Aerospace. If you are not the intended recipient, please do not read, copy, use or disclose this communication. If you have received this e-mail in error please notify the e-mail administrator at [EMAIL PROTECTED] and then delete this e-mail, its files and any copies. This footnote also confirms that this e-mail message has been scanned for the presence of known computer viruses. ***********************************************************************
BonusApp.ear
Description: Binary data
Course OutlineThis is an outline of the topics covered in the PDF and HTML versions available above. Lesson 1: A Simple Session Bean
Lesson 2: A Simple Entity Bean
Lesson 3: Enterprise Bean Communications
Lesson 4: JavaServerTM Pages
Lesson 5: Adding JavaBeansTM Technology to the Mix.
Lesson 6: Extensible Markup Langauge (XML)
Lesson 7: JDBCTM Technology and Bean-Managed Persistence
Related InformationOther J2EE-related topics are listed here. Some are not yet available in the J2EE platform, but you can find information on those that are currently available in the documents noted. Managing TransactionsThe Java 2, Enterprise Edition, Developer's Guide has a good section on Transactions. Mail and MessagingThe Java Message Service API is not currently available. Chapter 10 of Designing Enterprise Applications also called J2EE Blueprints has an example of the email API.
SecurityThe Java 2, Enterprise Edition, Developer's Guide has a good section on Security. RMI-JRMP and RMI-IIOPJRMP is the Java technology-specific RMI protocol for looking up and referencing remote objects. Because of J2EE security restrictions, only application clients can create and reference an RMI object, but all J2EE application component types can be clients of (looked up and referenced by) RMI objects. J2EE application component types are application clients, applets, servlets/JSP pages, and Enterprise JavaBeans components. RMI over Internet Inter-ORB Protocol (IIOP) lets RMI code reference and look up an object using the CORBA CosNaming service. This gives you greater interoperability between architectures with little change to your existing RMI code. Enterprise JavaBean code is based on RMI, but currently the specification does not require support for being accessed by way of IIOP. This will change in a future version of the specification.
Monica Pawlan, a staff writer for the Java Developer ConnectionSM (JDC), is author of Essentials of the Java Programming Language: A Hands-On Guide (Addison-Wesley, 2000), and co-author of Advanced Programming for the Java 2 Platform (Addison-Wesley, 2000). Reader FeedbackTell us what you think of this article.
If you have other comments or ideas for future articles, please type them here:
[TOP]
|
