danch wrote: > Hmm. > Well I can help with JAWS: JAWS really should be removed from the 3.0 > codebase because even if you deploy a vanilla 1.1 CMP bean, Dain's > JDBCStoreManager should be handling it (uh, right, Dain?).
It should. It is not used much, so the code is probably more buggy. > To paraphrase Monty Python, "JAWS is dead! it is deceased! it is no more!" This is a backwards compatibility issue. I except to fully remove JAWS in JBoss 4.0. > From the trace, JAWS isn't trying to do read-ahead. For the historic > record, read-ahead defaulted off in JAWS. > > Does your ejb-jar have a jbosscmp-jdbc.xml, or a jaws.xml? It should be > only jbosscmp-jdbc.xml (although any jaws.xml should be ignored by JBoss > 3.0 or later). Trying to use jaws.xml with JBoss 3.x is getting to be a > FAQ issue, but I know Dain's been trying to help you with this so I > imagine you've got this right. > > I'll try to take a look tonight and see why 3.0 would use JAWS at all. It is used for applications that do not use the new EJB 2.0 dtd for the ejb-jar.xml file. This is an EJB 1.1 jar and therefore CMP 1.1. -dain _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
