April 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-11438) Length import is not correct when using AS71 and HB4 seam generating entity

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11438?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-11438: ----------------------------------- Fix Version/s: LATER (was: 4.0.x) > Length import is not correct when using AS71 and HB4 seam generating entity > ----------------------------------------------------------------------------- > > Key: JBIDE-11438 > URL: https://issues.jboss.org/browse/JBIDE-11438 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate, seam2 > Affects Versions: 3.3.0.Beta2 > Environment: JBDS 5.0, Beta2, L64,HSQLDB 1.8 > Reporter: Jiri Peterka > Assignee: Koen Aers > Fix For: LATER > > Attachments: length-annotation.png > > > While generating entities (HB40,AS71), Length should be imported from: > import org.hibernate.validator.constraints.Length; > but it's imported non existing package: > import org.hibernate.validator.Length; > @Length(max = 200) > public String getSurname() { > return this.surname; > } > public void setSurname(String surname) { > this.surname = surname; > } > Generated classes should lib according to defined runtime I guess -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13237) Use "suggested-value" from faces-config.xml for JSF attribute suggestion

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13237?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-13237: ----------------------------------- Fix Version/s: LATER (was: 4.2.x) > Use "suggested-value" from faces-config.xml for JSF attribute suggestion > ------------------------------------------------------------------------ > > Key: JBIDE-13237 > URL: https://issues.jboss.org/browse/JBIDE-13237 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsf > Reporter: Paul Dijou > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: LATER > > > After reading [this wiki entry|https://community.jboss.org/wiki/NewKBPlug-inAndCodeAssistInJBossTo...], it looks like one property of the faces-config.xml isn't used so far, it's the *"suggested-value"* (see http://horstmann.com/corejsf/faces-config.html#suggested-value ). Its description is quite small and I couldn't find any real documentation about it. But we can read: "This value is advisory only and is intended for tools", and JBoss Tools is... a tool, right? :-) > So it would be great that JBoss Tools check the presence of such a "suggested-value" inside faces-config.xml and population an "enumeration" proposal type for the corresponding attribute. > Since "suggested-value" is a string, it cannot support natively a list of suggestions, so, right now, RichFaces is using "," as a separator. Which mean having: > {code} > <property-name>severity</property-name> > <property-class>java.lang.String</property-class> > <suggested-value>success,info,warning,important,inverse</suggested-value> > {code} > Should be equivalent to: > {code} > <attribute name="severity"> > <proposal type="enumeration"> > <param value="success" /> > <param value="info" /> > <param value="warning" /> > <param value="important" /> > <param value="inverse" /> > </proposal> > </attribute> > {code} > What do you think? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-3515) Actions that modifies resources (Add JSF/Custom Capabilities) should let user review the changes as Java Code refactoring and clean-up do

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-3515?page=com.atlassian.jira.plugin... ] Alexey Kazakov updated JBIDE-3515: ---------------------------------- Priority: Minor (was: Major) > Actions that modifies resources (Add JSF/Custom Capabilities) should let user review the changes as Java Code refactoring and clean-up do > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-3515 > URL: https://issues.jboss.org/browse/JBIDE-3515 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsf > Affects Versions: 3.0.0.cr1 > Reporter: Denis Golovin > Assignee: Daniel Azarov > Priority: Minor > Fix For: 4.2.x > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-3515) Actions that modifies resources (Add JSF/Custom Capabilities) should let user review the changes as Java Code refactoring and clean-up do

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-3515?page=com.atlassian.jira.plugin... ] Alexey Kazakov updated JBIDE-3515: ---------------------------------- Fix Version/s: LATER (was: 4.2.x) > Actions that modifies resources (Add JSF/Custom Capabilities) should let user review the changes as Java Code refactoring and clean-up do > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-3515 > URL: https://issues.jboss.org/browse/JBIDE-3515 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsf > Affects Versions: 3.0.0.cr1 > Reporter: Denis Golovin > Assignee: Daniel Azarov > Priority: Minor > Fix For: LATER > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-5435) JSF Resource identifier validator

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-5435?page=com.atlassian.jira.plugin... ] Alexey Kazakov updated JBIDE-5435: ---------------------------------- Fix Version/s: LATER (was: 4.2.x) > JSF Resource identifier validator > --------------------------------- > > Key: JBIDE-5435 > URL: https://issues.jboss.org/browse/JBIDE-5435 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsf > Reporter: Denis Golovin > Assignee: Alexey Kazakov > Labels: jsf2, new_and_noteworthy > Fix For: LATER > > > Validator should check: > 1. resource references in pages: xhtml, jsp, jspxand etc. > 2. resource names defined in current project or related projects > 3. resource names defined in jars > It should perform verification for JSF2 resources as it is defined in spec's "2.6.1.3 Resource Identifiers" chapter: "<resourceIdentifier> consists of several segments, specified as follows. > [localePrefix/][libraryName/][libraryVersion/]resourceName[/resourceVersion] > The run-time must enforce the following rules to consider a <resourceIdentifier>s valid. A <resourceIdentifier> that does not follow these rules must not be considered valid and must be ignored silently. > * Every character in a resource identifier must be a valid character suitable for use in a string passed to the constructor of java.io.File that takes a single String argument. > * Segments in square brackets [] are optional. > * The segments must appear in the order shown above. > * If libraryVersion is present, it must be preceded by libraryName. > * If libraryVersion is present, any leaf files under libraryName must be ignored. > * If resourceVersion is present, it must be preceded by resourceName. > * There must be a '/' between adjacent segments in a <resourceIdentifier> > * If libraryVersion or resourceVersion are present, both must be a '_' separated list of integers, neither starting nor ending with '_' > * If resourceVersion is present, it must be a version number in the same format as libraryVersion. An optional "file extension" may be used with the resourceVersion. If "file extension" is used, a "." character, followed by a "file extension" must be appended to the version number. See the following table for an example." -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-5435) JSF Resource identifier validator

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-5435?page=com.atlassian.jira.plugin... ] Alexey Kazakov reassigned JBIDE-5435: ------------------------------------- Assignee: Alexey Kazakov (was: Denis Golovin) > JSF Resource identifier validator > --------------------------------- > > Key: JBIDE-5435 > URL: https://issues.jboss.org/browse/JBIDE-5435 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsf > Reporter: Denis Golovin > Assignee: Alexey Kazakov > Labels: jsf2, new_and_noteworthy > Fix For: 4.2.x > > > Validator should check: > 1. resource references in pages: xhtml, jsp, jspxand etc. > 2. resource names defined in current project or related projects > 3. resource names defined in jars > It should perform verification for JSF2 resources as it is defined in spec's "2.6.1.3 Resource Identifiers" chapter: "<resourceIdentifier> consists of several segments, specified as follows. > [localePrefix/][libraryName/][libraryVersion/]resourceName[/resourceVersion] > The run-time must enforce the following rules to consider a <resourceIdentifier>s valid. A <resourceIdentifier> that does not follow these rules must not be considered valid and must be ignored silently. > * Every character in a resource identifier must be a valid character suitable for use in a string passed to the constructor of java.io.File that takes a single String argument. > * Segments in square brackets [] are optional. > * The segments must appear in the order shown above. > * If libraryVersion is present, it must be preceded by libraryName. > * If libraryVersion is present, any leaf files under libraryName must be ignored. > * If resourceVersion is present, it must be preceded by resourceName. > * There must be a '/' between adjacent segments in a <resourceIdentifier> > * If libraryVersion or resourceVersion are present, both must be a '_' separated list of integers, neither starting nor ending with '_' > * If resourceVersion is present, it must be a version number in the same format as libraryVersion. An optional "file extension" may be used with the resourceVersion. If "file extension" is used, a "." character, followed by a "file extension" must be appended to the version number. See the following table for an example." -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14699) New JSF Project Wizard layout problems

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14699?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-14699: ----------------------------------- Priority: Minor (was: Major) > New JSF Project Wizard layout problems > -------------------------------------- > > Key: JBIDE-14699 > URL: https://issues.jboss.org/browse/JBIDE-14699 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.1.0.Beta1 > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Priority: Minor > Fix For: 4.2.x > > Attachments: ServletVersion.png > > > 1. Left and right margins should be the same > 2. Combo boxes should have visible bottom line > See screenshot. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-3515) Actions that modifies resources (Add JSF/Custom Capabilities) should let user review the changes as Java Code refactoring and clean-up do

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-3515?page=com.atlassian.jira.plugin... ] Alexey Kazakov reassigned JBIDE-3515: ------------------------------------- Assignee: Daniel Azarov (was: Denis Golovin) > Actions that modifies resources (Add JSF/Custom Capabilities) should let user review the changes as Java Code refactoring and clean-up do > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-3515 > URL: https://issues.jboss.org/browse/JBIDE-3515 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsf > Affects Versions: 3.0.0.cr1 > Reporter: Denis Golovin > Assignee: Daniel Azarov > Fix For: 4.2.x > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16386) Quick fix which offers to disable Facelet HTML Validator

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16386?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-16386: ----------------------------------- Priority: Minor (was: Major) > Quick fix which offers to disable Facelet HTML Validator > -------------------------------------------------------- > > Key: JBIDE-16386 > URL: https://issues.jboss.org/browse/JBIDE-16386 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsf > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Priority: Minor > Labels: new_and_noteworthy > Fix For: 4.2.x > > > Facelet HTML Validator causes many false errors and we disabled it for projects with KB nature. Lets make a quick fix which offers to disable Facelet HTML Validator for any project. > Actually we already have such a quick fix - DisableFaceletHTMLValidatorMarkerResolution > we just need to make it visible for all kind of problems with validator_id - org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17176) Unable to browse and select PortletBridge runtime liberaries in JPP 6

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17176?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-17176: ----------------------------------- Component/s: (was: jsf) > Unable to browse and select PortletBridge runtime liberaries in JPP 6 > --------------------------------------------------------------------- > > Key: JBIDE-17176 > URL: https://issues.jboss.org/browse/JBIDE-17176 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein > Affects Versions: 4.1.2.Final > Reporter: abhishek vijra > Assignee: Snjezana Peco > > For Jboss Portal Platform . If one uses Jboss Tools to built portlet application . In Jboss Tools portlet wizard it is impossible to select the PortletBridge Runtime Liberaries -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2014