I'd just edit it
Sent from my iPod.
Am 08.03.2008 um 16:59 schrieb simon [EMAIL PROTECTED]:
Hi,
As I've just prepared a release for the first time, I need to add my
gpg
signing key to the keys file at
http://www.apache.org/dist/myfaces/KEYS
What's the correct way to do that? Do I just
[
https://issues.apache.org/jira/browse/TOBAGO-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Bohmann resolved TOBAGO-629.
--
Resolution: Fixed
Wrong char-encoding on browser when using WebSphere AS
[
https://issues.apache.org/jira/browse/TOBAGO-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Bohmann resolved TOBAGO-628.
--
Resolution: Fixed
Setting rendererType on TobagoMenuExtensionHandler for facelets
UIComponentBase catches all Exceptions on broadcast
---
Key: MYFACES-1833
URL: https://issues.apache.org/jira/browse/MYFACES-1833
Project: MyFaces Core
Issue Type: Bug
Components:
[
https://issues.apache.org/jira/browse/MYFACES-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12576753#action_12576753
]
Thomas Spiegl commented on MYFACES-1833:
catch(Exception ex) {
[
https://issues.apache.org/jira/browse/TOBAGO-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12576755#action_12576755
]
Bernd Bohmann commented on TOBAGO-572:
--
I think facelets has a bug if you are using
[
https://issues.apache.org/jira/browse/TOBAGO-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12576764#action_12576764
]
Bernd Bohmann commented on TOBAGO-325:
--
Helmut,
can you provide the patch for 1.1.x,
Hallo,
can anyone provide me with an example how to implement a
DialogRenderKitService that emulates the default behaviour hidden in
DialogServiceImpl.
I expected the implementation to be like this:
public boolean launchDialog(FacesContext context, UIViewRoot targetRoot,
tr:panelLabelAndMessage ... facet=help generates two help strings
---
Key: TRINIDAD-999
URL: https://issues.apache.org/jira/browse/TRINIDAD-999
Project: MyFaces Trinidad
Issue
hello,
before i'll commit the patch of TRINIDAD-909:
are there any suggestions concerning TRINIDAD-910?
(TRINIDAD-909 also improves the current situation of TRINIDAD-910. however,
there is still room for improvement.)
regards,
gerhard
--
http://www.irian.at
Your JSF powerhouse -
JSF
hello,
before i'll commit the patch of TRINIDAD-996:
are there any further suggestions?
it's an alternative mechanism (- no replacement).
(you have to activate it explicitly with a context-param.)
regards,
gerhard
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development
Hi All,
Currently, trinidad and core-1.2 use the myfaces-faces-plugin to
generate tag classes, config files and component classes.
There is some work going on to use this for core-1.1 and tomahawk too.
As I mentioned earlier, I don't like the approach used by the current
myaces-faces-plugin; I
http://svn.apache.org/repos/asf/myfaces/maven/trunk/KEYS
but I see some keys are missing in svn.
Mario Ivankovits
Leonardo Uribe
Scott O'Bryan
are not available in svn.
Thomas Spiegl
is missing in http://www.apache.org/dist/myfaces/KEYS
Can you synchronize and verify the files?
I think
On Sat, Mar 8, 2008 at 7:34 AM, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi!
+1 very good idea!
Are those +1 due to the fact that you think that Orchestra is not the
best place where such a component is located (which I understood), or is
it that this component is still
After investigating another hour in this problem I am convinced that -
unfortunately - there is no solution without using nasty details of the
current trinidad implementation because the ReturnEvent is broadcasted in a
newly spawned lifecycle (see TrinidadFilterImpl) that can only be triggered
by
Hi
The work for component generation for tomahawk and 1.2 modules is ready to
commit.
For component generation it follows abstract pattern and use myfaces faces
plugin.
For share 1.1 and 1.2 code it use maven-dependency plugin for unpack the
shared parts of the code.
The change on tomahawk
+1,
regards,
Martin
On Sat, Mar 8, 2008 at 4:38 PM, simon [EMAIL PROTECTED] wrote:
Hi All,
As has been discussed recently, it is time to get a core-1.1 release out.
This requires releasing the orchestra parent pom too.
The maven artifacts have been deployed to the staging repo:
*
Sounds interesting. Will you support everything the XML-syntax allows
to supply now? E.g, long descriptions?
will it basically be an option which component-set wants to use which
frontend? Then slowly every component set could decide if it wants to
move over...
How about restoreState/saveState?
18 matches
Mail list logo