The following comment has been added to this issue:
Author: Pascal Scheffers
Created: Mon, 22 Nov 2004 8:33 AM
Body:
Can this be fixed? It seems trivial enough to do - Hani suggested the right
solution, I think. At least just don't list the Local object if it has a remote.
---------------------------------------------------------------------
View this comment:
http://opensource.atlassian.com/projects/xdoclet/browse/XDT-263?page=comments#action_15289
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/xdoclet/browse/XDT-263
Here is an overview of the issue:
---------------------------------------------------------------------
Key: XDT-263
Summary: Dublicate location attribute on <entity-deployment> in
orion-ejb-jar.xml
Type: Bug
Status: Open
Priority: Major
Original Estimate: 0 minutes
Time Spent: Unknown
Remaining: 0 minutes
Project: XDoclet
Components:
Orion Module
Versions:
1.2 Beta 2
Assignee: xdoclet-devel (Use for new issues)
Reporter: Christian Bj�rnbak
Created: Fri, 24 Jan 2003 12:59 AM
Updated: Mon, 22 Nov 2004 8:33 AM
Environment: iAS/OC4J 9.0.3.
Description:
Using the @ejb.bean/view-type="both" in CMP-2.0 results in two location
attributes on <entity-deployment> in orion-ejb-jar.xml
Example:
* @ejb.bean
* name="PostAdresseEJB"
* view-type="both"
* jndi-name="RemoteJNDINAME"
* local-jndi-name="LocalJNDINAME"
* primkey-field="id"
gives
<entity-deployment name="PostAdresseEJB"
call-timeout="60000"
clustering-schema="asynchronous-cache"
copy-by-value="false"
data-source="jdbc/OracleDS"
exclusive-write-access="false"
location="RemoteJNDINAME"
location="LocalJNDINAME"
max-tx-retries="0"
table="PostAdresse"
>
In OC4J this results a weird error where OC4J tries to find a table named
PostAdresseEJB_TouristO_1i5324.
(The TouristO part comes from the ear or jar files named TouristOnline...)
Nov. 26th Ludovic announced a fix for this
http://www.mail-archive.com/[email protected]/msg03558.html
but it haven't made it's way into the CVS yet...
Ludovic fixes the issue by removing the insertion a location attribute in
<entity-deployment>. This makes the OC4J use the ejb name as JNDI-name
(creating the location attribute at deployment time).
This means the the @ejb.bean/jndi-name and @ejb.bean/local-jndi-name is
ignored, but it's better than the current implementation...
The bug persists with any combination of not suppling and content of
@ejb.bean/jndi-name and @ejb.bean/local-jndi-name even giving them the same
value.
I don't know the reasoning behind the rest of the patch.
---------------------------------------------------------------------
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
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
