The following comment has been added to this issue:
Author: Andrew Stevens
Created: Wed, 2 Feb 2005 7:38 PM
Body:
>I realize there isn't a lot of user base out there for easerver
At last - I've found the other EAServer user :-)
I guess you're currently adding the extra properties in using merge points?
What exactly are you trying to set in that Component/ResReference property, the
bean's registered (JNDI) home interface name or the name of the bean that's
being referenced? Or is it something else? Are you using the
@easerver.resource-ref tag - that can insert the res-ref-name and res-link
properties in
<configure type="update" entity="Component/ResReference:Package/MyBean/!merge">
<property name="res-ref-name" value="ejb/OtherBean" />
<property name="res-link" value="Package/OtherBean" />
</configure>
A com.sybase.jaguar.component.bind.naming property in there is a new one on me,
though. It sounds more like a property of the bean rather than of a reference.
---------------------------------------------------------------------
View this comment:
http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1251?page=comments#action_15858
---------------------------------------------------------------------
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: Wed, 2 Feb 2005 7:38 PM
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
