Yeah... I remember having to do this when I used JBoss 3.26...
b
Jeff Butler wrote:
The "java:comp/env" prefix is part of the J2EE specification - so it's
not Tomcat or iBATIS specific. But Tomcat JNDI works a little different
than other app servers. With most app servers, the "java:comp/env"
prefix gets added when resource references are defined in web.xml or
ejb-jar.xml.
Jeff Butler
On 2/22/06, *Eugeny N Dzhurinsky* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
On Wed, Feb 22, 2006 at 03:37:26PM +0100, Cimballi wrote:
> This a Tomcat specific prefix, not iBatis.
> Cimballi
Well, I'm not sure about that, because I'm using OSWorkflow and it uses
another JNDI resource, specified like this:
<propertysets>
<propertyset name="jdbc"
class="
com.merrimacind.devcase.devCase.workflow.storage.JDBCStoragePropertySetWrapper">
<arg name="datasource" value="jdbc/DefaultDS" />
<arg name=" table.name <http://table.name>"
value="OS_PROPERTYENTRY" />
<arg name="col.globalKey" value="GLOBAL_KEY" />
<arg name="col.itemKey" value="ITEM_KEY" />
<arg name="col.itemType" value="ITEM_TYPE" />
<arg name="col.string" value="STRING_VALUE" />
<arg name="col.date" value="DATE_VALUE" />
<arg name="col.data" value="DATA_VALUE" />
<arg name="col.float" value="FLOAT_VALUE" />
<arg name="col.number" value="NUMBER_VALUE" />
</propertyset>
<propertyset name="memory"
class="com.opensymphony.module.propertyset.memory.MemoryPropertySet" />
</propertysets>
no comp/env or whatever, and OSWorkflow isn't tomcat-related
application.
--
Eugene N Dzhurinsky
