Re: cwiki permissions

[Gerhard Petracek]

hi @ all,

thomas has all permissions which are available.
however, (as far as i was told) the roles which are (still) in place are
deprecated/read-only (because they shouldn't be used any longer).

regards,
gerhard



2015-12-15 15:07 GMT+01:00 Mike Kienenberger :

> Thomas Andraschko commented on MYFACES-4012:
> > [~mkienenb] Would you please check my wiki role? I would like to change
> it but AFAICS i have no edit role.
>
> There is a myfaces-committers entry with all permissions set.
> I have no idea how to add people to that entry, and a search on "apache
> cwiki permissions" only shows setting up individual permissions.I've
> gone ahead and added tandraschko with full permissions.
>

Re: cwiki permissions

[Mike Kienenberger]

Thanks.  I suspected that the myfaces-committers list was no longer being
updated, but it helps to hear you confirm that.


On Tue, Dec 15, 2015 at 12:11 PM, Gerhard Petracek <
gerhard.petra...@gmail.com> wrote:

> hi @ all,
>
> thomas has all permissions which are available.
> however, (as far as i was told) the roles which are (still) in place are
> deprecated/read-only (because they shouldn't be used any longer).
>
> regards,
> gerhard
>
>
>
> 2015-12-15 15:07 GMT+01:00 Mike Kienenberger :
>
>> Thomas Andraschko commented on MYFACES-4012:
>> > [~mkienenb] Would you please check my wiki role? I would like to
>> change it but AFAICS i have no edit role.
>>
>> There is a myfaces-committers entry with all permissions set.
>> I have no idea how to add people to that entry, and a search on "apache
>> cwiki permissions" only shows setting up individual permissions.I've
>> gone ahead and added tandraschko with full permissions.
>>
>
>

Re: JIRA MYFACES-4022

[Hank Ibell]

Hello Thomas,

I did think injecting the FlowBuilderCDIExtension would work -- I was quite
surprised when it did. Also, after looking at the code again, I agree that
the lists should be ArrayList instead. Thank you for the quick review and
suggestions!

The new patch has been attached to this email and to the JIRA.


Regards,
Hank Ibell

On Mon, Dec 14, 2015 at 4:09 PM, Thomas Andraschko <
andraschko.tho...@gmail.com> wrote:

> Hi,
>
> i did a small review:
>
> 1) Why you don't use @Inject for the FlowBuilderCDIExtension in the
> FlowBuilderFactoryBean?
> 2) Why do you use CopyOnWriteArrayList? ArrayList should be fine as the
> both lists are AppScoped and should only be used on startup.
>
>
>
> 2015-12-14 21:53 GMT+01:00 Hank Ibell :
>
>> Hello Thomas,
>>
>> Thank you for the information. :) I will wait for Leo's review then.
>>
>> Regards,
>> Hank Ibell
>>
>> On Mon, Dec 14, 2015 at 3:20 PM, Thomas Andraschko <
>> andraschko.tho...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> first of all: thanks for the patch.
>>>
>>> As the last release-vote just passed last week, please have a little
>>> patience.
>>>
>>> AFAIR the flows-feature was the developed by Leo, so it would be the
>>> best if he could review it.
>>> Otherwise i will check it.
>>>
>>> Regards,
>>> Thomas
>>>
>>>
>>> 2015-12-14 3:46 GMT+01:00 Hank Ibell :
>>>
 Hello,

 It has been about a week since MYFACES-4022 [link
 ] has been opened
 and a potential patch has been submitted. There has been no feedback on the
 issue however.

 Is there anything else that is needed so that we can resolve this issue
 as soon as possible?

 Regards,
 Hank Ibell

>>>
>>>
>>
>
Index: impl/src/main/java/org/apache/myfaces/flow/cdi/DefaultCDIFacesFlowProvider.java
===
--- impl/src/main/java/org/apache/myfaces/flow/cdi/DefaultCDIFacesFlowProvider.java	(revision 1720218)
+++ impl/src/main/java/org/apache/myfaces/flow/cdi/DefaultCDIFacesFlowProvider.java	(working copy)
@@ -19,10 +19,10 @@
 package org.apache.myfaces.flow.cdi;
 
 import java.util.Iterator;
+import java.util.List;
 import java.util.Map;
 import java.util.logging.Level;
 import java.util.logging.Logger;
-import javax.enterprise.inject.Instance;
 import javax.enterprise.inject.spi.BeanManager;
 import javax.faces.context.FacesContext;
 import javax.faces.flow.Flow;
@@ -51,9 +51,9 @@
 FlowBuilderFactoryBean bean = CDIUtils.lookup(
 beanManager, FlowBuilderFactoryBean.class);
 
-Instance instance = bean.getFlowDefinitions();
+List flows = bean.getFlowDefinitions();
 
-return instance.iterator();
+return flows.iterator();
 }
 else
 {
Index: impl/src/main/java/org/apache/myfaces/flow/cdi/FlowBuilderCDIExtension.java
===
--- impl/src/main/java/org/apache/myfaces/flow/cdi/FlowBuilderCDIExtension.java	(revision 1720218)
+++ impl/src/main/java/org/apache/myfaces/flow/cdi/FlowBuilderCDIExtension.java	(working copy)
@@ -18,32 +18,56 @@
  */
 package org.apache.myfaces.flow.cdi;
 
+import java.util.ArrayList;
+import java.util.List;
+
 import javax.enterprise.event.Observes;
 import javax.enterprise.inject.spi.AnnotatedType;
 import javax.enterprise.inject.spi.BeanManager;
 import javax.enterprise.inject.spi.BeforeBeanDiscovery;
 import javax.enterprise.inject.spi.Extension;
+import javax.enterprise.inject.spi.ProcessProducer;
+import javax.enterprise.inject.spi.Producer;
+import javax.faces.flow.Flow;
+import javax.faces.flow.builder.FlowDefinition;
 
 /**
  * This extension is responsible of scan flow definitions through CDI. For example:
- * 
+ *
  * 
  * @Produces @FlowDefinition
  * public Flow defineFlow(@FlowBuilderParameter FlowBuilder flowBuilder) {...}
  * 
- * 
+ *
  * @author Leonardo Uribe
  */
 public class FlowBuilderCDIExtension implements Extension
 {
-
+private List flowProducers = new ArrayList();
+
+public List getFlowProducers()
+{
+return flowProducers;
+}
+
 void beforeBeanDiscovery(
 @Observes final BeforeBeanDiscovery event, BeanManager beanManager)
 {
 // Register FlowBuilderFactoryBean as a bean with CDI annotations, so the system
 // can take it into account, and use it later when necessary.
-AnnotatedType flowDiscoveryHelper = beanManager.createAnnotatedType(FlowBuilderFactoryBean.class);
+AnnotatedType flowDiscoveryHelper =
+beanManager.createAnnotatedType(FlowBuilderFactoryBean.class);
 event.addAnnotatedType(flowDiscoveryHelper);
 }
 
+/**
+ * Stores any producer method that is annotated with @FlowDefinition.
+ */
+ void findFlowDefinition(@Observes 

[jira] [Resolved] (MYFACES-2932) More error logging when Bean Validation throws an exception at startup

[Thomas Andraschko (JIRA)]

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

Thomas Andraschko resolved MYFACES-2932.

Resolution: Won't Fix

Please check our issue closing policy: 
http://myfaces.apache.org/wiki/core/committer-and-pmc-guide/myfaces-project-management.html
If the is issue is still important for you, please reopen and attach a patch.

> More error logging when Bean Validation throws an exception at startup
> --
>
> Key: MYFACES-2932
> URL: https://issues.apache.org/jira/browse/MYFACES-2932
> Project: MyFaces Core
>  Issue Type: Improvement
>  Components: JSR-314
>Affects Versions: 2.0.2
> Environment: Any
>Reporter: Jan-Kees van Andel
>
> When the Bean Validation implementation fails to startup, for example because 
> it is misconfigured by the developer, or because of some dependency issue 
> (missing slf4j jar or something), the Bean Validator automatically turns 
> itself off.
> The error is logged as "fine", because in many cases the developer doesn't 
> care about this behavior. For example, if bean validation api is provided, 
> but impl is not. In these cases, logging an error is not desirable.
> But maybe this should be increased to "info", to ease debugging in the cases 
> where the developer is interested in why bean validation fails to startup.
> I guess we change the logging to "info", especially because the block of code 
> is guarded by a Class.forName() check, which takes care of the obvious case 
> that Bean Validation is unavailable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MYFACES-4025) Incorrect JS content-type

[Bill Lucy (JIRA)]

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

Bill Lucy updated MYFACES-4025:
---
Status: Patch Available  (was: Open)

> Incorrect JS content-type
> -
>
> Key: MYFACES-4025
> URL: https://issues.apache.org/jira/browse/MYFACES-4025
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.2.8
>Reporter: Bill Lucy
>Assignee: Bill Lucy
>Priority: Minor
> Attachments: MYFACES-4025.patch
>
>
> We maintain some HtmlUnit tests, and I noticed that with MyFaces we've been 
> getting these messages:
> Obsolete content type encountered: 'application/x-javascript'.
> We certainly don't want to be using 'application/x-javascript', since that's 
> a very outdated type.  Convention, and our own code, suggests that we should 
> be using the 'text/javascript' MIME type.  This is a fairly trivial change.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (MYFACES-2629) Accept abstract FaceletContext, do not force AbstractFaceletContext

[Thomas Andraschko (JIRA)]

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

Thomas Andraschko resolved MYFACES-2629.

Resolution: Won't Fix

Please check our issue closing policy: 
http://myfaces.apache.org/wiki/core/committer-and-pmc-guide/myfaces-project-management.html
If the is issue is still important for you, please reopen and attach a patch.

> Accept abstract FaceletContext, do not force AbstractFaceletContext
> ---
>
> Key: MYFACES-2629
> URL: https://issues.apache.org/jira/browse/MYFACES-2629
> Project: MyFaces Core
>  Issue Type: Improvement
>  Components: General, JSR-314
>Affects Versions: 2.0.0-beta-3
> Environment: Tomcat 6.0+, MyFaces 2.0.0-beta3 API/Impl.
>Reporter: Lewis Gass
>Assignee: Leonardo Uribe
> Attachments: MYFACES-2629-1.patch, MYFACES-2629-2.patch
>
>
> I am the main coder on the Gracelets project 
> (http://gracelets.sourceforge.net/) and have recently began integration of 
> Groovy with JSF 2.0. In order for Gracelets to harness the already existing 
> Facelets libraries it needs access to the TagLibrary class and the actual 
> libraries loaded by the JSF 2.0 implementation. Since that library is not 
> part of the JSF 2.0 public API, I have to write an extension for each 
> different JSF 2.0 implementation in order to load them. I have been able to 
> successfully integrate with the SUN RI with minimal code. However, in MyFaces 
> Core implementation this code appears on line 135 of the 
> org.apache.myfaces.view.facelets.tag.jsf.ComponentTagHandlerDelegate:
> AbstractFaceletContext actx = (AbstractFaceletContext) ctx;
> Gracelets has its own FaceletContext (which is part of the public API) in 
> order to mimimize integration between different JSF 2.0 implementations. 
> Since in MyFaces this is forced to be a particular sub class here, it breaks 
> portability. Is there anyway this can be avoided?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MYFACES-2618) Don't warn if there is no submitted value in the current request for every EditableValueHolder

[Thomas Andraschko (JIRA)]

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

Thomas Andraschko updated MYFACES-2618:
---
Resolution: Won't Fix
Status: Resolved  (was: Patch Available)

Please check our issue closing policy: 
http://myfaces.apache.org/wiki/core/committer-and-pmc-guide/myfaces-project-management.html
If the is issue is still important for you, please reopen and attach a patch.

> Don't warn if there is no submitted value in the current request for every 
> EditableValueHolder
> --
>
> Key: MYFACES-2618
> URL: https://issues.apache.org/jira/browse/MYFACES-2618
> Project: MyFaces Core
>  Issue Type: Task
>  Components: JSR-314
>Affects Versions: 2.0.0-beta-2
>Reporter: Jakob Korherr
>Assignee: Jakob Korherr
>Priority: Minor
> Attachments: MYFACES-2618.patch
>
>
> Take a look at HtmlRendererUtils.decodeUIInput(): There we do a check for 
> paramMap.containsKey(clientId) and if this returns false (meaning that there 
> is no submitted value for the given component in the request parameter map) 
> we add a warning message to the log.
> I think we should get rid of this warning, because as a reason of AJAX it is 
> on my opinion normal to not submit all values of a form in every request. 
> Furthermore it has no impact on the lifecycle, because if the submitted value 
> is null it just isn't processed any further.
> See also the related thread on the mailing list: 
> http://www.mail-archive.com/users@myfaces.apache.org/msg55238.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MYFACES-4024) Update the NOTICE.txt file in jsf.myfaces

[Bill Lucy (JIRA)]

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

Bill Lucy updated MYFACES-4024:
---
Resolution: Fixed
  Assignee: Bill Lucy
Status: Resolved  (was: Patch Available)

The patch looks good to me; I went ahead and committed it.  I glanced through 
the other licenses and didn't see anything else that needed removal.

> Update the NOTICE.txt file in jsf.myfaces
> -
>
> Key: MYFACES-4024
> URL: https://issues.apache.org/jira/browse/MYFACES-4024
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.2.8
>Reporter: Eduardo Breijo
>Assignee: Bill Lucy
> Fix For: 2.2.10
>
> Attachments: MYFACES-4024.patch
>
>
> The NOTICE.txt file under META-INF directory is making reference to two 
> schemas. These schemas are: javaee_web_services_client_1_2.xsd which doesn't 
> exist in JSF 2.2 any more and javaee_5.xsd which is not needed since we are 
> using the open source one. It does not look like the xsd files have CDDL 
> license. 
> I have attached a patch for this issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: JIRA MYFACES-4022

[Leonardo Uribe]

Hi

I remember the current solution works in a case where myfaces jars are
shared by different web applications. Suppose a TomEE environment. The
solution proposed in the patch cause a problem when two webapps uses faces
flow, because one app could find the flows of the other one (variable for
FlowBuilderCDIExtension).

I don't have idea if the solution proposed works in that case, so we need
to check that before apply it.

regards,

Leonardo Uribe


2015-12-15 14:58 GMT-05:00 Hank Ibell :

> Hello Thomas,
>
> I did think injecting the FlowBuilderCDIExtension would work -- I was
> quite surprised when it did. Also, after looking at the code again, I agree
> that the lists should be ArrayList instead. Thank you for the quick review
> and suggestions!
>
> The new patch has been attached to this email and to the JIRA.
>
>
> Regards,
> Hank Ibell
>
> On Mon, Dec 14, 2015 at 4:09 PM, Thomas Andraschko <
> andraschko.tho...@gmail.com> wrote:
>
>> Hi,
>>
>> i did a small review:
>>
>> 1) Why you don't use @Inject for the FlowBuilderCDIExtension in the
>> FlowBuilderFactoryBean?
>> 2) Why do you use CopyOnWriteArrayList? ArrayList should be fine as the
>> both lists are AppScoped and should only be used on startup.
>>
>>
>>
>> 2015-12-14 21:53 GMT+01:00 Hank Ibell :
>>
>>> Hello Thomas,
>>>
>>> Thank you for the information. :) I will wait for Leo's review then.
>>>
>>> Regards,
>>> Hank Ibell
>>>
>>> On Mon, Dec 14, 2015 at 3:20 PM, Thomas Andraschko <
>>> andraschko.tho...@gmail.com> wrote:
>>>
 Hi,

 first of all: thanks for the patch.

 As the last release-vote just passed last week, please have a little
 patience.

 AFAIR the flows-feature was the developed by Leo, so it would be the
 best if he could review it.
 Otherwise i will check it.

 Regards,
 Thomas


 2015-12-14 3:46 GMT+01:00 Hank Ibell :

> Hello,
>
> It has been about a week since MYFACES-4022 [link
> ] has been opened
> and a potential patch has been submitted. There has been no feedback on 
> the
> issue however.
>
> Is there anything else that is needed so that we can resolve this
> issue as soon as possible?
>
> Regards,
> Hank Ibell
>


>>>
>>
>

[jira] [Resolved] (MYFACES-2674) ClassNotFoundException when using "org.apache.myfaces.annotation.SCAN_PACKAGES" parameter with not existing package

[Thomas Andraschko (JIRA)]

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

Thomas Andraschko resolved MYFACES-2674.

Resolution: Won't Fix

Please check our issue closing policy: 
http://myfaces.apache.org/wiki/core/committer-and-pmc-guide/myfaces-project-management.html
If the is issue is still important for you, please reopen and attach a patch.

> ClassNotFoundException when using 
> "org.apache.myfaces.annotation.SCAN_PACKAGES" parameter with not existing 
> package
> ---
>
> Key: MYFACES-2674
> URL: https://issues.apache.org/jira/browse/MYFACES-2674
> Project: MyFaces Core
>  Issue Type: Bug
>  Components: JSR-314
>Reporter: Matthias Weßendorf
>
> in web.xml have the following ctx param:
> 
> org.apache.myfaces.annotation.SCAN_PACKAGES
> net.wessendorf
> 
> but if this package does not exist, you'll notice this:
> Caused by: java.lang.ClassNotFoundException: No resource for net/wessendorf
>   at 
> org.apache.myfaces.config.annotation._PackageInfo.getClasses(_PackageInfo.java:102)
>   at 
> org.apache.myfaces.config.annotation.AnnotationConfigurator.packageClasses(AnnotationConfigurator.java:332)
>   at 
> org.apache.myfaces.config.annotation.AnnotationConfigurator.configure(AnnotationConfigurator.java:186)
>   ... 17 more



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MYFACES-4025) Incorrect JS content-type

[Bill Lucy (JIRA)]

Bill Lucy created MYFACES-4025:
--

 Summary: Incorrect JS content-type
 Key: MYFACES-4025
 URL: https://issues.apache.org/jira/browse/MYFACES-4025
 Project: MyFaces Core
  Issue Type: Bug
Affects Versions: 2.2.8
Reporter: Bill Lucy
Assignee: Bill Lucy
Priority: Minor


We maintain some HtmlUnit tests, and I noticed that with MyFaces we've been 
getting these messages:

Obsolete content type encountered: 'application/x-javascript'.

We certainly don't want to be using 'application/x-javascript', since that's a 
very outdated type.  Convention, and our own code, suggests that we should be 
using the 'text/javascript' MIME type.  This is a fairly trivial change.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[ANNOUNCE] MyFaces Core v2.2.9 Release

[Leonardo Uribe]

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

MyFaces Core is a JavaServer(tm) Faces 2.2 implementation as specified by
JSR-344.

The artifacts passed the TCK test of Feb 2013 (jsftck-2.2_26-Feb-2013.zip).

MyFaces Core 2.2.9 is available in both binary and source distributions.

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

MyFaces Core is also available in the central Maven repository under Group
ID "org.apache.myfaces.core".

Release Notes - MyFaces Core - Version 2.2.9

Bug

[MYFACES-3957] - Disabled h:commandLink results in rendering of a span
with onclick
[MYFACES-3978] - NullPointerException in FaceletStateValueExpression
when ViewPooling enabled
[MYFACES-3980] - c:forEach varStatus is assigned with the wrong base
[MYFACES-3981] - Unable to resolve Integer API as Lambda expression in
a facelet
[MYFACES-3982] - javax.faces.context.ExternalContext#getInitParameter
should throw NPE when name is null
[MYFACES-3983] - ViewScopeBinding does not work, results in an
exception when using a datatable
[MYFACES-3986] - viewScope implicit object not resolved in a JSP page
[MYFACES-3988] - An empty tag in a custom tag-lib causes an Exception
[MYFACES-3989] - MalformedURLException when
javax.faces.FACELETS_LIBRARIES contains line feed
[MYFACES-3992] - f:ajax doesn't append javax.faces.ViewState back on
re-render of form in stateless view
[MYFACES-3996] - Value of HTML-Attribute class on Passthrough element
is casted to java.lang.Class if coming from EL
[MYFACES-4000] - Some MyFaces JSF 2.2 API signatures do not match the
Java EE 7 API
[MYFACES-4003] - Allow the "class" Attribute To Be Set For Custom Tags
[MYFACES-4008] - AbstractMethodError thrown by
javax.servlet.http.Part.getSubmittedFileName()
[MYFACES-4010] - MyFaces 2.2 throws UnsupportedOperationException with
an eager ManagedBean with ManagedProperty
[MYFACES-4016] - Error when submitting an Ajax request for an element
without an ID
[MYFACES-4017] - custom expression factory not correctly loaded
[MYFACES-4019] - Updating a bound value not possible if input component
is within c:forEach

Improvement

[MYFACES-3063] - code cleanup and performance review
[MYFACES-3985] - [perf] avoid field initialization on CDI beans
[MYFACES-4001] - Outdated java.sun.com XML namespaces in 2.2 tagdoc
[MYFACES-4014] - Log required startup time
[MYFACES-4015] - [perf] provide annotation scanning via CDI extension

Task

[MYFACES-4005] - Classloading conflict with httpclient (update
commons-codec to 1.10)


regards,

Leonardo Uribe

[jira] [Commented] (MYFACES-4021) blacklist org.codehaus.groovy.runtime.,org.apache.commons.collections.functors.,org.apache.xalan in MyFacesObjectInputStream

[Leonardo Uribe (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15059154#comment-15059154
 ] 

Leonardo Uribe commented on MYFACES-4021:
-

I think it is not necessary to do anything in this case. There is a web config 
parameter called org.apache.myfaces.SERIAL_FACTORY that allows you to provide 
your custom factory and override MyFacesObjectInputStream with something else. 
Add a blacklist on the default deserializer sounds overkill. 

> blacklist 
> org.codehaus.groovy.runtime.,org.apache.commons.collections.functors.,org.apache.xalan
>  in  MyFacesObjectInputStream
> -
>
> Key: MYFACES-4021
> URL: https://issues.apache.org/jira/browse/MYFACES-4021
> Project: MyFaces Core
>  Issue Type: Bug
>Reporter: Romain Manni-Bucau
>Priority: Blocker
>
> https://github.com/apache/incubator-batchee/commit/cfd133c309c21a82fb24cfcc9a7c2365aee4678a#diff-acd0bc06477ce776b0ad8fdda76f8b7eR56
>  mecanism can be used
> (due to recent vulnerability discovered in [collections], spring, groovy we 
> can't suppose we don't run with these libraries so we need this fix as well)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (MYFACES-4012) Documentation wrong about Error handling

[Thomas Andraschko (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15057981#comment-15057981
 ] 

Thomas Andraschko edited comment on MYFACES-4012 at 12/15/15 12:30 PM:
---

[~mkienenb] Would you please check my wiki role? I would like to change it but 
AFAICS i have no edit role.


was (Author: tandraschko):
[~mkienenb] Would you please check my wiki role? I would like to change it but 
AFAIK i have no edit role.

> Documentation wrong about Error handling
> 
>
> Key: MYFACES-4012
> URL: https://issues.apache.org/jira/browse/MYFACES-4012
> Project: MyFaces Core
>  Issue Type: Bug
>  Components: website
>Reporter: Matthew Alexander
>Priority: Minor
>
> https://cwiki.apache.org/confluence/display/MYFACES/Handling+Server+Errors
> Current version:
> {quote}
> *Provide an error page*
> The default ExceptionHandler in Production stage or when myfaces error 
> handling is disabled just throw an exception. So you can still setup an error 
> page adding something like this in your web.xml file:
> {code}
> 500
> /somepage.jsp
> {code}
> {quote}
> Should be:
> {quote}
> *Provide an error page*
> If org.apache.myfaces.ERROR_HANDLING is set to "false", or if it is undefined 
> and the project stage is "Development", the default ExceptionHandler just 
> throws an exception. So you can still setup an error page by adding something 
> like this in your web.xml file:
> {code}
> 500
> /somepage.jsp
> {code}
> {quote}
> Changes
> - Corrected the explanation of the behavior of the default ExceptionHandler.
> - Improved the grammar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MYFACES-4012) Documentation wrong about Error handling

[Thomas Andraschko (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15057981#comment-15057981
 ] 

Thomas Andraschko commented on MYFACES-4012:


[~mkienenb] Would you please check my wiki role? I would like to change it but 
AFAIK i have no edit role.

> Documentation wrong about Error handling
> 
>
> Key: MYFACES-4012
> URL: https://issues.apache.org/jira/browse/MYFACES-4012
> Project: MyFaces Core
>  Issue Type: Bug
>  Components: website
>Reporter: Matthew Alexander
>Priority: Minor
>
> https://cwiki.apache.org/confluence/display/MYFACES/Handling+Server+Errors
> Current version:
> {quote}
> *Provide an error page*
> The default ExceptionHandler in Production stage or when myfaces error 
> handling is disabled just throw an exception. So you can still setup an error 
> page adding something like this in your web.xml file:
> {code}
> 500
> /somepage.jsp
> {code}
> {quote}
> Should be:
> {quote}
> *Provide an error page*
> If org.apache.myfaces.ERROR_HANDLING is set to "false", or if it is undefined 
> and the project stage is "Development", the default ExceptionHandler just 
> throws an exception. So you can still setup an error page by adding something 
> like this in your web.xml file:
> {code}
> 500
> /somepage.jsp
> {code}
> {quote}
> Changes
> - Corrected the explanation of the behavior of the default ExceptionHandler.
> - Improved the grammar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

cwiki permissions

[Mike Kienenberger]

 Thomas Andraschko commented on MYFACES-4012:
> [~mkienenb] Would you please check my wiki role? I would like to change
it but AFAICS i have no edit role.

There is a myfaces-committers entry with all permissions set.
I have no idea how to add people to that entry, and a search on "apache
cwiki permissions" only shows setting up individual permissions.I've
gone ahead and added tandraschko with full permissions.

[jira] [Commented] (MYFACES-4012) Documentation wrong about Error handling

[Thomas Andraschko (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15058103#comment-15058103
 ] 

Thomas Andraschko commented on MYFACES-4012:


Thanks Mike!
Done!

> Documentation wrong about Error handling
> 
>
> Key: MYFACES-4012
> URL: https://issues.apache.org/jira/browse/MYFACES-4012
> Project: MyFaces Core
>  Issue Type: Bug
>  Components: website
>Reporter: Matthew Alexander
>Priority: Minor
>
> https://cwiki.apache.org/confluence/display/MYFACES/Handling+Server+Errors
> Current version:
> {quote}
> *Provide an error page*
> The default ExceptionHandler in Production stage or when myfaces error 
> handling is disabled just throw an exception. So you can still setup an error 
> page adding something like this in your web.xml file:
> {code}
> 500
> /somepage.jsp
> {code}
> {quote}
> Should be:
> {quote}
> *Provide an error page*
> If org.apache.myfaces.ERROR_HANDLING is set to "false", or if it is undefined 
> and the project stage is "Development", the default ExceptionHandler just 
> throws an exception. So you can still setup an error page by adding something 
> like this in your web.xml file:
> {code}
> 500
> /somepage.jsp
> {code}
> {quote}
> Changes
> - Corrected the explanation of the behavior of the default ExceptionHandler.
> - Improved the grammar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (MYFACES-4012) Documentation wrong about Error handling

[Thomas Andraschko (JIRA)]

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

Thomas Andraschko resolved MYFACES-4012.

Resolution: Fixed
  Assignee: Thomas Andraschko

> Documentation wrong about Error handling
> 
>
> Key: MYFACES-4012
> URL: https://issues.apache.org/jira/browse/MYFACES-4012
> Project: MyFaces Core
>  Issue Type: Bug
>  Components: website
>Reporter: Matthew Alexander
>Assignee: Thomas Andraschko
>Priority: Minor
>
> https://cwiki.apache.org/confluence/display/MYFACES/Handling+Server+Errors
> Current version:
> {quote}
> *Provide an error page*
> The default ExceptionHandler in Production stage or when myfaces error 
> handling is disabled just throw an exception. So you can still setup an error 
> page adding something like this in your web.xml file:
> {code}
> 500
> /somepage.jsp
> {code}
> {quote}
> Should be:
> {quote}
> *Provide an error page*
> If org.apache.myfaces.ERROR_HANDLING is set to "false", or if it is undefined 
> and the project stage is "Development", the default ExceptionHandler just 
> throws an exception. So you can still setup an error page by adding something 
> like this in your web.xml file:
> {code}
> 500
> /somepage.jsp
> {code}
> {quote}
> Changes
> - Corrected the explanation of the behavior of the default ExceptionHandler.
> - Improved the grammar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)