t:columns and findComponent
---
Key: TOMAHAWK-1105
URL: https://issues.apache.org/jira/browse/TOMAHAWK-1105
Project: MyFaces Tomahawk
Issue Type: Bug
Affects Versions: 1.1.6
Reporter: Daniel Herb
Hi,
You're correct simple="true" is causing this, because you've not specified a
. The alert you're seeing is a developer warning
that you've not provided a destination for messages on that component.
On 9/4/07, saurabh (JIRA) wrote:
>
> Getting validation error as alert instead of inline
> ---
Getting validation error as alert instead of inline
---
Key: TRINIDAD-689
URL: https://issues.apache.org/jira/browse/TRINIDAD-689
Project: MyFaces Trinidad
Issue Type: Bug
Components:
[
https://issues.apache.org/jira/browse/TRINIDAD-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danny Robinson resolved TRINIDAD-687.
-
Resolution: Fixed
Fix Version/s: 1.0.3-core
Added tr:panelCaptionGroup component
does not completely recover from submitted date/time
formatting/validation errors
---
Key: TOMAHAWK-1104
URL: https://issues.apache.org/jira/browse/TOMAHAWK-1104
Apply icons and css styles to each message rendered by tr:messages
--
Key: TRINIDAD-688
URL: https://issues.apache.org/jira/browse/TRINIDAD-688
Project: MyFaces Trinidad
Issue T
[
https://issues.apache.org/jira/browse/TRINIDAD-667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer updated TRINIDAD-667:
Resolution: Fixed
Fix Version/s: 1.0.3-core
Status: Resolved (was: Patch Availa
[
https://issues.apache.org/jira/browse/TRINIDAD-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer resolved TRINIDAD-679.
-
Resolution: Fixed
Fix Version/s: 1.0.3-core
Assignee: Adam Winer
Fixed, thanks
I am getting this error in MyFaces 1.1.5 / Tomahawk 1.1.7-SNAPSHOT. I
am not using JSCookMenu, Calendar or the TabbedPane. If I get it again
I will see if I can get more information on this.
The tomahawk/sandbox components that I am using mostly are
panelNavigation2, focus, roundedDiv and messages
For http://issues.apache.org/jira/browse/TRINIDAD-679:
LabeledFacesMessage's "label" property is currently extremely
obscure in that it can store either a ValueBinding or a String
(or in JSF 1.2, a ValueExpression). That's needed to support
f:loadBundle-based labels, but is totally undocumented.
Derek,
We just started seeing our Web application hanging this last week to too many
open files (Switched over to tomahawk 1.1.5 about two weeks ago and use both
the calendar function and the JSCookMenu). I saw your post here and was
wondering two things. First, do you know if the new version
Create a tr:panelCaptionGroup component to render fieldset/legend style content
grouping
Key: TRINIDAD-687
URL: https://issues.apache.org/jira/browse/TRINIDAD-687
On 9/4/07, Danny Robinson <[EMAIL PROTECTED]> wrote:
>
> > > I've just noticed the xOffset and YOffset properties of the panelPopup
> are
> > > behaving strangely. It seems like they are not correctly generated
> > > somewhere in build process.
> >
> > Is this 1.1 or 1.2?
>
> 1.1 trunk.
>
> > > If
Tag documentation in frames on the web site
---
Key: TRINIDAD-686
URL: https://issues.apache.org/jira/browse/TRINIDAD-686
Project: MyFaces Trinidad
Issue Type: Wish
Components: Documentation
I don't have the time at the moment, so go ahead once you have the
chance if you want. If I end up having the time. Shall we use the
assign/currently working on functionality of JIRA to make sure we
don't step on each others toes?
I just thought to drop in my wish list for the features I have thou
are you working on the panelPopup issues you've raised. I'd like to, but
I'm going to fix some c/s validation stuff first in my priority list. I do
have a prototype TrDragDrop.js class if you want it.
D.
On 9/4/07, Andrew Robinson (JIRA) wrote:
>
> Provide a way to have tr:panelPopup more easi
On 9/4/07, Danny Robinson <[EMAIL PROTECTED]> wrote:
>
> > I think that autoSubmit code should automatically call _validateInput
> > on its own - that is, we probably need a new JS method that will:
> > - run _validateInput() on the target field
> > - run the equivalent of the existing adfspu c
[
https://issues.apache.org/jira/browse/TRINIDAD-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524803
]
Danny Robinson commented on TRINIDAD-673:
-
Line 626
var pos = this._getEventPosition(popup);
should be
[
https://issues.apache.org/jira/browse/TRINIDAD-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524795
]
Matthias Weßendorf commented on TRINIDAD-682:
-
-see NumberConverter.js for "TODO matzew - TRINIDAD-682"
> This is a bit overmuch - it isn't a "thumbs-up/thumbs-down"
> process, where we take it as is or leave it. It's a collaborative
> design process. We discuss, we hopefully come to consensus.
> Calling for a vote up front is unproductive.
>
> And there don't need to be "fatal flaws", and we don't
Provide a way to have tr:panelPopup more easily rendered with rounded corners
or other type of similar skining
--
Key: TRINIDAD-685
URL: https://issues.apa
tr:panelPopup to provide resizing capabilities
--
Key: TRINIDAD-684
URL: https://issues.apache.org/jira/browse/TRINIDAD-684
Project: MyFaces Trinidad
Issue Type: Wish
Components: Componen
tr:panelPopup extend title bar functionality
Key: TRINIDAD-683
URL: https://issues.apache.org/jira/browse/TRINIDAD-683
Project: MyFaces Trinidad
Issue Type: Wish
Components: Components
[
https://issues.apache.org/jira/browse/TOMAHAWK-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cagatay Civici updated TOMAHAWK-1103:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> PasswordStrength
> > 663
> I'd really like to hear a concrete example of where this is absolutely
> necessary. This is a very abstract description that is mostly
> "I need functionality X because I need to do X", which is a tautology.
> It's also very difficult for me to judge why this component needs
> to su
+1
Everything works fine with me except one little thing extremely specific to
my usage where LocaleElement getting null during inputDate popup closing
when using delegate renderer for SimpleInputDateRenderer. I'm probably the
one of the few on the planet to have that use case and I'll fix it befo
>
> I think that autoSubmit code should automatically call _validateInput
> on its own - that is, we probably need a new JS method that will:
> - run _validateInput() on the target field
> - run the equivalent of the existing adfspu code
>
> Maybe TrPage._autoSubmit()?
... and refactor the Au
Overhaul of NumberFormat.js / Coreformat.js files
-
Key: TRINIDAD-682
URL: https://issues.apache.org/jira/browse/TRINIDAD-682
Project: MyFaces Trinidad
Issue Type: Improvement
Repor
Martin, I have them listed in the project's main POM file. It's
basically Michael Freedman, Lei Oh, and myself.
Scott O'Bryan
Martin Marinschek wrote:
Anyone else who contributed to the bridge from within Oracle?
regards,
Martin
On 9/3/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
How are you getting the stylesheet reference into the header now?
JSR-168 does not have a means of doing this.
Scott
Martin Marinschek wrote:
Yes, sure - it's the same problem. I've added it via javascript to the
head, works as well. Just adding it somewhere in the content might
work, but is
>
> > I've just noticed the xOffset and YOffset properties of the panelPopup
> are
> > behaving strangely. It seems like they are not correctly generated
> > somewhere in build process.
>
> Is this 1.1 or 1.2?
1.1 trunk.
> If I try and use them in JSP page, then page
> > errors, and in Facelets
On 9/4/07, Danny Robinson <[EMAIL PROTECTED]> wrote:
> Guys,
>
> I've just noticed the xOffset and YOffset properties of the panelPopup are
> behaving strangely. It seems like they are not correctly generated
> somewhere in build process.
Is this 1.1 or 1.2?
> If I try and use them in JSP page,
Guys,
I've just noticed the xOffset and YOffset properties of the panelPopup are
behaving strangely. It seems like they are not correctly generated
somewhere in build process. If I try and use them in JSP page, then page
errors, and in Facelets they are available in the bean, but only as
Strings
Andrew,
This is a bit overmuch - it isn't a "thumbs-up/thumbs-down"
process, where we take it as is or leave it. It's a collaborative
design process. We discuss, we hopefully come to consensus.
Calling for a vote up front is unproductive.
And there don't need to be "fatal flaws", and we don't a
I'm actually only a contributor to the Richclient Incubator project.
I'm not a MyFaces committer just yet.
Martin Marinschek wrote:
Hey *,
do all 301 developers (how many are there with contributions to the
301-code?) have ICLAs on file? Scott, Michael, anyone else?
regards,
Martin
Adam and the Trinidad developers,
As for these two components, they are simply utility components to
provide users more flexibility in the ways they wish to use the
trinidad tools. Both of them do not affect the framework of Trinidad
and are optional if people want to use them or not.
(As request
I think that autoSubmit code should automatically call _validateInput
on its own - that is, we probably need a new JS method that will:
- run _validateInput() on the target field
- run the equivalent of the existing adfspu code
Maybe TrPage._autoSubmit()?
BTW, I think we should start making a
+1
On 9/2/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I was running the needed tasks to get the 1.2.2 release of the Apache
> MyFaces Trinidad CORE out. The artifacts are deployed to my private
> Apache account ([1]).
>
> Please take a look at the "1.2.2" artifacts and vote
>
>
pinging for responses.
On 8/29/07, Danny Robinson <[EMAIL PROTECTED]> wrote:
>
> Folks,
>
> Need some pointers here. I've mainly got the event based c/s validation
> working fine. However, this morning we uncovered an issue that needs some
> of your feedback. Basically, we're registering the _v
On 9/4/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> As soon as I get a bit of time ;) I will send you a testcase.
>
> But the setup should not be difficult to produce: Use Seam 2.0Beta
> and combine it with tr:table. Then do a bit of paging. Sooner or later,
> you get the error.
Th
On 9/4/07, Andrew Robinson <[EMAIL PROTECTED]> wrote:
> I say that there was such a method in the RenderUtils. The method
> there does not support the "::" syntax.
It should...
> The function is not rendering
> specific, it can be used during even broadcasting, decoding and other
> phases as well
On 9/3/07, Andrew Robinson <[EMAIL PROTECTED]> wrote:
> Guess I didn't leave adequate time. I took the lack of response in a
> days time to be no negative opinion. I can always move them back out
> and put them into jsf-comp as I know people will make use of them.
That'd be great, thanks.
> Let
I say that there was such a method in the RenderUtils. The method
there does not support the "::" syntax. The function is not rendering
specific, it can be used during even broadcasting, decoding and other
phases as well. That is why I felt that it should be on
ComponentUtils, since it is a method
Hi Dennis,
i came accross this bug several months ago and i had even asked here
in list.
Subject: [tabbedPane example] bug confirmation???*
* excerpt
I tried to run example several times (both locally built and on irian.at
night build), but i'm getting several results
WITHOUT modifying
For the bottom tab component, if I click on the third tab, click on the
second tab, and click on the third tab again ...
java.lang.IllegalArgumentException - Value is no String (class=
org.apache.myfaces.shared_tomahawk.renderkit.RendererUtils$1, value=
[EMAIL PROTECTED]) and
component _idJsp0:pan
Bad init param causes infinite loop
---
Key: JSR301-1
URL: https://issues.apache.org/jira/browse/JSR301-1
Project: MyFaces Portlet Bridge
Issue Type: Bug
Components: General
Affects Versions: 1.0
[
https://issues.apache.org/jira/browse/TRINIDAD-681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danny Robinson resolved TRINIDAD-681.
-
Resolution: Fixed
Fix Version/s: 1.0.3-core
Re-applied changes from rev 565851 t
Dave,
Not sure what happened here, but I've re-applied the previous patch
(TRINIDAD-681).
Thanks,
Danny
On 9/4/07, David Brunette <[EMAIL PROTECTED]> wrote:
>
>
>
> Working off of the latest Trinidad trunk, I'm having a problem with
> the styling of my tr:panelBox components if they come a
tr:messages - Causes tr:panelBox styles to be corrupted with tr:messages styles
---
Key: TRINIDAD-681
URL: https://issues.apache.org/jira/browse/TRINIDAD-681
Project: MyFaces
Poll component does not work
Key: TRINIDAD-680
URL: https://issues.apache.org/jira/browse/TRINIDAD-680
Project: MyFaces Trinidad
Issue Type: Bug
Components: Components
Affects Versions: 1.0.2-core
Hi,
the check for UIButtonCommand breaks the datePicker and one of my
custom components.
I changed this to check for javax.faces.component.UICommand.
Was there a reason for this specific check? The same problem may
occour with the LinkRenderer and maybe at some other places where the
check is to
Working off of the latest Trinidad trunk, I'm having a problem with
the styling of my tr:panelBox components if they come after a
tr:messages component. The panelBox components are getting class
attributes of "af_messeges_top-start" and such.
Looking at the SVN log for MessageBoxR
52 matches
Mail list logo
