Re: [VOTE] Release Tobago 1.0.30
Hi Bernd, the release notes did not include TOBAGO-920 (The layout of the TabGroup is broken if one Tab is rendered=false). Wasn't this fixed before you tag this release? Regards, Volker 2010/9/28 Bernd Bohmann bernd.bohm...@atanion.com: Hello, I would like to release Tobago 1.0.30. For a detail list please consult the release notes: http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273styleName=Htmlversion=12315336 The version is available at the nexus staging repository. Staging repository: https://repository.apache.org/content/repositories/orgapachemyfaces-021/ The Vote is open for 72h. [ ] +1 [ ] +0 [ ] -1 Regards Bernd -- inexso - information exchange solutions GmbH Ofener Str. 30 | 26121 Oldenburg Tel.: +49 441 219 730 56 | FAX: +49 441 219 730 66 | eMail: volker.we...@inexso.de Firmensitz: Hamburg | Amtsgericht Hamburg, HRB 84273 Geschäftsführer: Stefan Schulte, Michael Terschüren, Dirk Fangohr
Re: [VOTE] Release Tobago 1.0.30
Hello Volker, TOBAGO-920 has the fixed version 1.0.30. I reasign the fixed version to 1.0.30. Now the release notes includes TOBAGO-920. Maybe a jira bug? Regards Bernd On Wed, Sep 29, 2010 at 9:08 AM, Volker Weber v.we...@inexso.de wrote: Hi Bernd, the release notes did not include TOBAGO-920 (The layout of the TabGroup is broken if one Tab is rendered=false). Wasn't this fixed before you tag this release? Regards, Volker 2010/9/28 Bernd Bohmann bernd.bohm...@atanion.com: Hello, I would like to release Tobago 1.0.30. For a detail list please consult the release notes: http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273styleName=Htmlversion=12315336 The version is available at the nexus staging repository. Staging repository: https://repository.apache.org/content/repositories/orgapachemyfaces-021/ The Vote is open for 72h. [ ] +1 [ ] +0 [ ] -1 Regards Bernd -- inexso - information exchange solutions GmbH Ofener Str. 30 | 26121 Oldenburg Tel.: +49 441 219 730 56 | FAX: +49 441 219 730 66 | eMail: volker.we...@inexso.de Firmensitz: Hamburg | Amtsgericht Hamburg, HRB 84273 Geschäftsführer: Stefan Schulte, Michael Terschüren, Dirk Fangohr
[jira] Created: (EXTCDI-66) deactivatable default implementations
deactivatable default implementations
-
Key: EXTCDI-66
URL: https://issues.apache.org/jira/browse/EXTCDI-66
Project: MyFaces CODI
Issue Type: New Feature
Components: Core, JEE-BV1-Module, JEE-JPA1-Module, JEE-JSF12-Module,
JEE-JSF20-Module, JSE-Message, JSE-Scripting, Trinidad Support
Reporter: Gerhard Petracek
it should be possible to deactivate classes which aren't pluggable via the
codi-config and which are activated per default.
esp. implementations which are configured via
- faces-config
- extension
- bean.xml
files.
that allows e.g. to tweak codi in cases of features/implementations which are
available out-of-the-box.
convention for an implementation of ClassDeactivator:
class-name: org.apache.myfaces.extensions.cdi.ClassDeactivator
e.g.:
package org.apache.myfaces.extensions.cdi;
import org.apache.myfaces.extensions.cdi.core.api.AbstractClassDeactivator;
public class ClassDeactivator extends AbstractClassDeactivator
{
protected void deactivateClasses()
{
addDeactivatedClass(...);
addDeactivatedClass(...);
}
}
or via vm param:
-Dorg.apache.myfaces.extensions.cdi.ClassDeactivator=custom.ClassDeactivator
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (EXTCDI-66) deactivatable default implementations
[
https://issues.apache.org/jira/browse/EXTCDI-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek resolved EXTCDI-66.
Fix Version/s: 1.0.0-SNAPSHOT
Resolution: Fixed
deactivatable default implementations
-
Key: EXTCDI-66
URL: https://issues.apache.org/jira/browse/EXTCDI-66
Project: MyFaces CODI
Issue Type: New Feature
Components: Core, JEE-BV1-Module, JEE-JPA1-Module, JEE-JSF12-Module,
JEE-JSF20-Module, JSE-Message, JSE-Scripting, Trinidad Support
Reporter: Gerhard Petracek
Fix For: 1.0.0-SNAPSHOT
it should be possible to deactivate classes which aren't pluggable via the
codi-config and which are activated per default.
esp. implementations which are configured via
- faces-config
- extension
- bean.xml
files.
that allows e.g. to tweak codi in cases of features/implementations which are
available out-of-the-box.
convention for an implementation of ClassDeactivator:
class-name: org.apache.myfaces.extensions.cdi.ClassDeactivator
e.g.:
package org.apache.myfaces.extensions.cdi;
import org.apache.myfaces.extensions.cdi.core.api.AbstractClassDeactivator;
public class ClassDeactivator extends AbstractClassDeactivator
{
protected void deactivateClasses()
{
addDeactivatedClass(...);
addDeactivatedClass(...);
}
}
or via vm param:
-Dorg.apache.myfaces.extensions.cdi.ClassDeactivator=custom.ClassDeactivator
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (EXTCDI-67) jsf2 scopes should be mapped to cdi scopes automatically
jsf2 scopes should be mapped to cdi scopes automatically Key: EXTCDI-67 URL: https://issues.apache.org/jira/browse/EXTCDI-67 Project: MyFaces CODI Issue Type: New Feature Components: JEE-JSF20-Module Reporter: Gerhard Petracek mapping: javax.faces.bean.ApplicationScoped - javax.enterprise.context.ApplicationScoped javax.faces.bean.SessionScoped - javax.enterprise.context.SessionScoped javax.faces.bean.RequestScoped - javax.enterprise.context.RequestScoped javax.faces.bean.ManagedBean - javax.inject.Named -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (EXTCDI-67) jsf2 scopes should be mapped to cdi scopes automatically
[ https://issues.apache.org/jira/browse/EXTCDI-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek resolved EXTCDI-67. Fix Version/s: 1.0.0-SNAPSHOT Resolution: Fixed jsf2 scopes should be mapped to cdi scopes automatically Key: EXTCDI-67 URL: https://issues.apache.org/jira/browse/EXTCDI-67 Project: MyFaces CODI Issue Type: New Feature Components: JEE-JSF20-Module Reporter: Gerhard Petracek Fix For: 1.0.0-SNAPSHOT mapping: javax.faces.bean.ApplicationScoped - javax.enterprise.context.ApplicationScoped javax.faces.bean.SessionScoped - javax.enterprise.context.SessionScoped javax.faces.bean.RequestScoped - javax.enterprise.context.RequestScoped javax.faces.bean.ManagedBean - javax.inject.Named -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TRINIDAD-1929) Trinidad CoreRenderer.encodeChild does not call encodeAll method on the child
Trinidad CoreRenderer.encodeChild does not call encodeAll method on the child
-
Key: TRINIDAD-1929
URL: https://issues.apache.org/jira/browse/TRINIDAD-1929
Project: MyFaces Trinidad
Issue Type: Bug
Affects Versions: 2.0.0.3-core
Reporter: Andrew Robinson
Assignee: Andrew Robinson
Priority: Critical
Fix For: 2.0.0.3-core
JSF2 introduced the encodeAll method on UIComponent. Trinidad's CoreRenderer is
not utilizing this method. Instead it is using:
protected void encodeChild(
FacesContext context,
UIComponent child
) throws IOException
{
assert(child.isRendered());
child.encodeBegin(context);
if (child.getRendersChildren())
{
child.encodeChildren(context);
}
else
{
if (child.getChildCount() 0)
{
for(UIComponent subChild : (ListUIComponent)child.getChildren())
{
RenderUtils.encodeRecursive(context, subChild);
}
}
}
child.encodeEnd(context);
}
It should be using the JSF 2 encodeAll method instead.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TRINIDAD-1927) Trinidad 2 CoreRenderer.encodeChild does not call the JSF 2 encodeAll method on the child
[
https://issues.apache.org/jira/browse/TRINIDAD-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Robinson resolved TRINIDAD-1927.
---
Fix Version/s: 2.0.0.3-core
Resolution: Fixed
Changed Trinidad 2 to use encodeAll. This should be done for Trinidad 1.2 as
well.
Trinidad 2 CoreRenderer.encodeChild does not call the JSF 2 encodeAll method
on the child
-
Key: TRINIDAD-1927
URL: https://issues.apache.org/jira/browse/TRINIDAD-1927
Project: MyFaces Trinidad
Issue Type: Bug
Affects Versions: 2.0.0.3-core
Reporter: Andrew Robinson
Assignee: Andrew Robinson
Priority: Critical
Fix For: 2.0.0.3-core
JSF2 introduced the encodeAll method on UIComponent. Trinidad's CoreRenderer
is not utilizing this method. Instead it is using:
protected void encodeChild(
FacesContext context,
UIComponent child
) throws IOException
{
assert(child.isRendered());
child.encodeBegin(context);
if (child.getRendersChildren())
{
child.encodeChildren(context);
}
else
{
if (child.getChildCount() 0)
{
for(UIComponent subChild : (ListUIComponent)child.getChildren())
{
RenderUtils.encodeRecursive(context, subChild);
}
}
}
child.encodeEnd(context);
}
It should be using the JSF 2 encodeAll method instead.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (EXTCDI-68) view-controller annotations based on view-config
view-controller annotations based on view-config Key: EXTCDI-68 URL: https://issues.apache.org/jira/browse/EXTCDI-68 Project: MyFaces CODI Issue Type: New Feature Components: JEE-JSF12-Module, JEE-JSF20-Module Reporter: Gerhard Petracek instead of using @BeforePhase(INVOKE_APPLICATION) and @BeforePhase(RENDER_RESPONSE) it should be possible to use @PreViewAction and @PreRenderView within page-beans (specified via the view-config). these annotations are easier to use and they are integrated a bit better. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (EXTCDI-68) view-controller annotations based on view-config
[ https://issues.apache.org/jira/browse/EXTCDI-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek resolved EXTCDI-68. Fix Version/s: 1.0.0-SNAPSHOT Resolution: Fixed view-controller annotations based on view-config Key: EXTCDI-68 URL: https://issues.apache.org/jira/browse/EXTCDI-68 Project: MyFaces CODI Issue Type: New Feature Components: JEE-JSF12-Module, JEE-JSF20-Module Reporter: Gerhard Petracek Fix For: 1.0.0-SNAPSHOT instead of using @BeforePhase(INVOKE_APPLICATION) and @BeforePhase(RENDER_RESPONSE) it should be possible to use @PreViewAction and @PreRenderView within page-beans (specified via the view-config). these annotations are easier to use and they are integrated a bit better. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TRINIDAD-1930) Ability to easily create a meta tag
Ability to easily create a meta tag
---
Key: TRINIDAD-1930
URL: https://issues.apache.org/jira/browse/TRINIDAD-1930
Project: MyFaces Trinidad
Issue Type: Improvement
Components: Components
Affects Versions: 1.2.14-core , 2.0.0.2-core
Reporter: Matt Cooper
Assignee: Matt Cooper
Ability to easily create a meta tag (e.g.
http://developer.apple.com/library/safari/#documentation/appleapplications/reference/safarihtmlref/articles/MetaTags.html
or http://www.webmarketingnow.com/tips/meta-tags-uncovered.html ) via a new
trh:meta tag.
Currently it is quite tedious to create a meta tag out of a component:
tr:document ...
f:facet name=metaContainer
tr:group id=metaContainer
tr:outputText escape=false
value='lt;meta name=viewport
content=width=device-width'
id=metaTag1/
tr:outputText escape=false
value='lt;meta name=apple-mobile-web-app-capable
content=yes'
id=metaTag2/
tr:outputText escape=false
value='lt;meta http-equiv=refresh
content=2;url=./test/index.jspx'
id=metaTag3/
/tr:group
/f:facet
/tr:document
It would be much better if we had a trh:meta component that looked like this:
tr:document ...
f:facet name=metaContainer
tr:group id=metaContainer
trh:meta name=viewport content=width=device-width/
trh:meta name=apple-mobile-web-app-capable content=yes/
trh:meta name=refresh nameType=http-equiv
content=2;url=./test/index.jspx/
/tr:group
/f:facet
/tr:document
So I would like to see a new trh:meta component that has an API like this:
Tag name: trh:meta
UIComponent class: org.apache.myfaces.trinidad.component.core.CoreMeta
Component type: org.apache.myfaces.trinidad.CoreMeta
The meta component generates an HTML meta tag and is intended to be used inside
either the trh:head tag or the document component's metaContainer facet.
Events
TypePhases Description
org.apache.myfaces.trinidad.event.AttributeChangeEvent Invoke Application,
Apply Request ValuesEvent delivered to describe an attribute change.
Attribute change events are not delivered for any programmatic change to a
property. They are only delivered when a renderer changes a property without
the application's specific request. An example of an attribute change events
might include the width of a column that supported client-side resizing.
Attributes
NameTypeSupports EL?Description
attributeChangeListener javax.el.MethodExpression Only EL
a method reference to an attribute change listener. Attribute change events are
not delivered for any programmatic change to a property. They are only
delivered when a renderer changes a property without the application's specific
request. An example of an attribute change events might include the width of a
column that supported client-side resizing.
binding org.apache.myfaces.trinidad.component.core.CoreMeta Only EL
an EL reference that will store the component instance on a bean. This
can be used to give programmatic access to a component from a backing bean, or
to move creation of the component to a backing bean.
id String No the identifier for the component. The identifier must
follow a subset of the syntax allowed in HTML:
* Must not be a zero-length String.
* First character must be an ASCII letter (A-Za-z) or an underscore ('_').
* Subsequent characters must be an ASCII letter or digit (A-Za-z0-9), an
underscore ('_'), or a dash ('-').
renderedboolean Yes whether the component is rendered. When
set to false, no output will be delivered for this component (the component
will not in any way be rendered, and cannot be made visible on the client).
nameString Yes the name or http-equiv attribute of the meta attribute
(see nameType)
nameTypeString Yes name or http-equiv indicating which kind of
name attribute is desired (name is the most common attribute but some older
meta tags need http-equiv)
content String Yes the content of the meta attribute
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (TRINIDAD-1931) Date-Time converter does not use 2DigitYearStart for parsing
Date-Time converter does not use 2DigitYearStart for parsing Key: TRINIDAD-1931 URL: https://issues.apache.org/jira/browse/TRINIDAD-1931 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions: 1.2.13-core Reporter: Yee-Wah Lee According to the doc: http://myfaces.apache.org/trinidad/devguide/configuration.html#trinidad-config.xml The two-digit-year-start element defines the year offset that should be used for parsing years with only two digits. If it is not set, it is defaulted to year 1950. This value is used by org.apache.myfaces.trinidad.converter.DateTimeConverter while converting strings to Date. This property may also be explicitly configured with an EL expression that returns Integer object if needed or can be directly harcoded to a integer value. This is not apparently used by the DateTimeConverter in parsing, probably a regression from TRINIDAD-208. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-2931) Regression: Template areas get lost when using ui:include
[ https://issues.apache.org/jira/browse/MYFACES-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12916359#action_12916359 ] Leonardo Uribe commented on MYFACES-2931: - Hi Christian Yes, the fix could possibly break existing applications but note the opposite is also true, if we don't apply the fix, there are other examples that are valid in syntax but fails (MYFACES-2753). After thinking a lot and checking the documentation left from the original author of facelets, including check facelets cvs and issue tracking, I think the right choice was apply it (really that conclusion was very difficult to find, because that code is the less documented but most important in facelets). Other argument that suggest the fixed behavior is preferred is related to the attributes of ui:include and ui:decorate tag. Note that ui:decorate has template attribute, but ui:include has src attribute. Therefore, the first one suggest the link points to a template, but the second one suggest that it points to a part or page. Regression: Template areas get lost when using ui:include Key: MYFACES-2931 URL: https://issues.apache.org/jira/browse/MYFACES-2931 Project: MyFaces Core Issue Type: Bug Components: General Affects Versions: 2.0.2 Reporter: Christian Kaltepoth Template areas specified with ui:define are not visible in files that the template includes with ui:include. See the following example. The template: http://github.com/chkal/myfaces-tests/blob/vdl-insert-bug/src/main/webapp/template.xhtml The file included by the template: http://github.com/chkal/myfaces-tests/blob/vdl-insert-bug/src/main/webapp/header.xhtml The page using the template: http://github.com/chkal/myfaces-tests/blob/vdl-insert-bug/src/main/webapp/page.xhtml MyFaces 2.0.2 will show Wrong Title in the title div, which is the default value of the ui:insert. MyFaces 2.0.1 and Mojarra will instead display Correct Title, which is the value definied in page.xhtml via ui:define. You can download an example application demonstrating this issue here: http://github.com/chkal/myfaces-tests/archives/vdl-insert-bug Start the app with: mvn jetty:run The page is then available here: http://localhost:9090/ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-2931) Regression: Template areas get lost when using ui:include
[ https://issues.apache.org/jira/browse/MYFACES-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12916382#action_12916382 ] Christian Kaltepoth commented on MYFACES-2931: -- Hi Leonardo, I think you are right. I wasn't aware of the problems described in MYFACES-2753. I originally thought that inheriting template areas to files imported via ui:include would be some kind of nice-to-have feature that won't break anything and is spec compliant (as the spec doesn't explicitly include a statement regarding this). I see you did some intensive research on this topic! ;-) Keep up the good work! :-) Regression: Template areas get lost when using ui:include Key: MYFACES-2931 URL: https://issues.apache.org/jira/browse/MYFACES-2931 Project: MyFaces Core Issue Type: Bug Components: General Affects Versions: 2.0.2 Reporter: Christian Kaltepoth Template areas specified with ui:define are not visible in files that the template includes with ui:include. See the following example. The template: http://github.com/chkal/myfaces-tests/blob/vdl-insert-bug/src/main/webapp/template.xhtml The file included by the template: http://github.com/chkal/myfaces-tests/blob/vdl-insert-bug/src/main/webapp/header.xhtml The page using the template: http://github.com/chkal/myfaces-tests/blob/vdl-insert-bug/src/main/webapp/page.xhtml MyFaces 2.0.2 will show Wrong Title in the title div, which is the default value of the ui:insert. MyFaces 2.0.1 and Mojarra will instead display Correct Title, which is the value definied in page.xhtml via ui:define. You can download an example application demonstrating this issue here: http://github.com/chkal/myfaces-tests/archives/vdl-insert-bug Start the app with: mvn jetty:run The page is then available here: http://localhost:9090/ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
