Issue with tr:inputDate tag in Edit Mode

2013-08-14 Thread SureshBabu Sabbu
Hi Team,

I had an issue with tr:inputDate tag with trinidad-impl-2.0.1.jar and
trinidad-api-2.0.1.jar.

We have a page where we have the tr:inputDate components for to select
Date on the page. This works fine as expected.

But when we go for editing the page which already has the Date, and try to
change the date the page hungs and it didn't allow to do anything on the
page. And observed a JS error on the console.



SCRIPT5007: The value of the property '_getLocaleTimeZoneDifference' is
null or undefined, not a Function object

Common2_0_0_beta_2.js, line 139 character 1



But, the functionality works when i keep the below conext param in web.xml


context-param
   param-nameorg.apache.myfaces.trinidad.CHANGE_PERSISTENCE
/param-name
   param-valuesession/param-value

/context-param

I don't understand the relation between the tr:inputDate and the
CHANGE_PERSISTENCE context param.

The same behaviour/scenario works fine with JSF1.2 Jars without the
CHANGE_PERSISTENCE context param.

So, Please suggest any resolution for this issue.

Thanks

Suresh Babu S


[Trinidad] tr:inputDate alternative

2012-03-15 Thread Walter Mourão
Hi folks,
tr:inputDate date selection works opening a new window/frame and I would
like to use only javascript/divs. Tomahawk is an option but have some
quirks and I would like to know if some of you have used another options...
Please let me know you use some javascript (detached from big packages like
jquery) to allow date selection. If I find a good option I will create a
composite component and bring it back to the community.

Thanks in advance,

Walter Mourão
http://waltermourao.com.br
http://arcadian.com.br
http://oriens.com.br


AW: [Trinidad] tr:inputDate alternative

2012-03-15 Thread Krebs Roland / BWO Systems AG
Hi Mourao

No frame will be opened anymore after setting (in web.xml):
context-param

param-nameorg.apache.myfaces.trinidad.ENABLE_LIGHTWEIGHT_DIALOGS/param-name
param-valuetrue/param-value
/context-param

That's how I'm using it.
Roland

-Ursprüngliche Nachricht-
Von: Walter Mourão [mailto:walter.mou...@gmail.com] 
Gesendet: Donnerstag, 15. März 2012 12:56
An: MyFaces Discussion
Betreff: [Trinidad] tr:inputDate alternative

Hi folks,
tr:inputDate date selection works opening a new window/frame and I would like 
to use only javascript/divs. Tomahawk is an option but have some quirks and I 
would like to know if some of you have used another options...
Please let me know you use some javascript (detached from big packages like
jquery) to allow date selection. If I find a good option I will create a 
composite component and bring it back to the community.

Thanks in advance,

Walter Mourão
http://waltermourao.com.br
http://arcadian.com.br
http://oriens.com.br


Re: [Trinidad] tr:inputDate alternative

2012-03-15 Thread Walter Mourão
Hi Roland,
in fact ENABLE_LIGHTWEIGHT_DIALOGS will open a iframe... it does not use a
new window, but it opens a iframe and it has some delay to open caused by
communication with the server.

Cheers,

Walter Mourão
http://waltermourao.com.br
http://arcadian.com.br
http://oriens.com.br



On Thu, Mar 15, 2012 at 10:22 AM, Krebs Roland / BWO Systems AG 
roland.kr...@bwo.ch wrote:

 Hi Mourao

 No frame will be opened anymore after setting (in web.xml):
 context-param

  
 param-nameorg.apache.myfaces.trinidad.ENABLE_LIGHTWEIGHT_DIALOGS/param-name
param-valuetrue/param-value
 /context-param

 That's how I'm using it.
 Roland

 -Ursprüngliche Nachricht-
 Von: Walter Mourão [mailto:walter.mou...@gmail.com]
 Gesendet: Donnerstag, 15. März 2012 12:56
 An: MyFaces Discussion
 Betreff: [Trinidad] tr:inputDate alternative

 Hi folks,
 tr:inputDate date selection works opening a new window/frame and I would
 like to use only javascript/divs. Tomahawk is an option but have some
 quirks and I would like to know if some of you have used another options...
 Please let me know you use some javascript (detached from big packages like
 jquery) to allow date selection. If I find a good option I will create a
 composite component and bring it back to the community.

 Thanks in advance,

 Walter Mourão
 http://waltermourao.com.br
 http://arcadian.com.br
 http://oriens.com.br



Re: Cannot get tr:inputDate to work

2010-04-14 Thread Matthias Wessendorf
On Tue, Apr 13, 2010 at 11:47 AM, Eisenträger, Tobias
tobias.eisentrae...@arag.de wrote:
 -Ursprüngliche Nachricht-
 Von: mwessend...@gmail.com [mailto:mwessend...@gmail.com] Im Auftrag von
 Matthias Wessendorf
 Gesendet: Dienstag, 13. April 2010 11:31
 An: MyFaces Discussion
 Betreff: Re: Cannot get tr:inputDate to work

 does the vanilla demo work for you ?
 No, gives the error as stated in original email.

hrm, I do not see that.

checked on here
http://svn.apache.org/repos/asf/myfaces/trinidad/branches/trinidad-1.2.x/

in trinidad-examples/trinidad-demo I simply called
mvn clean jetty:run -PjettyConfig (After I build the branch)

tr:inputDate works fine

-M


 Did you register the TrindadFilter ?
 filter
    filter-nametrinidad/filter-name
    filter-class
                        org.apache.myfaces.trinidad.webapp.TrinidadFilter
                /filter-class
  /filter

  filter-mapping
    filter-nametrinidad/filter-name
    servlet-namefaces/servlet-name
  /filter-mapping

  filter-mapping
    filter-nameMyFacesExtensionsFilter/filter-name
    url-pattern*.jsf/url-pattern
  /filter-mapping

  filter-mapping
    filter-nameMyFacesExtensionsFilter/filter-name
    url-pattern/faces/*/url-pattern
  /filter-mapping

 Do I need more filter mappings - I notice that only the urls with 
 appname/index.jsf work, the ones with /faces/index.jspx do not.

 Did you add the renderKit (to faces-cfg) ?
 application
    !-- Use the Trinidad RenderKit --
    default-render-kit-id
      org.apache.myfaces.trinidad.core
    /default-render-kit-id
    !--  Set the user locale --
    locale-config
                default-localede/default-locale
                supported-localede/supported-locale
        /locale-config
    resource-bundle
                base-namemessages/base-name
                varmsgs/var
        /resource-bundle
        resource-bundle
                base-namejflowwebclient/base-name
                varproperties/var
        /resource-bundle
  /application

 -M

 On Tue, Apr 13, 2010 at 11:23 AM, Eisenträger, Tobias
 tobias.eisentrae...@arag.de wrote:
  Hello,
 
 
 
  I think I am missing a configuration, something for additional resources
 from ADF, but I cannot remember how to configure that, and where. The
 problem is that when I use the tr:inputDate from the example at:
 http://myfaces.apache.org/trinidad/trinidad-api/tagdoc/tr_inputDate.html
 http://myfaces.apache.org/trinidad/trinidad-api/tagdoc/tr_inputDate.html
  on click nothing happens - the problem ist, that the browser is looking
 for:
 http://server:port/appName/__ADFv__?_t=cdvalue=1271150122202loc=deenc=i
 so-8859-1 where a 404 is returned.
 
 
 
  Apr 13, 2010 11:22:54 AM
 org.apache.myfaces.renderkit.html.HtmlRenderKitImpl getRenderer
 
  WARNING: Unsupported component-family/renderer-type:
 org.apache.myfaces.trinidad.Input/org.apache.myfaces.trinidad.CoreInputTex
 t
 
  Apr 13, 2010 11:22:54 AM
 org.apache.myfaces.trinidadinternal.renderkit.RenderKitBase getRenderer
 
  WARNING: Renderer 'org.apache.myfaces.trinidad.CoreInputText' not found
 for component family 'org.apache.myfaces.trinidad.Input'
 
  Apr 13, 2010 11:22:54 AM
 org.apache.myfaces.trinidad.component.UIXComponentBase _getRendererImpl
 
  WARNING: Could not find renderer for UIXInput[UIXEditableFacesBeanImpl,
 id=patitoPerez] rendererType = org.apache.myfaces.trinidad.CoreInputText
 
 
 
  Any tipps?
 
 
 
  Thanks!
 
 
 
  Mit freundlichen Grüßen
 
 
 
  Tobias Eisenträger
 
 
 
  Softwareentwickler
 
  Dokumentenmanagement/Workflow/Internet, AKB 8125
 
 
 
  ARAG IT GmbH
  ARAG Platz 1, 40472 Düsseldorf
 
  Tel.: +49 (0)211 964-1937
 
  tobias.eisentrae...@arag.de
  www.ARAG.de
 
 
 
  Aufsichtsratsvorsitzender:
 
  Gerd Peskes
 
  Vorstand:
 
  Dr. Paul-Otto Faßbender (Vors.),
 
  Dr. Jan-Peter Horst,
 
  Dr. Johannes Kathan, Werner Nicoll,
 
  Hanno Petersen, Dr. Joerg Schwarze
 
  Sitz und Registergericht:
 
  Düsseldorf, HRB 1371
 
  USt-ID-Nr.: DE 119 355 995
 
 
 
 



 --
 Matthias Wessendorf

 blog: http://matthiaswessendorf.wordpress.com/
 sessions: http://www.slideshare.net/mwessendorf
 twitter: http://twitter.com/mwessendorf




-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf


Cannot get tr:inputDate to work

2010-04-13 Thread Eisenträger , Tobias
Hello,

 

I think I am missing a configuration, something for additional resources from 
ADF, but I cannot remember how to configure that, and where. The problem is 
that when I use the tr:inputDate from the example at: 
http://myfaces.apache.org/trinidad/trinidad-api/tagdoc/tr_inputDate.html 
http://myfaces.apache.org/trinidad/trinidad-api/tagdoc/tr_inputDate.html  on 
click nothing happens - the problem ist, that the browser is looking for: 
http://server:port/appName/__ADFv__?_t=cdvalue=1271150122202loc=deenc=iso-8859-1
 where a 404 is returned.

 

Apr 13, 2010 11:22:54 AM org.apache.myfaces.renderkit.html.HtmlRenderKitImpl 
getRenderer

WARNING: Unsupported component-family/renderer-type: 
org.apache.myfaces.trinidad.Input/org.apache.myfaces.trinidad.CoreInputText

Apr 13, 2010 11:22:54 AM 
org.apache.myfaces.trinidadinternal.renderkit.RenderKitBase getRenderer

WARNING: Renderer 'org.apache.myfaces.trinidad.CoreInputText' not found for 
component family 'org.apache.myfaces.trinidad.Input'

Apr 13, 2010 11:22:54 AM org.apache.myfaces.trinidad.component.UIXComponentBase 
_getRendererImpl

WARNING: Could not find renderer for UIXInput[UIXEditableFacesBeanImpl, 
id=patitoPerez] rendererType = org.apache.myfaces.trinidad.CoreInputText

 

Any tipps?

 

Thanks!

 

Mit freundlichen Grüßen 

 

Tobias Eisenträger

 

Softwareentwickler

Dokumentenmanagement/Workflow/Internet, AKB 8125 

 

ARAG IT GmbH
ARAG Platz 1, 40472 Düsseldorf

Tel.: +49 (0)211 964-1937

tobias.eisentrae...@arag.de
www.ARAG.de

 

Aufsichtsratsvorsitzender:

Gerd Peskes

Vorstand:

Dr. Paul-Otto Faßbender (Vors.),

Dr. Jan-Peter Horst,

Dr. Johannes Kathan, Werner Nicoll,

Hanno Petersen, Dr. Joerg Schwarze

Sitz und Registergericht:

Düsseldorf, HRB 1371

USt-ID-Nr.: DE 119 355 995

 



Re: Cannot get tr:inputDate to work

2010-04-13 Thread Matthias Wessendorf
does the vanilla demo work for you ?

Did you register the TrindadFilter ?
Did you add the renderKit (to faces-cfg) ?

-M

On Tue, Apr 13, 2010 at 11:23 AM, Eisenträger, Tobias
tobias.eisentrae...@arag.de wrote:
 Hello,



 I think I am missing a configuration, something for additional resources from 
 ADF, but I cannot remember how to configure that, and where. The problem is 
 that when I use the tr:inputDate from the example at: 
 http://myfaces.apache.org/trinidad/trinidad-api/tagdoc/tr_inputDate.html 
 http://myfaces.apache.org/trinidad/trinidad-api/tagdoc/tr_inputDate.html  
 on click nothing happens - the problem ist, that the browser is looking for: 
 http://server:port/appName/__ADFv__?_t=cdvalue=1271150122202loc=deenc=iso-8859-1
  where a 404 is returned.



 Apr 13, 2010 11:22:54 AM org.apache.myfaces.renderkit.html.HtmlRenderKitImpl 
 getRenderer

 WARNING: Unsupported component-family/renderer-type: 
 org.apache.myfaces.trinidad.Input/org.apache.myfaces.trinidad.CoreInputText

 Apr 13, 2010 11:22:54 AM 
 org.apache.myfaces.trinidadinternal.renderkit.RenderKitBase getRenderer

 WARNING: Renderer 'org.apache.myfaces.trinidad.CoreInputText' not found for 
 component family 'org.apache.myfaces.trinidad.Input'

 Apr 13, 2010 11:22:54 AM 
 org.apache.myfaces.trinidad.component.UIXComponentBase _getRendererImpl

 WARNING: Could not find renderer for UIXInput[UIXEditableFacesBeanImpl, 
 id=patitoPerez] rendererType = org.apache.myfaces.trinidad.CoreInputText



 Any tipps?



 Thanks!



 Mit freundlichen Grüßen



 Tobias Eisenträger



 Softwareentwickler

 Dokumentenmanagement/Workflow/Internet, AKB 8125



 ARAG IT GmbH
 ARAG Platz 1, 40472 Düsseldorf

 Tel.: +49 (0)211 964-1937

 tobias.eisentrae...@arag.de
 www.ARAG.de



 Aufsichtsratsvorsitzender:

 Gerd Peskes

 Vorstand:

 Dr. Paul-Otto Faßbender (Vors.),

 Dr. Jan-Peter Horst,

 Dr. Johannes Kathan, Werner Nicoll,

 Hanno Petersen, Dr. Joerg Schwarze

 Sitz und Registergericht:

 Düsseldorf, HRB 1371

 USt-ID-Nr.: DE 119 355 995







-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf


AW: Cannot get tr:inputDate to work

2010-04-13 Thread Eisenträger , Tobias
 -Ursprüngliche Nachricht-
 Von: mwessend...@gmail.com [mailto:mwessend...@gmail.com] Im Auftrag von
 Matthias Wessendorf
 Gesendet: Dienstag, 13. April 2010 11:31
 An: MyFaces Discussion
 Betreff: Re: Cannot get tr:inputDate to work
 
 does the vanilla demo work for you ?
No, gives the error as stated in original email.
 
 Did you register the TrindadFilter ?
filter
filter-nametrinidad/filter-name
filter-class
org.apache.myfaces.trinidad.webapp.TrinidadFilter
/filter-class
  /filter

  filter-mapping
filter-nametrinidad/filter-name
servlet-namefaces/servlet-name
  /filter-mapping

  filter-mapping
filter-nameMyFacesExtensionsFilter/filter-name
url-pattern*.jsf/url-pattern
  /filter-mapping
  
  filter-mapping
filter-nameMyFacesExtensionsFilter/filter-name
url-pattern/faces/*/url-pattern
  /filter-mapping

Do I need more filter mappings - I notice that only the urls with 
appname/index.jsf work, the ones with /faces/index.jspx do not.

 Did you add the renderKit (to faces-cfg) ?
application
!-- Use the Trinidad RenderKit --
default-render-kit-id
  org.apache.myfaces.trinidad.core
/default-render-kit-id
!--  Set the user locale --
locale-config
default-localede/default-locale
supported-localede/supported-locale
/locale-config
resource-bundle
base-namemessages/base-name
varmsgs/var
/resource-bundle
resource-bundle
base-namejflowwebclient/base-name
varproperties/var
/resource-bundle
  /application
 
 -M
 
 On Tue, Apr 13, 2010 at 11:23 AM, Eisenträger, Tobias
 tobias.eisentrae...@arag.de wrote:
  Hello,
 
 
 
  I think I am missing a configuration, something for additional resources
 from ADF, but I cannot remember how to configure that, and where. The
 problem is that when I use the tr:inputDate from the example at:
 http://myfaces.apache.org/trinidad/trinidad-api/tagdoc/tr_inputDate.html
 http://myfaces.apache.org/trinidad/trinidad-api/tagdoc/tr_inputDate.html
  on click nothing happens - the problem ist, that the browser is looking
 for:
 http://server:port/appName/__ADFv__?_t=cdvalue=1271150122202loc=deenc=i
 so-8859-1 where a 404 is returned.
 
 
 
  Apr 13, 2010 11:22:54 AM
 org.apache.myfaces.renderkit.html.HtmlRenderKitImpl getRenderer
 
  WARNING: Unsupported component-family/renderer-type:
 org.apache.myfaces.trinidad.Input/org.apache.myfaces.trinidad.CoreInputTex
 t
 
  Apr 13, 2010 11:22:54 AM
 org.apache.myfaces.trinidadinternal.renderkit.RenderKitBase getRenderer
 
  WARNING: Renderer 'org.apache.myfaces.trinidad.CoreInputText' not found
 for component family 'org.apache.myfaces.trinidad.Input'
 
  Apr 13, 2010 11:22:54 AM
 org.apache.myfaces.trinidad.component.UIXComponentBase _getRendererImpl
 
  WARNING: Could not find renderer for UIXInput[UIXEditableFacesBeanImpl,
 id=patitoPerez] rendererType = org.apache.myfaces.trinidad.CoreInputText
 
 
 
  Any tipps?
 
 
 
  Thanks!
 
 
 
  Mit freundlichen Grüßen
 
 
 
  Tobias Eisenträger
 
 
 
  Softwareentwickler
 
  Dokumentenmanagement/Workflow/Internet, AKB 8125
 
 
 
  ARAG IT GmbH
  ARAG Platz 1, 40472 Düsseldorf
 
  Tel.: +49 (0)211 964-1937
 
  tobias.eisentrae...@arag.de
  www.ARAG.de
 
 
 
  Aufsichtsratsvorsitzender:
 
  Gerd Peskes
 
  Vorstand:
 
  Dr. Paul-Otto Faßbender (Vors.),
 
  Dr. Jan-Peter Horst,
 
  Dr. Johannes Kathan, Werner Nicoll,
 
  Hanno Petersen, Dr. Joerg Schwarze
 
  Sitz und Registergericht:
 
  Düsseldorf, HRB 1371
 
  USt-ID-Nr.: DE 119 355 995
 
 
 
 
 
 
 
 --
 Matthias Wessendorf
 
 blog: http://matthiaswessendorf.wordpress.com/
 sessions: http://www.slideshare.net/mwessendorf
 twitter: http://twitter.com/mwessendorf


AW: Cannot get tr:inputDate to work

2010-04-13 Thread Eisenträger , Tobias
It's an older bug (in myfaces-core) - but maybe it's just misconfiguration - 
can anyone look into this maybe? 
Here's the issue: 
https://issues.apache.org/jira/browse/MYFACES-1794

 -Ursprüngliche Nachricht-
 Von: Eisenträger, Tobias [mailto:tobias.eisentrae...@arag.de]
 Gesendet: Dienstag, 13. April 2010 11:47
 An: MyFaces Discussion
 Betreff: AW: Cannot get tr:inputDate to work
 
  -Ursprüngliche Nachricht-
  Von: mwessend...@gmail.com [mailto:mwessend...@gmail.com] Im Auftrag von
  Matthias Wessendorf
  Gesendet: Dienstag, 13. April 2010 11:31
  An: MyFaces Discussion
  Betreff: Re: Cannot get tr:inputDate to work
 
  does the vanilla demo work for you ?
 No, gives the error as stated in original email.
 
  Did you register the TrindadFilter ?
 filter
 filter-nametrinidad/filter-name
 filter-class
   org.apache.myfaces.trinidad.webapp.TrinidadFilter
   /filter-class
   /filter
 
   filter-mapping
 filter-nametrinidad/filter-name
 servlet-namefaces/servlet-name
   /filter-mapping
 
   filter-mapping
 filter-nameMyFacesExtensionsFilter/filter-name
 url-pattern*.jsf/url-pattern
   /filter-mapping
 
   filter-mapping
 filter-nameMyFacesExtensionsFilter/filter-name
 url-pattern/faces/*/url-pattern
   /filter-mapping
 
 Do I need more filter mappings - I notice that only the urls with
 appname/index.jsf work, the ones with /faces/index.jspx do not.
 
  Did you add the renderKit (to faces-cfg) ?
 application
 !-- Use the Trinidad RenderKit --
 default-render-kit-id
   org.apache.myfaces.trinidad.core
 /default-render-kit-id
 !--  Set the user locale --
 locale-config
   default-localede/default-locale
   supported-localede/supported-locale
   /locale-config
 resource-bundle
   base-namemessages/base-name
   varmsgs/var
   /resource-bundle
   resource-bundle
   base-namejflowwebclient/base-name
   varproperties/var
   /resource-bundle
   /application
 
  -M
 
  On Tue, Apr 13, 2010 at 11:23 AM, Eisenträger, Tobias
  tobias.eisentrae...@arag.de wrote:
   Hello,
  
  
  
   I think I am missing a configuration, something for additional
 resources
  from ADF, but I cannot remember how to configure that, and where. The
  problem is that when I use the tr:inputDate from the example at:
  http://myfaces.apache.org/trinidad/trinidad-api/tagdoc/tr_inputDate.html
  http://myfaces.apache.org/trinidad/trinidad-
 api/tagdoc/tr_inputDate.html
   on click nothing happens - the problem ist, that the browser is looking
  for:
 
 http://server:port/appName/__ADFv__?_t=cdvalue=1271150122202loc=deenc=i
  so-8859-1 where a 404 is returned.
  
  
  
   Apr 13, 2010 11:22:54 AM
  org.apache.myfaces.renderkit.html.HtmlRenderKitImpl getRenderer
  
   WARNING: Unsupported component-family/renderer-type:
 
 org.apache.myfaces.trinidad.Input/org.apache.myfaces.trinidad.CoreInputTex
  t
  
   Apr 13, 2010 11:22:54 AM
  org.apache.myfaces.trinidadinternal.renderkit.RenderKitBase getRenderer
  
   WARNING: Renderer 'org.apache.myfaces.trinidad.CoreInputText' not
 found
  for component family 'org.apache.myfaces.trinidad.Input'
  
   Apr 13, 2010 11:22:54 AM
  org.apache.myfaces.trinidad.component.UIXComponentBase _getRendererImpl
  
   WARNING: Could not find renderer for
 UIXInput[UIXEditableFacesBeanImpl,
  id=patitoPerez] rendererType = org.apache.myfaces.trinidad.CoreInputText
  
  
  
   Any tipps?
  
  
  
   Thanks!
  
  
  
   Mit freundlichen Grüßen
  
  
  
   Tobias Eisenträger
  
  
  
   Softwareentwickler
  
   Dokumentenmanagement/Workflow/Internet, AKB 8125
  
  
  
   ARAG IT GmbH
   ARAG Platz 1, 40472 Düsseldorf
  
   Tel.: +49 (0)211 964-1937
  
   tobias.eisentrae...@arag.de
   www.ARAG.de
  
  
  
   Aufsichtsratsvorsitzender:
  
   Gerd Peskes
  
   Vorstand:
  
   Dr. Paul-Otto Faßbender (Vors.),
  
   Dr. Jan-Peter Horst,
  
   Dr. Johannes Kathan, Werner Nicoll,
  
   Hanno Petersen, Dr. Joerg Schwarze
  
   Sitz und Registergericht:
  
   Düsseldorf, HRB 1371
  
   USt-ID-Nr.: DE 119 355 995
  
  
  
  
 
 
 
  --
  Matthias Wessendorf
 
  blog: http://matthiaswessendorf.wordpress.com/
  sessions: http://www.slideshare.net/mwessendorf
  twitter: http://twitter.com/mwessendorf


Re: [Trinidad] resource not available (404) at popup of tr:inputDate

2010-03-02 Thread Joachim Schrod

Donn Aiken wrote:

Joachim --


On Mon, Mar 1, 2010 at 1:09 PM, Joachim Schrodjsch...@acm.org  wrote:


 Donn Aiken wrote:


 On Mon, Mar 1, 2010 at 11:11 AM, Joachim Schrodjsch...@acm.org   wrote:



 Donn, thanks, but that doesn't quite cover my situation.

   When one uses extension mapping and Facelets, the popup dialog of a basic

  tr:inputDate   does not work, it causes the error message The
 requested
  resource (/CONTEXT/__ADFv__) is not available.

  This is known since July 2007:
  https://issues.apache.org/jira/browse/TRINIDAD-119
  A patch exists since July 2008, revised in July 2009. (But I don't want
 to
  wait until July 2010 for the next activity. :-)

  I just did a servlet mapping like this:


   servlet-mapping
 servlet-nameFaces Servlet/servlet-name
 url-pattern/__ADFv__*/url-pattern
 url-pattern/faces/*/url-pattern
   /servlet-mapping

 Ugly, but it seems to work fine under Tomcat.



 As I wrote above, I use extension mapping, i.e., my URIs have an extension
 .jsf and not a prefix /faces/. And sadly

  servlet-mapping
servlet-nameFaces Servlet/servlet-name
url-pattern/__ADFv__*/url-pattern
url-pattern*.jsf/url-pattern
  /servlet-mapping

 doesn't work, the popup request still returns a 404 response.
 (It's an interesting question why not, as this request is passed to the
 MyFaces Servlet, but somehow Trinidad doesn't get a hold on it, while it
 succeeds when using the filter. Really strange.)



Is it a problem to have both *.jsf and /faces configured?  Another approach
I have used successfully is to fix it up with a servlet filter.  But I did
use a sendRedirect to  /faces/__ADFv__ url pattern rather than /__ADFv__


/faces URI requests don't ever happen in my configuration, also no 
/faces/__ADFv__. It is definitively the case that just 
/__ADFv__ (+ leading context + query string) URIs are requested 
-- I traced the network traffic to check them.


Fixing with a servlet filter is the patch in JIRA issue 
TRINIDAD-119 that I wrote of above. This works, maybe with minor 
adaptions.


It seems I wasn't clear enough: I have a workaround, it works for 
me. I don't look for a solution for my application, I want to know 
about the future of that workaround -- is it the solution, will it 
be an official workaround, or will it stay as a patch in JIRA 
that useres have to search for.


Thus, my question were/are:
 -- Is there a real fix upcoming?
Maybe all dev work is in 2.0 and nobody cares for 1.2
any more.
 -- Or shouldn't such a filter be folded in the distribution
meanwhile?
 -- Or at least be mentioned in the Wiki, to save others the time
to search for that problem's workaround?

Maybe that makes it clearer.

Joachim

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Joachim Schrod  Email: jsch...@acm.org
Roedermark, Germany



[Trinidad] resource not available (404) at popup of tr:inputDate

2010-03-01 Thread Joachim Schrod

Hi,

When one uses extension mapping and Facelets, the popup dialog of a 
basic tr:inputDate does not work, it causes the error message 
The requested resource (/CONTEXT/__ADFv__) is not available.


This is known since July 2007:
https://issues.apache.org/jira/browse/TRINIDAD-119
A patch exists since July 2008, revised in July 2009. (But I don't 
want to wait until July 2010 for the next activity. :-)


The problem still exists for MyFaces 1.2.8, Trinidad 1.2.12, and 
Facelets 1.1.14. (I don't know if it's relevant that I use 
Facelets, other bug commenters seem to have used JSP, too.)


Is somebody in the know here who can tell me about the state of 
this bug? Is the patch OK?
If the patch is not the Right Way To Do It, maybe one can add the 
filter as a workaround to the distribution?
Or add some hint to the Wiki? It needed some time to analyze and 
find the issue, I'd be willing to do it and save others the same 
work if I get a go-ahead from project members.


Any input or reaction to this issue would be welcome.

Joachim

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Joachim Schrod  Email: jsch...@acm.org
Roedermark, Germany



Re: [Trinidad] resource not available (404) at popup of tr:inputDate

2010-03-01 Thread Donn Aiken
Joachim --

On Mon, Mar 1, 2010 at 11:11 AM, Joachim Schrod jsch...@acm.org wrote:

 Hi,

 When one uses extension mapping and Facelets, the popup dialog of a basic
 tr:inputDate does not work, it causes the error message The requested
 resource (/CONTEXT/__ADFv__) is not available.

 This is known since July 2007:
 https://issues.apache.org/jira/browse/TRINIDAD-119
 A patch exists since July 2008, revised in July 2009. (But I don't want to
 wait until July 2010 for the next activity. :-)

 The problem still exists for MyFaces 1.2.8, Trinidad 1.2.12, and Facelets
 1.1.14. (I don't know if it's relevant that I use Facelets, other bug
 commenters seem to have used JSP, too.)

 Is somebody in the know here who can tell me about the state of this bug?
 Is the patch OK?
 If the patch is not the Right Way To Do It, maybe one can add the filter as
 a workaround to the distribution?
 Or add some hint to the Wiki? It needed some time to analyze and find the
 issue, I'd be willing to do it and save others the same work if I get a
 go-ahead from project members.

 Any input or reaction to this issue would be welcome.

Joachim

 --
 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 Joachim Schrod  Email: jsch...@acm.org
 Roedermark, Germany


I just did a servlet mapping like this:

  servlet-mapping
servlet-nameFaces Servlet/servlet-name
url-pattern/__ADFv__*/url-pattern
url-pattern/faces/*/url-pattern
  /servlet-mapping

Ugly, but it seems to work fine under Tomcat.

Good luck!

DJ


Re: [Trinidad] resource not available (404) at popup of tr:inputDate

2010-03-01 Thread Joachim Schrod

Donn Aiken wrote:

On Mon, Mar 1, 2010 at 11:11 AM, Joachim Schrodjsch...@acm.org  wrote:


Donn, thanks, but that doesn't quite cover my situation.


 When one uses extension mapping and Facelets, the popup dialog of a basic
 tr:inputDate  does not work, it causes the error message The requested
 resource (/CONTEXT/__ADFv__) is not available.

 This is known since July 2007:
 https://issues.apache.org/jira/browse/TRINIDAD-119
 A patch exists since July 2008, revised in July 2009. (But I don't want to
 wait until July 2010 for the next activity. :-)


I just did a servlet mapping like this:

   servlet-mapping
 servlet-nameFaces Servlet/servlet-name
 url-pattern/__ADFv__*/url-pattern
 url-pattern/faces/*/url-pattern
   /servlet-mapping

Ugly, but it seems to work fine under Tomcat.


As I wrote above, I use extension mapping, i.e., my URIs have an 
extension .jsf and not a prefix /faces/. And sadly


  servlet-mapping
servlet-nameFaces Servlet/servlet-name
url-pattern/__ADFv__*/url-pattern
url-pattern*.jsf/url-pattern
  /servlet-mapping

doesn't work, the popup request still returns a 404 response.
(It's an interesting question why not, as this request is passed to 
the MyFaces Servlet, but somehow Trinidad doesn't get a hold on it, 
while it succeeds when using the filter. Really strange.)


So, my questions remain: What's on here? Is info in the Wiki wanted?

I can also supply a minimal demo project if somebody needs this for 
analysis.


Joachim

PS: In the meantime, I upgraded to Trinidad 1.2.13. No change.

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Joachim Schrod  Email: jsch...@acm.org
Roedermark, Germany



Re: [Trinidad] resource not available (404) at popup of tr:inputDate

2010-03-01 Thread Donn Aiken
Joachim --


On Mon, Mar 1, 2010 at 1:09 PM, Joachim Schrod jsch...@acm.org wrote:

 Donn Aiken wrote:

 On Mon, Mar 1, 2010 at 11:11 AM, Joachim Schrodjsch...@acm.org  wrote:


 Donn, thanks, but that doesn't quite cover my situation.

   When one uses extension mapping and Facelets, the popup dialog of a basic
  tr:inputDate  does not work, it causes the error message The
 requested
  resource (/CONTEXT/__ADFv__) is not available.

  This is known since July 2007:
  https://issues.apache.org/jira/browse/TRINIDAD-119
  A patch exists since July 2008, revised in July 2009. (But I don't want
 to
  wait until July 2010 for the next activity. :-)

  I just did a servlet mapping like this:

   servlet-mapping
 servlet-nameFaces Servlet/servlet-name
 url-pattern/__ADFv__*/url-pattern
 url-pattern/faces/*/url-pattern
   /servlet-mapping

 Ugly, but it seems to work fine under Tomcat.


 As I wrote above, I use extension mapping, i.e., my URIs have an extension
 .jsf and not a prefix /faces/. And sadly

  servlet-mapping
servlet-nameFaces Servlet/servlet-name
url-pattern/__ADFv__*/url-pattern
url-pattern*.jsf/url-pattern
  /servlet-mapping

 doesn't work, the popup request still returns a 404 response.
 (It's an interesting question why not, as this request is passed to the
 MyFaces Servlet, but somehow Trinidad doesn't get a hold on it, while it
 succeeds when using the filter. Really strange.)

 So, my questions remain: What's on here? Is info in the Wiki wanted?

 I can also supply a minimal demo project if somebody needs this for
 analysis.

Joachim

 PS: In the meantime, I upgraded to Trinidad 1.2.13. No change.

 --
 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 Joachim Schrod  Email: jsch...@acm.org
 Roedermark, Germany


Is it a problem to have both *.jsf and /faces configured?  Another approach
I have used successfully is to fix it up with a servlet filter.  But I did
use a sendRedirect to  /faces/__ADFv__ url pattern rather than /__ADFv__

DJ


Re: Allowing more than two date formats for tr:inputDate component

2008-07-18 Thread aashoku

Hi Bandaru,

Thanks for your reply.

I want to allow the user in following formats,
1) MM-dd-
2)MMM-dd-
3)MM dd 
4)MMM dd 
5) MMM,dd,

please help me out.
Ashok.
-- 
View this message in context: 
http://www.nabble.com/Allowing-more-than-two-date-formats-for-tr%3AinputDate-component-tp18484364p18525550.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.



Re: Allowing more than two date formats for tr:inputDate component

2008-07-17 Thread Vasista

Hi,
  For tr:convertDateTime ,i think its better to have 2 formats such that
the user doesn't confuse on various formats 
Ex: 10/10/2008 is not recognizable from M/d/ and d/MM/ formats.
Such types of conflicts may rise if we provide multiple date formats.
 This is just my opinion,let me know if it wrong.

-Bandaru



aashoku wrote:
 
 When tr:inputDate component is used to set a date, one can give convert it
 to a maximum of two formats using tr:convertDateAndTime converter and
 using attributes  pattern and secondPattern. 
 
 In case one requires to accept a date in any format(more than 2 formats)
 and not just get restricted to two (stated above) ,how can one achieve?
 
 Is there any other component other than  tr:inputDate to achieve such
 scenario or what methodology?
 
 Your suggestions are our beginning steps for completion of this great
 task:working:
 
 
 
 
 
  
 

-- 
View this message in context: 
http://www.nabble.com/Allowing-more-than-two-date-formats-for-tr%3AinputDate-component-tp18484364p18522807.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.



Allowing more than two date formats for tr:inputDate component

2008-07-16 Thread aashoku

When tr:inputDate component is used to set a date, one can give convert it to
a maximum of two formats using tr:convertDateAndTime converter and using
attributes  pattern and secondPattern. 

In case one requires to accept a date in any format(more than 2 formats) and
not just get restricted to two (stated above) ,how can one achieve?

Is there any other component other than  tr:inputDate to achieve such
scenario or what methodology?

Your suggestions are our beginning steps for completion of this great
task:working:





 
-- 
View this message in context: 
http://www.nabble.com/Allowing-more-than-two-date-formats-for-tr%3AinputDate-component-tp18484364p18484364.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.



RE: [Trinidad] Facelets, tr:treeTable and tr:inputDate

2008-07-10 Thread Gerard Donnelly
Hi Andrew,

I can see the el being evaluated correctly when using outputText.


tr:inputDate id=dateChoice value=#{nodeData}
rendered=#{nodeType['date'] and !nodeReadOnly}
maximumLength=#{nodePrecision} shortDesc=#{nodeFormat}
tr:convertDateTime pattern=#{entity['format']}
secondaryPattern=#{entity['format']} /
/tr:inputDate

tr:outputText value=pattern: #{nodeFormat}
inlineStyle=display:block; /

tr:outputText value=pattern: #{entity['format']}
inlineStyle=display:block; /

Adding a few logs it would appear that the pattern and secondaryPattern
attributes are not being set in the
org.apache.myfaces.trinidad.convert.DateTimeConverter objects.

If I use the converter on a standalone inputDate it appears to be fine.
Just the use in the treetable that seems to be affected. 

I see that the ConvertDateTimeTag is auto generated. How can I get in
there and see if this is sending blanks or receiving them. 

BTW, I have moved back to Trinidad 1.2.7

G



-Original Message-
From: Andrew Robinson [mailto:[EMAIL PROTECTED] 
Sent: 09 July 2008 18:37
To: MyFaces Discussion
Subject: Re: [Trinidad] Facelets, tr:treeTable and tr:inputDate

Try adding this to the page and email the result:

tr:outputText value=pattern: #{entity['format']}
inlineStyle=display:block; /

Add one of these for every EL expression that you may question if it
is working or not.

-Andrew

On Wed, Jul 9, 2008 at 10:47 AM, Gerard Donnelly
[EMAIL PROTECTED] wrote:
 Hi Andrew,

 I've sorted the issue with the Illegal Argument. My mistake.

 However, the convertDateTime tag is still not working.

 The tag is kicking in but the evaluation of the pattern is not.

 If I hard code a value of 'MMdd' everything is sweet - in those
 cases where that is the actual pattern I require.
 If I rely on el (either nodeFormat or entity['format']) the pattern
 seems to be set to .

 I'm guessing this is the case as the attached image shows a valid
 example being blank.

 Setting of shortDesc with nodeFormat is fine and the required value is
 displayed as a tool tip.


tr:inputDate id=dateChoice value=#{nodeData}
rendered=#{nodeType['date'] and !nodeReadOnly}
maximumLength=#{nodePrecision}
 shortDesc=#{nodeFormat}
tr:convertDateTime pattern=#{entity['format']}
secondaryPattern=#{entity['format']} /
/tr:inputDate


 Thanks,
 Gerry


 -Original Message-
 From: Andrew Robinson [mailto:[EMAIL PROTECTED]
 Sent: 08 July 2008 16:56
 To: MyFaces Discussion
 Subject: Re: [Trinidad] Facelets, tr:treeTable and tr:inputDate

 ** This Message Originated From The Internet Please Be Aware Of
 Suspicious Attachments And Content **

 Didn't realise that that was the case. Seems to be working though.

 I think there may be a discrepancy between the c:set in JSTL and the
 behavior of the c:set TagHandler in facelets. Another user was saying
 that it worked as well. Facelets must implement it differently by not
 evaluating the EL immediately, but instead doing a substitution of EL.


 With the exception of tr:convertDateTime. Is this also related to
 evaluation order?

 I just looked at the source code after reading your stack trace, and
 the UIXComponentBase.findComponent is dying on this line:

if (.equals(id))
  throw new IllegalArgumentException();

 Interpreting the stack trace:
 Caused by: java.lang.IllegalArgumentException
 at

org.apache.myfaces.trinidad.component.UIXComponentBase.findComponent(UIX
 ComponentBase.java:491)
 at

org.apache.myfaces.trinidad.util.ComponentUtils.findRelativeComponent(Co
 mponentUtils.java:385)
 at

org.apache.myfaces.trinidadinternal.context.RequestContextImpl.addPartia
 lTriggerListeners(RequestContextImpl.java:550)
 at

org.apache.myfaces.trinidad.component.UIXComponentBase.decode(UIXCompone
 ntBase.java:710)

 It seems that the partialTtriggers of a component is  during decode,
 which is an invalid value (although if true, this should probably be
 handled).

 From the stack, it appears that the problem is a child of a column
 component. Try to see if you can determine the component and
 partialTriggers that may be blank on decode, then get back to us.



 P Please consider the environment before printing this email


 P Please consider the environment before printing this email
 _

 1. The information contained in this E-mail, including any files
transmitted with it, is confidential and may be legally privileged. This
E-mail is intended only for the personal attention of the stated
addressee(s). Any access to this E-mail, including any files transmitted
with it, by any other person is unauthorised. If you are not an
addressee, you must not disclose, copy, circulate or in any other way
use or rely on the information contained in this E-mail or any files
transmitted with it. Such unauthorised use may be unlawful

Re: [Trinidad] Facelets, tr:treeTable and tr:inputDate

2008-07-10 Thread Andrew Robinson
It is working on 1.2.7?

Either way, it sounds like a bug could be created to look more into
this, especially if this is a regression.

It wouldn't hurt to add a page that could work in the trinidad demo or
some kind project and attach it to the issue to reproduce the problem.

-Andrew

On Thu, Jul 10, 2008 at 5:58 AM, Gerard Donnelly
[EMAIL PROTECTED] wrote:
 Hi Andrew,

 I can see the el being evaluated correctly when using outputText.


 tr:inputDate id=dateChoice value=#{nodeData}
rendered=#{nodeType['date'] and !nodeReadOnly}
maximumLength=#{nodePrecision} shortDesc=#{nodeFormat}
tr:convertDateTime pattern=#{entity['format']}
secondaryPattern=#{entity['format']} /
 /tr:inputDate

 tr:outputText value=pattern: #{nodeFormat}
inlineStyle=display:block; /

 tr:outputText value=pattern: #{entity['format']}
inlineStyle=display:block; /

 Adding a few logs it would appear that the pattern and secondaryPattern
 attributes are not being set in the
 org.apache.myfaces.trinidad.convert.DateTimeConverter objects.

 If I use the converter on a standalone inputDate it appears to be fine.
 Just the use in the treetable that seems to be affected.

 I see that the ConvertDateTimeTag is auto generated. How can I get in
 there and see if this is sending blanks or receiving them.

 BTW, I have moved back to Trinidad 1.2.7

 G



 -Original Message-
 From: Andrew Robinson [mailto:[EMAIL PROTECTED]
 Sent: 09 July 2008 18:37
 To: MyFaces Discussion
 Subject: Re: [Trinidad] Facelets, tr:treeTable and tr:inputDate

 Try adding this to the page and email the result:

 tr:outputText value=pattern: #{entity['format']}
 inlineStyle=display:block; /

 Add one of these for every EL expression that you may question if it
 is working or not.

 -Andrew

 On Wed, Jul 9, 2008 at 10:47 AM, Gerard Donnelly
 [EMAIL PROTECTED] wrote:
 Hi Andrew,

 I've sorted the issue with the Illegal Argument. My mistake.

 However, the convertDateTime tag is still not working.

 The tag is kicking in but the evaluation of the pattern is not.

 If I hard code a value of 'MMdd' everything is sweet - in those
 cases where that is the actual pattern I require.
 If I rely on el (either nodeFormat or entity['format']) the pattern
 seems to be set to .

 I'm guessing this is the case as the attached image shows a valid
 example being blank.

 Setting of shortDesc with nodeFormat is fine and the required value is
 displayed as a tool tip.


tr:inputDate id=dateChoice value=#{nodeData}
rendered=#{nodeType['date'] and !nodeReadOnly}
maximumLength=#{nodePrecision}
 shortDesc=#{nodeFormat}
tr:convertDateTime pattern=#{entity['format']}
secondaryPattern=#{entity['format']} /
/tr:inputDate


 Thanks,
 Gerry


 -Original Message-
 From: Andrew Robinson [mailto:[EMAIL PROTECTED]
 Sent: 08 July 2008 16:56
 To: MyFaces Discussion
 Subject: Re: [Trinidad] Facelets, tr:treeTable and tr:inputDate

 ** This Message Originated From The Internet Please Be Aware Of
 Suspicious Attachments And Content **

 Didn't realise that that was the case. Seems to be working though.

 I think there may be a discrepancy between the c:set in JSTL and the
 behavior of the c:set TagHandler in facelets. Another user was saying
 that it worked as well. Facelets must implement it differently by not
 evaluating the EL immediately, but instead doing a substitution of EL.


 With the exception of tr:convertDateTime. Is this also related to
 evaluation order?

 I just looked at the source code after reading your stack trace, and
 the UIXComponentBase.findComponent is dying on this line:

if (.equals(id))
  throw new IllegalArgumentException();

 Interpreting the stack trace:
 Caused by: java.lang.IllegalArgumentException
 at

 org.apache.myfaces.trinidad.component.UIXComponentBase.findComponent(UIX
 ComponentBase.java:491)
 at

 org.apache.myfaces.trinidad.util.ComponentUtils.findRelativeComponent(Co
 mponentUtils.java:385)
 at

 org.apache.myfaces.trinidadinternal.context.RequestContextImpl.addPartia
 lTriggerListeners(RequestContextImpl.java:550)
 at

 org.apache.myfaces.trinidad.component.UIXComponentBase.decode(UIXCompone
 ntBase.java:710)

 It seems that the partialTtriggers of a component is  during decode,
 which is an invalid value (although if true, this should probably be
 handled).

 From the stack, it appears that the problem is a child of a column
 component. Try to see if you can determine the component and
 partialTriggers that may be blank on decode, then get back to us.



 P Please consider the environment before printing this email


 P Please consider the environment before printing this email
 _

 1. The information contained in this E-mail, including any files
 transmitted with it, is confidential and may be legally privileged. This
 E-mail

RE: [Trinidad] Facelets, tr:treeTable and tr:inputDate

2008-07-09 Thread Gerard Donnelly
Hi Andrew,

I've sorted the issue with the Illegal Argument. My mistake.

However, the convertDateTime tag is still not working. 

The tag is kicking in but the evaluation of the pattern is not.

If I hard code a value of 'MMdd' everything is sweet - in those
cases where that is the actual pattern I require.
If I rely on el (either nodeFormat or entity['format']) the pattern
seems to be set to . 

I'm guessing this is the case as the attached image shows a valid
example being blank.

Setting of shortDesc with nodeFormat is fine and the required value is
displayed as a tool tip.


tr:inputDate id=dateChoice value=#{nodeData}
rendered=#{nodeType['date'] and !nodeReadOnly}
maximumLength=#{nodePrecision}
shortDesc=#{nodeFormat}
tr:convertDateTime pattern=#{entity['format']}
secondaryPattern=#{entity['format']} /
/tr:inputDate


Thanks,
Gerry


-Original Message-
From: Andrew Robinson [mailto:[EMAIL PROTECTED] 
Sent: 08 July 2008 16:56
To: MyFaces Discussion
Subject: Re: [Trinidad] Facelets, tr:treeTable and tr:inputDate

** This Message Originated From The Internet Please Be Aware Of
Suspicious Attachments And Content **
 
 Didn't realise that that was the case. Seems to be working though.

I think there may be a discrepancy between the c:set in JSTL and the
behavior of the c:set TagHandler in facelets. Another user was saying
that it worked as well. Facelets must implement it differently by not
evaluating the EL immediately, but instead doing a substitution of EL.


 With the exception of tr:convertDateTime. Is this also related to
 evaluation order?

I just looked at the source code after reading your stack trace, and
the UIXComponentBase.findComponent is dying on this line:

if (.equals(id))
  throw new IllegalArgumentException();

Interpreting the stack trace:
Caused by: java.lang.IllegalArgumentException
at
org.apache.myfaces.trinidad.component.UIXComponentBase.findComponent(UIX
ComponentBase.java:491)
at
org.apache.myfaces.trinidad.util.ComponentUtils.findRelativeComponent(Co
mponentUtils.java:385)
at
org.apache.myfaces.trinidadinternal.context.RequestContextImpl.addPartia
lTriggerListeners(RequestContextImpl.java:550)
at
org.apache.myfaces.trinidad.component.UIXComponentBase.decode(UIXCompone
ntBase.java:710)

It seems that the partialTtriggers of a component is  during decode,
which is an invalid value (although if true, this should probably be
handled).

From the stack, it appears that the problem is a child of a column
component. Try to see if you can determine the component and
partialTriggers that may be blank on decode, then get back to us.

 
 
P Please consider the environment before printing this email


P Please consider the environment before printing this email
_ 
 
1. The information contained in this E-mail, including any files transmitted 
with it, is confidential and may be legally privileged. This E-mail is intended 
only for the personal attention of the stated addressee(s). Any access to this 
E-mail, including any files transmitted with it, by any other person is 
unauthorised. If you are not an addressee, you must not disclose, copy, 
circulate or in any other way use or rely on the information contained in this 
E-mail or any files transmitted with it. Such unauthorised use may be unlawful. 
If you have received this E-mail in error, please inform the sender immediately 
and delete it and all copies from your system. You may not forward this E-mail 
without the permission of the sender.
 
2. The views expressed in this E-mail are those of the author, and do not 
necessarily represent the views of AMT-SYBEX. Internet communications are not 
secure and AMT-SYBEX cannot, therefore, accept legal responsibility for the 
contents of this message nor for any damage caused by viruses.
 
AMT-SYBEX Limited is a UK company, registration number GB03036807 at address 
The Spirella Building, Bridge Road, Letchworth, SG6 4ET. 
AMT-SYBEX (NI) Limited is a UK company, registration number NI024104 at address 
Edgewater Office Park, Edgewater Rd, Belfast, BT3 9JQ.
For more information on the AMT-SYBEX Group visit http://www.amt-sybex.com
_
attachment: inputDate.JPG

Re: [Trinidad] Facelets, tr:treeTable and tr:inputDate

2008-07-09 Thread Andrew Robinson
Try adding this to the page and email the result:

tr:outputText value=pattern: #{entity['format']}
inlineStyle=display:block; /

Add one of these for every EL expression that you may question if it
is working or not.

-Andrew

On Wed, Jul 9, 2008 at 10:47 AM, Gerard Donnelly
[EMAIL PROTECTED] wrote:
 Hi Andrew,

 I've sorted the issue with the Illegal Argument. My mistake.

 However, the convertDateTime tag is still not working.

 The tag is kicking in but the evaluation of the pattern is not.

 If I hard code a value of 'MMdd' everything is sweet - in those
 cases where that is the actual pattern I require.
 If I rely on el (either nodeFormat or entity['format']) the pattern
 seems to be set to .

 I'm guessing this is the case as the attached image shows a valid
 example being blank.

 Setting of shortDesc with nodeFormat is fine and the required value is
 displayed as a tool tip.


tr:inputDate id=dateChoice value=#{nodeData}
rendered=#{nodeType['date'] and !nodeReadOnly}
maximumLength=#{nodePrecision}
 shortDesc=#{nodeFormat}
tr:convertDateTime pattern=#{entity['format']}
secondaryPattern=#{entity['format']} /
/tr:inputDate


 Thanks,
 Gerry


 -Original Message-
 From: Andrew Robinson [mailto:[EMAIL PROTECTED]
 Sent: 08 July 2008 16:56
 To: MyFaces Discussion
 Subject: Re: [Trinidad] Facelets, tr:treeTable and tr:inputDate

 ** This Message Originated From The Internet Please Be Aware Of
 Suspicious Attachments And Content **

 Didn't realise that that was the case. Seems to be working though.

 I think there may be a discrepancy between the c:set in JSTL and the
 behavior of the c:set TagHandler in facelets. Another user was saying
 that it worked as well. Facelets must implement it differently by not
 evaluating the EL immediately, but instead doing a substitution of EL.


 With the exception of tr:convertDateTime. Is this also related to
 evaluation order?

 I just looked at the source code after reading your stack trace, and
 the UIXComponentBase.findComponent is dying on this line:

if (.equals(id))
  throw new IllegalArgumentException();

 Interpreting the stack trace:
 Caused by: java.lang.IllegalArgumentException
 at
 org.apache.myfaces.trinidad.component.UIXComponentBase.findComponent(UIX
 ComponentBase.java:491)
 at
 org.apache.myfaces.trinidad.util.ComponentUtils.findRelativeComponent(Co
 mponentUtils.java:385)
 at
 org.apache.myfaces.trinidadinternal.context.RequestContextImpl.addPartia
 lTriggerListeners(RequestContextImpl.java:550)
 at
 org.apache.myfaces.trinidad.component.UIXComponentBase.decode(UIXCompone
 ntBase.java:710)

 It seems that the partialTtriggers of a component is  during decode,
 which is an invalid value (although if true, this should probably be
 handled).

 From the stack, it appears that the problem is a child of a column
 component. Try to see if you can determine the component and
 partialTriggers that may be blank on decode, then get back to us.



 P Please consider the environment before printing this email


 P Please consider the environment before printing this email
 _

 1. The information contained in this E-mail, including any files transmitted 
 with it, is confidential and may be legally privileged. This E-mail is 
 intended only for the personal attention of the stated addressee(s). Any 
 access to this E-mail, including any files transmitted with it, by any other 
 person is unauthorised. If you are not an addressee, you must not disclose, 
 copy, circulate or in any other way use or rely on the information contained 
 in this E-mail or any files transmitted with it. Such unauthorised use may be 
 unlawful. If you have received this E-mail in error, please inform the sender 
 immediately and delete it and all copies from your system. You may not 
 forward this E-mail without the permission of the sender.

 2. The views expressed in this E-mail are those of the author, and do not 
 necessarily represent the views of AMT-SYBEX. Internet communications are not 
 secure and AMT-SYBEX cannot, therefore, accept legal responsibility for the 
 contents of this message nor for any damage caused by viruses.

 AMT-SYBEX Limited is a UK company, registration number GB03036807 at address 
 The Spirella Building, Bridge Road, Letchworth, SG6 4ET.
 AMT-SYBEX (NI) Limited is a UK company, registration number NI024104 at 
 address Edgewater Office Park, Edgewater Rd, Belfast, BT3 9JQ.
 For more information on the AMT-SYBEX Group visit http://www.amt-sybex.com
 _



RE: [Trinidad] Facelets, tr:treeTable and tr:inputDate

2008-07-08 Thread Gerard Donnelly
Hi Andrew,

Didn't realise that that was the case. Seems to be working though.

With the exception of tr:convertDateTime. Is this also related to
evaluation order?

Thanks,
Gerry

-Original Message-
From: Andrew Robinson [mailto:[EMAIL PROTECTED] 
Sent: 07 July 2008 17:45
To: MyFaces Discussion
Subject: Re: [Trinidad] Facelets, tr:treeTable and tr:inputDate

** This Message Originated From The Internet Please Be Aware Of
Suspicious Attachments And Content **
 
You cannot use c:set with a dataTable var. JSTL is evaluated at JSP
tag execution, treeTable var is only available during JSF lifecycle
processing

On Mon, Jul 7, 2008 at 10:40 AM, Gerard Donnelly
[EMAIL PROTECTED] wrote:
 Hi all,



 I have created a treeStructure component and used it as below. Ideally
I'd
 like to reuse the structure for tree models and bindings coming from
 different backing beans.



 tr:treeTable id=dtsTable value=#{searchBean.dtsTreeModel}

   var=treeRow binding=#{searchBean.bindings.flowTreeTable}

   summary=#{bundle.tb_sum_createFlow} rowBandingInterval=1

   rendered=#{searchBean.fileData.cdffAvailable}

   initiallyExpanded=true



   dts:treeStructure entity=#{treeRow} /



 /tr:treeTable





 The tree structure itself is defined as :



 ui:composition xmlns=http://www.w3.org/1999/xhtml;

   xmlns:c=http://java.sun.com/jstl/core;

   xmlns:ui=http://java.sun.com/jsf/facelets;

   xmlns:f=http://java.sun.com/jsf/core;

   xmlns:tr=http://myfaces.apache.org/trinidad;



   c:set var=nodeType value=#{entity['logicalType']} /

   c:set var=nodeData value=#{entity['data']} /

   c:set var=nodeReadOnly value=#{entity['readOnly']} /

   c:set var=nodePrecision value=#{entity['precision']} /

   c:set var=nodeFormat value=#{entity['format']} /



   f:facet name=nodeStamp

 tr:column headerText=#{bundle.th_TT_description}

   tr:outputText value=#{entity['description']}


styleClass=MandatoryField-#{entity['mandatory']}
 /

 /tr:column

   /f:facet



   tr:column

 f:facet name=header

   tr:outputText value=#{bundle.th_TT_data} /

 /f:facet



 tr:outputText value=#{nodeData}

   rendered=#{nodeReadOnly} /



 tr:inputText value=#{nodeData}

   rendered=#{(nodeType['time'] || nodeType['string']
||
 nodeType['number']) and !nodeReadOnly}

   maximumLength=#{nodePrecision}
shortDesc=#{nodeFormat}

   readOnly=#{nodeReadOnly} /



 tr:selectOneChoice id=valSetChoice value=#{nodeData}

   autoSubmit=true rendered=#{nodeType['validSet']
and
 !nodeReadOnly}

   tr:selectItem value= label=#{bundle.dd_select}
/

   f:selectItems value=#{entity['validSet']} /

 /tr:selectOneChoice



 tr:inputDate id=dateChoice value=#{nodeData}
 autoSubmit=true

   rendered=#{nodeType['date'] and !nodeReadOnly}

   maximumLength=#{nodePrecision}
 shortDesc=#{nodeFormat}

   tr:convertDateTime pattern=#{nodeFormat} /

 /tr:inputDate



   /tr:column



   tr:column styleClass=DecodeColumn

 f:facet name=header

   tr:outputText value=#{bundle.th_TT_decoded} /

 /f:facet

 tr:outputText value=#{entity['decoded']}

   partialTriggers=valSetChoice dateChoice /

   /tr:column



 /ui:composition





 Everything appears to work fine except the tr:convertDateTime. It
seems to
 just ignore it and I end up with invalid date warnings.



 I've also tried passing the converter into the tag and putting in a
 ui:insert placeholder in the custom component but this doesn't have
any
 effect.



 Is there anything else I can try?



 Regards,

 Gerry

 P Please consider the environment before printing this email
 _

 1. The information contained in this E-mail, including any files
transmitted
 with it, is confidential and may be legally privileged. This E-mail is
 intended only for the personal attention of the stated addressee(s).
Any
 access to this E-mail, including any files transmitted with it, by any
other
 person is unauthorised. If you are not an addressee, you must not
disclose,
 copy, circulate or in any other way use or rely on the information
contained
 in this E-mail or any files transmitted with it. Such unauthorised use
may
 be unlawful. If you have received this E-mail in error, please inform
the
 sender immediately and delete it and all copies from your system. You
may
 not forward this E-mail without the permission of the sender.

 2. The views expressed in this E-mail are those of the author, and do
not
 necessarily represent the views of AMT-SYBEX. Internet communications
are
 not secure and AMT-SYBEX cannot, therefore

Re: [Trinidad] Facelets, tr:treeTable and tr:inputDate

2008-07-08 Thread Andrew Robinson
 Didn't realise that that was the case. Seems to be working though.

I think there may be a discrepancy between the c:set in JSTL and the
behavior of the c:set TagHandler in facelets. Another user was saying
that it worked as well. Facelets must implement it differently by not
evaluating the EL immediately, but instead doing a substitution of EL.


 With the exception of tr:convertDateTime. Is this also related to
 evaluation order?

I just looked at the source code after reading your stack trace, and
the UIXComponentBase.findComponent is dying on this line:

if (.equals(id))
  throw new IllegalArgumentException();

Interpreting the stack trace:
Caused by: java.lang.IllegalArgumentException
at 
org.apache.myfaces.trinidad.component.UIXComponentBase.findComponent(UIXComponentBase.java:491)
at 
org.apache.myfaces.trinidad.util.ComponentUtils.findRelativeComponent(ComponentUtils.java:385)
at 
org.apache.myfaces.trinidadinternal.context.RequestContextImpl.addPartialTriggerListeners(RequestContextImpl.java:550)
at 
org.apache.myfaces.trinidad.component.UIXComponentBase.decode(UIXComponentBase.java:710)

It seems that the partialTtriggers of a component is  during decode,
which is an invalid value (although if true, this should probably be
handled).

From the stack, it appears that the problem is a child of a column
component. Try to see if you can determine the component and
partialTriggers that may be blank on decode, then get back to us.


Re: [Trinidad] Facelets, tr:treeTable and tr:inputDate

2008-07-07 Thread Andrew Robinson
You cannot use c:set with a dataTable var. JSTL is evaluated at JSP
tag execution, treeTable var is only available during JSF lifecycle
processing

On Mon, Jul 7, 2008 at 10:40 AM, Gerard Donnelly
[EMAIL PROTECTED] wrote:
 Hi all,



 I have created a treeStructure component and used it as below. Ideally I'd
 like to reuse the structure for tree models and bindings coming from
 different backing beans.



 tr:treeTable id=dtsTable value=#{searchBean.dtsTreeModel}

   var=treeRow binding=#{searchBean.bindings.flowTreeTable}

   summary=#{bundle.tb_sum_createFlow} rowBandingInterval=1

   rendered=#{searchBean.fileData.cdffAvailable}

   initiallyExpanded=true



   dts:treeStructure entity=#{treeRow} /



 /tr:treeTable





 The tree structure itself is defined as :



 ui:composition xmlns=http://www.w3.org/1999/xhtml;

   xmlns:c=http://java.sun.com/jstl/core;

   xmlns:ui=http://java.sun.com/jsf/facelets;

   xmlns:f=http://java.sun.com/jsf/core;

   xmlns:tr=http://myfaces.apache.org/trinidad;



   c:set var=nodeType value=#{entity['logicalType']} /

   c:set var=nodeData value=#{entity['data']} /

   c:set var=nodeReadOnly value=#{entity['readOnly']} /

   c:set var=nodePrecision value=#{entity['precision']} /

   c:set var=nodeFormat value=#{entity['format']} /



   f:facet name=nodeStamp

 tr:column headerText=#{bundle.th_TT_description}

   tr:outputText value=#{entity['description']}

 styleClass=MandatoryField-#{entity['mandatory']}
 /

 /tr:column

   /f:facet



   tr:column

 f:facet name=header

   tr:outputText value=#{bundle.th_TT_data} /

 /f:facet



 tr:outputText value=#{nodeData}

   rendered=#{nodeReadOnly} /



 tr:inputText value=#{nodeData}

   rendered=#{(nodeType['time'] || nodeType['string'] ||
 nodeType['number']) and !nodeReadOnly}

   maximumLength=#{nodePrecision} shortDesc=#{nodeFormat}

   readOnly=#{nodeReadOnly} /



 tr:selectOneChoice id=valSetChoice value=#{nodeData}

   autoSubmit=true rendered=#{nodeType['validSet'] and
 !nodeReadOnly}

   tr:selectItem value= label=#{bundle.dd_select} /

   f:selectItems value=#{entity['validSet']} /

 /tr:selectOneChoice



 tr:inputDate id=dateChoice value=#{nodeData}
 autoSubmit=true

   rendered=#{nodeType['date'] and !nodeReadOnly}

   maximumLength=#{nodePrecision}
 shortDesc=#{nodeFormat}

   tr:convertDateTime pattern=#{nodeFormat} /

 /tr:inputDate



   /tr:column



   tr:column styleClass=DecodeColumn

 f:facet name=header

   tr:outputText value=#{bundle.th_TT_decoded} /

 /f:facet

 tr:outputText value=#{entity['decoded']}

   partialTriggers=valSetChoice dateChoice /

   /tr:column



 /ui:composition





 Everything appears to work fine except the tr:convertDateTime. It seems to
 just ignore it and I end up with invalid date warnings.



 I've also tried passing the converter into the tag and putting in a
 ui:insert placeholder in the custom component but this doesn't have any
 effect.



 Is there anything else I can try?



 Regards,

 Gerry

 P Please consider the environment before printing this email
 _

 1. The information contained in this E-mail, including any files transmitted
 with it, is confidential and may be legally privileged. This E-mail is
 intended only for the personal attention of the stated addressee(s). Any
 access to this E-mail, including any files transmitted with it, by any other
 person is unauthorised. If you are not an addressee, you must not disclose,
 copy, circulate or in any other way use or rely on the information contained
 in this E-mail or any files transmitted with it. Such unauthorised use may
 be unlawful. If you have received this E-mail in error, please inform the
 sender immediately and delete it and all copies from your system. You may
 not forward this E-mail without the permission of the sender.

 2. The views expressed in this E-mail are those of the author, and do not
 necessarily represent the views of AMT-SYBEX. Internet communications are
 not secure and AMT-SYBEX cannot, therefore, accept legal responsibility for
 the contents of this message nor for any damage caused by viruses.

 AMT-SYBEX Limited is a UK company, registration number GB03036807 at address
 The Spirella Building, Bridge Road, Letchworth, SG6 4ET.
 AMT-SYBEX (NI) Limited is a UK company, registration number NI024104 at
 address Edgewater Office Park, Edgewater Rd, Belfast, BT3 9JQ.
 For more information on the AMT-SYBEX Group visit http://www.amt-sybex.com
 _


Re: [TRINIDAD] Unable to use Converter with tr:inputDate

2008-07-04 Thread dushyant agarwal
I need to put the converter from backing bean because the inputDate component 
is being created dynamically based upon the number of records in the 
database.Why can't we put sort of tr:validateDateTime in the backing bean

I further tried to make a sample application that contained a class 
implementing Converter class. It was registered in faces-config.There was a JSF 
page with a button and inputDate. I the action method of the button I created 
an instance of the converter class and set it as follows:-
inputDate1.setConverter(new myConverter());

But here as well the calendar component gave up working(rant)!!

Please specify what u mean by cross-postings..

Thanks,
Dushyant

--- On Thu, 3/7/08, Matthias Wessendorf [EMAIL PROTECTED] wrote:
From: Matthias Wessendorf [EMAIL PROTECTED]
Subject: Re: [TRINIDAD] Unable to use Converter with tr:inputDate
To: MyFaces Discussion users@myfaces.apache.org, [EMAIL PROTECTED]
Date: Thursday, 3 July, 2008, 5:55 PM

Please do no cross-postings...

On Thu, Jul 3, 2008 at 2:14 PM, dushyant agarwal
[EMAIL PROTECTED] wrote:
 Hi,
 I have JSF page which contains a tr:inputDate component as given below:-

 tr:inputDate binding=#{BB.inputDate1}/
 As well as there is a commandButton
 tr:commandButton action=#{BB.action}

 In the Backing bean the action method is as follows:-
 public String action(){

 DateTimeConverter converter = new DateTimeConverter();//the Trinidad
 DateTime Converter
 converter.setPattern(dd/MM/);
 inputDate1.setConverter(converter);
 return null;

 }

 While running the JSF page, on clicking the button the converter does get
 applied, But after the Page gets rendered if the user again clicks on the
 calendar button to select a new date then a javascript error appears
 (/**incomprehensible**/). How else can I set the above mentioned converter
 on the inputDate cpmponent from the backing bean.

is the scope of the BB bean request ?

 pl. consider that I strictly need to set the converter from  the backing
 bean.

why?


 Thanks,
 Dushyant




 
 Bollywood, fun, friendship, sports and more. You name it, we have it.



-- 
Matthias Wessendorf

further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org


  Explore your hobbies and interests. Go to 
http://in.promos.yahoo.com/groups/

Fw: Re: [TRINIDAD] Unable to use Converter with tr:inputDate

2008-07-04 Thread dushyant agarwal





I need to put the converter from backing bean because the inputDate component 
is being created dynamically based upon the number of records in the 
database.Why can't we put sort of tr:validateDateTime in the backing bean

And yes the BB bean is request scoped

I further tried to make a sample application that contained a class 
implementing Converter class. It was registered in faces-config.There was a JSF 
page with a button and inputDate. I the action method of the button I created 
an instance of the converter class and set it as follows:-
inputDate1.setConverter(new myConverter());

But here as well the calendar component gave up working(rant)!!

Please specify what u mean by cross-postings..

Thanks,
Dushyant

--- On Thu, 3/7/08, Matthias Wessendorf [EMAIL PROTECTED] wrote:
From: Matthias Wessendorf [EMAIL PROTECTED]
Subject: Re: [TRINIDAD] Unable to use Converter with tr:inputDate
To: MyFaces Discussion users@myfaces.apache.org, [EMAIL PROTECTED]
Date: Thursday, 3 July, 2008, 5:55 PM

Please do no cross-postings...

On Thu, Jul 3, 2008 at 2:14 PM, dushyant agarwal
[EMAIL PROTECTED] wrote:
 Hi,
 I have JSF page which contains a tr:inputDate component as given below:-

 tr:inputDate binding=#{BB.inputDate1}/
 As well as there is a commandButton
 tr:commandButton action=#{BB.action}

 In the Backing bean the action method is as follows:-
 public String action(){

 DateTimeConverter converter = new DateTimeConverter();//the Trinidad
 DateTime Converter

 converter.setPattern(dd/MM/);
 inputDate1.setConverter(converter);
 return null;

 }

 While running the JSF page, on clicking the button the converter does get
 applied, But after the Page gets rendered if the user again clicks on the
 calendar button to select a new date then a javascript error appears
 (/**incomprehensible**/). How else can I set the above mentioned converter
 on the inputDate cpmponent from the backing bean.

is the scope of the BB bean request ?

 pl. consider that I strictly need to set the converter from  the backing
 bean.

why?


 Thanks,
 Dushyant




 
 Bollywood, fun, friendship, sports and more. You name it, we have it.



-- 
Matthias Wessendorf

further stuff:
blog:
 http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org



   Best Jokes, Best Friends, Best Food. Get all this and more on  Best of 
Yahoo! Groups.


  Bollywood, fun, friendship, sports and more.. You name it, we have it on 
http://in.promos.yahoo.com/groups/bestofyahoo/

Re: [TRINIDAD] Unable to use Converter with tr:inputDate

2008-07-04 Thread Matthias Wessendorf
On Fri, Jul 4, 2008 at 10:43 AM, dushyant agarwal
[EMAIL PROTECTED] wrote:
 I need to put the converter from backing bean because the inputDate
 component is being created dynamically based upon the number of records in
 the database.Why can't we put sort of tr:validateDateTime in the backing
 bean

some don't like bindings, but in some cases, it is OK.


 I further tried to make a sample application that contained a class
 implementing Converter class. It was registered in faces-config.There was a
 JSF page with a button and inputDate. I the action method of the button I
 created an instance of the converter class and set it as follows:-
 inputDate1.setConverter(new myConverter());

 But here as well the calendar component gave up working(rant)!!

you may file an issue and/or provide a patch for that ?


 Please specify what u mean by cross-postings..

sending one email to two mailing lists
(user and dev)


 Thanks,
 Dushyant

 --- On Thu, 3/7/08, Matthias Wessendorf [EMAIL PROTECTED] wrote:

 From: Matthias Wessendorf [EMAIL PROTECTED]
 Subject: Re: [TRINIDAD] Unable to use Converter with tr:inputDate
 To: MyFaces Discussion users@myfaces.apache.org,
 [EMAIL PROTECTED]
 Date: Thursday, 3 July, 2008, 5:55 PM

 Please do no cross-postings...

 On Thu, Jul 3, 2008 at 2:14 PM, dushyant agarwal
 [EMAIL PROTECTED] wrote:
 Hi,
 I have JSF page which contains a tr:inputDate component as given below:-

 tr:inputDate binding=#{BB.inputDate1}/
 As well as there is a commandButton
 tr:commandButton action=#{BB.action}

 In the Backing bean the action method is as follows:-
 public String action(){

 DateTimeConverter converter = new DateTimeConverter();//the Trinidad
 DateTime Converter

  converter.setPattern(dd/MM/);
 inputDate1.setConverter(converter);
 return null;

 }

 While running the JSF page, on clicking the button the converter does get
 applied, But after the Page gets rendered if the user again clicks on the
 calendar button to select a new date then a javascript error appears
 (/**incomprehensible**/). How else can I set the above mentioned converter
 on the inputDate cpmponent from the backing bean.

 is the scope of the BB bean request ?

 pl. consider that I strictly need to set the converter from  the backing
 bean.

 why?


 Thanks,
 Dushyant




 
 Bollywood, fun, friendship, sports and more. You name it, we have it.



 --
 Matthias Wessendorf

 further stuff:
 blog:
  http://matthiaswessendorf.wordpress.com/
 sessions: http://www.slideshare.net/mwessendorf
 mail: matzew-at-apache-dot-org

 
 Best Jokes, Best Friends, Best Food. Get all this and more on Best of Yahoo!
 Groups.



-- 
Matthias Wessendorf

further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org


Re: [TRINIDAD] Unable to use Converter with tr:inputDate

2008-07-04 Thread dushyant agarwal
please find the content in blue.

Thanks,
Dushyant

--- On Thu, 3/7/08, Volker Weber [EMAIL PROTECTED] wrote:
From: Volker Weber [EMAIL PROTECTED]
Subject: Re: [TRINIDAD] Unable to use Converter with tr:inputDate
To: MyFaces Discussion users@myfaces.apache.org, [EMAIL PROTECTED]
Date: Thursday, 3 July, 2008, 6:10 PM

Hi!

IMO
  You should not use binding if you can avoid it !
  If you need the component in the bean it is better to do a lookup
via clientId.
/IMO

The components in my case are being generated dynamically based upon the 
records in my database. Their instance is generated at runtime in an action 
method 
.. After their instance is created I wish to put the converter on them.
How can I bring this about??

2008/7/3 dushyant agarwal [EMAIL PROTECTED]:
 Hi,
 I have JSF page which contains a tr:inputDate component as given below:-

 tr:inputDate binding=#{BB.inputDate1}/

have you tried:

tr:inputDate converter=#{BB.dateConverter} /

public Converter getDateConverter() {
  DateTimeConverter converter = new DateTimeConverter();//the Trinidad
DateTime Converter
  converter.setPattern(dd/MM/);
  return converter;
}

Yeah I tried using this but still the same runtime javascript error comes along 
on clicking on a date in the calendar


 As well as there is a commandButton
 tr:commandButton action=#{BB.action}

 In the Backing bean the action method is as follows:-
 public String action(){

 DateTimeConverter converter = new DateTimeConverter();//the Trinidad
 DateTime Converter
 converter.setPattern(dd/MM/);
 inputDate1.setConverter(converter);
 return null;

 }

 While running the JSF page, on clicking the button the converter does get
 applied, But after the Page gets rendered if the user again clicks on the
 calendar button to select a new date then a javascript error appears
 (/**incomprehensible**/). How else can I set the above mentioned converter
 on the inputDate cpmponent from the backing bean.

 pl. consider that I strictly need to set the converter from  the backing
 bean.

in the action? why?


Regards,
Volker


 Thanks,
 Dushyant




 
 Bollywood, fun, friendship, sports and more. You name it, we have it.



-- 
inexso - information exchange solutions GmbH
Bismarckstraße 13 | 26122 Oldenburg
Tel.: +49 441 4082 356 |
FAX: +49 441 4082 355 | www.inexso.de


  Bollywood, fun, friendship, sports and more. You name it, we have it on 
http://in.promos.yahoo.com/groups/bestofyahoo/

Re: [TRINIDAD] Unable to use Converter with tr:inputDate

2008-07-04 Thread Matthias Wessendorf
What kind of JavaScript error ?
What does it say?

Would be good if this is covered by an issue, do you mind filing one ?

-M

On Fri, Jul 4, 2008 at 11:04 AM, dushyant agarwal
[EMAIL PROTECTED] wrote:
 please find the content in blue.

 Thanks,
 Dushyant

 --- On Thu, 3/7/08, Volker Weber [EMAIL PROTECTED] wrote:

 From: Volker Weber [EMAIL PROTECTED]
 Subject: Re: [TRINIDAD] Unable to use Converter with tr:inputDate
 To: MyFaces Discussion users@myfaces.apache.org,
 [EMAIL PROTECTED]
 Date: Thursday, 3 July, 2008, 6:10 PM

 Hi!

 IMO
   You should not use binding if you can avoid it !
   If you need the component in the bean it is better to do a lookup
 via clientId.
 /IMO

 The components in my case are being generated dynamically based upon the
 records in my database. Their instance is
  generated at runtime in an action method
 . After their instance is created I wish to put the converter on them.
 How can I bring this about??

 2008/7/3 dushyant agarwal [EMAIL PROTECTED]:
 Hi,
 I have JSF page which contains a tr:inputDate component as given below:-

 tr:inputDate binding=#{BB.inputDate1}/

 have you tried:

 tr:inputDate converter=#{BB.dateConverter} /

 public Converter getDateConverter() {
   DateTimeConverter converter = new DateTimeConverter();//the Trinidad
 DateTime Converter
   converter.setPattern(dd/MM/);
   return converter;
 }

 Yeah I tried using this but still the same runtime javascript error comes
 along
 on clicking on a date in the calendar


 As well as there is a
  commandButton
 tr:commandButton action=#{BB.action}

 In the Backing bean the action method is as follows:-
 public String action(){

 DateTimeConverter converter = new DateTimeConverter();//the Trinidad
 DateTime Converter
 converter.setPattern(dd/MM/);
 inputDate1.setConverter(converter);
 return null;

 }

 While running the JSF page, on clicking the button the converter does get
 applied, But after the Page gets rendered if the user again clicks on the
 calendar button to select a new date then a javascript error appears
 (/**incomprehensible**/). How else can I set the above mentioned converter
 on the inputDate cpmponent from the backing bean.

 pl. consider that I strictly need to set the converter from  the backing
 bean.

 in the action? why?


 Regards,

  Volker


 Thanks,
 Dushyant




 
 Bollywood, fun, friendship, sports and more. You name it, we have it.



 --
 inexso - information exchange solutions GmbH
 Bismarckstraße 13 | 26122 Oldenburg
 Tel.: +49 441 4082 356 |
 FAX: +49 441 4082 355 | www.inexso.de

 
 Unlimited freedom, unlimited storage. Get it now



-- 
Matthias Wessendorf

further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org


Re: [TRINIDAD] Unable to use Converter with tr:inputDate

2008-07-04 Thread Matthias Wessendorf
On Fri, Jul 4, 2008 at 11:07 AM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
 What kind of JavaScript error ?
 What does it say?

 Would be good if this is covered by an issue, do you mind filing one ?

please check before if a similar issue is already in our JIRA, thanks!


 -M

 On Fri, Jul 4, 2008 at 11:04 AM, dushyant agarwal
 [EMAIL PROTECTED] wrote:
 please find the content in blue.

 Thanks,
 Dushyant

 --- On Thu, 3/7/08, Volker Weber [EMAIL PROTECTED] wrote:

 From: Volker Weber [EMAIL PROTECTED]
 Subject: Re: [TRINIDAD] Unable to use Converter with tr:inputDate
 To: MyFaces Discussion users@myfaces.apache.org,
 [EMAIL PROTECTED]
 Date: Thursday, 3 July, 2008, 6:10 PM

 Hi!

 IMO
   You should not use binding if you can avoid it !
   If you need the component in the bean it is better to do a lookup
 via clientId.
 /IMO

 The components in my case are being generated dynamically based upon the
 records in my database. Their instance is
  generated at runtime in an action method
 . After their instance is created I wish to put the converter on them.
 How can I bring this about??

 2008/7/3 dushyant agarwal [EMAIL PROTECTED]:
 Hi,
 I have JSF page which contains a tr:inputDate component as given below:-

 tr:inputDate binding=#{BB.inputDate1}/

 have you tried:

 tr:inputDate converter=#{BB.dateConverter} /

 public Converter getDateConverter() {
   DateTimeConverter converter = new DateTimeConverter();//the Trinidad
 DateTime Converter
   converter.setPattern(dd/MM/);
   return converter;
 }

 Yeah I tried using this but still the same runtime javascript error comes
 along
 on clicking on a date in the calendar


 As well as there is a
  commandButton
 tr:commandButton action=#{BB.action}

 In the Backing bean the action method is as follows:-
 public String action(){

 DateTimeConverter converter = new DateTimeConverter();//the Trinidad
 DateTime Converter
 converter.setPattern(dd/MM/);
 inputDate1.setConverter(converter);
 return null;

 }

 While running the JSF page, on clicking the button the converter does get
 applied, But after the Page gets rendered if the user again clicks on the
 calendar button to select a new date then a javascript error appears
 (/**incomprehensible**/). How else can I set the above mentioned converter
 on the inputDate cpmponent from the backing bean.

 pl. consider that I strictly need to set the converter from  the backing
 bean.

 in the action? why?


 Regards,

  Volker


 Thanks,
 Dushyant




 
 Bollywood, fun, friendship, sports and more. You name it, we have it.



 --
 inexso - information exchange solutions GmbH
 Bismarckstraße 13 | 26122 Oldenburg
 Tel.: +49 441 4082 356 |
 FAX: +49 441 4082 355 | www.inexso.de

 
 Unlimited freedom, unlimited storage. Get it now



 --
 Matthias Wessendorf

 further stuff:
 blog: http://matthiaswessendorf.wordpress.com/
 sessions: http://www.slideshare.net/mwessendorf
 mail: matzew-at-apache-dot-org




-- 
Matthias Wessendorf

further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org


[TRINIDAD]Issue:Unable to set DateTimeConverter with tr:inputDate component from the backing bean

2008-07-04 Thread dushyant agarwal
Hi,
 I have JSF page which contains a tr:inputDate component as given
 below:-

 tr:inputDate
  binding=#{BB.inputDate1}/
 As well as there is a commandButton
 tr:commandButton action=#{BB.action}/

 In the Backing bean the action method is as follows:-
 public String action(){

 DateTimeConverter converter = new DateTimeConverter();//the
 Trinidad
 DateTime Converter

  converter.setPattern(dd/MM/);
 inputDate1.setConverter(converter);
 return null;

 }

Then I tried using

tr:inputDate converter=#{BB.dateConverter} /

public Converter getDateConverter() {
  DateTimeConverter converter = new DateTimeConverter();//the Trinidad
DateTime Converter
  converter.setPattern(dd/MM/);
  return converter;
}

 While running the JSF page, on clicking the button the converter
 does
 get
 applied, But after the Page gets rendered if the user again clicks
 on
 the
 calendar button to select a new date then a javascript error
 appears
[Got this info on using firebug for debugging]

_getDateFieldFormat(input#inputDate1.af_inputDate_content)
_dfsv(input#inputDate1.af_inputDate_content,1217411811404)
 returnCalendarvalue(Window,undefined)
_checkUnload(undefined)
_selectdate(121735620)
onclick(click client X=1842, client Y =1842)
Common1_2_4.js line 2170

This error appear in the popup window where the calendar gets rendered
 
 How can I set
  the above mentioned
 converter
 on the inputDate cpmponent from the backing bean.

 The scope of the BB bean request.

 pl. consider that I strictly need to set the converter from  the
 backing bean.(Beacause sometimes the component gets generated dynamically. so 
 no way to put tr:convertDateTime  )

Thanks,
Dushyant




  Bring your gang together. Do your thing. Find your favourite Yahoo! group 
at http://in.promos.yahoo.com/groups/

Re: [TRINIDAD]Issue:Unable to set DateTimeConverter with tr:inputDate component from the backing bean

2008-07-04 Thread Matthias Wessendorf
Not a bug.
Works fine with the recent trunk.

Do this in your action:

DateTimeConverter converter = (DateTimeConverter)
FacesContext.getCurrentInstance().getApplication().createConverter(Date.class);
converter.setPattern(dd/MM/);
date.setConverter(converter);

Trinidad itself registers the correct DateTimeConverter for the
classes Date and calendar.
So, using this syntax is much more safe.

I guess you were using the one from the API JAR, but actually that guy
that provides the client-side JS, is an extended DateTimeConverter,
that extends the one from the API. And... to not have dependency to
-IMPL in your app, this is the second reason to use the
.createConverter() method,
offered by the JSF spec itself.



On Fri, Jul 4, 2008 at 12:16 PM, dushyant agarwal
[EMAIL PROTECTED] wrote:
 Hi,
  I have JSF page which contains a tr:inputDate component as given
  below:-

  tr:inputDate
   binding=#{BB.inputDate1}/
  As well as there is a commandButton
  tr:commandButton action=#{BB.action}/

  In the Backing bean the action method is as follows:-
  public String action(){

  DateTimeConverter converter = new DateTimeConverter();//the
  Trinidad
  DateTime Converter

   converter.setPattern(dd/MM/);
  inputDate1.setConverter(converter);
  return null;

  }

 Then I tried using

 tr:inputDate converter=#{BB.dateConverter} /

 public Converter getDateConverter() {
   DateTimeConverter converter = new DateTimeConverter();//the Trinidad
 DateTime Converter
   converter.setPattern(dd/MM/);
   return converter;
 }

  While running the JSF page, on clicking the button the converter
  does
  get
  applied, But after the Page gets rendered if the user again clicks
  on
  the
  calendar button to select a new date then a javascript error
  appears
 [Got this info on using firebug for debugging]

 _getDateFieldFormat(input#inputDate1.af_inputDate_content)
 _dfsv(input#inputDate1.af_inputDate_content,1217411811404)
  returnCalendarvalue(Window,undefined)
 _checkUnload(undefined)
 _selectdate(121735620)
 onclick(click client X=1842, client Y =1842)
 Common1_2_4.js line 2170

 This error appear in the popup window where the calendar gets rendered

  How can I set
   the above mentioned
  converter
  on the inputDate cpmponent from the backing bean.

  The scope of the BB bean request.

  pl. consider that I strictly need to set the converter from  the
  backing bean.(Beacause sometimes the component gets generated dynamically.
 so
  no way to put tr:convertDateTime  )

 Thanks,
 Dushyant


 
 Download prohibited? No problem. CHAT from any browser, without download.



-- 
Matthias Wessendorf

further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org


[TRINIDAD] Unable to use Converter with tr:inputDate

2008-07-03 Thread dushyant agarwal
Hi,
I have JSF page which contains a tr:inputDate component as given below:-

tr:inputDate binding=#{BB.inputDate1}/
As well as there is a commandButton 
tr:commandButton action=#{BB.action}

In the Backing bean the action method is as follows:-
public String action(){

DateTimeConverter converter = new DateTimeConverter();//the Trinidad DateTime 
Converter
converter.setPattern(dd/MM/);
inputDate1.setConverter(converter);
return null;

}

While running the JSF page, on clicking the button the converter does get 
applied, But after the Page gets rendered if the user again clicks on the 
calendar button to select a new date then a javascript error appears 
(/**incomprehensible**/). How else can I set the above mentioned converter on 
the inputDate cpmponent from the backing bean.

pl. consider that I strictly need to set the converter from  the backing bean.

Thanks,
Dushyant






  Explore your hobbies and interests. Go to 
http://in.promos.yahoo.com/groups/

Re: [TRINIDAD] Unable to use Converter with tr:inputDate

2008-07-03 Thread Matthias Wessendorf
Please do no cross-postings...

On Thu, Jul 3, 2008 at 2:14 PM, dushyant agarwal
[EMAIL PROTECTED] wrote:
 Hi,
 I have JSF page which contains a tr:inputDate component as given below:-

 tr:inputDate binding=#{BB.inputDate1}/
 As well as there is a commandButton
 tr:commandButton action=#{BB.action}

 In the Backing bean the action method is as follows:-
 public String action(){

 DateTimeConverter converter = new DateTimeConverter();//the Trinidad
 DateTime Converter
 converter.setPattern(dd/MM/);
 inputDate1.setConverter(converter);
 return null;

 }

 While running the JSF page, on clicking the button the converter does get
 applied, But after the Page gets rendered if the user again clicks on the
 calendar button to select a new date then a javascript error appears
 (/**incomprehensible**/). How else can I set the above mentioned converter
 on the inputDate cpmponent from the backing bean.

is the scope of the BB bean request ?

 pl. consider that I strictly need to set the converter from  the backing
 bean.

why?


 Thanks,
 Dushyant




 
 Bollywood, fun, friendship, sports and more. You name it, we have it.



-- 
Matthias Wessendorf

further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org


Re: [TRINIDAD] Unable to use Converter with tr:inputDate

2008-07-03 Thread Volker Weber
Hi!

IMO
  You should not use binding if you can avoid it !
  If you need the component in the bean it is better to do a lookup
via clientId.
/IMO

2008/7/3 dushyant agarwal [EMAIL PROTECTED]:
 Hi,
 I have JSF page which contains a tr:inputDate component as given below:-

 tr:inputDate binding=#{BB.inputDate1}/

have you tried:

tr:inputDate converter=#{BB.dateConverter} /

public Converter getDateConverter() {
  DateTimeConverter converter = new DateTimeConverter();//the Trinidad
DateTime Converter
  converter.setPattern(dd/MM/);
  return converter;
}


 As well as there is a commandButton
 tr:commandButton action=#{BB.action}

 In the Backing bean the action method is as follows:-
 public String action(){

 DateTimeConverter converter = new DateTimeConverter();//the Trinidad
 DateTime Converter
 converter.setPattern(dd/MM/);
 inputDate1.setConverter(converter);
 return null;

 }

 While running the JSF page, on clicking the button the converter does get
 applied, But after the Page gets rendered if the user again clicks on the
 calendar button to select a new date then a javascript error appears
 (/**incomprehensible**/). How else can I set the above mentioned converter
 on the inputDate cpmponent from the backing bean.

 pl. consider that I strictly need to set the converter from  the backing
 bean.

in the action? why?


Regards,
Volker


 Thanks,
 Dushyant




 
 Bollywood, fun, friendship, sports and more. You name it, we have it.



-- 
inexso - information exchange solutions GmbH
Bismarckstraße 13 | 26122 Oldenburg
Tel.: +49 441 4082 356 |
FAX: +49 441 4082 355 | www.inexso.de


Re: [TRINIDAD] Unable to use Converter with tr:inputDate

2008-07-03 Thread Matthias Wessendorf
On Thu, Jul 3, 2008 at 2:40 PM, Volker Weber [EMAIL PROTECTED] wrote:
 Hi!

 IMO
  You should not use binding if you can avoid it !
  If you need the component in the bean it is better to do a lookup
 via clientId.
 /IMO

+1


 2008/7/3 dushyant agarwal [EMAIL PROTECTED]:
 Hi,
 I have JSF page which contains a tr:inputDate component as given below:-

 tr:inputDate binding=#{BB.inputDate1}/

 have you tried:

 tr:inputDate converter=#{BB.dateConverter} /

 public Converter getDateConverter() {
  DateTimeConverter converter = new DateTimeConverter();//the Trinidad
 DateTime Converter
  converter.setPattern(dd/MM/);
  return converter;
 }


 As well as there is a commandButton
 tr:commandButton action=#{BB.action}

 In the Backing bean the action method is as follows:-
 public String action(){

 DateTimeConverter converter = new DateTimeConverter();//the Trinidad
 DateTime Converter
 converter.setPattern(dd/MM/);
 inputDate1.setConverter(converter);
 return null;

 }

 While running the JSF page, on clicking the button the converter does get
 applied, But after the Page gets rendered if the user again clicks on the
 calendar button to select a new date then a javascript error appears
 (/**incomprehensible**/). How else can I set the above mentioned converter
 on the inputDate cpmponent from the backing bean.

 pl. consider that I strictly need to set the converter from  the backing
 bean.

 in the action? why?


 Regards,
Volker


 Thanks,
 Dushyant




 
 Bollywood, fun, friendship, sports and more. You name it, we have it.



 --
 inexso - information exchange solutions GmbH
 Bismarckstraße 13 | 26122 Oldenburg
 Tel.: +49 441 4082 356 |
 FAX: +49 441 4082 355 | www.inexso.de




-- 
Matthias Wessendorf

further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org


RE: [Trinidad] Facelets, tr:treeTable and tr:inputDate

2008-07-03 Thread Gerard Donnelly
Hi All,

 

I'm still looking at this.

 

From looking at the source code it appears that the exception below is
thrown for blank (as opposed to null) ids.

 

Caused by: java.lang.IllegalArgumentException

at
org.apache.myfaces.trinidad.component.UIXComponentBase.findComponent(UIX
ComponentBase.java:491)

at
org.apache.myfaces.trinidad.util.ComponentUtils.findRelativeComponent(Co
mponentUtils.java:385)

 

With this in mind I have explicitly given ids to components likely to
use PPR. However, the exception is still being thrown.

 

Is there anything particular to components within a treeTable either
having their ids reset or just not being found?

 

Thanks,

Gerry

 



From: Gerard Donnelly [mailto:[EMAIL PROTECTED] 
Sent: 30 June 2008 12:01
To: MyFaces Discussion
Subject: RE: [Trinidad] Facelets, tr:treeTable and tr:inputDate

 

Sorry, that should be myfaces 1.2.3

 



From: Gerard Donnelly [mailto:[EMAIL PROTECTED] 
Sent: 30 June 2008 11:41
To: MyFaces Discussion
Subject: [Trinidad] Facelets, tr:treeTable and tr:inputDate

 

** This Message Originated From The Internet Please Be Aware Of
Suspicious Attachments And Content ** 

  

Hi all,

 

I have an existing small project. It's getting larger so I'm attempting
to make use of Facelets. 

 

I would like to make a reusable component based on the tr:treetable.
But, as yet, I cannot get it working when using it as the content of a
predefined template.  The tree table has several columns but only one
input field - rendered based on the type of the required data (see
attached extract).

 

 

I have implemented this without Facelets and it works fine. Using
Facelets, it seems to ignore the pattern specified in the
convertDataTime. I'm also getting a PPR error when clicking on the icon
to display the calendar. This doesn't occur all the time and I haven't
yet determined how to regularly recreate this. The exception is
attached.

 

These errors are particular to use in a tr:treeTable component - I've
used input dates in a standard tr:form and have no issues.

 

I've using Trinidad 1.2.8, myfaces 1.2.4 and Facelets 1.1.14 on SAP
Netweaver

 

Any tips would be greatly appreciated.

 

Regards,

Gerry Donnelly

 

P Please consider the environment before printing this email 

_ 
 
1. The information contained in this E-mail, including any files
transmitted with it, is confidential and may be legally privileged. This
E-mail is intended only for the personal attention of the stated
addressee(s). Any access to this E-mail, including any files transmitted
with it, by any other person is unauthorised. If you are not an
addressee, you must not disclose, copy, circulate or in any other way
use or rely on the information contained in this E-mail or any files
transmitted with it. Such unauthorised use may be unlawful. If you have
received this E-mail in error, please inform the sender immediately and
delete it and all copies from your system. You may not forward this
E-mail without the permission of the sender.
 
2. The views expressed in this E-mail are those of the author, and do
not necessarily represent the views of AMT-SYBEX. Internet
communications are not secure and AMT-SYBEX cannot, therefore, accept
legal responsibility for the contents of this message nor for any damage
caused by viruses. 
  

AMT-SYBEX Limited is a UK company, registration number GB03036807 at
address The Spirella Building, Bridge Road, Letchworth, SG6 4ET.  

AMT-SYBEX (NI) Limited is a UK company, registration number NI024104 at
address Edgewater Office Park, Edgewater Rd, Belfast, BT3 9JQ.
For more information on the AMT-SYBEX Group visit
http://www.amt-sybex.com http://www.amt-sybex.com/ 
_ 

 

 

P Please consider the environment before printing this email 

 



[Trinidad] Facelets, tr:treeTable and tr:inputDate

2008-06-30 Thread Gerard Donnelly
Hi all,

 

I have an existing small project. It's getting larger so I'm attempting
to make use of Facelets. 

 

I would like to make a reusable component based on the tr:treetable.
But, as yet, I cannot get it working when using it as the content of a
predefined template.  The tree table has several columns but only one
input field - rendered based on the type of the required data (see
attached extract).

 

 

I have implemented this without Facelets and it works fine. Using
Facelets, it seems to ignore the pattern specified in the
convertDataTime. I'm also getting a PPR error when clicking on the icon
to display the calendar. This doesn't occur all the time and I haven't
yet determined how to regularly recreate this. The exception is
attached.

 

These errors are particular to use in a tr:treeTable component - I've
used input dates in a standard tr:form and have no issues.

 

I've using Trinidad 1.2.8, myfaces 1.2.4 and Facelets 1.1.14 on SAP
Netweaver

 

Any tips would be greatly appreciated.

 

Regards,

Gerry Donnelly


P Please consider the environment before printing this email
_ 
 
1. The information contained in this E-mail, including any files transmitted 
with it, is confidential and may be legally privileged. This E-mail is intended 
only for the personal attention of the stated addressee(s). Any access to this 
E-mail, including any files transmitted with it, by any other person is 
unauthorised. If you are not an addressee, you must not disclose, copy, 
circulate or in any other way use or rely on the information contained in this 
E-mail or any files transmitted with it. Such unauthorised use may be unlawful. 
If you have received this E-mail in error, please inform the sender immediately 
and delete it and all copies from your system. You may not forward this E-mail 
without the permission of the sender.
 
2. The views expressed in this E-mail are those of the author, and do not 
necessarily represent the views of AMT-SYBEX. Internet communications are not 
secure and AMT-SYBEX cannot, therefore, accept legal responsibility for the 
contents of this message nor for any damage caused by viruses.
 
AMT-SYBEX Limited is a UK company, registration number GB03036807 at address 
The Spirella Building, Bridge Road, Letchworth, SG6 4ET. 
AMT-SYBEX (NI) Limited is a UK company, registration number NI024104 at address 
Edgewater Office Park, Edgewater Rd, Belfast, BT3 9JQ.
For more information on the AMT-SYBEX Group visit http://www.amt-sybex.com
_


tree.xhtml
Description: tree.xhtml
org.apache.myfaces.trinidadinternal.config.xmlHttp.XmlHttpConfigurator 
handleError
SEVERE: Server Exception during PPR, #1
javax.servlet.ServletException
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:256)
at 
com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:163)
at 
com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:82)
at 
org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._invokeDoFilter(TrinidadFilterImpl.java:238)
at 
org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:195)
at 
org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:138)
at 
org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
at 
com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:74)
at 
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:425)
at 
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289)
at 
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at 
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
at 
com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
at 
com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at 
com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
at 
com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at 
com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
at 
com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at 
com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at 
com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at 
com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at 
com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at 

RE: [Trinidad] Facelets, tr:treeTable and tr:inputDate

2008-06-30 Thread Gerard Donnelly
Sorry, that should be myfaces 1.2.3

 



From: Gerard Donnelly [mailto:[EMAIL PROTECTED] 
Sent: 30 June 2008 11:41
To: MyFaces Discussion
Subject: [Trinidad] Facelets, tr:treeTable and tr:inputDate

 

** This Message Originated From The Internet Please Be Aware Of
Suspicious Attachments And Content ** 

  

Hi all,

 

I have an existing small project. It's getting larger so I'm attempting
to make use of Facelets. 

 

I would like to make a reusable component based on the tr:treetable.
But, as yet, I cannot get it working when using it as the content of a
predefined template.  The tree table has several columns but only one
input field - rendered based on the type of the required data (see
attached extract).

 

 

I have implemented this without Facelets and it works fine. Using
Facelets, it seems to ignore the pattern specified in the
convertDataTime. I'm also getting a PPR error when clicking on the icon
to display the calendar. This doesn't occur all the time and I haven't
yet determined how to regularly recreate this. The exception is
attached.

 

These errors are particular to use in a tr:treeTable component - I've
used input dates in a standard tr:form and have no issues.

 

I've using Trinidad 1.2.8, myfaces 1.2.4 and Facelets 1.1.14 on SAP
Netweaver

 

Any tips would be greatly appreciated.

 

Regards,

Gerry Donnelly





P Please consider the environment before printing this email 

_ 
 
1. The information contained in this E-mail, including any files
transmitted with it, is confidential and may be legally privileged. This
E-mail is intended only for the personal attention of the stated
addressee(s). Any access to this E-mail, including any files transmitted
with it, by any other person is unauthorised. If you are not an
addressee, you must not disclose, copy, circulate or in any other way
use or rely on the information contained in this E-mail or any files
transmitted with it. Such unauthorised use may be unlawful. If you have
received this E-mail in error, please inform the sender immediately and
delete it and all copies from your system. You may not forward this
E-mail without the permission of the sender.
 
2. The views expressed in this E-mail are those of the author, and do
not necessarily represent the views of AMT-SYBEX. Internet
communications are not secure and AMT-SYBEX cannot, therefore, accept
legal responsibility for the contents of this message nor for any damage
caused by viruses. 
  

AMT-SYBEX Limited is a UK company, registration number GB03036807 at
address The Spirella Building, Bridge Road, Letchworth, SG6 4ET.  

AMT-SYBEX (NI) Limited is a UK company, registration number NI024104 at
address Edgewater Office Park, Edgewater Rd, Belfast, BT3 9JQ.
For more information on the AMT-SYBEX Group visit
http://www.amt-sybex.com http://www.amt-sybex.com/ 
_ 

 

 

P Please consider the environment before printing this email 

 



Re: [Trinidad] tr:inputDate and dialog:xyz results in HTTP404 resource not found

2008-06-13 Thread Matthias Wessendorf
Hi Alexander,

just a quick note, since nobody yet responded.

I just tested the following setting:
-jetty6x
-trinidad1.2.9
-myfaces-123
-JSPX
-w/ and w/o lightweight dialogs.

= inputDate worked fine for me (just did a quick run of our little
demo app)

But... it doesn't use Facelets... so... I am not really sure if that
did a kinda side effect on your
settings...

-Matthias


On Thu, Jun 12, 2008 at 4:24 AM,  [EMAIL PROTECTED] wrote:
 Hi all,



 we are currently developing a JSF-1.2/Facelets application using
 MyFaces-1.2.3, Hibernate-3.2 and Trinidad 1.2.8. Target server is
 Tomcat-6.0.16.



 We encounter problems both in displaying popup dialogs using the dialog
 framework as well as tr:inputDate controls not being displayed.



 When enabling LIGHTWEIGHT_DIALOGS popup dialogs are displayed, but no
 tr:inputDate control shows up (I have not tested other popup controls but I
 am pretty sure, that the problem will be the same). With LIGHTWEIGHT_DIALOGS
 being disabled, both popup dialogs and tr:inputDate launch a separate HTTP
 404 browser page ('description  The requested resource (/IRMAT/__ADFv__) is
 not available', where IRMAT is the name of the project/WebApp root folder).
 This has been tested with Firefox-2.0.0.14. IE7 though, does not display
 anything in the latter case, not even the tr:inputDate control icon is
 displayed. IE7 instead has some 'page error' notes instead, but which show
 no real hint on the error at all. The HTTP 404 description above shows up
 for the simple test page replacing the startup. When running the actual
 application then the description turns into 'The requested resource
 (/IRMAT/views/%5Bobject%20Window%5D) is not available.' (the pages are using
 a template). As the effect is the same for both use cases I suppose we have
 a general configuration error or else. I tried several servlet mappings but
 nothing helped.



 Additionally in the server output console window we get a lot of

 13:16:59,734 ERROR DebugUtils:232 - javax.faces.FacesException: Could not
 get property facetCount of component j_id2

 Maybe that gives someone a clue, I am not sure, if this has something to do
 with the problems with the popup windows.



 This is the code of the simple test page for the tr:inputDate:



 body

 ui:composition

   tr:form id=testForm

 tr:inputDate id=testDate label=Date
 value=#{teamBean.date} /

   /tr:form

 /ui:composition

 /body



 This is the code for the popup dialog (Delete-commandLink):



 body

 ui:composition template=/templates/page-template.xhtml



   ui:define name=title#{msg['team-edit.title']}/ui:define



   ui:define name=breadcrumbsAdministration - #{teamBean.editMode}
 Team/ui:define



   ui:define name=body

 tr:messages globalOnly=true /



 tr:form defaultCommand=buttonSaveTeam styleClass=noPrint

   tr:panelHeader text=#{teamBean.editMode} Team /



   tr:panelFormLayout

 tr:inputText id=teamNameInput
 label=#{msg['team.name']}

  value=#{teamBean.team.name} required=true
 maximumLength=16

 /tr:inputText

 div id=teamNameErrh:message for=teamNameInput
 //div



   /tr:panelFormLayout



   tr:spacer height=10px /



   tr:panelButtonBar

 tr:commandButton id=buttonSaveTeam
 styleClass=airbusButton

  text=#{teamBean.selectedTeamId == null ?
 'Create' : 'Save'}

  inlineStyle=width:120px
 action=#{teamBean.saveTeam}

 /tr:commandButton



   /tr:panelButtonBar



 /tr:form

   /ui:define

 /ui:composition

 /body



 Here's our Trinidad config file:



 trinidad-config xmlns=http://myfaces.apache.org/trinidad/config;



   client-validationINLINE/client-validation



   client-validationDISABLED/client-validation



   skin-familyairbus/skin-family



   !-- Enable debug output here --

   debug-outputfalse/debug-output



   !-- Improve a4j compatibility --

   accessibility-modeinaccessible/accessibility-mode

 /trinidad-config





 This is the content of our web.xml:




 !--#--

 !--# Tomcat begin
 #--


 !--#--



   welcome-file-list

 welcome-filetest_page.xhtml/welcome-file

   /welcome-file-list




 !--#--

 !--# Tomcat end
#--


 !--#--






 !--#--

 !--# JSF begin

Re: [Trinidad] How to change the first day of week in an tr:inputDate

2008-06-05 Thread Rafa Pérez
Hi Simon,

I have been searching the related issue (TRINIDAD-634) and changing
the code to make it work properly. I would like to attach a patch, but
I have never done it before. How can I create it? Should I attach it
directly to JIRA?

Regards,

-- Rafa


On Tue, Jun 3, 2008 at 7:05 PM, Simon Lessard [EMAIL PROTECTED] wrote:
 Hello Rafa,

 It's currently impossible, but there's a JIRA ticket about this already, so
 it'll be added eventually.


 Sorry,

 ~ Simon

 On Tue, Jun 3, 2008 at 12:21 PM, Rafa Pérez [EMAIL PROTECTED] wrote:

 Hi all,

 I have just figured out that tr:inputDate shows Sunday as the first
 day of the week. How could this be changed to set Monday as the first
 day of the week?

 Thanks in advance,

 -- Rafa




Re: [Trinidad] How to change the first day of week in an tr:inputDate

2008-06-05 Thread Matthias Wessendorf
Hi,

On Thu, Jun 5, 2008 at 2:29 PM, Rafa Pérez [EMAIL PROTECTED] wrote:
 Hi Simon,

 I have been searching the related issue (TRINIDAD-634) and changing
 the code to make it work properly. I would like to attach a patch, but
 I have never done it before. How can I create it? Should I attach it
 directly to JIRA?

use svn to create a patch (a diff file) and simply attach the patch to the jira
ticket. That way we (the committers) can apply the patch very easily.

-M


 Regards,

 -- Rafa


 On Tue, Jun 3, 2008 at 7:05 PM, Simon Lessard [EMAIL PROTECTED] wrote:
 Hello Rafa,

 It's currently impossible, but there's a JIRA ticket about this already, so
 it'll be added eventually.


 Sorry,

 ~ Simon

 On Tue, Jun 3, 2008 at 12:21 PM, Rafa Pérez [EMAIL PROTECTED] wrote:

 Hi all,

 I have just figured out that tr:inputDate shows Sunday as the first
 day of the week. How could this be changed to set Monday as the first
 day of the week?

 Thanks in advance,

 -- Rafa






-- 
Matthias Wessendorf

further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org


Re: [Trinidad] How to change the first day of week in an tr:inputDate

2008-06-05 Thread Rafa Pérez
Patch added.

On Thu, Jun 5, 2008 at 2:37 PM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
 Hi,

 On Thu, Jun 5, 2008 at 2:29 PM, Rafa Pérez [EMAIL PROTECTED] wrote:
 Hi Simon,

 I have been searching the related issue (TRINIDAD-634) and changing
 the code to make it work properly. I would like to attach a patch, but
 I have never done it before. How can I create it? Should I attach it
 directly to JIRA?

 use svn to create a patch (a diff file) and simply attach the patch to the 
 jira
 ticket. That way we (the committers) can apply the patch very easily.

 -M


 Regards,

 -- Rafa


 On Tue, Jun 3, 2008 at 7:05 PM, Simon Lessard [EMAIL PROTECTED] wrote:
 Hello Rafa,

 It's currently impossible, but there's a JIRA ticket about this already, so
 it'll be added eventually.


 Sorry,

 ~ Simon

 On Tue, Jun 3, 2008 at 12:21 PM, Rafa Pérez [EMAIL PROTECTED] wrote:

 Hi all,

 I have just figured out that tr:inputDate shows Sunday as the first
 day of the week. How could this be changed to set Monday as the first
 day of the week?

 Thanks in advance,

 -- Rafa






 --
 Matthias Wessendorf

 further stuff:
 blog: http://matthiaswessendorf.wordpress.com/
 sessions: http://www.slideshare.net/mwessendorf
 mail: matzew-at-apache-dot-org



Re: [Trinidad] How to change the first day of week in an tr:inputDate

2008-06-05 Thread Matthias Wessendorf
saw that.
will check the patch soon.

Thanks!

On Thu, Jun 5, 2008 at 4:02 PM, Rafa Pérez [EMAIL PROTECTED] wrote:
 Patch added.

 On Thu, Jun 5, 2008 at 2:37 PM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
 Hi,

 On Thu, Jun 5, 2008 at 2:29 PM, Rafa Pérez [EMAIL PROTECTED] wrote:
 Hi Simon,

 I have been searching the related issue (TRINIDAD-634) and changing
 the code to make it work properly. I would like to attach a patch, but
 I have never done it before. How can I create it? Should I attach it
 directly to JIRA?

 use svn to create a patch (a diff file) and simply attach the patch to the 
 jira
 ticket. That way we (the committers) can apply the patch very easily.

 -M


 Regards,

 -- Rafa


 On Tue, Jun 3, 2008 at 7:05 PM, Simon Lessard [EMAIL PROTECTED] wrote:
 Hello Rafa,

 It's currently impossible, but there's a JIRA ticket about this already, so
 it'll be added eventually.


 Sorry,

 ~ Simon

 On Tue, Jun 3, 2008 at 12:21 PM, Rafa Pérez [EMAIL PROTECTED] wrote:

 Hi all,

 I have just figured out that tr:inputDate shows Sunday as the first
 day of the week. How could this be changed to set Monday as the first
 day of the week?

 Thanks in advance,

 -- Rafa






 --
 Matthias Wessendorf

 further stuff:
 blog: http://matthiaswessendorf.wordpress.com/
 sessions: http://www.slideshare.net/mwessendorf
 mail: matzew-at-apache-dot-org





-- 
Matthias Wessendorf

further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org


Re: [Trinidad] How to change the first day of week in an tr:inputDate

2008-06-05 Thread Rafa Pérez
Nice to help, only hope it works ok!! :D


On Thu, Jun 5, 2008 at 4:40 PM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
 saw that.
 will check the patch soon.

 Thanks!

 On Thu, Jun 5, 2008 at 4:02 PM, Rafa Pérez [EMAIL PROTECTED] wrote:
 Patch added.

 On Thu, Jun 5, 2008 at 2:37 PM, Matthias Wessendorf [EMAIL PROTECTED] 
 wrote:
 Hi,

 On Thu, Jun 5, 2008 at 2:29 PM, Rafa Pérez [EMAIL PROTECTED] wrote:
 Hi Simon,

 I have been searching the related issue (TRINIDAD-634) and changing
 the code to make it work properly. I would like to attach a patch, but
 I have never done it before. How can I create it? Should I attach it
 directly to JIRA?

 use svn to create a patch (a diff file) and simply attach the patch to the 
 jira
 ticket. That way we (the committers) can apply the patch very easily.

 -M


 Regards,

 -- Rafa


 On Tue, Jun 3, 2008 at 7:05 PM, Simon Lessard [EMAIL PROTECTED] wrote:
 Hello Rafa,

 It's currently impossible, but there's a JIRA ticket about this already, 
 so
 it'll be added eventually.


 Sorry,

 ~ Simon

 On Tue, Jun 3, 2008 at 12:21 PM, Rafa Pérez [EMAIL PROTECTED] wrote:

 Hi all,

 I have just figured out that tr:inputDate shows Sunday as the first
 day of the week. How could this be changed to set Monday as the first
 day of the week?

 Thanks in advance,

 -- Rafa






 --
 Matthias Wessendorf

 further stuff:
 blog: http://matthiaswessendorf.wordpress.com/
 sessions: http://www.slideshare.net/mwessendorf
 mail: matzew-at-apache-dot-org





 --
 Matthias Wessendorf

 further stuff:
 blog: http://matthiaswessendorf.wordpress.com/
 sessions: http://www.slideshare.net/mwessendorf
 mail: matzew-at-apache-dot-org



Re: [Trinidad] How to change the first day of week in an tr:inputDate

2008-06-05 Thread Matthias Wessendorf
On Thu, Jun 5, 2008 at 4:45 PM, Rafa Pérez [EMAIL PROTECTED] wrote:
 Nice to help, only hope it works ok!! :D

I think, testing helps ;-)




 On Thu, Jun 5, 2008 at 4:40 PM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
 saw that.
 will check the patch soon.

 Thanks!

 On Thu, Jun 5, 2008 at 4:02 PM, Rafa Pérez [EMAIL PROTECTED] wrote:
 Patch added.

 On Thu, Jun 5, 2008 at 2:37 PM, Matthias Wessendorf [EMAIL PROTECTED] 
 wrote:
 Hi,

 On Thu, Jun 5, 2008 at 2:29 PM, Rafa Pérez [EMAIL PROTECTED] wrote:
 Hi Simon,

 I have been searching the related issue (TRINIDAD-634) and changing
 the code to make it work properly. I would like to attach a patch, but
 I have never done it before. How can I create it? Should I attach it
 directly to JIRA?

 use svn to create a patch (a diff file) and simply attach the patch to the 
 jira
 ticket. That way we (the committers) can apply the patch very easily.

 -M


 Regards,

 -- Rafa


 On Tue, Jun 3, 2008 at 7:05 PM, Simon Lessard [EMAIL PROTECTED] wrote:
 Hello Rafa,

 It's currently impossible, but there's a JIRA ticket about this already, 
 so
 it'll be added eventually.


 Sorry,

 ~ Simon

 On Tue, Jun 3, 2008 at 12:21 PM, Rafa Pérez [EMAIL PROTECTED] wrote:

 Hi all,

 I have just figured out that tr:inputDate shows Sunday as the first
 day of the week. How could this be changed to set Monday as the first
 day of the week?

 Thanks in advance,

 -- Rafa






 --
 Matthias Wessendorf

 further stuff:
 blog: http://matthiaswessendorf.wordpress.com/
 sessions: http://www.slideshare.net/mwessendorf
 mail: matzew-at-apache-dot-org





 --
 Matthias Wessendorf

 further stuff:
 blog: http://matthiaswessendorf.wordpress.com/
 sessions: http://www.slideshare.net/mwessendorf
 mail: matzew-at-apache-dot-org





-- 
Matthias Wessendorf

further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org


[Trinidad] How to change the first day of week in an tr:inputDate

2008-06-03 Thread Rafa Pérez
Hi all,

I have just figured out that tr:inputDate shows Sunday as the first
day of the week. How could this be changed to set Monday as the first
day of the week?

Thanks in advance,

-- Rafa


Re: [Trinidad] How to change the first day of week in an tr:inputDate

2008-06-03 Thread Simon Lessard
Hello Rafa,

It's currently impossible, but there's a JIRA ticket about this already, so
it'll be added eventually.


Sorry,

~ Simon

On Tue, Jun 3, 2008 at 12:21 PM, Rafa Pérez [EMAIL PROTECTED] wrote:

 Hi all,

 I have just figured out that tr:inputDate shows Sunday as the first
 day of the week. How could this be changed to set Monday as the first
 day of the week?

 Thanks in advance,

 -- Rafa



[TRINIDAT] tr:inputDate PPR works for a Date but do not support a Timestamp. Any Idea how to resolve.

2008-04-30 Thread Martin Piekorz
Hello all,

yesterday I posted that my tr:inputDate supports PPR after changing it twice.
I also have a second inputDate in my GUI. It is the date of birth of a person 
and there it is supported!
In our project we use hibernate and jpa.
The difference between these properties is:

The javax.persistence.TemporalType:

DateOfBirth is a  TemporalType DATE  - PPR works fine.

ValidTo is a TemporalType.TIMESTAMP - PPR works after changing value twice.


...
private Date dateOfBirth;
private Date validTo;

@Temporal(TemporalType.DATE)
public Date getDateOfBirth()
{
 return this.dateOfBirth;
}


@Temporal(TemporalType.TIMESTAMP)
public Date getValidTo()
{
 return this.validTo;
}
...

Does someone know what the problem might be? I think something with the time...?
How could I resolve this? A converter which add a time?

Kind regards
Martin



Re: [Trinidad] JS-Error dialog-Framework and tr:inputDate

2008-04-23 Thread Scott O'Bryan
Yeah, Trinidad 1.2 won't run on Tomcat 5.  It's JSF 1.2 so it requires 
Tomcat 6.


Kuhn, Harald wrote:


Hi to all,

we are using Trinidad-1.2.8-SNAPSHOT while testing our application on 
tomcat 5.5.25 / Linux / Apache2.

Browser is Firefox 2.0.0.14.

There we get an JS-Exception on trying to open a dialog (i.e. calendar 
of tr:inputDate).

The message is:
uncaught exception: Right to read property Window._dependents denied.

From Firebug:
uncaught exception: Die Erlaubnis für das Lesen der Eigenschaft 
Window._dependents wurde verweigert
_getValidators(form#mainForm myReports.xhtml)DebugCommon1_2_8 
(line 8378)
_validateInline(form#mainForm myReports.xhtml, j_id29, 
undefined)DebugCommon1_2_8 (line 6877)
_mainFormValidator(form#mainForm myReports.xhtml, 
j_id29)settings.xhtml (line 143)
_validateForm(form#mainForm myReports.xhtml, 
j_id29)DebugCommon1_2_8 (line 6749)
submitForm(form#mainForm myReports.xhtml, 1, Object source=j_id29, 
undefined)DebugCommon1_2_8 (line 7230)

onclick(click clientX=0, clientY=0)

Are there any know bugs/issues in the current SNAPSHOT-Release?

Even more weird is the fact that on Windows (tomcat 6.0.14) the 
calendar is shown, but if you choose a date the following message is 
shown:


Picture (Device Independent Bitmap)

Thanks for any hints.

  Harald


*/**/*
*/Harald Kuhn/*
*/AirPlus International/*
*/Business Information Services/*
*/Phone:   +49 (0) 61 02 204-821/*
*/Fax: +49 (0) 61 02 204-139/*
*/E-Mail:   [EMAIL PROTECTED]/*
*/Internet:  /**/_www.airplus.com_/* http://www.airplus.com*//*
*/**/*

*AirPlus International - Winner of the Buying Business Travel Diamond 
Award 2008 for Best Corporate Card Provider*


Lufthansa AirPlus Servicekarten GmbH · Hans-Böckler-Straße 7 · 63263 
Neu-Isenburg · Deutschland · Geschäftsführer: Patrick W. Diemer 
(Vorsitz), Klaus Busch · Vorsitzender des Aufsichtsrates: Stephan 
Gemkow · Handelsregister: Amtsgericht Offenbach/Main, HRB 8119 */ /*







Re: [trinidad] Clicking tr:inputDate icon gives Page not found

2008-02-28 Thread Matthias Wessendorf
Hi,

On Thu, Feb 28, 2008 at 8:07 AM, Paul van Rossem [EMAIL PROTECTED] wrote:
 Hi,
  If I use the tr:inputDate tag, clicking the calendar icon yields a
  Page not found, page /__ADFv__.jsf.
  Both in FF and IE. I'm using Trinidad 1.2.6. Do I need to include

and MyFaces 1.2.x ?


  anything special, apart from the 2 libraries (api en impl) or has it
  something to do with my web.xml or faces-config.xml?

I'd suggest to use this *mapping*:
/faces/*
and not:
*.jsf

-Matthias


  I saw some additional configuration items in the examples
  faces-config.xml. Is that required?
   component

  component-typeorg.apache.myfaces.trinidaddemo.DateField/component-type

  
 component-classorg.apache.myfaces.trinidaddemo.composite.DateField/component-class
   /component
  Should I include something linke that in my faces-config.xml or what is
  it for?
  Any tips would be appreciated, regards, Paul.





-- 
Matthias Wessendorf

further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org


Re: [trinidad] Clicking tr:inputDate icon gives Page not found

2008-02-28 Thread Paul van Rossem

Hi Matthias,

Thanks a lot for your reply. It solved my problem.
Indeed, if I use the /faces/* mapping instead *.jsf, it loads the 
correct page.


Shouldn't it be independent of the mapping? Should I file a JIRA issue 
for this?

I was using the jsf-1.2_07-b03 RI, not MyFaces.
Regards, Paul.


Matthias Wessendorf wrote:

Hi,

On Thu, Feb 28, 2008 at 8:07 AM, Paul van Rossem [EMAIL PROTECTED] wrote:
  

Hi,
 If I use the tr:inputDate tag, clicking the calendar icon yields a
 Page not found, page /__ADFv__.jsf.
 Both in FF and IE. I'm using Trinidad 1.2.6. Do I need to include



and MyFaces 1.2.x ?


  

 anything special, apart from the 2 libraries (api en impl) or has it
 something to do with my web.xml or faces-config.xml?



I'd suggest to use this *mapping*:
/faces/*
and not:
*.jsf

-Matthias

  

 I saw some additional configuration items in the examples
 faces-config.xml. Is that required?
  component

 component-typeorg.apache.myfaces.trinidaddemo.DateField/component-type

 
component-classorg.apache.myfaces.trinidaddemo.composite.DateField/component-class
  /component
 Should I include something linke that in my faces-config.xml or what is
 it for?
 Any tips would be appreciated, regards, Paul.







  


--
Paul van Rossem, Van Rossem Timeware
Tempellaan  18,  3721  VH  Bilthoven
tel: 030-220.4006, fax: 030-220.3445
www.timeware.nl, mobiel 06-5468.3405



Re: [trinidad] Clicking tr:inputDate icon gives Page not found

2008-02-28 Thread Matthias Wessendorf
Hi,

On Thu, Feb 28, 2008 at 11:09 AM, Paul van Rossem [EMAIL PROTECTED] wrote:
 Hi Matthias,

  Thanks a lot for your reply. It solved my problem.
  Indeed, if I use the /faces/* mapping instead *.jsf, it loads the
  correct page.

  Shouldn't it be independent of the mapping? Should I file a JIRA issue
  for this?
  I was using the jsf-1.2_07-b03 RI, not MyFaces.
  Regards, Paul.

hrm... it was working with the RI.
Is it possible to go back (just for testing) to 1.2_04 of the RI ?
and use using *.faces mapping ?

-Matthias





  Matthias Wessendorf wrote:
   Hi,
  
   On Thu, Feb 28, 2008 at 8:07 AM, Paul van Rossem [EMAIL PROTECTED] wrote:
  
   Hi,
If I use the tr:inputDate tag, clicking the calendar icon yields a
Page not found, page /__ADFv__.jsf.
Both in FF and IE. I'm using Trinidad 1.2.6. Do I need to include
  
  
   and MyFaces 1.2.x ?
  
  
  
anything special, apart from the 2 libraries (api en impl) or has it
something to do with my web.xml or faces-config.xml?
  
  
   I'd suggest to use this *mapping*:
   /faces/*
   and not:
   *.jsf
  
   -Matthias
  
  
I saw some additional configuration items in the examples
faces-config.xml. Is that required?
 component
  

 component-typeorg.apache.myfaces.trinidaddemo.DateField/component-type
  

 component-classorg.apache.myfaces.trinidaddemo.composite.DateField/component-class
 /component
Should I include something linke that in my faces-config.xml or what is
it for?
Any tips would be appreciated, regards, Paul.
  
  
  
  
  
  
  

  --
  Paul van Rossem, Van Rossem Timeware
  Tempellaan  18,  3721  VH  Bilthoven
  tel: 030-220.4006, fax: 030-220.3445
  www.timeware.nl, mobiel 06-5468.3405





-- 
Matthias Wessendorf

further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org


Re: [trinidad] Clicking tr:inputDate icon gives Page not found

2008-02-28 Thread Paul van Rossem

Hi Matthias,

Using the RI 1.2_04, 1.2_07-b03 or 1.2_08-b06 makes no difference. With 
either I get the following results:


/faces/* mapping: works OK
*.jsf  mapping: page not found
*.faces  mapping: no pop-up, no exception

Should I file a JIRA issue?

Regards and thanks, Paul.


Matthias Wessendorf wrote:

Hi,

On Thu, Feb 28, 2008 at 11:09 AM, Paul van Rossem [EMAIL PROTECTED] wrote:
  

Hi Matthias,

 Thanks a lot for your reply. It solved my problem.
 Indeed, if I use the /faces/* mapping instead *.jsf, it loads the
 correct page.

 Shouldn't it be independent of the mapping? Should I file a JIRA issue
 for this?
 I was using the jsf-1.2_07-b03 RI, not MyFaces.
 Regards, Paul.



hrm... it was working with the RI.
Is it possible to go back (just for testing) to 1.2_04 of the RI ?
and use using *.faces mapping ?

-Matthias
  

 Matthias Wessendorf wrote:
  Hi,
 
  On Thu, Feb 28, 2008 at 8:07 AM, Paul van Rossem [EMAIL PROTECTED] wrote:
 
  Hi,
   If I use the tr:inputDate tag, clicking the calendar icon yields a
   Page not found, page /__ADFv__.jsf.
   Both in FF and IE. I'm using Trinidad 1.2.6. Do I need to include
 
 
  and MyFaces 1.2.x ?
 
 
 
   anything special, apart from the 2 libraries (api en impl) or has it
   something to do with my web.xml or faces-config.xml?
 
 
  I'd suggest to use this *mapping*:
  /faces/*
  and not:
  *.jsf
 
  -Matthias
 
 
   I saw some additional configuration items in the examples
   faces-config.xml. Is that required?
component
 
   component-typeorg.apache.myfaces.trinidaddemo.DateField/component-type
 
   
component-classorg.apache.myfaces.trinidaddemo.composite.DateField/component-class
/component
   Should I include something linke that in my faces-config.xml or what is
   it for?
   Any tips would be appreciated, regards, Paul.



Re: [trinidad] Clicking tr:inputDate icon gives Page not found

2008-02-28 Thread Matthias Wessendorf
Hi,

can you try
1.2_04 ?

there was a huge overhaul in 1.2_07

thanks.
-Matthias

On Thu, Feb 28, 2008 at 1:17 PM, Paul van Rossem [EMAIL PROTECTED] wrote:
 Hi Matthias,

  Using the RI 1.2_04, 1.2_07-b03 or 1.2_08-b06 makes no difference. With
  either I get the following results:

  /faces/* mapping: works OK
  *.jsf  mapping: page not found
  *.faces  mapping: no pop-up, no exception

  Should I file a JIRA issue?

  Regards and thanks, Paul.




  Matthias Wessendorf wrote:
   Hi,
  
   On Thu, Feb 28, 2008 at 11:09 AM, Paul van Rossem [EMAIL PROTECTED] 
 wrote:
  
   Hi Matthias,
  
Thanks a lot for your reply. It solved my problem.
Indeed, if I use the /faces/* mapping instead *.jsf, it loads the
correct page.
  
Shouldn't it be independent of the mapping? Should I file a JIRA issue
for this?
I was using the jsf-1.2_07-b03 RI, not MyFaces.
Regards, Paul.
  
  
   hrm... it was working with the RI.
   Is it possible to go back (just for testing) to 1.2_04 of the RI ?
   and use using *.faces mapping ?
  
   -Matthias
  
Matthias Wessendorf wrote:
 Hi,

 On Thu, Feb 28, 2008 at 8:07 AM, Paul van Rossem [EMAIL PROTECTED] 
 wrote:

 Hi,
  If I use the tr:inputDate tag, clicking the calendar icon yields a
  Page not found, page /__ADFv__.jsf.
  Both in FF and IE. I'm using Trinidad 1.2.6. Do I need to include


 and MyFaces 1.2.x ?



  anything special, apart from the 2 libraries (api en impl) or has it
  something to do with my web.xml or faces-config.xml?


 I'd suggest to use this *mapping*:
 /faces/*
 and not:
 *.jsf

 -Matthias


  I saw some additional configuration items in the examples
  faces-config.xml. Is that required?
   component

  
 component-typeorg.apache.myfaces.trinidaddemo.DateField/component-type

  
 component-classorg.apache.myfaces.trinidaddemo.composite.DateField/component-class
   /component
  Should I include something linke that in my faces-config.xml or what 
 is
  it for?
  Any tips would be appreciated, regards, Paul.
  




-- 
Matthias Wessendorf

further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org


RE: (Trinidad) How to make an inputListOfValues and tr:inputDate field non-editable

2007-12-13 Thread sandeep gururaj
Hello All,

 

Does anybody have any suggestions on this?

 

~Sandeep

 



From: sandeep gururaj [mailto:[EMAIL PROTECTED] 
Sent: Friday, December 07, 2007 12:22 PM
To: MyFaces Discussion
Subject: (Trinidad) How to make an inputListOfValues and tr:inputDate
field non-editable

 

Hi All,

 

I have a requirement to make the text fileds associated with
tr:inputListOfValues and tr:inputDate components non-editable. Instead,
a user should be selecting an item or date and that should be displayed
in the text field.

 

Earliar, I was setting maximumLength=0 for both these components to
achieve this. I have recently moved to Trinidad 1.0.4 and MyFaces 1.1.5
and since then this attribute setting is ignored.

 

I would like to know if there are any alternatives for making the text
fields of tr:inputListOfValues and tr:inputDate components non-editable.

 

Thanks

~Sandeep



Re: (Trinidad) How to make an inputListOfValues and tr:inputDate field non-editable

2007-12-13 Thread Frank Nimphius




Hi,

this should work for Trinidad as well

http://thepeninsulasedge.com/frank_nimphius/2007/11/27/adf-faces-diabling-user-input-for-afselectinputdate/

Frank

sandeep gururaj wrote:

  
  
   Hello All,  
  
   Does anybody have any suggestions on this?  
  
   ~Sandeep  
  
  
  
  
 
   From:   sandeep gururaj
[mailto:[EMAIL PROTECTED]] 
  Sent: Friday, December 07, 2007
12:22 PM
  To: MyFaces Discussion
  Subject: ( Trinidad )
How to make an inputListOfValues and tr:inputDate field non-editable
  
  
  
   Hi All,  
  
   I have a requirement to make the text fileds associated
with
tr:inputListOfValues and tr:inputDate components non-editable. Instead,
a user
should be selecting an item or date and that should be displayed in the
text
field.  
  
   Earliar, I was setting maximumLength=0 for both these
components to
achieve this. I have recently moved to Trinidad 1.0.4 and MyFaces 1.1.5
and since then this attribute setting is ignored.  
  
   I would like to know if there are any alternatives for
making the text
fields of tr:inputListOfValues and tr:inputDate components
non-editable.  
  
   Thanks  
   ~Sandeep  
  


-- 


Frank Nimphius
Principal Product Manager
Application Development Tools
Oracle Corporation
mail: [EMAIL PROTECTED]
phone:+49 2058 782481




(Trinidad) How to make an inputListOfValues and tr:inputDate field non-editable

2007-12-06 Thread sandeep gururaj
Hi All,

 

I have a requirement to make the text fileds associated with
tr:inputListOfValues and tr:inputDate components non-editable. Instead,
a user should be selecting an item or date and that should be displayed
in the text field.

 

Earliar, I was setting maximumLength=0 for both these components to
achieve this. I have recently moved to Trinidad 1.0.4 and MyFaces 1.1.5
and since then this attribute setting is ignored.

 

I would like to know if there are any alternatives for making the text
fields of tr:inputListOfValues and tr:inputDate components non-editable.

 

Thanks

~Sandeep



[Trinidad] tr:inputDate showing a calendar as a popup

2007-10-31 Thread Renzo Tomaselli
Hi, subject says all. Is that possible to have it as a popup instead of 
a dialog ? Or if not - just to exclude it and use a separate (popup) 
calendar component ?

Thanks -- Renzo



[Trinidad] tr:inputDate PPR problem

2007-10-01 Thread Stephen Booth
Hello,

I'm trying to use the Trinidad inputDate component to fire a PPR event
and I'm getting an error whenever I use the date picker.

If I just enter the date in the textbox part, the PPR fires correctly
and the page updates as expected.

However, if I use the date picker, I get the following exception:

01-Oct-2007 15:25:39
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.PanelPartialRoo
tRenderer encodeAll
SEVERE: Error during partial-page rendering
java.lang.IndexOutOfBoundsException
at
com.evermind.io.ChunkedOutputStream.write(ChunkedOutputStream.java:64)
at
com.evermind.server.http.EvermindServletOutputStream.flushBuffer(Evermin
dServletOutputStream.java:88)
at
com.evermind.server.http.EvermindServletOutputStream.write(EvermindServl
etOutputStream.java:181)
at
com.evermind.server.http.ServletWriter.convertAndWriteChars(ServletWrite
r.java:284)
at
com.evermind.server.http.ServletWriter.flushBuffer(ServletWriter.java:30
9)
at
com.evermind.server.http.ServletWriter.getWrittenByteCount(ServletWriter
.java:195)
at
com.evermind.server.http.ServletWriter.checkWriteLength(ServletWriter.ja
va:421)
at
com.evermind.server.http.ServletWriter.write(ServletWriter.java:486)
at
org.apache.myfaces.trinidadinternal.config.xmlHttp.XmlOutput$2.write(Xml
Output.java:109)
at java.io.Writer.write(Writer.java:92)
at java.io.PrintWriter.write(PrintWriter.java:333)
at
org.apache.myfaces.trinidadinternal.io.HtmlResponseWriter.write(HtmlResp
onseWriter.java:347)
at
org.apache.myfaces.trinidadinternal.io.ResponseWriterDecorator.write(Res
ponseWriterDecorator.java:159)
at
org.apache.myfaces.trinidadinternal.renderkit.core.ppr.ScriptBufferingRe
sponseWriter.write(ScriptBufferingResponseWriter.java:158)
at
org.apache.myfaces.trinidadinternal.renderkit.core.ppr.PPRResponseWriter
.write(PPRResponseWriter.java:200)
at com.sun.facelets.StateWriter.write(StateWriter.java:108)
at
org.apache.myfaces.trinidadinternal.io.HtmlResponseWriter.writeAttribute
(HtmlResponseWriter.java:229)
at
org.apache.myfaces.trinidadinternal.io.ResponseWriterDecorator.writeAttr
ibute(ResponseWriterDecorator.java:110)

[rest snipped for brevity]

I'm using Trinidad 1.0.3 with MyFaces 1.1.5 and Facelets 1.1.12. My
servlet container is OC4J - hence the com.evermind stuff.

Any ideas gratefully received!

Thanks,

Stephen
 
 


NOTICE

This message and any files transmitted with it is intended for the addressee 
only and may contain information that is confidential or privileged. 
Unauthorised use is strictly prohibited. If you are not the addressee, you 
should not read, copy, disclose or otherwise use this message, except for the 
purpose of delivery to the addressee. 

Any views or opinions expressed within this e-mail are those of the author and 
do not necessarily represent those of Coventry University.


[Trinidad] tr:inputDate vs. servlet mapping

2007-09-26 Thread Björn Thalheim

Hi,

I'd like to use just a plain
tr:inputDate binding=#{backend.variable} /
in a form. Unfortunately, the popup-Window which opens when clicking at 
the calendar icon of the inputDate-tag returns me:

HTTP Status 404 -
´   typeStatus report
message
description The requested resource () is not available.
The corresponding log message is:
[#|2007-09-26T15:36:06.687+0200|SEVERE|sun-appserver9.1|org.apache.jasper.servlet.JspServlet|
_ThreadID=14;_ThreadName=httpSSLWorkerThread-8080-0;_RequestID=5b18f541-b475-44c0-a5e3-536a9369fde2;|
PWC6117:File bla\bla}bla\myModule\__ADFv__.jsp not found|#]

This is a problem of the servlet mapping in my web.xml. It at the moment 
looks like this:

  !-- Faces Servlet Mappings --
   servlet-mapping
servlet-namefaces/servlet-name
url-pattern*.jsf/url-pattern
  /servlet-mapping

  !-- I wouldn't mind getting rid of this entry. --
  servlet-mapping
servlet-namefaces/servlet-name
url-pattern/faces/*/url-pattern
  /servlet-mapping

  servlet-mapping
servlet-nameresources/servlet-name
url-pattern/adf/*/url-pattern
  /servlet-mapping

If I used only the second of these mappings, the inputDate would work, 
according to 
http://www.nabble.com/Trinidad-404-error:-requested-resource-(-tutoring-__ADFv__.jsp)-is-not-available-t4504436.html,

but this is not an option because then everything else wouldn't work.

Is there any way to get this running without the faces - /faces/* 
servlet mapping? And preferably, without hacking the trinidad taglibs? 
That would be really helpful.


Björn


Re: [Trinidad] tr:inputDate vs. servlet mapping

2007-09-26 Thread Matthias Wessendorf
Björn,

not 100% sure, but I think it works with myfaces 1.1.x
the issue is only present in the 1.2.x line of myfaces, at least here
i noticed the issue.

AFAIK it was present in an older RI (1.2.x) as well

On 9/26/07, Björn Thalheim [EMAIL PROTECTED] wrote:
 Hi,

 I'd like to use just a plain
 tr:inputDate binding=#{backend.variable} /
 in a form. Unfortunately, the popup-Window which opens when clicking at
 the calendar icon of the inputDate-tag returns me:
 HTTP Status 404 -
 ´   typeStatus report
 message
 description The requested resource () is not available.
 The corresponding log message is:
 [#|2007-09-26T15:36:06.687+0200|SEVERE|sun-appserver9.1|org.apache.jasper.servlet.JspServlet|
 _ThreadID=14;_ThreadName=httpSSLWorkerThread-8080-0;_RequestID=5b18f541-b475-44c0-a5e3-536a9369fde2;|
 PWC6117:File bla\bla}bla\myModule\__ADFv__.jsp not found|#]

 This is a problem of the servlet mapping in my web.xml. It at the moment
 looks like this:
!-- Faces Servlet Mappings --
 servlet-mapping
  servlet-namefaces/servlet-name
  url-pattern*.jsf/url-pattern
/servlet-mapping

!-- I wouldn't mind getting rid of this entry. --
servlet-mapping
  servlet-namefaces/servlet-name
  url-pattern/faces/*/url-pattern
/servlet-mapping

servlet-mapping
  servlet-nameresources/servlet-name
  url-pattern/adf/*/url-pattern
/servlet-mapping

 If I used only the second of these mappings, the inputDate would work,
 according to
 http://www.nabble.com/Trinidad-404-error:-requested-resource-(-tutoring-__ADFv__.jsp)-is-not-available-t4504436.html,
 but this is not an option because then everything else wouldn't work.

 Is there any way to get this running without the faces - /faces/*
 servlet mapping? And preferably, without hacking the trinidad taglibs?
 That would be really helpful.

 Björn



-- 
Matthias Wessendorf

further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org


Re: tr:inputDate

2007-09-21 Thread andymorton
Hi again.
I did some more investigation into this, and it seems that whenever you pick a 
date after the end of october, when daylight savings time switches, the date 
picker is ok.
All very confusing.
Should i be setting my default timezone to be GMT or a different one, like 
Europe/London?

Andy


- Original Message 
From: Adam Winer [EMAIL PROTECTED]
To: MyFaces Discussion users@myfaces.apache.org
Sent: Sunday, 16 September, 2007 7:57:24 PM
Subject: Re: tr:inputDate


I still strongly suspect this is a daylight savings time issue,
or at least a time zone issue, where one part of the system is
interpreting the date with one time zone, and another part
of the system is doing so with a different time zone.
Because of how java.util.Date is misdesigned, that means
that something entered as midnight of 16/09/2007 can
end up as 23:00 of 15/09/2007 when re-displayed.

-- Adam


On 9/16/07, Simon Lessard [EMAIL PROTECTED] wrote:
 I just checked demo files and we don't use a TimeZone setting in
 trinidad-config.xml, so my hunch wasn't good.


 On 9/16/07, Simon Lessard  [EMAIL PROTECTED] wrote:
  If that's the sole issue, then yes it should fix it.
 
 
 
  On 9/16/07, [EMAIL PROTECTED]  [EMAIL PROTECTED] wrote:
  
  
  
   Hi,
  
   Sounds like that could be it -seeing as it affects all instances.
   Not to sound too stupid, but i take it that this can be addressed by
 applying a timezone object to the inputDate through the use of the
 convertDateTime tag?
  
   Regards,
   Andrew
  
  
   - Original Message 
   From: Simon Lessard  [EMAIL PROTECTED]
   To: MyFaces Discussion users@myfaces.apache.org
  
   Sent: Sunday, 16 September, 2007 4:36:45 PM
   Subject: Re: tr:inputDate
  
   My hunch would be the timezone setting. I don't have access to SVN and
 source right now to check, but if the TimeZone use the 3-char format ( i.e.
 EST or PST), then daylight saving is ignored (and we're currently under
 daylight saving), resulting in hour hour lost. Since we set the date using
 midnight (0:00:00,000), losing 1 hours means going back one day.
  
   I plan to check out on that while fixing the first day of week issue to
 see if there's a way to prevent such issues.
  
  
   Regards,
  
   ~ Simon
  
  
   On 9/16/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
   
   
   
It also happens with the live demos, which is weird...
   
   
- Original Message 
From: Leonardo Uribe  [EMAIL PROTECTED]
To: MyFaces Discussion users@myfaces.apache.org
Sent: Sunday, 16 September, 2007 12:00:19 AM
Subject: Re: tr:inputDate
   
   
   
   



  and also if i click the first available date (in this case
 16/09/2007), it populates the field with 15/09/2007.

   
I remember this issue. Are you using java.sql.Date as the type for the
 property in the bean? I just changed it for java.util.Date and
all works well for me.
   
Regards
   
Leonardo Uribe
   
   
   
   
  
  
  
  
 
 



Re: tr:inputDate

2007-09-21 Thread Martin Marinschek
I didn't read very carefully - but this link might be relevant for the issue.

What I remember, we were initially using the system timezone for the
f:convertDateTime, but had to change over to using GMT cause else the
TCK would fail under certain circumstances.

http://mail-archives.apache.org/mod_mbox/myfaces-users/200509.mbox/[EMAIL 
PROTECTED]

regards,

Martin

On 9/21/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

 Hi again.
 I did some more investigation into this, and it seems that whenever you pick
 a date after the end of october, when daylight savings time switches, the
 date picker is ok.
 All very confusing.
 Should i be setting my default timezone to be GMT or a different one, like
 Europe/London?

 Andy


 - Original Message 
 From: Adam Winer [EMAIL PROTECTED]
 To: MyFaces Discussion users@myfaces.apache.org
 Sent: Sunday, 16 September, 2007 7:57:24 PM
 Subject: Re: tr:inputDate


 I still strongly suspect this is a daylight savings time issue,
 or at least a time zone issue, where one part of the system is
 interpreting the date with one time zone, and another part
 of the system is doing so with a different time zone.
 Because of how java.util.Date is misdesigned, that means
 that something entered as midnight of 16/09/2007 can
 end up as 23:00 of 15/09/2007 when re-displayed.

 -- Adam


 On 9/16/07, Simon Lessard [EMAIL PROTECTED] wrote:
  I just checked demo files and we don't use a TimeZone setting in
  trinidad-config.xml, so my hunch wasn't good.
 
 
  On 9/16/07, Simon Lessard  [EMAIL PROTECTED] wrote:
   If that's the sole issue, then yes it should fix it.
  
  
  
   On 9/16/07, [EMAIL PROTECTED]  [EMAIL PROTECTED]
 wrote:
   
   
   
Hi,
   
Sounds like that could be it -seeing as it affects all instances.
Not to sound too stupid, but i take it that this can be addressed by
  applying a timezone object to the inputDate through the use of the
  convertDateTime tag?
   
Regards,
Andrew
   
   
- Original Message 
From: Simon Lessard  [EMAIL PROTECTED]
To: MyFaces Discussion users@myfaces.apache.org
   
Sent: Sunday, 16 September, 2007 4:36:45 PM
Subject: Re: tr:inputDate
   
My hunch would be the timezone setting. I don't have access to SVN and
  source right now to check, but if the TimeZone use the 3-char format (
 i.e.
  EST or PST), then daylight saving is ignored (and we're currently under
  daylight saving), resulting in hour hour lost. Since we set the date using
  midnight (0:00:00,000), losing 1 hours means going back one day.
   
I plan to check out on that while fixing the first day of week issue
 to
  see if there's a way to prevent such issues.
   
   
Regards,
   
~ Simon
   
   
On 9/16/07, [EMAIL PROTECTED] [EMAIL PROTECTED]
 wrote:



 It also happens with the live demos, which is weird...


 - Original Message 
 From: Leonardo Uribe  [EMAIL PROTECTED]
 To: MyFaces Discussion users@myfaces.apache.org
 Sent: Sunday, 16 September, 2007 12:00:19 AM
 Subject: Re: tr:inputDate




 
 
 
   and also if i click the first available date (in this case
  16/09/2007), it populates the field with 15/09/2007.
 

 I remember this issue. Are you using java.sql.Date as the type for
 the
  property in the bean? I just changed it for java.util.Date and
 all works well for me.

 Regards

 Leonardo Uribe




   
   
   
   
  
  
 
 




-- 

http://www.irian.at

Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German

Professional Support for Apache MyFaces


Re: tr:inputDate

2007-09-21 Thread andymorton
Hi Martin,

The problem seems to be a fundamental bug in the way that daylight savings is 
calculated.
Whenever you select a day in the date picker, it seems to select the previous 
day.
This happens on the live demos, which is defaulted to GMT, as there is no 
default in trinidad-config.xml.

This then affects validation of the date.  If we take the example where the 
date should have a minimum of todays date.
The popup will not allow you to select it, as it calculates that the max day is 
tomorrow (strangely). I then set the minimum date as today -1.  This allows you 
to then select todays date in the popup, which then selects the previous day.
Eg today = 20/09/2007 (dd/MM/).  Minimum date = 19/09/2007, popup selected 
= '20/09/2007'
Value returned to text area = 19/09/2007l, which then fails validation - even 
though the minimum date is set.

It seems like a complex problem with the daylights savingwhich i think is 
coupled with the timezone.

Andrew



- Original Message 
From: Martin Marinschek [EMAIL PROTECTED]
To: MyFaces Discussion users@myfaces.apache.org
Sent: Friday, 21 September, 2007 1:34:40 PM
Subject: Re: tr:inputDate


I didn't read very carefully - but this link might be relevant for the issue.

What I remember, we were initially using the system timezone for the
f:convertDateTime, but had to change over to using GMT cause else the
TCK would fail under certain circumstances.

http://mail-archives.apache.org/mod_mbox/myfaces-users/200509.mbox/[EMAIL 
PROTECTED]

regards,

Martin

On 9/21/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

 Hi again.
 I did some more investigation into this, and it seems that whenever you pick
 a date after the end of october, when daylight savings time switches, the
 date picker is ok.
 All very confusing.
 Should i be setting my default timezone to be GMT or a different one, like
 Europe/London?

 Andy


 - Original Message 
 From: Adam Winer [EMAIL PROTECTED]
 To: MyFaces Discussion users@myfaces.apache.org
 Sent: Sunday, 16 September, 2007 7:57:24 PM
 Subject: Re: tr:inputDate


 I still strongly suspect this is a daylight savings time issue,
 or at least a time zone issue, where one part of the system is
 interpreting the date with one time zone, and another part
 of the system is doing so with a different time zone.
 Because of how java.util.Date is misdesigned, that means
 that something entered as midnight of 16/09/2007 can
 end up as 23:00 of 15/09/2007 when re-displayed.

 -- Adam


 On 9/16/07, Simon Lessard [EMAIL PROTECTED] wrote:
  I just checked demo files and we don't use a TimeZone setting in
  trinidad-config.xml, so my hunch wasn't good.
 
 
  On 9/16/07, Simon Lessard  [EMAIL PROTECTED] wrote:
   If that's the sole issue, then yes it should fix it.
  
  
  
   On 9/16/07, [EMAIL PROTECTED]  [EMAIL PROTECTED]
 wrote:
   
   
   
Hi,
   
Sounds like that could be it -seeing as it affects all instances.
Not to sound too stupid, but i take it that this can be addressed by
  applying a timezone object to the inputDate through the use of the
  convertDateTime tag?
   
Regards,
Andrew
   
   
- Original Message 
From: Simon Lessard  [EMAIL PROTECTED]
To: MyFaces Discussion users@myfaces.apache.org
   
Sent: Sunday, 16 September, 2007 4:36:45 PM
Subject: Re: tr:inputDate
   
My hunch would be the timezone setting. I don't have access to SVN and
  source right now to check, but if the TimeZone use the 3-char format (
 i.e.
  EST or PST), then daylight saving is ignored (and we're currently under
  daylight saving), resulting in hour hour lost. Since we set the date using
  midnight (0:00:00,000), losing 1 hours means going back one day.
   
I plan to check out on that while fixing the first day of week issue
 to
  see if there's a way to prevent such issues.
   
   
Regards,
   
~ Simon
   
   
On 9/16/07, [EMAIL PROTECTED] [EMAIL PROTECTED]
 wrote:



 It also happens with the live demos, which is weird...


 - Original Message 
 From: Leonardo Uribe  [EMAIL PROTECTED]
 To: MyFaces Discussion users@myfaces.apache.org
 Sent: Sunday, 16 September, 2007 12:00:19 AM
 Subject: Re: tr:inputDate




 
 
 
   and also if i click the first available date (in this case
  16/09/2007), it populates the field with 15/09/2007.
 

 I remember this issue. Are you using java.sql.Date as the type for
 the
  property in the bean? I just changed it for java.util.Date and
 all works well for me.

 Regards

 Leonardo Uribe




   
   
   
   
  
  
 
 




-- 

http://www.irian.at

Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German

Professional Support for Apache MyFaces

Re: tr:inputDate

2007-09-21 Thread andymorton
In another cruel twist of fate, the date popup seems to work from 1st November 
onwards.
That means that there is no way to select 31st October, as the 1st Nov selects 
the correct date, but selecting the 31st October will select the 30th October.


- Original Message 
From: Martin Marinschek [EMAIL PROTECTED]
To: MyFaces Discussion users@myfaces.apache.org
Sent: Friday, 21 September, 2007 1:34:40 PM
Subject: Re: tr:inputDate


I didn't read very carefully - but this link might be relevant for the issue.

What I remember, we were initially using the system timezone for the
f:convertDateTime, but had to change over to using GMT cause else the
TCK would fail under certain circumstances.

http://mail-archives.apache.org/mod_mbox/myfaces-users/200509.mbox/[EMAIL 
PROTECTED]

regards,

Martin

On 9/21/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

 Hi again.
 I did some more investigation into this, and it seems that whenever you pick
 a date after the end of october, when daylight savings time switches, the
 date picker is ok.
 All very confusing.
 Should i be setting my default timezone to be GMT or a different one, like
 Europe/London?

 Andy


 - Original Message 
 From: Adam Winer [EMAIL PROTECTED]
 To: MyFaces Discussion users@myfaces.apache.org
 Sent: Sunday, 16 September, 2007 7:57:24 PM
 Subject: Re: tr:inputDate


 I still strongly suspect this is a daylight savings time issue,
 or at least a time zone issue, where one part of the system is
 interpreting the date with one time zone, and another part
 of the system is doing so with a different time zone.
 Because of how java.util.Date is misdesigned, that means
 that something entered as midnight of 16/09/2007 can
 end up as 23:00 of 15/09/2007 when re-displayed.

 -- Adam


 On 9/16/07, Simon Lessard [EMAIL PROTECTED] wrote:
  I just checked demo files and we don't use a TimeZone setting in
  trinidad-config.xml, so my hunch wasn't good.
 
 
  On 9/16/07, Simon Lessard  [EMAIL PROTECTED] wrote:
   If that's the sole issue, then yes it should fix it.
  
  
  
   On 9/16/07, [EMAIL PROTECTED]  [EMAIL PROTECTED]
 wrote:
   
   
   
Hi,
   
Sounds like that could be it -seeing as it affects all instances.
Not to sound too stupid, but i take it that this can be addressed by
  applying a timezone object to the inputDate through the use of the
  convertDateTime tag?
   
Regards,
Andrew
   
   
- Original Message 
From: Simon Lessard  [EMAIL PROTECTED]
To: MyFaces Discussion users@myfaces.apache.org
   
Sent: Sunday, 16 September, 2007 4:36:45 PM
Subject: Re: tr:inputDate
   
My hunch would be the timezone setting. I don't have access to SVN and
  source right now to check, but if the TimeZone use the 3-char format (
 i.e.
  EST or PST), then daylight saving is ignored (and we're currently under
  daylight saving), resulting in hour hour lost. Since we set the date using
  midnight (0:00:00,000), losing 1 hours means going back one day.
   
I plan to check out on that while fixing the first day of week issue
 to
  see if there's a way to prevent such issues.
   
   
Regards,
   
~ Simon
   
   
On 9/16/07, [EMAIL PROTECTED] [EMAIL PROTECTED]
 wrote:



 It also happens with the live demos, which is weird...


 - Original Message 
 From: Leonardo Uribe  [EMAIL PROTECTED]
 To: MyFaces Discussion users@myfaces.apache.org
 Sent: Sunday, 16 September, 2007 12:00:19 AM
 Subject: Re: tr:inputDate




 
 
 
   and also if i click the first available date (in this case
  16/09/2007), it populates the field with 15/09/2007.
 

 I remember this issue. Are you using java.sql.Date as the type for
 the
  property in the bean? I just changed it for java.util.Date and
 all works well for me.

 Regards

 Leonardo Uribe




   
   
   
   
  
  
 
 




-- 

http://www.irian.at

Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German

Professional Support for Apache MyFaces

RE: [Trinidad] tr:inputDate problem

2007-09-17 Thread Stephen Booth
Simon,

Thanks very much for the response - it was exactly that problem. I've
set the time-zone in trinidad-config.xml to my timezone (GMT) and that
has fixed it.

Thanks very much for your help.

Stephen
 

-Original Message-
From: Simon Kitching [mailto:[EMAIL PROTECTED] 
Sent: 14 September 2007 14:07
To: MyFaces Discussion
Cc: sandeep gururaj
Subject: RE: [Trinidad] tr:inputDate problem

Are you sure the problem isn't this one?
  http://wiki.apache.org/myfaces/FAQ#Date


 sandeep gururaj [EMAIL PROTECTED] schrieb:
 Not sure why, I face the same problem if I use IE7. When on IE6, it
 works properly.
 
  
 
 ~Sandeep
 
  
 
  
 
 -Original Message-
 From: Stephen Booth [mailto:[EMAIL PROTECTED] 
 Sent: Friday, September 14, 2007 3:34 PM
 To: users@myfaces.apache.org
 Subject: [Trinidad] tr:inputDate problem
 
  
 
 Hello,
 
  
 
 I'm trying to use the Trinidad inputDate component and I'm getting an
 
 odd problem with the date picker.
 
  
 
 Whenever I select a date from it, it returns one day earlier than that
 
 chosen. This normally happens every time I use it but occasionally
only
 
 happens on the second and subsequent picks (i.e. the first returns the
 
 correct result).
 
  
 
 I'm relatively new to Trinidad so I'm just wondering whether anybody
has
 
 come across this issue before?
 
  
 
 For info, I'm using Trinidad 1.0.2 with MyFaces 1.1.5 and Facelets
 
 1.1.12.
 
 


NOTICE

This message and any files transmitted with it is intended for the addressee 
only and may contain information that is confidential or privileged. 
Unauthorised use is strictly prohibited. If you are not the addressee, you 
should not read, copy, disclose or otherwise use this message, except for the 
purpose of delivery to the addressee. 

Any views or opinions expressed within this e-mail are those of the author and 
do not necessarily represent those of Coventry University.


Re: [Trinidad] tr:inputDate problem

2007-09-17 Thread Simon Lessard
Ah yeah, GMT-5 or else is not daylight saving enabled either. Only the long
America/New York (or something like that) format works with it.


Regards,

~ Simon

On 9/17/07, Stephen Booth [EMAIL PROTECTED] wrote:

 Simon,

 Thanks very much for the response - it was exactly that problem. I've
 set the time-zone in trinidad-config.xml to my timezone (GMT) and that
 has fixed it.

 Thanks very much for your help.

 Stephen


 -Original Message-
 From: Simon Kitching [mailto:[EMAIL PROTECTED]
 Sent: 14 September 2007 14:07
 To: MyFaces Discussion
 Cc: sandeep gururaj
 Subject: RE: [Trinidad] tr:inputDate problem

 Are you sure the problem isn't this one?
   http://wiki.apache.org/myfaces/FAQ#Date


  sandeep gururaj [EMAIL PROTECTED] schrieb:
  Not sure why, I face the same problem if I use IE7. When on IE6, it
  works properly.
 
 
 
  ~Sandeep
 
 
 
 
 
  -Original Message-
  From: Stephen Booth [mailto:[EMAIL PROTECTED]
  Sent: Friday, September 14, 2007 3:34 PM
  To: users@myfaces.apache.org
  Subject: [Trinidad] tr:inputDate problem
 
 
 
  Hello,
 
 
 
  I'm trying to use the Trinidad inputDate component and I'm getting an
 
  odd problem with the date picker.
 
 
 
  Whenever I select a date from it, it returns one day earlier than that
 
  chosen. This normally happens every time I use it but occasionally
 only
 
  happens on the second and subsequent picks (i.e. the first returns the
 
  correct result).
 
 
 
  I'm relatively new to Trinidad so I'm just wondering whether anybody
 has
 
  come across this issue before?
 
 
 
  For info, I'm using Trinidad 1.0.2 with MyFaces 1.1.5 and Facelets
 
  1.1.12.


 

 NOTICE

 This message and any files transmitted with it is intended for the
 addressee only and may contain information that is confidential or
 privileged. Unauthorised use is strictly prohibited. If you are not the
 addressee, you should not read, copy, disclose or otherwise use this
 message, except for the purpose of delivery to the addressee.

 Any views or opinions expressed within this e-mail are those of the author
 and do not necessarily represent those of Coventry University.



Re: [Trinidad] tr:inputDate problem

2007-09-17 Thread Matthias Wessendorf
I think this comes from the JSF spec

If a timezone has been specified, it must be passed to the underlying
DateFormat instance. Otherwise the GMT timezone is used.

http://java.sun.com/javaee/javaserverfaces/1.2_MR1/docs/api/javax/faces/convert/DateTimeConverter.html

On 9/17/07, Simon Lessard [EMAIL PROTECTED] wrote:
 I think I found the culprit:

 org.apache.myfaces.trinidad.convert.DateTimeConverter._DEFAULT_TIME_ZONE
 = TimeZone.getTimeZone(GMT);

 I think we should change that to :

 org.apache.myfaces.trinidad.convert.DateTimeConverter._DEFAULT_TIME_ZONE
 = TimeZone.getDefault();

 That would set the default TimeZone to the server configured time zone.


 ~ Simon


 On 9/17/07, Simon Lessard [EMAIL PROTECTED] wrote:
  Ah yeah, GMT-5 or else is not daylight saving enabled either. Only the
 long America/New York (or something like that) format works with it.
 
 
  Regards,
 
  ~ Simon
 
 
 
  On 9/17/07, Stephen Booth [EMAIL PROTECTED] wrote:
   Simon,
  
   Thanks very much for the response - it was exactly that problem. I've
   set the time-zone in trinidad-config.xml to my timezone (GMT) and that
   has fixed it.
  
   Thanks very much for your help.
  
   Stephen
  
  
   -Original Message-
   From: Simon Kitching [mailto:[EMAIL PROTECTED] ]
   Sent: 14 September 2007 14:07
   To: MyFaces Discussion
   Cc: sandeep gururaj
   Subject: RE: [Trinidad] tr:inputDate problem
  
   Are you sure the problem isn't this one?
  http://wiki.apache.org/myfaces/FAQ#Date
  
  
    sandeep gururaj  [EMAIL PROTECTED] schrieb:
Not sure why, I face the same problem if I use IE7. When on IE6, it
works properly.
   
   
   
~Sandeep
   
   
   
   
   
-Original Message-
From: Stephen Booth [mailto: [EMAIL PROTECTED]
Sent: Friday, September 14, 2007 3:34 PM
To: users@myfaces.apache.org
Subject: [Trinidad] tr:inputDate problem
   
   
   
Hello,
   
   
   
I'm trying to use the Trinidad inputDate component and I'm getting an
   
odd problem with the date picker.
   
   
   
Whenever I select a date from it, it returns one day earlier than that
   
chosen. This normally happens every time I use it but occasionally
   only
   
happens on the second and subsequent picks (i.e. the first returns the
   
correct result).
   
   
   
I'm relatively new to Trinidad so I'm just wondering whether anybody
   has
   
come across this issue before?
   
   
   
For info, I'm using Trinidad 1.0.2 with MyFaces 1.1.5 and Facelets
   
1.1.12.
  
  
  
 
  
   NOTICE
  
   This message and any files transmitted with it is intended for the
 addressee only and may contain information that is confidential or
 privileged. Unauthorised use is strictly prohibited. If you are not the
 addressee, you should not read, copy, disclose or otherwise use this
 message, except for the purpose of delivery to the addressee.
  
   Any views or opinions expressed within this e-mail are those of the
 author and do not necessarily represent those of Coventry University.
  
 
 




-- 
Matthias Wessendorf

further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org


Re: [Trinidad] tr:inputDate problem

2007-09-17 Thread Simon Lessard
I think I found the culprit:

org.apache.myfaces.trinidad.convert.DateTimeConverter._DEFAULT_TIME_ZONE =
TimeZone.getTimeZone(GMT);

I think we should change that to :

org.apache.myfaces.trinidad.convert.DateTimeConverter._DEFAULT_TIME_ZONE =
TimeZone.getDefault();

That would set the default TimeZone to the server configured time zone.


~ Simon

On 9/17/07, Simon Lessard [EMAIL PROTECTED] wrote:

 Ah yeah, GMT-5 or else is not daylight saving enabled either. Only the
 long America/New York (or something like that) format works with it.


 Regards,

 ~ Simon

 On 9/17/07, Stephen Booth [EMAIL PROTECTED] wrote:
 
  Simon,
 
  Thanks very much for the response - it was exactly that problem. I've
  set the time-zone in trinidad-config.xml to my timezone (GMT) and that
  has fixed it.
 
  Thanks very much for your help.
 
  Stephen
 
 
  -Original Message-
  From: Simon Kitching [mailto:[EMAIL PROTECTED]
  Sent: 14 September 2007 14:07
  To: MyFaces Discussion
  Cc: sandeep gururaj
  Subject: RE: [Trinidad] tr:inputDate problem
 
  Are you sure the problem isn't this one?
http://wiki.apache.org/myfaces/FAQ#Date
 
 
   sandeep gururaj  [EMAIL PROTECTED] schrieb:
   Not sure why, I face the same problem if I use IE7. When on IE6, it
   works properly.
  
  
  
   ~Sandeep
  
  
  
  
  
   -Original Message-
   From: Stephen Booth [mailto:[EMAIL PROTECTED]
   Sent: Friday, September 14, 2007 3:34 PM
   To: users@myfaces.apache.org
   Subject: [Trinidad] tr:inputDate problem
  
  
  
   Hello,
  
  
  
   I'm trying to use the Trinidad inputDate component and I'm getting an
  
   odd problem with the date picker.
  
  
  
   Whenever I select a date from it, it returns one day earlier than that
  
   chosen. This normally happens every time I use it but occasionally
  only
  
   happens on the second and subsequent picks (i.e. the first returns the
  
   correct result).
  
  
  
   I'm relatively new to Trinidad so I'm just wondering whether anybody
  has
  
   come across this issue before?
  
  
  
   For info, I'm using Trinidad 1.0.2 with MyFaces 1.1.5 and Facelets
  
   1.1.12.
 
 
  
 
  NOTICE
 
  This message and any files transmitted with it is intended for the
  addressee only and may contain information that is confidential or
  privileged. Unauthorised use is strictly prohibited. If you are not the
  addressee, you should not read, copy, disclose or otherwise use this
  message, except for the purpose of delivery to the addressee.
 
  Any views or opinions expressed within this e-mail are those of the
  author and do not necessarily represent those of Coventry University.
 




Re: [Trinidad] tr:inputDate problem

2007-09-17 Thread Simon Lessard
Fishy, but in any case, I think the problem occurs only if one part of the
code use a TimeZone while another uses a different one. I guess we'll have
to run through the code and find all TimeZone usages to make sure they're
consistently using the same value, because it must not be the case
currently.

~ Simon

On 9/17/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:

 I think this comes from the JSF spec

 If a timezone has been specified, it must be passed to the underlying
 DateFormat instance. Otherwise the GMT timezone is used.


 http://java.sun.com/javaee/javaserverfaces/1.2_MR1/docs/api/javax/faces/convert/DateTimeConverter.html

 On 9/17/07, Simon Lessard [EMAIL PROTECTED] wrote:
  I think I found the culprit:
 
  org.apache.myfaces.trinidad.convert.DateTimeConverter._DEFAULT_TIME_ZONE
  = TimeZone.getTimeZone(GMT);
 
  I think we should change that to :
 
  org.apache.myfaces.trinidad.convert.DateTimeConverter._DEFAULT_TIME_ZONE
  = TimeZone.getDefault();
 
  That would set the default TimeZone to the server configured time zone.
 
 
  ~ Simon
 
 
  On 9/17/07, Simon Lessard [EMAIL PROTECTED] wrote:
   Ah yeah, GMT-5 or else is not daylight saving enabled either. Only the
  long America/New York (or something like that) format works with it.
  
  
   Regards,
  
   ~ Simon
  
  
  
   On 9/17/07, Stephen Booth [EMAIL PROTECTED] wrote:
Simon,
   
Thanks very much for the response - it was exactly that problem.
 I've
set the time-zone in trinidad-config.xml to my timezone (GMT) and
 that
has fixed it.
   
Thanks very much for your help.
   
Stephen
   
   
-Original Message-
From: Simon Kitching [mailto:[EMAIL PROTECTED] ]
Sent: 14 September 2007 14:07
To: MyFaces Discussion
Cc: sandeep gururaj
Subject: RE: [Trinidad] tr:inputDate problem
   
Are you sure the problem isn't this one?
   http://wiki.apache.org/myfaces/FAQ#Date
   
   
 sandeep gururaj  [EMAIL PROTECTED] schrieb:
 Not sure why, I face the same problem if I use IE7. When on IE6,
 it
 works properly.



 ~Sandeep





 -Original Message-
 From: Stephen Booth [mailto: [EMAIL PROTECTED]
 Sent: Friday, September 14, 2007 3:34 PM
 To: users@myfaces.apache.org
 Subject: [Trinidad] tr:inputDate problem



 Hello,



 I'm trying to use the Trinidad inputDate component and I'm getting
 an

 odd problem with the date picker.



 Whenever I select a date from it, it returns one day earlier than
 that

 chosen. This normally happens every time I use it but occasionally
only

 happens on the second and subsequent picks (i.e. the first returns
 the

 correct result).



 I'm relatively new to Trinidad so I'm just wondering whether
 anybody
has

 come across this issue before?



 For info, I'm using Trinidad 1.0.2 with MyFaces 1.1.5 and Facelets

 1.1.12.
   
   
   
  
   
NOTICE
   
This message and any files transmitted with it is intended for the
  addressee only and may contain information that is confidential or
  privileged. Unauthorised use is strictly prohibited. If you are not the
  addressee, you should not read, copy, disclose or otherwise use this
  message, except for the purpose of delivery to the addressee.
   
Any views or opinions expressed within this e-mail are those of the
  author and do not necessarily represent those of Coventry University.
   
  
  
 
 


 --
 Matthias Wessendorf

 further stuff:
 blog: http://matthiaswessendorf.wordpress.com/
 mail: matzew-at-apache-dot-org



Re: [Trinidad] tr:inputDate problem

2007-09-17 Thread Simon Lessard
Another possible issue is private static final long _MILLIS_IN_DAY = 1000L *
60 * 60 * 24; found in ChooseDateRenderer. All dates ms are calculated
relative to that offset applied from a base date (so day5 is day1 +
4*_MILLIS_IN_DAY). While looking at a possible patch for the first day of
week issue, I took a note to compare the use of that offset compared with
Calendar to make sure the ms values match, because it looked potentially
dangerous when daylight saving is active, especially at hour change dates
when the amount of ms in the days varies by ± 3,600,000ms. Since the issue
seems to happen mainly with the calendar popup, that might be the true
culprit.


~ Simon


On 9/17/07, Simon Lessard [EMAIL PROTECTED] wrote:

 Fishy, but in any case, I think the problem occurs only if one part of the
 code use a TimeZone while another uses a different one. I guess we'll have
 to run through the code and find all TimeZone usages to make sure they're
 consistently using the same value, because it must not be the case
 currently.

 ~ Simon

 On 9/17/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
 
  I think this comes from the JSF spec
 
  If a timezone has been specified, it must be passed to the underlying
  DateFormat instance. Otherwise the GMT timezone is used.
 
 
  http://java.sun.com/javaee/javaserverfaces/1.2_MR1/docs/api/javax/faces/convert/DateTimeConverter.html
 
  On 9/17/07, Simon Lessard [EMAIL PROTECTED] wrote:
   I think I found the culprit:
  
  
  org.apache.myfaces.trinidad.convert.DateTimeConverter._DEFAULT_TIME_ZONE
   = TimeZone.getTimeZone(GMT);
  
   I think we should change that to :
  
  
  org.apache.myfaces.trinidad.convert.DateTimeConverter._DEFAULT_TIME_ZONE
   = TimeZone.getDefault();
  
   That would set the default TimeZone to the server configured time
  zone.
  
  
   ~ Simon
  
  
   On 9/17/07, Simon Lessard [EMAIL PROTECTED] wrote:
Ah yeah, GMT-5 or else is not daylight saving enabled either. Only
  the
   long America/New York (or something like that) format works with it.
   
   
Regards,
   
~ Simon
   
   
   
On 9/17/07, Stephen Booth  [EMAIL PROTECTED] wrote:
 Simon,

 Thanks very much for the response - it was exactly that problem.
  I've
 set the time-zone in trinidad-config.xml to my timezone (GMT) and
  that
 has fixed it.

 Thanks very much for your help.

 Stephen


 -Original Message-
 From: Simon Kitching [mailto:[EMAIL PROTECTED] ]
 Sent: 14 September 2007 14:07
 To: MyFaces Discussion
 Cc: sandeep gururaj
 Subject: RE: [Trinidad] tr:inputDate problem

 Are you sure the problem isn't this one?
 http://wiki.apache.org/myfaces/FAQ#Date


  sandeep gururaj  [EMAIL PROTECTED] schrieb:
  Not sure why, I face the same problem if I use IE7. When on IE6,
  it
  works properly.
 
 
 
  ~Sandeep
 
 
 
 
 
  -Original Message-
  From: Stephen Booth [mailto: [EMAIL PROTECTED]
  Sent: Friday, September 14, 2007 3:34 PM
  To: users@myfaces.apache.org
  Subject: [Trinidad] tr:inputDate problem
 
 
 
  Hello,
 
 
 
  I'm trying to use the Trinidad inputDate component and I'm
  getting an
 
  odd problem with the date picker.
 
 
 
  Whenever I select a date from it, it returns one day earlier
  than that
 
  chosen. This normally happens every time I use it but
  occasionally
 only
 
  happens on the second and subsequent picks ( i.e. the first
  returns the
 
  correct result).
 
 
 
  I'm relatively new to Trinidad so I'm just wondering whether
  anybody
 has
 
  come across this issue before?
 
 
 
  For info, I'm using Trinidad 1.0.2 with MyFaces 1.1.5 and
  Facelets
 
  1.1.12.



   

 NOTICE

 This message and any files transmitted with it is intended for the
   addressee only and may contain information that is confidential or
   privileged. Unauthorised use is strictly prohibited. If you are not
  the
   addressee, you should not read, copy, disclose or otherwise use this
   message, except for the purpose of delivery to the addressee.

 Any views or opinions expressed within this e-mail are those of
  the
   author and do not necessarily represent those of Coventry University.

   
   
  
  
 
 
  --
  Matthias Wessendorf
 
  further stuff:
  blog: http://matthiaswessendorf.wordpress.com/
  mail: matzew-at-apache-dot-org
 




Re: tr:inputDate

2007-09-16 Thread andymorton
It also happens with the live demos, which is weird...


- Original Message 
From: Leonardo Uribe [EMAIL PROTECTED]
To: MyFaces Discussion users@myfaces.apache.org
Sent: Sunday, 16 September, 2007 12:00:19 AM
Subject: Re: tr:inputDate



 and also if i click the first available date (in this case 16/09/2007), it 
populates the field with 15/09/2007.
 

I remember this issue. Are you using java.sql.Date as the type for the property 
in the bean? I just changed it for java.util.Date and
all works well for me.

Regards 

Leonardo Uribe

Re: tr:inputDate on live demo

2007-09-16 Thread andymorton
Hi,

I have done some more investigation with my problem on the live demo, and have 
tested with several browsers.
It seems that whenever you have an empty field for the inputDate, and select 
the date popup, it sets it correctly.
However, if a date is there, and the popup is selected, any date chosen in the 
popup date will be disregarded and the day before taken as the selected value.

Have i missed something really simple here? This seems like quite a fundamental 
problem.

Regards,
Andrew


- Original Message 
From: Leonardo Uribe [EMAIL PROTECTED]
To: MyFaces Discussion users@myfaces.apache.org
Sent: Sunday, 16 September, 2007 12:00:19 AM
Subject: Re: tr:inputDate



 and also if i click the first available date (in this case 16/09/2007), it 
populates the field with 15/09/2007.
 

I remember this issue. Are you using java.sql.Date as the type for the property 
in the bean? I just changed it for java.util.Date and
all works well for me.

Regards 

Leonardo Uribe

Re: tr:inputDate

2007-09-16 Thread Simon Lessard
My hunch would be the timezone setting. I don't have access to SVN and
source right now to check, but if the TimeZone use the 3-char format (i.e.
EST or PST), then daylight saving is ignored (and we're currently under
daylight saving), resulting in hour hour lost. Since we set the date using
midnight (0:00:00,000), losing 1 hours means going back one day.

I plan to check out on that while fixing the first day of week issue to see
if there's a way to prevent such issues.


Regards,

~ Simon

On 9/16/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

 It also happens with the live demos, which is weird...

 - Original Message 
 From: Leonardo Uribe [EMAIL PROTECTED]
 To: MyFaces Discussion users@myfaces.apache.org
 Sent: Sunday, 16 September, 2007 12:00:19 AM
 Subject: Re: tr:inputDate


and also if i click the first available date (in this case 16/09/2007),
  it populates the field with 15/09/2007.
 
 

 I remember this issue. Are you using java.sql.Date as the type for the
 property in the bean? I just changed it for java.util.Date and
 all works well for me.

 Regards

 Leonardo Uribe






Re: tr:inputDate

2007-09-16 Thread andymorton
Hi,

Sounds like that could be it -seeing as it affects all instances.
Not to sound too stupid, but i take it that this can be addressed by applying a 
timezone object to the inputDate through the use of the convertDateTime tag?

Regards,
Andrew


- Original Message 
From: Simon Lessard [EMAIL PROTECTED]
To: MyFaces Discussion users@myfaces.apache.org
Sent: Sunday, 16 September, 2007 4:36:45 PM
Subject: Re: tr:inputDate

My hunch would be the timezone setting. I don't have access to SVN and source 
right now to check, but if the TimeZone use the 3-char format (i.e. EST or 
PST), then daylight saving is ignored (and we're currently under daylight 
saving), resulting in hour hour lost. Since we set the date using midnight 
(0:00:00,000), losing 1 hours means going back one day. 

I plan to check out on that while fixing the first day of week issue to see if 
there's a way to prevent such issues.


Regards,

~ Simon


On 9/16/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
It also happens with the live demos, which is weird... 


- Original Message 
From: Leonardo Uribe  [EMAIL PROTECTED]
To: MyFaces Discussion users@myfaces.apache.org
Sent: Sunday, 16 September, 2007 12:00:19 AM 
Subject: Re: tr:inputDate



 and also if i click the first available date (in this case 16/09/2007), it 
populates the field with 15/09/2007.
 

I remember this issue. Are you using java.sql.Date as the type for the property 
in the bean? I just changed it for java.util.Date and
all works well for me.

Regards 

Leonardo Uribe

Re: tr:inputDate

2007-09-16 Thread Simon Lessard
If that's the sole issue, then yes it should fix it.

On 9/16/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

 Hi,

 Sounds like that could be it -seeing as it affects all instances.
 Not to sound too stupid, but i take it that this can be addressed by
 applying a timezone object to the inputDate through the use of the
 convertDateTime tag?

 Regards,
 Andrew

 - Original Message 
 From: Simon Lessard [EMAIL PROTECTED]
 To: MyFaces Discussion users@myfaces.apache.org
 Sent: Sunday, 16 September, 2007 4:36:45 PM
 Subject: Re: tr:inputDate

 My hunch would be the timezone setting. I don't have access to SVN and
 source right now to check, but if the TimeZone use the 3-char format (i.e.
 EST or PST), then daylight saving is ignored (and we're currently under
 daylight saving), resulting in hour hour lost. Since we set the date using
 midnight (0:00:00,000), losing 1 hours means going back one day.

 I plan to check out on that while fixing the first day of week issue to
 see if there's a way to prevent such issues.


 Regards,

 ~ Simon

 On 9/16/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
 
   It also happens with the live demos, which is weird...
 
  - Original Message 
  From: Leonardo Uribe  [EMAIL PROTECTED]
  To: MyFaces Discussion users@myfaces.apache.org
  Sent: Sunday, 16 September, 2007 12:00:19 AM
  Subject: Re: tr:inputDate
 
 
 and also if i click the first available date (in this case
   16/09/2007), it populates the field with 15/09/2007.
  
  
 
  I remember this issue. Are you using java.sql.Date as the type for the
  property in the bean? I just changed it for java.util.Date and
  all works well for me.
 
  Regards
 
  Leonardo Uribe
 
 
 
 




Re: tr:inputDate

2007-09-16 Thread Simon Lessard
I just checked demo files and we don't use a TimeZone setting in
trinidad-config.xml, so my hunch wasn't good.

On 9/16/07, Simon Lessard [EMAIL PROTECTED] wrote:

 If that's the sole issue, then yes it should fix it.

 On 9/16/07, [EMAIL PROTECTED]  [EMAIL PROTECTED] wrote:
 
  Hi,
 
  Sounds like that could be it -seeing as it affects all instances.
  Not to sound too stupid, but i take it that this can be addressed by
  applying a timezone object to the inputDate through the use of the
  convertDateTime tag?
 
  Regards,
  Andrew
 
  - Original Message 
  From: Simon Lessard  [EMAIL PROTECTED]
  To: MyFaces Discussion users@myfaces.apache.org
  Sent: Sunday, 16 September, 2007 4:36:45 PM
  Subject: Re: tr:inputDate
 
  My hunch would be the timezone setting. I don't have access to SVN and
  source right now to check, but if the TimeZone use the 3-char format (
  i.e. EST or PST), then daylight saving is ignored (and we're currently
  under daylight saving), resulting in hour hour lost. Since we set the date
  using midnight (0:00:00,000), losing 1 hours means going back one day.
 
  I plan to check out on that while fixing the first day of week issue to
  see if there's a way to prevent such issues.
 
 
  Regards,
 
  ~ Simon
 
  On 9/16/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
  
It also happens with the live demos, which is weird...
  
   - Original Message 
   From: Leonardo Uribe  [EMAIL PROTECTED]
   To: MyFaces Discussion users@myfaces.apache.org
   Sent: Sunday, 16 September, 2007 12:00:19 AM
   Subject: Re: tr:inputDate
  
  
  and also if i click the first available date (in this case
16/09/2007), it populates the field with 15/09/2007.
   
   
  
   I remember this issue. Are you using java.sql.Date as the type for the
   property in the bean? I just changed it for java.util.Date and
   all works well for me.
  
   Regards
  
   Leonardo Uribe
  
  
  
  
 
 



Re: tr:inputDate

2007-09-16 Thread Adam Winer
I still strongly suspect this is a daylight savings time issue,
or at least a time zone issue, where one part of the system is
interpreting the date with one time zone, and another part
of the system is doing so with a different time zone.
Because of how java.util.Date is misdesigned, that means
that something entered as midnight of 16/09/2007 can
end up as 23:00 of 15/09/2007 when re-displayed.

-- Adam


On 9/16/07, Simon Lessard [EMAIL PROTECTED] wrote:
 I just checked demo files and we don't use a TimeZone setting in
 trinidad-config.xml, so my hunch wasn't good.


 On 9/16/07, Simon Lessard  [EMAIL PROTECTED] wrote:
  If that's the sole issue, then yes it should fix it.
 
 
 
  On 9/16/07, [EMAIL PROTECTED]  [EMAIL PROTECTED] wrote:
  
  
  
   Hi,
  
   Sounds like that could be it -seeing as it affects all instances.
   Not to sound too stupid, but i take it that this can be addressed by
 applying a timezone object to the inputDate through the use of the
 convertDateTime tag?
  
   Regards,
   Andrew
  
  
   - Original Message 
   From: Simon Lessard  [EMAIL PROTECTED]
   To: MyFaces Discussion users@myfaces.apache.org
  
   Sent: Sunday, 16 September, 2007 4:36:45 PM
   Subject: Re: tr:inputDate
  
   My hunch would be the timezone setting. I don't have access to SVN and
 source right now to check, but if the TimeZone use the 3-char format ( i.e.
 EST or PST), then daylight saving is ignored (and we're currently under
 daylight saving), resulting in hour hour lost. Since we set the date using
 midnight (0:00:00,000), losing 1 hours means going back one day.
  
   I plan to check out on that while fixing the first day of week issue to
 see if there's a way to prevent such issues.
  
  
   Regards,
  
   ~ Simon
  
  
   On 9/16/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
   
   
   
It also happens with the live demos, which is weird...
   
   
- Original Message 
From: Leonardo Uribe  [EMAIL PROTECTED]
To: MyFaces Discussion users@myfaces.apache.org
Sent: Sunday, 16 September, 2007 12:00:19 AM
Subject: Re: tr:inputDate
   
   
   
   



  and also if i click the first available date (in this case
 16/09/2007), it populates the field with 15/09/2007.

   
I remember this issue. Are you using java.sql.Date as the type for the
 property in the bean? I just changed it for java.util.Date and
all works well for me.
   
Regards
   
Leonardo Uribe
   
   
   
   
  
  
  
  
 
 




tr:inputDate

2007-09-15 Thread andymorton
Hi,

I am using the trinidad component tr:inputDate, and dont know if im doing 
something completely stupid.
Whenever i click on the popup, it appears ok.  
I also have a tr:validateDateRange element with it, which takes the limit from 
a managed bean through some el.
If, for example, i set the minimum date to be 15/09/2007 (dd/MM/) in the 
managed bean, whenever i click on the date picker icon, it brings up the popup 
ok, but i am not able to select the minimum date, and also if i click the first 
available date (in this case 16/09/2007), it populates the field with 
15/09/2007.

As you can imagine its been a source of frustration.  
Any ideas - ive been googling for hours with little success

Regards,
Andy

Re: tr:inputDate

2007-09-15 Thread Leonardo Uribe
  and also if i click the first available date (in this case 16/09/2007),
 it populates the field with 15/09/2007.



I remember this issue. Are you using java.sql.Date as the type for the
property in the bean? I just changed it for java.util.Date and
all works well for me.

Regards

Leonardo Uribe


Re: tr:inputDate

2007-09-15 Thread andymorton
just double checked there- i am using java.util.Date...

Regards,
Andy


- Original Message 
From: Leonardo Uribe [EMAIL PROTECTED]
To: MyFaces Discussion users@myfaces.apache.org
Sent: Sunday, 16 September, 2007 12:00:19 AM
Subject: Re: tr:inputDate



 and also if i click the first available date (in this case 16/09/2007), it 
populates the field with 15/09/2007.
 

I remember this issue. Are you using java.sql.Date as the type for the property 
in the bean? I just changed it for java.util.Date and
all works well for me.

Regards 

Leonardo Uribe

[Trinidad] tr:inputDate problem

2007-09-14 Thread Stephen Booth
Hello,

I'm trying to use the Trinidad inputDate component and I'm getting an
odd problem with the date picker.

Whenever I select a date from it, it returns one day earlier than that
chosen. This normally happens every time I use it but occasionally only
happens on the second and subsequent picks (i.e. the first returns the
correct result).

I'm relatively new to Trinidad so I'm just wondering whether anybody has
come across this issue before?

For info, I'm using Trinidad 1.0.2 with MyFaces 1.1.5 and Facelets
1.1.12.

Thanks,

Stephen
 
 


NOTICE

This message and any files transmitted with it is intended for the addressee 
only and may contain information that is confidential or privileged. 
Unauthorised use is strictly prohibited. If you are not the addressee, you 
should not read, copy, disclose or otherwise use this message, except for the 
purpose of delivery to the addressee. 

Any views or opinions expressed within this e-mail are those of the author and 
do not necessarily represent those of Coventry University.


RE: [Trinidad] tr:inputDate problem

2007-09-14 Thread sandeep gururaj
Not sure why, I face the same problem if I use IE7. When on IE6, it
works properly.

 

~Sandeep

 

 

-Original Message-
From: Stephen Booth [mailto:[EMAIL PROTECTED] 
Sent: Friday, September 14, 2007 3:34 PM
To: users@myfaces.apache.org
Subject: [Trinidad] tr:inputDate problem

 

Hello,

 

I'm trying to use the Trinidad inputDate component and I'm getting an

odd problem with the date picker.

 

Whenever I select a date from it, it returns one day earlier than that

chosen. This normally happens every time I use it but occasionally only

happens on the second and subsequent picks (i.e. the first returns the

correct result).

 

I'm relatively new to Trinidad so I'm just wondering whether anybody has

come across this issue before?

 

For info, I'm using Trinidad 1.0.2 with MyFaces 1.1.5 and Facelets

1.1.12.

 

Thanks,

 

Stephen

 

 



 

NOTICE

 

This message and any files transmitted with it is intended for the
addressee only and may contain information that is confidential or
privileged. Unauthorised use is strictly prohibited. If you are not the
addressee, you should not read, copy, disclose or otherwise use this
message, except for the purpose of delivery to the addressee. 

 

Any views or opinions expressed within this e-mail are those of the
author and do not necessarily represent those of Coventry University.



RE: [Trinidad] tr:inputDate problem

2007-09-14 Thread Simon Kitching
Are you sure the problem isn't this one?
  http://wiki.apache.org/myfaces/FAQ#Date


 sandeep gururaj [EMAIL PROTECTED] schrieb:
 Not sure why, I face the same problem if I use IE7. When on IE6, it
 works properly.
 
  
 
 ~Sandeep
 
  
 
  
 
 -Original Message-
 From: Stephen Booth [mailto:[EMAIL PROTECTED] 
 Sent: Friday, September 14, 2007 3:34 PM
 To: users@myfaces.apache.org
 Subject: [Trinidad] tr:inputDate problem
 
  
 
 Hello,
 
  
 
 I'm trying to use the Trinidad inputDate component and I'm getting an
 
 odd problem with the date picker.
 
  
 
 Whenever I select a date from it, it returns one day earlier than that
 
 chosen. This normally happens every time I use it but occasionally only
 
 happens on the second and subsequent picks (i.e. the first returns the
 
 correct result).
 
  
 
 I'm relatively new to Trinidad so I'm just wondering whether anybody has
 
 come across this issue before?
 
  
 
 For info, I'm using Trinidad 1.0.2 with MyFaces 1.1.5 and Facelets
 
 1.1.12.


Re: tr:inputDate and hour/minute oddity

2007-06-13 Thread Chris Hane



Adam Winer wrote:

On 6/12/07, Chris Hane [EMAIL PROTECTED] wrote:
When I select add an tr:inputDate tag with a converter that displays 
the

hours/minutes also, the hours are not correct.  For example, in the demo
inputDate.jspx, change the last inputDate to be:

tr:inputDate id=mdf5 value=2004/09/06 label=attached 
converter

   tr:convertDateTime secondaryPattern=d/M/ hh:mm
   pattern=/M/d hh:mm /
/tr:inputDate


I added the hh:mm to the converter.  When you select a day in the 
current

month, the time will default to the current time.  Select another day in
the current month and the time stays the same.

Select a day in the past (say January) and the time increases by 1 hour.
Select another day in January and the time increases again by 1 hour.

Is this a known issue?  Are there any workarounds?

Is there something else I should be looking at for this issue?

I'm running everything on my development box:
Windows XP
Jboss 4.0.x
Firefox 2.x
Java 1.5.x
MyFaces 1.latest
Facelets 1.11

My local machine timezone is EST.


Actually, I suspect your timezone is EDT, and that this
is a daylight savings time issue.

-- Adam



Adam - thanks for the response.  You were right, it was EDT.

The whole date thing has me a little perplexed.

I setup the following:
  - computer time (GMT - made sure DST was off)
  - added GMT to inputDate

Voila, no time change.  My next step is to setup the server/pages this way 
and test on a client that is not GMT.  Will the time be changed since the 
client has a different timezone?


I've done a little google searching; but feel I'm missing the keywords I 
should be looking for.  Suggestions on what I can read to understand 
dates/timezone better and how they impact the various JSF/java components?


Thanks,
Chris


Re: tr:inputDate and hour/minute oddity

2007-06-13 Thread Adam Winer

The issue here (I'm guessing) is that the field is goingin and out of
daylight savings time, and some bit
of code isn't accounting for that.  That's why when
you pick a date back in January, you get a bump
in time - because January is really one hour different
from June.

-- Adam


On 6/13/07, Chris Hane [EMAIL PROTECTED] wrote:




Adam Winer wrote:
 On 6/12/07, Chris Hane [EMAIL PROTECTED] wrote:
 When I select add an tr:inputDate tag with a converter that displays
 the
 hours/minutes also, the hours are not correct.  For example, in the
demo
 inputDate.jspx, change the last inputDate to be:

 tr:inputDate id=mdf5 value=2004/09/06 label=attached
 converter
tr:convertDateTime secondaryPattern=d/M/ hh:mm
pattern=/M/d hh:mm /
 /tr:inputDate


 I added the hh:mm to the converter.  When you select a day in the
 current
 month, the time will default to the current time.  Select another day
in
 the current month and the time stays the same.

 Select a day in the past (say January) and the time increases by 1
hour.
 Select another day in January and the time increases again by 1 hour.

 Is this a known issue?  Are there any workarounds?

 Is there something else I should be looking at for this issue?

 I'm running everything on my development box:
 Windows XP
 Jboss 4.0.x
 Firefox 2.x
 Java 1.5.x
 MyFaces 1.latest
 Facelets 1.11

 My local machine timezone is EST.

 Actually, I suspect your timezone is EDT, and that this
 is a daylight savings time issue.

 -- Adam


Adam - thanks for the response.  You were right, it was EDT.

The whole date thing has me a little perplexed.

I setup the following:
   - computer time (GMT - made sure DST was off)
   - added GMT to inputDate

Voila, no time change.  My next step is to setup the server/pages this way
and test on a client that is not GMT.  Will the time be changed since the
client has a different timezone?

I've done a little google searching; but feel I'm missing the keywords I
should be looking for.  Suggestions on what I can read to understand
dates/timezone better and how they impact the various JSF/java components?

Thanks,
Chris



tr:inputDate and hour/minute oddity

2007-06-12 Thread Chris Hane
When I select add an tr:inputDate tag with a converter that displays the 
hours/minutes also, the hours are not correct.  For example, in the demo 
inputDate.jspx, change the last inputDate to be:


   tr:inputDate id=mdf5 value=2004/09/06 label=attached converter
  tr:convertDateTime secondaryPattern=d/M/ hh:mm
  pattern=/M/d hh:mm /
   /tr:inputDate


I added the hh:mm to the converter.  When you select a day in the current 
month, the time will default to the current time.  Select another day in 
the current month and the time stays the same.


Select a day in the past (say January) and the time increases by 1 hour. 
Select another day in January and the time increases again by 1 hour.


Is this a known issue?  Are there any workarounds?

Is there something else I should be looking at for this issue?

I'm running everything on my development box:
Windows XP
Jboss 4.0.x
Firefox 2.x
Java 1.5.x
MyFaces 1.latest
Facelets 1.11

My local machine timezone is EST.

Chris


Re: tr:inputDate and hour/minute oddity

2007-06-12 Thread Adam Winer

On 6/12/07, Chris Hane [EMAIL PROTECTED] wrote:

When I select add an tr:inputDate tag with a converter that displays the
hours/minutes also, the hours are not correct.  For example, in the demo
inputDate.jspx, change the last inputDate to be:

tr:inputDate id=mdf5 value=2004/09/06 label=attached converter
   tr:convertDateTime secondaryPattern=d/M/ hh:mm
   pattern=/M/d hh:mm /
/tr:inputDate


I added the hh:mm to the converter.  When you select a day in the current
month, the time will default to the current time.  Select another day in
the current month and the time stays the same.

Select a day in the past (say January) and the time increases by 1 hour.
Select another day in January and the time increases again by 1 hour.

Is this a known issue?  Are there any workarounds?

Is there something else I should be looking at for this issue?

I'm running everything on my development box:
Windows XP
Jboss 4.0.x
Firefox 2.x
Java 1.5.x
MyFaces 1.latest
Facelets 1.11

My local machine timezone is EST.


Actually, I suspect your timezone is EDT, and that this
is a daylight savings time issue.

-- Adam


[Trinidad] tr:inputDate and hour/minute oddity

2007-06-12 Thread Chris Hane
When I select add an tr:inputDate tag with a converter that displays the 
hours/minutes also, the hours are not correct.  For example, in the demo 
inputDate.jspx, change the last inputDate to be:


   tr:inputDate id=mdf5 value=2004/09/06 label=attached converter
  tr:convertDateTime secondaryPattern=d/M/ hh:mm
  pattern=/M/d hh:mm /
   /tr:inputDate


I added the hh:mm to the converter.  When you select a day in the current 
month, the time will default to the current time.  Select another day in 
the current month and the time stays the same.


Select a day in the past (say January) and the time increases by 1 hour. 
Select another day in January and the time increases again by 1 hour.


Is this a known issue?  Are there any workarounds?

Is there something else I should be looking at for this issue?

I'm running everything on my development box:
Windows XP
Jboss 4.0.x
Firefox 2.x
Java 1.5.x
MyFaces 1.latest
Facelets 1.11

My local machine timezone is EST.

Chris