July 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-6667) NPE in org.jboss.tools.seam.core

by Snjezana Peco (JIRA)

NPE in org.jboss.tools.seam.core -------------------------------- Key: JBIDE-6667 URL: https://jira.jboss.org/browse/JBIDE-6667 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.2.x Reporter: Snjezana Peco Assignee: Alexey Kazakov Steps to reproduce: - create some project (it doesn't have to be a Java project) - close it You will get the following exception: !ENTRY org.eclipse.ui.ide 2 4 2010-07-20 22:33:43.046 !MESSAGE Problems occurred closing the selected resources. !SUBENTRY 1 org.eclipse.core.resources 2 566 2010-07-20 22:33:43.046 !MESSAGE Problems occurred during save. !STACK 0 java.lang.NullPointerException at org.jboss.tools.seam.core.SeamCorePlugin$1.saving(SeamCorePlugin.java:84) at org.eclipse.core.internal.resources.SaveManager.executeLifecycle(SaveManager.java:361) at org.eclipse.core.internal.resources.SaveManager$1.run(SaveManager.java:170) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.resources.SaveManager.broadcastLifecycle(SaveManager.java:173) at org.eclipse.core.internal.resources.SaveManager.save(SaveManager.java:1108) at org.eclipse.core.internal.resources.SaveManager.save(SaveManager.java:1087) at org.eclipse.core.internal.resources.Project.close(Project.java:190) at org.eclipse.ui.actions.CloseResourceAction.invokeOperation(CloseResourceAction.java:129) at org.eclipse.ui.actions.WorkspaceAction.execute(WorkspaceAction.java:162) at org.eclipse.ui.actions.WorkspaceAction$2.runInWorkspace(WorkspaceAction.java:483) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6610) seam components defined in custom component.xml files not recognized

by Marcel Sebek (JIRA)

seam components defined in custom component.xml files not recognized -------------------------------------------------------------------- Key: JBIDE-6610 URL: https://jira.jboss.org/browse/JBIDE-6610 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.1 Environment: seam version 2.2.0.GA, icefaces, ear-type of project Reporter: Marcel Sebek Assignee: Alexey Kazakov The component defined in custom ???.component.xml is not recognized by jboss tools. When I inject the component, I get a warning about unknown context variable name 'xyz'. However, pasting the content of custom component.xml into global components.xml hides the warnings. The injection works, therefore the code should be correct. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-6686) Hibernate platform names for JPA Facet are misleading/incorrect

by Max Rydahl Andersen (JIRA)

Hibernate platform names for JPA Facet are misleading/incorrect --------------------------------------------------------------- Key: JBIDE-6686 URL: https://jira.jboss.org/browse/JBIDE-6686 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.2.0.M1 Reporter: Max Rydahl Andersen Assignee: Dmitry Geraskov Fix For: 3.2.0.M2 We seem to provide two platform names under JPA Facet: "Hibernate" & "Hibernate jpa 2.0" 1) Both shows up no matter if I choose JPA 1 or JPA 2 on the facet page, that does not sound correct to me. 2) Why is "jpa" lower case ? 3) Why does one has a version and the on none ? 4) Shouldn't these be named after the main Hibernate version they target ? i.e. Hibernate 3.3-3.4 and Hibernate 3.5 ? Or simply Hibernate EntityManager 3.4, Hibernate EntityManager 3.5 ? (need to check the version numbers if they are correct, since i'm just speaking of memory here) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6541) code assist does not show Seam components when Eclipse first starts (until you 'refresh' or clean project)

by Vadim Berezniker (JIRA)

code assist does not show Seam components when Eclipse first starts (until you 'refresh' or clean project) ---------------------------------------------------------------------------------------------------------- Key: JBIDE-6541 URL: https://jira.jboss.org/browse/JBIDE-6541 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.1 Reporter: Vadim Berezniker Relevant forum post is here: https://community.jboss.org/message/549587#549587 As the title says, if I restart Eclipse and open a .xhtml file and try to perform EL code assist, I do not see any Seam components in the list. If I refresh the project, clean the project or expand the project in the 'Seam Components' window then it starts to work. I tried it with a clean workspace with JBoss Tools 3.1.1 with the same results. Tried it on another machine with JBoss Tools 3.1.0 with the same results. I noticed that Eclipse doesn't appear to run builders if the project is in 'pristine' state. That is if the project is built when you close Eclipse, it won't try to build it when you reopen Eclipse. Eclipse version is 3.5.2 It's a pretty minor issue as it's relatively easy to resolve, but it may be confusing to new users if they encounter it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

4
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5994) CSS Class dialog allows entering invalid class name

by Libor Zoubek (JIRA)

CSS Class dialog allows entering invalid class name --------------------------------------------------- Key: JBIDE-5994 URL: https://jira.jboss.org/jira/browse/JBIDE-5994 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.CR2 Reporter: Libor Zoubek Priority: Minor CSS Class dialog allows entering class name 'aaa;aaa' which is not valid class name. 1. create CSS file 2. Open Class Dialog (Ctrl+Shift+C) 3. Click Add CSS Class 4. enter invalid name -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-5979) CSS Properties view does not update values immediately

by Libor Zoubek (JIRA)

CSS Properties view does not update values immediately ------------------------------------------------------ Key: JBIDE-5979 URL: https://jira.jboss.org/jira/browse/JBIDE-5979 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.1.0.CR2 Reporter: Libor Zoubek Priority: Minor 'CSS Properties' view should update values of properties immediately as they are typed. When I type property value in CSS editor, everyting works. When I type in 'Properties View' updating is not working when I change value to empty string or when changing property which is yet not declared in css file. 1.Open any CSS file with CSS style class defined 2.Choose Window -> Show View -> Other -> CSS Properties. Press OK. 3.Mouse click or set cursor on any CSS Style 4.Go to CSS Properties View, select and change some properties, for example, Text color, background-color, font and so on... 5.Open standard Properties view (Window -> Show View -> Other -> General -> Properties View). 6.Edit some properties in standart Properties view and click on CSS Properties view. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

4
10
0 / 0

[JBoss JIRA] Created: (JBIDE-6600) No way to select VPE templates to render particular XML and HTML files

by Yahor Radtsevich (JIRA)

No way to select VPE templates to render particular XML and HTML files ---------------------------------------------------------------------- Key: JBIDE-6600 URL: https://jira.jboss.org/browse/JBIDE-6600 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.1.1 Reporter: Yahor Radtsevich Assignee: Maxim Areshkau Priority: Optional Regardless of which type of content is opened, VPE uses all available template libraries. Say, the same templates are used to render DocBook and HTML files. This approach works well if the templates do not intersect, but there are cases when they do (e.g. templates for 'head' tag, JBIDE-6586). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

4
9
0 / 0

[JBoss JIRA] Created: (JBIDE-6631) Add Import/Export buttons to Visual Templates Preferences page

by Yahor Radtsevich (JIRA)

Add Import/Export buttons to Visual Templates Preferences page -------------------------------------------------------------- Key: JBIDE-6631 URL: https://jira.jboss.org/browse/JBIDE-6631 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor core, Visual Page Editor Templates Reporter: Yahor Radtsevich Assignee: Yahor Radtsevich Fix For: 3.2.0.M2 Now the templates can be exported through File->Export->Unknown tags templates only. This place is hard to find. It would be great if the Visual Templates Preferences page had buttons Import/Export (same as Visual Page Editor->Code Templates). See screenshot-1.png. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-6747) New Seam Project Wizard: Don't add com.sun.facelets.FaceletViewHandler into faces-config.xml 2.0

by Alexey Kazakov (JIRA)

New Seam Project Wizard: Don't add com.sun.facelets.FaceletViewHandler into faces-config.xml 2.0 ------------------------------------------------------------------------------------------------ Key: JBIDE-6747 URL: https://jira.jboss.org/browse/JBIDE-6747 Project: Tools (JBoss Tools) Issue Type: Sub-task Reporter: Alexey Kazakov Assignee: Alexey Kazakov -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6019) Explicit action to add complex variable initialization in Assign

by Robert (Bob) Brodt (JIRA)

Explicit action to add complex variable initialization in Assign ---------------------------------------------------------------- Key: JBIDE-6019 URL: https://jira.jboss.org/jira/browse/JBIDE-6019 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: bpm Affects Versions: 3.1.0.CR2 Reporter: Robert (Bob) Brodt this could easily be solved with the addition of a button to the Assign Properties/Details tab which displays a variables selection dialog. The editor could then generate the appropriate XML to initialize complex variables. Apparently, the Riftsaw engine requires the structure of complex variables to be set before they can be accessed. An alternative would be to add an "Initialize" tab to the Assign Properties, similar to the Variable Property sheet. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

3
4
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 July 2010