Another thing which is still missing for promotion of the pprPanelGroup
is the site-documentation (thats required for promotion as well).
There are also some issues left in JIRA which I wanted to fix before promotion
but didn't find the time so far...
speaking of TOMAHAWK-1226 TOMAHAWK-1227
[
https://issues.apache.org/jira/browse/TOMAHAWK-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12587779#action_12587779
]
Ernst Fastl commented on TOMAHAWK-1226:
---
In order to resolve this issue, I suggest
Sounds like a good idea. While we are at that we could also add a general
before- and afterUpdateJSHook=jsFunction which will be executed
before and after the group has been updated. this way users could for instance
implement their own loading message display or just postprocess the updated
, 2008 at 9:53 AM, a clem [EMAIL PROTECTED] wrote:
On Fri, Mar 28, 2008 at 9:41 AM, Ernst Fastl [EMAIL PROTECTED] wrote:
+1 for ExternalContextUtils
Good idea Scott
In this case I wait for those utils before doing the changes in the
PPRPhaseListener
greez
[
https://issues.apache.org/jira/browse/TOMAHAWK-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12583508#action_12583508
]
Ernst Fastl commented on TOMAHAWK-1215:
---
At first I'd like to point out
+1 for ExternalContextUtils
Good idea Scott
In this case I wait for those utils before doing the changes in the
PPRPhaseListener
greez
E
On Fri, Mar 28, 2008 at 1:15 AM, Scott O'Bryan [EMAIL PROTECTED] wrote:
Take a look at Trinidad's ExternalContextUtils class. It uses
reflection. I'm
This seems to be addressing the more general JSF Problem immediate is
not enough
which the subForm tries to solve. I personally would dream of instead
of just required=true|false
requiredFor=buttonId1,buttonId2,... but that might just be an IDEA
for JSF 2.0.
The reason PPR uses a PhaseListener is
[EMAIL PROTECTED] wrote:
I would not recommend forceSpan as an attribute as the use of a span
is renderer specific, not component specific. The component should not
care how the renderer works
On Tue, Mar 25, 2008 at 4:41 PM, Ernst Fastl [EMAIL PROTECTED]
wrote
PROTECTED] wrote:
Hi,
custom lifecycles are possible in jsf1.1, tobago has a custom
lifecycle which integrates the ajax (ppr) into the normal jsf
lifcycle. in case of ajax the process* methods are only run on the
partially requested components.
Regards,
Volker
2008/3/27, Ernst
[
https://issues.apache.org/jira/browse/TOMAHAWK-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12582807#action_12582807
]
Ernst Fastl commented on TOMAHAWK-1215:
---
solved with two new attributes
[
https://issues.apache.org/jira/browse/TOMAHAWK-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernst Fastl resolved TOMAHAWK-1215.
---
Resolution: Fixed
Fix Version/s: 1.1.7-SNAPSHOT
Add a communication channel
hi guys,
seems like the maven build is broken. I get
[INFO] Failed to resolve artifact.
GroupId: org.apache.myfaces
ArtifactId: myfaces
Version: 5-SNAPSHOT
I would fix it myself - unfortunatly I'm not a maven export :(
has anyone a got a clue what happend
for me it worked just 2 days ago
Issue Type: Bug
Components: PPRPanelGroup
Affects Versions: 1.1.7-SNAPSHOT
Reporter: Ernst Fastl
Assignee: Ernst Fastl
Fix For: 1.1.7-SNAPSHOT
Since findComponent returns UiComponentPerspective for client Ids within a
dataTable
Hi,
I think it would be good to have
UIComponentPerspective.setupPerspective and
UIComponentPerspective.teardownPerspective public.
Just take the ugly ugly workaround in the fix for TOMAHAWK-1218 as an
example why this would be a good idea.
Has anybody got objections or a different idea of how
[
https://issues.apache.org/jira/browse/TOMAHAWK-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernst Fastl resolved TOMAHAWK-1218.
---
Resolution: Fixed
resolved by handling UiComponentPerspective correctly
Hi,
I would like to add renderedIfEmpty to the t:messages component which
per default is false (current behaviour)
The reason for that: To update/append FacesMessages to a
messages-component after AJAX requests (e.g. PPR)
it has to be possible to locate a DOM element to which this messages
can be
Hi,
I believe the tomahawk component t:message does something similar to
what you want.
At least it displays the label instead of the id). Maybe you can use
that one or just check
org.apache.myfaces.renderkit.html.ext.HtmlMessageRenderer and do
something similar
in a custom renderer.
cheers
, 2008-03-25 at 20:50 +0100, Ernst Fastl wrote:
Hi,
I would like to add renderedIfEmpty to the t:messages component which
per default is false (current behaviour)
The reason for that: To update/append FacesMessages to a
messages-component after AJAX requests (e.g. PPR
as an attribute as the use of a span
is renderer specific, not component specific. The component should not
care how the renderer works
On Tue, Mar 25, 2008 at 4:41 PM, Ernst Fastl [EMAIL PROTECTED] wrote:
Hi,
I like the idea of making that the default behavior. I think for
t:messages
Hi,
I just took a quick glance at the changes in the PPRPhaseListener.
What I've seen looks
alright so far and since I'm working on that class at the moment
anyway I'll be happy to
factor in those changes.
As for the DojoUtils, those are as far as I know mainly maintained by werner.
Maybe he
Issue Type: New Feature
Components: PPRPanelGroup
Reporter: Ernst Fastl
Assignee: Ernst Fastl
As any conventional JSF request PPR requests can lead to conversion and
validation errors or other
events which produce FacesMessages. The PPRPanelGroup should be enhanced
Excellent work guys! Looks great!
On Wed, Mar 19, 2008 at 9:26 PM, Scott O'Bryan [EMAIL PROTECTED] wrote:
Yeah, that would be most helpful I think.. Once again, good work.
Scott
Catalin Kormos wrote:
Sure, that will be changed. On the current website the publish date is
displayed
+1 from me
our demos may functually be complete but almost all other component vendors
enhance the user experience in their demos greatly by proper design
also looks better in presentations
I think we would attract more users with nicer CSS in the demos
Ernst
On Wed, Mar 19, 2008 at 10:08 PM,
[
https://issues.apache.org/jira/browse/TOMAHAWK-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12580077#action_12580077
]
Ernst Fastl commented on TOMAHAWK-1214:
---
Sound like a cool feature. There are 2
I would also go for the M since it is a name and not an instance variable :)
On Dec 10, 2007 12:59 AM, Catalin Kormos [EMAIL PROTECTED] wrote:
I also prefer M, as i always known MyFaces like that, and agreed with
Mathias for the naming convention Apache MyFaces, etc instead of Apache
myFaces,
Sounds great!
I believe this will be helpful in dealing with new JavaScript includes in PPR
responses ( TOMAHAWK-1054 ). Looking forward to checking it out :)
regards
Ernst
On 9/21/07, Mario Ivankovits [EMAIL PROTECTED] wrote:
Ok, I've found the first problem, the stylesheets were inserted
Hi Mario!
thanks for pointing out this issues.
I must have missed the point where
this log got in - my guess is that it can optionally be defined or turned on
in dojo or something. However I would think a check wether or not the object
is defined before using it cannot hurt.
@whoever did this -
Components: PPRPanelGroup
Affects Versions: 1.1.6
Reporter: Ernst Fastl
Assignee: Ernst Fastl
Fix For: 1.1.7-SNAPSHOT
form elements arrays are iterated instead of just the input elements while
registering partialTriggerPatterns
--
This message
Issue Type: Bug
Components: PPRPanelGroup
Affects Versions: 1.1.6
Reporter: Ernst Fastl
Assignee: Ernst Fastl
Fix For: 1.1.7-SNAPSHOT
If multiple partialTriggers or patterns match for an input component, the
event-handler advices
[
https://issues.apache.org/jira/browse/TOMAHAWK-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernst Fastl resolved TOMAHAWK-1089.
---
Resolution: Fixed
PPRPanelGroupRenderer should obtain the encoding from
: PPRPanelGroup
Affects Versions: 1.1.6
Reporter: Ernst Fastl
Assignee: Ernst Fastl
Fix For: 1.1.7-SNAPSHOT
Provide an easy to use javascript method for updating the content of
pprpanelgoups and other components
which render html tags with ids like
oamPPRUpdate
Project: MyFaces Tomahawk
Issue Type: New Feature
Components: PPRPanelGroup
Affects Versions: 1.1.6
Reporter: Ernst Fastl
Assignee: Ernst Fastl
Fix For: 1.1.7-SNAPSHOT
build easy to use Util classes in order to enable other custom
Components: PPRPanelGroup
Affects Versions: 1.1.6
Reporter: Ernst Fastl
Assignee: Ernst Fastl
Priority: Minor
Fix For: 1.1.7-SNAPSHOT
dojo.io.bind which is used by the pprPanelGroup uses the encoding set in the
dojoConfig
since we don't yet
Hi,
Might be an option too. I thought it best to return the client the
encoding he requests. Maybe the responseWriter-encoding
should be used before the hardcoded default.
Where does the responseWriter get the encoding from?
Is that configured?
cheers
Ernst
On 8/15/07, Mario Ivankovits [EMAIL
Hi,
I just checked - the commits are definitly in the SVN. These commit
emails are auto-generated right? do I need to set something in
my SVN client for that to work?
regards
Ernst
On 7/16/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
hi,
I saw that Ernst fixed some tomahawk stuff, but I
Issue Type: Bug
Components: PPRPanelGroup
Affects Versions: 1.1.6
Reporter: Ernst Fastl
Assignee: Ernst Fastl
Priority: Minor
Fix For: 1.1.7-SNAPSHOT
Transient components like html in facelets templates or text in verbatim
Project: MyFaces Tomahawk
Issue Type: Bug
Components: PPRPanelGroup
Affects Versions: 1.1.6
Reporter: Ernst Fastl
Assignee: Ernst Fastl
Priority: Minor
Fix For: 1.1.7-SNAPSHOT
Some components render inline JavaScript . If those
: PPRPanelGroup
Affects Versions: 1.1.6
Reporter: Ernst Fastl
Assignee: Ernst Fastl
Priority: Minor
Fix For: 1.1.7-SNAPSHOT
When components which previously had not been rendered appear additional
JS-includes are
not included. Somehow it would
Hi everyone!
Cool that we use templating now. However after a recent checkout
I ran into the problem that whenever I have an output text which
has a value = null I got:
javax.servlet.jsp.JspException: Expression text is undefined on line
1, column 3 in outputText_children.ftl.
I then changed
[
https://issues.apache.org/jira/browse/TOMAHAWK-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernst Fastl resolved TOMAHAWK-1052.
---
Resolution: Fixed
Solution:
In the PPRPanelGroupRenderer encodeBegin method
[
https://issues.apache.org/jira/browse/TOMAHAWK-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernst Fastl resolved TOMAHAWK-1055.
---
fixed by initially iterating over the form elements and adding the
corresponding partial
[
https://issues.apache.org/jira/browse/TOMAHAWK-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernst Fastl updated TOMAHAWK-1042:
--
Resolution: Fixed
Fix Version/s: 1.1.7-SNAPSHOT
Status: Resolved
Hi!
At the moment the JavaScript function which are starting
with oam (e.g. oamSetHiddenInput, oamSubmit, ...)
are rendered at the first commandLink or commandButton.
Is there a special reason for not having those in, for instance
commons.js
The PPR JavaScript for instance uses the
Hi mario,
that is exactly the solution we had in mind for that problem.
Unfortunately I didn't have time to implement that so far because there
have always been more pressing issues. I hope I'll be able to do so
next week during ApacheCon.
regards
Ernst
On 4/26/07, Mario Ivankovits [EMAIL
on this, if found.
Should be easy to implement something like this in the
PPRPhaseListener for aliasScope,
a bit more complicated for aliasBean.
Regards,
Volker
2007/4/25, Ernst Fastl [EMAIL PROTECTED]:
Thaks for the info,
following stuff is missing:
-JavaDoc - I'll write that together
/26/07, Ernst Fastl [EMAIL PROTECTED] wrote:
Hi,
The PPRPhaseListener is called before RenderResponse so in my understanding
decode should have been called normally on all components.
The only thing
ommited is the normal rendering. Rather the PPRPhaseListener seeks the
affected components
look into this, but i wouldn`t say this is
kind of a blocker issue for promotion to tomahawk.
cheers,
Gerald
On 4/25/07, Ernst Fastl [EMAIL PROTECTED] wrote:
There is one issue I'd like to sort out before that:
https://issues.apache.org/jira/browse/TOMAHAWK-969
I hope I'll find time to do
: MyFaces Tomahawk
Issue Type: Bug
Components: PPRPanelGroup
Affects Versions: 1.1.6-SNAPSHOT
Reporter: Ernst Fastl
Fix For: 1.1.6-SNAPSHOT
If a PPRPanelGroup triggers on a button which is rendered after the
PPRPanelGroup the partial refresh does
There is one issue I'd like to sort out before that:
https://issues.apache.org/jira/browse/TOMAHAWK-969
I hope I'll find time to do that on the weekend or next week during the con.
other than that since I'm using the PPRPanelGroup sucessfully in 2
projects for 8 months now I have the feeling
Project: MyFaces Tomahawk
Issue Type: Bug
Components: PPRPanelGroup
Affects Versions: 1.1.6-SNAPSHOT
Reporter: Ernst Fastl
Fix For: 1.1.6-SNAPSHOT
all PPR examples which contain commandLinks produce Javascript errors instead
of submitting
when
[
https://issues.apache.org/jira/browse/TOMAHAWK-966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernst Fastl updated TOMAHAWK-966:
-
Status: Patch Available (was: Open)
PPR examples containing commandLinks produce javascript
Hi,
The PPR update is asynchronous, so it should not matter if the Dialog
pops up before or after the update. At least this is the way it works for me.
regards
Ernst
On 3/30/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
ok, lemme check the dojo behind ;)
On 3/30/07, Gerald Müllan [EMAIL
();
t:updateActionListener
property=#{table.detailCustomer} value=#{customer} /
h:outputText value=view details /
/h:commandLink
and presenting this inside the modalDialog...
value=#{detailCustomer.firstname}
.M
On 3/30/07, Ernst Fastl [EMAIL PROTECTED] wrote:
Hi,
The PPR update
you probably mean
typeof foo == undefined
vs
foo === undefined
but to be honest I was never really sure what the difference is.
If the latter is the better approach u can go ahead and replace
the statements, or I'll do it in the next patch.
regards
Ernst
On 3/30/07, Matthias Wessendorf
:42 2007
New Revision: 523853
URL: http://svn.apache.org/viewvc?view=revrev=523853
Log:
applied patch https://issues.apache.org/jira/browse/TOMAHAWK-945, Thx to
Ernst Fastl
Added:
myfaces/tomahawk/trunk/sandbox/examples/src/main/webapp/pprPanelGroupCommandLink.jsp
[
https://issues.apache.org/jira/browse/TOMAHAWK-945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485546
]
Ernst Fastl commented on TOMAHAWK-945:
--
Good idea, I wouldn't have liked that as well. thanks Jeff
Split
[
https://issues.apache.org/jira/browse/TOMAHAWK-945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernst Fastl updated TOMAHAWK-945:
-
Status: Patch Available (was: Open)
Split the PPR Example into smaller easy to understand
Hi!
I just split the PPR example into few simpler, easier to understand examples.
see TOMAHAWK-945 patch
While doing so I noticed, that the commandLinks in the examples won't submit
in firefox (haven't tried other browsers so far). In the file common.js the
renderMessages function gets called
: MyFaces Tomahawk
Issue Type: Improvement
Components: PPRPanelGroup
Affects Versions: 1.1.6-SNAPSHOT
Reporter: Ernst Fastl
Fix For: 1.1.6-SNAPSHOT
A lot of users have been complaining, that the sandbox PPR example is difficult
to understand
: Bug
Reporter: Ernst Fastl
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[
https://issues.apache.org/jira/browse/TOMAHAWK-909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernst Fastl updated TOMAHAWK-909:
-
Status: Patch Available (was: Open)
PPRPanelGroup ignores return value of false from custom
Hi,
a good starting point is always the myfaces wiki
http://wiki.apache.org/myfaces/
examples can be found at
http://www.irian.at/myfaces.jsf
scrolling a little down searching for MyFaces Examples you
will find links to the online examples which also
show the source code.
hope that helps
Hi again,
Thank you very much for your opinions and insights. I understand now that there
are doubts supporting such a feature. What I understood these are mainly
about encouraging users to use not best practise approaches. IMO this
is for sure a duty of teachers or books, but a webdevelopment
Issue Type: Bug
Affects Versions: 1.1.5-SNAPSHOT
Reporter: Ernst Fastl
Fix For: 1.1.5-SNAPSHOT
modalDialog shows in page instead of being a popup in Internet Explorer since
the lates changes in the DojoUtils stuff
I couldn't figure out why this doesn't work anymore
also wanna check some of the *extensions* in the MyFAcesNH_Impl
for accessing navigation cases. It is important in security cases to
*check* navigation cases ...
so your impl could benefit from that !
On 10/29/06, Ernst Fastl [EMAIL PROTECTED] wrote:
You're right, an alternate NavigationHandler
: MyFaces Tomahawk
Issue Type: Improvement
Components: PPRPanelGroup
Affects Versions: 1.1.4-SNAPSHOT
Reporter: Ernst Fastl
Priority: Minor
Fix For: 1.1.5-SNAPSHOT
Default behaviour if an exception occurs during a partial update
[ http://issues.apache.org/jira/browse/TOMAHAWK-758?page=all ]
Ernst Fastl updated TOMAHAWK-758:
-
Status: Patch Available (was: Open)
Enable traditional submit for exceptions during partial update to show error
pages
Putting the article in the wiki sounds like a good idea to me. Everybody
would have the possiblility of adding information and we would hopefully
also have a nice collection of information for new users.
btw. I'd also be interested in writing
regards
Ernst
On 10/26/06, Arash Rajaeeyan [EMAIL
Cool stuff,
there is also a similar new serachengine
http://www.krugle.com/
where you can search for code and projects
On 10/26/06, Kito D. Mann [EMAIL PROTECTED] wrote:
One of the coolest things I noticed in my vanity search was that it looks
inside zip files:
great idea,
maybe we could put the examples right after or before the screen shots
I have the impression, that many users like to first see an example
and then read additional information
regards
Ernst
On 10/27/06, Arash Rajaeeyan [EMAIL PROTECTED] wrote:
Hello All,
I want to synchronize the
Hi!
At the moment when no navigation case for an outcome is found
the navigationHandler decides to stay at the same view. I think
an option for web.xml would be useful to tell the navigationHandler
if no navigation case for an outcome is found, but the outcome
matches a viewId to navigate to
be forced to use the feature, I'd
say it's for starters and lazy programmers, the others can leave it
turned off.
All together, I see your points, but I don't understand
what harm could be caused by an optional feature?
On 10/30/06, Ernst Fastl [EMAIL PROTECTED] wrote:
Hi!
At the moment when
You're right, an alternate NavigationHandler shipped with MyFaces
is probably the better choice let's go with that approach.
thanks for your ideas
On 10/29/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
2) since in JSF 1.1 navigation outcomes are string it is completely possible
for a
Components: General
Affects Versions: 1.1.4
Reporter: Ernst Fastl
Priority: Minor
Fix For: 1.1.5-SNAPSHOT
Provide an alternative NavigationHandler Implementation that checks if an
outcome
for which no navigation Case could be identifiied matches
On one hand it is right that components of the sandbox are potential subjects
for change, but would it really hurt to do a slower deprecation? Like Werner
pointed out, some people are already using sandbox components in their
production environments although this may never have been recommended
files.
Before upgrading users should read the release notes anyway :-)
On 10/13/06, Werner Punz [EMAIL PROTECTED] wrote:
Ernst Fastl schrieb:
On one hand it is right that components of the sandbox are potential
subjects
for change, but would it really hurt to do a slower deprecation? Like
Hi Manmeet!
You could either write a new component similar to the SelectOneRow.
It would probably have two additional attributes like image and
selectedImage which renders an input type image.
or you could just use a normal image inide a commandLink.
The commandLink would then probably also
is empty the validation will fail. But for the rerendering of
the second selectbox this validation isn't necessary.
I hope it is clear, what I mean.
Best regards
Björn
-Ursprüngliche Nachricht-
Von: Ernst Fastl [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 27. September 2006 22:36
Hello everyone!
In the recent tomahawk issues related to the pprPanelGroup partial Page
Rendering has been improved in the following points:
-partialTriggers also work for commandLinks, selectOneMenu and
selectBooleanCheckBox (the last two still need onchange-Handlers)
-partialTriggers are
, the second one of your future plans; is it like an automatically
refresh after a given timeout? Seems very practicable to me.
cheers,
Gerald
On 9/27/06, Ernst Fastl [EMAIL PROTECTED] wrote:
Hello everyone!
In the recent tomahawk issues related to the pprPanelGroup partial Page
Rendering has
/browse/TOMAHAWK-707
Project: MyFaces Tomahawk
Issue Type: Bug
Components: PPRPanelGroup
Affects Versions: 1.1.5-SNAPSHOT
Reporter: Ernst Fastl
Priority: Minor
Fix For: 1.1.5-SNAPSHOT
PPRPanelGroup partialTriggerPattern js
Components: PPRPanelGroup
Affects Versions: 1.1.5-SNAPSHOT
Reporter: Ernst Fastl
Priority: Minor
Fix For: 1.1.5-SNAPSHOT
PPRPanelGroup should support an inline Loading Message to avoid Users clicking
on Elements
which are already rerequested from
[ http://issues.apache.org/jira/browse/TOMAHAWK-708?page=all ]
Ernst Fastl updated TOMAHAWK-708:
-
Status: Patch Available (was: Open)
PPRPanelGroup should support an inline Loading Message
[ http://issues.apache.org/jira/browse/TOMAHAWK-707?page=all ]
Ernst Fastl updated TOMAHAWK-707:
-
Status: Patch Available (was: Open)
PPRPanelGroup partialTriggerPattern js-function produces JS-error when
invoked with non-string object
/TOMAHAWK-695
Project: MyFaces Tomahawk
Issue Type: Bug
Components: PPRPanelGroup
Affects Versions: 1.1.5-SNAPSHOT
Reporter: Ernst Fastl
Priority: Minor
Fix For: 1.1.5-SNAPSHOT
If the ids of commandLinks, selectOneMenus
[ http://issues.apache.org/jira/browse/TOMAHAWK-695?page=all ]
Ernst Fastl updated TOMAHAWK-695:
-
Status: Patch Available (was: Open)
PPRPanelGroup partialTriggers don't work for commandLink, selectOneMenu and
selectBooleanCheckBox
Components: PPRPanelGroup
Affects Versions: 1.1.5-SNAPSHOT
Reporter: Ernst Fastl
Priority: Minor
Fix For: 1.1.5-SNAPSHOT
valueBindings can't be used for the partialTriggers Attribute
--
This message is automatically generated by JIRA.
-
If you think
[ http://issues.apache.org/jira/browse/TOMAHAWK-696?page=all ]
Ernst Fastl updated TOMAHAWK-696:
-
Status: Patch Available (was: Open)
PPRPanelGroup partialTriggers don't support ValueBindings
[ http://issues.apache.org/jira/browse/TOMAHAWK-697?page=all ]
Ernst Fastl updated TOMAHAWK-697:
-
Status: Patch Available (was: Open)
PPRPanelGroup panelGroup insert renderd spans into each other when repeatetly
refreshing
Project: MyFaces Tomahawk
Issue Type: Bug
Reporter: Ernst Fastl
Priority: Minor
If a page is refreshed partially more often the rendered span always inserts
itself into itself over and over again
--
This message is automatically generated by JIRA.
-
If you
: Bug
Components: PPRPanelGroup
Affects Versions: 1.1.5-SNAPSHOT
Reporter: Ernst Fastl
Priority: Minor
Fix For: 1.1.5-SNAPSHOT
This happens when the original Button onclick-Handler is called and the submit
function afterwards
--
This message
[
http://issues.apache.org/jira/browse/TOMAHAWK-695?page=comments#action_12437506
]
Ernst Fastl commented on TOMAHAWK-695:
--
the selectOneMenu-components and selectBooleanCheckBox need to call the
oamSubmitForm - funciton in the onChange
: PPRPanelGroup
Reporter: Ernst Fastl
Priority: Minor
partialTriggers currently only work within the form the PPRPanelGroup is
defined.
this should be enhanced by defining them on a per window basis to enable
updates from multiple forms
--
This message is automatically
[ http://issues.apache.org/jira/browse/TOMAHAWK-700?page=all ]
Ernst Fastl updated TOMAHAWK-700:
-
Status: Patch Available (was: Open)
enable shareing partialTriggers between Forms
-
Key
Issue Type: New Feature
Components: PPRPanelGroup
Affects Versions: 1.1.5-SNAPSHOT
Reporter: Ernst Fastl
Priority: Minor
Fix For: 1.1.5-SNAPSHOT
Support a new Attribute which takes a regular Expression. if the Client-ID of a
submitting component
[ http://issues.apache.org/jira/browse/TOMAHAWK-702?page=all ]
Ernst Fastl updated TOMAHAWK-702:
-
Status: Patch Available (was: Open)
PPRPanelGroup support a regular Expression as partialTrigger attribute
Components: New Component
Reporter: Ernst Fastl
Recent changes lead to an infinite recursion in the Button-onclick-handler
replacement functions if 2 or
more PanelGroups are used on the page.
To provide the intended functionality of the previous change the PPRCtrl
Objects should
[ http://issues.apache.org/jira/browse/TOMAHAWK-640?page=all ]
Ernst Fastl updated TOMAHAWK-640:
-
Status: Patch Available (was: Open)
Javascript-Code broken when using 2 or more PPRPanelGroups
, Ernst Fastl [EMAIL PROTECTED] wrote:
Hi,
If I understood the recent discussions correctly we should
create JIRA Issues seperately for every change we want to make
rather than Issues like Enhancing component x. Following
List are suggestions for improvements to the PPRPanelGroup.
1. Update
how to implement them yet. Also some of them will probably need to
be discussed like for instance the Client-Side State saving.
however, thanks for the support
kind regards
Ernst
On 8/28/06, Mike Kienenberger [EMAIL PROTECTED] wrote:
On 8/26/06, Ernst Fastl [EMAIL PROTECTED] wrote:
If I
1 - 100 of 122 matches
Mail list logo
