Btw. Howard could you blog what you did for the migration, this might
interest other users as well.
Werner
Am 22.11.12 17:16, schrieb Howard W. Smith, Jr.:
+1 Werner's response, too. Thanks for that response, so I know where to
file relevant issues and which email list to send to, but honestly, I think
this issue should go to TomEE as well as MyFaces user lists, because others
may be using MyFaces Core (like myself).
Mark,
FYI, for some/whatever reason, I added JUEL jar to tomee /lib, and it has
'lived' there ever since, and my app is running well with it (since I have
context-parm in web.xml referencing juel). I just have to find and resolve
any issues I have, and as you have already noticed, I like to communicate
issues I have as well as 'my workarounds' to these issues. I always do what
I can to workaround issues that I'm confronted with. :)
IMHO, some weeks ago, I didn't find tomcat7 'easy' at all, and I 'found'
TomEE 'easier' than tomcat7. That may be a more accurate way of saying
it...at least from the community of users migrating from 'Glassfish' to
tomcat7. TomEE and the really-great (Apache) user community is the
solution!!! :)
File an issue. I love filing issues and providing as many details as
possible. I just need the experiencing of filing a new issue, and then I
should be set/fine, going forward.
I'll read [1][2] that you provided and respond accordingly or as necessary.
Thanks,
Howard
On Thu, Nov 22, 2012 at 5:46 AM, Mark Struberg <strub...@yahoo.de> wrote:
+1
Howard, as most other stuff is now working, we can continue with getting
back JUEL in place. But please file a tomcat issue for the EL stuff first!
For TomEE it's as easy as for tomcat7. A long time ago I wrote up a
description in our wiki [1] which is basically still true.
There is also some info on the juel page [2].
[1] http://wiki.apache.org/myfaces/HowToEnableEl22
[2] http://juel.sourceforge.net/guide/service.html
----- Original Message -----
From: Werner Punz <werner.p...@gmail.com>
To: MyFaces Discussion <users@myfaces.apache.org>
Cc:
Sent: Thursday, November 22, 2012 9:48 AM
Subject: Re: Migration to TomEE/CODI: very strange AJAX issue during
regression testing
If there is an EL struggling problem then this is probably a tomcat
issue. Tomcat is providing the EL in tomee to my knowledge.
Werner
Am 22.11.12 00:07, schrieb Howard W. Smith, Jr.:
I think I just solved this issue as follows:
*CAUSED BY:* p:calendar
*readonlyInput="#{pf_usersController.loggedInViaIpad
== 'Y' ? 'true' : 'false'}"*
1. Glassfish 3.1.2.2 and MyFaces Core 2.1.9 handles that perfectly
2. OpenWebBeans and MyFaces Core 2.1.9 seem to struggle with that
EL
for
whatever reason
3. So, I made it easy on OpenWebBeans and moved that EL to
rendered="...", and conditionally render separate components
with a
readonlyInput="true" only for iPad device/endusers
*CODE CHANGES* below:
<h:outputText value="From:" />
<p:calendar id="filterTripDateFrom"
value="#{pf_ordersController.filterTripDateFrom}"
mode="popup" showOn="button"
navigator="true" effect="fadeIn"
pattern="MM/dd/yyyy" size="10"
rendered="#{pf_usersController.loggedInViaIpad ==
'N'}">
<p:ajax partialSubmit="false"
event="dateSelect"
listener="#{pf_ordersController.filterTripDateFromSelected}"
update=":ordersBrowseForm:ordersDataTable
:ordersBrowseForm:formMessages :ordersBrowseForm:_ajax_status" />
</p:calendar>
<p:calendar id="filterTripDateFromOnIpad"
value="#{pf_ordersController.filterTripDateFrom}"
mode="popup" showOn="button"
readonlyInput="true"
navigator="true" effect="fadeIn"
pattern="MM/dd/yyyy" size="10"
rendered="#{pf_usersController.loggedInViaIpad ==
'Y'}">
<p:ajax partialSubmit="false"
event="dateSelect"
listener="#{pf_ordersController.filterTripDateFromSelected}"
update=":ordersBrowseForm:ordersDataTable
:ordersBrowseForm:formMessages :ordersBrowseForm:_ajax_status" />
</p:calendar>
<h:outputText value="To:" />
<p:calendar id="filterTripDateTo"
value="#{pf_ordersController.filterTripDateTo}"
mode="popup" showOn="button"
navigator="true" effect="fadeIn"
pattern="MM/dd/yyyy" size="10"
rendered="#{pf_usersController.loggedInViaIpad ==
'N'}">
<p:ajax partialSubmit="false"
event="dateSelect"
listener="#{pf_ordersController.filterTripDateToSelected}"
update=":ordersBrowseForm:ordersDataTable
:ordersBrowseForm:formMessages :ordersBrowseForm:_ajax_status" />
</p:calendar>
<p:calendar id="filterTripDateToOnIpad"
value="#{pf_ordersController.filterTripDateTo}"
mode="popup" showOn="button"
readonlyInput="true"
navigator="true" effect="fadeIn"
pattern="MM/dd/yyyy" size="10"
rendered="#{pf_usersController.loggedInViaIpad ==
'Y'}">
<p:ajax partialSubmit="false"
event="dateSelect"
listener="#{pf_ordersController.filterTripDateToSelected}"
update=":ordersBrowseForm:ordersDataTable
:ordersBrowseForm:formMessages :ordersBrowseForm:_ajax_status" />
</p:calendar>
On Wed, Nov 21, 2012 at 3:19 PM, Howard W. Smith, Jr. <
smithh032...@gmail.com> wrote:
The following is the XHTML for the *FROM* and *TO* p:calendar
components
in PrimeFaces p:dataTable component. Please note that the
*mode="popup"
showOn="button"* is hardcoded in the xhtml below, and is not
conditionally dependent on EL.
As the screen captures will show, I am testing this via my
test/development server, so please do not think I'm testing from
iPad
(since there is EL for iPad devices below).
This issue is not happening in the Production environment (Glassfish
3.1.2.2 and MyFaces Core 2.1.9).
<p:calendar id="filterTripDateFrom"
value="#{pf_ordersController.filterTripDateFrom}"
mode="popup" showOn="button"
readonlyInput="#{pf_usersController.loggedInViaIpad == 'Y'
? 'true' :
'false'}"
navigator="true" effect="fadeIn"
pattern="MM/dd/yyyy" size="10">
<p:ajax partialSubmit="false"
event="dateSelect"
listener="#{pf_ordersController.filterTripDateFromSelected}"
update=":ordersBrowseForm:ordersDataTable
:ordersBrowseForm:formMessages :ordersBrowseForm:_ajax_status"
/>
</p:calendar>
<h:outputText value="To:" />
<p:calendar id="filterTripDateTo"
value="#{pf_ordersController.filterTripDateTo}"
mode="popup" showOn="button"
readonlyInput="#{pf_usersController.loggedInViaIpad == 'Y'
? 'true' :
'false'}"
navigator="true" effect="fadeIn"
pattern="MM/dd/yyyy"
size="10">
<p:ajax partialSubmit="false"
event="dateSelect"
listener="#{pf_ordersController.filterTripDateToSelected}"
update=":ordersBrowseForm:ordersDataTable
:ordersBrowseForm:formMessages :ordersBrowseForm:_ajax_status"
/>
</p:calendar>
On Wed, Nov 21, 2012 at 3:06 PM, Howard W. Smith, Jr. <
smithh032...@gmail.com> wrote:
You all know by now that I recently migrated
*FROM*: Glassfish 3.1.2.2, MyFaces 2.1.9, and JSF Managed beans
*TO*: TomEE 1.5 SNAPSHOT, Apache MyFaces CDI Extensions 1.0.6
(CODI),
and CDI managed beans
So, I am regression testing, and I am experiencing a very very
strange
issue with *TomEE/CODI* (development/test environment) that I have
never
seen with *Glassfish 3.1.2.2 *and* MyFaces 2.1.9* (currently in
production).
Attached you will find screen captures:
1. Page that shows *FROM* and *TO* (PrimeFaces) p:calendar
components
(jQuery DatePicker) that has *button* beside the textInput
2. Page that shows FROM and TO p:calendar components *without
the
button* beside textInput; this is an issue and *not* working as
designed; this happens *sporadically after AJAX update* on the
page,
after I click the p:calendar button to update the data on the
page via AJAX
Someone please open an issue for this, and let me know if this is a
TomEE/OpenEJB issue *or* MyFaces Core 2.1.9 and CODI issue. This is
the
reason why I am sending this email to both user mail lists.
Thanks,
Howard
