CC'd xdoclet-user, where this should have gone originally...
On Mon, 2005-02-07 at 16:55, Miriam Senovilla wrote:
> Hi!!!
>
> I'm trying to generate an EJB by Xdoclet, but it's generated with a
> wrong doctype.
...
> destDir="src" verbose="true" addedTags="@xdoclet-generated at
> ${TODAY},@copy
Update of /cvsroot/xdoclet/xdoclet/xdocs
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv25616
Modified Files:
valueobjects.xml
Log Message:
More typos (XDT-1267).
Index: valueobjects.xml
===
RCS file: /cvsroot/xdoc
Hi Miriam,
You can set the mergeDir attribute for the ejbdoclet ant task or the
deploymentdescriptor subtask (see
http://xdoclet.sourceforge.net/xdoclet/ant/xdoclet/modules/ejb/EjbDocletTask.html).
This is the mailing list for the xdoclet developpers. Please ask further
questions about the usag
+1. This looks like really good stuff. I've become quite a Tapestry
fanatic lately and I might find this module useful. One thing I would
ask for in addition to what this patch contains is to include an
xtags.xml file to document all of the Tapestry-specific tags.
Newcomb, Michael P. wrote:
I'm
Miriam Senovilla wrote:
But when i run xdoclet, it makes the ejb-jar.xml version 3.2:
http://www.jboss.org/j2ee/dtd/jboss_3_2.dtd";>
How can i specify that i want 4.0 version??? I'm using Jboss 4.0.1,
Eclipse, Xdoclet 1.2.2
Thanks
support for the correct JBoss 4.0 doctype was added in septemb
+1 - I was just thinking how nice it would be to have XDoclet for
Tapestry.
The most important piece is probably documenting and examples.
Matt
On Feb 7, 2005, at 2:08 PM, Newcomb, Michael P. wrote:
I'm getting ready to commit updates to the Apache module that will
enable support for generating
Title: tapestry support for XDoclet
I'm getting ready to commit updates to the Apache module that will enable support for generating Tapestry (http://jakarta.apache.org/tapestry) component-specifications and page-specifications.
It is currently under xdoclet.modules.apache.tapestry package an
Hello!
I agree with Andrew!
Parsing J2SE 5.0 syntax and supporting J2EE 1.4 seems to be good targets for
XDoclet v1.3.
Regards,
Magnus.
On Monday 07 February 2005 20:44, Andrew Stevens wrote:
> On Mon, 2005-02-07 at 17:33, Matthias Germann wrote:
> > Hi all,
> >
> > Is there already a release
On Mon, 2005-02-07 at 17:33, Matthias Germann wrote:
> Hi all,
>
> Is there already a release date planned for XDoclet 1.3?
"When it's ready".
Actually, unless we have complete J2EE 1.4 (i.e. EJB 2.1 & Servlet 2.4)
support and/or JDK 1.5 syntax parsing, I'd be inclined just to call it
1.2.3 rath
The following issue has been updated:
Updater: Chris Longfield (mailto:[EMAIL PROTECTED])
Date: Mon, 7 Feb 2005 12:46 PM
Comment:
This patch provides the ability to arbitrarily assign an access modifier class,
but gets rid of the 'type checking' functionality of the previous defini
Title: [Xdoclet-devel] [Fwd: XDoclet 1.3]
Hi,
not that I am aware of.
My intention when setting the next version
1.3 was that this will be the JDK 1.5/5.0 supporting release.
This means fixing XJD-41 and resulting
fallout in the XDoclet side.
Heiko
Von: [EMAIL PROTECTED]
im Auftrag v
I can't find any reference to it in the whole xdoclet project. IMHO, it
should be removed if it is legacy code.
Michael Kopp wrote:
I think it is legacy code, as I agree it is not used anymore. It should be
removed. I made some fixes myself to this file before noticing that they do
not have effect.
Hi all,
Is there already a release date planned for XDoclet 1.3?
Regards,
Matthias
Original Message
Subject:XDoclet 1.3
Date: Mon, 7 Feb 2005 12:44:59 +0300
From: Kasatkin Konstantin <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Hello Matthias,
Could you inform me w
Hi!!!
I'm trying to generate an EJB by Xdoclet, but it's
generated with a wrong doctype.
My bean is like that:
package entity.ejb;
import
java.rmi.RemoteException;
import
javax.ejb.CreateException;
import
javax.ejb.EntityBean;
import
javax.ejb.EntityContext;
import
javax.naming.Na
The merge directory is where you tell ejbdoclet to be it
:-)
Create a new directory in the project and build the same
directories in it as in the source path
where the corresponding java file can be
found
E.g.:
src/
de/
foo/
MyEJB.java
<-- needs merge file
ba
Hi!
I need to create an "entity-beans" xml on merge
directory, "to add entity beans that I
have deployment descriptor info for". Maybe it's obvious,
but, where is merge directory or where i've to create it?? Have i configure
Eclipse to do it??
Thanks
[EMAIL PROTECTED]Miriam
Senovilla Ma
Message:
The following issue has been re-assigned.
Assignee: Andrew Stevens (mailto:[EMAIL PROTECTED])
-
View the issue:
http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1267
Here is an overview of the issue:
The following comment has been added to this issue:
Author: Michael Kopp
Created: Mon, 7 Feb 2005 12:40 AM
Body:
Well kind of. My problem is not that the COMP_NAME does not have the Local
suffix, but that the generated code and the generated DD are not consistent.
The COMP_NAME i
The following comment has been added to this issue:
Author: Andrew Stevens
Created: Sun, 6 Feb 2005 6:57 PM
Body:
Wrong project (there's no docs/valueobject.html in xjavadoc, that's in
xdoclet). Also, it would have been helpful if you'd said what the typo was - I
assume it's the
19 matches
Mail list logo
