[
https://issues.apache.org/jira/browse/MYFACES-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497738
]
sarah haas commented on MYFACES-1563:
-
Hi Bruno
Thanks for your comment. But I'm not clear what you mean! The
[
https://issues.apache.org/jira/browse/TOMAHAWK-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Grimm updated TOMAHAWK-542:
-
Status: Patch Available (was: Open)
forceId does not work on dataTable
ContentType cannot be set when only text/* media range is accepted
--
Key: MYFACES-1641
URL: https://issues.apache.org/jira/browse/MYFACES-1641
Project: MyFaces Core
Issue
[
https://issues.apache.org/jira/browse/MYFACES-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497765
]
Bruno Aranda commented on MYFACES-1639:
---
In 1.2 the DTDs are not needed. They have been removed as they were
ReducedHTMLParser.java reports invalid line numbers
---
Key: TOMAHAWK-1005
URL: https://issues.apache.org/jira/browse/TOMAHAWK-1005
Project: MyFaces Tomahawk
Issue Type: Bug
Affects
[
https://issues.apache.org/jira/browse/TOMAHAWK-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Ryagin updated TOMAHAWK-1005:
-
Status: Patch Available (was: Open)
ReducedHTMLParser.java reports invalid line
rendering of DatePicker produces automatic id warning.
--
Key: TOBAGO-406
URL: https://issues.apache.org/jira/browse/TOBAGO-406
Project: MyFaces Tobago
Issue Type: Bug
Hi,
I have to develop a new JSF component (component, tag and renderer).
The goal of this new component is easy... Put together severals input zone in
one single component.
I have done somethink that works... But i'm not sure I did everything
correctly. (in the State of Art)
-- Should be
[
https://issues.apache.org/jira/browse/TOBAGO-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volker Weber resolved TOBAGO-406.
-
Resolution: Fixed
rendering of DatePicker produces automatic id warning.
I've always been of Manfred's opinion - it would be better to decouple
spec version numbers from implementation version numbers, so I'm...
+1 for MyFaces-Impl 2.0
if we don't do that, we force ourselves into an artifical corset in
which we cannot move - we can only increment minor version
Questions like this on the [EMAIL PROTECTED] list please.
Thanks,
Manfred
On 5/22/07, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Hi,
I have to develop a new JSF component (component, tag and renderer).
The goal of this new component is easy... Put together severals input zone
in one single
yes I am.
Adam, please try again.
(The project roles for trinidad where not properly assigned to the groups)
--Manfred
On 5/21/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
I mailed Martin on that already, on the myfaces-dev list.
Manfred, aren't you also a JIRA-Super-Admin ?
-M
On
for me - not a problem.
but:
this function is only available then if you use MyFaces as an
implementation, not the RI. So it's not a good idea to rely on this
function being there beforehand!
regards,
Martin
On 5/21/07, Ernst Fastl [EMAIL PROTECTED] wrote:
Hi!
At the moment the JavaScript
Hi, I can imagine a free evolution of myfaces-impl, but this would
come at a cost of incompatibility with the RI. If we add new
signatures and other artifacts depend on those signatures, that
artifact is depending in the implementation and cannot be used with
other implementations (e.g. RI). Is
What about performance enhancements?
regards,
Martin
On 5/22/07, Bruno Aranda [EMAIL PROTECTED] wrote:
Hi, I can imagine a free evolution of myfaces-impl, but this would
come at a cost of incompatibility with the RI. If we add new
signatures and other artifacts depend on those signatures,
MessageFactory.BindingFacesMessage resolves parameters only once
Key: TRINIDAD-28
URL: https://issues.apache.org/jira/browse/TRINIDAD-28
Project: MyFaces Trinidad
Issue Type:
https://issues.apache.org/jira/browse/TRINIDAD-28
Adam Winer píše v Pá 18. 05. 2007 v 10:55 -0700:
Yeah, looks like a good fix. I doubt the optimization of caching
here is buying us much of anything.
-- Adam
On 5/17/07, Martin Koci [EMAIL PROTECTED] wrote:
Hi,
[
https://issues.apache.org/jira/browse/TRINIDAD-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Koci updated TRINIDAD-28:
Status: Patch Available (was: Open)
MessageFactory.BindingFacesMessage resolves parameters only
I am also in agreement with Manfred's opinion.
If we tie the MyFaces version number to the spec, what do we do in the following
cases:
1) A fix to the spec is release, i.e. 1.2.1? It is very likely that MyFaces
releases
will be more frequent then spec releases, thus we can be faces with
Bruno,
Regardless if the version number, I would expect the community
and PMC would prevent this from occurring.
Paul Spencer
Bruno Aranda wrote:
Hi, I can imagine a free evolution of myfaces-impl, but this would
come at a cost of incompatibility with the RI. If we add new
signatures and other
It's working now. Thanks, Manfred!
-- Adam
On 5/22/07, Manfred Geiler [EMAIL PROTECTED] wrote:
yes I am.
Adam, please try again.
(The project roles for trinidad where not properly assigned to the groups)
--Manfred
On 5/21/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
I mailed Martin
[
https://issues.apache.org/jira/browse/TRINIDAD-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer updated TRINIDAD-24:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
JspUtils.getEncoding() blindly
Ok, I see your points of having a more flexible versioning of
myfaces-impl (as Martin says, myfaces-api is not going to change ever,
a part from bug fixing). The only thing is that I think is more
natural to the standard user to know which jsf is implemented by
looking just at the version of the
Volker Weber wrote:
the nightly builds are here:
http://people.apache.org/builds/myfaces/nightly/
Hmmm ... wer are on 1.1.6 for tomahawk, no? I can't find them in the
nightly directory.
Anyone knows whats wrong?
Ciao,
Mario
Hello all,
I'm a user of the MyFaces implementation of JSF and would like to give my
opinion on this.
It appair that there are two opinion on this issue based upon two motivations:
1) Lock the versionnumber of MyFaces to the specifications.
2) Use the common major.minor.patch-versioning-schema
Mario,
I started looking at this yesterday, but got side tracked. There used to be
a continuum task that copied the binaries from the continuum build area to
the nightly repository area. Unfortunately when the continuum config got
hosed, we lost that.
On 5/22/07, Mario Ivankovits [EMAIL
Just to follow up on this, it seems that the Tobago nightlies are
functioning perfectly! Perhaps we should follow their example and use
whatever method is in use ? It would be great to have a unified approach for
this across all component libs / apis.
On 5/22/07, Grant Smith [EMAIL PROTECTED]
[
https://issues.apache.org/jira/browse/MYFACES-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cagatay Civici resolved MYFACES-1641.
-
Resolution: Fixed
Fix Version/s: 1.1.6-SNAPSHOT
ContentType cannot be set
[
https://issues.apache.org/jira/browse/MYFACES-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Smith resolved MYFACES-1639.
--
Resolution: Fixed
Done.
Some DTDs hold Sun Microsystems copyrights.
t:panelNavigation2 does not render separators in list mode
--
Key: TOMAHAWK-1006
URL: https://issues.apache.org/jira/browse/TOMAHAWK-1006
Project: MyFaces Tomahawk
Issue Type: Bug
[
https://issues.apache.org/jira/browse/TOMAHAWK-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas LE BAS updated TOMAHAWK-1006:
-
Status: Patch Available (was: Open)
t:panelNavigation2 does not render separators
[
https://issues.apache.org/jira/browse/TOMAHAWK-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas LE BAS updated TOMAHAWK-1006:
-
Status: Open (was: Patch Available)
t:panelNavigation2 does not render separators
[
https://issues.apache.org/jira/browse/TOMAHAWK-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497931
]
Nicolas LE BAS commented on TOMAHAWK-1006:
--
Since I'm not familiar with the apache procedures, can
The Trinidad subclass of LengthValidator needs some work.
Changes I plan to make - feedback appreciated:
- The messages are copied from the LongRangeValidator, so
we say Enter a value greater than or equal to 5 instead
of Enter a value of 5 or more characters. (I'll use the latter)
- If min
On 5/22/07, Adam Winer [EMAIL PROTECTED] wrote:
The Trinidad subclass of LengthValidator needs some work.
Changes I plan to make - feedback appreciated:
- The messages are copied from the LongRangeValidator, so
we say Enter a value greater than or equal to 5 instead
of Enter a value of 5 or
Hi,
my guess is, that we need to release the plugins, before we start to
release the CORE.
Why? Because it's only release as a -incubating.
Some projects do have dependencies like that, but since there was also
some work on the plugins, I am pretty fine in doing the plugins first
and then CORE
Adam Winer wrote:
The Trinidad subclass of LengthValidator needs some work.
Changes I plan to make - feedback appreciated:
- The messages are copied from the LongRangeValidator, so
we say Enter a value greater than or equal to 5 instead
of Enter a value of 5 or more characters. (I'll use the
+1 to all three.
On 5/22/2007 10:55 AM, Adam Winer wrote:
The Trinidad subclass of LengthValidator needs some work.
Changes I plan to make - feedback appreciated:
- The messages are copied from the LongRangeValidator, so
we say Enter a value greater than or equal to 5 instead
of Enter a
On 5/22/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
On 5/22/07, Adam Winer [EMAIL PROTECTED] wrote:
The Trinidad subclass of LengthValidator needs some work.
Changes I plan to make - feedback appreciated:
- The messages are copied from the LongRangeValidator, so
we say Enter a value
On 5/22/07, Blake Sullivan [EMAIL PROTECTED] wrote:
Adam Winer wrote:
The Trinidad subclass of LengthValidator needs some work.
Changes I plan to make - feedback appreciated:
- The messages are copied from the LongRangeValidator, so
we say Enter a value greater than or equal to 5 instead
Inline validation glitches when rapidly validating
--
Key: TRINIDAD-29
URL: https://issues.apache.org/jira/browse/TRINIDAD-29
Project: MyFaces Trinidad
Issue Type: Bug
Reporter:
[
https://issues.apache.org/jira/browse/TRINIDAD-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497985
]
Adam Winer commented on TRINIDAD-29:
Resolved the first problem. It's still the case that if you get
some
tr:validateLength does not send range message to client
---
Key: TRINIDAD-30
URL: https://issues.apache.org/jira/browse/TRINIDAD-30
Project: MyFaces Trinidad
Issue Type: Bug
Affects
Custom messages on tr:validateLength are not used
-
Key: TRINIDAD-31
URL: https://issues.apache.org/jira/browse/TRINIDAD-31
Project: MyFaces Trinidad
Issue Type: Bug
Reporter: Adam
[
https://issues.apache.org/jira/browse/TRINIDAD-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497986
]
Adam Winer commented on TRINIDAD-31:
The .java code in LengthValidator does not use any of the custom messages.
tr:validateLength messages are poor: don't refer to length
---
Key: TRINIDAD-32
URL: https://issues.apache.org/jira/browse/TRINIDAD-32
Project: MyFaces Trinidad
Issue Type: Bug
tr:lengthValidator: provide better error message when min==max
--
Key: TRINIDAD-33
URL: https://issues.apache.org/jira/browse/TRINIDAD-33
Project: MyFaces Trinidad
Issue Type:
tr:longRangeValidator/tr:doubleRangeValidator: Logic for showing NOT_IN_RANGE
is wrong
--
Key: TRINIDAD-34
URL: https://issues.apache.org/jira/browse/TRINIDAD-34
[
https://issues.apache.org/jira/browse/TRINIDAD-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer updated TRINIDAD-28:
---
Resolution: Fixed
Fix Version/s: 1.0.1-core
Status: Resolved (was: Patch
[
https://issues.apache.org/jira/browse/TRINIDAD-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer resolved TRINIDAD-34.
Resolution: Fixed
Fix Version/s: 1.0.1-core
Fixed.
tc:validateFileItem forces required=true
--
Key: TOBAGO-407
URL: https://issues.apache.org/jira/browse/TOBAGO-407
Project: MyFaces Tobago
Issue Type: Bug
Components: Core
Affects
[
https://issues.apache.org/jira/browse/TRINIDAD-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer resolved TRINIDAD-33.
Resolution: Fixed
Fix Version/s: 1.0.1-core
Fixed.
tr:lengthValidator: provide better
[
https://issues.apache.org/jira/browse/TRINIDAD-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer resolved TRINIDAD-32.
Resolution: Fixed
Fix Version/s: 1.0.1-core
Fixed.
tr:validateLength messages are poor:
[
https://issues.apache.org/jira/browse/TRINIDAD-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498004
]
Adam Winer commented on TRINIDAD-33:
We have a new org.apache.myfaces.trinidad.validator.LengthValidator.EXACT
[
https://issues.apache.org/jira/browse/TRINIDAD-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer resolved TRINIDAD-31.
Resolution: Fixed
Fix Version/s: 1.0.1-core
Assignee: Adam Winer
Custom messages
[
https://issues.apache.org/jira/browse/TRINIDAD-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer resolved TRINIDAD-30.
Resolution: Fixed
Fix Version/s: 1.0.1-core
Fixed.
tr:validateLength does not send range
[
https://issues.apache.org/jira/browse/TRINIDAD-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer resolved TRINIDAD-3.
---
Resolution: Won't Fix
The behavior is required by the spec. See the MYFACES issue for discussion.
[
https://issues.apache.org/jira/browse/TRINIDAD-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer resolved TRINIDAD-15.
Resolution: Fixed
Fix Version/s: 1.0.1-core
Assignee: Adam Winer
Fixed.
Sounds great. I know we've got a lot of fixes ready
for 1.0.1 too - is there anything unpatched that someone's
waiting on?
-- Adam
On 5/22/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Hi,
my guess is, that we need to release the plugins, before we start to
release the CORE.
Why? Because
I'm just updating the patch for iframe dialogs. Should have that to you
shortly.
On 5/22/07, Adam Winer [EMAIL PROTECTED] wrote:
Sounds great. I know we've got a lot of fixes ready
for 1.0.1 too - is there anything unpatched that someone's
waiting on?
-- Adam
On 5/22/07, Matthias
Hello,
I try to enable the nightly build for myfaces at the last weekend.
I discovered one problem the nigthly build contains different svn urls
for myfaces core, shared and tomahawk. I can't use the the same scheme
as the tobago nightly.
Now I try the old system for the myfaces nightly. The
Nightly build should work again.
Bernd
Bernd Bohmann wrote:
Hello,
I try to enable the nightly build for myfaces at the last weekend.
I discovered one problem the nigthly build contains different svn urls
for myfaces core, shared and tomahawk. I can't use the the same scheme
as the tobago
cool,
I have time for that in June, so we really can wait for you.
Thanks!
-Matthias
On 5/22/07, Danny Robinson [EMAIL PROTECTED] wrote:
I'm just updating the patch for iframe dialogs. Should have that to you
shortly.
On 5/22/07, Adam Winer [EMAIL PROTECTED] wrote:
Sounds great. I know
Adam Winer wrote:
On 5/22/07, Blake Sullivan [EMAIL PROTECTED] wrote:
Adam Winer wrote:
The Trinidad subclass of LengthValidator needs some work.
Changes I plan to make - feedback appreciated:
- The messages are copied from the LongRangeValidator, so
we say Enter a value greater than or
Dialog Framework to support 'iframe/lightweight' dialogs
Key: TRINIDAD-35
URL: https://issues.apache.org/jira/browse/TRINIDAD-35
Project: MyFaces Trinidad
Issue Type: Improvement
XMLMenuModel: MenuContentHandlerImpl.setRootModelRowKey() writes to static
variable
---
Key: TRINIDAD-36
URL: https://issues.apache.org/jira/browse/TRINIDAD-36
Project:
Bernd, Thank you very much !
On 5/22/07, Bernd Bohmann [EMAIL PROTECTED] wrote:
Nightly build should work again.
Bernd
Bernd Bohmann wrote:
Hello,
I try to enable the nightly build for myfaces at the last weekend.
I discovered one problem the nigthly build contains different svn urls
[
https://issues.apache.org/jira/browse/TRINIDAD-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danny Robinson updated TRINIDAD-35:
---
Status: Patch Available (was: Open)
Dialog Framework to support 'iframe/lightweight'
[
https://issues.apache.org/jira/browse/TRINIDAD-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498046
]
Danny Robinson commented on TRINIDAD-35:
Patch includes panelPopup component from ADF-FACES dialog branch.
Client-side validation should support onblur/onchange validation when set to
'inline'
--
Key: TRINIDAD-37
URL: https://issues.apache.org/jira/browse/TRINIDAD-37
Any ideas why continuum is getting checksum failure on the dependencies?
Is access to myfaces.zones.apache.org is need to correct the problem, I do
not have it, so someone else must correct the problem.
FYI: The Build Definition used is the one with goals clean package and
arguments containing
[
https://issues.apache.org/jira/browse/TRINIDAD-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer resolved TRINIDAD-36.
Resolution: Fixed
Fix Version/s: 1.0.1-core
Assignee: Adam Winer
Checked in patch
[
https://issues.apache.org/jira/browse/TOMAHAWK-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498074
]
Joost Schouten commented on TOMAHAWK-811:
-
I have to bent over backward to make my calendar work across
On 5/22/07, Bernd Bohmann [EMAIL PROTECTED] wrote:
I try to enable the nightly build for myfaces at the last weekend.
I discovered one problem the nigthly build contains different svn urls
for myfaces core, shared and tomahawk. I can't use the the same scheme
as the tobago nightly.
Now I try
On 5/13/07, Wendy Smoak [EMAIL PROTECTED] wrote:
Continuum 1.1-alpha-1 is running here:
http://myfaces.zones.apache.org:8081/continuum
I have some time tomorrow afternoon/evening (GMT -7) to help if
anything remains to be done to get the Continuum instance back where
it was before the upgrade
[
https://issues.apache.org/jira/browse/TRINIDAD-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498103
]
Adam Winer commented on TRINIDAD-37:
What would be best is if inline validation always fired with
76 matches
Mail list logo
