× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



WDSC by default puts all the JARs required by the web module into the
WEB-INF/lib directory (one of the mixed benefits of J2EE is that
everything gets encapsulated and can stand on its own).  You can
identify any non-standard (or not-standard-yet) classes because the
packages wil start with com.ibm.


-----Original Message-----
From: wdsci-l-bounces+rdean=landstar.com@xxxxxxxxxxxx
[mailto:wdsci-l-bounces+rdean=landstar.com@xxxxxxxxxxxx] On Behalf Of
Bartell, Aaron L. (TC)
Sent: Friday, October 29, 2004 6:17 PM
To: Websphere Development Studio Client for iSeries
Subject: [WDSCI-L] JSF and App Servers

As I read different groups implementation of JSF (IBM, Sun, etc) I am
finding that they all have their own custom JSP tag lib for the JSF
components.

My question is specifically this.  What do I need to watch out for if I
develop my JSF in WDSc using jsf-ibm.jar and deploy that to Tomcat 5?
Note that I am not using WDO which I have heard is IBM specific (for
now).

Thanks in advance,
Aaron Bartell

_______________________________________________
This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.