Re: [VOTE] Add MyfacesBuilderPlugin to buildtools branch and use it on myfaces 1.1

Leonardo Uribe schrieb: MyfacesBuilderPlugin is now available for use on myfaces 1.1, so we can officially vote about what plugin use on myfaces 1.1, 1.2 and tomahawk for code generation +1 for myfaces-core 1.1.x and tomahawk now! (+1 for myfaces-core 1.2.x eventually, but there's no hurry..)

Re: [VOTE] Add MyfacesBuilderPlugin to buildtools branch and use it on myfaces 1.1

Hi, great work! So please vote if you want to see this feature included on myfaces 1.x and tomahawk +1 cheers, Gerald -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces

Re: [VOTE] Add MyfacesBuilderPlugin to buildtools branch and use it on myfaces 1.1

Leonardo Uribe schrieb: +0 ... just due to the fact that I don't have time to review these bits, but I trust you guys that *everything* ;-) works as expected. +1 for the architecture and the general approach! Great work! Hi MyfacesBuilderPlugin is now available for use on myfaces 1.1, so we

Re: possible replacement for our kupu based html editor

[EMAIL PROTECTED] schrieb: Werner Punz schrieb: Mario Ivankovits schrieb: No way - http://www.cdolivet.net/editarea/editarea/docs/license.html - its LGPL Probably contacting the author and asking him to change the license or dual license it might be worth a try. Urgs sorry about that I

Re: [VOTE] Add MyfacesBuilderPlugin to buildtools branch and use it on myfaces 1.1

+1 definitely for jsf 1.1 we need something working and well documented. Leonardo Uribe schrieb: +1 On Tue, Apr 22, 2008 at 11:12 PM, Leonardo Uribe [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi MyfacesBuilderPlugin is now available for use on myfaces 1.1, so we can

[jira] Created: (TRINIDAD-1055) Navigation from treeTable fails if rootNodeRendered=false

Navigation from treeTable fails if rootNodeRendered=false --- Key: TRINIDAD-1055 URL: https://issues.apache.org/jira/browse/TRINIDAD-1055 Project: MyFaces Trinidad Issue Type: Bug

Re: [VOTE] Add MyfacesBuilderPlugin to buildtools branch and use it on myfaces 1.1

Werner Punz schrieb: +1 definitely for jsf 1.1 we need something working and well documented. Just to be clear: the options for the next core-1.1and tomahawk releases are: (a) the new myfaces-builder-plugin (b) the myfaces-faces-plugin (formerly called trinidad-faces-plugin) as currently used

Re: [VOTE] Add MyfacesBuilderPlugin to buildtools branch and use it on myfaces 1.1

Hi, +1 for (a) and for component class generation: Annotated class is a private class that is used as template (never instantiated, just the code is copied inside the generated class) (to not lose typeof checking in deeper trees - using abstract class in the middle would lose it for

Re: [VOTE] Add MyfacesBuilderPlugin to buildtools branch and use it on myfaces 1.1

+1a! Bruno On 23/04/2008, Sochor Zdeněk [EMAIL PROTECTED] wrote: Hi, +1 for (a) and for component class generation: Annotated class is a private class that is used as template (never instantiated, just the code is copied inside the generated class) (to not lose typeof checking in

Re: [VOTE] Add MyfacesBuilderPlugin to buildtools branch and use it on myfaces 1.1

+1 for (a) 2008/4/23 Bruno Aranda [EMAIL PROTECTED]: +1a! Bruno On 23/04/2008, Sochor Zdeněk [EMAIL PROTECTED] wrote: Hi, +1 for (a) and for component class generation: Annotated class is a private class that is used as template (never instantiated, just the code is

Re: [VOTE] Add MyfacesBuilderPlugin to buildtools branch and use it on myfaces 1.1

[EMAIL PROTECTED] schrieb: Werner Punz schrieb: +1 definitely for jsf 1.1 we need something working and well documented. Just to be clear: the options for the next core-1.1and tomahawk releases are: (a) the new myfaces-builder-plugin I am voting for a in this case the old trinidad plugin is

[jira] Commented: (TRINIDAD-1055) Navigation from treeTable fails if rootNodeRendered=false

[ https://issues.apache.org/jira/browse/TRINIDAD-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12591685#action_12591685 ] Andrew Robinson commented on TRINIDAD-1055: --- Assigning this to me to have a

Re: possible replacement for our kupu based html editor

Werner, This is great! On 4/23/08, Werner Punz [EMAIL PROTECTED] wrote: Actually our t:htmlEditor edit control (dont ask the exact name for it) which is rather old and based on a kupu sourcebase which originated from the pre GPL/LGPL times of the editor. Did not know that s: alread has a html

Re: [VOTE] Add MyfacesBuilderPlugin to buildtools branch and use it on myfaces 1.1

Before I vote, I am curious to know if there has been an audit of the functionality compared to the maven-faces-plugin tool. I am wondering about that I can think of right now: 1. component, facet and property meta data extensions that live in faces-config.xml 2. importing of code from shared

[jira] Resolved: (TRINIDAD-1) Add @agent support for skin properties

[ https://issues.apache.org/jira/browse/TRINIDAD-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeanne Waldman resolved TRINIDAD-1. --- Resolution: Fixed Fix Version/s: 1.2.8-core 1.0.8-core This will

Pending on the following patch!

Hi Team, Iam pending on applying the following patch : https://issues.apache.org/jira/browse/TOMAHAWK-1231 I cannot add new code before applying this patch to avoid conflicts. Would you please apply it when u have sometime ? I cannot apply now as Iam still pending on the account. Thanks. --

Re: Upgrading to MyFace 1.2 in Jboss Portal Server giving problem...

Souravm, There should be one in the demo project. You can get it here: http://www.apache.org/dyn/closer.cgi/myfaces/binaries/portlet-bridge-1.0.0-alpha-2-example.zip Scott souravm wrote: Hi Scott, I see your point. Thanks for the explanation. Can u pls share with me a sample web.xml

Re: Pending on the following patch!

Hi Hazem Do you want to implement the suggestion of Matthias, about be the h:commandButton or commandLink to surround the exporter? or you think that it is better as is right now? I'm not committed this by that reason (better make sure what this looks like). regards Leonardo Uribe On Wed, Apr

Re: [VOTE] Add MyfacesBuilderPlugin to buildtools branch and use it on myfaces 1.1

There are my personal opinions and solutions about each point : On Wed, Apr 23, 2008 at 12:48 PM, Andrew Robinson [EMAIL PROTECTED] wrote: Before I vote, I am curious to know if there has been an audit of the functionality compared to the maven-faces-plugin tool. I am wondering about that I

Re: FW: Myfaces Portlet does not work when a bean is stored in Requestscope...

Okay -- the JBoss portal must be validating the faces-config.xml file included in the jar. Anyway you can disable this? If not you will need to remove the offending stuff from the faces-config.xml file. The initial lines of the file (after the comments are: faces-config version="1.2"

Re: FW: Myfaces Portlet does not work when a bean is stored in Requestscope...

Ohh, good point Mike. I think he's picking this up from the faces config INSIDE of the bridge jars... Scott Michael Freedman wrote: Okay -- the JBoss portal must be validating the faces-config.xml file included in the jar. Anyway you can disable this? If not you will need to remove the

Re: FW: Myfaces Portlet does not work when a bean is stored in Requestscope...

Hey Mike, do we have a JIRA ticket on this? It SHOULD be able to pick the schema up from the jar. scott Scott O'Bryan wrote: Ohh, good point Mike. I think he's picking this up from the faces config INSIDE of the bridge jars... Scott Michael Freedman wrote: Okay -- the JBoss portal must

new name for sev-en

hello, 'sev-en' is just the intermediate (code-)name - let's find a final name. there will be some modules within commons-[new name] (which means several jar files). e.g.: required to use sev-en: commons-[new name]-core (currently one for jsf 1.1 and one for jsf 1.2) optional: commons-[new

Re: new name for sev-en

Sounds like fun, but I've already put enough on my plate :) Perhaps in the future. On Wed, Apr 23, 2008 at 4:45 PM, Gerhard Petracek [EMAIL PROTECTED] wrote: hello, 'sev-en' is just the intermediate (code-)name - let's find a final name. there will be some modules within commons-[new name]

Re: Pending on the following patch!

Hi Leonardo, I just wanted to have the two components integrated on the source repository. So that Me and Cagatay can start applying Matzew's idea. Thanks! On Wed, Apr 23, 2008 at 8:55 PM, Leonardo Uribe [EMAIL PROTECTED] wrote: Hi Hazem Do you want to implement the suggestion of Matthias,

Re: new name for sev-en

Couple of things. Can any of this be consolidated into fewer jars? I'm worried that the jars in the commons project are starting to look TOO segmented and functionality that is similar is not being put into a common jar. I haven't had time to take a look at Sev-en, but provided the

[jira] Updated: (TOMAHAWK-1238) CAPTCHA component - Enhancement #3 - Adding width, height attributes to CAPTCHA.

[ https://issues.apache.org/jira/browse/TOMAHAWK-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hazem Saleh updated TOMAHAWK-1238: -- Status: Patch Available (was: Open) CAPTCHA component - Enhancement #3 - Adding width,

CAPTCHA component - Enhancement #3 - Adding width, height attributes to CAPTCHA.

Hi Team, Please apply this patch when you have someTime. https://issues.apache.org/jira/browse/TOMAHAWK-1238 Thanks! -- Hazem Ahmed Saleh Ahmed http://www.jroller.com/page/HazemBlog