WebSphere Application Server - wsadmin - modifying JDBCProvider classpath ADDS new classpath

This is Interesting: Free IT Magazines  
Home > Archive > WebSphere Application Server > September 2006 > wsadmin - modifying JDBCProvider classpath ADDS new classpath





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author wsadmin - modifying JDBCProvider classpath ADDS new classpath

2006-09-28, 1:22 pm

I'm trying to update a JDBCProvider created from a template using wsadmin. When I submit the following command:

$AdminConfig modify $provider [subst {{description "$desc"} {classpath $cp}}];

(where $provider is the id of the JDBCProvider object, $desc is a string like "Oracle 9i JDBC Driver" and $cp is a list containing the full paths to two zip files, shown in the second <classpath> tag below)

This is what I see as a result in the resources.xml file:

<classpath>${ORACLE_JDBC_DRIVER_PATH}/ojdbc14.jar</classpath>
<classpath>/usr/WebSphere/AppServer/jars/jdbc/Oracle9iDriver/OracleClasses12.zip /usr/WebSphere/AppServer/jars/jdbc/Oracle9iDriver/ocrs12.zip</classpath>

I can't figure out why the modify adds this second <classpath> line instead of modifying the existing one. If I run the command a second time, it will just update the second <classpath> and leave the original one alone.
Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com