<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/xdoclet/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/xdoclet/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Thu, 22 Jul 2004 13:51:36 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/xdoclet/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>JBoss and insert-after-ejb-post-create</title><link>https://sourceforge.net/p/xdoclet/feature-requests/85/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hi xdoclet-team,&lt;/p&gt;
&lt;p&gt;I could not find the support for the JBoss&lt;br /&gt;
insert-after-ejb-post-create attribute.&lt;br /&gt;
How can I set this ?&lt;/p&gt;
&lt;p&gt;Greetings,&lt;br /&gt;
Tolja&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tolja Zubow</dc:creator><pubDate>Thu, 22 Jul 2004 13:51:36 -0000</pubDate><guid>https://sourceforge.net68fa12f11fe57d524dc1e9fa5c8b04aa45a103da</guid></item><item><title>Support Java 1.5 Syntax</title><link>https://sourceforge.net/p/xdoclet/feature-requests/84/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Is there any plan to support Java 1.5 syntax in &lt;br /&gt;
xjavadoc?&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Howard Chen</dc:creator><pubDate>Fri, 27 Feb 2004 20:00:09 -0000</pubDate><guid>https://sourceforge.netb841c4990241b331d651ecc2e12a76411292898c</guid></item><item><title>&amp;quot;Full path&amp;quot; JNDI Names</title><link>https://sourceforge.net/p/xdoclet/feature-requests/83/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;When XDoclet generates a jndi name, it uses the &lt;br /&gt;
bean name as default, unless if you don't specify it &lt;br /&gt;
in the @ejb:bean tag for each bean.&lt;br /&gt;
Would it be possible to have XDoclet generate &amp;amp;quot;full-&lt;br /&gt;
path&amp;amp;quot; jndi names automaticly?&lt;/p&gt;
&lt;p&gt;I use xdoclet to generate home and local home &lt;br /&gt;
interfaces in my J2EE application on a BEA Weblogic &lt;br /&gt;
server. &lt;br /&gt;
Say I have a bean named com.foo.MyBean, the jndi &lt;br /&gt;
name will be MyBean. I would like the possibility to &lt;br /&gt;
set the jndi name to com.foo.MyBean.&lt;/p&gt;
&lt;p&gt;Regards, Eigil Řkstad&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Fri, 04 Oct 2002 13:14:22 -0000</pubDate><guid>https://sourceforge.netb4d205e57941336e7794c4fad0ba4262c21828ed</guid></item><item><title>JBoss 3.0.0 - Support for JBoss-QL</title><link>https://sourceforge.net/p/xdoclet/feature-requests/82/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;After reading the JBoss 3.0.0 CMP documentation it seems that &lt;br /&gt;
the mechanism for overriding a finder methods EJB-QL with JBoss-&lt;br /&gt;
QL is to provide a correct &amp;amp;lt;query&amp;amp;gt; tag in the jbosscmp-jdbc.xml &lt;br /&gt;
file.&lt;/p&gt;
&lt;p&gt;I assume that the current @ejb:finder and &lt;br /&gt;
@jboss:finder-query tags were designed to allow this type of &lt;br /&gt;
configuration to be done simply. However the tags seem to &lt;br /&gt;
produce output in the jaws.xml file. This will not work with JBoss &lt;br /&gt;
3.0.0. The configuration that is need is:&lt;/p&gt;
&lt;p&gt;&amp;amp;lt;query&amp;amp;gt;&lt;/p&gt;
&lt;p&gt;&amp;amp;lt;query-method&amp;amp;gt;&lt;br /&gt;
&amp;amp;lt;method-&lt;br /&gt;
name&amp;amp;gt;findMatchingUsersUserName&amp;amp;lt;/method-name&amp;amp;gt;&lt;/p&gt;
&lt;p&gt;&amp;amp;lt;method-params&amp;amp;gt;&lt;br /&gt;
&amp;amp;lt;method-&lt;br /&gt;
param&amp;amp;gt;java.lang.String&amp;amp;lt;/method-param&amp;amp;gt;&lt;br /&gt;
&amp;amp;lt;/method-&lt;br /&gt;
params&amp;amp;gt;&lt;br /&gt;
&amp;amp;lt;/query-method&amp;amp;gt;&lt;br /&gt;
&amp;amp;lt;jboss-&lt;br /&gt;
ql&amp;amp;gt;&amp;amp;lt;![CDATA[SELECT OBJECT(a) FROM User a WHERE &lt;br /&gt;
(LCASE(a.username) = LCASE(?1))]]&amp;amp;gt;&amp;amp;lt;/jboss-&lt;br /&gt;
ql&amp;amp;gt;&lt;br /&gt;
&amp;amp;lt;/query&amp;amp;gt;&lt;/p&gt;
&lt;p&gt;Searching through the *.j files in XDoclet &lt;br /&gt;
there is no sign of a jboss-ql being produced.&lt;/p&gt;
&lt;p&gt;It seems that &lt;br /&gt;
either the existing tags need to be changed for JBoss 3.0.0 or a new &lt;br /&gt;
tag produced. The jboss:declared-sql seems to have been &lt;br /&gt;
intended to do something like this but does not look designed for &lt;br /&gt;
JBoss 3.0.0.&lt;/p&gt;
&lt;p&gt;Any comments welcome...&lt;/p&gt;
&lt;p&gt;Chris &lt;br /&gt;
Mein&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Mein</dc:creator><pubDate>Fri, 20 Sep 2002 13:50:51 -0000</pubDate><guid>https://sourceforge.net365ac8ab867ed07d89495661bffd40f4dd8adf38</guid></item><item><title>Add support for AspectJ</title><link>https://sourceforge.net/p/xdoclet/feature-requests/81/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;How hard is it to add support for AspectJ extension to &lt;br /&gt;
java? &lt;/p&gt;
&lt;p&gt;I am starting to write quite a few Aspects and I'd like to &lt;br /&gt;
add some custom tag to generate some stuff. Here's &lt;br /&gt;
an example:&lt;/p&gt;
&lt;p&gt;public abstract aspect AbstractSopTestAspect&lt;br /&gt;
{&lt;br /&gt;
/**&lt;br /&gt;
* @template &lt;br /&gt;
maven.patterntesting.java.sop.applicationCode&lt;br /&gt;
*/&lt;br /&gt;
public abstract pointcut applicationCode();&lt;br /&gt;
[...]&lt;br /&gt;
}&lt;/p&gt;
&lt;p&gt;That would generate the following source file:&lt;/p&gt;
&lt;p&gt;public aspect SopTestAspect extends &lt;br /&gt;
AbstractSopTestAspect&lt;br /&gt;
{&lt;br /&gt;
public pointcut applicationCode() : &lt;br /&gt;
@maven.patterntesting.java.sop.applicationCode@;&lt;br /&gt;
}&lt;/p&gt;
&lt;p&gt;But to implement this, I would need xdoclet to support &lt;br /&gt;
the aspectj extension, right? &lt;/p&gt;
&lt;p&gt;Thanks&lt;br /&gt;
-Vincent&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Vincent Massol</dc:creator><pubDate>Wed, 18 Sep 2002 17:47:13 -0000</pubDate><guid>https://sourceforge.net580da7ab9b302cc15d302068f1538b4ba7c06eda</guid></item><item><title>add jboss:clustered tag</title><link>https://sourceforge.net/p/xdoclet/feature-requests/80/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The jboss:clustered tag should ne added to the jboss&lt;br /&gt;
tags. It inserts the &amp;amp;lt;clustered&amp;amp;gt; tag in the jboss.xml&lt;br /&gt;
for the specific ejb&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dirk Hoffmann</dc:creator><pubDate>Sat, 07 Sep 2002 15:18:20 -0000</pubDate><guid>https://sourceforge.netc6d1c35b3161a78650b96495c7710081449fcf0e</guid></item><item><title>make VO soap-serializable</title><link>https://sourceforge.net/p/xdoclet/feature-requests/79/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Concerning value-objects: I make my sessionbean  &lt;br /&gt;
usecases also available through webservices. Which is &lt;br /&gt;
a common design and will become more common when &lt;br /&gt;
JSR 109 is implemented in J2EE 1.4. Then my value-&lt;br /&gt;
objects that I use to exchange domain-object trees with &lt;br /&gt;
the client will become SOAP-serialized. This will not &lt;br /&gt;
work when the value-objects implement any CM &lt;br /&gt;
relations. (I think it's great, by the way, that they DO &lt;br /&gt;
support CM relations) The 1-n relations between value-&lt;br /&gt;
objects are implemented using methods with a &lt;br /&gt;
java.util.Collection as a result value. &lt;br /&gt;
But SOAP can not deserialize untyped collections. &lt;br /&gt;
Which is logical when you think about it. See the axis-&lt;br /&gt;
user mailinglist thread that starts at &lt;br /&gt;
&lt;a href="http://marc.theaimsgroup.com/?l=axis-" rel="nofollow"&gt;http://marc.theaimsgroup.com/?l=axis-&lt;/a&gt;&lt;br /&gt;
user&amp;amp;amp;m=102879912615022&amp;amp;amp;w=2. &lt;br /&gt;
This could be fixed by providing, maybe by some switch, &lt;br /&gt;
the possibility to generate methods that return arrays of &lt;br /&gt;
the specific value-object instead of collections. Adding &lt;br /&gt;
and deleting value-object instances to the relation &lt;br /&gt;
should then be handled differently ofcourse. &lt;/p&gt;
&lt;p&gt;On the xdoclet-user list there was heartfelt support for &lt;br /&gt;
this request from David Ward.&lt;/p&gt;
&lt;p&gt;Sincerely,&lt;br /&gt;
Joost de Vries&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Joost de Vries</dc:creator><pubDate>Fri, 30 Aug 2002 12:44:53 -0000</pubDate><guid>https://sourceforge.netb04b69aad6ddb5fb44e3f1758b3bff6801c10763</guid></item><item><title>preserver parameter names in ejbCreate</title><link>https://sourceforge.net/p/xdoclet/feature-requests/78/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;the generate home interface of entity beans (probably session beans as well, I did not check) does not preserver the parameter names as used in the implementation of the ejbCreate method in the *Bean.java class.&lt;/p&gt;
&lt;p&gt;It would be much easier if those parameter names were used in the home interfaces since arg1, arg2, .. etc is not very descriptive when using codeinsight features of JBuilder or IntelliJ.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Fri, 23 Aug 2002 07:35:51 -0000</pubDate><guid>https://sourceforge.netba4968f8b611a25c3b180d19f8cbc65022f4ac1a</guid></item><item><title>xdoclet facade for external applications</title><link>https://sourceforge.net/p/xdoclet/feature-requests/77/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;xdoclet is all based on ant. it is very hard for&lt;br /&gt;
external 3rd party applications to run xdoclet without&lt;br /&gt;
going through some faked ant interface. it would be&lt;br /&gt;
very nice to have a facade layer on top of xdoclet so&lt;br /&gt;
that external applications can run xdoclet very easly..&lt;/p&gt;
&lt;p&gt;couple of methods that comes to mind.&lt;/p&gt;
&lt;p&gt;OutputStream process(task ,subtask, templateContent,&lt;br /&gt;
beanContent) &lt;/p&gt;
&lt;p&gt;OutputStream process (Document xmldocument)&lt;/p&gt;
&lt;p&gt;OutputStream process (subtask, template, bean)&lt;/p&gt;
&lt;p&gt;and so on.&lt;/p&gt;
&lt;p&gt;whole layer should be independent of ant scripts and&lt;br /&gt;
should always use stream, writers and readers..&lt;/p&gt;
&lt;p&gt;thanks for the good work&lt;/p&gt;
&lt;p&gt;talip&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Mon, 19 Aug 2002 23:54:32 -0000</pubDate><guid>https://sourceforge.net459ba0fe2b767c0710bdd1d7325713475260ff06</guid></item><item><title>Integrating Xdoclet, UML2EJB &amp;amp; Karapan</title><link>https://sourceforge.net/p/xdoclet/feature-requests/76/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;What a great combination would be to have a full &lt;br /&gt;
integration between UML2EJB, XDOCLET &amp;amp;amp; KARAPAN -&lt;br /&gt;
code generation nirvana from model to back-end &amp;amp;amp; front-&lt;br /&gt;
end - all SF projects!&lt;/p&gt;
&lt;p&gt;How far are we from that?  Are you guys considering &lt;br /&gt;
something similar or tried to get in touch with the other &lt;br /&gt;
projects?&lt;/p&gt;
&lt;p&gt;I hope it can be easily(?) done!&lt;/p&gt;
&lt;p&gt;Cheers&lt;/p&gt;
&lt;p&gt;Ismael&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ismael Matos</dc:creator><pubDate>Sat, 17 Aug 2002 14:01:53 -0000</pubDate><guid>https://sourceforge.netabe824a00370fa3fb9903d2040596db0379aef69</guid></item></channel></rss>