September 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-2006) Add @PreMatching to the CORS Filter

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2006?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2006. ---------------------------------- Resolution: Done > Add @PreMatching to the CORS Filter > ----------------------------------- > > Key: FORGE-2006 > URL: https://issues.jboss.org/browse/FORGE-2006 > Project: Forge > Issue Type: Enhancement > Components: Java EE > Affects Versions: 2.9.2.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.9.3.Final > > > According to http://www.developerscrappad.com/1781/java/java-ee/rest-jax-rs/java-ee-7-..., this is needed to indicate that such filter should be applied globally on all resources in the application before the actual resource matching occurs. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2006) Add @PreMatching to the CORS Filter

by George Gastaldi (JIRA)

George Gastaldi created FORGE-2006: -------------------------------------- Summary: Add @PreMatching to the CORS Filter Key: FORGE-2006 URL: https://issues.jboss.org/browse/FORGE-2006 Project: Forge Issue Type: Enhancement Components: Java EE Affects Versions: 2.9.2.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.9.3.Final According to http://www.developerscrappad.com/1781/java/java-ee/rest-jax-rs/java-ee-7-..., this is needed to indicate that such filter should be applied globally on all resources in the application before the actual resource matching occurs. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2005) Display the project build errors after a command is executed when in a project context

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2005?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2005. ---------------------------------- Resolution: Done > Display the project build errors after a command is executed when in a project context > -------------------------------------------------------------------------------------- > > Key: FORGE-2005 > URL: https://issues.jboss.org/browse/FORGE-2005 > Project: Forge > Issue Type: Feature Request > Components: Build Tools - Maven, Projects, UI - API > Affects Versions: 2.9.2.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.9.3.Final > > > More details in JBIDE-17492 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2005) Display the project build errors after a command is executed when in a project context

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2005?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-2005: ----------------------------------- Summary: Display the project build errors after a command is executed when in a project context (was: Display the project build errors when in a project context) > Display the project build errors after a command is executed when in a project context > -------------------------------------------------------------------------------------- > > Key: FORGE-2005 > URL: https://issues.jboss.org/browse/FORGE-2005 > Project: Forge > Issue Type: Feature Request > Components: Build Tools - Maven, Projects, UI - API > Affects Versions: 2.9.2.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.9.3.Final > > > More details in JBIDE-17492 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2005) Display the project build errors when in a project context

by George Gastaldi (JIRA)

George Gastaldi created FORGE-2005: -------------------------------------- Summary: Display the project build errors when in a project context Key: FORGE-2005 URL: https://issues.jboss.org/browse/FORGE-2005 Project: Forge Issue Type: Feature Request Components: Build Tools - Maven, Projects, UI - API Affects Versions: 2.9.2.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.9.3.Final More details in JBIDE-17492 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-33) Accessor of type boolean starting with 'is' are not considered accessor

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/ROASTER-33?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated ROASTER-33: ------------------------------------- Description: If I parse a class with a boolean attribute with {{is/set}} instead of {{get/set}}, the accessor is not recognized. I think it's because of the {{AbstractJavaSourceMemberHolder.extractPropertyName}} method : {code} private String extractPropertyName(Method<O, ?> method) { if (method.getName().matches("^[gs]et.+$")) { return Strings.uncapitalize(method.getName().substring(3)); } return null; } {code} I'm attaching a test case that reproduces it if you want was: If I parse a class with a boolean attribute with is/set instead of get/set, the accessor is not recognizes. I think it's because of the {{AbstractJavaSourceMemberHolder.extractPropertyName}} method : {code} private String extractPropertyName(Method<O, ?> method) { if (method.getName().matches("^[gs]et.+$")) { return Strings.uncapitalize(method.getName().substring(3)); } return null; } {code} I'm attaching a test case that reproduces it if you want > Accessor of type boolean starting with 'is' are not considered accessor > ----------------------------------------------------------------------- > > Key: ROASTER-33 > URL: https://issues.jboss.org/browse/ROASTER-33 > Project: Roaster > Issue Type: Bug > Affects Versions: 2.7.1.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > Attachments: IsTest.java > > > If I parse a class with a boolean attribute with {{is/set}} instead of {{get/set}}, the accessor is not recognized. I think it's because of the {{AbstractJavaSourceMemberHolder.extractPropertyName}} method : > {code} > private String extractPropertyName(Method<O, ?> method) > { > if (method.getName().matches("^[gs]et.+$")) > { > return Strings.uncapitalize(method.getName().substring(3)); > } > return null; > } > {code} > I'm attaching a test case that reproduces it if you want -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-33) Accessor of type boolean starting with 'is' are not considered accessor

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/ROASTER-33?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated ROASTER-33: ------------------------------------- Attachment: IsTest.java > Accessor of type boolean starting with 'is' are not considered accessor > ----------------------------------------------------------------------- > > Key: ROASTER-33 > URL: https://issues.jboss.org/browse/ROASTER-33 > Project: Roaster > Issue Type: Bug > Affects Versions: 2.7.1.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > Attachments: IsTest.java > > > If I parse a class with a boolean attribute with is/set instead of get/set, the accessor is not recognizes. I think it's because of the {{AbstractJavaSourceMemberHolder.extractPropertyName}} method : > {code} > private String extractPropertyName(Method<O, ?> method) > { > if (method.getName().matches("^[gs]et.+$")) > { > return Strings.uncapitalize(method.getName().substring(3)); > } > return null; > } > {code} > I'm attaching a test case that reproduces it if you want -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-33) Accessor of type boolean starting with 'is' are not considered accessor

by Antonio Goncalves (JIRA)

Antonio Goncalves created ROASTER-33: ---------------------------------------- Summary: Accessor of type boolean starting with 'is' are not considered accessor Key: ROASTER-33 URL: https://issues.jboss.org/browse/ROASTER-33 Project: Roaster Issue Type: Bug Affects Versions: 2.7.1.Final Reporter: Antonio Goncalves Fix For: 2.x Future If I parse a class with a boolean attribute with is/set instead of get/set, the accessor is not recognizes. I think it's because of the {{AbstractJavaSourceMemberHolder.extractPropertyName}} method : {code} private String extractPropertyName(Method<O, ?> method) { if (method.getName().matches("^[gs]et.+$")) { return Strings.uncapitalize(method.getName().substring(3)); } return null; } {code} I'm attaching a test case that reproduces it if you want -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2004) UIContext.getSelection() should return a UISelection object

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2004?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2004. ---------------------------------- Resolution: Done > UIContext.getSelection() should return a UISelection object > ----------------------------------------------------------- > > Key: FORGE-2004 > URL: https://issues.jboss.org/browse/FORGE-2004 > Project: Forge > Issue Type: Enhancement > Components: UI - API > Affects Versions: 2.9.2.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: api-change > Fix For: 2.9.3.Final > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2004) UIContext.getSelection() should return a UISelection object

by George Gastaldi (JIRA)

George Gastaldi created FORGE-2004: -------------------------------------- Summary: UIContext.getSelection() should return a UISelection object Key: FORGE-2004 URL: https://issues.jboss.org/browse/FORGE-2004 Project: Forge Issue Type: Enhancement Components: UI - API Affects Versions: 2.9.2.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.9.3.Final -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues September 2014