[JBoss JIRA] (JBIDE-12847) VPE throws StackOverflowError and visual part is blank
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12847?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-12847:
---------------------------------------
Patch looks good for me. Ran local build without errors.
> VPE throws StackOverflowError and visual part is blank
> ------------------------------------------------------
>
> Key: JBIDE-12847
> URL: https://issues.jboss.org/browse/JBIDE-12847
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Visual Page Editor core
> Reporter: Yahor Radtsevich
> Assignee: Yahor Radtsevich
> Labels: respin-b
> Fix For: 3.3.2
>
> Attachments: JBIDE-12847.diff, screenshot.png
>
>
> # Create new RichFaces project from JBoss Central View
> # Open richfaces-webapp/src/main/webapp/WEB-INF/templates/mobile.xhtml in VPE
> *Result:*
> VPE is blank:
> !screenshot.png|thumbnail!
> {code}
> java.lang.StackOverflowError
> at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556)
> at java.util.regex.Pattern$Loop.match(Pattern.java:4683)
> at java.util.regex.Pattern$GroupTail.match(Pattern.java:4615)
> at java.util.regex.Pattern$BranchConn.match(Pattern.java:4466)
> at java.util.regex.Pattern$CharProperty.match(Pattern.java:3694)
> at java.util.regex.Pattern$Branch.match(Pattern.java:4502)
> {code}
--
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
13 years, 6 months
[JBoss JIRA] (JBIDE-13254) In Seam 2.3 seam-gen generated project imported in JBDS, EL completion for Seam Messages doesn't work
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13254?page=com.atlassian.jira.plugi... ]
Alexey Kazakov edited comment on JBIDE-13254 at 1/10/13 4:42 PM:
-----------------------------------------------------------------
Actually code assist for Seam Messages doesn't require a dynamic web project.
Seam message bundles should (AFAIK) be in project class path.
But in seam-gen generated project all messages-*.properties files are placed in <project>/resources folder which is not a java source folder.
They are copied to {code}${war.dir}/WEB-INF/classes{code} by ant script. Code assist start working as soon as you copy these files to any java source folder.
But anyway some features can be disabled (some validation, code completion, navigation) until you convert the project to a faceted project (Project properties->Project Facets) and install JSF and Seam facets there. Seam facets actually is not required since you have seam support enabled but installing Seam facet you will enable JBoss Tools Knowledge Base support too. So if you want to have all the features enabled you need to install JSF facet + either install Seam facet or enable JBoss Tools Knowledge Base support (Project Properties->JBoss Tools Knowledge Base).
The following files will be updated/created:
<project>/.project
<project>/.classpath
<project>/.settings/*
But again, for Seam *code assist* you don't need it (some seam *validation* does require a dynamic web project. see JBIDE-13242). All you need is a properly configured java project with enabled seam support. These facets are required for JSF code assist/validation/navigation.
was (Author: akazakov):
Actually code assist for Seam Messages doesn't require a dynamic web project.
Seam message bundles should (AFAIK) be in project class path.
But in seam-gen generated project all messages-*.properties files are placed in <project>/resources folder which is not a java source folder.
They are copied to {code}${war.dir}/WEB-INF/classes{code} by ant script. Code assist start working as soon as you copy these files to any java source folder.
But anyway some features can be disabled (some validation, code completion, navigation) until you convert the project to a faceted project (Project properties->Project Facets) and install JSF and Seam facets there. Seam facets actually is not required since you have seam support enabled but installing Seam facet you will enable JBoss Tools Knowledge Base support too. So if you want to have all the features enabled you need to install JSF facet + either install Seam facet or enable JBoss Tools Knowledge Base support (Project Properties->JBoss Tools Knowledge Base).
The following files will be updated/created:
<project>/.project
<project>/.classpath
<project>/.settings/*
But again, for Seam code assist you don't need it. All you need is a properly configured java project with enabled seam support. These facets are required for JSF code assist/validation/navigation.
> In Seam 2.3 seam-gen generated project imported in JBDS, EL completion for Seam Messages doesn't work
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13254
> URL: https://issues.jboss.org/browse/JBIDE-13254
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Seam 2, UpStream
> Affects Versions: 3.3.1, 4.0.0.Beta2
> Environment: WFK 2.1.0.CR2 Seam.2.3.0.Final-redhat-1, JBDS 5.0.1.GA, JBDS 6.0.0.Beta2a
> Reporter: Ron Šmeral
> Assignee: Alexey Kazakov
> Fix For: 4.1.x
>
>
> After importing a Seam 2.3 seam-gen generated project in JBDS, the EL completion for Seam Messages doesn't work.
> This works OK for a Seam project created in JBDS and for a Maven project imported to JBDS.
>
> Actual results:
> Even though the "messages" component is suggested, no actual messages from the properties files are suggested. A warning is shown for e.g #{messages['org.jboss.seam.NotLoggedIn']}.
> Expected results:
> Messages from messages_xx.properties should be suggested without warnings.
--
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
13 years, 6 months
[JBoss JIRA] (JBIDE-13242) Seam 2.3: seam-gen generated project, JBDS reports missing files referenced from view-id in pages.xml
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13242?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-13242:
----------------------------------------
The problem is that seam-gen project is not a dynamic web project. So JBoss Tools cannot recognize <project>/view as a webroot folder.
See https://issues.jboss.org/browse/JBIDE-13254?focusedCommentId=12744574&pag...
But you cannot get this false validation problem in a fresh generated project since WST (Eclipse Web Tools) validation is not enabled there. Seam validation is an extension of WST validation so it won't work if WST validation disabled. You probably enabled JBoss Tools Knowledge Base support after importing the project (you will be asked to do it when opening any xhtml file for such a project). JBT KB enables WST validation.
> Seam 2.3: seam-gen generated project, JBDS reports missing files referenced from view-id in pages.xml
> -----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13242
> URL: https://issues.jboss.org/browse/JBIDE-13242
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Seam 2
> Affects Versions: 4.0.0.Beta2
> Environment: Seam.2.3.0, JBDS 5.0.1.GA or JBDS 6.0.0.Beta2a
> Reporter: Marek Novotny
> Assignee: Alexey Kazakov
> Fix For: 4.1.0.Alpha1
>
>
> After importing and building a Seam 2.3 seam-gen generated project in JBDS, it reports missing files referenced from view-id in pages.xml and in somEntity.page.xml files.
> This works OK for a Seam project created in JBDS and for a Maven project imported to JBDS.
> How reproducible:
> Import a seam-gen generated EAR project, check pages.xml.
> Steps to Reproduce:
> 1. Create a seam-gen EAR project.
> 2. Import into JBDS.
> 3. Open pages.xml, make a change (to trigger build).
>
> Actual results:
> On lines referencing a view-id, like
> <redirect view-id="/home.xhtml"/>
> JBDS shows an error saying:
> Cannot find target resource: "/home.xhtml"
--
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
13 years, 6 months
[JBoss JIRA] (JBIDE-13242) Seam 2.3: seam-gen generated project, JBDS reports missing files referenced from view-id in pages.xml
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13242?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-13242:
-----------------------------------
Component/s: UpStream
> Seam 2.3: seam-gen generated project, JBDS reports missing files referenced from view-id in pages.xml
> -----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13242
> URL: https://issues.jboss.org/browse/JBIDE-13242
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Seam 2, UpStream
> Affects Versions: 4.0.0.Beta2
> Environment: Seam.2.3.0, JBDS 5.0.1.GA or JBDS 6.0.0.Beta2a
> Reporter: Marek Novotny
> Assignee: Alexey Kazakov
> Fix For: 4.1.0.Alpha1
>
>
> After importing and building a Seam 2.3 seam-gen generated project in JBDS, it reports missing files referenced from view-id in pages.xml and in somEntity.page.xml files.
> This works OK for a Seam project created in JBDS and for a Maven project imported to JBDS.
> How reproducible:
> Import a seam-gen generated EAR project, check pages.xml.
> Steps to Reproduce:
> 1. Create a seam-gen EAR project.
> 2. Import into JBDS.
> 3. Open pages.xml, make a change (to trigger build).
>
> Actual results:
> On lines referencing a view-id, like
> <redirect view-id="/home.xhtml"/>
> JBDS shows an error saying:
> Cannot find target resource: "/home.xhtml"
--
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
13 years, 6 months
[JBoss JIRA] (JBIDE-13351) Dialogs look and fill problems
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13351?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-13351:
----------------------------------
Description:
Follow
1. New->Other->JBoss Tools->Configure MavenRepositories
ConfigureMavenRepositoriesWizard.java
Wizard banner has wrong high less than 66 pixels
!ConfigureMavenRepositories.png!
2. Window->Preferences, JBoss Tools->Remote Repositories, button "Add..."
EditNexusRepositoryDialog.java
Dialog should have a banner:
!NewRepositoryDialog.png!
3. Window->Preferences, JBoss Tools->JBoss Maven Integration, button "Configure Maven Repositories"
Dialog should have a not empty banner:
!ConfigureMavenRepositories2.png!
4. Window->Preferences, JBoss Tools->JBoss ESB Runtimes, button "Add". BTW it should be "Add..."
Dialog should have a not empty banner:
!NewJBossESBRuntime.png!
5.Window->Preferences, JBoss Tools->JBoss Runtime Detection, button "Download..."
Dialog should have a not empty banner:
!DownloadRuntimes.png!
6. Window->Preferences, JBoss Tools->Web->Custom Capabilities, buttons "Add" (button should be "Add...")
Dialogs should have a not default bunner:
!AddCapability.png!
!AddLibraryReference.png!
7. Window->Preferences, JBoss Tools->Web->Editors->Visual Page Editor, tab Visual Templates, buttons "Add..." and "Import..."
Dialogs should have a not default bunner:
!UserSpecifiedTagTemplate.png!
!ImportUserSpecifiedTagTemplates.png!
8. Window->Preferences, JBoss Tools->Web->Expression Language->Variables, button "Add" (button should be "Add...")
Dialog should have a not default bunner:
!AddELReeference.png!
9. Window->Preferences, JBoss Tools->Web->JSF->JSF Environment, button "Add" (button should be "Add...")
Dialog should have a not default bunner:
!AddJSFProjectVersion.png!
10. Window->Preferences, JBoss Tools->Web->Library Sets, button "Add" (button should be "Add...")
Dialog should have a not default bunner:
!AddLibrarySet.png!
11. Window->Preferences, JBoss Tools->Web->Templates, buttons "Add" and "Edit"(buttons should be "Add..." and "Edit...")
Dialogs should have a not default bunner:
!AddInterface.png!
!EditInterface.png!
was:
Follow
1. New->Other->JBoss Tools->Configure MavenRepositories
ConfigureMavenRepositoriesWizard.java
Wizard banner has wrong high less than 66 pixels
!ConfigureMavenRepositories.png!
2. Window->Preferences, JBoss Tools->Remote Repositories, button "Add..."
EditNexusRepositoryDialog.java
Dialog should have a banner:
!NewRepositoryDialog.png!
3. Window->Preferences, JBoss Tools->JBoss Maven Integration, button "Configure Maven Repositories"
Dialog should have a not empty banner:
!ConfigureMavenRepositories2.png!
4. Window->Preferences, JBoss Tools->JBoss ESB Runtimes, button "Add". BTW it should be "Add..."
Dialog should have a not empty banner:
!NewJBossESBRuntime.png!
5.Window->Preferences, JBoss Tools->JBoss Runtime Detection, button "Download..."
Dialog should have a not empty banner:
!DownloadRuntimes.png!
6. Window->Preferences, JBoss Tools->Web->Custom Capabilities, buttons "Add" (button should be "Add...")
Dialogs should have a not default bunner:
!AddCapability.png!
!AddLibraryReference.png!
7. Window->Preferences, JBoss Tools->Web->Editors->Visual Page Editor, tab Visual Templates, buttons "Add..." and "Import..."
Dialogs should have a not default bunner:
!UserSpecifiedTagTemplate.png!
!ImportUserSpecifiedTagTemplates.png!
8. Window->Preferences, JBoss Tools->Web->Expression Language->Variables, buttons "Add" (button should be "Add...")
Dialog should have a not default bunner:
!AddELReeference.png!
9. Window->Preferences, JBoss Tools->Web->JSF->JSF Environment, buttons "Add" (button should be "Add...")
Dialog should have a not default bunner:
!AddJSFProjectVersion.png!
10. Window->Preferences, JBoss Tools->Web->Library Sets, buttons "Add" (button should be "Add...")
Dialog should have a not default bunner:
!AddLibrarySet.png!
> Dialogs look and fill problems
> ------------------------------
>
> Key: JBIDE-13351
> URL: https://issues.jboss.org/browse/JBIDE-13351
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JSF, runtime-detection, Seam 2, Visual Page Editor Templates
> Affects Versions: 4.1.0.Alpha1
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Priority: Trivial
> Fix For: 4.1.x
>
> Attachments: AddCapability.png, AddELReeference.png, AddInterface.png, ADDJBossToolsRuntimeDialog.png, AddJSFProjectVersion.png, AddLibraryReference.png, AddLibrarySet.png, BrowseFontDialog.png, ConfigureMavenRepositories.png, ConfigureMavenRepositories2.png, DownloadRuntimes.png, EditInterface.png, EditServletClassDialog.png, EditTLDFilesDialog.png, ImportUserSpecifiedTagTemplates.png, NewJBossESBRuntime.png, NewRepositoryDialog.png, NewTemplateDialog.png, UserSpecifiedTagTemplate.png
>
>
> Follow
> 1. New->Other->JBoss Tools->Configure MavenRepositories
> ConfigureMavenRepositoriesWizard.java
> Wizard banner has wrong high less than 66 pixels
> !ConfigureMavenRepositories.png!
> 2. Window->Preferences, JBoss Tools->Remote Repositories, button "Add..."
> EditNexusRepositoryDialog.java
> Dialog should have a banner:
> !NewRepositoryDialog.png!
> 3. Window->Preferences, JBoss Tools->JBoss Maven Integration, button "Configure Maven Repositories"
> Dialog should have a not empty banner:
> !ConfigureMavenRepositories2.png!
> 4. Window->Preferences, JBoss Tools->JBoss ESB Runtimes, button "Add". BTW it should be "Add..."
> Dialog should have a not empty banner:
> !NewJBossESBRuntime.png!
> 5.Window->Preferences, JBoss Tools->JBoss Runtime Detection, button "Download..."
> Dialog should have a not empty banner:
> !DownloadRuntimes.png!
> 6. Window->Preferences, JBoss Tools->Web->Custom Capabilities, buttons "Add" (button should be "Add...")
> Dialogs should have a not default bunner:
> !AddCapability.png!
> !AddLibraryReference.png!
> 7. Window->Preferences, JBoss Tools->Web->Editors->Visual Page Editor, tab Visual Templates, buttons "Add..." and "Import..."
> Dialogs should have a not default bunner:
> !UserSpecifiedTagTemplate.png!
> !ImportUserSpecifiedTagTemplates.png!
> 8. Window->Preferences, JBoss Tools->Web->Expression Language->Variables, button "Add" (button should be "Add...")
> Dialog should have a not default bunner:
> !AddELReeference.png!
> 9. Window->Preferences, JBoss Tools->Web->JSF->JSF Environment, button "Add" (button should be "Add...")
> Dialog should have a not default bunner:
> !AddJSFProjectVersion.png!
> 10. Window->Preferences, JBoss Tools->Web->Library Sets, button "Add" (button should be "Add...")
> Dialog should have a not default bunner:
> !AddLibrarySet.png!
> 11. Window->Preferences, JBoss Tools->Web->Templates, buttons "Add" and "Edit"(buttons should be "Add..." and "Edit...")
> Dialogs should have a not default bunner:
> !AddInterface.png!
> !EditInterface.png!
--
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
13 years, 6 months