Afternoon guys,
Just curious about one thing... Does XDoclet fully support the new
features of WLS7.0? Is there documentation/examples on the specific
tags (Specificly clusters)? If it is the case, I'm going to stop using
EJBGen, and convert to XDoclet.
THANKS!
dav
-----Original Message-----
From: xdoclet-user-request
Sent: Wednesday, October 23, 2002 8:58 PM
To: xdoclet-user
Subject: Xdoclet-user digest, Vol 1 #673 - 10 msgs
Send Xdoclet-user mailing list submissions to
[EMAIL PROTECTED]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Xdoclet-user digest..."
Today's Topics:
1. EJB Security ([EMAIL PROTECTED])
2. Re: EJB Security (Konstantin Priblouda)
3. RE: EJB Security ([EMAIL PROTECTED])
4. RE: EJB Security (Konstantin Priblouda)
5. RE: EJB Security ([EMAIL PROTECTED])
6. Problems after upgrade to XDoclet 1.2.0 (Jesse Stockall)
7. xdoclet reverse (Sebastien BLANC)
8. RE: Problems after upgrade to XDoclet 1.2.0
(=?iso-8859-1?Q?Aslak_Helles=F8y?=)
9. RE: xdoclet reverse (=?us-ascii?Q?Aslak_Hellesoy?=)
10. Re: Problems after upgrade to XDoclet 1.2.0 (Jesse Stockall)
--__--__--
Message: 1
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: Wed, 23 Oct 2002 15:57:20 +0100
Subject: [Xdoclet-user] EJB Security
Hello all,
After blundering around in the darkness I am now doing the sensible
thing
and asking for help.
I am trying to implement through XDoclet 1.2 tags security on methods on
my
beans that allow only certain roles to access them. Could some kind sole
explain the correct tags I should use? and in what order. I am deploying
to
JBoss 3.0.3.
TIA.
Regards,
Stephen.
x 5125
------------------------------------------------------------------------
-------------------
Copyright material and/or confidential and/or privileged information may
be contained in this e-mail and any attached documents. The material
and information is intended for the use of the intended addressee only.
If you are not the intended addressee, or the person responsible for
delivering it to the intended addressee, you may not copy, disclose,
distribute, disseminate or deliver it to anyone else or use it in any
unauthorised manner or take or omit to take any action in reliance on
it. To do so is prohibited and may be unlawful. The views expressed in
this e-mail may not be official policy but the personal views of the
originator. If you receive this e-mail in error, please advise the
sender immediately by using the reply facility in your e-mail software,
or contact [EMAIL PROTECTED] Please also delete this e-mail and
all documents attached immediately.
Many thanks for your co-operation.
BMW Financial Services (GB) Limited is registered in England and Wales
under company number 01288537.
Registered Offices : Europa House, Bartley Way, Hook, Hants, RG27 9UF
------------------------------------------------------------------------
------------------
--__--__--
Message: 2
Date: Wed, 23 Oct 2002 08:17:12 -0700 (PDT)
From: Konstantin Priblouda <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Re: [Xdoclet-user] EJB Security
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
--- [EMAIL PROTECTED] wrote:
> Hello all,
>
> After blundering around in the darkness I am now
> doing the sensible thing
> and asking for help.
>
> I am trying to implement through XDoclet 1.2 tags
> security on methods on my
> beans that allow only certain roles to access them.
> Could some kind sole
> explain the correct tags I should use? and in what
> order. I am deploying to
> JBoss 3.0.3.
You can use:
@ejb:permission role-name="foo,bar,baz"
( or just unchecked="true" )
on both class and method level
( on class level applies everywhere, method overrides
class setting )
Additionally, you can specify role-name="foo,bar,baz"
or unchecked on: @ejb.pk , and all finder tags
regards,
=====
Konstantin Priblouda ( ko5tik ) Freelance Software developer
< http://www.pribluda.de > < play java games -> http://www.yook.de >
< render charts online -> http://www.pribluda.de/povray/ >
__________________________________________________
Do you Yahoo!?
Y! Web Hosting - Let the expert host your web site
http://webhosting.yahoo.com/
--__--__--
Message: 3
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: [Xdoclet-user] EJB Security
Date: Wed, 23 Oct 2002 16:18:51 +0100
That's what I thought, but this does not seem to work. The container
still
allows the method to be executed. Is there something else I have missed?
Thanks again.
-----Original Message-----
From: Konstantin Priblouda [mailto:kpriblouda@;yahoo.com]
Sent: 23 October 2002 16:17
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [Xdoclet-user] EJB Security
--- [EMAIL PROTECTED] wrote:
> Hello all,
>
> After blundering around in the darkness I am now
> doing the sensible thing
> and asking for help.
>
> I am trying to implement through XDoclet 1.2 tags
> security on methods on my
> beans that allow only certain roles to access them.
> Could some kind sole
> explain the correct tags I should use? and in what
> order. I am deploying to
> JBoss 3.0.3.
You can use:
@ejb:permission role-name="foo,bar,baz"
( or just unchecked="true" )
on both class and method level
( on class level applies everywhere, method overrides
class setting )
Additionally, you can specify role-name="foo,bar,baz"
or unchecked on: @ejb.pk , and all finder tags
regards,
=====
Konstantin Priblouda ( ko5tik ) Freelance Software developer
< http://www.pribluda.de > < play java games -> http://www.yook.de >
< render charts online -> http://www.pribluda.de/povray/ >
__________________________________________________
Do you Yahoo!?
Y! Web Hosting - Let the expert host your web site
http://webhosting.yahoo.com/
------------------------------------------------------------------------
-------------------
Copyright material and/or confidential and/or privileged information may
be contained in this e-mail and any attached documents. The material
and information is intended for the use of the intended addressee only.
If you are not the intended addressee, or the person responsible for
delivering it to the intended addressee, you may not copy, disclose,
distribute, disseminate or deliver it to anyone else or use it in any
unauthorised manner or take or omit to take any action in reliance on
it. To do so is prohibited and may be unlawful. The views expressed in
this e-mail may not be official policy but the personal views of the
originator. If you receive this e-mail in error, please advise the
sender immediately by using the reply facility in your e-mail software,
or contact [EMAIL PROTECTED] Please also delete this e-mail and
all documents attached immediately.
Many thanks for your co-operation.
BMW Financial Services (GB) Limited is registered in England and Wales
under company number 01288537.
Registered Offices : Europa House, Bartley Way, Hook, Hants, RG27 9UF
------------------------------------------------------------------------
------------------
--__--__--
Message: 4
Date: Wed, 23 Oct 2002 08:33:26 -0700 (PDT)
From: Konstantin Priblouda <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: RE: [Xdoclet-user] EJB Security
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
--- [EMAIL PROTECTED] wrote:
> That's what I thought, but this does not seem to
> work. The container still
> allows the method to be executed. Is there something
> else I have missed?
>
> Thanks again.
In case you need electric light, you shall swith it
on.
The same is with security which is disable by default
in JBoss.
Basically, you have to specify your security domain in
your application ( jboss.xml ). If you do not, all
your beans go into "other" application policy, and you
have to configure it
in jboss confs.
File is:
server/default/conf/login-config.xml
Here are my configs:
( jboss.xml )
<jboss>
<secure>True</secure>
<security-domain>java:/jaas/ukw</security-domain>
<container-configurations>
</container-configurations>
</jboss>
login-config.xml:
<application-policy name = "ukw">
<!--
security policy for ukw
application
-->
<authentication>
<login-module code =
"org.jboss.security.auth.spi.UsersRolesLoginModul
flag = "required">
<module-option name =
"unauthenticatedIdentity">nobody<
</login-module>
</authentication>
</application-policy>
You do not mind me to spare properties files with my
actual user passwords and roles?
regards,
=====
Konstantin Priblouda ( ko5tik ) Freelance Software developer
< http://www.pribluda.de > < play java games -> http://www.yook.de >
< render charts online -> http://www.pribluda.de/povray/ >
__________________________________________________
Do you Yahoo!?
Y! Web Hosting - Let the expert host your web site
http://webhosting.yahoo.com/
--__--__--
Message: 5
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: [Xdoclet-user] EJB Security
Date: Wed, 23 Oct 2002 16:46:34 +0100
Thanks.
-----Original Message-----
From: Konstantin Priblouda [mailto:kpriblouda@;yahoo.com]
Sent: 23 October 2002 16:33
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: [Xdoclet-user] EJB Security
--- [EMAIL PROTECTED] wrote:
> That's what I thought, but this does not seem to
> work. The container still
> allows the method to be executed. Is there something
> else I have missed?
>
> Thanks again.
In case you need electric light, you shall swith it
on.
The same is with security which is disable by default
in JBoss.
Basically, you have to specify your security domain in
your application ( jboss.xml ). If you do not, all
your beans go into "other" application policy, and you
have to configure it
in jboss confs.
File is:
server/default/conf/login-config.xml
Here are my configs:
( jboss.xml )
<jboss>
<secure>True</secure>
<security-domain>java:/jaas/ukw</security-domain>
<container-configurations>
</container-configurations>
</jboss>
login-config.xml:
<application-policy name = "ukw">
<!--
security policy for ukw
application
-->
<authentication>
<login-module code =
"org.jboss.security.auth.spi.UsersRolesLoginModul
flag = "required">
<module-option name =
"unauthenticatedIdentity">nobody<
</login-module>
</authentication>
</application-policy>
You do not mind me to spare properties files with my
actual user passwords and roles?
regards,
=====
Konstantin Priblouda ( ko5tik ) Freelance Software developer
< http://www.pribluda.de > < play java games -> http://www.yook.de >
< render charts online -> http://www.pribluda.de/povray/ >
__________________________________________________
Do you Yahoo!?
Y! Web Hosting - Let the expert host your web site
http://webhosting.yahoo.com/
------------------------------------------------------------------------
-------------------
Copyright material and/or confidential and/or privileged information may
be contained in this e-mail and any attached documents. The material
and information is intended for the use of the intended addressee only.
If you are not the intended addressee, or the person responsible for
delivering it to the intended addressee, you may not copy, disclose,
distribute, disseminate or deliver it to anyone else or use it in any
unauthorised manner or take or omit to take any action in reliance on
it. To do so is prohibited and may be unlawful. The views expressed in
this e-mail may not be official policy but the personal views of the
originator. If you receive this e-mail in error, please advise the
sender immediately by using the reply facility in your e-mail software,
or contact [EMAIL PROTECTED] Please also delete this e-mail and
all documents attached immediately.
Many thanks for your co-operation.
BMW Financial Services (GB) Limited is registered in England and Wales
under company number 01288537.
Registered Offices : Europa House, Bartley Way, Hook, Hants, RG27 9UF
------------------------------------------------------------------------
------------------
--__--__--
Message: 6
From: Jesse Stockall <[EMAIL PROTECTED]>
To: xdoclet-user <[EMAIL PROTECTED]>
Date: 23 Oct 2002 13:15:40 -0400
Subject: [Xdoclet-user] Problems after upgrade to XDoclet 1.2.0
Hi
I have successfully using XDoclet 1.1.2 for many months to generate
deployment descriptors.
I wanted some of the new 1.2 features, so I decided to upgrade. After
sorting out the <taskdef> issues and removing the sourcepath and
classpathref attributes, I was able to get 1.2.0 to run. Unfortunately
the ejb-jar.xml it generates is empty.
I changed all the @tags to use @ejb.bean instead of @ebj:bean.
This is a sample of the tags in my beans:
/**
* The TokenBean implements a token for administrative access.
* Authentication currently instantiates a token directly in the
* Authenticator bean.
*
* @ejb.bean type="BMP" name="TokenBean" jndi-name="ejb/Token"
reentrant="False"
* @ejb.home remote-class="com.cryptocard.ejb.TokenHome"
* @ejb.pk class="com.cryptocard.mgtapi.TokenPK"
* @ejb.interface remote-class="com.cryptocard.ejb.TokenRemote"
*
* @ejb.env-entry name="CRYPTOCard/TokenDataType"
type="java.lang.String" value="jdbc"
* @ejb.resource-ref res-name="CRYPTOCard/TokenDataSource"
res-type="javax.sql.DataSource" res-auth="Container"
*
* @weblogic.resource-description
res-ref-name="CRYPTOCard/TokenDataSource"
jndi-name="CRYPTOCard/1"
*
*/
This is the target that works with 1.1.2:
<ejbdoclet
sourcepath="${src.dir}/java"
destdir="${build.dir}/ejb"
classpathref="ejbdoclet.class.path"
excludedtags="@version,@author"
ejbspec="1.1"
force="true">
<fileset dir="${src.dir}/java">
<include name="com/cryptocard/ejb/*Bean.java" />
</fileset>
<deploymentdescriptor
destdir="${descriptors.dir}/${ant.project.name}"
validatexml="true"
/>
<weblogic
version="6.1"
xmlencoding="UTF-8"
destdir="${descriptors.dir}/${ant.project.name}"
validatexml="true"
/>
</ejbdoclet>
With 1.2.0 I had to make a couple minor changes:
<ejbdoclet
destdir="${build.classes.dep.dir}"
excludedtags="@version,@author,@todo"
ejbspec="1.1"
force="true"
verbose="true">
<fileset dir="${src.dir}/java">
<include name="com/cryptocard/ejb/*Bean.java"/>
</fileset>
<deploymentdescriptor
destdir="${descriptors.dir}/${ant.project.name}"
validatexml="true"
/>
<weblogic
version="6.1"
xmlencoding="UTF-8"
destdir="${descriptors.dir}/${ant.project.name}"
validatexml="true"
/>
</ejbdoclet>
But now the generated deployment descriptor look like this:
<ejb-jar >
<description><![CDATA[No Description.]]></description>
<display-name>Generated by XDoclet</display-name>
<enterprise-beans>
<!-- Session Beans -->
<!--
To add session beans that you have deployment descriptor info
for, add
a file to your XDoclet merge directory called session-beans.xml
that contains
the <session></session> markup for those beans.
-->
<!-- Entity Beans -->
<!--
To add entity beans that you have deployment descriptor info for,
add
a file to your XDoclet merge directory called entity-beans.xml
that contains
the <entity></entity> markup for those beans.
-->
</enterprise-beans>
<!-- Assembly Descriptor -->
<assembly-descriptor >
<!--
To add additional assembly descriptor info here, add a file to
your
XDoclet merge directory called assembly-descriptor.xml that
contains
the <assembly-descriptor></assembly-descriptor> markup.
-->
<!-- transactions -->
<!-- finder transactions -->
</assembly-descriptor>
</ejb-jar>
I grabbed the latest from CVS and built it, but it generates the same
empty ejb-jar.xml file. The samples however build properly.
Any help would be appreciated.
Jesse
--
Jesse Stockall
[EMAIL PROTECTED]
--__--__--
Message: 7
Date: Wed, 23 Oct 2002 13:20:01 -0500
From: Sebastien BLANC <[EMAIL PROTECTED]>
Organization: Alcatel USA
To: [EMAIL PROTECTED]
Subject: [Xdoclet-user] xdoclet reverse
Hello !
just migrating from nothing to xdoclet use, our project has a pretty big
legacy of XML EJB descriptors.
I've seen on the xdoclet online help pages that reversing XML desc to
update java files is on its way, yet I need to find a solution right now
to do this job on thousands of file. Has anyone any information or
existing QAD scripts that would do the job ?
Thank you for any help.
Sebastien.
--__--__--
Message: 8
From: =?iso-8859-1?Q?Aslak_Helles=F8y?= <[EMAIL PROTECTED]>
To: "Jesse Stockall" <[EMAIL PROTECTED]>,
"xdoclet-user" <[EMAIL PROTECTED]>
Subject: RE: [Xdoclet-user] Problems after upgrade to XDoclet 1.2.0
Date: Wed, 23 Oct 2002 20:42:26 +0200
3 things that might be wrong in your environment:
1) Your definition of
<path id="ejbdoclet.class.path">
doesn not include Sun's EJB classes. It should
2) The fileset you pass to <ejbdoclet> is empty. Try to remove the
sourcepath attribute and include **/*.java.
3) Your TokenBean doesn't implement javax.ejb.EntityBean. Maybe it
extends
from a class Foo implements EntityBean that XDoclet doesn't know about?
Foo
must be on ejbdoclet.class.path too.
If this doesn't help, please let's see the class declaration and the
definition of ejbdoclet.class.path.
Aslak
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:xdoclet-user-admin@;lists.sourceforge.net]On Behalf Of Jesse
> Stockall
> Sent: 23. oktober 2002 19:16
> To: xdoclet-user
> Subject: [Xdoclet-user] Problems after upgrade to XDoclet 1.2.0
>
>
> Hi
>
> I have successfully using XDoclet 1.1.2 for many months to generate
> deployment descriptors.
>
> I wanted some of the new 1.2 features, so I decided to upgrade. After
> sorting out the <taskdef> issues and removing the sourcepath and
> classpathref attributes, I was able to get 1.2.0 to run. Unfortunately
> the ejb-jar.xml it generates is empty.
>
> I changed all the @tags to use @ejb.bean instead of @ebj:bean.
>
> This is a sample of the tags in my beans:
>
> /**
> * The TokenBean implements a token for administrative access.
> * Authentication currently instantiates a token directly in the
> * Authenticator bean.
> *
> * @ejb.bean type="BMP" name="TokenBean" jndi-name="ejb/Token"
> reentrant="False"
> * @ejb.home remote-class="com.cryptocard.ejb.TokenHome"
> * @ejb.pk class="com.cryptocard.mgtapi.TokenPK"
> * @ejb.interface remote-class="com.cryptocard.ejb.TokenRemote"
> *
> * @ejb.env-entry name="CRYPTOCard/TokenDataType"
> type="java.lang.String" value="jdbc"
> * @ejb.resource-ref res-name="CRYPTOCard/TokenDataSource"
> res-type="javax.sql.DataSource" res-auth="Container"
> *
> * @weblogic.resource-description
> res-ref-name="CRYPTOCard/TokenDataSource"
> jndi-name="CRYPTOCard/1"
> *
> */
>
>
> This is the target that works with 1.1.2:
>
> <ejbdoclet
> sourcepath="${src.dir}/java"
> destdir="${build.dir}/ejb"
> classpathref="ejbdoclet.class.path"
> excludedtags="@version,@author"
> ejbspec="1.1"
> force="true">
>
> <fileset dir="${src.dir}/java">
> <include name="com/cryptocard/ejb/*Bean.java" />
> </fileset>
>
> <deploymentdescriptor
> destdir="${descriptors.dir}/${ant.project.name}"
> validatexml="true"
> />
>
> <weblogic
> version="6.1"
> xmlencoding="UTF-8"
> destdir="${descriptors.dir}/${ant.project.name}"
> validatexml="true"
> />
> </ejbdoclet>
>
> With 1.2.0 I had to make a couple minor changes:
>
> <ejbdoclet
> destdir="${build.classes.dep.dir}"
> excludedtags="@version,@author,@todo"
> ejbspec="1.1"
> force="true"
> verbose="true">
>
> <fileset dir="${src.dir}/java">
> <include name="com/cryptocard/ejb/*Bean.java"/>
> </fileset>
>
> <deploymentdescriptor
> destdir="${descriptors.dir}/${ant.project.name}"
> validatexml="true"
> />
>
> <weblogic
> version="6.1"
> xmlencoding="UTF-8"
> destdir="${descriptors.dir}/${ant.project.name}"
> validatexml="true"
> />
>
> </ejbdoclet>
>
> But now the generated deployment descriptor look like this:
> <ejb-jar >
>
> <description><![CDATA[No Description.]]></description>
> <display-name>Generated by XDoclet</display-name>
>
> <enterprise-beans>
>
> <!-- Session Beans -->
> <!--
> To add session beans that you have deployment descriptor info
> for, add
> a file to your XDoclet merge directory called session-beans.xml
> that contains
> the <session></session> markup for those beans.
> -->
>
> <!-- Entity Beans -->
> <!--
> To add entity beans that you have deployment descriptor info
for,
> add
> a file to your XDoclet merge directory called entity-beans.xml
> that contains
> the <entity></entity> markup for those beans.
> -->
>
> </enterprise-beans>
>
> <!-- Assembly Descriptor -->
> <assembly-descriptor >
> <!--
> To add additional assembly descriptor info here, add a file to
> your
> XDoclet merge directory called assembly-descriptor.xml that
> contains
> the <assembly-descriptor></assembly-descriptor> markup.
> -->
>
> <!-- transactions -->
>
> <!-- finder transactions -->
> </assembly-descriptor>
>
> </ejb-jar>
>
> I grabbed the latest from CVS and built it, but it generates the same
> empty ejb-jar.xml file. The samples however build properly.
>
> Any help would be appreciated.
>
> Jesse
>
> --
> Jesse Stockall
> [EMAIL PROTECTED]
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: Influence the future
> of Java(TM) technology. Join the Java Community
> Process(SM) (JCP(SM)) program now.
> http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en
>
> _______________________________________________
> Xdoclet-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/xdoclet-user
--__--__--
Message: 9
From: =?us-ascii?Q?Aslak_Hellesoy?= <[EMAIL PROTECTED]>
To: "Sebastien BLANC" <[EMAIL PROTECTED]>,
<[EMAIL PROTECTED]>
Subject: RE: [Xdoclet-user] xdoclet reverse
Date: Wed, 23 Oct 2002 20:47:38 +0200
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:xdoclet-user-admin@;lists.sourceforge.net]On Behalf Of
Sebastien
> BLANC
> Sent: 23. oktober 2002 20:20
> To: [EMAIL PROTECTED]
> Subject: [Xdoclet-user] xdoclet reverse
>
>
> Hello !
> just migrating from nothing to xdoclet use, our project has a pretty
big
> legacy of XML EJB descriptors.
> I've seen on the xdoclet online help pages that reversing XML desc to
> update java files is on its way, yet I need to find a solution right
now
It's not really on its way anymore, because we're too busy with other
things. If someone wants to implement it, it would be awesome. XJavadoc
has
an API that allows tag insertion. So this would be a thingy that sits
between an XML parser and XJavadoc.
> to do this job on thousands of file. Has anyone any information or
> existing QAD scripts that would do the job ?
QAD? Qu'est-ce que c'est?
> Thank you for any help.
> Sebastien.
>
Aslak
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: Influence the future
> of Java(TM) technology. Join the Java Community
> Process(SM) (JCP(SM)) program now.
> http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en
>
> _______________________________________________
> Xdoclet-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/xdoclet-user
--__--__--
Message: 10
Subject: Re: [Xdoclet-user] Problems after upgrade to XDoclet 1.2.0
From: Jesse Stockall <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: xdoclet-user <[EMAIL PROTECTED]>
Date: 23 Oct 2002 14:53:27 -0400
On Wed, 2002-10-23 at 14:28, Konstantin Priblouda wrote:
>
> Ensure that you are using full qualified class names
> for inheritance from
> javax.ejb.(Entity|Session|MessageDriven)Bean
>
I do have the javax.ejb.* classes on the task classpath, XDoclet
wouldn't start without them.
I'm now using FQDN for the javax.ejb.* package and am getting generated
content in ejb-jar.xml.
Unfortunately XDoclet 1.2.0 is generating xml that does not comply to
the 1.1 spec.
With XDoclet 1.1.2 using ejbspec="1.1" a tag of "@ejb:home-method" would
generate xml like this:
<method>
<ebj-name>TokenBean</ejb-name>
<method-intf>Home</method-intf>
<method-name>remove</method-name>
<method-params>
<method-param>java.lang.Object</method-param>
</method-params>
</method>
Now with XDoclet 1.2.0 using ejbspec="1.1" a tag of "@ejb:home-method"
would generate xml like the above but will also generate another entry
with <method-intf>LocalHome</method-intf>
In EJB 1.1 only Home or Remote are valid for <method-intf>
With XDoclet 1.2.0 '@ejb.create-method' and '@ejb.interface-method' tags
with out view-type were getting 2 entries in ejb-jar.xml, one with
<method-intf>Remote</method-intf> and one with
<method-intf>Home</method-intf> again not supported by the 1.1 spec.
I can get around this by specifying
view=type="home" for @ejb.create-method
and
view=type="remote" for @ejb.interface-method
but the @ejb:home-method tags seem to ignore the view-type attribute.
Also xjavadoc does not like assert as a method name, even if running
with JRE 1.3.1 and it fails to parse a static initializer blocks that
have a ';' after the trailing '}'
Jesse
--
Jesse Stockall
[EMAIL PROTECTED]
--__--__--
_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
End of Xdoclet-user Digest
Visit our website at http://www.ubswarburg.com
This message contains confidential information and is intended only
for the individual named. If you are not the named addressee you
should not disseminate, distribute or copy this e-mail. Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses. The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission. If
verification is required please request a hard-copy version. This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.
-------------------------------------------------------
This sf.net email is sponsored by: Influence the future
of Java(TM) technology. Join the Java Community
Process(SM) (JCP(SM)) program now.
http://ad.doubleclick.net/clk;4729346;7592162;s?http://www.sun.com/javavote
_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
