RE : Re: Re : RE : Re: Oracle ADF and Shale tiles/validator

2007-02-01 Thread Adrian Gonzalez
 I agree,  please add it to the wiki when you have
 time. 

Done ! I've put a link on the main wiki's page 
for Shale And Other JSF libraries ((Shale  ADF).
I really don't know if it's good or if the shale team
wants to move it elsewhere, so if it's a you think
it's crapy, just delete it !

Thank you very much for your appreciated help Gary !

 However, Tiles/JSF 1.2 and JSP might workout since
 the verbatim issue is fixed 
 but I have not heard from anyone who's tried it
 either. 

I know, but my IDE don't support facelets and one of
the main points (for me) of JSF is IDE RAD support.

Just one final point (which doesn't help anybody), I
believe one of the main problems of JSF (other than
the well known ones) is library incompatibility (i.e.
Icefaces components can't be used on the same page
with other third party components, ADF problem with
Shale or Tiles, and surely others I don't know since
I'm a newbie). It's really a pity (since some JSF
libraries are really incredible), and I don't know if
this problem will be resolved in the future.

--- Gary VanMatre [EMAIL PROTECTED] a écrit :

 From: Adrian Gonzalez [EMAIL PROTECTED] 
 
  Thank you very much Gary for this information,
 I'll try ADF validators instead 
  of Shale's. 
  
  Do you have similar info about Shale tiles and ADF
 ? Do you know if ADF (or 
  Trinidad) has a feature similar as Tiles
 composition ? 
  
 
 I've not tried Shale Tiles with ADF but I suspect
 the two won't play nicely together.
 Many will also tell you not to use JSP with JSF 1.1
 due to the verbatim issue.
 
 However, Tiles/JSF 1.2 and JSP might workout since
 the verbatim issue is fixed 
 but I have not heard from anyone who's tried it
 either. 
 
 
  Perhaps the information about incompatibility
 between shale tiles/validator and 
  ADF (and perhaps Trinidad) should be usefull for
 other newbies (in a wiki ?). 
  
 
 I agree,  please add it to the wiki when you have
 time.  
 
 
 Gary
 
  - Message d'origine  
  De : Gary VanMatre 
  À : user@shale.apache.org 
  Envoyé le : Mercredi, 31 Janvier 2007, 17h47mn 08s
 
  Objet : Re: RE : Re: Oracle ADF and Shale
 tiles/validator 
  
  From: Adrian Gonzalez 
   
   
   I've found the problem (using both Oracle ADF
 and some 
   shale extensions doesn't work). 
   
   It's in shale-validator and in shale-tiles
 (1.0.4 
   version). For info, I'm using adf-faces
 10_1_3_0_4. 
   
   To reproduce the problem with shale-validator,
 one 
   just needs to put the shale-validator.jar in 
   WEB-INF/lib. We don't need to use a validator 
   explicitly in jsf page. 
   
   To reproduce the problem with shale-tiles, one
 needs 
   to put the shale-tiles.jar in WEB-INF/lib AND to
 call 
   jsf page through a tile definition. 
   
   I've done some debugging with shale-validator. 
   The problem with this validator is that it
 changes the 
   current renderKit (see 
  
 org.apache.shale.validator.faces.setupRenderKit). 
   
   I've just commented the setupRenderKit method 
   implementation and the JSF page displays fine. 
   
   Can we change something in order to use ADF with
 those 
   Shale extensions ? 
   
  
  I don't know if the two will work together. The
 ADF component 
  library takes advantage of about every JSF
 extension point. I'm 
  making this statement based on reviewing
 Trinidad's code. 
  
  Both ADF and Shale Validator use a custom
 RenderKit. In 
  Shale Validator's case, it decorates the original
 so that it can 
  decorate renderers. This is needed because Shale
 is not a 
  widget library and we are not interested in build
 a suite of 
  components from the ground up as you will see with
 ADF. 
  This trick allows us to modify a renderers
 behavior without 
  rewritting every renderer that is a Input or
 Command component. 
  
  If the registration of shale validator's
 faces-config is prior to 
  ADF, there might be a chance to make it work
 however 
  I'm doubtful. 
  
  Assuming that ADF has the same validator support
 as Trinidad, 
  you might rather look at their's which is couple
 with their components 
  and provides client side validation. 
  
  
  tr:validateRegExp - Validate expression using java
 regular expression syntax. 
  tr:validateLongRange - Validate that the date
 entered is within a given range. 
  tr:validateLength - Validate that the date entered
 is within a given range. 
  tr:validateDoubleRange - Validate that the date
 entered is within a given range. 
  tr:validateDateTimeRange - Validate that the date
 entered is within a given 
  range. 
  tr:validateDateRestriction - Validate that the
 date entered is within a given 
  restriction. 
  tr:validateByteLength - Validate the byte length
 of strings when encoded. 
  
  
   Thanks 
   
  
  Gary 
  
   
   
   
   
  

___
 
   Découvrez une nouvelle façon d'obtenir des
 réponses à toutes vos questions ! 
   Profitez des connaissances, des opinions et des

Re: RE : Re: Re : RE : Re: Oracle ADF and Shale tiles/validator

2007-02-01 Thread Matthias Wessendorf

Hey Adrian,

can you send me offline a simple sample WAR file, that uses ADF Faces
and Shale Validator? Not the Shale-Tiles thing.

Only those two ?

I'd like to look at it.

Thanks,
Matthias

On 2/1/07, Adrian Gonzalez [EMAIL PROTECTED] wrote:

 I agree,  please add it to the wiki when you have
 time.

Done ! I've put a link on the main wiki's page
for Shale And Other JSF libraries ((Shale  ADF).
I really don't know if it's good or if the shale team
wants to move it elsewhere, so if it's a you think
it's crapy, just delete it !

Thank you very much for your appreciated help Gary !

 However, Tiles/JSF 1.2 and JSP might workout since
 the verbatim issue is fixed
 but I have not heard from anyone who's tried it
 either.

I know, but my IDE don't support facelets and one of
the main points (for me) of JSF is IDE RAD support.

Just one final point (which doesn't help anybody), I
believe one of the main problems of JSF (other than
the well known ones) is library incompatibility (i.e.
Icefaces components can't be used on the same page
with other third party components, ADF problem with
Shale or Tiles, and surely others I don't know since
I'm a newbie). It's really a pity (since some JSF
libraries are really incredible), and I don't know if
this problem will be resolved in the future.

--- Gary VanMatre [EMAIL PROTECTED] a écrit :

 From: Adrian Gonzalez [EMAIL PROTECTED]
 
  Thank you very much Gary for this information,
 I'll try ADF validators instead
  of Shale's.
 
  Do you have similar info about Shale tiles and ADF
 ? Do you know if ADF (or
  Trinidad) has a feature similar as Tiles
 composition ?
 

 I've not tried Shale Tiles with ADF but I suspect
 the two won't play nicely together.
 Many will also tell you not to use JSP with JSF 1.1
 due to the verbatim issue.

 However, Tiles/JSF 1.2 and JSP might workout since
 the verbatim issue is fixed
 but I have not heard from anyone who's tried it
 either.


  Perhaps the information about incompatibility
 between shale tiles/validator and
  ADF (and perhaps Trinidad) should be usefull for
 other newbies (in a wiki ?).
 

 I agree,  please add it to the wiki when you have
 time.


 Gary

  - Message d'origine 
  De : Gary VanMatre
  À : user@shale.apache.org
  Envoyé le : Mercredi, 31 Janvier 2007, 17h47mn 08s

  Objet : Re: RE : Re: Oracle ADF and Shale
 tiles/validator
 
  From: Adrian Gonzalez
  
  
   I've found the problem (using both Oracle ADF
 and some
   shale extensions doesn't work).
  
   It's in shale-validator and in shale-tiles
 (1.0.4
   version). For info, I'm using adf-faces
 10_1_3_0_4.
  
   To reproduce the problem with shale-validator,
 one
   just needs to put the shale-validator.jar in
   WEB-INF/lib. We don't need to use a validator
   explicitly in jsf page.
  
   To reproduce the problem with shale-tiles, one
 needs
   to put the shale-tiles.jar in WEB-INF/lib AND to
 call
   jsf page through a tile definition.
  
   I've done some debugging with shale-validator.
   The problem with this validator is that it
 changes the
   current renderKit (see
  
 org.apache.shale.validator.faces.setupRenderKit).
  
   I've just commented the setupRenderKit method
   implementation and the JSF page displays fine.
  
   Can we change something in order to use ADF with
 those
   Shale extensions ?
  
 
  I don't know if the two will work together. The
 ADF component
  library takes advantage of about every JSF
 extension point. I'm
  making this statement based on reviewing
 Trinidad's code.
 
  Both ADF and Shale Validator use a custom
 RenderKit. In
  Shale Validator's case, it decorates the original
 so that it can
  decorate renderers. This is needed because Shale
 is not a
  widget library and we are not interested in build
 a suite of
  components from the ground up as you will see with
 ADF.
  This trick allows us to modify a renderers
 behavior without
  rewritting every renderer that is a Input or
 Command component.
 
  If the registration of shale validator's
 faces-config is prior to
  ADF, there might be a chance to make it work
 however
  I'm doubtful.
 
  Assuming that ADF has the same validator support
 as Trinidad,
  you might rather look at their's which is couple
 with their components
  and provides client side validation.
 
 
  tr:validateRegExp - Validate expression using java
 regular expression syntax.
  tr:validateLongRange - Validate that the date
 entered is within a given range.
  tr:validateLength - Validate that the date entered
 is within a given range.
  tr:validateDoubleRange - Validate that the date
 entered is within a given range.
  tr:validateDateTimeRange - Validate that the date
 entered is within a given
  range.
  tr:validateDateRestriction - Validate that the
 date entered is within a given
  restriction.
  tr:validateByteLength - Validate the byte length
 of strings when encoded.
 
 
   Thanks
  
 
  Gary

RE : Re: Oracle ADF and Shale tiles/validator

2007-01-31 Thread Adrian Gonzalez
Thank you Matthias.

I removed this filter, but no way.

The problem is resolved when I remove all shale and
ajax4jsf librairies from /WEB-INF/lib.

I've put a custom Listener for logging purpose and the
difference I see is :
- it works fine if viewroot is
javax.faces.component.UIViewRoot.
- it doesn't work if viewroot is different (i.e. :
org.apache.shale.view.faces.ShaleViewRoot).

I'll continue to debug my app, but if anyone has
resolved this kind of problem I'll be most gratefull
for the tips, I'm really having a hard time with this
JSF stuff.

--- Matthias Wessendorf [EMAIL PROTECTED] a écrit :

 I saw you are using the Spring
 CharacterEncodingFilter.
 In Trinidad we saw issues when that one is in front
 of the Trinidad
 (Adf Faces) Filter
 
 I think your issue is related to the ordering of the
 filters.
 
 -Matthias
 







___ 
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! 
Profitez des connaissances, des opinions et des expériences des internautes sur 
Yahoo! Questions/Réponses 
http://fr.answers.yahoo.com


RE : Re: Oracle ADF and Shale tiles/validator

2007-01-31 Thread Adrian Gonzalez
I've just changed the JSP test page to include some
ADF components, and it changed the stackTrace to :
java.lang.IllegalStateException: No
AdfRenderingContext

---
Here's the jsp page :
!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0
Transitional//EN
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;
%@ taglib uri=http://java.sun.com/jsf/core;
prefix=f%
[EMAIL PROTECTED] uri=http://java.sun.com/jsf/html;
prefix=h%
[EMAIL PROTECTED] uri=http://xmlns.oracle.com/adf/faces/html;
prefix=afh%
[EMAIL PROTECTED] uri=http://xmlns.oracle.com/adf/faces;
prefix=af%

f:view
af:document title=Oracle ADF Faces Demo Index
html xmlns=http://www.w3.org/1999/xhtml;
body
pPlacez le contenu ici./p
h:form styleClass=form id=form1
h:inputText styleClass=inputText id=text1
value=message sample/h:inputText
/h:form
/body
/html
/af:document
/f:view

---
Here's the stackTrace :


 Begin backtrace for Nested Throwables
java.lang.IllegalStateException: No
AdfRenderingContext
at
oracle.adfinternal.view.faces.renderkit.core.CoreRenderer.encodeEnd(CoreRenderer.java:154)
at
oracle.adf.view.faces.component.UIXComponentBase.encodeEnd(UIXComponentBase.java:624)
at
javax.faces.webapp.UIComponentTag.encodeEnd(UIComponentTag.java:495)
at
javax.faces.webapp.UIComponentTag.doEndTag(UIComponentTag.java:363)
at
oracle.adf.view.faces.webapp.UIXComponentTag.doEndTag(UIXComponentTag.java:100)
at
com.ibm._jsp._simple._jspx_meth_af_document_0(_simple.java:151)
at
com.ibm._jsp._simple._jspx_meth_f_view_0(_simple.java:176)
at com.ibm._jsp._simple._jspService(_simple.java:76)
at
com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:88)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1282)
at
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1239)
at
com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:113)
at
com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:82)
at
com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:670)
at
com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:117)
at
com.ibm.ws.jsp.webcontainerext.JSPExtensionServletWrapper.handleRequest(JSPExtensionServletWrapper.java:178)
at
com.ibm.ws.jsp.webcontainerext.JSPExtensionProcessor.handleRequest(JSPExtensionProcessor.java:241)
at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:265)
at
org.apache.myfaces.context.servlet.ServletExternalContextImpl.dispatch(ServletExternalContextImpl.java:416)
at
org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHandlerImpl.java:234)
at
oracle.adfinternal.view.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:157)
at
org.ajax4jsf.framework.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:101)
at
org.apache.shale.tiles.TilesViewHandler.renderView(TilesViewHandler.java:176)
at
org.apache.shale.validator.faces.ValidatorViewHandler.renderView(ValidatorViewHandler.java:130)
at
org.apache.shale.view.faces.ViewViewHandler.renderView(ViewViewHandler.java:147)
at
org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:384)
at
javax.faces.webapp.FacesServlet.service(FacesServlet.java:138)
at
org.apache.myfaces.webapp.MyFacesServlet.service(MyFacesServlet.java:74)
at
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1282)
at
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1239)
at
com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:136)
at
org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:144)
at
com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:142)
at
com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:121)
at
oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl._invokeDoFilter(AdfFacesFilterImpl.java:367)
at
oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl._doFilterImpl(AdfFacesFilterImpl.java:336)
at
oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl.doFilter(AdfFacesFilterImpl.java:196)
at
oracle.adf.view.faces.webapp.AdfFacesFilter.doFilter(AdfFacesFilter.java:87)
at
com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:142)
at

RE : Re: Oracle ADF and Shale tiles/validator

2007-01-31 Thread Adrian Gonzalez

I've found the problem (using both Oracle ADF and some
shale extensions doesn't work).

It's in shale-validator and in shale-tiles (1.0.4
version). For info, I'm using adf-faces 10_1_3_0_4.

To reproduce the problem with shale-validator, one
just needs to put the shale-validator.jar in
WEB-INF/lib. We don't need to use a validator
explicitly in jsf page.

To reproduce the problem with shale-tiles, one needs
to put the shale-tiles.jar in WEB-INF/lib AND to call
jsf page through a tile definition.

I've done some debugging with shale-validator.
The problem with this validator is that it changes the
current renderKit (see
org.apache.shale.validator.faces.setupRenderKit).

I've just commented the setupRenderKit method
implementation and the JSF page displays fine.

Can we change something in order to use ADF with those
Shale extensions ?

Thanks





___ 
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! 
Profitez des connaissances, des opinions et des expériences des internautes sur 
Yahoo! Questions/Réponses 
http://fr.answers.yahoo.com


Re: RE : Re: Oracle ADF and Shale tiles/validator

2007-01-31 Thread Gary VanMatre
From: Adrian Gonzalez [EMAIL PROTECTED] 

 
 I've found the problem (using both Oracle ADF and some 
 shale extensions doesn't work). 
 
 It's in shale-validator and in shale-tiles (1.0.4 
 version). For info, I'm using adf-faces 10_1_3_0_4. 
 
 To reproduce the problem with shale-validator, one 
 just needs to put the shale-validator.jar in 
 WEB-INF/lib. We don't need to use a validator 
 explicitly in jsf page. 
 
 To reproduce the problem with shale-tiles, one needs 
 to put the shale-tiles.jar in WEB-INF/lib AND to call 
 jsf page through a tile definition. 
 
 I've done some debugging with shale-validator. 
 The problem with this validator is that it changes the 
 current renderKit (see 
 org.apache.shale.validator.faces.setupRenderKit). 
 
 I've just commented the setupRenderKit method 
 implementation and the JSF page displays fine. 
 
 Can we change something in order to use ADF with those 
 Shale extensions ? 
 

I don't know if the two will work together.  The ADF component 
library takes advantage of about every JSF extension point.  I'm
making this statement based on reviewing Trinidad's code.

Both ADF and Shale Validator use a custom RenderKit.  In
Shale Validator's case, it decorates the original so that it can
decorate renderers.  This is needed because Shale is not a 
widget library and we are not interested in build a suite of 
components from the ground up as you will see with ADF.
This trick allows us to modify a renderers behavior without
rewritting every renderer that is a Input or Command component.

If the registration of shale validator's faces-config is prior to
ADF, there might be a chance to make it work however
I'm doubtful.

Assuming that ADF has the same validator support as Trinidad,
you might rather look at their's which is couple with their components
and provides client side validation.


tr:validateRegExp - Validate expression using java regular expression syntax.
tr:validateLongRange - Validate that the date entered is within a given range.
tr:validateLength - Validate that the date entered is within a given range.
tr:validateDoubleRange - Validate that the date entered is within a given range.
tr:validateDateTimeRange - Validate that the date entered is within a given 
range.
tr:validateDateRestriction - Validate that the date entered is within a given 
restriction.
tr:validateByteLength - Validate the byte length of strings when encoded.


 Thanks 
 

Gary

 
 
 
 
 ___ 
 Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! 
 Profitez des connaissances, des opinions et des expériences des internautes 
 sur 
 Yahoo! Questions/Réponses 
 http://fr.answers.yahoo.com 

Re : RE : Re: Oracle ADF and Shale tiles/validator

2007-01-31 Thread Adrian Gonzalez
Thank you very much Gary for this information, I'll try ADF validators instead 
of Shale's.

Do you have similar info about Shale tiles and ADF ? Do you know if ADF (or 
Trinidad) has a feature similar as Tiles composition ?

Perhaps the information about incompatibility between shale tiles/validator and 
ADF (and perhaps Trinidad) should be usefull for other newbies (in a wiki ?).

- Message d'origine 
De : Gary VanMatre [EMAIL PROTECTED]
À : user@shale.apache.org
Envoyé le : Mercredi, 31 Janvier 2007, 17h47mn 08s
Objet : Re: RE : Re: Oracle ADF and Shale tiles/validator

From: Adrian Gonzalez [EMAIL PROTECTED] 

 
 I've found the problem (using both Oracle ADF and some 
 shale extensions doesn't work). 
 
 It's in shale-validator and in shale-tiles (1.0.4 
 version). For info, I'm using adf-faces 10_1_3_0_4. 
 
 To reproduce the problem with shale-validator, one 
 just needs to put the shale-validator.jar in 
 WEB-INF/lib. We don't need to use a validator 
 explicitly in jsf page. 
 
 To reproduce the problem with shale-tiles, one needs 
 to put the shale-tiles.jar in WEB-INF/lib AND to call 
 jsf page through a tile definition. 
 
 I've done some debugging with shale-validator. 
 The problem with this validator is that it changes the 
 current renderKit (see 
 org.apache.shale.validator.faces.setupRenderKit). 
 
 I've just commented the setupRenderKit method 
 implementation and the JSF page displays fine. 
 
 Can we change something in order to use ADF with those 
 Shale extensions ? 
 

I don't know if the two will work together.  The ADF component 
library takes advantage of about every JSF extension point.  I'm
making this statement based on reviewing Trinidad's code.

Both ADF and Shale Validator use a custom RenderKit.  In
Shale Validator's case, it decorates the original so that it can
decorate renderers.  This is needed because Shale is not a 
widget library and we are not interested in build a suite of 
components from the ground up as you will see with ADF.
This trick allows us to modify a renderers behavior without
rewritting every renderer that is a Input or Command component.

If the registration of shale validator's faces-config is prior to
ADF, there might be a chance to make it work however
I'm doubtful.

Assuming that ADF has the same validator support as Trinidad,
you might rather look at their's which is couple with their components
and provides client side validation.


tr:validateRegExp - Validate expression using java regular expression syntax.
tr:validateLongRange - Validate that the date entered is within a given range.
tr:validateLength - Validate that the date entered is within a given range.
tr:validateDoubleRange - Validate that the date entered is within a given range.
tr:validateDateTimeRange - Validate that the date entered is within a given 
range.
tr:validateDateRestriction - Validate that the date entered is within a given 
restriction.
tr:validateByteLength - Validate the byte length of strings when encoded.


 Thanks 
 

Gary

 
 
 
 
 ___ 
 Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! 
 Profitez des connaissances, des opinions et des expériences des internautes 
 sur 
 Yahoo! Questions/Réponses 
 http://fr.answers.yahoo.com 








___ 
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! 
Profitez des connaissances, des opinions et des expériences des internautes sur 
Yahoo! Questions/Réponses 
http://fr.answers.yahoo.com


Re: Re : RE : Re: Oracle ADF and Shale tiles/validator

2007-01-31 Thread Gary VanMatre
From: Adrian Gonzalez [EMAIL PROTECTED] 

 Thank you very much Gary for this information, I'll try ADF validators 
 instead 
 of Shale's. 
 
 Do you have similar info about Shale tiles and ADF ? Do you know if ADF (or 
 Trinidad) has a feature similar as Tiles composition ? 
 

I've not tried Shale Tiles with ADF but I suspect the two won't play nicely 
together.
Many will also tell you not to use JSP with JSF 1.1 due to the verbatim issue.

However, Tiles/JSF 1.2 and JSP might workout since the verbatim issue is 
fixed 
but I have not heard from anyone who's tried it either. 


 Perhaps the information about incompatibility between shale tiles/validator 
 and 
 ADF (and perhaps Trinidad) should be usefull for other newbies (in a wiki ?). 
 

I agree,  please add it to the wiki when you have time.  


Gary

 - Message d'origine  
 De : Gary VanMatre 
 À : user@shale.apache.org 
 Envoyé le : Mercredi, 31 Janvier 2007, 17h47mn 08s 
 Objet : Re: RE : Re: Oracle ADF and Shale tiles/validator 
 
 From: Adrian Gonzalez 
  
  
  I've found the problem (using both Oracle ADF and some 
  shale extensions doesn't work). 
  
  It's in shale-validator and in shale-tiles (1.0.4 
  version). For info, I'm using adf-faces 10_1_3_0_4. 
  
  To reproduce the problem with shale-validator, one 
  just needs to put the shale-validator.jar in 
  WEB-INF/lib. We don't need to use a validator 
  explicitly in jsf page. 
  
  To reproduce the problem with shale-tiles, one needs 
  to put the shale-tiles.jar in WEB-INF/lib AND to call 
  jsf page through a tile definition. 
  
  I've done some debugging with shale-validator. 
  The problem with this validator is that it changes the 
  current renderKit (see 
  org.apache.shale.validator.faces.setupRenderKit). 
  
  I've just commented the setupRenderKit method 
  implementation and the JSF page displays fine. 
  
  Can we change something in order to use ADF with those 
  Shale extensions ? 
  
 
 I don't know if the two will work together. The ADF component 
 library takes advantage of about every JSF extension point. I'm 
 making this statement based on reviewing Trinidad's code. 
 
 Both ADF and Shale Validator use a custom RenderKit. In 
 Shale Validator's case, it decorates the original so that it can 
 decorate renderers. This is needed because Shale is not a 
 widget library and we are not interested in build a suite of 
 components from the ground up as you will see with ADF. 
 This trick allows us to modify a renderers behavior without 
 rewritting every renderer that is a Input or Command component. 
 
 If the registration of shale validator's faces-config is prior to 
 ADF, there might be a chance to make it work however 
 I'm doubtful. 
 
 Assuming that ADF has the same validator support as Trinidad, 
 you might rather look at their's which is couple with their components 
 and provides client side validation. 
 
 
 tr:validateRegExp - Validate expression using java regular expression syntax. 
 tr:validateLongRange - Validate that the date entered is within a given 
 range. 
 tr:validateLength - Validate that the date entered is within a given range. 
 tr:validateDoubleRange - Validate that the date entered is within a given 
 range. 
 tr:validateDateTimeRange - Validate that the date entered is within a given 
 range. 
 tr:validateDateRestriction - Validate that the date entered is within a given 
 restriction. 
 tr:validateByteLength - Validate the byte length of strings when encoded. 
 
 
  Thanks 
  
 
 Gary 
 
  
  
  
  
  ___ 
  Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions 
  ! 
  Profitez des connaissances, des opinions et des expériences des internautes 
 sur 
  Yahoo! Questions/Réponses 
  http://fr.answers.yahoo.com 
 
 
 
 
 
 
 
 
 ___ 
 Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! 
 Profitez des connaissances, des opinions et des expériences des internautes 
 sur 
 Yahoo! Questions/Réponses 
 http://fr.answers.yahoo.com