.
If there is a newer release of the jsf1.1 spec where this has been changed,
then please let us know.
Otherwise the tomahawk solution is as good as we can get while remaining
spec-compliant.
Moving to JSF 1.2 will fix your problem..
Regards, Simon
JSR-252 Issue #58: Enabled protected access to internal
sources trunk -- private. Checked out
branches/1_2_2 --- no UIData at all... It seems I completely misunderstand
MyFaces SVN. Is https://svn.apache.org/repos/asf/myfaces/core/trunk a valid
URL for trunk at all?
JSR-252 Issue #58: Enabled protected access to internal DataModel in
UIData
/myfaces/core/trunk_1.2.x/api/src/main/java-templates/javax/faces/component/UIDataTemplate.java
JSR-252 Issue #58: Enabled protected access to internal DataModel in
UIData
---
Key: MYFACES-1225
are possible without major code duplication as with
1.1.
JSR-252 Issue #58: Enabled protected access to internal DataModel in
UIData
---
Key: MYFACES-1225
URL: https
. is not Tomahawk-specific, I want to do the same...
JSR-252 Issue #58: Enabled protected access to internal DataModel in
UIData
---
Key: MYFACES-1225
URL: https://issues.apache.org
Available)
fixed at revision 600199
JSR-252 Issue 21 - Provided an additional binding attribute for the core
Converter, Listener and Validator tags has wrong behaviour
this:
f:actionListener
type=#{calcForm.actionClass}/f:actionListener
or
f:actionListener
type=org.apache.myfaces.examples.example1.CalcActionListener/f:actionListener
JSR-252 Issue 21 - Provided an additional binding attribute for the core
[
https://issues.apache.org/jira/browse/MYFACES-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe resolved MYFACES-1741.
-
Resolution: Fixed
fixed at 600206
JSR-252 Issue 21 - Provided an additional binding
Status: Resolved (was: Patch Available)
fixed at revision 600207
label attribute does not resolve EL expresion (JSR 252 Issue 6 related)
---
Key: MYFACES-1729
URL: https
Status: Resolved (was: Patch Available)
fixed at revision 600216
JSR-252 Issue 74: disabled property for outputLink does not work
Key: MYFACES-1766
URL: https://issues.apache.org/jira
[
https://issues.apache.org/jira/browse/MYFACES-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf reopened MYFACES-1769:
-
JSR-252 Issue #224: Corrected h:dataTable var to be a String
[
https://issues.apache.org/jira/browse/MYFACES-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf resolved MYFACES-1769.
-
Resolution: Fixed
Fix Version/s: 1.2.1-SNAPSHOT
JSR-252 Issue #224
: Resolved (was: Patch Available)
Thx to Leonardo Uribe, for his patch
JSR-252 Issue #69: Permit the passing of a null value to
SelectItem.setValue(). A SelectItem with null value adds message Value is not
valid
[
https://issues.apache.org/jira/browse/MYFACES-1208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf resolved MYFACES-1208.
-
Resolution: Fixed
Fix Version/s: 1.2.1-SNAPSHOT
already fixed
JSR-252
JSR-252 Issue #224: Corrected h:dataTable var to be a String, and not
ValueExpression enabled
-
Key: MYFACES-1769
URL: https://issues.apache.org/jira/browse/MYFACES-1769
JSR-252 Issue 74: disabled property for outputLink does not work
Key: MYFACES-1766
URL: https://issues.apache.org/jira/browse/MYFACES-1766
Project: MyFaces Core
Issue Type
[
https://issues.apache.org/jira/browse/MYFACES-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe updated MYFACES-1766:
Status: Patch Available (was: Open)
JSR-252 Issue 74: disabled property for outputLink
[
https://issues.apache.org/jira/browse/MYFACES-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe updated MYFACES-1759:
Status: Patch Available (was: Open)
JSR-252 Issue #69: Permit the passing of a null
JSR-252 Issue #69: Permit the passing of a null value to SelectItem.setValue().
A SelectItem with null value adds message Value is not valid
[
https://issues.apache.org/jira/browse/MYFACES-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe updated MYFACES-1741:
Status: Patch Available (was: Open)
JSR-252 Issue 21 - Provided an additional binding
relies on the current spec behavior, I
think this hybrid solution is the best
that we can do until JSF 2.0 clarifies this situation. ...
JSR-252 Issue 21 - Provided an additional binding attribute for the core
Converter, Listener and Validator tags has wrong behaviour
them later.
It's a different solution to the same problem, but I think it's compatible with
my solution.
label attribute does not resolve EL expresion (JSR 252 Issue 6 related)
---
Key: MYFACES-1729
if there are any
compatibility problems here.
May I ask you to look at the RI as well? Why is it working there? I think they
will have a different trick, can we check if the two tricks together will
remain compatible?
regards,
Martin
label attribute does not resolve EL expresion (JSR 252
(was: Patch Available)
Thanks to Leonardo Uribe for supplying this patch.
regards,
Martin
JSR-252 Issue #13: needs converter-for-class converter registration for
BigDecimal and BigInteger
), I'll take a look at it.
I haven't looked to deep into the spec with regards to this binding attribute
on converters/validators so far.
regards,
Martin
JSR-252 Issue 21 - Provided an additional binding attribute for the core
Converter, Listener and Validator tags has wrong behaviour
on this issue if you post a
message to the dev mailing list rather than adding comments to the issue. If
it's broad enough to include the JSF RI, you probably should cross-post between
the jsf ri dev mailng list and the myfaces dev mailing list.
JSR-252 Issue 21 - Provided an additional binding
, so I suppose that it is possible to create a class that
implements Converter and StateHolder,
and do something like a delegate pattern, to save converterId and binding
values on the tree.
2. Restore the binding when getConverter() is called or something like that.
JSR-252 Issue 21
.
JSR-252 Issue 21 - Provided an additional binding attribute for the core
Converter, Listener and Validator tags has wrong behaviour
-
Key
JSR-252 Issue 21 - Provided an additional binding attribute for the core
Converter, Listener and Validator tags has wrong behaviour
-
Key: MYFACES
the
method getDetail and getSummary is called.
Again, I provide this patch, and finally I feel that this is a correct solution
for this issue.
label attribute does not resolve EL expresion (JSR 252 Issue 6 related
JSR-252 Issue #13: needs converter-for-class converter registration for
BigDecimal and BigInteger
--
Key: MYFACES-1739
URL: https://issues.apache.org/jira/browse
[
https://issues.apache.org/jira/browse/MYFACES-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe updated MYFACES-1739:
Status: Patch Available (was: Open)
JSR-252 Issue #13: needs converter-for-class
252 Issue 6 related)
---
Key: MYFACES-1729
URL: https://issues.apache.org/jira/browse/MYFACES-1729
Project: MyFaces Core
Issue Type: Bug
Components: JSR-252
to me but I'm open to any suggestion, critic or improvement.
label attribute does not resolve EL expresion (JSR 252 Issue 6 related)
---
Key: MYFACES-1729
URL: https://issues.apache.org/jira
a
PhaseListenerLoadBundle to restore it's particular state.
I don't know how to do
Any suggestions? Suggestions and Expert opinions are welcome.
label attribute does not resolve EL expresion (JSR 252 Issue 6 related
attribute does not resolve EL expresion (JSR 252 Issue 6 related)
---
Key: MYFACES-1729
URL: https://issues.apache.org/jira/browse/MYFACES-1729
Project: MyFaces Core
Issue Type
is stored in request-scope and not availiable in case of validation
error.
label attribute does not resolve EL expresion (JSR 252 Issue 6 related)
---
Key: MYFACES-1729
URL: https://issues.apache.org
a validation error
occur.
The problem should be on f:loadBundle, because the var is not added to the
ELContext, or the ResourceBundle is not resolved
as the spec says. I will try this and see what happens
label attribute does not resolve EL expresion (JSR 252 Issue 6 related
footerClass and headerClass does not work (issue 4 of JSR 252)
---
Key: MYFACES-1727
URL: https://issues.apache.org/jira/browse/MYFACES-1727
Project: MyFaces Core
Issue
label attribute does not resolve EL expresion (JSR 252 Issue 6 related)
---
Key: MYFACES-1729
URL: https://issues.apache.org/jira/browse/MYFACES-1729
Project: MyFaces Core
h:column footerClass and headerClass does not work (issue 4 of JSR 252)
---
Key: MYFACES-1727
URL: https://issues.apache.org/jira/browse/MYFACES-1727
Project: MyFaces Core
checked standard-faces-config.xml and h.tld and all are fine.
Any suggestions?
Att: Leonardo Uribe
h:column footerClass and headerClass does not work (issue 4 of JSR 252)
---
Key: MYFACES-1727
: Resolved (was: Patch Available)
fixed.
thx for the patch !
JSR-252 Issue #95: Allow multiple instances of FacesServlet in a single
webapp, mapped with different URI mappings, to use different implementations
of Lifecycle
.
JSR-252 Issue #95: Allow multiple instances of FacesServlet in a single
webapp, mapped with different URI mappings, to use different implementations
of Lifecycle
me a nitpicker,
but isn't this behaviour required by the JSF 1.2 specification (see section
10.2.6.2, paragraph 2)? Note that the patch is somewhat outdated by now but as
it's just a single method it shouldn't be a problem.
JSR-252 Issue #95: Allow multiple instances of FacesServlet in a single
[
https://issues.apache.org/jira/browse/MYFACES-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Aranda resolved MYFACES-1223.
---
Resolution: Fixed
Assignee: Bruno Aranda
Already implemented
JSR-252 Issue #54
(was: Matthias Weßendorf)
This does not apply to myfaces, right? Closing it
JSR-252 Issue #45: Avoided concurrent read issues by using a
java.util.HashMap instead of java.util.WeakHashMap for a component's Property
Descriptor Map
, as it is difficult to assess when will be done
and the current implementation works fine
JSR-252 Issue #99: Specified Java EE 5 Generics usage where applicable.
---
Key: MYFACES-1262
URL: https
[
https://issues.apache.org/jira/browse/MYFACES-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Aranda resolved MYFACES-1243.
---
Resolution: Invalid
This applies to the spec
JSR-252 Issue #87: Modified specification
[
https://issues.apache.org/jira/browse/MYFACES-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Aranda resolved MYFACES-1233.
---
Resolution: Fixed
Fix Version/s: 1.2.0-SNAPSHOT
Done
JSR-252 Issue #73: Added
:
[
https://issues.apache.org/jira/browse/MYFACES-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Aranda resolved MYFACES-1243.
---
Resolution: Invalid
This applies to the spec
JSR-252 Issue #87: Modified specification
this one, as it is difficult to assess when will be done
and the current implementation works fine
JSR-252 Issue #99: Specified Java EE 5 Generics usage where applicable.
---
Key: MYFACES-1262
URL
[
https://issues.apache.org/jira/browse/MYFACES-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Aranda reopened MYFACES-1262:
---
Assignee: Bruno Aranda (was: Mathias Broekelmann)
JSR-252 Issue #99: Specified Java EE
[
https://issues.apache.org/jira/browse/MYFACES-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Aranda resolved MYFACES-1262.
---
Resolution: Fixed
JSR-252 Issue #99: Specified Java EE 5 Generics usage where applicable
to assess when
will be done and the current implementation works fine
JSR-252 Issue #99: Specified Java EE 5 Generics usage where
applicable.
-
--
Key: MYFACES-1262
URL: https
=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Aranda resolved MYFACES-1262.
---
Resolution: Fixed
Fix Version/s: 1.2.0-SNAPSHOT
I guess we can close this one, as it is difficult to assess when will be done
and the current implementation works fine
JSR-252 Issue
.
A12.4. The JSR-252 MyFaces API lib would get the name
myfaces-api-2.0.0.jar (!). Mind: This is a new argument pro 1.2.x!
;-)
A12.5. MyFaces 1.2 is an incremental improvement over 1.1 that
doesn't have giant technology changes in its core.
A12.6. Tomahawk/Trinidad/Tobago are no longer tightly-coupled
has
its lobby).
regards
Alexander
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Manfred Geiler
Sent: Friday, May 25, 2007 10:32 AM
To: MyFaces Development
Subject: [PROPOSAL] MyFaces JSR-252 Version Number (was MyFaces 2.0.0)
Hi all,
I want to get rid
Hi Manfred!
For me, all in your post result in a simple +1 from my side ;-)
A20.5. not solved, but if there is a JSF fix we must join all our
influence and convice Ed to call it JSF-1.3 ;-)
This only happens if there is a minor release of the spec do we
have seen something in the past?
.
A12.4. The JSR-252 MyFaces API lib would get the name
myfaces-api-2.0.0.jar (!). Mind: This is a new argument pro 1.2.x!
;-)
A12.5. MyFaces 1.2 is an incremental improvement over 1.1 that
doesn't have giant technology changes in its core.
A12.6. Tomahawk/Trinidad/Tobago are no longer tightly
sounds
strange and will confuse people.
A12.3. When the JSF 2.0 spec is out in 2008 there will by a MyFaces
2.0.x implementation which will confuse people even more.
A12.4. The JSR-252 MyFaces API lib would get the name
myfaces-api-2.0.0.jar (!). Mind: This is a new argument pro 1.2.x!
;-)
A12.5
it is safe to talk about that one as JSR-314, just in case...
Bruno
regards
Alexander
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Manfred Geiler
Sent: Friday, May 25, 2007 10:32 AM
To: MyFaces Development
Subject: [PROPOSAL] MyFaces JSR-252 Version
: Friday, May 25, 2007 10:32 AM
To: MyFaces Development
Subject: [PROPOSAL] MyFaces JSR-252 Version Number (was MyFaces 2.0.0)
Hi all,
I want to get rid of that 1.2 vs. 2.0 discussion blocker. Therefore I
will try to summarize all of the arguments and collect the pros and
cons once more
Manfred,
Thank you for this! Below are a couple questions.
Manfred Geiler wrote:
Hi all,
snip
Ok, here is my compromise proposal, which I hope everyone can live with:
C1. We switch MyFaces Core to a 4 digit version numbering: 1.2.0.0 which
means
see inline
On 5/25/07, Paul Spencer [EMAIL PROTECTED] wrote:
Manfred,
Thank you for this! Below are a couple questions.
Manfred Geiler wrote:
Hi all,
snip
Ok, here is my compromise proposal, which I hope everyone can live with:
C1. We switch MyFaces Core to a 4 digit version numbering:
2.0 sounds
strange and will confuse people.
A12.3. When the JSF 2.0 spec is out in 2008 there will by a MyFaces
2.0.x implementation which will confuse people even more.
A12.4. The JSR-252 MyFaces API lib would get the name
myfaces-api-2.0.0.jar (!). Mind: This is a new argument pro 1.2.x
Manfred,
+1 for the Proposal.
Once the proposal is accepted, please post a proposal for the next version
number
for each affected sub project. I would posts one now for Tomahawk, but I do not
want to distract anyone.
Paul Spencer
Manfred Geiler wrote:
see inline
On 5/25/07, Paul Spencer
spec is out in 2008 there will by a MyFaces
2.0.x implementation which will confuse people even more.
A12.4. The JSR-252 MyFaces API lib would get the name
myfaces-api-2.0.0.jar (!). Mind: This is a new argument pro 1.2.x!
;-)
A12.5. MyFaces 1.2 is an incremental improvement over 1.1 that
doesn't have
.
A12.3. When the JSF 2.0 spec is out in 2008 there will by a MyFaces
2.0.x implementation which will confuse people even more.
A12.4. The JSR-252 MyFaces API lib would get the name
myfaces-api-2.0.0.jar (!). Mind: This is a new argument pro 1.2.x!
;-)
A12.5. MyFaces 1.2 is an incremental improvement
On May 25, 2007, at 4:31 AM, Manfred Geiler wrote:
Arguments pro 2.x.y:
A20.1. Tomcat does the same. They do not align there container
versions to the spec and nobody complains.
This is an excellent proposal and clearly takes all the factors we
have discussed into account. I would have no
(was: Patch Available)
Implement JSR-252 core tag: convertDateTimeTag
--
Key: MYFACES-1478
URL: https://issues.apache.org/jira/browse/MYFACES-1478
Project: MyFaces Core
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/MYFACES-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Aranda resolved MYFACES-1485.
---
Resolution: Fixed
Fix Version/s: 1.2.0-SNAPSHOT
Implement JSR-252 core tag
[
https://issues.apache.org/jira/browse/MYFACES-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Aranda resolved MYFACES-1201.
---
Resolution: Fixed
Fix Version/s: 1.2.0-SNAPSHOT
JSR-252 Issue #4: Added
JSR-252 Issue #43: Migrated over to using XML Schema (from DTD) for
configuration file validation.
--
Key: MYFACES-1217
URL: https://issues.apache.org/jira/browse
[
https://issues.apache.org/jira/browse/MYFACES-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Aranda resolved MYFACES-1264.
---
Resolution: Fixed
JSR-252 Issue #108: JSF in Java EE containers must validate
to _ComponentAttributesMap?
JSR-252 Issue #45: Avoided concurrent read issues by using a
java.util.HashMap instead of java.util.WeakHashMap for a component's Property
Descriptor Map
[
https://issues.apache.org/jira/browse/MYFACES-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Aranda resolved MYFACES-1232.
---
Resolution: Won't Fix
This issue is RI specific, right?
JSR-252 Issue #72: Improve XHTML
that this is implemented
already.
Regards,
Martin Haimberger
JSR-252 Issue # 48: Specify the algorithm used for client id generation as
well as provide a way to allow the page author to specify exactly what the
client id should be, and preventing Faces from altering
(was: Patch Available)
Path applied. Thanks!
JSR-252 Issue #51: Allow implementations to check for the presence of a
servlet-class definition in a web app deployment descriptor as a means to
abort the configuration and save startup time
you either fix your code or the test? Thank you!
JSR-252 Issue #51: Allow implementations to check for the presence of a
servlet-class definition in a web app deployment descriptor as a means to
abort the configuration and save startup time
(was: Patch Available)
Path applied. Thanks!
JSR-252 Issue #8: Made UIViewRoot a source of PhaseEvent(s) for all phases of
the request processing lifecycle except RestoreView
that the issue is
already implemented?
JSR-252 Issue #50: Allow an application to specify multiple render kits by
introducing an optional renderKitId attribute on f:view
(was: Patch Available)
Well yes, it seem it is implemented. Thanks!
JSR-252 Issue #50: Allow an application to specify multiple render kits by
introducing an optional renderKitId attribute on f:view
JSR-252 Issue #152: Specified EL coercion usage in API javadocs
UISelectOne/UISelectMany (when items are compared in validation) and standard
html renderkit docs during encoding of select components
Yes, it seems to me too that it is a fix to the spec
JSR-252 Issue #68: Specify that the component tree may be manipulated
throughout the request processing lifecycle, except during render
---
Key: MYFACES-1212
URL: https://issues.apache.org/jira/browse/MYFACES-1212
Project: MyFaces Core
Issue Type: Bug
Components: JSR-252
Reporter
Already implemented
Implementation of new/modified JSR-252 methods for the Application class
Key: MYFACES-1439
URL: https://issues.apache.org/jira/browse/MYFACES-1439
Project
Status: Resolved (was: Patch Available)
Already implemented. Thanks Andreas
Implement JSR-252 core tag: phaseListenerTag
Key: MYFACES-1484
URL: https://issues.apache.org/jira/browse/MYFACES-1484
this is also ok.
For me, it seems, this is no bug in MyFaces.
Regards,
Martin Haimberger
JSR-252 Issue #147: Clarified grammer with respect to component id.
---
Key: MYFACES-1253
URL: https
. Thanks Martin for checking
JSR-252 Issue #147: Clarified grammer with respect to component id.
---
Key: MYFACES-1253
URL: https://issues.apache.org/jira/browse/MYFACES-1253
Project
[
https://issues.apache.org/jira/browse/MYFACES-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christoph Ebner updated MYFACES-1222:
-
Status: Patch Available (was: Reopened)
JSR-252 Issue #51: Allow implementations
. The
ServletContext-Mock won't return its WebXml instance, so
DefaultFacesInitializer will stop initializing.
I've created a new patch, that avoids the NPE, if no WebXml is present, but the
test will still fail!
JSR-252 Issue #51: Allow implementations to check for the presence of a
servlet
Christoph!
JSR-252 Issue #51: Allow implementations to check for the presence of a
servlet-class definition in a web app deployment descriptor as a means to
abort the configuration and save startup time
[
https://issues.apache.org/jira/browse/MYFACES-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christoph Ebner updated MYFACES-1222:
-
Status: Patch Available (was: Open)
JSR-252 Issue #51: Allow implementations
[
https://issues.apache.org/jira/browse/MYFACES-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Haimberger updated MYFACES-1221:
---
Status: Patch Available (was: Open)
JSR-252 Issue #50: Allow an application
[
https://issues.apache.org/jira/browse/MYFACES-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cagatay Civici resolved MYFACES-1214.
-
Resolution: Won't Fix
Already implemented in myfaces commandlink.
JSR-252 Issue #29
[
https://issues.apache.org/jira/browse/MYFACES-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Haimberger updated MYFACES-1204:
---
Status: Patch Available (was: Open)
JSR-252 Issue #8: Made UIViewRoot a source
[
https://issues.apache.org/jira/browse/MYFACES-1244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christoph Ebner updated MYFACES-1244:
-
Status: Patch Available (was: Open)
JSR-252 Issue #95: Allow multiple instances
[
https://issues.apache.org/jira/browse/MYFACES-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Haimberger updated MYFACES-1458:
---
Status: Patch Available (was: Open)
Implement JSR-252 core tag: SubviewTag
1.2.
Regards,
Martin Haimberger
Implement JSR-252 core tag: FacetTag
Key: MYFACES-1485
URL: https://issues.apache.org/jira/browse/MYFACES-1485
Project: MyFaces Core
Issue Type: Sub-task
1 - 100 of 318 matches
Mail list logo
