Bugs item #613360, was opened at 2002-09-23 21:00 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=613360&group_id=22866
Category: JBossServer Group: v3.2 >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Dain Sundstrom (dsundstrom) Assigned to: Christian Riege (lqd) Summary: Verifier: abstract-schema-name Initial Comment: 10.3.13 An abstract-schema-name element for each entity bean. The abstract-schema-name must be a valid Java identifier and must be unique within the ejb-jar file. 10.6.14 The Bean Provider should not use reserved identifiers as ejb-names or abstract-schema-names. Reserved identifiers are discussed in Section 11.2.6.1. 22.2 Entity Bean’s abstract schema name. If the enterprise bean is an Entity Bean with container-managed persistence and cmp-version 2.x, the Bean Provider must specify the abstract schema name of the entity bean using the abstract-schema-name element. I suggest we make this an enforced error in 3.2 and 4.0 but only a warning in 3.0. ---------------------------------------------------------------------- >Comment By: Christian Riege (lqd) Date: 2002-10-01 11:06 Message: Logged In: YES user_id=176671 Fixed in 3.2. Backport to 3.0 when I have the time (includes some more changes), 4.0 will get a new Verification logic anyways so I don't see its worthwhile actually porting this. ---------------------------------------------------------------------- Comment By: Christian Riege (lqd) Date: 2002-09-24 15:06 Message: Logged In: YES user_id=176671 Hm, the Spec is (as usual) a bit ambigious in some cases here: according to the spec the rules of <ejb-name> being a valid Java Identifier only apply to CMP 2.0 Entity Beans. There's no mentioning of this on BMP, Session or Message Driven Beans. IMO we should enforce this on all types of EJB's though, it "Just makes sense" and it'll be consistent. Dain, what's your opinion on this issue? Of course this change hoses some parts of the testsuite and a couple of default JBoss Components (e.g. the JMX-EJB Adaptor). I'll try to fix these as I go along but I don't think I will catch all :). ---------------------------------------------------------------------- Comment By: Dain Sundstrom (dsundstrom) Date: 2002-09-23 21:02 Message: Logged In: YES user_id=251431 The valid Java identifier rule also applies to ejb-name so the common style name 'my/app/MyBean' name is not legal. Again, I think this should be enforced in 3.2 and 4.0 but not in 3.0. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=613360&group_id=22866 ------------------------------------------------------- This sf.net email is sponsored by: DEDICATED SERVERS only $89! Linux or FreeBSD, FREE setup, FAST network. Get your own server today at http://www.ServePath.com/indexfm.htm _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
