[
https://issues.apache.org/jira/browse/TOBAGO-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12561257#action_12561257
]
Martin Marinschek commented on TOBAGO-516:
--
I would suspect it is - what Ryan is
[
https://issues.apache.org/jira/browse/TRINIDAD-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12561256#action_12561256
]
Martin Marinschek commented on TRINIDAD-906:
Hi Gabrielle,
I'm just
Matthias Wessendorf [EMAIL PROTECTED] schrieb:
On Jan 21, 2008 12:03 AM, Simon Kitching [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] schrieb:
-removed redundant versions as well...
plugin
-groupIdorg.apache.myfaces.trinidadbuild/groupId
-
[
https://issues.apache.org/jira/browse/TRINIDAD-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12561265#action_12561265
]
Martin Marinschek commented on TRINIDAD-906:
Ok, I've read a little more -
[
https://issues.apache.org/jira/browse/MYFACES-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mario Ivankovits updated MYFACES-1804:
--
Resolution: Duplicate
Status: Resolved (was: Patch Available)
It is so
[
https://issues.apache.org/jira/browse/TRINIDAD-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12561299#action_12561299
]
Tomas Havelka commented on TRINIDAD-884:
Ad iii) Actually you can skin message
[
https://issues.apache.org/jira/browse/TOBAGO-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12561303#action_12561303
]
Bernd Bohmann commented on TOBAGO-516:
--
What is the difference between
Simon Kitching schrieb:
Ah, should have my eyes checked!
I do not like using pluginManagement (or dependencyManagement) to manage
artifact versions. I think it is obscure, and would much rather see the
actual version attached to each use (as it originally was).
Yes, the above
InlineFrame component
-
Key: TRINIDAD-913
URL: https://issues.apache.org/jira/browse/TRINIDAD-913
Project: MyFaces Trinidad
Issue Type: Wish
Components: Components
Affects Versions: 1.2.5-core, 1.0.5-core
Bernd Bohmann [EMAIL PROTECTED] schrieb:
Simon Kitching schrieb:
Yes, the above approach will work. But it is worrying to look at a pom and
see something without a version attached. It requires work to confirm that
this is valid (ie that a parent does define a version). And it
[
https://issues.apache.org/jira/browse/TOBAGO-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Helmut Swaczinna updated TOBAGO-594:
Status: Patch Available (was: Open)
tc:columnEvent does not work with selectable=none
[
https://issues.apache.org/jira/browse/TOBAGO-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Helmut Swaczinna updated TOBAGO-595:
Status: Patch Available (was: Open)
Support for tc:command onclick attribute in
[
https://issues.apache.org/jira/browse/TOBAGO-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Helmut Swaczinna updated TOBAGO-539:
Status: Patch Available (was: Open)
Accelerator keys don't work properly in tabGroup
[
https://issues.apache.org/jira/browse/MYFACES-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12561338#action_12561338
]
Stephen Cunliffe commented on MYFACES-1805:
---
This may be the result of 1 of 2
Hi,
I was running the needed tasks to get the 1.2.2 release of Apache
MyFaces core out.
Please note that this vote concerns all of the following parts:
1. Maven artifact group org.apache.myfaces.shared v3.0.2 [1]
2. Maven artifact group org.apache.myfaces.core v1.2.2 [1]
The artifacts are
[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12561372#action_12561372
]
Michael Freedman commented on PORTLETBRIDGE-15:
---
What is the status
+1
On 22/01/2008, Matthias Wessendorf [EMAIL PROTECTED] wrote:
+1 on the bits.
On Jan 22, 2008 7:50 AM, Leonardo Uribe [EMAIL PROTECTED] wrote:
Hi,
I was running the needed tasks to get the 1.2.2 release of Apache
MyFaces core out.
Please note that this vote concerns all of the
What is the status here? Its marked patch available but the only
attached file is a portlet.xml? There also seem to be two
conversations going on. Could you guys either upload or e-mail the
samples (in particular the ones not working) to me so I can test them
directly in my environment?
+1 on the bits.
On Jan 22, 2008 7:50 AM, Leonardo Uribe [EMAIL PROTECTED] wrote:
Hi,
I was running the needed tasks to get the 1.2.2 release of Apache
MyFaces core out.
Please note that this vote concerns all of the following parts:
1. Maven artifact group org.apache.myfaces.shared v3.0.2
Hello Simon,
I think a multi module project should define the common configuration of
plugins and dependencies in the management section.
For example: If you define different versions of the commons-logging
api. The dependency mechanism is not using the most recent version of
commons-logging,
+1!
regards,
Martin
On 1/22/08, Bruno Aranda [EMAIL PROTECTED] wrote:
+1
On 22/01/2008, Matthias Wessendorf [EMAIL PROTECTED] wrote:
+1 on the bits.
On Jan 22, 2008 7:50 AM, Leonardo Uribe [EMAIL PROTECTED] wrote:
Hi,
I was running the needed tasks to get the 1.2.2 release of
[
https://issues.apache.org/jira/browse/TOBAGO-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12561381#action_12561381
]
Ryan Lubke commented on TOBAGO-516:
---
If you're running in a non-javaee environment, you
+1,
Cagatay
On Jan 22, 2008 7:02 PM, Martin Marinschek [EMAIL PROTECTED]
wrote:
+1!
regards,
Martin
On 1/22/08, Bruno Aranda [EMAIL PROTECTED] wrote:
+1
On 22/01/2008, Matthias Wessendorf [EMAIL PROTECTED] wrote:
+1 on the bits.
On Jan 22, 2008 7:50 AM, Leonardo Uribe
Selected and disclosed row key sets in UIXTableTemplate.java are assumed to be
non-null
---
Key: TRINIDAD-914
URL: https://issues.apache.org/jira/browse/TRINIDAD-914
On Tue, 2008-01-22 at 12:50 -0300, Leonardo Uribe wrote:
Hi,
I was running the needed tasks to get the 1.2.2 release of Apache
MyFaces core out.
Please note that this vote concerns all of the following parts:
1. Maven artifact group org.apache.myfaces.shared v3.0.2 [1]
2. Maven
[
https://issues.apache.org/jira/browse/TRINIDAD-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12561404#action_12561404
]
Matthias Weßendorf commented on TRINIDAD-906:
-
commit to this ticket isn't
Hi Martin,
Thanks for the feedback. I have to say, I'm not a perf expert, I
suggested using the request and it was the perf guy here who suggested
ThreadLocal instead if anyone has perf concerns about this please
let me know.
Thanks,
Gab
Martin Marinschek (JIRA) wrote:
[
overridding converter/validator messages does only work on the server
-
Key: TRINIDAD-915
URL: https://issues.apache.org/jira/browse/TRINIDAD-915
Project: MyFaces Trinidad
+1
On Jan 22, 2008 9:38 AM, Cagatay Civici [EMAIL PROTECTED] wrote:
+1,
Cagatay
On Jan 22, 2008 7:02 PM, Martin Marinschek [EMAIL PROTECTED]
wrote:
+1!
regards,
Martin
On 1/22/08, Bruno Aranda [EMAIL PROTECTED] wrote:
+1
On 22/01/2008, Matthias Wessendorf [EMAIL
+1
2008/1/20, Bernd Bohmann [EMAIL PROTECTED]:
Hello,
I would like to release Tobago 1.0.14,
The 1.0.x series has only maintenance focus.
This release contains only a few changes.
For a detail list please consult the release notes:
[
https://issues.apache.org/jira/browse/TRINIDAD-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12561416#action_12561416
]
Matt Cooper commented on TRINIDAD-914:
--
The fixes have been committed to:
Hazem Saleh schrieb:
Hello Gerald;
Actually Dojo 1.0.0 has many nice stuff :).
I will follow your idea; making local development till Werner makes the update.
Thanks very much.
Sorry for not updating so long on this issue, the main problem I face
simply is time, I have plans to move upwards
Oops, I guess I should put this comment in the issue. :-)
Gabrielle Crawford wrote:
Hi Martin,
Thanks for the feedback. I have to say, I'm not a perf expert, I
suggested using the request and it was the perf guy here who suggested
ThreadLocal instead if anyone has perf concerns about
[
https://issues.apache.org/jira/browse/TRINIDAD-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12561462#action_12561462
]
Gabrielle Crawford commented on TRINIDAD-906:
-
Thanks for the comment. Yes,
Hi,
Tomas - Thanks for the comment. However, I don't seem to be able to get
the icons to work. Could you show an extract of the CSS please?
I'm on trinidad trunk, revision 614286.
Thanks,
Yee-Wah
Tomas Havelka (JIRA) wrote:
[
In the development of a library based on Trinidad, I need to have some hooks
in the renderer to improve performance. Specifically, I need to setup a
context and strip down a context for a component. Right now,
CoreRenderer.encodeEnd(FacesContext, UIComponent) is final, so I cannot
extend that
Here's my non-binding +1 vote.
Thanks,
Joe Bohn
Leonardo Uribe wrote:
Hi,
I was running the needed tasks to get the 1.2.2 release of Apache
MyFaces core out.
Please note that this vote concerns all of the following parts:
1. Maven artifact group org.apache.myfaces.shared v3.0.2 [1]
2.
[
https://issues.apache.org/jira/browse/TRINIDAD-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12561478#action_12561478
]
Scott O'Bryan commented on TRINIDAD-906:
Then yeah, I think you implemented this
[
https://issues.apache.org/jira/browse/TRINIDAD-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12561491#action_12561491
]
Martin Marinschek commented on TRINIDAD-906:
Up to JDK1.4 getting the current
On Jan 22, 2008 7:23 PM, simon [EMAIL PROTECTED] wrote:
On Tue, 2008-01-22 at 12:50 -0300, Leonardo Uribe wrote:
Hi,
I was running the needed tasks to get the 1.2.2 release of Apache
MyFaces core out.
Please note that this vote concerns all of the following parts:
1. Maven
what is the reason of having encodeEnd and encodeBegin final?
I have never understood why Trinidad is trying to hide possibilities from
the developer. Isn't it safe enough to say that renderers are not part of
the API, what you are doing there, might break with an update. Instead,
everyone is
[
https://issues.apache.org/jira/browse/TRINIDAD-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12561498#action_12561498
]
Scott O'Bryan commented on TRINIDAD-906:
Yeah Martin, I think you're correct on
important
(1)
in the impl jar, file META-INF/standard-faces-config.xml has a few
component entries like this:
property
description
lt;pgt;
The URL of the image. If the URL starts with a '/', it
is relative
to the context
Hello Martin,
Those two methods are final mainly because Trinidad works with FacesBean. As
for the original issue, why don't you override encodeBegin and encodeEnd
receiving a FacesBean instance? So far I'm -1 on adding new encode methods
to CoreRenderer. The signature is
protected void
Neither the shared, api nor impl jars have these entries.
The bytecode version in the classes is 49, ie java5 which is fine.
isn't java5 required for JSF 1.2 ?
hmm... it might have been better to build with 1.4, right? is it necessary
for the release to go out?
(4)
The
encodeEnd is not always called if you look at the source.
On Jan 22, 2008 3:32 PM, Simon Lessard [EMAIL PROTECTED] wrote:
Hello Martin,
Those two methods are final mainly because Trinidad works with FacesBean.
As for the original issue, why don't you override encodeBegin and encodeEnd
Usually I would completely agree, but in this case it may be valid. The
encodeEnd/Begin methods that don't use the FacesBean are setup in such a way
to use either encodeAll or encodeEnd (with the FacesBean). So I really don't
think people should be extending these methods.
On Jan 22, 2008 3:27
It's going to be called if the renderer does not render its children. It's
basically the same algorithm as UIComponent's encodeAll method.
On Jan 22, 2008 5:34 PM, Andrew Robinson [EMAIL PROTECTED]
wrote:
encodeEnd is not always called if you look at the source.
On Jan 22, 2008 3:32 PM,
ok I see your issue now... Hmmm... I would prefer the names beforeEncode and
afterEncode then.
On Jan 22, 2008 5:36 PM, Andrew Robinson [EMAIL PROTECTED]
wrote:
Usually I would completely agree, but in this case it may be valid. The
encodeEnd/Begin methods that don't use the FacesBean are
sounds good.
On Jan 22, 2008 2:38 PM, Simon Lessard [EMAIL PROTECTED] wrote:
ok I see your issue now... Hmmm... I would prefer the names beforeEncode and
afterEncode then.
On Jan 22, 2008 5:36 PM, Andrew Robinson [EMAIL PROTECTED]
wrote:
Usually I would completely agree, but in this
well, then - if there is a valid reason in this case -
I have seen other cases where such restrictions don't make sense.
regards,
Martin
On Jan 22, 2008 11:36 PM, Andrew Robinson [EMAIL PROTECTED]
wrote:
Usually I would completely agree, but in this case it may be valid. The
encodeEnd/Begin
On Jan 22, 2008 11:33 PM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Neither the shared, api nor impl jars have these entries.
The bytecode version in the classes is 49, ie java5 which is fine.
isn't java5 required for JSF 1.2 ?
oh, of course- excuse my dumb statement ;)
regards,
[
https://issues.apache.org/jira/browse/TRINIDAD-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Cooper updated TRINIDAD-642:
-
Resolution: Fixed
Fix Version/s: 1.2.6-core
1.0.6-core
+1
Volker Weber schrieb:
+1
2008/1/20, Bernd Bohmann [EMAIL PROTECTED]:
Hello,
I would like to release Tobago 1.0.14,
The 1.0.x series has only maintenance focus.
This release contains only a few changes.
For a detail list please consult the release notes:
Hi
The binary and sources artifacts in zip and tgz signed are here:
http://people.apache.org/~lu4242/myfaces122binsrc/sources/
Take a look at this :)
regards
Leonardo Uribe
[
https://issues.apache.org/jira/browse/TRINIDAD-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott O'Bryan resolved TRINIDAD-798.
Resolution: Fixed
Fix Version/s: 1.2.6-core
1.0.6-core
In the
Hi
The clirr reports for api, build and impl for myfaces 1.2.2 are here
http://people.apache.org/~lu4242/myfaces122clirr/api/clirr-report.html
http://people.apache.org/~lu4242/myfaces122clirr/build/clirr-report.html
http://people.apache.org/~lu4242/myfaces122clirr/impl/clirr-report.html
No
hi,
I know that there was an overhaul on the site.
I am not able to look up the TAGDOC. the used to be linked by the start page.
Sure under project reports they are. But... not 100% sure if that is clear to
every user...
Thanks!
Matthias
--
Matthias Wessendorf
further stuff:
blog:
Matthias Wessendorf [EMAIL PROTECTED] schrieb:
hi,
I know that there was an overhaul on the site.
I am not able to look up the TAGDOC. the used to be linked by the start page.
Sure under project reports they are. But... not 100% sure if that is clear
to
every user...
The tagdocs can
[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12561606#action_12561606
]
Christian Raschka commented on PORTLETBRIDGE-15:
Sorry, the patch
Hi,
I was talking about the Tomahawk TLD doc.
It used to be listed under documentation / javadocs (on the first page).
No now.
The core javadoc is fine for h: / f: things.
The Tomahawk doesn't have a javadocs link.
These tagdocs used to be linked by the start page.
So, just wondering why the
61 matches
Mail list logo
