Re: [TRINIDAD] Header rendering multiple times.

2010-03-17 Thread Bart Kummel
Hi Joachim,

The pageFlowScope is *the* alternative for t:savestate. I don't see why
pageFlowScope is less convenient. I admit you'll have to get used to it. But
in the end, I think pageFlowScope is a more structural solution. And
pageFlowScope is more versatile, as it can be used across pages too.

You should also be aware that JSF 2.0 uses a similar solution to this
problem. So by getting used to pageFlowScope you are already preparing
yourself for a switch to JSF 2.0...

Best regards,
Bart

On Tue, Mar 16, 2010 at 15:38, Joachim Schrod jsch...@acm.org wrote:

 Bart Kummel wrote:

 Hello,


 Why are you mixing Tomahawk and Trinidad components? Apart from some
 special
 cases (e.g. captcha and schedule) there are Trinidad alternatives to every
 Tomahawk component.


 What do you use as the Trinidad replacement for t:savestate, as a method to
 cache request-scoped beans on the same page? E.g., to avoid the need for
 another database roundtrip in postback or redirect requests.

 I know pageFlowScope, but it is more inconvenient to use and has also a
 slightly different focus, AFAIU.

Joachim

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




-- 
___
Bart Kummel

Author of the book Apache MyFaces 1.2 Web Application Development
See http://tinyurl.com/am12wad


Re: [Trinidad] Problem with chooseDate and chart in Opera

2010-03-17 Thread Bart Kummel
Hi Jozef,

I don't have any experience with Opera. (I don't even have it installed...)
So I cannot help you on this. But I can give you some clues...

- The charts are rendered with SVG and JavaScript. So you should check if
Opera can render SVG. Perhaps you'll need some plugin?
- The date picker: perhaps Opera has a built-in popup blocker that blocks
the date picker popup? To prevent this, you can use Trinidad's lightweigt
dialogs, see [1].

Best regards,
Bart

[1]
http://myfaces.apache.org/trinidad/devguide/configuration.html#org.apache.myfaces.trinidad.ENABLE_LIGHTWEIGHT_DIALOGS

On Sun, Mar 14, 2010 at 14:51, Jozef Dropco jozef.dro...@gmail.com wrote:

 Hello again,
 I did not mention that, this does not work also in examples on
 http://test.codebeat.ro/trinidad-components-demo/component-demo/chart-Default.
 Could somebody say something to it, its a bug?
 Thanks
 Jozef

 On 10.3.2010 13:57, Jozef Dropco wrote:

 Hello all,
 I dont know why it doesnt work but, i have opera 10.5 and it does not
 work. If I open my page in Firefox everything is fine, but in opera
 chooseDate is not rendered at all and chart loads something but never stops.
 What is wrong here I cant understand it.

 Thanks Jozef
 Conf: Facelets 1.1.14, trinidad:1.2.13, Glassfish (and same on tomcat)





-- 
___
Bart Kummel

Author of the book Apache MyFaces 1.2 Web Application Development
See http://tinyurl.com/am12wad


Re: [Trinidad] How to get control over tr:table detail disclose link table cell?

2010-03-17 Thread Elmar Kretzer
Hi Bart,

the skinning support for the automatic disclose link is not sufficient as far 
as i can see.

E.g. in tr:column i can set the style class via EL so i have full control 
over the styles in a rendered table row,
and I can explicitly change the style class of a disclosed row's table cells.

But there is no possibility to change the style class of the cell with the 
built-in disclose link of a disclosed row.

i am missing something like:

1.
 f:facet name=discloser /f:facet 
or

2.
an attribute in tr:table like: 
discloseLinkCellStyleClass={#xxx.yyy}
or

3.
any way to hide the built-in disclose link (cell). 
we already implemented an own listener for enhanced control over the row 
disclosing which we place inside a normal tr:column.
but there is no way to hide the built-in disclose link (cell). As soon as i add 
the necessary detail facet, the cell gets rendered.

you see my problem? 
=)

Best regards,
Elmar



 Hi Elmar,
 
 You should use Trinidad Skinning for this. You can take an existing skin and
 change the elements you want to change the appearance of. See [1] for more
 information.
 
 Best regards,
 Bart
 
 [1] http://myfaces.apache.org/trinidad/devguide/skinning.html
 
 On Wed, Mar 10, 2010 at 11:58, Elmar Kretzer e.kret...@symentis.com wrote:
 
 Hi all,
 
 is it possible to get control over the appearance of the disclose link in a
 tr:table?
 
 Currently it seems like the td with the disclose link get automagically
 rendered with class af_column_cell-text and OraTableBorder when you add
 the detail stamp.
 
 Like:
 td nowrap= class=af_column_cell-text OraTableBorder
 headers=j_id1div/div/td
 
 Is there any hook to change the style class of this td?
 
 We want to mark the disclosed rows + details with a different background
 color.
 The only problem now is that the disclose link able cell has always the
 same style class .
 
 Thx for any suggestions.
 
 Elmar
 
 
 
 
 -- 
 ___
 Bart Kummel
 
 Author of the book Apache MyFaces 1.2 Web Application Development
 See http://tinyurl.com/am12wad



Re: [Trinidad] Problem with chooseDate and chart in Opera

2010-03-17 Thread Jozef Dropco

Thanks for response Bart,

I have tried this before I send this message. I tried other sites with 
svg in Opera and it works just fine and to chooseDate: there are 2 
options inputDate and chooseDate tag, with chooseDate it works but 
chooseDate should be rendered in my web page as calendar but it does not 
render anything in my page, see attached files.


Jozef
On 17.3.2010 8:12, Bart Kummel wrote:

Hi Jozef,

I don't have any experience with Opera. (I don't even have it installed...)
So I cannot help you on this. But I can give you some clues...

- The charts are rendered with SVG and JavaScript. So you should check if
Opera can render SVG. Perhaps you'll need some plugin?
- The date picker: perhaps Opera has a built-in popup blocker that blocks
the date picker popup? To prevent this, you can use Trinidad's lightweigt
dialogs, see [1].

Best regards,
Bart

[1]
http://myfaces.apache.org/trinidad/devguide/configuration.html#org.apache.myfaces.trinidad.ENABLE_LIGHTWEIGHT_DIALOGS

On Sun, Mar 14, 2010 at 14:51, Jozef Dropcojozef.dro...@gmail.com  wrote:

   

Hello again,
I did not mention that, this does not work also in examples on
http://test.codebeat.ro/trinidad-components-demo/component-demo/chart-Default.
Could somebody say something to it, its a bug?
Thanks
Jozef

On 10.3.2010 13:57, Jozef Dropco wrote:

 

Hello all,
I dont know why it doesnt work but, i have opera 10.5 and it does not
work. If I open my page in Firefox everything is fine, but in opera
chooseDate is not rendered at all and chart loads something but never stops.
What is wrong here I cant understand it.

Thanks Jozef
Conf: Facelets 1.1.14, trinidad:1.2.13, Glassfish (and same on tomcat)


   
 


   


 td id=content class=content!--Start: 
org.apache.myfaces.trinidad.Form[contentForm]--
form id=contentForm name=contentForm style=margin:0px 
method=POST onkeypress=return _submitOnEnter(event,'contentForm'); 
action=/Hostel-IS/faces/index.xhtml!--Start: 
org.apache.myfaces.trinidad.Choose[dateChooser]--table id=dateChooser 
cellpadding=0 cellspacing=0 border=0 summary=script 
type=text/javascriptvar _locale='en';var _tLocale='en';/scriptscript 
type=text/javascript 
src=/Hostel-IS/adf/jsLibs/resources/LocaleElements_en1_2_13.js?loc=en/scriptscript
 type=text/javascriptvar _df2DYS=1950;/scripttr
  td class=af_chooseDate_nav align=lefta href=# 
onclick=_firePartialChange('/Hostel-IS/faces/__ADFv__?_t=idpamp;source=dateChooseramp;minValue=108863280amp;maxValue=141998040amp;value=1268814706403amp;loc=enamp;scrolledValue=126731160');return
 false;span title=Previous monthlt;/span/a/td

  td colspan=5 class=af_chooseDate_title nowrapselect 
id=dateChoosermonth name=dateChoosermonth title=Choose month 
onchange=_updateCal(this,'/Hostel-IS/faces/__ADFv__?_t=idpamp;source=dateChooseramp;minValue=108863280amp;maxValue=141998040amp;value=1268814706403amp;loc=en',1);
 class=AFFieldText
  option value=126351000January/option

  option value=126618840February/option


  option selected value=126860760March/option

  option value=127128240April/option

  option value=127387440May/option

  option value=127655280June/option

  option value=127914480July/option

  option value=128182320August/option


  option value=128450160September/option

  option value=128709360October/option

  option value=128977560November/option

  option value=129236760December/option
/selectlabel for=dateChoosermonth 
class=p_OraHiddenLabelChoose month/labelnbsp;select 
name=dateChooseryear id=dateChooseryear title=Choose year 
onchange=_updateCal(this,'/Hostel-IS/faces/__ADFv__?_t=idpamp;source=dateChooseramp;minValue=108863280amp;maxValue=141998040amp;value=1268814706403amp;loc=en',1);
 class=AFFieldText
  option value=1079305202004/option


  option value=1110841202005/option

  option value=1142377202006/option

  option value=1173913202007/option

  option value=1205535602008/option

  option value=1237071602009/option

  option selected value=1268607602010/option


   

Re: [Trinidad] How to get control over tr:table detail disclose link table cell?

2010-03-17 Thread Bart Kummel
Hi Elmar,

Yeah, I got your problem. In skinning terms, I think you can summarize your
problem by saying that a af|table::disclosureCell skinning selector is
missing, right?

I can think of a couple of solutions, you also mentioned some. I think for a
lot of use cases the addition of aforementioned skinning selector is a good
solution. This way the cell with the disclosure link and everything that is
in that cell can be styled as you like. (This includes hiding it.)

Adding a discloser facet, as you suggest, gives even more flexibility,
especially when combined with one or more extra skinning selectors. A
downside of adding such a facet might be that it can make things overly
complex.

I'm not a fan of extra styleClass attributes. I think it is better to have
enough skinning selectors. In my opinion, using styleClass attributes is
very close to mixing View code with Controller logic, which should be
prevented.

Long story short: I don't think what you want is possible yet. However, you
can always create an enhancement request in Jira and/or supply a patch...

Best regards,
Bart

On Wed, Mar 17, 2010 at 09:26, Elmar Kretzer e.kret...@symentis.com wrote:

 Hi Bart,

 the skinning support for the automatic disclose link is not sufficient as
 far as i can see.

 E.g. in tr:column i can set the style class via EL so i have full control
 over the styles in a rendered table row,
 and I can explicitly change the style class of a disclosed row's table
 cells.

 But there is no possibility to change the style class of the cell with the
 built-in disclose link of a disclosed row.

 i am missing something like:

 1.
  f:facet name=discloser /f:facet
 or

 2.
 an attribute in tr:table like:
 discloseLinkCellStyleClass={#xxx.yyy}
 or

 3.
 any way to hide the built-in disclose link (cell).
 we already implemented an own listener for enhanced control over the row
 disclosing which we place inside a normal tr:column.
 but there is no way to hide the built-in disclose link (cell). As soon as i
 add the necessary detail facet, the cell gets rendered.

 you see my problem?
 =)

 Best regards,
 Elmar



  Hi Elmar,
 
  You should use Trinidad Skinning for this. You can take an existing skin
 and
  change the elements you want to change the appearance of. See [1] for
 more
  information.
 
  Best regards,
  Bart
 
  [1] http://myfaces.apache.org/trinidad/devguide/skinning.html
 
  On Wed, Mar 10, 2010 at 11:58, Elmar Kretzer e.kret...@symentis.com
 wrote:
 
  Hi all,
 
  is it possible to get control over the appearance of the disclose link
 in a
  tr:table?
 
  Currently it seems like the td with the disclose link get automagically
  rendered with class af_column_cell-text and OraTableBorder when you
 add
  the detail stamp.
 
  Like:
  td nowrap= class=af_column_cell-text OraTableBorder
  headers=j_id1div/div/td
 
  Is there any hook to change the style class of this td?
 
  We want to mark the disclosed rows + details with a different background
  color.
  The only problem now is that the disclose link able cell has always the
  same style class .
 
  Thx for any suggestions.
 
  Elmar
 
 
 
 
  --
  ___
  Bart Kummel
 
  Author of the book Apache MyFaces 1.2 Web Application Development
  See http://tinyurl.com/am12wad




-- 
___
Bart Kummel

Author of the book Apache MyFaces 1.2 Web Application Development
See http://tinyurl.com/am12wad


Re: [Trinidad] Old pocket IE

2010-03-17 Thread Walter Mourão
I hacked the AgentFactoryImpl to use the generic pda when the Windows CE is
of version 4.20 and it is working fine now...

Could somebody confirm the Windows CE 4.20 does not work with Trinidad in a
way I open an issue+patch in Trinidad ?

FYI, the request headers:
{cookie=JSESSIONID=C71C1786C80463B62427EDE54E5C024B, ua-pixels=240x320,
connection=Keep-Alive, host=10.0.1.1:8080, accept=*/*, ua-os=Windows CE
(Pocket PC) - Version 4.20, user-agent=Mozilla/4.0 (compatible; MSIE 4.01;
Windows CE; PPC; 240x320), accept-encoding=gzip, deflate,
ua-language=JavaScript, ua-cpu=ARM PXA255, ua-voice=FALSE, ua-color=color16}


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



2010/3/16 Walter Mourão walter.mou...@gmail.com

 Hi folks,

 I just realized the tr:commandLink isn't working with an old Pocket PC /
 Pocket IE... it looks like this browser does not support javascript. Is
 there a way to force Trinidad to render without javascript ?

 FYI: the application works with Windows Mobile 5... but my customer has
 lots of data collectors running the old Pocket IE..

 Thanks in advance,

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




Primefaces p:dataTable not decoding, seems to be a MyFaces 2 problem

2010-03-17 Thread Bruno Aranda
Hi,

In my fancy little webapp I am using Primefaces dataTable in lazy mode such
as in this example[1], and I want to use it with MyFaces 2. However there
seems to be a bug and the component decoding is not invoked, so if you
navigate to another page of the table the row index does not change.

It can be reproduced just getting the primefaces showcase examples:

svn co http://primefaces.googlecode.com/svn/examples/trunk/prime-showcase

Then replacing the MyFaces 2 dependencies in the profile to the latest (it
does not work either with Myfaces 2.0.0-beta or beta2). And run the showcase
with:

mvn jetty:run-exploded -Pmyfaces-2.0

If you modify slightly the dataTable example so it shows the first result in
one column (by modifying the TableBean class), you will see it is always 0.

A debugging session shows that the decode for dataTable renderer is never
invoked. I am a bit rusty with all this, does any one have an idea what may
be happening or what could I look to pinpoint the problem?

Thanks,

Bruno

[1] http://www.primefaces.org:8080/prime-showcase/ui/datatableLazy.jsf


How to fill child table records on the row selection of parent table (Nested Tables) in Trinidad.

2010-03-17 Thread navnath kumbhar
Hi All,

I am using Trinidad 2.0.0 and myfaces 2.0.0
I am trying to implement nested tables using tr:table tag of Trinidad.
It's showing child table on each row of parent table.
But the problem is different child records in child table on the selection
from parent table's row?

Is there any action or event should I call in child table.

Here is my code snippets:
jspx file

tr:table var=row rowSelection=multiple
value=#{saveData.nameList}
binding=#{tableActions.table}
tr:column
f:facet name=header
tr:outputText value=Name /
/f:facet
tr:inputText value=#{row.name} /
/tr:column
tr:column
f:facet name=header
tr:outputText value=Gender /
/f:facet
tr:selectOneChoice value=#{row.selectGender}
f:selectItems value=#{row.gendar} /

/tr:selectOneChoice


/tr:column

tr:column
f:facet name=header
tr:outputText value=Address /
/f:facet
tr:inputText value=#{row.add} /

/tr:column

f:facet name=detailStamp
tr:table var=row rowSelection=multiple
binding=#{tableActions.tableContact}
value=#{saveData.nestedNameList}
tr:column
f:facet name=header
tr:outputText value=Second Name
/
/f:facet
tr:inputText value=#{row.name} /
/tr:column
tr:column
f:facet name=header
tr:outputText value=Gender /
/f:facet
tr:selectOneChoice
value=#{row.selectGender}
f:selectItems value=#{row.gendar}
/

/tr:selectOneChoice


/tr:column

tr:column
f:facet name=header
tr:outputText value=Address /
/f:facet
tr:inputText value=#{row.add} /
/tr:column
tr:column
f:facet name=header
tr:outputText value=Subtable /
/f:facet
/tr:column


/tr:table
/f:facet


/tr:table


Can any one suggest me, how do I fill child table on the bases of row
selection in parent table?

Thank You,
Navnath Kumbhar.


Re: [TRINIDAD] Header rendering multiple times.

2010-03-17 Thread Samba
hey,

Is it possible that when we explicitly removed the mention of state saving
mechanism from web.xml configuration; that every component library is
choosing its own default rather and that could be causing things correctly?

here is my take at it:

1. state saving configured to client-- Trinidad components work fine but
some tomahawk components have isssues
2. state saving configured to server-- Tomahawk components and JSF RI
components work correctly, but some trinidad
componetns show some issues.
3. state saving method explicitly removed so that each component library
picks up its own default mechanism for saving and   restoring the
component's state; thus harmoniously ork with each other with out any issues

I'm just guessing but it would be better if this analysis I put forward in
the above three points holds true for any JSF librar, so that developers can
build pages and applications with the best components available in the
market; (OSS or proprietary).

Regards,
Samba

On Mon, Mar 15, 2010 at 9:56 PM, Andrew Robinson 
andrew.rw.robin...@gmail.com wrote:

 Sorry, not sure then, anyone else have an idea?

 -A

 On Mon, Mar 15, 2010 at 6:11 AM, preeti agarwal
 preetiagarwa...@gmail.com wrote:
   There are no JSTL components being used.
  Though we use facelets.
 
  There is an entry in web.xml file :
 
   context-param
 param-namejavax.faces.STATE_SAVING_METHOD/param-name
 param-valueclient/param-value
 !--param-valueserver/param-value--
 /context-param
  When this entry is removed (thereby reverting to default settings), the
  problem gets solved. Any reason why client side State Saving is causing
 an
  issue?
 
 
 
  On Tue, Mar 9, 2010 at 10:23 PM, Andrew Robinson 
  andrew.rw.robin...@gmail.com wrote:
 
  Do you use any JSTL tags?
  Have you any component binding in the page, especially ones that may
  live longer than one request?
 
  On Tue, Mar 9, 2010 at 7:31 AM, preeti agarwal
  preetiagarwa...@gmail.com wrote:
   Description of problem : I have an xhtml page in which I use trininad
   components (like tablelayout) and also tomahawk components (like
 form). I
   have used some usual HTML components along with it. First time the
 page
  is
   rendered correctly. But anysubsequent refresh causes the header to
 render
   multiple times. I suspect it might have something to do with state
  saving.
   Can anyone help me with this?
  
  
  
  
   PS: I originally suspected that it had something to do with mixing of
   incompatible HTML div and Trinidad components.Changing div to
 t:div
   didn't solve the issue.
  
 
 



Re: Primefaces p:dataTable not decoding, seems to be a MyFaces 2 problem

2010-03-17 Thread Jakob Korherr
Hi Bruno,

I tried the example with my latest build from MyFaces trunk and I got the
following exception for every click on the dataTable navigation:

17.03.2010 15:40:34
org.apache.myfaces.view.facelets.DefaultFaceletsStateManagementHelper
serializeView
SCHWERWIEGEND: Exiting serializeView - Could not serialize state:
org.primefaces.examples.view.TableBean
java.io.NotSerializableException: org.primefaces.examples.view.TableBean
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1156)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
at java.util.HashMap.writeObject(HashMap.java:1001)
at sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1461)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1338)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1146)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
at java.util.HashMap.writeObject(HashMap.java:1001)
at sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1461)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
at
org.apache.myfaces.view.facelets.DefaultFaceletsStateManagementHelper.serializeView(DefaultFaceletsStateManagementHelper.java:293)
at
org.apache.myfaces.view.facelets.DefaultFaceletsStateManagementHelper.saveSerializedViewInServletSession(DefaultFaceletsStateManagementHelper.java:178)
at
org.apache.myfaces.view.facelets.DefaultFaceletsStateManagementStrategy.saveView(DefaultFaceletsStateManagementStrategy.java:422)
at
org.apache.myfaces.application.jsp.JspStateManagerImpl.saveView(JspStateManagerImpl.java:447)
at
org.primefaces.component.datatable.DataTableRenderer.encodePartially(DataTableRenderer.java:171)
at
org.primefaces.component.datatable.DataTable.encodePartially(DataTable.java:469)
at
org.primefaces.application.PrimeFacesPhaseListener$2.invokeContextCallback(PrimeFacesPhaseListener.java:260)
at javax.faces.component.UIData.invokeOnComponent(UIData.java:312)
at
javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:209)
at
javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:936)
at
javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:209)
at
javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:936)
at
javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:209)
at
javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:936)
at
org.primefaces.application.PrimeFacesPhaseListener.handleAjaxRequest(PrimeFacesPhaseListener.java:111)
at
org.primefaces.application.PrimeFacesPhaseListener.beforePhase(PrimeFacesPhaseListener.java:66)
at
org.apache.myfaces.lifecycle.PhaseListenerManager.informPhaseListenersBefore(PhaseListenerManager.java:76)
at
org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:200)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:191)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)
at
org.primefaces.examples.filter.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:32)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at
org.primefaces.webapp.filter.FileUploadFilter.doFilter(FileUploadFilter.java:79)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
at
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
at

Re: Primefaces p:dataTable not decoding, seems to be a MyFaces 2 problem

2010-03-17 Thread Jakob Korherr
Hi again,

OK, setting the org.apache.myfaces.SERIALIZE_STATE_IN_SESSION config param
to false solves the NotSerializableException.

Unfortunately it does not solve the other problem..

Regards,
Jakob

2010/3/17 Jakob Korherr jakob.korh...@gmail.com

 Hi Bruno,

 I tried the example with my latest build from MyFaces trunk and I got the
 following exception for every click on the dataTable navigation:

 17.03.2010 15:40:34
 org.apache.myfaces.view.facelets.DefaultFaceletsStateManagementHelper
 serializeView
 SCHWERWIEGEND: Exiting serializeView - Could not serialize state:
 org.primefaces.examples.view.TableBean
 java.io.NotSerializableException: org.primefaces.examples.view.TableBean
 at
 java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1156)
 at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
 at java.util.HashMap.writeObject(HashMap.java:1001)
 at sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source)
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at
 java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945)
 at
 java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1461)
 at
 java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
 at
 java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
 at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1338)
 at
 java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1146)
 at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
 at java.util.HashMap.writeObject(HashMap.java:1001)
 at sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source)
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at
 java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945)
 at
 java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1461)
 at
 java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
 at
 java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
 at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
 at
 org.apache.myfaces.view.facelets.DefaultFaceletsStateManagementHelper.serializeView(DefaultFaceletsStateManagementHelper.java:293)
 at
 org.apache.myfaces.view.facelets.DefaultFaceletsStateManagementHelper.saveSerializedViewInServletSession(DefaultFaceletsStateManagementHelper.java:178)
 at
 org.apache.myfaces.view.facelets.DefaultFaceletsStateManagementStrategy.saveView(DefaultFaceletsStateManagementStrategy.java:422)
 at
 org.apache.myfaces.application.jsp.JspStateManagerImpl.saveView(JspStateManagerImpl.java:447)
 at
 org.primefaces.component.datatable.DataTableRenderer.encodePartially(DataTableRenderer.java:171)
 at
 org.primefaces.component.datatable.DataTable.encodePartially(DataTable.java:469)
 at
 org.primefaces.application.PrimeFacesPhaseListener$2.invokeContextCallback(PrimeFacesPhaseListener.java:260)
 at javax.faces.component.UIData.invokeOnComponent(UIData.java:312)
 at
 javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:209)
 at
 javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:936)
 at
 javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:209)
 at
 javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:936)
 at
 javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:209)
 at
 javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:936)
 at
 org.primefaces.application.PrimeFacesPhaseListener.handleAjaxRequest(PrimeFacesPhaseListener.java:111)
 at
 org.primefaces.application.PrimeFacesPhaseListener.beforePhase(PrimeFacesPhaseListener.java:66)
 at
 org.apache.myfaces.lifecycle.PhaseListenerManager.informPhaseListenersBefore(PhaseListenerManager.java:76)
 at
 org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:200)
 at javax.faces.webapp.FacesServlet.service(FacesServlet.java:191)
 at
 org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
 at
 org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)
 at
 org.primefaces.examples.filter.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:32)
 at
 org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
 at
 org.primefaces.webapp.filter.FileUploadFilter.doFilter(FileUploadFilter.java:79)
 at
 org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
 at
 org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
 at
 

Re: Primefaces p:dataTable not decoding, seems to be a MyFaces 2 problem

2010-03-17 Thread Matthias Wessendorf
On Wed, Mar 17, 2010 at 4:27 AM, Bruno Aranda brunoara...@gmail.com wrote:
 Hi,

 In my fancy little webapp I am using Primefaces dataTable in lazy mode such
 as in this example[1], and I want to use it with MyFaces 2. However there
 seems to be a bug and the component decoding is not invoked, so if you
 navigate to another page of the table the row index does not change.

 It can be reproduced just getting the primefaces showcase examples:

 svn co http://primefaces.googlecode.com/svn/examples/trunk/prime-showcase

 Then replacing the MyFaces 2 dependencies in the profile to the latest (it
 does not work either with Myfaces 2.0.0-beta or beta2). And run the showcase
 with:

 mvn jetty:run-exploded -Pmyfaces-2.0

oh, that's not the default?
Pretty odd, especially since the stuff is from a committer ;-)

@NotSerializableException: IMO it is ok to have that exception,
since the bean is in session and not implements the right contract
for passivation... (= demo bug)

-Matthias


 If you modify slightly the dataTable example so it shows the first result in
 one column (by modifying the TableBean class), you will see it is always 0.

 A debugging session shows that the decode for dataTable renderer is never
 invoked. I am a bit rusty with all this, does any one have an idea what may
 be happening or what could I look to pinpoint the problem?

 Thanks,

 Bruno

 [1] http://www.primefaces.org:8080/prime-showcase/ui/datatableLazy.jsf




-- 
Matthias Wessendorf

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


MyFaces 1.2.6, JBoss PortletBridge 1.0.0CR3 Postback with LifeRay 5.2.3

2010-03-17 Thread Sertic Mirko, Bedag
h...@all

 

We are running into a strange problem with MyFaces, Facelets, the JBoss
PortletBridge running on LifeRay.

 

It seems that normal h:commandLinks are no longer working. After some
debugging, it seems that HtmlResponseStateManager.isPostback() always
returns false, and the Lifecycle jumps to the RENDER_RESPONSE phase. No
action is invoked. In fact there is no VIEW_STATE_PARAM request
parameter.

 

What is going wrong here? I noticed that there are two form elements
in the resulting HTML of the page. Is the MyFaces JavaScript just
submitting the wrong form?

 

Thanks in advance

Mirko

 



Re: MyFaces 1.2.6, JBoss PortletBridge 1.0.0CR3 Postback with LifeRay 5.2.3

2010-03-17 Thread Jakob Korherr
Hi,

It has to be something like that, yes. But why are there two different forms
in the HTML anyway?

Regards,
Jakob

2010/3/17 Sertic Mirko, Bedag mirko.ser...@bedag.ch

 h...@all



 We are running into a strange problem with MyFaces, Facelets, the JBoss
 PortletBridge running on LifeRay.



 It seems that normal h:commandLinks are no longer working. After some
 debugging, it seems that HtmlResponseStateManager.isPostback() always
 returns false, and the Lifecycle jumps to the RENDER_RESPONSE phase. No
 action is invoked. In fact there is no VIEW_STATE_PARAM request
 parameter.



 What is going wrong here? I noticed that there are two form elements
 in the resulting HTML of the page. Is the MyFaces JavaScript just
 submitting the wrong form?



 Thanks in advance

 Mirko






Re: MyFaces 1.2.6, JBoss PortletBridge 1.0.0CR3 Postback with LifeRay 5.2.3

2010-03-17 Thread Leonardo Uribe
Hi

I remember this one. In apache myfaces portlet bridge there is an special
configuration to allow some params to be preserved between action request
and render request, so the state is not lost when it is used server side
state saving. The hack there looks like this:

faces-config version=1.2 xmlns=http://java.sun.com/xml/ns/javaee;
xmlns:bridge=
http://www.apache.org/myfaces/xml/ns/bridge/bridge-extension;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/web-facesconfig_1_2.xsd;

application

view-handlerorg.apache.myfaces.portlet.faces.application.PortletViewHandlerImpl/view-handler

state-managerorg.apache.myfaces.portlet.faces.application.PortletStateManagerImpl/state-manager

el-resolverorg.apache.myfaces.portlet.faces.el.PortletELResolver/el-resolver
application-extension
  bridge:excluded-attributes

bridge:excluded-attributecom.sun.faces.*/bridge:excluded-attribute

bridge:excluded-attributecom.sun.faces.util.*/bridge:excluded-attribute

bridge:excluded-attributeorg.apache.myfaces.application.jsp.JspStateManagerImpl.*/bridge:excluded-attribute

bridge:excluded-attributeorg.apache.myfaces.el.unified.resolver.managedbean.*/bridge:excluded-attribute

bridge:excluded-attributeorg.apache.myfaces.shared_impl.renderkit.RendererUtils.*/bridge:excluded-attribute

bridge:excluded-attributeorg.apache.myfaces.application.DefaultViewHandlerSupport.*/bridge:excluded-attribute

bridge:excluded-attributejsf_sequence/bridge:excluded-attribute
  /bridge:excluded-attributes
/application-extension
/application
/faces-config

to check if this is what is happening, change your jsf state saving to
client. If so, there should be something in jboss portlet bridge that allows
do something similar. I have never tried it before (but good to know that
this bridge exists).

regards,

Leonardo Uribe

2010/3/17 Sertic Mirko, Bedag mirko.ser...@bedag.ch

 h...@all



 We are running into a strange problem with MyFaces, Facelets, the JBoss
 PortletBridge running on LifeRay.



 It seems that normal h:commandLinks are no longer working. After some
 debugging, it seems that HtmlResponseStateManager.isPostback() always
 returns false, and the Lifecycle jumps to the RENDER_RESPONSE phase. No
 action is invoked. In fact there is no VIEW_STATE_PARAM request
 parameter.



 What is going wrong here? I noticed that there are two form elements
 in the resulting HTML of the page. Is the MyFaces JavaScript just
 submitting the wrong form?



 Thanks in advance

 Mirko






[TOBAGO] tx:date in a popup

2010-03-17 Thread Fernando Augusto

Hello,

I am using Tobago 1.0.24 and just ran in a weird situation... I have a 
form inside a popup, that uses tx:date. When I click in the calendar 
icon, only the modal DIV appears, behind the popup. I must click the 
calendar again to show it correctly. I already tried to change the modal 
property of the popup window to false, but the behavior continues... How 
can I make the calendar icon to appear in a single click, while the form 
is inside the popup?


Best Regards,

Fernando Augusto


Re: Primefaces p:dataTable not decoding, seems to be a MyFaces 2 problem

2010-03-17 Thread Jakob Korherr
Found it!

The problem is that Primefaces' PartialViewRoot keeps its own children list
and the method on UIComponentBase (getFacetsAndChildren()) does not take
getChildren() but _childrenList into account when creating the Iterator.
This one was hard to find...

I will create a JIRA issue for this and fix it asap.

Regards,
Jakob

2010/3/17 Matthias Wessendorf mat...@apache.org

 On Wed, Mar 17, 2010 at 4:27 AM, Bruno Aranda brunoara...@gmail.com
 wrote:
  Hi,
 
  In my fancy little webapp I am using Primefaces dataTable in lazy mode
 such
  as in this example[1], and I want to use it with MyFaces 2. However there
  seems to be a bug and the component decoding is not invoked, so if you
  navigate to another page of the table the row index does not change.
 
  It can be reproduced just getting the primefaces showcase examples:
 
  svn co
 http://primefaces.googlecode.com/svn/examples/trunk/prime-showcase
 
  Then replacing the MyFaces 2 dependencies in the profile to the latest
 (it
  does not work either with Myfaces 2.0.0-beta or beta2). And run the
 showcase
  with:
 
  mvn jetty:run-exploded -Pmyfaces-2.0

 oh, that's not the default?
 Pretty odd, especially since the stuff is from a committer ;-)

 @NotSerializableException: IMO it is ok to have that exception,
 since the bean is in session and not implements the right contract
 for passivation... (= demo bug)

 -Matthias

 
  If you modify slightly the dataTable example so it shows the first result
 in
  one column (by modifying the TableBean class), you will see it is always
 0.
 
  A debugging session shows that the decode for dataTable renderer is never
  invoked. I am a bit rusty with all this, does any one have an idea what
 may
  be happening or what could I look to pinpoint the problem?
 
  Thanks,
 
  Bruno
 
  [1] http://www.primefaces.org:8080/prime-showcase/ui/datatableLazy.jsf
 



 --
 Matthias Wessendorf

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



[TOBAGO] formatting fields with tx:in

2010-03-17 Thread Fernando Augusto

Hello,

Is there a way to make tx:in to format the string passed (like a phone 
number, or anything like) while the user is typing? I tried 
f:convertNumber to make the currency format but it is not working. Any 
help on the issue?


Best Regards,

Fernando Augusto


Re: Primefaces p:dataTable not decoding, seems to be a MyFaces 2 problem

2010-03-17 Thread Bruno Aranda
Wonderful! I was too rusty for this one :)

Thanks!

Bruno

On 17 March 2010 16:44, Jakob Korherr jakob.korh...@gmail.com wrote:

 Found it!

 The problem is that Primefaces' PartialViewRoot keeps its own children list
 and the method on UIComponentBase (getFacetsAndChildren()) does not take
 getChildren() but _childrenList into account when creating the Iterator.
 This one was hard to find...

 I will create a JIRA issue for this and fix it asap.

 Regards,
 Jakob

 2010/3/17 Matthias Wessendorf mat...@apache.org

  On Wed, Mar 17, 2010 at 4:27 AM, Bruno Aranda brunoara...@gmail.com
  wrote:
   Hi,
  
   In my fancy little webapp I am using Primefaces dataTable in lazy mode
  such
   as in this example[1], and I want to use it with MyFaces 2. However
 there
   seems to be a bug and the component decoding is not invoked, so if you
   navigate to another page of the table the row index does not change.
  
   It can be reproduced just getting the primefaces showcase examples:
  
   svn co
  http://primefaces.googlecode.com/svn/examples/trunk/prime-showcase
  
   Then replacing the MyFaces 2 dependencies in the profile to the latest
  (it
   does not work either with Myfaces 2.0.0-beta or beta2). And run the
  showcase
   with:
  
   mvn jetty:run-exploded -Pmyfaces-2.0
 
  oh, that's not the default?
  Pretty odd, especially since the stuff is from a committer ;-)
 
  @NotSerializableException: IMO it is ok to have that exception,
  since the bean is in session and not implements the right contract
  for passivation... (= demo bug)
 
  -Matthias
 
  
   If you modify slightly the dataTable example so it shows the first
 result
  in
   one column (by modifying the TableBean class), you will see it is
 always
  0.
  
   A debugging session shows that the decode for dataTable renderer is
 never
   invoked. I am a bit rusty with all this, does any one have an idea what
  may
   be happening or what could I look to pinpoint the problem?
  
   Thanks,
  
   Bruno
  
   [1] http://www.primefaces.org:8080/prime-showcase/ui/datatableLazy.jsf
  
 
 
 
  --
  Matthias Wessendorf
 
  blog: http://matthiaswessendorf.wordpress.com/
  sessions: http://www.slideshare.net/mwessendorf
  twitter: http://twitter.com/mwessendorf
 



Re: Primefaces p:dataTable not decoding, seems to be a MyFaces 2 problem

2010-03-17 Thread Jakob Korherr
So, I committed the fix - this works now perfectly :) :)

Regards,
Jakob

2010/3/17 Bruno Aranda brunoara...@gmail.com

 Wonderful! I was too rusty for this one :)

 Thanks!

 Bruno

 On 17 March 2010 16:44, Jakob Korherr jakob.korh...@gmail.com wrote:

  Found it!
 
  The problem is that Primefaces' PartialViewRoot keeps its own children
 list
  and the method on UIComponentBase (getFacetsAndChildren()) does not take
  getChildren() but _childrenList into account when creating the Iterator.
  This one was hard to find...
 
  I will create a JIRA issue for this and fix it asap.
 
  Regards,
  Jakob
 
  2010/3/17 Matthias Wessendorf mat...@apache.org
 
   On Wed, Mar 17, 2010 at 4:27 AM, Bruno Aranda brunoara...@gmail.com
   wrote:
Hi,
   
In my fancy little webapp I am using Primefaces dataTable in lazy
 mode
   such
as in this example[1], and I want to use it with MyFaces 2. However
  there
seems to be a bug and the component decoding is not invoked, so if
 you
navigate to another page of the table the row index does not change.
   
It can be reproduced just getting the primefaces showcase examples:
   
svn co
   http://primefaces.googlecode.com/svn/examples/trunk/prime-showcase
   
Then replacing the MyFaces 2 dependencies in the profile to the
 latest
   (it
does not work either with Myfaces 2.0.0-beta or beta2). And run the
   showcase
with:
   
mvn jetty:run-exploded -Pmyfaces-2.0
  
   oh, that's not the default?
   Pretty odd, especially since the stuff is from a committer ;-)
  
   @NotSerializableException: IMO it is ok to have that exception,
   since the bean is in session and not implements the right contract
   for passivation... (= demo bug)
  
   -Matthias
  
   
If you modify slightly the dataTable example so it shows the first
  result
   in
one column (by modifying the TableBean class), you will see it is
  always
   0.
   
A debugging session shows that the decode for dataTable renderer is
  never
invoked. I am a bit rusty with all this, does any one have an idea
 what
   may
be happening or what could I look to pinpoint the problem?
   
Thanks,
   
Bruno
   
[1]
 http://www.primefaces.org:8080/prime-showcase/ui/datatableLazy.jsf
   
  
  
  
   --
   Matthias Wessendorf
  
   blog: http://matthiaswessendorf.wordpress.com/
   sessions: http://www.slideshare.net/mwessendorf
   twitter: http://twitter.com/mwessendorf
  
 



Re: MyFaces 1.2.6, JBoss PortletBridge 1.0.0CR3 Postback with LifeRay 5.2.3

2010-03-17 Thread Michael Freedman
I don't think this is related.  FYI ... there are two types of state 
(potentially) being managed/preserved by the bridge: 
   1) action parameters saved and reexposed during the render
   this is off by default -- there is a portlet init parameter you 
set to enable this

   2) request scope attributes saved until the next action
   this is always on and by default the bridge preserves all 
attributes in the request scope.  One can exclude specific attributes 
from this cache using the

   syntax Leonardo described in his message.

Note:  in both of these cases the state management has nothing to do 
with the View State -- once a render occurs that state is managed by 
Faces in whatever manner the app defines (client/server, etc.)

   -Mike-

On 3/17/2010 8:46 AM, Leonardo Uribe wrote:

Hi

I remember this one. In apache myfaces portlet bridge there is an special
configuration to allow some params to be preserved between action request
and render request, so the state is not lost when it is used server side
state saving. The hack there looks like this:

faces-config version=1.2 xmlns=http://java.sun.com/xml/ns/javaee;
xmlns:bridge=
http://www.apache.org/myfaces/xml/ns/bridge/bridge-extension;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/web-facesconfig_1_2.xsd;

application

view-handlerorg.apache.myfaces.portlet.faces.application.PortletViewHandlerImpl/view-handler

state-managerorg.apache.myfaces.portlet.faces.application.PortletStateManagerImpl/state-manager

el-resolverorg.apache.myfaces.portlet.faces.el.PortletELResolver/el-resolver
application-extension
  bridge:excluded-attributes

bridge:excluded-attributecom.sun.faces.*/bridge:excluded-attribute

bridge:excluded-attributecom.sun.faces.util.*/bridge:excluded-attribute

bridge:excluded-attributeorg.apache.myfaces.application.jsp.JspStateManagerImpl.*/bridge:excluded-attribute

bridge:excluded-attributeorg.apache.myfaces.el.unified.resolver.managedbean.*/bridge:excluded-attribute

bridge:excluded-attributeorg.apache.myfaces.shared_impl.renderkit.RendererUtils.*/bridge:excluded-attribute

bridge:excluded-attributeorg.apache.myfaces.application.DefaultViewHandlerSupport.*/bridge:excluded-attribute

bridge:excluded-attributejsf_sequence/bridge:excluded-attribute
  /bridge:excluded-attributes
/application-extension
/application
/faces-config

to check if this is what is happening, change your jsf state saving to
client. If so, there should be something in jboss portlet bridge that allows
do something similar. I have never tried it before (but good to know that
this bridge exists).

regards,

Leonardo Uribe

2010/3/17 Sertic Mirko, Bedag mirko.ser...@bedag.ch

  

h...@all



We are running into a strange problem with MyFaces, Facelets, the JBoss
PortletBridge running on LifeRay.



It seems that normal h:commandLinks are no longer working. After some
debugging, it seems that HtmlResponseStateManager.isPostback() always
returns false, and the Lifecycle jumps to the RENDER_RESPONSE phase. No
action is invoked. In fact there is no VIEW_STATE_PARAM request
parameter.



What is going wrong here? I noticed that there are two form elements
in the resulting HTML of the page. Is the MyFaces JavaScript just
submitting the wrong form?



Thanks in advance

Mirko







  


Re: MyFaces 1.2.6, JBoss PortletBridge 1.0.0CR3 Postback with LifeRay 5.2.3

2010-03-17 Thread Michael Freedman
You will need to do a little digging to see if your intuition is right.  
Double check the html source in the browser of the page that contains 
the commandLink.  Does is look like the reference tries to submit the 
form that the commandLink is contained within (via javascript)?  If so, 
can you verify this is actually occuring over the wire by using 
javascript debugging in the browser or a tunneler?  If its the correct 
form what parameters are being sent?  Is this only a problem if you use 
MyFaces (vs. Mojarra)


FYI its not unusual for the portal page containing the portlet to output 
its own markup (within forms) -- and hence the likely cause of having 
multiple forms in the client page -- it should not be impacting your usage.

   -Mike-

On 3/17/2010 8:37 AM, Sertic Mirko, Bedag wrote:

h...@all

 


We are running into a strange problem with MyFaces, Facelets, the JBoss
PortletBridge running on LifeRay.

 


It seems that normal h:commandLinks are no longer working. After some
debugging, it seems that HtmlResponseStateManager.isPostback() always
returns false, and the Lifecycle jumps to the RENDER_RESPONSE phase. No
action is invoked. In fact there is no VIEW_STATE_PARAM request
parameter.

 


What is going wrong here? I noticed that there are two form elements
in the resulting HTML of the page. Is the MyFaces JavaScript just
submitting the wrong form?

 


Thanks in advance

Mirko

 



  


Re: Primefaces p:dataTable not decoding, seems to be a MyFaces 2 problem

2010-03-17 Thread Bruno Aranda
Yes, it works beautifully! Many thanks for the quick action! :)

Bruno

On 17 March 2010 17:10, Jakob Korherr jakob.korh...@gmail.com wrote:

 So, I committed the fix - this works now perfectly :) :)

 Regards,
 Jakob

 2010/3/17 Bruno Aranda brunoara...@gmail.com

  Wonderful! I was too rusty for this one :)
 
  Thanks!
 
  Bruno
 
  On 17 March 2010 16:44, Jakob Korherr jakob.korh...@gmail.com wrote:
 
   Found it!
  
   The problem is that Primefaces' PartialViewRoot keeps its own children
  list
   and the method on UIComponentBase (getFacetsAndChildren()) does not
 take
   getChildren() but _childrenList into account when creating the
 Iterator.
   This one was hard to find...
  
   I will create a JIRA issue for this and fix it asap.
  
   Regards,
   Jakob
  
   2010/3/17 Matthias Wessendorf mat...@apache.org
  
On Wed, Mar 17, 2010 at 4:27 AM, Bruno Aranda brunoara...@gmail.com
 
wrote:
 Hi,

 In my fancy little webapp I am using Primefaces dataTable in lazy
  mode
such
 as in this example[1], and I want to use it with MyFaces 2. However
   there
 seems to be a bug and the component decoding is not invoked, so if
  you
 navigate to another page of the table the row index does not
 change.

 It can be reproduced just getting the primefaces showcase examples:

 svn co
http://primefaces.googlecode.com/svn/examples/trunk/prime-showcase

 Then replacing the MyFaces 2 dependencies in the profile to the
  latest
(it
 does not work either with Myfaces 2.0.0-beta or beta2). And run the
showcase
 with:

 mvn jetty:run-exploded -Pmyfaces-2.0
   
oh, that's not the default?
Pretty odd, especially since the stuff is from a committer ;-)
   
@NotSerializableException: IMO it is ok to have that exception,
since the bean is in session and not implements the right contract
for passivation... (= demo bug)
   
-Matthias
   

 If you modify slightly the dataTable example so it shows the first
   result
in
 one column (by modifying the TableBean class), you will see it is
   always
0.

 A debugging session shows that the decode for dataTable renderer is
   never
 invoked. I am a bit rusty with all this, does any one have an idea
  what
may
 be happening or what could I look to pinpoint the problem?

 Thanks,

 Bruno

 [1]
  http://www.primefaces.org:8080/prime-showcase/ui/datatableLazy.jsf

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



RE: [Trinidad] Old pocket IE

2010-03-17 Thread Tadashi Enomori
Hi Walter,

Trinidad mobile support does not specifically support Windows CE 4.2, while
5.x and 6.x are supported. Implementations of Javascript, DOM and CSS on 
different versions of Windows CEs' browsers are very much different from 
each other, and I do not expect Trinidad will work with Windows CE 4.2. 

Generic PDA works without any support of Javascript as it does not depend 
on Javascript at all. In my opinion, Trinidad should regard Windows CE 4.2
(any version less than 5.0) as Generic PDA.

Regards,
Tadashi

-Original Message-
From: Walter Mourão [mailto:walter.mou...@gmail.com] 
Sent: Wednesday, March 17, 2010 4:14 AM
To: MyFaces Discussion
Subject: Re: [Trinidad] Old pocket IE

I hacked the AgentFactoryImpl to use the generic pda when the Windows CE is
of version 4.20 and it is working fine now...

Could somebody confirm the Windows CE 4.20 does not work with Trinidad in a
way I open an issue+patch in Trinidad ?

FYI, the request headers:
{cookie=JSESSIONID=C71C1786C80463B62427EDE54E5C024B, ua-pixels=240x320,
connection=Keep-Alive, host=10.0.1.1:8080, accept=*/*, ua-os=Windows CE
(Pocket PC) - Version 4.20, user-agent=Mozilla/4.0 (compatible; MSIE 4.01;
Windows CE; PPC; 240x320), accept-encoding=gzip, deflate,
ua-language=JavaScript, ua-cpu=ARM PXA255, ua-voice=FALSE, ua-color=color16}


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



2010/3/16 Walter Mourão walter.mou...@gmail.com

 Hi folks,

 I just realized the tr:commandLink isn't working with an old Pocket PC /
 Pocket IE... it looks like this browser does not support javascript. Is
 there a way to force Trinidad to render without javascript ?

 FYI: the application works with Windows Mobile 5... but my customer has
 lots of data collectors running the old Pocket IE..

 Thanks in advance,

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




Re: Primefaces p:dataTable not decoding, seems to be a MyFaces 2 problem

2010-03-17 Thread Matthias Wessendorf
cool stuff! :)

On Wed, Mar 17, 2010 at 10:45 AM, Bruno Aranda brunoara...@gmail.com wrote:
 Yes, it works beautifully! Many thanks for the quick action! :)

 Bruno

 On 17 March 2010 17:10, Jakob Korherr jakob.korh...@gmail.com wrote:

 So, I committed the fix - this works now perfectly :) :)

 Regards,
 Jakob

 2010/3/17 Bruno Aranda brunoara...@gmail.com

  Wonderful! I was too rusty for this one :)
 
  Thanks!
 
  Bruno
 
  On 17 March 2010 16:44, Jakob Korherr jakob.korh...@gmail.com wrote:
 
   Found it!
  
   The problem is that Primefaces' PartialViewRoot keeps its own children
  list
   and the method on UIComponentBase (getFacetsAndChildren()) does not
 take
   getChildren() but _childrenList into account when creating the
 Iterator.
   This one was hard to find...
  
   I will create a JIRA issue for this and fix it asap.
  
   Regards,
   Jakob
  
   2010/3/17 Matthias Wessendorf mat...@apache.org
  
On Wed, Mar 17, 2010 at 4:27 AM, Bruno Aranda brunoara...@gmail.com
 
wrote:
 Hi,

 In my fancy little webapp I am using Primefaces dataTable in lazy
  mode
such
 as in this example[1], and I want to use it with MyFaces 2. However
   there
 seems to be a bug and the component decoding is not invoked, so if
  you
 navigate to another page of the table the row index does not
 change.

 It can be reproduced just getting the primefaces showcase examples:

 svn co
http://primefaces.googlecode.com/svn/examples/trunk/prime-showcase

 Then replacing the MyFaces 2 dependencies in the profile to the
  latest
(it
 does not work either with Myfaces 2.0.0-beta or beta2). And run the
showcase
 with:

 mvn jetty:run-exploded -Pmyfaces-2.0
   
oh, that's not the default?
Pretty odd, especially since the stuff is from a committer ;-)
   
@NotSerializableException: IMO it is ok to have that exception,
since the bean is in session and not implements the right contract
for passivation... (= demo bug)
   
-Matthias
   

 If you modify slightly the dataTable example so it shows the first
   result
in
 one column (by modifying the TableBean class), you will see it is
   always
0.

 A debugging session shows that the decode for dataTable renderer is
   never
 invoked. I am a bit rusty with all this, does any one have an idea
  what
may
 be happening or what could I look to pinpoint the problem?

 Thanks,

 Bruno

 [1]
  http://www.primefaces.org:8080/prime-showcase/ui/datatableLazy.jsf

   
   
   
--
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


Re: Issue with running myfaces-example-simple-1_1_9_war on websphere 6.1

2010-03-17 Thread Ashish Kulkarni
Hi
This URL helped me solve this issue

http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14280127
http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14280127

On Fri, Mar 12, 2010 at 5:20 PM, Ashish Kulkarni 
ashish.kulkarn...@gmail.com wrote:

 Hi
 I tried this also, i am getting following error in my system.out log file

 Any ideas

 [3/12/10 11:16:53:904 EST] 0015 WebAppE   Exception caught
 while initializing context
 javax.xml.parsers.FactoryConfigurationError: Provider for
 javax.xml.parsers.SAXParserFactory cannot be found
 at javax.xml.parsers.SAXParserFactory.newInstance(Unknown Source)
  at org.apache.commons.digester.Digester.getFactory(Digester.java:500)
 at org.apache.commons.digester.Digester.getParser(Digester.java:714)
  at org.apache.commons.digester.Digester.getXMLReader(Digester.java:944)
 at org.apache.commons.digester.Digester.parse(Digester.java:1745)
  at
 org.apache.myfaces.config.impl.digester.DigesterFacesConfigUnmarshallerImpl.getFacesConfig(DigesterFacesConfigUnmarshallerImpl.java:197)
 at
 org.apache.myfaces.config.FacesConfigurator.feedStandardConfig(FacesConfigurator.java:311)
  at
 org.apache.myfaces.config.FacesConfigurator.configure(FacesConfigurator.java:276)
 at
 org.apache.myfaces.webapp.StartupServletContextListener.initFaces(StartupServletContextListener.java:82)
  at
 org.apache.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:65)
 at
 com.ibm.ws.wswebcontainer.webapp.WebApp.notifyServletContextCreated(WebApp.java:652)
  at
 com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinish(WebApp.java:355)
 at com.ibm.ws.wswebcontainer.webapp.WebApp.initialize(WebApp.java:292)
  at
 com.ibm.ws.wswebcontainer.webapp.WebGroup.addWebApplication(WebGroup.java:92)

 On Fri, Mar 12, 2010 at 2:50 PM, Jakob Korherr jakob.korh...@gmail.comwrote:

 Hi,

 Maybe your websphere 6.1 is one of the few containers that does not
 support
 adding listeners via TLD. Try adding the following to your web.xml:

 listener

  
 listener-classorg.apache.myfaces.webapp.StartupServletContextListener/listener-class
 /listener

 Regards,
 Jakob


 2010/3/12 Ashish Kulkarni ashish.kulkarn...@gmail.com

  Hi
  I recently downloaded and installed myfaces-example-simple-1_1_9_war
 on
  websphere 6.1 (6.1.0.23) and  changed class loaded order to Classed
 loaded
  with application class loaded first, and then restarted the application
 and
  i got following error
 
  What am i missing
  *
  *
 
  *java.lang.IllegalStateException: No Factories configured for this
  Application. This happens if the faces-initialization does not work at
  all - make sure that you properly include all configuration settings
  necessary for a basic faces application and that all the necessary
  libs are included.
 
   Make sure that the JSF-API (myfaces-api-xxx.jar) is not included
  twice on the classpath - if not, the factories might be configured in
  the wrong class instance.
 
  If you use Tomcat, it might also pay off to clear your
  /[tomcat-installation]/work/ directory - Tomcat sometimes stumbles
  over its own tld-cache stored there, and doesn't load the
  StartupServletContextListener.
 
  Also check the logging output of your web application and your
  container for any exceptions!
  If you did that and find nothing, the mistake might be due to the fact
  that you use one of the very few web-containers which do not support
  registering context-listeners via TLD files and a context listener is
  not setup in your web.xml.
 
  Add the following lines to your web.xml file to work around this issue :
 
  listener
 
 
  
 listener-classorg.apache.myfaces.webapp.StartupServletContextListener/listener-class
  /listener
 at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:110)
 at javax.faces.webapp.FacesServlet.init(FacesServlet.java:99)
 at
 
 com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:226)
 at
 
 com.ibm.ws.wswebcontainer.servlet.ServletWrapper.init(ServletWrapper.java:320)
 at
 
 com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:434)
 at
 
 com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:481)
 at
  com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3453)
 at
  com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:267)
 at
 
 com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:815)
 at
 
 com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1466)
 at
 
 com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:119)
 at
 
 com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:458)
 at
 
 com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:387)
 at