On 1/20/2011 11:18 AM, Jess Holle wrote:
> This is why I'd suggested a project classpath of
>
> WT_HOME/codebase (or a jar form thereof)
> WT_HOME/codebase/WEB-INF/lib/*.jar
> WT_HOME/lib/*.jar
>
> That should suffice for any server-side development.
Note that this is almost certainly /more/ than what you'll need for any
server-side development, but it gives you access to everything that the
Windchill server has at its disposal at runtime -- so you lack for
nothing. [Well, okay there is also the JDK's tools.jar, which you could
add if you want to call various JDK APIs that are not present in the JRE].
If you're writing code for the servlet engine (and not in R10.0), then
drop WT_HOME/lib/*.jar from this list -- as that's not accessible from
within the servlet engine and thus attempting to use anything in
WT_HOME/lib will just bring you frustration in this case. You'll
probably need to add back servlet.jar, though -- as the servlet engine
normally provides its own libraries in this regard but you need to spell
these out for compilation in most IDEs (and need to be sure to select
the right version of these in any case).
--
Jess Holle
