| Author |
JSF compatibility issues
|
|
|
| I am developing portlet application for IBM WebSphere portal server v 5.1.0.1 using JSR 169 with JSF support, utilizing RAD 6.0.0.1 version. Currently IBM provides support for JSF 1.0 when you use a RAD, but it has an outdated version of commons-collectio
n.jar library that causing me some problems using Hibernate 3.0. I am wondering if any one already has any solutions for this or has an updated JSF 1.1 set for IBM JSF wrappers.
Thanks and
Regards, Gregory.
| |
|
| I have the same setup. This is how I got mine working:
When you create a webapp project and add the first Faces JSP, RAD adds the commons libraries. For some reason these are different than the ones you get when you create a Faces Portlet project. I copied the commons jars from the webapp to the portlet proje
ct and it worked fine. The only other problem I ran into was I had to delete the commons-logging.jar before the portlet would deploy on AIX. Seemed to work OK on Windows.
| |
|
| Are you using Hibernate 3 as well ?
and what is the list of the jar and versions that you use..
Here is what i have
JSF:
commons-beanutils.jar 1.6
commons-collections.jar 1.1dev
commons-digester.jar 1.5
jaxen-full.jar 1.0-FCS
jsf-portal.jar 5.1.0.1
jstl.jar 1.0.5
jstl_el.jar 1.0
saxpath.jar 1.0
standard.jar 1.0.5
Hibernate 3.0
ant-antlr.jar 1.6.3
antlr.jar 2.7.5H3
asm-attrs.jar 1.5.3
asm.jar 1.5.3
cglib.jar 2.1
commons-collections.jar 2.1.1
commons-logging.jar 1.0.4
dom4j.jar 1.6
ehcache.jar 1.1
hibernate.jar 3.0.5
hsqldb.jar 4.0.1
jta.jar 1.0
log4j.jar 1.2.9
| |
|
| Yes. I'm using Hibernate 3. Here's the list:
commons-beanutils.jar 1.6
commons-collections.jar 2.1
commons-digester.jar 1.5
jaxen-full.jar 1.0 FCS
jsf-api.jar
jsf-ibm.jar
jsf-impl.jar
jstl.jar 1.0.5
jstl_el.jar
saxpath.jar 1.0
standard.jar 1.0.5
jsf-portlet.jar
asm.jar 1.5.3
jta.jar
c3p0-0.8.5.2.jar
cglib-2.1.jar
dom4j-1.6.jar
hibernate3.jar 3.0.5
asm-attrs.jar 1.5.3
jakarta-oro.jar
ehcache-1.1.jar
jsf-wp.jar
mysql-connector-java-3.1.8-bin.jar
I couldn't find version numbers on all of them.
| |
|
| But you are using c2a IBM JSF implementation and I am using JSR 168 version.
Which has a different set on jar's. (E.g. jsf-wp.jar is a JSF wrappers for IBM API container.. ) ..
Do you know if anyone using JSR 168 version.
| |
|
| You are correct. I forgot that I added people awareness to the portlet. I can only tell you that the portlet was also working prior to me adding the jsf-wp.jar.
| |
|
| The problem that i have is that we using jsr 168 JSF portlets and it has a different runtime container and API set outside of standard JSF call. Plus JSF is only supported up to version 1.0 .. no lates support for 1.1 specification. jsf-wp.jar is an IBM c
ontainer environemt. And I have jsf-portlet.jar instead..
|
|
|
|