[jira] [Commented] (MYFACES-4129) When @FacesConfig annotation is used in a CDI bean, implicit EL objects don't work

[Eduardo Breijo (JIRA)]

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

Eduardo Breijo commented on MYFACES-4129:
-

I have provided a patch. You will noticed that I added few more missing EL 
implicit objects. Any feedback will be appreciated.

> When @FacesConfig annotation is used in a CDI bean, implicit EL objects don't 
> work
> --
>
> Key: MYFACES-4129
> URL: https://issues.apache.org/jira/browse/MYFACES-4129
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Eduardo Breijo
> Attachments: ImplicitELObjects.war, MYFACES-4129.patch
>
>
> When the @javax.faces.annotation.FacesConfig annotation is used in a CDI 
> bean, the implicit EL Objects from JSF 2.3 spec section 5.9.2 don't work. 
> This is because when that FacesConfig annotation is in a bean we remove the 
> implicit EL resolver from the chain so we don't have any mechanism for CDI to 
> do the resolution of the implicit objects.
> Tested this on Mojarra and it works fine, with or without @FacesConfig 
> annotation.
> A sample app is provided. It can be deployed on tomcat:
> 1) Drive a request to: http://localhost:8080/ImplicitELObjects/index.jsf
> 2) You should see that Application: ApplicationScope: and Component: are 
> empty since they cannot be resolved



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (MYFACES-4129) When @FacesConfig annotation is used in a CDI bean, implicit EL objects don't work

[Eduardo Breijo (JIRA)]

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

Eduardo Breijo edited comment on MYFACES-4129 at 7/27/17 8:03 PM:
--

I have provided a patch. You will notice that I added few more missing EL 
implicit objects. Any feedback will be appreciated.


was (Author: eduardobreijo):
I have provided a patch. You will noticed that I added few more missing EL 
implicit objects. Any feedback will be appreciated.

> When @FacesConfig annotation is used in a CDI bean, implicit EL objects don't 
> work
> --
>
> Key: MYFACES-4129
> URL: https://issues.apache.org/jira/browse/MYFACES-4129
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Eduardo Breijo
> Attachments: ImplicitELObjects.war, MYFACES-4129.patch
>
>
> When the @javax.faces.annotation.FacesConfig annotation is used in a CDI 
> bean, the implicit EL Objects from JSF 2.3 spec section 5.9.2 don't work. 
> This is because when that FacesConfig annotation is in a bean we remove the 
> implicit EL resolver from the chain so we don't have any mechanism for CDI to 
> do the resolution of the implicit objects.
> Tested this on Mojarra and it works fine, with or without @FacesConfig 
> annotation.
> A sample app is provided. It can be deployed on tomcat:
> 1) Drive a request to: http://localhost:8080/ImplicitELObjects/index.jsf
> 2) You should see that Application: ApplicationScope: and Component: are 
> empty since they cannot be resolved



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MYFACES-4129) When @FacesConfig annotation is used in a CDI bean, implicit EL objects don't work

[Eduardo Breijo (JIRA)]

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

Eduardo Breijo updated MYFACES-4129:

Status: Patch Available  (was: Open)

> When @FacesConfig annotation is used in a CDI bean, implicit EL objects don't 
> work
> --
>
> Key: MYFACES-4129
> URL: https://issues.apache.org/jira/browse/MYFACES-4129
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Eduardo Breijo
> Attachments: ImplicitELObjects.war, MYFACES-4129.patch
>
>
> When the @javax.faces.annotation.FacesConfig annotation is used in a CDI 
> bean, the implicit EL Objects from JSF 2.3 spec section 5.9.2 don't work. 
> This is because when that FacesConfig annotation is in a bean we remove the 
> implicit EL resolver from the chain so we don't have any mechanism for CDI to 
> do the resolution of the implicit objects.
> Tested this on Mojarra and it works fine, with or without @FacesConfig 
> annotation.
> A sample app is provided. It can be deployed on tomcat:
> 1) Drive a request to: http://localhost:8080/ImplicitELObjects/index.jsf
> 2) You should see that Application: ApplicationScope: and Component: are 
> empty since they cannot be resolved



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Migrate all MyFaces projects to Git

[Bernd Bohmann]

And we need a formal vote

Regards

Bernd

On Thu, Jul 27, 2017 at 8:47 PM, Bernd Bohmann  wrote:

> We should define a workflow like this:
>
> https://wiki.apache.org/nutch/UsingGit
>
> And we should aware that commiters must enable 2 factor auth on Github and
> add the github id to the apache profile
> see: https://gitbox.apache.org/setup/
>
> On Thu, Jul 27, 2017 at 7:09 PM, Bernd Bohmann <
> bernd.bohm...@googlemail.com> wrote:
>
>> I'm fine with everything with better integration.
>>
>> Bernd
>>
>>
>> Am 27.07.2017 17:50 schrieb "Dennis Kieselhorst" :
>>
>> In the meantime infra launched Gitbox with even better GitHub
>> integration, so in my view we should use that from the beginning:
>> http://gitbox.apache.org
>>
>>
>>
>

Re: Migrate all MyFaces projects to Git

[Bernd Bohmann]

We should define a workflow like this:

https://wiki.apache.org/nutch/UsingGit

And we should aware that commiters must enable 2 factor auth on Github and
add the github id to the apache profile
see: https://gitbox.apache.org/setup/

On Thu, Jul 27, 2017 at 7:09 PM, Bernd Bohmann  wrote:

> I'm fine with everything with better integration.
>
> Bernd
>
>
> Am 27.07.2017 17:50 schrieb "Dennis Kieselhorst" :
>
> In the meantime infra launched Gitbox with even better GitHub
> integration, so in my view we should use that from the beginning:
> http://gitbox.apache.org
>
>
>

Re: Migrate all MyFaces projects to Git

[Bernd Bohmann]

I'm fine with everything with better integration.

Bernd

Am 27.07.2017 17:50 schrieb "Dennis Kieselhorst" :

In the meantime infra launched Gitbox with even better GitHub
integration, so in my view we should use that from the beginning:
http://gitbox.apache.org

Re: Migrate all MyFaces projects to Git

[Dennis Kieselhorst]

In the meantime infra launched Gitbox with even better GitHub
integration, so in my view we should use that from the beginning:
http://gitbox.apache.org

[jira] [Commented] (MYFACES-4129) When @FacesConfig annotation is used in a CDI bean, implicit EL objects don't work

[Eduardo Breijo (JIRA)]

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

Eduardo Breijo commented on MYFACES-4129:
-

I'm currently working on a patch. I'll upload it once it is finished.

> When @FacesConfig annotation is used in a CDI bean, implicit EL objects don't 
> work
> --
>
> Key: MYFACES-4129
> URL: https://issues.apache.org/jira/browse/MYFACES-4129
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Eduardo Breijo
> Attachments: ImplicitELObjects.war
>
>
> When the @javax.faces.annotation.FacesConfig annotation is used in a CDI 
> bean, the implicit EL Objects from JSF 2.3 spec section 5.9.2 don't work. 
> This is because when that FacesConfig annotation is in a bean we remove the 
> implicit EL resolver from the chain so we don't have any mechanism for CDI to 
> do the resolution of the implicit objects.
> Tested this on Mojarra and it works fine, with or without @FacesConfig 
> annotation.
> A sample app is provided. It can be deployed on tomcat:
> 1) Drive a request to: http://localhost:8080/ImplicitELObjects/index.jsf
> 2) You should see that Application: ApplicationScope: and Component: are 
> empty since they cannot be resolved



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Migrate all MyFaces projects to Git

[Bernd Bohmann]

Hello Dora

this is not possible for apache projects

see: https://git-wip-us.apache.org

and

https://www.apache.org/dev/writable-git

but there are readonly mirrors at https://github.com/apache

Regards

Bernd

On Thu, Jul 27, 2017 at 4:10 PM, Dora Rajappan 
wrote:

> Is it github.com where you are going to migrate myfaces to?
>
>
> On Thursday, July 27, 2017, 7:06:06 PM GMT+5:30, Bernd Bohmann <
> bernd.bohm...@googlemail.com> wrote:
>
>
> for Trinidad as well
>
> On Thu, Jul 27, 2017 at 2:29 PM, Udo Schnurpfeil 
> wrote:
>
> Hi,
>
> for Tobago I think, we can do it now!
>
> Regards,
>
> Udo
>
> Am 27.07.17 um 13:03 schrieb Bernd Bohmann:
> > Ok
> >
> > we have some agreement about moving to git.
> > Now we should define some time line.
> > Any suggestions from the active subprojects?
> >
> > Something like
> > 'I would like to move to git after blah blah release'
> > 'I would like to move now'
> > 'I would like to move in 2 weeks'
> > or whatever
> >
> > I can support the migration to git.
> >
> > Regards
> >
> > Bernd
> >
> >
> >
> >
> > On Thu, Apr 20, 2017 at 5:16 PM, Kito Mann  > > wrote:
> >
> > Ah, this may be why it's worked for me -- smaller projects with
> > defined release cycles.
> >
> > Anyway, I never meant to imply that git == git flow. We will need
> > some sort of process, though, and the DeltaSpike one seems like a
> > good place to start.
> >
> > ___
> >
> > Kito D. Mann | @kito99 | Author, JSF in Action
> > Web Components, Polymer, JSF, PrimeFaces, Java EE training and
> > consulting
> > Virtua, Inc. | virtua.tech
> > JSFCentral.com | @jsfcentral | knowesis.io  -
> > fresh Web Components info
> > +1 203-998-0403 
> >
> > * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
> > 
> > * Listen to the Enterprise Java Newscast:
> http://enterprisejavanews.com
> >
> >
> > On Thu, Apr 20, 2017 at 8:02 AM, Mark Struberg  > > wrote:
> >
> > gitflow is pure pita ;)
> > It basically only works for companies where you have a single
> > manager who decides what goes in and what not.
> >
> > But GIT != gitflow. gitflow has nothing to do with the GIT scm
> > itself, but is just a fancy name for a development process with
> > an explicit build-branch and a build-master.
> >
> > +0 on moving to GIT.
> > SVN works good enough imo, but GIT ofc also would work.
> >
> > LIeGrue,
> > strub
> >
> > > Am 19.04.2017 um 12:57 schrieb Kito Mann  > > :
> > >
> > > +1
> > >
> > > Wha's wrong with GitFlow?
> > >
> > > ___
> > >
> > > Kito D. Mann | @kito99 | Author, JSF in Action
> > > Web Components, Polymer, JSF, PrimeFaces, Java EE training and
> > consulting
> > > Virtua, Inc. | virtua.tech
> > > JSFCentral.com | @jsfcentral | knowesis.io
> >  - fresh Web Components info
> > > +1 203-998-0403 
> > >
> > > * See me speak at the ng-conf April 5th-8th:
> http://bit.ly/2mw7HBj
> > > * Listen to the Enterprise Java Newscast:
> > http://enterprisejavanews.com
> > >
> > >
> > > On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann
> >  >  >> wrote:
> > > Hello
> > >
> > > I think the changes will be not so complicated. The deltaspike
> > pom looks nice :-)
> > > If someone talks about git-flow process i'm out.
> > >
> > > Regards
> > >
> > > Bernd
> > >
> > > On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe
> > > wrote:
> > > +1
> > >
> > > Change the release process is a pain, but I agree there are
> > some benefits moving to git.
> > >
> > > But when I see here:
> > >
> > > https://github.com/apache/ myfaces
> 
> >  >
> > >
> > > It says:
> > >
> > > mirrored from git://git.apache.org/myfaces. git
> 
> >  >
> > >
> > > But I have never checked where that file is or how to change
> it.
> > >
> > > Looking in deltaspike, the svn repo only has the site (for the
> > CMS) and 

[jira] [Commented] (TOBAGO-1751) Add META-tags to -tag

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/TOBAGO-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16103297#comment-16103297
 ] 

Hudson commented on TOBAGO-1751:


SUCCESS: Integrated in Jenkins build Tobago Trunk #965 (See 
[https://builds.apache.org/job/Tobago%20Trunk/965/])
TOBAGO-1751: Add META-tags to -tag
* fix:  is no longer rendered twice. (lofwyr: 
[http://svn.apache.org/viewvc/?view=rev=1803189])
* (edit) 
tobago-trunk/tobago-core/src/main/java/org/apache/myfaces/tobago/internal/renderkit/renderer/PageRenderer.java


> Add META-tags to -tag
> ---
>
> Key: TOBAGO-1751
> URL: https://issues.apache.org/jira/browse/TOBAGO-1751
> Project: MyFaces Tobago
>  Issue Type: New Feature
>  Components: Core
>Reporter: Guido Dubois
>Assignee: Udo Schnurpfeil
>Priority: Minor
> Fix For: 4.0.0
>
>
> Is there a simple way to include META-tags to the  section of a 
> ?
> It would be nice to have a tag according to  or  file=""> for this.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Migrate all MyFaces projects to Git

[Dora Rajappan]

Is it github.com where you are going to migrate myfaces to?

On Thursday, July 27, 2017, 7:06:06 PM GMT+5:30, Bernd Bohmann 
 wrote:

for Trinidad as well
On Thu, Jul 27, 2017 at 2:29 PM, Udo Schnurpfeil  wrote:

Hi,

for Tobago I think, we can do it now!

Regards,

Udo

Am 27.07.17 um 13:03 schrieb Bernd Bohmann:
> Ok
>
> we have some agreement about moving to git.
> Now we should define some time line.
> Any suggestions from the active subprojects?
>
> Something like
> 'I would like to move to git after blah blah release'
> 'I would like to move now'
> 'I would like to move in 2 weeks'
> or whatever
>
> I can support the migration to git.
>
> Regards
>
> Bernd
>
>
>
>
> On Thu, Apr 20, 2017 at 5:16 PM, Kito Mann  > wrote:
>
>     Ah, this may be why it's worked for me -- smaller projects with
>     defined release cycles.
>
>     Anyway, I never meant to imply that git == git flow. We will need
>     some sort of process, though, and the DeltaSpike one seems like a
>     good place to start.
>
>     ___
>
>     Kito D. Mann | @kito99 | Author, JSF in Action
>     Web Components, Polymer, JSF, PrimeFaces, Java EE training and
>     consulting
>     Virtua, Inc. | virtua.tech
>     JSFCentral.com | @jsfcentral | knowesis.io  -
>     fresh Web Components info
>     +1 203-998-0403 
>
>     * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
>     
>     * Listen to the Enterprise Java Newscast: http://enterprisejavanews.com
>
>
>     On Thu, Apr 20, 2017 at 8:02 AM, Mark Struberg      > wrote:
>
>         gitflow is pure pita ;)
>         It basically only works for companies where you have a single
>         manager who decides what goes in and what not.
>
>         But GIT != gitflow. gitflow has nothing to do with the GIT scm
>         itself, but is just a fancy name for a development process with
>         an explicit build-branch and a build-master.
>
>         +0 on moving to GIT.
>         SVN works good enough imo, but GIT ofc also would work.
>
>         LIeGrue,
>         strub
>
>         > Am 19.04.2017 um 12:57 schrieb Kito Mann          > :
>         >
>         > +1
>         >
>         > Wha's wrong with GitFlow?
>         >
>         > ___
>         >
>         > Kito D. Mann | @kito99 | Author, JSF in Action
>         > Web Components, Polymer, JSF, PrimeFaces, Java EE training and
>         consulting
>         > Virtua, Inc. | virtua.tech
>         > JSFCentral.com | @jsfcentral | knowesis.io
>          - fresh Web Components info
>         > +1 203-998-0403 
>         >
>         > * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
>         > * Listen to the Enterprise Java Newscast:
>         http://enterprisejavanews.com
>         >
>         >
>         > On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann
>                  > wrote:
>         > Hello
>         >
>         > I think the changes will be not so complicated. The deltaspike
>         pom looks nice :-)
>         > If someone talks about git-flow process i'm out.
>         >
>         > Regards
>         >
>         > Bernd
>         >
>         > On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe
>         > wrote:
>         > +1
>         >
>         > Change the release process is a pain, but I agree there are
>         some benefits moving to git.
>         >
>         > But when I see here:
>         >
>         > https://github.com/apache/ myfaces
>         
>         >
>         > It says:
>         >
>         > mirrored from git://git.apache.org/myfaces. git
>         
>         >
>         > But I have never checked where that file is or how to change it.
>         >
>         > Looking in deltaspike, the svn repo only has the site (for the
>         CMS) and the source code lives on git. If that so, we still need
>         the svn, so I agree it is a good idea to move only some
>         subprojects to git.
>         >
>         > regards,
>         >
>         > Leonardo Uribe
>         >
>         >
>         >       Virus-free. www.avast.com 
>         >
>         > 2017-04-17 11:40 GMT-05:00 Grant Smith          > :
>         > +1
>         >
>         > Couldn't agree more.
>         >
>         > Grant Smith - V.P. Information Technology
>         > Marathon Computer Systems, LLC.
>         >
>         > On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann
>         

[jira] [Commented] (TOBAGO-1751) Add META-tags to -tag

[Udo Schnurpfeil (JIRA)]

[ 
https://issues.apache.org/jira/browse/TOBAGO-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16103245#comment-16103245
 ] 

Udo Schnurpfeil commented on TOBAGO-1751:
-

 is no longer rendered twice.

> Add META-tags to -tag
> ---
>
> Key: TOBAGO-1751
> URL: https://issues.apache.org/jira/browse/TOBAGO-1751
> Project: MyFaces Tobago
>  Issue Type: New Feature
>  Components: Core
>Reporter: Guido Dubois
>Assignee: Udo Schnurpfeil
>Priority: Minor
> Fix For: 4.0.0
>
>
> Is there a simple way to include META-tags to the  section of a 
> ?
> It would be nice to have a tag according to  or  file=""> for this.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TOBAGO-1751) Add META-tags to -tag

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/TOBAGO-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16103222#comment-16103222
 ] 

Hudson commented on TOBAGO-1751:


FAILURE: Integrated in Jenkins build Tobago Trunk #963 (See 
[https://builds.apache.org/job/Tobago%20Trunk/963/])
TOBAGO-1751: Add META-tags to -tag
* workaround: drop jsf.js from WebSphere (lofwyr: 
[http://svn.apache.org/viewvc/?view=rev=1803181])
* (edit) 
tobago-trunk/tobago-core/src/main/java/org/apache/myfaces/tobago/internal/renderkit/renderer/PageRenderer.java


> Add META-tags to -tag
> ---
>
> Key: TOBAGO-1751
> URL: https://issues.apache.org/jira/browse/TOBAGO-1751
> Project: MyFaces Tobago
>  Issue Type: New Feature
>  Components: Core
>Reporter: Guido Dubois
>Assignee: Udo Schnurpfeil
>Priority: Minor
> Fix For: 4.0.0
>
>
> Is there a simple way to include META-tags to the  section of a 
> ?
> It would be nice to have a tag according to  or  file=""> for this.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Migrate all MyFaces projects to Git

[Bernd Bohmann]

for Trinidad as well

On Thu, Jul 27, 2017 at 2:29 PM, Udo Schnurpfeil  wrote:

> Hi,
>
> for Tobago I think, we can do it now!
>
> Regards,
>
> Udo
>
> Am 27.07.17 um 13:03 schrieb Bernd Bohmann:
> > Ok
> >
> > we have some agreement about moving to git.
> > Now we should define some time line.
> > Any suggestions from the active subprojects?
> >
> > Something like
> > 'I would like to move to git after blah blah release'
> > 'I would like to move now'
> > 'I would like to move in 2 weeks'
> > or whatever
> >
> > I can support the migration to git.
> >
> > Regards
> >
> > Bernd
> >
> >
> >
> >
> > On Thu, Apr 20, 2017 at 5:16 PM, Kito Mann  > > wrote:
> >
> > Ah, this may be why it's worked for me -- smaller projects with
> > defined release cycles.
> >
> > Anyway, I never meant to imply that git == git flow. We will need
> > some sort of process, though, and the DeltaSpike one seems like a
> > good place to start.
> >
> > ___
> >
> > Kito D. Mann | @kito99 | Author, JSF in Action
> > Web Components, Polymer, JSF, PrimeFaces, Java EE training and
> > consulting
> > Virtua, Inc. | virtua.tech
> > JSFCentral.com | @jsfcentral | knowesis.io  -
> > fresh Web Components info
> > +1 203-998-0403 
> >
> > * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
> > 
> > * Listen to the Enterprise Java Newscast:
> http://enterprisejavanews.com
> >
> >
> > On Thu, Apr 20, 2017 at 8:02 AM, Mark Struberg  > > wrote:
> >
> > gitflow is pure pita ;)
> > It basically only works for companies where you have a single
> > manager who decides what goes in and what not.
> >
> > But GIT != gitflow. gitflow has nothing to do with the GIT scm
> > itself, but is just a fancy name for a development process with
> > an explicit build-branch and a build-master.
> >
> > +0 on moving to GIT.
> > SVN works good enough imo, but GIT ofc also would work.
> >
> > LIeGrue,
> > strub
> >
> > > Am 19.04.2017 um 12:57 schrieb Kito Mann  > >:
> > >
> > > +1
> > >
> > > Wha's wrong with GitFlow?
> > >
> > > ___
> > >
> > > Kito D. Mann | @kito99 | Author, JSF in Action
> > > Web Components, Polymer, JSF, PrimeFaces, Java EE training and
> > consulting
> > > Virtua, Inc. | virtua.tech
> > > JSFCentral.com | @jsfcentral | knowesis.io
> >  - fresh Web Components info
> > > +1 203-998-0403 
> > >
> > > * See me speak at the ng-conf April 5th-8th:
> http://bit.ly/2mw7HBj
> > > * Listen to the Enterprise Java Newscast:
> > http://enterprisejavanews.com
> > >
> > >
> > > On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann
> >  > > wrote:
> > > Hello
> > >
> > > I think the changes will be not so complicated. The deltaspike
> > pom looks nice :-)
> > > If someone talks about git-flow process i'm out.
> > >
> > > Regards
> > >
> > > Bernd
> > >
> > > On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe
> > > wrote:
> > > +1
> > >
> > > Change the release process is a pain, but I agree there are
> > some benefits moving to git.
> > >
> > > But when I see here:
> > >
> > > https://github.com/apache/myfaces
> > 
> > >
> > > It says:
> > >
> > > mirrored from git://git.apache.org/myfaces.git
> > 
> > >
> > > But I have never checked where that file is or how to change
> it.
> > >
> > > Looking in deltaspike, the svn repo only has the site (for the
> > CMS) and the source code lives on git. If that so, we still need
> > the svn, so I agree it is a good idea to move only some
> > subprojects to git.
> > >
> > > regards,
> > >
> > > Leonardo Uribe
> > >
> > >
> > >   Virus-free. www.avast.com 
> > >
> > > 2017-04-17 11:40 GMT-05:00 Grant Smith  > >:
> > > +1
> > >
> > > Couldn't agree more.
> > >
> > > Grant Smith - V.P. Information Technology
> > > Marathon Computer Systems, LLC.
> > >
> >   

[jira] [Commented] (TOBAGO-1751) Add META-tags to -tag

[Udo Schnurpfeil (JIRA)]

[ 
https://issues.apache.org/jira/browse/TOBAGO-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16103206#comment-16103206
 ] 

Udo Schnurpfeil commented on TOBAGO-1751:
-

I've seen WebSphere adds a jsf.js resource entry to the header. This has to be 
dropped, because Tobago brings its own tobago-jsf.js.

> Add META-tags to -tag
> ---
>
> Key: TOBAGO-1751
> URL: https://issues.apache.org/jira/browse/TOBAGO-1751
> Project: MyFaces Tobago
>  Issue Type: New Feature
>  Components: Core
>Reporter: Guido Dubois
>Assignee: Udo Schnurpfeil
>Priority: Minor
> Fix For: 4.0.0
>
>
> Is there a simple way to include META-tags to the  section of a 
> ?
> It would be nice to have a tag according to  or  file=""> for this.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TOBAGO-1751) Add META-tags to -tag

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/TOBAGO-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16103172#comment-16103172
 ] 

Hudson commented on TOBAGO-1751:


SUCCESS: Integrated in Jenkins build Tobago Trunk #962 (See 
[https://builds.apache.org/job/Tobago%20Trunk/962/])
TOBAGO-1751 Add META-tags to -tag
* add comment (hnoeth: [http://svn.apache.org/viewvc/?view=rev=1803172])
* (edit) 
tobago-trunk/tobago-core/src/main/java/org/apache/myfaces/tobago/internal/renderkit/renderer/PageRenderer.java


> Add META-tags to -tag
> ---
>
> Key: TOBAGO-1751
> URL: https://issues.apache.org/jira/browse/TOBAGO-1751
> Project: MyFaces Tobago
>  Issue Type: New Feature
>  Components: Core
>Reporter: Guido Dubois
>Assignee: Udo Schnurpfeil
>Priority: Minor
> Fix For: 4.0.0
>
>
> Is there a simple way to include META-tags to the  section of a 
> ?
> It would be nice to have a tag according to  or  file=""> for this.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Migrate all MyFaces projects to Git

[Udo Schnurpfeil]

Hi,

for Tobago I think, we can do it now!

Regards,

Udo

Am 27.07.17 um 13:03 schrieb Bernd Bohmann:
> Ok
> 
> we have some agreement about moving to git.
> Now we should define some time line.
> Any suggestions from the active subprojects?
> 
> Something like 
> 'I would like to move to git after blah blah release'
> 'I would like to move now'
> 'I would like to move in 2 weeks'
> or whatever
> 
> I can support the migration to git.
> 
> Regards 
> 
> Bernd
> 
> 
>  
> 
> On Thu, Apr 20, 2017 at 5:16 PM, Kito Mann  > wrote:
> 
> Ah, this may be why it's worked for me -- smaller projects with
> defined release cycles.
> 
> Anyway, I never meant to imply that git == git flow. We will need
> some sort of process, though, and the DeltaSpike one seems like a
> good place to start.
> 
> ___
> 
> Kito D. Mann | @kito99 | Author, JSF in Action
> Web Components, Polymer, JSF, PrimeFaces, Java EE training and
> consulting
> Virtua, Inc. | virtua.tech 
> JSFCentral.com | @jsfcentral | knowesis.io  -
> fresh Web Components info
> +1 203-998-0403 
> 
> * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
> 
> * Listen to the Enterprise Java Newscast: http://enterprisejavanews.com
> 
> 
> On Thu, Apr 20, 2017 at 8:02 AM, Mark Struberg  > wrote:
> 
> gitflow is pure pita ;)
> It basically only works for companies where you have a single
> manager who decides what goes in and what not.
> 
> But GIT != gitflow. gitflow has nothing to do with the GIT scm
> itself, but is just a fancy name for a development process with
> an explicit build-branch and a build-master.
> 
> +0 on moving to GIT.
> SVN works good enough imo, but GIT ofc also would work.
> 
> LIeGrue,
> strub
> 
> > Am 19.04.2017 um 12:57 schrieb Kito Mann  >:
> >
> > +1
> >
> > Wha's wrong with GitFlow?
> >
> > ___
> >
> > Kito D. Mann | @kito99 | Author, JSF in Action
> > Web Components, Polymer, JSF, PrimeFaces, Java EE training and
> consulting
> > Virtua, Inc. | virtua.tech
> > JSFCentral.com | @jsfcentral | knowesis.io
>  - fresh Web Components info
> > +1 203-998-0403 
> >
> > * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
> > * Listen to the Enterprise Java Newscast:
> http://enterprisejavanews.com
> >
> >
> > On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann
>  > wrote:
> > Hello
> >
> > I think the changes will be not so complicated. The deltaspike
> pom looks nice :-)
> > If someone talks about git-flow process i'm out.
> >
> > Regards
> >
> > Bernd
> >
> > On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe
> > wrote:
> > +1
> >
> > Change the release process is a pain, but I agree there are
> some benefits moving to git.
> >
> > But when I see here:
> >
> > https://github.com/apache/myfaces
> 
> >
> > It says:
> >
> > mirrored from git://git.apache.org/myfaces.git
> 
> >
> > But I have never checked where that file is or how to change it.
> >
> > Looking in deltaspike, the svn repo only has the site (for the
> CMS) and the source code lives on git. If that so, we still need
> the svn, so I agree it is a good idea to move only some
> subprojects to git.
> >
> > regards,
> >
> > Leonardo Uribe
> >
> >
> >   Virus-free. www.avast.com 
> >
> > 2017-04-17 11:40 GMT-05:00 Grant Smith  >:
> > +1
> >
> > Couldn't agree more.
> >
> > Grant Smith - V.P. Information Technology
> > Marathon Computer Systems, LLC.
> >
> > On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann
> >
> wrote:
> > From my side a big
> >
> > +1
> >
> > I'm still happy with subversion but for others the
> collaboration is easier and the project visibility a little bit
> better.
> 

[jira] [Commented] (MYFACES-4127) Unexpected exception thrown when FlowMap is injected on a RequestScoped bean

[Dora Rajappan (JIRA)]

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

Dora Rajappan commented on MYFACES-4127:


Could you please put and war and source for this scenario. I am getting the 
same exception if I made the bean to @Applicationscoped also!!!

> Unexpected exception thrown when FlowMap is injected on a RequestScoped bean
> 
>
> Key: MYFACES-4127
> URL: https://issues.apache.org/jira/browse/MYFACES-4127
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Eduardo Breijo
>Priority: Minor
>
> When @FlowMap is injected on a RequestScoped bean, and you try to use that 
> object (which should be null since we are not inside of a flow), an 
> unexpected exception is thrown. This was noted after JIRA issue: 
> https://issues.apache.org/jira/browse/MYFACES-4126
> Caused by: org.jboss.weld.exceptions.IllegalProductException: WELD-52: 
> Cannot return null from a non-dependent producer method: Producer for 
> Producer Method [Map] with qualifiers [@FlowMap @Any] 
> declared as [[UnbackedAnnotatedMethod] @Produces @FlowMap @ApplicationScoped 
> public 
> org.apache.myfaces.cdi.faces.ApplicationScopeObjectProducer.getFlowMap()] 
> declared on Managed Bean [class 
> org.apache.myfaces.cdi.faces.ApplicationScopeObjectProducer] with qualifiers 
> [@Any @Default]
>   at 
> org.apache.myfaces.cdi.faces.ApplicationScopeObjectProducer.getFlowMap(ApplicationScopeObjectProducer.java:73)
>   StackTrace:
>   at 
> org.jboss.weld.bean.AbstractProducerBean.checkReturnValue(AbstractProducerBean.java:136)
>   at [internal classes]
>   at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96)
>   at 
> org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:100)
>   at [internal classes]
>   at java.lang.String.valueOf(String.java:2994)
>   at java.lang.StringBuilder.append(StringBuilder.java:131)
>   at 
> com.ibm.ws.jsf23.fat.beans.ELImplicitObjectBean.execute(ELImplicitObjectBean.java:163)
> On Mojarra 2.3, we get a different exception which looks more appropriate.
> org.jboss.weld.contexts.ContextNotActiveException: WELD-001303: No active 
> contexts for scope type javax.faces.flow.FlowScoped
>   
> org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:623)
>   
> org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:89)
>   
> org.jboss.weld.bean.ContextualInstance.getIfExists(ContextualInstance.java:63)
>   
> org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:87)
>   
> org.jboss.weld.bean.proxy.ProxyMethodHandler.getInstance(ProxyMethodHandler.java:125)
>   
> org.jboss.weld.util.Map$1302817811$Proxy$_$$_WeldClientProxy.toString(Unknown 
> Source)
>   java.lang.String.valueOf(String.java:2994)
>   java.lang.StringBuilder.append(StringBuilder.java:131)
>   
> com.ibm.ws.jsf23.fat.beans.ELImplicitObjectBean.execute(ELImplicitObjectBean.java:163)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TOBAGO-1752) DeltaSpike WindowId doesn't work correctly with Tobago

[Udo Schnurpfeil (JIRA)]

[ 
https://issues.apache.org/jira/browse/TOBAGO-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16103073#comment-16103073
 ] 

Udo Schnurpfeil commented on TOBAGO-1752:
-

If tried to check the problem with the second click on the same link (or 
button). It seems the problem is not the link (or button). Same behavior with 
plain HTML:
{code}

  
http://localhost:8080/content/40-test/4000-button+link/x-link.xhtml; 
target="foo">Tobago


  

{code}

> DeltaSpike WindowId doesn't work correctly with Tobago
> --
>
> Key: TOBAGO-1752
> URL: https://issues.apache.org/jira/browse/TOBAGO-1752
> Project: MyFaces Tobago
>  Issue Type: Bug
>  Components: Core, Themes
>Affects Versions: 3.0.4
>Reporter: Udo Schnurpfeil
>Assignee: Udo Schnurpfeil
> Fix For: 3.0.5, 4.0.0
>
>
> Problem is, that CSP conflicts with code rendered by 
> {code:java}
> 
> {code}
> Solution: Tobago renders all the stuff, there is *no need* to use this tag.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Migrate all MyFaces projects to Git

[Bernd Bohmann]

Ok

we have some agreement about moving to git.
Now we should define some time line.
Any suggestions from the active subprojects?

Something like
'I would like to move to git after blah blah release'
'I would like to move now'
'I would like to move in 2 weeks'
or whatever

I can support the migration to git.

Regards

Bernd




On Thu, Apr 20, 2017 at 5:16 PM, Kito Mann  wrote:

> Ah, this may be why it's worked for me -- smaller projects with defined
> release cycles.
>
> Anyway, I never meant to imply that git == git flow. We will need some
> sort of process, though, and the DeltaSpike one seems like a good place to
> start.
>
> ___
>
> Kito D. Mann | @kito99 | Author, JSF in Action
> Web Components, Polymer, JSF, PrimeFaces, Java EE training and consulting
> Virtua, Inc. | virtua.tech
> JSFCentral.com | @jsfcentral | knowesis.io - fresh Web Components info
> +1 203-998-0403 <(203)%20998-0403>
>
> * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
> 
> * Listen to the Enterprise Java Newscast: http://enterprisejavanews.com
>
>
> On Thu, Apr 20, 2017 at 8:02 AM, Mark Struberg  wrote:
>
>> gitflow is pure pita ;)
>> It basically only works for companies where you have a single manager who
>> decides what goes in and what not.
>>
>> But GIT != gitflow. gitflow has nothing to do with the GIT scm itself,
>> but is just a fancy name for a development process with an explicit
>> build-branch and a build-master.
>>
>> +0 on moving to GIT.
>> SVN works good enough imo, but GIT ofc also would work.
>>
>> LIeGrue,
>> strub
>>
>> > Am 19.04.2017 um 12:57 schrieb Kito Mann :
>> >
>> > +1
>> >
>> > Wha's wrong with GitFlow?
>> >
>> > ___
>> >
>> > Kito D. Mann | @kito99 | Author, JSF in Action
>> > Web Components, Polymer, JSF, PrimeFaces, Java EE training and
>> consulting
>> > Virtua, Inc. | virtua.tech
>> > JSFCentral.com | @jsfcentral | knowesis.io - fresh Web Components info
>> > +1 203-998-0403
>> >
>> > * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
>> > * Listen to the Enterprise Java Newscast: http://enterprisejavanews.com
>> >
>> >
>> > On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann <
>> bernd.bohm...@googlemail.com> wrote:
>> > Hello
>> >
>> > I think the changes will be not so complicated. The deltaspike pom
>> looks nice :-)
>> > If someone talks about git-flow process i'm out.
>> >
>> > Regards
>> >
>> > Bernd
>> >
>> > On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe 
>> wrote:
>> > +1
>> >
>> > Change the release process is a pain, but I agree there are some
>> benefits moving to git.
>> >
>> > But when I see here:
>> >
>> > https://github.com/apache/myfaces
>> >
>> > It says:
>> >
>> > mirrored from git://git.apache.org/myfaces.git
>> >
>> > But I have never checked where that file is or how to change it.
>> >
>> > Looking in deltaspike, the svn repo only has the site (for the CMS) and
>> the source code lives on git. If that so, we still need the svn, so I agree
>> it is a good idea to move only some subprojects to git.
>> >
>> > regards,
>> >
>> > Leonardo Uribe
>> >
>> >
>> >   Virus-free. www.avast.com
>> >
>> > 2017-04-17 11:40 GMT-05:00 Grant Smith :
>> > +1
>> >
>> > Couldn't agree more.
>> >
>> > Grant Smith - V.P. Information Technology
>> > Marathon Computer Systems, LLC.
>> >
>> > On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann <
>> bernd.bohm...@atanion.com> wrote:
>> > From my side a big
>> >
>> > +1
>> >
>> > I'm still happy with subversion but for others the collaboration is
>> easier and the project visibility a little bit better.
>> >
>> > Regards
>> >
>> > Bernd
>> >
>> > Am 13.04.2017 09:41 schrieb "Thomas Andraschko" <
>> andraschko.tho...@gmail.com>:
>> > +0
>> > I usually just work on MF core and there it doesn't make much
>> difference.
>> >
>> > 2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst :
>> > Hi,
>> >
>> > have you ever thought of migrating to Git? I see more and more Apache
>> > projects moving. In the past SVN or Git didn't make any difference to me
>> > but now I'm thinking that as an Open Source project you need to be
>> > present on GitHub to get Pull Requests from the community. It's much
>> > more fun contributing there than attaching patches to JIRA issues.
>> >
>> > We could start with Trinidad and Tobago to avoid conflicts with the 2.3
>> > release.
>> >
>> > Cheers
>> > Dennis
>> >
>> >
>> >
>> >
>> >
>>
>>
>

[jira] [Commented] (MYFACES-4127) Unexpected exception thrown when FlowMap is injected on a RequestScoped bean

[Dora Rajappan (JIRA)]

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

Dora Rajappan commented on MYFACES-4127:


Caused by: org.jboss.weld.exceptions.IllegalProductException: WELD-52: 
Cannot return null from a non-dependent producer method:  Producer for Producer 
Method [Map] with qualifiers [@FlowMap @Any] declared as 
[[UnbackedAnnotatedMethod] @Produces @FlowMap @ApplicationScoped public 
org.apache.myfaces.cdi.faces.ApplicationScopeObjectProducer.getFlowMap()] 
declared on Managed Bean [class 
org.apache.myfaces.cdi.faces.ApplicationScopeObjectProducer] with qualifiers 
[@Any @Default]
at 
org.jboss.weld.bean.AbstractProducerBean.checkReturnValue(AbstractProducerBean.java:136)
at 
org.jboss.weld.bean.AbstractProducerBean.create(AbstractProducerBean.java:184)
at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:94)
at 
org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:98)
at 
org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:99)
at 
org.jboss.weld.proxies.Map$1822649053$Proxy$_$$_WeldClientProxy.isEmpty(Unknown 
Source)
at guess.ConfigItems.postConstruct(ConfigItems.java:29)
Got the above exception for the said scenario. Trying to resolve.

> Unexpected exception thrown when FlowMap is injected on a RequestScoped bean
> 
>
> Key: MYFACES-4127
> URL: https://issues.apache.org/jira/browse/MYFACES-4127
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Eduardo Breijo
>Priority: Minor
>
> When @FlowMap is injected on a RequestScoped bean, and you try to use that 
> object (which should be null since we are not inside of a flow), an 
> unexpected exception is thrown. This was noted after JIRA issue: 
> https://issues.apache.org/jira/browse/MYFACES-4126
> Caused by: org.jboss.weld.exceptions.IllegalProductException: WELD-52: 
> Cannot return null from a non-dependent producer method: Producer for 
> Producer Method [Map] with qualifiers [@FlowMap @Any] 
> declared as [[UnbackedAnnotatedMethod] @Produces @FlowMap @ApplicationScoped 
> public 
> org.apache.myfaces.cdi.faces.ApplicationScopeObjectProducer.getFlowMap()] 
> declared on Managed Bean [class 
> org.apache.myfaces.cdi.faces.ApplicationScopeObjectProducer] with qualifiers 
> [@Any @Default]
>   at 
> org.apache.myfaces.cdi.faces.ApplicationScopeObjectProducer.getFlowMap(ApplicationScopeObjectProducer.java:73)
>   StackTrace:
>   at 
> org.jboss.weld.bean.AbstractProducerBean.checkReturnValue(AbstractProducerBean.java:136)
>   at [internal classes]
>   at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96)
>   at 
> org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:100)
>   at [internal classes]
>   at java.lang.String.valueOf(String.java:2994)
>   at java.lang.StringBuilder.append(StringBuilder.java:131)
>   at 
> com.ibm.ws.jsf23.fat.beans.ELImplicitObjectBean.execute(ELImplicitObjectBean.java:163)
> On Mojarra 2.3, we get a different exception which looks more appropriate.
> org.jboss.weld.contexts.ContextNotActiveException: WELD-001303: No active 
> contexts for scope type javax.faces.flow.FlowScoped
>   
> org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:623)
>   
> org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:89)
>   
> org.jboss.weld.bean.ContextualInstance.getIfExists(ContextualInstance.java:63)
>   
> org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:87)
>   
> org.jboss.weld.bean.proxy.ProxyMethodHandler.getInstance(ProxyMethodHandler.java:125)
>   
> org.jboss.weld.util.Map$1302817811$Proxy$_$$_WeldClientProxy.toString(Unknown 
> Source)
>   java.lang.String.valueOf(String.java:2994)
>   java.lang.StringBuilder.append(StringBuilder.java:131)
>   
> com.ibm.ws.jsf23.fat.beans.ELImplicitObjectBean.execute(ELImplicitObjectBean.java:163)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TOBAGO-1771) Not escaping quot " and slash /

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/TOBAGO-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16103017#comment-16103017
 ] 

Hudson commented on TOBAGO-1771:


SUCCESS: Integrated in Jenkins build Tobago Trunk #961 (See 
[https://builds.apache.org/job/Tobago%20Trunk/961/])
TOBAGO-1771: Not escaping quot " and slash / (lofwyr: 
[http://svn.apache.org/viewvc/?view=rev=1803147])
* (edit) 
tobago-trunk/tobago-core/src/main/java/org/apache/myfaces/tobago/internal/util/HtmlWriterHelper.java
* (edit) 
tobago-trunk/tobago-core/src/test/java/org/apache/myfaces/tobago/webapp/TobagoResponseWriterUnitTest.java


> Not escaping quot " and slash /
> ---
>
> Key: TOBAGO-1771
> URL: https://issues.apache.org/jira/browse/TOBAGO-1771
> Project: MyFaces Tobago
>  Issue Type: Improvement
>  Components: Core
>Reporter: Udo Schnurpfeil
>Assignee: Udo Schnurpfeil
>Priority: Trivial
> Fix For: 4.0.0
>
>
> We should not escaping quot " and slash / here, because we not really need 
> that in our case.
> It makes the HTML code better readable and shorter. There are many 
> occurrences of quot, because of JSON.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (TOBAGO-1771) Not escaping quot " and slash /

[Udo Schnurpfeil (JIRA)]

Udo Schnurpfeil created TOBAGO-1771:
---

 Summary: Not escaping quot " and slash /
 Key: TOBAGO-1771
 URL: https://issues.apache.org/jira/browse/TOBAGO-1771
 Project: MyFaces Tobago
  Issue Type: Improvement
  Components: Core
Reporter: Udo Schnurpfeil
Assignee: Udo Schnurpfeil
Priority: Trivial


We should not escaping quot " and slash / here, because we not really need that 
in our case.
It makes the HTML code better readable and shorter. There are many occurrences 
of quot, because of JSON.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (TOBAGO-1769) Ajax doesn't work for text containing non-printable control characters

[Udo Schnurpfeil (JIRA)]

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

Udo Schnurpfeil resolved TOBAGO-1769.
-
Resolution: Fixed

> Ajax doesn't work for text containing non-printable control characters
> --
>
> Key: TOBAGO-1769
> URL: https://issues.apache.org/jira/browse/TOBAGO-1769
> Project: MyFaces Tobago
>  Issue Type: Bug
>Affects Versions: 3.0.4
>Reporter: Henning Noeth
>Assignee: Udo Schnurpfeil
> Fix For: 3.0.5, 4.0.0
>
>
> A text with a control character.
> {code:java}private String controlFoo = "Deimoyyy\u001Azzz";
> public String getControlFoo() {
>   return controlFoo;
> }{code}
> {code:xml} value="#{controller.controlFoo}"/>
> 
>   
> {code}
> The page is rendered properly if execute a full page reload.
> If pressing the ajax button, this 'ajaxOut' component is not rendered. You 
> can find the control character in the ajax response.
> Please note, the error is not only for the 'value' attribute. It also appears 
> for the 'tip' attribute (and probably for all other string attributes).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)