[Trinidad] Patch Review for Mobile Development

[mamallan . uthaman]

Hi all,

I have uploaded a patch (TRINIDAD- 1728) for handling Opera-Mobile 
browser that runs in HTC device. You are welcome to review the patch.


Thanks
Mamallan

[jira] Issue Comment Edited: (TRINIDAD-1728) Trinidad not supporting Opera Mobile in HTC

[Mamallan Uthaman (JIRA)]

[ 
https://issues.apache.org/jira/browse/TRINIDAD-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834611#action_12834611
 ] 

Mamallan Uthaman edited comment on TRINIDAD-1728 at 2/17/10 2:32 AM:
-

This patch applies to the branches 1.2.12.2 and  1.2.12.1

  was (Author: mamallan.uthaman):
This patch applies to the branches 1.2.12.2 and  1.2.12.21
  
> Trinidad not supporting Opera Mobile in HTC
> ---
>
> Key: TRINIDAD-1728
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1728
> Project: MyFaces Trinidad
>  Issue Type: Bug
>  Components: Components
>Affects Versions: 1.2.13-core 
> Environment: HTC Opera Mobile
>Reporter: Mamallan Uthaman
>Priority: Minor
> Attachments: TRINIDAD-1728.patch
>
>
> Trinidad is not handling requests from Opera Mobile running in HTC. The 
> reason is current user-agent parsing logic for Opera mobile cannot handle 
> requests from HTC.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (TRINIDAD-1728) Trinidad not supporting Opera Mobile in HTC

[Mamallan Uthaman (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TRINIDAD-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mamallan Uthaman updated TRINIDAD-1728:
---

Status: Patch Available  (was: Open)

> Trinidad not supporting Opera Mobile in HTC
> ---
>
> Key: TRINIDAD-1728
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1728
> Project: MyFaces Trinidad
>  Issue Type: Bug
>  Components: Components
>Affects Versions: 1.2.13-core 
> Environment: HTC Opera Mobile
>Reporter: Mamallan Uthaman
>Priority: Minor
>
> Trinidad is not handling requests from Opera Mobile running in HTC. The 
> reason is current user-agent parsing logic for Opera mobile cannot handle 
> requests from HTC.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (TRINIDAD-1729) provide a hook for for an external decorator of Skin InputStreamProvider

[Jeanne Waldman (JIRA)]

provide a hook for for an external decorator of Skin InputStreamProvider


 Key: TRINIDAD-1729
 URL: https://issues.apache.org/jira/browse/TRINIDAD-1729
 Project: MyFaces Trinidad
  Issue Type: Improvement
  Components: Skinning
Reporter: Jeanne Waldman
Assignee: Jeanne Waldman


A third party (Oracle MDS) would like to use their own InputStreamProvider to 
find skinning css files (like purple-desktop.css) in their own system. The 
current ways to find css files do not work for them.
1. We first discussed decorating ExternalContext.getResource(), since in
Trinidad we create the URL by calling FacesContext's ExternalContext's
getResource(style-sheet-name). For an example, see
http://insights2jsf.wordpress.com/2009/07/03/using-custom-factories-or-howto-wrap-facescontext/
2. This won't work for them because it returns an URL object
3. using ExternalContext's getResourceAsStream won't work because you can't 
find out if the file has been modified.
4. What would work is if they decorate or extend the InputStreamProvider, and 
we check this if none of the other means finds the .css file. The other means 
are those found in SkinStyleSheetProvider.java
5. To allow them to plugin their InputStreamProvider we
can do this with a service provider interface where we open up
META-INF/services/ and load all of the
services that way.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (TRINIDAD-1728) Trinidad not supporting Opera Mobile in HTC

[Mamallan Uthaman (JIRA)]

Trinidad not supporting Opera Mobile in HTC
---

 Key: TRINIDAD-1728
 URL: https://issues.apache.org/jira/browse/TRINIDAD-1728
 Project: MyFaces Trinidad
  Issue Type: Bug
  Components: Components
Affects Versions: 1.2.13-core 
 Environment: HTC Opera Mobile
Reporter: Mamallan Uthaman
Priority: Minor


Trinidad is not handling requests from Opera Mobile running in HTC. The reason 
is current user-agent parsing logic for Opera mobile cannot handle requests 
from HTC.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (TRINIDAD-1723) Trinidad 2: ClassCastEXception while running componentDemos.jspx

[Jeanne Waldman (JIRA)]

[ 
https://issues.apache.org/jira/browse/TRINIDAD-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834515#action_12834515
 ] 

Jeanne Waldman commented on TRINIDAD-1723:
--

Good find. I agree that this definitely seems like a bug in WLS.

> Trinidad 2: ClassCastEXception while running componentDemos.jspx
> 
>
> Key: TRINIDAD-1723
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1723
> Project: MyFaces Trinidad
>  Issue Type: Bug
>  Components: Components
>Affects Versions: 2.0.0-alpha-2
>Reporter: Max Starets
>
> Grab the latest trinidad-2.0.x branch and try running componentDemos.jspx. 
> The following exception will be thrown:
> java.lang.ClassCastException: 
> org.apache.myfaces.trinidadinternal.uinode.UIComponentUINode cannot be cast 
> to org.apache.myfaces.trinidadinternal.uinode.UIXComponentUINode
>   at 
> org.apache.myfaces.trinidadinternal.uinode.UIXComponentUINode.__getAdapter(UIXComponentUINode.java:439)
>   at 
> org.apache.myfaces.trinidadinternal.uinode.UINodeRendererBase.encodeEnd(UINodeRendererBase.java:65)
>   at 
> org.apache.myfaces.trinidad.component.UIXComponentBase.encodeEnd(UIXComponentBase.java:852)
>   at 
> org.apache.myfaces.trinidad.render.RenderUtils.encodeRecursive(RenderUtils.java:70)
>   at 
> org.apache.myfaces.trinidad.render.CoreRenderer.encodeChild(CoreRenderer.java:509)
>   at 
> org.apache.myfaces.trinidad.render.CoreRenderer.encodeAllChildren(CoreRenderer.java:531)
>   at 
> org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.PanelPartialRootRenderer.renderContent(PanelPartialRootRenderer.java:70)
>   at 
> org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.BodyRenderer.renderContent(BodyRenderer.java:151)
>   at 
> org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.PanelPartialRootRenderer.encodeAll(PanelPartialRootRenderer.java:153)
>   at 
> org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.BodyRenderer.encodeAll(BodyRenderer.java:80)
>   at 
> org.apache.myfaces.trinidad.render.CoreRenderer.delegateRenderer(CoreRenderer.java:546)
>   at 
> org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.DocumentRenderer.encodeAll(DocumentRenderer.java:82)
> This does not seem to be JSF 2 specific, but I have not had time to try it on 
> the latest MAIN.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (TRINIDAD-1722) Trinidad 2: Wrong locale rule used in skinng

[Max Starets (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TRINIDAD-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Max Starets resolved TRINIDAD-1722.
---

   Resolution: Fixed
Fix Version/s: 2.0.0-alpha-2
 Assignee: Max Starets

Thanks for the patch, Andy Schwartz!

> Trinidad 2: Wrong locale rule used in skinng
> 
>
> Key: TRINIDAD-1722
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1722
> Project: MyFaces Trinidad
>  Issue Type: Bug
>  Components: Skinning
>Affects Versions: 2.0.0-alpha-2
>Reporter: Max Starets
>Assignee: Max Starets
> Fix For: 2.0.0-alpha-2
>
> Attachments: trinidad-1722.patch
>
>
> To reproduce the issue,  run table.jspx in Firefox with the latest 2.0.x 
> branch. Notice that the font size is huge. For some strange reason, the skin 
> picks up the following Thai locale rule in base-desktop.xss:
> 
> 
>   
> Browallia 
> New,Arial,Helvetica,Geneva,sans-serif
> 16pt
>   
> If you remove the rule, everything runs fine. If you use IE, it works fine 
> too.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

RE: [TRINIDAD][API]TRINIDAD-1668 Speed up UIXComponent.getId()

[Maria Kaval]

Are JIRA 1668 and JIRA 1700 dupes?
Maria

-Original Message-
From: Blake Sullivan 
Sent: Tuesday, January 19, 2010 12:09 PM
To: MyFaces Development
Subject: Re: [TRINIDAD][API]TRINIDAD-1668 Speed up UIXComponent.getId()

The api part of the fix is that UIXFacesBeanImpl and 
UIXEditableFacesBeanImpl have been moved to 
org.apache.myfaces.trinidad.component.  There is nothing interesting 
about these classes and it was kind of rude that they were present only 
in impl, since everyone needs an implementation (for example, the test 
code had copies of these classes).  By moving these classes to api, 
FacesBeanImpl can tell when it is OK to optimize by storing the id 
locally and when it isn't.

There is also one subtle behavior change.  getId() never returns null in 
the current code.  The old code would return null for getId() (but not 
for getClientId()) until the id was set.  That behavior was bad since it 
resulted in cases where the last element of the clientId was not the 
component's id.  The JSF RI code as slightly better, but still incorrect 
behavior--it sets the component's id as a side effect of calling 
getClientId() if the component's id isn't set.

-- Blake Sullivan


Blake Sullivan said the following On 1/6/2010 4:20 PM PT:
> OK.  I got smarter and looked more carefully at the FacesBean 
> implementations. The best solution is to modify 
> org.apache.myfaces.trinidadinternal.bean.UIXFacesBeanImpl to hang onto 
> the UIXComponent passed to init() and then override setProperty(), 
> getLocalPropertyImpl(), saveState(), and restoreState() to handle the 
> id attribute by calling _component.getId()/setId() as appropriate.  No 
> api changes and the change is encapsulated in UIXFacesBeanImpl and 
> UIXComponentBase.
>
> -- Blake Sullivan
>
>
> \Simon Lessard said the following On 1/6/2010 10:40 AM PT:
>> Hi Blake,
>>
>> Yep, that's exactly what I meant. I'm aware that the main risk lies with
>> compatibility, but I think it's minimal.
>>
>>
>> Regards,
>>
>> ~ Simon
>>
>> On Tue, Jan 5, 2010 at 8:00 PM, Blake Sullivan 
>> wrote:
>>
>>  
>>>  Simon Lessard said the following On 1/5/2010 2:34 PM PT:
>>>
>>> Blake,
>>>
>>> For 1, both possibilities exist. However, I would prefer them to not be
>>> available on the FacesBean from a performance PoV. Those don't have 
>>> indexed
>>> property keys anyway so the lookup for them is actually quite 
>>> inefficient.
>>> That would requires some additional changes to the state saving though.
>>>
>>>
>>>  Hmm.  I believe that FlaggedPropertyMap uses a HashMap to store 
>>> these, so
>>> they aren't that bad.(this isn't necessarily the best choice for 
>>> size
>>> reasons, but that's a separate issue)
>>>
>>> We are talking about optimization at the constant level--all proposed
>>> mechanism are O(1) in all cases right now.  The differences between the
>>> different proposals are:
>>>
>>>
>>>  1) Current
>>>  2) ValueExpression Proposal
>>>  3) Split AttributeMap and FacesBean (Simon's proposal A)
>>>  4) Simon's  Custom Properties in FacesBean-B
>>>   UIComponent.getFoo()
>>>  Flagged Map Access
>>>  Flagged Map Access Flagged Map Access Flagged Map Access  *
>>> UIComponent.getId()* *Map Access (since id always set)
>>> * *Direct
>>> * *Direct
>>> * *Direct*
>>>   FacesBean.getProperty(FOO_KEY)
>>>  Flagged Map Access Flagged Map Access Flagged Map Access
>>>
>>>  Flagged Map Access  *UIComponent.getAttributes().get("foo")
>>> * *2 Map Accesses* *2 Map Accesses* *2 Map Accesses (one flagged) and a
>>> reflection call
>>> * *2 Map Accesses (one flagged) and a reflection call*  *
>>> UIComponent.getAttributes().get("id")
>>> * *2 Map Accesses
>>> * *2 Map Accesses, 1 cast and  function call
>>> * *1 Map Access and reflection call
>>> * *1 Map Access and reflection call*  
>>> *UIComponent.getAttributes().get("custom
>>> foo")* *2 Map Accesses* *2 Map Accesses* *Map access
>>> * *2 Map Accesses (one flagged) and a reflection call*  *
>>> *I've bold-faced the rows that are actually different.
>>>
>>> The proposals also differ slightly with regards to whether the same 
>>> values
>>> are available through the attributeMap, UIComponent direct accessor, 
>>> and the
>>> FacesBean.  The current implementation makes all three of these 
>>> identical.
>>> The ValueExpression does likewise.  In the split implementation custom
>>> attributes aren't available from the FacesBean.  In the custom 
>>> properties
>>> case, proeprties that were optimized, wouldn't be available from the
>>> FacesBean, which may or may not be OK (some Renderer apis 
>>> unfortunately only
>>> pass FacesBeans and not the UIComponent as well)
>>>
>>> Another option for speeding up attributes like getId(), would be to 
>>> add a
>>> different flag to the PROPERTY_KEYS, requesting that the storage of 
>>> this
>>> particular property be optimized.  Depending on how flexible the use of
>>> these keys needed to be, this could result in only the lowest keys 
>>> being
>>> allowed to be opti

[Announce] Release of Apache MyFaces Trinidad 1.0.12

[Matthias Wessendorf]

The Apache MyFaces Trinidad team is pleased to announce the release of
Apache MyFaces Trinidad Core 1.0.12.

Apache MyFaces Trinidad is a JavaServer(tm) Faces 1.1 component library.

Trinidad Core 1.0.12 is available in both binary and source distributions:

 * http://myfaces.apache.org/trinidad/download.html

Apache MyFaces Trinidad is available in the central Maven repository under
Group ID "org.apache.myfaces.trinidad".


Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310661&styleName=Html&version=12314137

Enjoy!

-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

[Announce] Release of Apache MyFaces Trinidad 2.0.0-alpha-2

[Matthias Wessendorf]

The Apache MyFaces Trinidad team is pleased to announce the release of
Apache MyFaces Trinidad Core 2.0.0-alpha-2.

Apache MyFaces Trinidad 2 is a JavaServer(tm) Faces 2.0 component library.

Note: This is the second release of the Apache MyFaces Trinidad 2 series and it
is an alpha relases.

Apache MyFaces Trinidad Core 2.0.0-alpha-2 is available in both binary
and source distributions:

 * http://myfaces.apache.org/trinidad/download.html

Apache MyFaces Trinidad is available in the central Maven repository under
Group ID "org.apache.myfaces.trinidad".


Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310661&styleName=Html&version=12314513

Enjoy!
Matthias


-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

[jira] Commented: (MYFACES-2561) StackOverflowError if a composite component implementation uses another composite component

[Jakob Korherr (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834291#action_12834291
 ] 

Jakob Korherr commented on MYFACES-2561:


OK, good to know.

I opened this issue, because on mojarra the code works. I will try find out 
which spec-change was applied here and provide a patch. After a review we can 
then commit it.

> StackOverflowError if a composite component implementation uses another 
> composite component
> ---
>
> Key: MYFACES-2561
> URL: https://issues.apache.org/jira/browse/MYFACES-2561
> Project: MyFaces Core
>  Issue Type: Bug
>  Components: JSR-314
>Affects Versions: 2.0.0-beta-3
>Reporter: Jakob Korherr
>Assignee: Jakob Korherr
>
> If you use another composite component in your composite component's 
> implementation you will get a StackOverflowError.
> javax.faces.FacesException: java.lang.StackOverflowError
>   at 
> org.apache.myfaces.context.ExceptionHandlerImpl.wrap(ExceptionHandlerImpl.java:241)
>   at 
> org.apache.myfaces.context.ExceptionHandlerImpl.handle(ExceptionHandlerImpl.java:156)
>   at 
> org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:216)
>   at javax.faces.webapp.FacesServlet.service(FacesServlet.java:191)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>   at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>   at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>   at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
>   at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>   at 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>   at 
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
>   at 
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:849)
>   at 
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
>   at 
> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:454)
>   at java.lang.Thread.run(Thread.java:637)
> Caused by: java.lang.StackOverflowError
>   at java.util.ArrayList.toArray(ArrayList.java:306)
>   at java.util.logging.Logger.getHandlers(Logger.java:1200)
>   at 
> java.util.logging.LogManager$RootLogger.getHandlers(LogManager.java:1019)
>   at java.util.logging.Logger.log(Logger.java:454)
>   at java.util.logging.Logger.doLog(Logger.java:480)
>   at java.util.logging.Logger.logp(Logger.java:680)
>   at org.apache.juli.logging.DirectJDKLog.log(DirectJDKLog.java:167)
>   at org.apache.juli.logging.DirectJDKLog.error(DirectJDKLog.java:135)
>   at org.apache.catalina.connector.Request.setAttribute(Request.java:1448)
>   at 
> org.apache.catalina.connector.RequestFacade.setAttribute(RequestFacade.java:503)
>   at 
> org.apache.myfaces.context.servlet.RequestMap.setAttribute(RequestMap.java:53)
>   at 
> org.apache.myfaces.util.AbstractAttributeMap.put(AbstractAttributeMap.java:113)
>   at 
> org.apache.myfaces.util.AbstractAttributeMap.put(AbstractAttributeMap.java:1)
>   at 
> org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver.setScope(FacesCompositeELResolver.java:191)
>   at 
> org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:139)
>   at org.apache.el.parser.AstIdentifier.getValue(AstIdentifier.java:61)
>   at org.apache.el.parser.AstValue.getValue(AstValue.java:107)
>   at 
> org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186)
>   at 
> org.apache.myfaces.view.facelets.el.TagValueExpression.getValue(TagValueExpression.java:84)
>   at 
> org.apache.myfaces.el.unified.resolver.CompositeComponentELResolver$CompositeComponentAttributesMapWrapper.get(CompositeComponentELResolver.java:245)
>   at javax.el.MapELResolver.getValue(MapELResolver.java:51)
>   at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:54)
>   at 
> org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:140)
>   at org.apache.el.parser.AstValue.getValue(AstValue.java:118)
>   at 
> org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186)
>   at 
> org.apache.myfaces.view.facelets.el.TagValueExpression.getValue(TagValueExpression.java:84)
>   at 
> org.apache.myfaces.el.unified.resolver.CompositeCompo

[jira] Commented: (TOMAHAWK-596) Duplicate id exception for HtmlDataScrollerRenderer

[Razan Abbass (JIRA)]

[ 
https://issues.apache.org/jira/browse/TOMAHAWK-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834290#action_12834290
 ] 

Razan Abbass commented on TOMAHAWK-596:
---

[buy cheap tramadol o|http://ptl.sys.virginia.edu/@api/deki/files/257]
[buy tramadol at a cheap price 
online|http://ptl.sys.virginia.edu/@api/deki/files/258]
[buy cheap tramadol online 
inurl|http://ptl.sys.virginia.edu/@api/deki/files/259]
[buy cheap tramadol online 
inurl|http://ptl.sys.virginia.edu/@api/deki/files/260]
[cheapest tramadol without 
prescription|http://ptl.sys.virginia.edu/@api/deki/files/261]
[buy tramadol cod|http://ptl.sys.virginia.edu/@api/deki/files/262]
[tramadol price|http://ptl.sys.virginia.edu/@api/deki/files/263]
[tramadol prescription from discount 
pharmacy|http://ptl.sys.virginia.edu/@api/deki/files/264]
[generic tramadol er dosage|http://ptl.sys.virginia.edu/@api/deki/files/265]
[tramadol next day|http://ptl.sys.virginia.edu/@api/deki/files/266]
[tramadol price|http://ptl.sys.virginia.edu/@api/deki/files/267]
[side effects of tramadol|http://ptl.sys.virginia.edu/@api/deki/files/268]
[tramadol hcl 50 mg tab mylan|http://ptl.sys.virginia.edu/@api/deki/files/269]
[tramadol 50mg|http://ptl.sys.virginia.edu/@api/deki/files/270]
[tramadol 50mg 180 pills|http://ptl.sys.virginia.edu/@api/deki/files/271]
[tramadol addiction properties|http://ptl.sys.virginia.edu/@api/deki/files/272]
[tramadol com|http://ptl.sys.virginia.edu/@api/deki/files/273]
[canine tramadol dosage|http://ptl.sys.virginia.edu/@api/deki/files/274]
[what is canine tramadol dose|http://ptl.sys.virginia.edu/@api/deki/files/275]
[drug reactions vicodin and 
tramadol|http://ptl.sys.virginia.edu/@api/deki/files/276]
[side effects of tramadol 
hydrochloride|http://ptl.sys.virginia.edu/@api/deki/files/277]
[tramadol sales|http://ptl.sys.virginia.edu/@api/deki/files/278]
[tramadol hcl 50 mg|http://ptl.sys.virginia.edu/@api/deki/files/279]
[tramadol hydrochloride|http://ptl.sys.virginia.edu/@api/deki/files/280]
[tramadol sale us no prescription 
required|http://ptl.sys.virginia.edu/@api/deki/files/281]
[tramadol hydrochloride 100mg|http://ptl.sys.virginia.edu/@api/deki/files/282]
[what is tramadol|http://ptl.sys.virginia.edu/@api/deki/files/283]
[tramadol 100 mg|http://ptl.sys.virginia.edu/@api/deki/files/284]
[buy tramadol with no 
prescription|http://ptl.sys.virginia.edu/@api/deki/files/285]
[buy cheap tramadol o|http://ptl.sys.virginia.edu/@api/deki/files/286]
[tramadol online|http://ptl.sys.virginia.edu/@api/deki/files/287]
[cod accepted tramadol order|http://ptl.sys.virginia.edu/@api/deki/files/288]
[buy tramadol cheap medication 
inurl|http://ptl.sys.virginia.edu/@api/deki/files/289]
[buy tramadol online overnight 
delivery|http://ptl.sys.virginia.edu/@api/deki/files/290]
[can i take tramadol pain pills if theyre a year 
old|http://ptl.sys.virginia.edu/@api/deki/files/291]
[canadian pharmacy that sells tramadol without a 
prescription|http://ptl.sys.virginia.edu/@api/deki/files/292]
[can i take tramadol pain pills if theyre a year 
old|http://ptl.sys.virginia.edu/@api/deki/files/293]
[best price tramadol|http://ptl.sys.virginia.edu/@api/deki/files/294]
[tramadol no prescription|http://ptl.sys.virginia.edu/@api/deki/files/295]
[tramadol hydrochloride|http://ptl.sys.virginia.edu/@api/deki/files/296]
[tramadol price|http://ptl.sys.virginia.edu/@api/deki/files/297]
[tramadol without a rx and 
prednisone|http://ptl.sys.virginia.edu/@api/deki/files/298]
[tramadol sales|http://ptl.sys.virginia.edu/@api/deki/files/299]
[tramadol tablets|http://ptl.sys.virginia.edu/@api/deki/files/300]
[tramadol hydrochloride use in 
dogs|http://ptl.sys.virginia.edu/@api/deki/files/301]
[tramadol withdrawals|http://ptl.sys.virginia.edu/@api/deki/files/302]
[tramadol hydrochloride|http://ptl.sys.virginia.edu/@api/deki/files/303]
[what is tramadol|http://ptl.sys.virginia.edu/@api/deki/files/304]
[ultram|http://ptl.sys.virginia.edu/@api/deki/files/305]


> Duplicate id exception for HtmlDataScrollerRenderer
> ---
>
> Key: TOMAHAWK-596
> URL: https://issues.apache.org/jira/browse/TOMAHAWK-596
> Project: MyFaces Tomahawk
>  Issue Type: Bug
>  Components: Data Scroller
>Affects Versions: 1.1.3
> Environment: Linux, Windows
>Reporter: Ryan Wynn
>Assignee: Leonardo Uribe
> Fix For: 1.1.9
>
> Attachments: datascroller-issue.txt, HtmlDataScrollerRenderer.java, 
> HtmlDataScrollerRenderer.java.example, HtmlDataScrollerRenderer.patch, 
> HtmlDataScrollerRenderer.patch, TOMAHAWK-596.patch
>
>
> In a portlet environment a non-faces request produces an exception when the 
> faces tree is rendered if the faces tree contains a DataScroller component.  
> The HtmlDataScroller renderer actually renders its children twice in this 
> case, once in the 

[jira] Commented: (TRINIDAD-1723) Trinidad 2: ClassCastEXception while running componentDemos.jspx

[Max Starets (JIRA)]

[ 
https://issues.apache.org/jira/browse/TRINIDAD-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834287#action_12834287
 ] 

Max Starets commented on TRINIDAD-1723:
---

The issue is that WLS is not loading faces-bean.properties from the impl jar, 
so we get a wrong FacesBean bean created for CorePanelPage.
Prior to Blake's change (revision 901411), we had only one 
faces-bean.properties in the impl jar. That worked fine in both Jetty and WLS. 
Since 901411, we have two faces-bean.properties files - one in the impl jar, 
and one in the api. 

FacesBeanFactory._initializeBeanTypes() calls  _getClassLoader().getResources( 
"META-INF/faces-bean.properties"); Jetty will return two URLs (one for 
faces-bean.properties in the api and one in impl), while WLS - only one (in the 
api).  The behavior of WLS seems wrong to me.

It looks like the faces-bean.properties is required for some unit tests in the 
API package. A temporary workaround for WLS would be to copy all entries from 
the impl's faces-bean.properties into the api's faces-bean.properties and 
building with tests disabled.

> Trinidad 2: ClassCastEXception while running componentDemos.jspx
> 
>
> Key: TRINIDAD-1723
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1723
> Project: MyFaces Trinidad
>  Issue Type: Bug
>  Components: Components
>Affects Versions: 2.0.0-alpha-2
>Reporter: Max Starets
>
> Grab the latest trinidad-2.0.x branch and try running componentDemos.jspx. 
> The following exception will be thrown:
> java.lang.ClassCastException: 
> org.apache.myfaces.trinidadinternal.uinode.UIComponentUINode cannot be cast 
> to org.apache.myfaces.trinidadinternal.uinode.UIXComponentUINode
>   at 
> org.apache.myfaces.trinidadinternal.uinode.UIXComponentUINode.__getAdapter(UIXComponentUINode.java:439)
>   at 
> org.apache.myfaces.trinidadinternal.uinode.UINodeRendererBase.encodeEnd(UINodeRendererBase.java:65)
>   at 
> org.apache.myfaces.trinidad.component.UIXComponentBase.encodeEnd(UIXComponentBase.java:852)
>   at 
> org.apache.myfaces.trinidad.render.RenderUtils.encodeRecursive(RenderUtils.java:70)
>   at 
> org.apache.myfaces.trinidad.render.CoreRenderer.encodeChild(CoreRenderer.java:509)
>   at 
> org.apache.myfaces.trinidad.render.CoreRenderer.encodeAllChildren(CoreRenderer.java:531)
>   at 
> org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.PanelPartialRootRenderer.renderContent(PanelPartialRootRenderer.java:70)
>   at 
> org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.BodyRenderer.renderContent(BodyRenderer.java:151)
>   at 
> org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.PanelPartialRootRenderer.encodeAll(PanelPartialRootRenderer.java:153)
>   at 
> org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.BodyRenderer.encodeAll(BodyRenderer.java:80)
>   at 
> org.apache.myfaces.trinidad.render.CoreRenderer.delegateRenderer(CoreRenderer.java:546)
>   at 
> org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.DocumentRenderer.encodeAll(DocumentRenderer.java:82)
> This does not seem to be JSF 2 specific, but I have not had time to try it on 
> the latest MAIN.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: AW: [VOTE] codi as a new myfaces extensions sub-project

[Jan-Kees van Andel]

+1

2010/2/16 Werner Punz :
> +1
>
> Mario Ivankovits schrieb:
>>
>> +1
>>
>>
>>
>> *Von:* gerhard.petra...@gmail.com [mailto:gerhard.petra...@gmail.com] *Im
>> Auftrag von *Gerhard Petracek
>> *Gesendet:* Dienstag, 16. Februar 2010 12:01
>> *An:* MyFaces Development
>> *Betreff:* [VOTE] codi as a new myfaces extensions sub-project
>>
>>
>> hi @ all,
>>
>>
>> we have collected a lot of possible features for ext-cdi/codi and we have
>> several people who are interested in working on it [1].
>>
>> so we should vote about the new module officially.
>>
>>
>>
>> ---
>>
>> [ ] +1 for: codi should become a myfaces extensions sub-project
>>
>> [ ] +0
>>
>> [ ] -1 for: codi shouldn't become a myfaces extensions sub-project
>>
>>
>> ---
>>
>>
>> the module should be hosted at [2].
>>
>> i think we have a clear winner for the name: MyFaces CODI
>>
>> (svn and jira will use (ext-)cdi to be consistent with the other extension
>> modules.)
>>
>>
>> regards,
>>
>> gerhard
>>
>>
>> [1] http://wiki.apache.org/myfaces/Extensions/CDI/DevDoc/Drafts
>>
>> [2] http://svn.apache.org/repos/asf/myfaces/extensions/cdi/
>>
>>
>> http://www.irian.at
>>
>> Your JSF powerhouse -
>> JSF Consulting, Development and
>> Courses in English and German
>>
>> Professional Support for Apache MyFaces
>>
>
>

[jira] Created: (EXTSCRIPT-65) add optional compile whitelist

[Werner Punz (JIRA)]

add optional compile whitelist
--

 Key: EXTSCRIPT-65
 URL: https://issues.apache.org/jira/browse/EXTSCRIPT-65
 Project: MyFaces Extensions Scripting
  Issue Type: Bug
Reporter: Werner Punz
Assignee: Werner Punz


a bigger integration into an existing system has shown that it makes sense to 
add compiler whitelists, to allow a pointing towards the full source directory 
but only include certain packages and their subpackages to the compile!


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (EXTSCRIPT-60) overall code cleanup and unification

[Werner Punz (JIRA)]

[ 
https://issues.apache.org/jira/browse/EXTSCRIPT-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834254#action_12834254
 ] 

Werner Punz commented on EXTSCRIPT-60:
--

resolving this one for now

> overall code cleanup and unification
> 
>
> Key: EXTSCRIPT-60
> URL: https://issues.apache.org/jira/browse/EXTSCRIPT-60
> Project: MyFaces Extensions Scripting
>  Issue Type: Improvement
>Reporter: Werner Punz
>Assignee: Werner Punz
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (EXTSCRIPT-60) overall code cleanup and unification

[Werner Punz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EXTSCRIPT-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Werner Punz resolved EXTSCRIPT-60.
--

Resolution: Fixed

> overall code cleanup and unification
> 
>
> Key: EXTSCRIPT-60
> URL: https://issues.apache.org/jira/browse/EXTSCRIPT-60
> Project: MyFaces Extensions Scripting
>  Issue Type: Improvement
>Reporter: Werner Punz
>Assignee: Werner Punz
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (MYFACES-2561) StackOverflowError if a composite component implementation uses another composite component

[Leonardo Uribe (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834248#action_12834248
 ] 

Leonardo Uribe commented on MYFACES-2561:
-

It is a know problem about the semantic of #{cc}. In this case it resolves to 
the closest composite component and in that case is the same one. See this two 
topics on jsr-314-open mailing list (specially the first one):

[jsr-314-open] #{cc} semantics
[jsr-314-open] cc.parent mystery

In http://wiki.jcp.org/wiki/index.php?page=JSF+2.0+Rev+A+Change+Log it appears 
like:

C034 Change  Modify table 5-10 to state that implicit object cc 
returns the current composite component, relative to the composite component 
markup page in which the expression appears 

I'm keeping an eye on this change (there is other related to cc.parent 
resolution). It could be good to know what ri does in this case.

It could be good to have a patch for this one.



> StackOverflowError if a composite component implementation uses another 
> composite component
> ---
>
> Key: MYFACES-2561
> URL: https://issues.apache.org/jira/browse/MYFACES-2561
> Project: MyFaces Core
>  Issue Type: Bug
>  Components: JSR-314
>Affects Versions: 2.0.0-beta-3
>Reporter: Jakob Korherr
>Assignee: Jakob Korherr
>
> If you use another composite component in your composite component's 
> implementation you will get a StackOverflowError.
> javax.faces.FacesException: java.lang.StackOverflowError
>   at 
> org.apache.myfaces.context.ExceptionHandlerImpl.wrap(ExceptionHandlerImpl.java:241)
>   at 
> org.apache.myfaces.context.ExceptionHandlerImpl.handle(ExceptionHandlerImpl.java:156)
>   at 
> org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:216)
>   at javax.faces.webapp.FacesServlet.service(FacesServlet.java:191)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>   at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>   at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>   at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
>   at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>   at 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>   at 
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
>   at 
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:849)
>   at 
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
>   at 
> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:454)
>   at java.lang.Thread.run(Thread.java:637)
> Caused by: java.lang.StackOverflowError
>   at java.util.ArrayList.toArray(ArrayList.java:306)
>   at java.util.logging.Logger.getHandlers(Logger.java:1200)
>   at 
> java.util.logging.LogManager$RootLogger.getHandlers(LogManager.java:1019)
>   at java.util.logging.Logger.log(Logger.java:454)
>   at java.util.logging.Logger.doLog(Logger.java:480)
>   at java.util.logging.Logger.logp(Logger.java:680)
>   at org.apache.juli.logging.DirectJDKLog.log(DirectJDKLog.java:167)
>   at org.apache.juli.logging.DirectJDKLog.error(DirectJDKLog.java:135)
>   at org.apache.catalina.connector.Request.setAttribute(Request.java:1448)
>   at 
> org.apache.catalina.connector.RequestFacade.setAttribute(RequestFacade.java:503)
>   at 
> org.apache.myfaces.context.servlet.RequestMap.setAttribute(RequestMap.java:53)
>   at 
> org.apache.myfaces.util.AbstractAttributeMap.put(AbstractAttributeMap.java:113)
>   at 
> org.apache.myfaces.util.AbstractAttributeMap.put(AbstractAttributeMap.java:1)
>   at 
> org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver.setScope(FacesCompositeELResolver.java:191)
>   at 
> org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:139)
>   at org.apache.el.parser.AstIdentifier.getValue(AstIdentifier.java:61)
>   at org.apache.el.parser.AstValue.getValue(AstValue.java:107)
>   at 
> org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186)
>   at 
> org.apache.myfaces.view.facelets.el.TagValueExpression.getValue(TagValueExpression.java:84)
>   at 
> org.apache.myfaces.el.unified.resolver.CompositeComponentELResolver$CompositeComponentAttributesMapWrapper.get(CompositeComponentELResolver.java:245)
>   at javax.el.M

[jira] Commented: (MYFACES-2561) StackOverflowError if a composite component implementation uses another composite component

[Jakob Korherr (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834227#action_12834227
 ] 

Jakob Korherr commented on MYFACES-2561:


To run into the StackOverflowError both composite components need to have the 
same attribute name and use this attribute in their implementation.

Example:
component test1:





test1



component test2:





test2
#{cc.attrs.test}


> StackOverflowError if a composite component implementation uses another 
> composite component
> ---
>
> Key: MYFACES-2561
> URL: https://issues.apache.org/jira/browse/MYFACES-2561
> Project: MyFaces Core
>  Issue Type: Bug
>  Components: JSR-314
>Affects Versions: 2.0.0-beta-3
>Reporter: Jakob Korherr
>Assignee: Jakob Korherr
>
> If you use another composite component in your composite component's 
> implementation you will get a StackOverflowError.
> javax.faces.FacesException: java.lang.StackOverflowError
>   at 
> org.apache.myfaces.context.ExceptionHandlerImpl.wrap(ExceptionHandlerImpl.java:241)
>   at 
> org.apache.myfaces.context.ExceptionHandlerImpl.handle(ExceptionHandlerImpl.java:156)
>   at 
> org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:216)
>   at javax.faces.webapp.FacesServlet.service(FacesServlet.java:191)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>   at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>   at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>   at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
>   at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>   at 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>   at 
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
>   at 
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:849)
>   at 
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
>   at 
> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:454)
>   at java.lang.Thread.run(Thread.java:637)
> Caused by: java.lang.StackOverflowError
>   at java.util.ArrayList.toArray(ArrayList.java:306)
>   at java.util.logging.Logger.getHandlers(Logger.java:1200)
>   at 
> java.util.logging.LogManager$RootLogger.getHandlers(LogManager.java:1019)
>   at java.util.logging.Logger.log(Logger.java:454)
>   at java.util.logging.Logger.doLog(Logger.java:480)
>   at java.util.logging.Logger.logp(Logger.java:680)
>   at org.apache.juli.logging.DirectJDKLog.log(DirectJDKLog.java:167)
>   at org.apache.juli.logging.DirectJDKLog.error(DirectJDKLog.java:135)
>   at org.apache.catalina.connector.Request.setAttribute(Request.java:1448)
>   at 
> org.apache.catalina.connector.RequestFacade.setAttribute(RequestFacade.java:503)
>   at 
> org.apache.myfaces.context.servlet.RequestMap.setAttribute(RequestMap.java:53)
>   at 
> org.apache.myfaces.util.AbstractAttributeMap.put(AbstractAttributeMap.java:113)
>   at 
> org.apache.myfaces.util.AbstractAttributeMap.put(AbstractAttributeMap.java:1)
>   at 
> org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver.setScope(FacesCompositeELResolver.java:191)
>   at 
> org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:139)
>   at org.apache.el.parser.AstIdentifier.getValue(AstIdentifier.java:61)
>   at org.apache.el.parser.AstValue.getValue(AstValue.java:107)
>   at 
> org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186)
>   at 
> org.apache.myfaces.view.facelets.el.TagValueExpression.getValue(TagValueExpression.java:84)
>   at 
> org.apache.myfaces.el.unified.resolver.CompositeComponentELResolver$CompositeComponentAttributesMapWrapper.get(CompositeComponentELResolver.java:245)
>   at javax.el.MapELResolver.getValue(MapELResolver.java:51)
>   at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:54)
>   at 
> org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:140)
>   at org.apache.el.parser.AstValue.getValue(AstValue.java:118)
>   at 
> org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186)
>   at 
> org.apache.myfaces.view.facelets.el.TagValueExpression.getValue(TagValueExpression.java:84)

[jira] Commented: (TOBAGO-811) Dublicate Id Excepiton with RI 1.1

[Udo Schnurpfeil (JIRA)]

[ 
https://issues.apache.org/jira/browse/TOBAGO-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834226#action_12834226
 ] 

Udo Schnurpfeil commented on TOBAGO-811:


There was also a fixed problem while restore in the JSF 1.2 variant.

> Dublicate Id Excepiton with RI 1.1
> --
>
> Key: TOBAGO-811
> URL: https://issues.apache.org/jira/browse/TOBAGO-811
> Project: MyFaces Tobago
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 1.5.0-alpha-1
> Environment: Sun RI 1.1_02
> Facelets 1.1.14
>Reporter: Udo Schnurpfeil
>Assignee: Udo Schnurpfeil
> Fix For: 1.0.25, 1.5.0-alpha-2, 1.5.0
>
>
> When using e.g. some tc:cell in a page, there will be an dublicate id 
> exception thrown.
> The problem is, that the id counter in UIViewRoot will be resetted in the 
> method "encodeBegin".
> The automatically generated LayoutManager components are created while 
> encoding, and so they are getting ids counted up from 0.
> The solution is 
>   - override the createUniqueId in case of JSF 1.1 and
>   - create the dynamic components before the encoding phase

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (TOBAGO-850) tx components will be created new when rerendering in JSF 1.2 and using JSP

[Udo Schnurpfeil (JIRA)]

tx components will be created new when rerendering in JSF 1.2 and using JSP
---

 Key: TOBAGO-850
 URL: https://issues.apache.org/jira/browse/TOBAGO-850
 Project: MyFaces Tobago
  Issue Type: Bug
  Components: Core
 Environment: MyFaces 1.2
JSP
Reporter: Udo Schnurpfeil
Assignee: Udo Schnurpfeil


The tx-Tags should support the JspIdConsumer class which is new in JSP 2.1.
The problem is, that the findComponent method of UIComponentClassicTagBase will 
not identify the component and create a new one.
Result: the submitted value will not be shown in case of an error. Also 
FacesMessages uses ids which are not on the page (because they a created new).


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (MYFACES-2561) StackOverflowError if a composite component implementation uses another composite component

[Jakob Korherr (JIRA)]

StackOverflowError if a composite component implementation uses another 
composite component
---

 Key: MYFACES-2561
 URL: https://issues.apache.org/jira/browse/MYFACES-2561
 Project: MyFaces Core
  Issue Type: Bug
  Components: JSR-314
Affects Versions: 2.0.0-beta-3
Reporter: Jakob Korherr
Assignee: Jakob Korherr


If you use another composite component in your composite component's 
implementation you will get a StackOverflowError.

javax.faces.FacesException: java.lang.StackOverflowError
at 
org.apache.myfaces.context.ExceptionHandlerImpl.wrap(ExceptionHandlerImpl.java:241)
at 
org.apache.myfaces.context.ExceptionHandlerImpl.handle(ExceptionHandlerImpl.java:156)
at 
org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:216)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:191)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:849)
at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at 
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:454)
at java.lang.Thread.run(Thread.java:637)
Caused by: java.lang.StackOverflowError
at java.util.ArrayList.toArray(ArrayList.java:306)
at java.util.logging.Logger.getHandlers(Logger.java:1200)
at 
java.util.logging.LogManager$RootLogger.getHandlers(LogManager.java:1019)
at java.util.logging.Logger.log(Logger.java:454)
at java.util.logging.Logger.doLog(Logger.java:480)
at java.util.logging.Logger.logp(Logger.java:680)
at org.apache.juli.logging.DirectJDKLog.log(DirectJDKLog.java:167)
at org.apache.juli.logging.DirectJDKLog.error(DirectJDKLog.java:135)
at org.apache.catalina.connector.Request.setAttribute(Request.java:1448)
at 
org.apache.catalina.connector.RequestFacade.setAttribute(RequestFacade.java:503)
at 
org.apache.myfaces.context.servlet.RequestMap.setAttribute(RequestMap.java:53)
at 
org.apache.myfaces.util.AbstractAttributeMap.put(AbstractAttributeMap.java:113)
at 
org.apache.myfaces.util.AbstractAttributeMap.put(AbstractAttributeMap.java:1)
at 
org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver.setScope(FacesCompositeELResolver.java:191)
at 
org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:139)
at org.apache.el.parser.AstIdentifier.getValue(AstIdentifier.java:61)
at org.apache.el.parser.AstValue.getValue(AstValue.java:107)
at 
org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186)
at 
org.apache.myfaces.view.facelets.el.TagValueExpression.getValue(TagValueExpression.java:84)
at 
org.apache.myfaces.el.unified.resolver.CompositeComponentELResolver$CompositeComponentAttributesMapWrapper.get(CompositeComponentELResolver.java:245)
at javax.el.MapELResolver.getValue(MapELResolver.java:51)
at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:54)
at 
org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:140)
at org.apache.el.parser.AstValue.getValue(AstValue.java:118)
at 
org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186)
at 
org.apache.myfaces.view.facelets.el.TagValueExpression.getValue(TagValueExpression.java:84)
at 
org.apache.myfaces.el.unified.resolver.CompositeComponentELResolver$CompositeComponentAttributesMapWrapper.get(CompositeComponentELResolver.java:245)
at javax.el.MapELResolver.getValue(MapELResolver.java:51)
at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:54)
at 
org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:140)
at org.apache.el.parser.AstValue.getValue(AstValue.java:118)
at 
org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186)
at 
or

[jira] Updated: (MYFACES-2560) Known class name for EL RI's ExpressionFactoryImpl is wrong

[Ali Ok (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYFACES-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ali Ok updated MYFACES-2560:


Status: Patch Available  (was: Open)

> Known class name for EL RI's ExpressionFactoryImpl is wrong
> ---
>
> Key: MYFACES-2560
> URL: https://issues.apache.org/jira/browse/MYFACES-2560
> Project: MyFaces Core
>  Issue Type: Bug
>  Components: JSR-314
>Affects Versions: 2.0.0-alpha, 2.0.0-beta
> Environment: JSP 2.0 Environment, like Google App Engine
>Reporter: Ali Ok
>
> On Jsp2.0 environment using Myfaces 2.0 beta, users should provide the
> ExpressionFactory implementation.
> And if Jasper EL Impl or Sun's RI is available on the classpath, they are
> automatically set.
> However, impl class name of RI may be wrong.
> Until revision 761982, it was "com.sun.el.ExpressionFactoryImpl", which is
> correct class name.
> Then it became "com.sun.facelets.el.ExpressionFactoryImpl", that I couldn't
> find anywhere (spec, facelets.dev.java.net, etc. )
> Is this change correct?
> You can see the code on Jsp20FacesInitializer#EL_RI_EXPRESSION_FACTORY_IMPL.
> It is still "com.sun.el.ExpressionFactoryImpl" on Myfaces 1.2.8.
> It is not big deal, I can override it with a context parameter; but running
> Myfaces out-of-the-box is important :)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (MYFACES-2560) Known class name for EL RI's ExpressionFactoryImpl is wrong

[Ali Ok (JIRA)]

Known class name for EL RI's ExpressionFactoryImpl is wrong
---

 Key: MYFACES-2560
 URL: https://issues.apache.org/jira/browse/MYFACES-2560
 Project: MyFaces Core
  Issue Type: Bug
  Components: JSR-314
Affects Versions: 2.0.0-beta, 2.0.0-alpha
 Environment: JSP 2.0 Environment, like Google App Engine
Reporter: Ali Ok


On Jsp2.0 environment using Myfaces 2.0 beta, users should provide the
ExpressionFactory implementation.
And if Jasper EL Impl or Sun's RI is available on the classpath, they are
automatically set.
However, impl class name of RI may be wrong.
Until revision 761982, it was "com.sun.el.ExpressionFactoryImpl", which is
correct class name.
Then it became "com.sun.facelets.el.ExpressionFactoryImpl", that I couldn't
find anywhere (spec, facelets.dev.java.net, etc. )

Is this change correct?

You can see the code on Jsp20FacesInitializer#EL_RI_EXPRESSION_FACTORY_IMPL.

It is still "com.sun.el.ExpressionFactoryImpl" on Myfaces 1.2.8.

It is not big deal, I can override it with a context parameter; but running
Myfaces out-of-the-box is important :)


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[ANN] Release of Apache MyFaces Trinidad's Maven plugins (2.0.1)

[Matthias Wessendorf]

Hi,

The Apache MyFaces community is pleased to announce its
2.0.1 release of the Apache MyFaces Trinidad Maven2 plugins.

This release contains support for the new JSF 2.0 related API/metadata.

These Maven2 plugins have been deployed to the Apache Maven2 repository and they
should be mirrored by ibiblio as well (very soon).

release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310661&styleName=Html&version=12314512

-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

[ANN] Release of Apache MyFaces Trinidad's Maven plugins (1.2.12)

[Matthias Wessendorf]

Hi,

The Apache MyFaces community is pleased to announce its
1.2.12 release of the Apache MyFaces Trinidad Maven2 plugins.

These Maven2 plugins have been deployed to the Apache Maven2 repository.
They are mirrored by ibiblio as well.

release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310661&styleName=Html&version=12314452

-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

Re: AW: [VOTE] codi as a new myfaces extensions sub-project

[Werner Punz]

+1

Mario Ivankovits schrieb:

+1

 

 

*Von:* gerhard.petra...@gmail.com [mailto:gerhard.petra...@gmail.com] 
*Im Auftrag von *Gerhard Petracek

*Gesendet:* Dienstag, 16. Februar 2010 12:01
*An:* MyFaces Development
*Betreff:* [VOTE] codi as a new myfaces extensions sub-project

 


hi @ all,

 

we have collected a lot of possible features for ext-cdi/codi and we 
have several people who are interested in working on it [1].


so we should vote about the new module officially.

 


---

[ ] +1 for: codi should become a myfaces extensions sub-project

[ ] +0

[ ] -1 for: codi shouldn't become a myfaces extensions sub-project

---

 


the module should be hosted at [2].

i think we have a clear winner for the name: MyFaces CODI

(svn and jira will use (ext-)cdi to be consistent with the other 
extension modules.)


 


regards,

gerhard

 


[1] http://wiki.apache.org/myfaces/Extensions/CDI/DevDoc/Drafts

[2] http://svn.apache.org/repos/asf/myfaces/extensions/cdi/

 


http://www.irian.at

Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German

Professional Support for Apache MyFaces

[jira] Commented: (MYFACES-2504) Google App Engine Support

[Ali Ok (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834214#action_12834214
 ] 

Ali Ok commented on MYFACES-2504:
-

Hi,
I created the a new issue for Myfaces2 since some different stuff should be 
made (see MYFACES-2559).
Matthias,
Since ExternalContextUtils that you put is under Myfaces Shared 4.x.x, and 
Myfaces 1.2 uses a different version, I couldn't use the util.
Do you plan changing it?
If not, there is no more change on this issue based on your comments.

I wrote a tutorial article about Myfaces on GAE, but since I cannot say users 
to "apply patch for MYFACES-2504", I am saving the article to myself :)
Once the code goes into trunk and a snapshot is released, I will share it with 
the world.

> Google App Engine Support
> -
>
> Key: MYFACES-2504
> URL: https://issues.apache.org/jira/browse/MYFACES-2504
> Project: MyFaces Core
>  Issue Type: Improvement
>  Components: JSR-252, JSR-314
>Affects Versions: 1.2.8, 2.0.0-alpha
> Environment: Google App Engine 1.3
>Reporter: Ali Ok
>Priority: Minor
> Attachments: 2504-5.diff, 2504-doc.diff
>
>
> Support for Google App Engine for MyFaces 1.2 and 2.0.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (MYFACES-2559) Google App Engine Support for Myfaces 2

[Ali Ok (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYFACES-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ali Ok updated MYFACES-2559:


Status: Patch Available  (was: Open)

> Google App Engine Support for Myfaces 2
> ---
>
> Key: MYFACES-2559
> URL: https://issues.apache.org/jira/browse/MYFACES-2559
> Project: MyFaces Core
>  Issue Type: Improvement
>  Components: JSR-314
>Affects Versions: 2.0.0-beta
> Environment: Google App Engine
>Reporter: Ali Ok
>Priority: Minor
> Attachments: 2559.patch
>
>
> Google App Engine Support for Myfaces 2

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (MYFACES-2559) Google App Engine Support for Myfaces 2

[Ali Ok (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834209#action_12834209
 ] 

Ali Ok commented on MYFACES-2559:
-

I created a new ticket for Myfaces2 since there are some differences between 
Myfaces2 and Myfaces 1.2.
You can see the ticket for Google App Engine Support Myfaces 1.2 on:
https://issues.apache.org/jira/browse/MYFACES-2504

> Google App Engine Support for Myfaces 2
> ---
>
> Key: MYFACES-2559
> URL: https://issues.apache.org/jira/browse/MYFACES-2559
> Project: MyFaces Core
>  Issue Type: Improvement
>  Components: JSR-314
>Affects Versions: 2.0.0-beta
> Environment: Google App Engine
>Reporter: Ali Ok
>Priority: Minor
> Attachments: 2559.patch
>
>
> Google App Engine Support for Myfaces 2

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (MYFACES-2559) Google App Engine Support for Myfaces 2

[Ali Ok (JIRA)]

Google App Engine Support for Myfaces 2
---

 Key: MYFACES-2559
 URL: https://issues.apache.org/jira/browse/MYFACES-2559
 Project: MyFaces Core
  Issue Type: Improvement
  Components: JSR-314
Affects Versions: 2.0.0-beta
 Environment: Google App Engine
Reporter: Ali Ok
Priority: Minor


Google App Engine Support for Myfaces 2

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [Vote] Trinidad plugins 1.2.12 release

[Matthias Wessendorf]

Thx for voting.

We got 4 votes, all +1:
-Matthias Wessendorf
-Max Starets
-Leo Uribe
-Gabrielle Crawford

I will run the final steps to get this release out

-Matthias

On Thu, Feb 11, 2010 at 11:30 PM, Gabrielle Crawford
 wrote:
> +1
>
> Matthias Wessendorf wrote:
>>
>> Hi,
>>
>> I was running the needed tasks to get the 1.2.12 release of the Apache
>> MyFaces Trinidad Maven 2 Plugins.
>>
>> The artifacts are deployed to my private Apache account ([1]).
>>
>> Please take a look at the "1.2.12" artifacts and vote.
>>
>> How to test those JARs ?
>>
>> Use the stage repo inside your pom.xml file:
>> ...
>> 
>> 
>> apache.stage
>> Apache Stage Repository
>> http://people.apache.org/~matzew/staging_repo/
>> default
>> 
>> 
>> ...
>>
>> 
>> [ ] +1 for community members who have reviewed and tested the bits
>> [ ] +0
>> [ ] -1 for fatal flaws that should cause these bits not to be released,
>> and why..
>> 
>>
>> Thanks,
>> Matthias
>>
>> [1] http://people.apache.org/~matzew/staging_repo/
>>
>>
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

Result - Re: [VOTE] Release of Trinidad 1.0.12

[Matthias Wessendorf]

Thx for voting.

We got 3 votes, all +1:
-Matthias Wessendorf
-Max Starets
-Gerhard Petracek

I will run the final steps to get this release out

-Matthias

On Fri, Feb 12, 2010 at 3:19 PM, Gerhard Petracek
 wrote:
> +1
> regards,
> gerhard
>
> http://www.irian.at
>
> Your JSF powerhouse -
> JSF Consulting, Development and
> Courses in English and German
>
> Professional Support for Apache MyFaces
>
>
> 2010/2/11 Matthias Wessendorf 
>>
>> +1
>>
>> On Thu, Feb 11, 2010 at 10:28 PM, Matthias Wessendorf 
>> wrote:
>> > Hi,
>> >
>> > I was running the needed tasks to get the 1.0.12 release of the Apache
>> > MyFaces Trinidad CORE out. The artifacts are deployed to my private
>> > Apache account ([1]). The distribution is located at [2].
>> >
>> > Please take a look at the "1.0.12" artifacts and vote
>> >
>> > 
>> > [ ] +1 for community members who have reviewed the bits
>> > [ ] +0
>> > [ ] -1 for fatal flaws that should cause these bits not to be released,
>> >  and why..
>> > 
>> >
>> > Thanks,
>> > Matthias
>> >
>> > [1] http://people.apache.org/~matzew/staging_repo/
>> > [2] http://people.apache.org/~matzew/trinidad-1.0.12_dist/
>> >
>> > --
>> > Matthias Wessendorf
>> >
>> > blog: http://matthiaswessendorf.wordpress.com/
>> > sessions: http://www.slideshare.net/mwessendorf
>> > twitter: http://twitter.com/mwessendorf
>> >
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

Re: [Vote] Trinidad plugins 2.0.1 release

[Matthias Wessendorf]

Thx for voting.

We got 3 votes, all +1:
-Matthias Wessendorf
-Max Starets
-Gerhard Petracek

I will run the final steps to get this release out

-Matthias

On Fri, Feb 12, 2010 at 3:38 PM, Gerhard Petracek
 wrote:
> +1
> regards,
> gerhard
>
> http://www.irian.at
>
> Your JSF powerhouse -
> JSF Consulting, Development and
> Courses in English and German
>
> Professional Support for Apache MyFaces
>
>
> 2010/2/12 Max Starets 
>>
>> +1.
>>
>>
>> Matthias Wessendorf wrote:
>>>
>>> Hi,
>>>
>>> I was running the needed tasks to get the 2.0.1 release of the Apache
>>> MyFaces Trinidad Maven 2 Plugins. This contains more JSF 2.0
>>> support for the MyFaces Trinidad Maven plugins.
>>>
>>> yes, it contains this fix:
>>> https://issues.apache.org/jira/browse/TRINIDAD-1681
>>>
>>> The artifacts are deployed to my private Apache account ([1]).
>>>
>>> Please take a look at the "2.0.1" artifacts and vote.
>>>
>>> How to test those JARs ?
>>>
>>> Use the stage repo inside your pom.xml file:
>>> ...
>>> 
>>> 
>>> apache.stage
>>> Apache Stage Repository
>>> http://people.apache.org/~matzew/staging_repo/
>>> default
>>> 
>>> 
>>> ...
>>>
>>> 
>>> [ ] +1 for community members who have reviewed and tested the bits
>>> [ ] +0
>>> [ ] -1 for fatal flaws that should cause these bits not to be released,
>>> and why..
>>> 
>>>
>>> Thanks,
>>> Matthias
>>>
>>> [1] http://people.apache.org/~matzew/staging_repo/
>>>
>>>
>>
>
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

RESULT - Re: [VOTE] Release of Trinidad 2.0.0-alpha2

[Matthias Wessendorf]

Thx for voting.

We got 4 votes, all +1:
-Matthias Wessendorf
-Max Starets
-Gerhard Petracek
-Gabrielle Crawford

I will run the final steps to get this release out

-Matthias

On Fri, Feb 12, 2010 at 7:35 PM, Gabrielle Crawford
 wrote:
> +1
>
> Gerhard Petracek wrote:
>>
>> +1
>>
>> regards,
>> gerhard
>>
>> http://www.irian.at
>>
>> Your JSF powerhouse -
>> JSF Consulting, Development and
>> Courses in English and German
>>
>> Professional Support for Apache MyFaces
>>
>>
>> 2010/2/12 Matthias Wessendorf > >
>>
>>    +1
>>
>>    On Fri, Feb 12, 2010 at 3:15 PM, Matthias Wessendorf
>>    mailto:mat...@apache.org>> wrote:
>>    > Hi,
>>    >
>>    > I was running the needed tasks to get the second alpha release
>>    of the Apache
>>    > MyFaces Trinidad 2.x CORE out. The artifacts are deployed to my
>>    private
>>    > Apache account ([1]). The distribution is located at [2].
>>    >
>>    > Please take a look at the "2.0.0-alpha2" artifacts and vote
>>    >
>>    > 
>>    > [ ] +1 for community members who have reviewed the bits
>>    > [ ] +0
>>    > [ ] -1 for fatal flaws that should cause these bits not to be
>>    released,
>>    >  and why..
>>    > 
>>    >
>>    > Thanks,
>>    > Matthias
>>    >
>>    > [1] http://people.apache.org/~matzew/staging_repo/
>>    
>>    > [2] http://people.apache.org/~matzew/trinidad-2.0.0-alpha2_dist/
>>    
>>    >
>>    > --
>>    > Matthias Wessendorf
>>    >
>>    > blog: http://matthiaswessendorf.wordpress.com/
>>    > sessions: http://www.slideshare.net/mwessendorf
>>    > twitter: http://twitter.com/mwessendorf
>>    >
>>
>>
>>
>>    --
>>    Matthias Wessendorf
>>
>>    blog: http://matthiaswessendorf.wordpress.com/
>>    sessions: http://www.slideshare.net/mwessendorf
>>    twitter: http://twitter.com/mwessendorf
>>
>>
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

[jira] Commented: (TRINIDAD-1724) Generated Facelets taglib.xml files don't validate against schema

[JIRA]

[ 
https://issues.apache.org/jira/browse/TRINIDAD-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834182#action_12834182
 ] 

Matthias Weßendorf commented on TRINIDAD-1724:
--

but as said on mailing list, this one is also not "complete".

> Generated Facelets taglib.xml files don't validate against schema
> -
>
> Key: TRINIDAD-1724
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1724
> Project: MyFaces Trinidad
>  Issue Type: Bug
>  Components: Plugins
>Affects Versions:  2.0.2-plugins 
>Reporter: Catalin Kormos
>
> At least the tr.taglib.xml I just checked and it contains a lot of 
> < elements, for example:
>
>   
> an EL binding to the method that will deliver the file contents.  The 
> method must take two parameters, a FacesContext and an OutputStream.
>   
>   method
>   true
>   void myMethod(javax.faces.context.FacesContext, 
> java.io.OutputStream)
> 
> Checking the schema  is not allowed in 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [VOTE] codi as a new myfaces extensions sub-project

[Jakob Korherr]

+1

Regards,
Jakob

2010/2/16 Hazem Saleh 

> +1 for sure.
>
>
> On Tue, Feb 16, 2010 at 1:41 PM, Gerhard Petracek <
> gerhard.petra...@gmail.com> wrote:
>
>> hi mark,
>>
>> we should be consistent with the other modules...
>> however, if you have an important reason to handle it differently, we can
>> discuss it again after the vote.
>>
>> regards,
>> gerhard
>>
>>
>> http://www.irian.at
>>
>> Your JSF powerhouse -
>> JSF Consulting, Development and
>> Courses in English and German
>>
>> Professional Support for Apache MyFaces
>>
>>
>> 2010/2/16 Mark Struberg 
>>
>> +1
>>>
>>>
>>> but maybe we can move svn and Jira to "ext-codi" instead of ext-cdi?
>>>
>>> Btw, the Context for @ViewScoped is already available in my github repo
>>> too.
>>>
>>> LieGrue,
>>> strub
>>>
>>> --- Gerhard Petracek  schrieb am Di, 16.2.2010:
>>>
>>> > Von: Gerhard Petracek 
>>> > Betreff: [VOTE] codi as a new myfaces extensions sub-project
>>> > An: "MyFaces Development" 
>>> > Datum: Dienstag, 16. Februar, 2010 12:00 Uhr
>>> > hi @ all,
>>> > we have collected a lot of possible features for
>>> > ext-cdi/codi and we have several people who are interested
>>> > in working on it [1].so we should vote about the
>>> > new module officially.
>>> >
>>> >
>>> >
>>> ---[
>>> > ] +1 for: codi should become a myfaces extensions
>>> > sub-project[ ] +0
>>> >
>>> > [ ] -1 for: codi shouldn't become a myfaces
>>> > extensions
>>> >
>>> sub-project---
>>> >
>>> >
>>> > the module should be hosted at
>>> > [2].i think we have a clear winner for the name:
>>> > MyFaces CODI(svn and jira will use (ext-)cdi to
>>> > be consistent with the other extension modules.)
>>> >
>>> >
>>> > regards,gerhard
>>> > [1] http://wiki.apache.org/myfaces/Extensions/CDI/DevDoc/Drafts
>>> > [2] http://svn.apache.org/repos/asf/myfaces/extensions/cdi/
>>> >
>>> > http://www.irian.at
>>> >
>>> > Your JSF powerhouse -
>>> > JSF Consulting, Development and
>>> > Courses in English and German
>>> >
>>> > Professional Support for Apache MyFaces
>>> >
>>> >
>>> >
>>> >
>>> >
>>>
>>> __
>>> Do You Yahoo!?
>>> Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz
>>> gegen Massenmails.
>>> http://mail.yahoo.com
>>>
>>
>>
>
>
> --
> Hazem Ahmed Saleh Ahmed
>
> Author of (The Definitive Guide to Apache MyFaces and Facelets):
>
> http://www.amazon.com/Definitive-Guide-Apache-MyFaces-Facelets/dp/1590597370
> http://www.amazon.com/-/e/B002M052KY
>
> Web blog: http://www.jroller.com/page/HazemBlog
>
> [Web 2.0] Google Maps Integration with JSF:
> http://code.google.com/p/gmaps4jsf/
> http://www.ibm.com/developerworks/library/wa-aj-gmaps/
>

Re: [VOTE] codi as a new myfaces extensions sub-project

[Hazem Saleh]

+1 for sure.

On Tue, Feb 16, 2010 at 1:41 PM, Gerhard Petracek <
gerhard.petra...@gmail.com> wrote:

> hi mark,
>
> we should be consistent with the other modules...
> however, if you have an important reason to handle it differently, we can
> discuss it again after the vote.
>
> regards,
> gerhard
>
>
> http://www.irian.at
>
> Your JSF powerhouse -
> JSF Consulting, Development and
> Courses in English and German
>
> Professional Support for Apache MyFaces
>
>
> 2010/2/16 Mark Struberg 
>
> +1
>>
>>
>> but maybe we can move svn and Jira to "ext-codi" instead of ext-cdi?
>>
>> Btw, the Context for @ViewScoped is already available in my github repo
>> too.
>>
>> LieGrue,
>> strub
>>
>> --- Gerhard Petracek  schrieb am Di, 16.2.2010:
>>
>> > Von: Gerhard Petracek 
>> > Betreff: [VOTE] codi as a new myfaces extensions sub-project
>> > An: "MyFaces Development" 
>> > Datum: Dienstag, 16. Februar, 2010 12:00 Uhr
>> > hi @ all,
>> > we have collected a lot of possible features for
>> > ext-cdi/codi and we have several people who are interested
>> > in working on it [1].so we should vote about the
>> > new module officially.
>> >
>> >
>> >
>> ---[
>> > ] +1 for: codi should become a myfaces extensions
>> > sub-project[ ] +0
>> >
>> > [ ] -1 for: codi shouldn't become a myfaces
>> > extensions
>> >
>> sub-project---
>> >
>> >
>> > the module should be hosted at
>> > [2].i think we have a clear winner for the name:
>> > MyFaces CODI(svn and jira will use (ext-)cdi to
>> > be consistent with the other extension modules.)
>> >
>> >
>> > regards,gerhard
>> > [1] http://wiki.apache.org/myfaces/Extensions/CDI/DevDoc/Drafts
>> > [2] http://svn.apache.org/repos/asf/myfaces/extensions/cdi/
>> >
>> > http://www.irian.at
>> >
>> > Your JSF powerhouse -
>> > JSF Consulting, Development and
>> > Courses in English and German
>> >
>> > Professional Support for Apache MyFaces
>> >
>> >
>> >
>> >
>> >
>>
>> __
>> Do You Yahoo!?
>> Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz
>> gegen Massenmails.
>> http://mail.yahoo.com
>>
>
>


-- 
Hazem Ahmed Saleh Ahmed

Author of (The Definitive Guide to Apache MyFaces and Facelets):
http://www.amazon.com/Definitive-Guide-Apache-MyFaces-Facelets/dp/1590597370
http://www.amazon.com/-/e/B002M052KY

Web blog: http://www.jroller.com/page/HazemBlog

[Web 2.0] Google Maps Integration with JSF:
http://code.google.com/p/gmaps4jsf/
http://www.ibm.com/developerworks/library/wa-aj-gmaps/

Re: [VOTE] codi as a new myfaces extensions sub-project

[Gerhard Petracek]

hi mark,

we should be consistent with the other modules...
however, if you have an important reason to handle it differently, we can
discuss it again after the vote.

regards,
gerhard

http://www.irian.at

Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German

Professional Support for Apache MyFaces


2010/2/16 Mark Struberg 

> +1
>
>
> but maybe we can move svn and Jira to "ext-codi" instead of ext-cdi?
>
> Btw, the Context for @ViewScoped is already available in my github repo
> too.
>
> LieGrue,
> strub
>
> --- Gerhard Petracek  schrieb am Di, 16.2.2010:
>
> > Von: Gerhard Petracek 
> > Betreff: [VOTE] codi as a new myfaces extensions sub-project
> > An: "MyFaces Development" 
> > Datum: Dienstag, 16. Februar, 2010 12:00 Uhr
> > hi @ all,
> > we have collected a lot of possible features for
> > ext-cdi/codi and we have several people who are interested
> > in working on it [1].so we should vote about the
> > new module officially.
> >
> >
> >
> ---[
> > ] +1 for: codi should become a myfaces extensions
> > sub-project[ ] +0
> >
> > [ ] -1 for: codi shouldn't become a myfaces
> > extensions
> >
> sub-project---
> >
> >
> > the module should be hosted at
> > [2].i think we have a clear winner for the name:
> > MyFaces CODI(svn and jira will use (ext-)cdi to
> > be consistent with the other extension modules.)
> >
> >
> > regards,gerhard
> > [1] http://wiki.apache.org/myfaces/Extensions/CDI/DevDoc/Drafts
> > [2] http://svn.apache.org/repos/asf/myfaces/extensions/cdi/
> >
> > http://www.irian.at
> >
> > Your JSF powerhouse -
> > JSF Consulting, Development and
> > Courses in English and German
> >
> > Professional Support for Apache MyFaces
> >
> >
> >
> >
> >
>
> __
> Do You Yahoo!?
> Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz
> gegen Massenmails.
> http://mail.yahoo.com
>

[jira] Issue Comment Edited: (TRINIDAD-1724) Generated Facelets taglib.xml files don't validate against schema

[Bernd Bohmann (JIRA)]

[ 
https://issues.apache.org/jira/browse/TRINIDAD-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834164#action_12834164
 ] 

Bernd Bohmann edited comment on TRINIDAD-1724 at 2/16/10 11:27 AM:
---

I think we should use a local version of the xsd or the xsd from 
myfaces-2.0.x/impl/src/main/resources/org/apache/myfaces/resource/web-facelettaglibrary_2_0.xsd
 to support offline build.

  was (Author: bommel):
I think we use a local version of the xsd or the xsd from 
myfaces-2.0.x/impl/src/main/resources/org/apache/myfaces/resource/web-facelettaglibrary_2_0.xsd
 to support offline build.
  
> Generated Facelets taglib.xml files don't validate against schema
> -
>
> Key: TRINIDAD-1724
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1724
> Project: MyFaces Trinidad
>  Issue Type: Bug
>  Components: Plugins
>Affects Versions:  2.0.2-plugins 
>Reporter: Catalin Kormos
>
> At least the tr.taglib.xml I just checked and it contains a lot of 
> < elements, for example:
>
>   
> an EL binding to the method that will deliver the file contents.  The 
> method must take two parameters, a FacesContext and an OutputStream.
>   
>   method
>   true
>   void myMethod(javax.faces.context.FacesContext, 
> java.io.OutputStream)
> 
> Checking the schema  is not allowed in 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (TRINIDAD-1724) Generated Facelets taglib.xml files don't validate against schema

[Bernd Bohmann (JIRA)]

[ 
https://issues.apache.org/jira/browse/TRINIDAD-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834164#action_12834164
 ] 

Bernd Bohmann commented on TRINIDAD-1724:
-

I think we use a local version of the xsd or the xsd from 
myfaces-2.0.x/impl/src/main/resources/org/apache/myfaces/resource/web-facelettaglibrary_2_0.xsd
 to support offline build.

> Generated Facelets taglib.xml files don't validate against schema
> -
>
> Key: TRINIDAD-1724
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1724
> Project: MyFaces Trinidad
>  Issue Type: Bug
>  Components: Plugins
>Affects Versions:  2.0.2-plugins 
>Reporter: Catalin Kormos
>
> At least the tr.taglib.xml I just checked and it contains a lot of 
> < elements, for example:
>
>   
> an EL binding to the method that will deliver the file contents.  The 
> method must take two parameters, a FacesContext and an OutputStream.
>   
>   method
>   true
>   void myMethod(javax.faces.context.FacesContext, 
> java.io.OutputStream)
> 
> Checking the schema  is not allowed in 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

AW: [VOTE] codi as a new myfaces extensions sub-project

[Mario Ivankovits]

+1

 

 

Von: gerhard.petra...@gmail.com [mailto:gerhard.petra...@gmail.com] Im
Auftrag von Gerhard Petracek
Gesendet: Dienstag, 16. Februar 2010 12:01
An: MyFaces Development
Betreff: [VOTE] codi as a new myfaces extensions sub-project

 

hi @ all,

 

we have collected a lot of possible features for ext-cdi/codi and we have
several people who are interested in working on it [1].

so we should vote about the new module officially.

 


---

[ ] +1 for: codi should become a myfaces extensions sub-project

[ ] +0

[ ] -1 for: codi shouldn't become a myfaces extensions sub-project


---

 

the module should be hosted at [2].

i think we have a clear winner for the name: MyFaces CODI

(svn and jira will use (ext-)cdi to be consistent with the other extension
modules.)

 

regards,

gerhard

 

[1] http://wiki.apache.org/myfaces/Extensions/CDI/DevDoc/Drafts

[2] http://svn.apache.org/repos/asf/myfaces/extensions/cdi/

 

http://www.irian.at

Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German

Professional Support for Apache MyFaces



smime.p7s
Description: S/MIME cryptographic signature

AW: [VOTE] codi as a new myfaces extensions sub-project

[Mark Struberg]

+1


but maybe we can move svn and Jira to "ext-codi" instead of ext-cdi?

Btw, the Context for @ViewScoped is already available in my github repo too.

LieGrue,
strub

--- Gerhard Petracek  schrieb am Di, 16.2.2010:

> Von: Gerhard Petracek 
> Betreff: [VOTE] codi as a new myfaces extensions sub-project
> An: "MyFaces Development" 
> Datum: Dienstag, 16. Februar, 2010 12:00 Uhr
> hi @ all,
> we have collected a lot of possible features for
> ext-cdi/codi and we have several people who are interested
> in working on it [1].so we should vote about the
> new module officially.
> 
> 
> ---[
> ] +1 for: codi should become a myfaces extensions
> sub-project[ ] +0
> 
> [ ] -1 for: codi shouldn't become a myfaces
> extensions
> sub-project---
> 
> 
> the module should be hosted at
> [2].i think we have a clear winner for the name:
> MyFaces CODI(svn and jira will use (ext-)cdi to
> be consistent with the other extension modules.)
> 
> 
> regards,gerhard
> [1] http://wiki.apache.org/myfaces/Extensions/CDI/DevDoc/Drafts
> [2] http://svn.apache.org/repos/asf/myfaces/extensions/cdi/
> 
> http://www.irian.at
> 
> Your JSF powerhouse -
> JSF Consulting, Development and
> Courses in English and German
> 
> Professional Support for Apache MyFaces
> 
> 
> 
> 
> 

__
Do You Yahoo!?
Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen 
Massenmails. 
http://mail.yahoo.com

Re: [VOTE] codi as a new myfaces extensions sub-project

[Matthias Wessendorf]

+1

On Tue, Feb 16, 2010 at 12:00 PM, Gerhard Petracek
 wrote:
> +1
> regards,
> gerhard
> http://www.irian.at
>
> Your JSF powerhouse -
> JSF Consulting, Development and
> Courses in English and German
>
> Professional Support for Apache MyFaces
>
>
> 2010/2/16 Gerhard Petracek 
>>
>> hi @ all,
>> we have collected a lot of possible features for ext-cdi/codi and we have
>> several people who are interested in working on it [1].
>> so we should vote about the new module officially.
>>
>> ---
>> [ ] +1 for: codi should become a myfaces extensions sub-project
>> [ ] +0
>> [ ] -1 for: codi shouldn't become a myfaces extensions sub-project
>>
>> ---
>> the module should be hosted at [2].
>> i think we have a clear winner for the name: MyFaces CODI
>> (svn and jira will use (ext-)cdi to be consistent with the other extension
>> modules.)
>> regards,
>> gerhard
>> [1] http://wiki.apache.org/myfaces/Extensions/CDI/DevDoc/Drafts
>> [2] http://svn.apache.org/repos/asf/myfaces/extensions/cdi/
>> http://www.irian.at
>>
>> Your JSF powerhouse -
>> JSF Consulting, Development and
>> Courses in English and German
>>
>> Professional Support for Apache MyFaces
>
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

Re: [VOTE] codi as a new myfaces extensions sub-project

[Gerhard Petracek]

+1

regards,
gerhard

http://www.irian.at

Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German

Professional Support for Apache MyFaces


2010/2/16 Gerhard Petracek 

> hi @ all,
>
> we have collected a lot of possible features for ext-cdi/codi and we have
> several people who are interested in working on it [1].
> so we should vote about the new module officially.
>
>
> ---
> [ ] +1 for: codi should become a myfaces extensions sub-project
> [ ] +0
> [ ] -1 for: codi shouldn't become a myfaces extensions sub-project
>
> ---
>
> the module should be hosted at [2].
> i think we have a clear winner for the name: MyFaces CODI
> (svn and jira will use (ext-)cdi to be consistent with the other extension
> modules.)
>
> regards,
> gerhard
>
> [1] http://wiki.apache.org/myfaces/Extensions/CDI/DevDoc/Drafts
> [2] http://svn.apache.org/repos/asf/myfaces/extensions/cdi/
>
> http://www.irian.at
>
> Your JSF powerhouse -
> JSF Consulting, Development and
> Courses in English and German
>
> Professional Support for Apache MyFaces
>

[VOTE] codi as a new myfaces extensions sub-project

[Gerhard Petracek]

hi @ all,

we have collected a lot of possible features for ext-cdi/codi and we have
several people who are interested in working on it [1].
so we should vote about the new module officially.

---
[ ] +1 for: codi should become a myfaces extensions sub-project
[ ] +0
[ ] -1 for: codi shouldn't become a myfaces extensions sub-project
---

the module should be hosted at [2].
i think we have a clear winner for the name: MyFaces CODI
(svn and jira will use (ext-)cdi to be consistent with the other extension
modules.)

regards,
gerhard

[1] http://wiki.apache.org/myfaces/Extensions/CDI/DevDoc/Drafts
[2] http://svn.apache.org/repos/asf/myfaces/extensions/cdi/

http://www.irian.at

Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German

Professional Support for Apache MyFaces

Re: [VOTE] release for myfaces core 2.0.0-beta-2

[Bernd Bohmann]

+1

Regards

Bernd

On Tue, Feb 16, 2010 at 9:43 AM, Gerhard Petracek
 wrote:
> +1
> regards,
> gerhard
>
> http://www.irian.at
>
> Your JSF powerhouse -
> JSF Consulting, Development and
> Courses in English and German
>
> Professional Support for Apache MyFaces
>
>
> 2010/2/16 Grant Smith 
>>
>> +1
>>
>> On Mon, Feb 15, 2010 at 12:41 PM, Werner Punz 
>> wrote:
>>>
>>> +1
>>>
>>> Jakob Korherr schrieb:

 +1

 Regards,
 Jakob

 2010/2/15 Leonardo Uribe mailto:lu4...@gmail.com>>

    +1

    2010/2/15 Leonardo Uribe mailto:lu4...@gmail.com>>

        Hi,

        I was running the needed tasks to get the 2.0.0-beta-2 release
        of Apache
        MyFaces core out.

        This artifacts are very close to pass all TCK tests.

        Please note that this vote concerns all of the following parts:
         1. Maven artifact group "org.apache.myfaces.shared"
        v4.0.1-beta-2  [1]
         2. Maven artifact group "org.apache.myfaces.core"
        v2.0.0-beta-2  [1]
         3. Maven artifact group "org.apache.myfaces.test" v1.0.0-beta
 [1]

        The artifacts are deployed to my private Apache account ([1] and
        [3] for binary and source packages).

        The release notes could be found at [4].

        Also the clirr test does not show binary incompatibilities with
        myfaces-api.

        Please take a look at the "2.0.0-beta-2" artifacts and vote!

        Please note: This vote is "majority approval" with a minimum of
        three
        +1 votes (see [3]).

        
        [ ] +1 for community members who have reviewed the bits
        [ ] +0
        [ ] -1 for fatal flaws that should cause these bits not to be
        released,
         and why..
        

        Thanks,
        Leonardo Uribe

        [1] http://people.apache.org/~lu4242/myfaces200beta2
        
        [2] http://www.apache.org/foundation/voting.html#ReleaseVotes
        [3] http://people.apache.org/~lu4242/myfaces200beta2binsrc
        
        [4]

  https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600&styleName=Html&version=12314539

  



>>>
>>
>>
>>
>> --
>> Grant Smith - V.P. Information Technology
>> Marathon Computer Systems, LLC.
>>
>
>

Re: [VOTE] release for myfaces core 2.0.0-beta-2

[Gerhard Petracek]

+1

regards,
gerhard

http://www.irian.at

Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German

Professional Support for Apache MyFaces


2010/2/16 Grant Smith 

> +1
>
>
> On Mon, Feb 15, 2010 at 12:41 PM, Werner Punz wrote:
>
>> +1
>>
>> Jakob Korherr schrieb:
>>
>>> +1
>>>
>>> Regards,
>>> Jakob
>>>
>>> 2010/2/15 Leonardo Uribe mailto:lu4...@gmail.com>>
>>>
>>>+1
>>>
>>>2010/2/15 Leonardo Uribe mailto:lu4...@gmail.com>>
>>>
>>>
>>>Hi,
>>>
>>>I was running the needed tasks to get the 2.0.0-beta-2 release
>>>of Apache
>>>MyFaces core out.
>>>
>>>This artifacts are very close to pass all TCK tests.
>>>
>>>Please note that this vote concerns all of the following parts:
>>> 1. Maven artifact group "org.apache.myfaces.shared"
>>>v4.0.1-beta-2  [1]
>>> 2. Maven artifact group "org.apache.myfaces.core"
>>>v2.0.0-beta-2  [1]
>>> 3. Maven artifact group "org.apache.myfaces.test" v1.0.0-beta [1]
>>>
>>>The artifacts are deployed to my private Apache account ([1] and
>>>[3] for binary and source packages).
>>>
>>>The release notes could be found at [4].
>>>
>>>Also the clirr test does not show binary incompatibilities with
>>>myfaces-api.
>>>
>>>Please take a look at the "2.0.0-beta-2" artifacts and vote!
>>>
>>>Please note: This vote is "majority approval" with a minimum of
>>>three
>>>+1 votes (see [3]).
>>>
>>>
>>>[ ] +1 for community members who have reviewed the bits
>>>[ ] +0
>>>[ ] -1 for fatal flaws that should cause these bits not to be
>>>released,
>>> and why..
>>>
>>>
>>>Thanks,
>>>Leonardo Uribe
>>>
>>>[1] 
>>> http://people.apache.org/~lu4242/myfaces200beta2
>>>
>>>
>>>[2] http://www.apache.org/foundation/voting.html#ReleaseVotes
>>>[3] 
>>> http://people.apache.org/~lu4242/myfaces200beta2binsrc
>>>
>>>
>>>[4]
>>>
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600&styleName=Html&version=12314539
>>><
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600&styleName=Html&version=12314539
>>> >
>>>
>>>
>>>
>>>
>>
>
>
> --
> Grant Smith - V.P. Information Technology
> Marathon Computer Systems, LLC.
>
>