Title: Message
Hi,
 
I had the same problems recently. It is a classpath-related issue - make sure you have nothing on the command line classpath when running ant. Also, make sure you run 'ant clean' after an aborted build attempt.
 
Regards,
 

Liam.

 

 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Jose Luis Peleteiro - Sistemas e Processos
Sent: Wednesday, September 04, 2002 7:06 AM
To: '[EMAIL PROTECTED]'
Subject: RES: [JBoss-user] XDoclet jbosscmp-jdbc_xml.j

I downloaded CVS version, but when I try to make (ant) I recived:
 
BUILD FAILED
file:D:/cvsroot/xdoclet/modules/modules-common.ent:171: The <xdoclet> task doesn
't support the nested "externalizer" element.
 
 
Please, Help me.
-----Mensagem original-----
De: Jonathan.O'[EMAIL PROTECTED] [mailto:Jonathan.O'[EMAIL PROTECTED]]
Enviada em: terça-feira, 3 de setembro de 2002 12:03
Para: [EMAIL PROTECTED]
Assunto: Re: [JBoss-user] XDoclet jbosscmp-jdbc_xml.j


Jose,
This file only works with the released version of XDoclet. You may want to get the CVS source and try that instead. Here's what you'll need:
1. JDK 1.4 for the build in SAX parser.
2. ANT 1.5 (requires JDK 1.4)
3. CVS HEAD version of XDoclet.

Now for the changes we went through to make all this work:
A) The ejbdoclet task gets the root of the package structure from the <fileset dir = "${src.dir}"> rather than using package name in the java source file. The symptoms are the <ejb-class> will not be fully qualified in the ejb-jar.xml file.
B) If you use CMR-relationships, you will need (at least for JBoss 3.0.0) to add a @jboss.relation-mapping style = "foreign-key" otherwise you will get lots of exceptions during deployment.
C) The @jboss.table-name is deprecated. You must use @ejb.persistence table-name = "TABLE" instead,
D) The @ejb.select tag is no longer a bean tag. Instead you place it before the abstract ejbSelect method it applies to. Also, you must remove any signature parameter. This change definitely makes sense.

That's it, from what I remember, best of luck,
Jonathan O'Connor
Ph: +353 1 872 3305
Mob: +353 86 824 9736
Fax: +353 1 873 3612



Jose Luis Peleteiro - Sistemas e Processos <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]

03.09.2002 10:11
Please respond to jboss-user

       
        To:        "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
        cc:        
        Subject:        [JBoss-user] XDoclet jbosscmp-jdbc_xml.j



Can any one sendme this file. (jbosscmp-jdbc_xml.j)
Please!
 
 
FROM: Stephen Coy
DATE: 06/28/2002 07:17:41
SUBJECT: RE:  [JBoss-user] CMP 2.0 / FINDER CREATION PROBLEM

Unfortunately, xdoclet 1.1.2 has only limited support for custom jboss
queries for CMP 2.0.

"jboss:finder-query" generates JAWS (CMP 1.1) configuration data.

I'm including a modified jbosscmp-jdbc_xml.j file that we are using,
which has almost full support for "jboss:declared-sql" and "jboss:query"
tags, which generate <declared-sql> and <query> sections in your
jbosscmp-jdbc.xml file.

You need to replace this file in your xdoclet.jar.

Here's a sample:

 @jboss:declared-sql
                signature="Collection findInSequence()"
                order="precedence"
 @jboss:query
                signature="java.util.Collection
ejbSelectUserLists(com.whitesmiths.sacha.ejb.auth.interfaces.UserLocal
user)"
                query="SELECT DISTINCT r.worklist FROM User AS u, IN (u.userRoles)
AS r WHERE r.worklist IS NOT NULL AND u = ?1 ORDER BY
r.worklist.precedence ASC"
                strategy="on-find"
                page-size="16"

 @jboss:query
                signature="java.util.Set ejbSelectGeneric( java.lang.String query,
java.lang.Object[] args)"
                dynamic="true"

For more detailed information on these JBoss constructs, the USD10 CMP
documentation is well worth it.

Reply via email to