Message: The following issue has been reopened.
--------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/xdoclet/secure/ViewIssue.jspa?key=XDT-220 Here is an overview of the issue: --------------------------------------------------------------------- Key: XDT-220 Summary: <utilobject> shouldn't default to neither COMP_NAME nor JNDI_NAME Type: Improvement Status: Reopened Priority: Major Time Spent: Unknown Remaining: 0 minutes Project: XDoclet Components: EJB Module Fix Fors: 1.2 Versions: 1.1.2 1.2 Beta 1 1.2 Beta 2 Assignee: xdoclet-devel (Use for new issues) Reporter: Marcus Brito Created: Wed, 1 Jan 2003 11:49 PM Updated: Sun, 16 Nov 2003 4:52 PM Description: The problem with COMP_NAME lookups in Util Object's has generated quite some traffic in the mailing list. Are we right defaulting to use logical lookups as the default in Util Object classes? Would we be right to use physical lookups instead? We can't tell it. I propose we shouldn't assume any default and make the kind parameter to <utilobject> task mandatory. That way we avoid the common "util object can't find my bean!" pitfall. --------------------------------------------------------------------- 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: GoToMyPC GoToMyPC is the fast, easy and secure way to access your computer from any Web browser or wireless device. Click here to Try it Free! https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl _______________________________________________ xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
