The following comment has been added to this issue:
Author: Dave Knipp
Created: Mon, 31 Jan 2005 9:04 AM
Body:
Sorry if I wasn't specific enough. I am currently trying to make our
application work in both easerver and jboss and to do that I am using xdoclet
on all of our EJBs. This is working beautifully except that the easerver
configuration file is not consistent with some of the attributes of @ejb.bean.
For instance the jndi-name is not used in the configuration file for sybase,
instead the jndi name is defaulted to the component's name, ie.
<configure type="update" entity="Component/ResReference:ComponentName/BeanName
/!merge">
</configure>
The way to override this default is to supply <property> tags to the
<configure> tag, like this :
<configure type="update"
entity="Component/ResReference:ComponentName/BeanName/!merge">
<property name="com.sybase.jaguar.component.bind.naming"
value="JNDIFromXdoclet" />
</configure>
If xdoclet were to include another tag, say @easerver.property which could have
two attributes, name and value.
This would allow me to declare something like this in within my class :
@easerver.property name="com.sybase.jaguar.component.bind.naming"
value="JNDINameForThisBean".
OR this could be automatically done with the @ejb.bean jndi-name attribute.
You could map that attribute to the 'com.sybase.jaguar.component.bind.naming'
property and create a <property> element under <configure> for that bean.
I realize there isn't alot of user base out there for easerver, but this would
be a really nice thing to have.
---------------------------------------------------------------------
View this comment:
http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1251?page=comments#action_15806
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1251
Here is an overview of the issue:
---------------------------------------------------------------------
Key: XDT-1251
Summary: EAServer Component Properties
Type: Improvement
Status: Open
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: XDoclet
Components:
Sybase Module
Versions:
1.2.2
Assignee: xdoclet-devel (Use for new issues)
Reporter: Dave Knipp
Created: Thu, 27 Jan 2005 3:18 PM
Updated: Mon, 31 Jan 2005 9:04 AM
Environment: EAServer 5.1, Xdoclet 1.2.2
Description:
I am currently in the process of trying to deploy to both jboss and easerver
and I'm using xdoclet to generate the ejb-jar.xml and the server specific
configuration files.
THe problem with easerver is that the local-jndi-name and jndi-name properties
of @ejb.bean do not correspond with the jndi names that easerver uses. It
bases the jndi name off of the component name that is declared in the 'entity'
attribute.
There should be a way to map the ejb.bean properties to the actual deployment
within easerver.
I know not many people are using easerer, but it woudl be nice to have this
functionality.
Thanks,
Dave
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/xdoclet/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
xdoclet-devel mailing list
xdoclet-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
