Site update not working?
I can't seem to get http://myfaces.apache.org/team-list.html to update. I used continuum to re-build the master project, then build the site project, but the site project is not picking up any of the changes to the master POM file (the developers in this case). I checked the continuum working directory and see that the file there is wrong in the target directory, so it is not a deployment problem. What am I missing? Thanks, -Andrew
Re: MyFaces PMC += Andrew Robinson
Thank you all for your support. I hope that I can continue to do good work for this project. 3/12/08, Grant Smith <[EMAIL PROTECTED]> wrote: > Nice job, Andrew :) > > On Tue, Mar 11, 2008 at 1:43 PM, Martin Marinschek < > [EMAIL PROTECTED]> wrote: > > > Welcome in the PMC! > > > > regards, > > > > Martin > > > > On Tue, Mar 11, 2008 at 10:27 PM, Matt Cooper <[EMAIL PROTECTED]> > > wrote: > > > Congratulations Andrew! > > > > > > > > > > > > On Tue, Mar 11, 2008 at 11:11 AM, Scott O'Bryan <[EMAIL PROTECTED]> > > wrote: > > > > -1.. > > > > > > > > Just kidding.. Congratulations Andrew. > > > > > > > > > > > > > > > > > > > > Matthias Wessendorf wrote: > > > > > Dear MyFaces community, > > > > > > > > > > please welcome our new MyFaces PMC member Andrew Robinson. > > > > > > > > > > Andrew is working on the Apache MyFaces and Trinidad stuff. > > > > > > > > > > Therefore last week there was a vote to invite him to the MyFaces > > > > > Project Management Committee (PMC) and fortunately he did accept. > > > > > > > > > > Andrew, > > > > > Please subscribe to the [EMAIL PROTECTED] list and update > > > > > your status on the site. Thanks. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > http://www.irian.at > > > > Your JSF powerhouse - > > JSF Consulting, Development and > > Courses in English and German > > > > Professional Support for Apache MyFaces > > > > > > -- > Grant Smith >
[jira] Commented: (TRINIDAD-948) the tr:commandNavigationItem does not handle leading "//" in the icon attribute to mean that the path is absolute
[ https://issues.apache.org/jira/browse/TRINIDAD-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578834#action_12578834 ] Richard Yee commented on TRINIDAD-948: -- This problem prevents having image files served from a separate web server when using the icon attribute in a commandNavigationItem. > the tr:commandNavigationItem does not handle leading "//" in the icon > attribute to mean that the path is absolute > - > > Key: TRINIDAD-948 > URL: https://issues.apache.org/jira/browse/TRINIDAD-948 > Project: MyFaces Trinidad > Issue Type: Bug > Components: Components >Affects Versions: 1.0.5-core > Environment: MyFaces 1.1.5, Trinidad 1.0.5 >Reporter: Richard Yee >Priority: Minor > Fix For: 1.0.5-core > > > The commandNavigationItem doesn't use the same API as tr:image uses to handle > the "source" attribute. The "//" should indicate that the path is an > absolute path. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [ANNOUNCE] Release of Apache MyFaces Portlet Bridge 1.0.0-alpha-2
Yup Matthias Wessendorf wrote: Good job! can you also post these news on: [EMAIL PROTECTED] [EMAIL PROTECTED] Thanks! Matthias On Fri, Mar 14, 2008 at 12:59 AM, Scott O'Bryan <[EMAIL PROTECTED]> wrote: The Apache MyFaces Portlet Bridge team is pleased to announce the release of Apache MyFaces Portlet Bridge 1.0.0-alpha-2. This release is intended as a development release and is not intended to be use in production environments. The Apache MyFaces Portlet Bridge project is intended to be the Reference Implementation for the specifications produced under JSR-301. Portlet Bridge 1.0.x releases will address the Bridge for JSF 1.2 and Portlet 1.0 while Portlet Bridge 2.0.x release will address the Bridge for JSF 1.2 and Portlet 2.0. Future projects will be added as Portlet/JSF version increase. Apache MyFaces Portlet Bridge 1.0.0-alpha-2 is available in both binary and source distributions: * http://myfaces.apache.org/portlet-bridge/download.html Apache MyFaces Portlet Bridge is available in the central Maven repository under Group ID "org.apache.myfaces.portlet-bridge". Release Notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310733&styleName=Html&version=12312834 Enjoy! Scott O'Bryan
[jira] Commented: (TRINIDAD-1006) PPR does not work for components setup programatically
[
https://issues.apache.org/jira/browse/TRINIDAD-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578794#action_12578794
]
Shane Petroff commented on TRINIDAD-1006:
-
Based on one of Matthais' comments on the users list, I've changed a bit of the
code. It works better now in the sense that both fields get updated when one
uses the declarative version, but the programmatic one is still broken. Is
there something else which needs to be set up?
public void returnedFromPage2( ReturnEvent event)
{
if (event.getReturnValue() != null)
{
Object[] array = (Object[]) event.getReturnValue();
System.out.println( "returned value " + array[0] );
setSessionText(array[0].toString());
UIComponent comp = event.getComponent().findComponent("txtID");
RequestContext afContext = RequestContext.getCurrentInstance();
afContext.addPartialTarget(comp);
}
}
> PPR does not work for components setup programatically
> --
>
> Key: TRINIDAD-1006
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1006
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Components
>Affects Versions: 1.0.6-core
> Environment: Win2K, Tomahawk 6.0.14, Firefox 2.0.0.12
>Reporter: Shane Petroff
>Priority: Blocker
> Attachments: testApp.war
>
>
> I've set up two sets of components which are supposed to be functionally
> identical, but they do no behave in the same way. Each pair is composed of a
> tr:inputText and a tr:commandButton. The first 'version' is composed into a
> standard page, and the second is created programmatically.
> The normal declarative version works fine, but the programmatic one does not.
> To get to this state, I used the maven create archetype
> (http://wiki.apache.org/myfaces/MyFaces_Archetypes_for_Maven) to generate a
> hello world app. I dropped back the version numbers for JSF 1.1 (tr v 1.0.6),
> then deployed to Tomcat 6.0.14. The return events are 'heard', but the PPR
> refresh never succeeds. The files below contain the respective changes to the
> hello world app. There are no errors either on the server or js, but the
> refresh never happens. I can't decipher the posts associated with the PPR
> activity. Any help appreciated, my only fall-back now is to drop Trinidad,
> thanks.
> Shane
> HelloWorldBacking.java**
> package org.apache.myfaces.trinidad.blank;
> import org.apache.myfaces.trinidad.context.RequestContext;
> import org.apache.myfaces.trinidad.event.ReturnEvent;
> import org.apache.myfaces.trinidad.component.core.input.CoreInputText;
> import org.apache.myfaces.trinidad.component.core.nav.CoreCommandButton;
> import javax.faces.component.html.HtmlSelectManyListbox;
> import javax.faces.component.html.HtmlPanelGrid;
> import javax.faces.model.SelectItem;
> import javax.faces.context.FacesContext;
> import javax.faces.application.Application;
> import java.util.List;
> import java.util.ArrayList;
> public class HelloWorldBacking
> {
>private HtmlSelectManyListbox m_CommentList;
>public HelloWorldBacking()
>{
>}
>public HtmlSelectManyListbox getCommentList()
>{
>return m_CommentList;
>}
>public void setCommentList(HtmlSelectManyListbox commentList )
>{
>m_CommentList = commentList;
>}
>public String cancelCommentLibrary()
>{
>RequestContext.getCurrentInstance().returnFromDialog(null, null);
>return null;
>}
>public String insertFromCommentLibrary()
>{
>Object returnValue = m_CommentList.getSelectedValues();
>RequestContext.getCurrentInstance().returnFromDialog(returnValue,
> null);
>return null;
>}
>public List getComments()
>{
>List comments = new ArrayList();
>comments.add(new SelectItem("This is a comment"));
>comments.add(new SelectItem("qwerty"));
>comments.add(new SelectItem("The quick brown fox jumped over the lazy
> sleeping dog"));
>return comments;
>}
>///
>public String getSessionText()
>{
>FacesContext context = FacesContext.getCurrentInstance();
>return (String)
> context.getExternalContext().getSessionMap().get("testText");
>}
>public void setSessionText(final String s)
>{
>FacesContext context = FacesContext.getCurrentInstance();
>context.getExternalContext().getSessionMap().put("testText", s);
>}
>public String onOpenPage2()
>{
>return "dialog:openPage2";
>}
>public void returnedFromPage2( ReturnEvent event)
>{
>if (event.getReturnValue() != null)
>{
>Object[] array
[jira] Commented: (TOBAGO-595) Support for tc:command onclick attribute in tc:columnEvent
[ https://issues.apache.org/jira/browse/TOBAGO-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578755#action_12578755 ] Helmut Swaczinna commented on TOBAGO-595: - Can you apply this patch please. > Support for tc:command onclick attribute in tc:columnEvent > -- > > Key: TOBAGO-595 > URL: https://issues.apache.org/jira/browse/TOBAGO-595 > Project: MyFaces Tobago > Issue Type: Improvement > Components: Core, Themes >Affects Versions: 1.0.13 > Environment: All >Reporter: Helmut Swaczinna > Attachments: TOBAGO-595.diff > > > The onclick attribute of tc:command in tc:columnEvent is not yet implemented > but useful to have -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TOBAGO-594) tc:columnEvent does not work with selectable="none"
[ https://issues.apache.org/jira/browse/TOBAGO-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578751#action_12578751 ] Helmut Swaczinna commented on TOBAGO-594: - Can you apply this patch please. > tc:columnEvent does not work with selectable="none" > --- > > Key: TOBAGO-594 > URL: https://issues.apache.org/jira/browse/TOBAGO-594 > Project: MyFaces Tobago > Issue Type: Bug > Components: Core, Themes >Affects Versions: 1.0.13 > Environment: All >Reporter: Helmut Swaczinna >Priority: Minor > Attachments: TOBAGO-594.diff > > > The action of tc:command of tc:columnEvent is not executed when the row > selection is not enabled in the sheet. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-997) tag with no attributes is not rendered when using Trinidad
[
https://issues.apache.org/jira/browse/TRINIDAD-997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Herr updated TRINIDAD-997:
---
Status: Patch Available (was: Open)
> tag with no attributes is not rendered when using Trinidad
> -
>
> Key: TRINIDAD-997
> URL: https://issues.apache.org/jira/browse/TRINIDAD-997
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Components, Facelets, Skinning
>Affects Versions: 1.0.6-core
>Reporter: Jonathan Herr
>Priority: Critical
> Attachments: elementOptimization.patch
>
>
> We recently integrated Trinidad into our application to evaluate it.
> Immediately we noticed that most pages would not render correctly. We
> discovered the problem was that if a tag had no attributes (id, class,
> etc.), it would not be rendered. For example:
>
> Example
>
>
> Renders as:
> Example
>
> In most applications this would not matter since by default the tag
> has no style, but we overrode the CSS of the tag to have very unique
> styles:
> form fieldset span { position: relative; display: block; width: 100%;
> margin-bottom: 6px; overflow: hidden; }
> If the tag was removed, we lost these styles and the page would be
> very distorted.
> Our only workaround right now is to update the hundreds of tags
> throughout our application and give them a class attribute so they will
> render.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[Orchestra] Are you using Orchestra ?
Hi, are you using Apache MyFaces Orchestra ? Please add your company to this list, if not already listed. http://wiki.apache.org/myfaces/Companies_Using_Orchestra Thanks! Matthias -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf mail: matzew-at-apache-dot-org
[Trinidad] Are you using Trinidad ?
Hi, are you using Apache MyFaces Trinidad ? Please add your company to this list, if not already listed. http://wiki.apache.org/myfaces/Companies_using_Trinidad Thanks! Matthias -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf mail: matzew-at-apache-dot-org
Re: [ANNOUNCE] Release of Apache MyFaces Portlet Bridge 1.0.0-alpha-2
Good job! can you also post these news on: [EMAIL PROTECTED] [EMAIL PROTECTED] Thanks! Matthias On Fri, Mar 14, 2008 at 12:59 AM, Scott O'Bryan <[EMAIL PROTECTED]> wrote: > The Apache MyFaces Portlet Bridge team is pleased to announce the > release of Apache MyFaces Portlet Bridge 1.0.0-alpha-2. This release is > intended as a development release and is not intended to be use in > production environments. > > The Apache MyFaces Portlet Bridge project is intended to be the > Reference Implementation for the specifications produced under JSR-301. > Portlet Bridge 1.0.x releases will address the Bridge for JSF 1.2 and > Portlet 1.0 while Portlet Bridge 2.0.x release will address the Bridge > for JSF 1.2 and Portlet 2.0. Future projects will be added as > Portlet/JSF version increase. > > Apache MyFaces Portlet Bridge 1.0.0-alpha-2 is available in both binary > and source distributions: > > * http://myfaces.apache.org/portlet-bridge/download.html > > Apache MyFaces Portlet Bridge is available in the central Maven > repository under Group ID "org.apache.myfaces.portlet-bridge". > > Release Notes: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310733&styleName=Html&version=12312834 > > Enjoy! > > Scott O'Bryan > > -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf mail: matzew-at-apache-dot-org
[jira] Commented: (TOBAGO-466) Extend AttributeHandler for handling methodexpression in a facelet composition
[ https://issues.apache.org/jira/browse/TOBAGO-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578670#action_12578670 ] Bernd Bohmann commented on TOBAGO-466: -- Yes, this should be possible adding an attribute to declare this is an methodbinding or a different Tag like attributeMethodXXX.. > Extend AttributeHandler for handling methodexpression in a facelet composition > -- > > Key: TOBAGO-466 > URL: https://issues.apache.org/jira/browse/TOBAGO-466 > Project: MyFaces Tobago > Issue Type: Improvement > Components: Facelets >Reporter: Bernd Bohmann >Assignee: Bernd Bohmann > Fix For: 1.0.12 > > > In a facelets composition a method expression as an argument did not work. > > > > > instead you can use the attribute tag > > > > the attribute tag evaluate the value expression and create if required a > method expression from the value of the expression. > If the value is not a value expression the attribute tag create the method > expression directly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] Created: (TOBAGO-637) Generate Components, JSP Tags from annotations
Hello Simon, simon schrieb: > Hi Bernd, > > On Thu, 2008-03-13 at 03:31 -0700, Bernd Bohmann (JIRA) wrote: >> Generate Components, JSP Tags from annotations > > Well, it seems like rewriting build systems is the trendy topic this > month :-) I wondered why you were smiling this afternoon while tapping > away on your keyboard; now I know. I'm smiling everytime :-) > > As there are now several people (you, myself, leonardo) working on new > build ideas, perhaps we (and anyone else interested) should pool our > ideas together? Yes, we should pool the ideas together. But I think let speek the code. > > Do you perhaps have any design documents describing how your new build > system works? I have had an initial look at the code, but am not > currently completely clear how things fit together. Of course I haven't > had any time to write up docs either; and I'm still experimenting > (committing on a branch, rather than committing to trunk as you are > doing). The build system is not new. I just extend the build system to generate the UIComponents, Tags and RendererWrapper. The former version generates the faces-config.xml and the tlds and Facelets configuration. > > The commits you made touch a lot of code; it seems to me that they > include patches for several unrelated things including adding ajax > support, making UIPanel a NamingContainer, etc. Is this right? For the faces-config and tld we don't need this kind of information. But for generating the components I need more metadata. > > I see some of the patch is removing saveState/restoreState methods, > which I presume is because these methods will be auto-generated later. > But I don't see removal of any Tag classes, which I would have expected > given the title of this commit. Is this coming later or have I > misunderstood something? I would like to ensure that it's save to delete the old code. > > Here's some points/questions I have after reading the code: > > (1) > You appear to be using ".stg" files as templates for code generation. > Does this stand for "org.antlr.stringtemplate.StringTemplateGroup"? > > http://www.stringtemplate.org/doc/api/org/antlr/stringtemplate/StringTemplateGroup.html > > Why did you choose this as a templating engine? Is it better than > Velocity or xslt for this task, or because you are more familiar with > it? The only reason is I don't like velocity. I think we can choose a different templating engine. > > (2) > The CreateComponentAnnotationVisitor class appears to be using the > StringTemplateGroup files to generate output. > > The CreateComponentAnnotationProcessor class first "visits" each > annotated object, effectively gathering needed metadata. > > Then CreateComponentAnnotationVisitor.process is then invoked to iterate > over the gathered data and apply it to the template. The createRenderer > method generates a renderer java file, and the createTag method > generates a tag java file. > Yes > (3) > You appear to be using the info from the annotations pretty directly to > generate the artifacts. Tag annotations contain the information used to > generate Tag classes etc. > > Yes > > > This is really not very different from what I would like to achieve with > the work I am doing. And really not too different from what the current > trinidad-derived build process currently does either. > yes > The issue I have is that the trinidad-based approach is very tightly > coupled to the concept that the input is an xml file in > almost-faces-config.xml format. Sadly, I just cannot plug into it to > provide an alternative way of building metadata. > > And it looks to me like your code is also very tightly coupled to the > concepts of the sun APT processor, and again cannot be extended to allow > other ways of building the metadata. > > What I would like to see (and am working towards) is a neutral format in > the middle (see ComponentModel, RendererModel, etc classes). Then > anything can populate this model (apt annotations, xml or doclet-tags). > The code just implements ModelBuilder and then fetches the data however > it wants. A Common Model would be nice, but I think it's not a easy step. > > And equally I hope to have a simple ModelProcessor interface. Then > multiple different implementations of that can exist, eg one that > uses .stg files to generate classes, or one that uses velocity to > generate facelets-taglib.xml files, or ... Yes > > Of course the common metadata representation would need to be carefully > chosen. For example, I would hope to avoid explicitly modelling "tag" > information; I regard that as something that can be derived from > information about the hand-written classes rather than something that > classes should explicitly declare. Therefore I would not personally have > a TagModel class. However that can certainly be debated, and there is > room for compromise I'm sure. > > Unfortunately, I cannot see how to apply the Tobago approach to myfaces > core, tomahawk,
