December 2009 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-1273) When hot code replace fails, offer "restart deployment "as an alternative

by Gavin King (JIRA)

When hot code replace fails, offer "restart deployment "as an alternative ------------------------------------------------------------------------- Key: JBIDE-1273 URL: http://jira.jboss.com/jira/browse/JBIDE-1273 Project: JBoss Tools Issue Type: Feature Request Reporter: Gavin King The dialog box t hat eclipse pops up when hot code replace fails is very irritating, but it would be less irritating if it offered "restart deployment" as an alternative. Actually it should be smart enough to NOT pop this dialog at all for classes in src/action. So I think the Seam tools need to hijack this whole feature of eclipse. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

4
9
0 / 0

[JBoss JIRA] Created: (JBIDE-3113) Consolidation/clean up of preference pages

by John Graham (JIRA)

Consolidation/clean up of preference pages ------------------------------------------ Key: JBIDE-3113 URL: https://jira.jboss.org/jira/browse/JBIDE-3113 Project: Tools (JBoss Tools) Issue Type: Bug Components: common, drools, jbpm Affects Versions: 3.0.0.cr1 Environment: JBossTools-3.0.0.CR1-N200811050757-ALL-linux-gtk Reporter: John Graham Priority: Minor JBT currently has three preference page categories: 1. Drools 2. JBoss jBPM 3. JBoss Tools The first two should be listed as subsections of the JBoss Tools category. Alternatively, I suggest that the top level category should just be JBoss: - JBoss -- Drools -- jBPM Also, the JBoss Tools and JBoss jBPM top level pages in each of these categories do not expose preferences, but rather the default buttons or simply a label ("JBoss Tools"). These top level pages should show overall JBT preferences. See the Java preferences or other examples in the Eclipse platform for this idea. (Also note that the DTP 1.6.x way of doing this is wrong... ;) ) -- 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

14 years, 6 months

6
19
0 / 0

[JBoss JIRA] Created: (JBIDE-5099) OpenOn for custom Jsf 2.0 components

by Maxim Areshkau (JIRA)

OpenOn for custom Jsf 2.0 components ------------------------------------ Key: JBIDE-5099 URL: https://jira.jboss.org/jira/browse/JBIDE-5099 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: jsp/jsf/xml source editing, Visual Page Editor core Affects Versions: 3.1.0.M4 Reporter: Maxim Areshkau Assignee: Alexey Kazakov Fix For: 3.1.0.CR1 OpenOn for custom Jsf 2.0 components from source part. -- 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

14 years, 7 months

7
17
0 / 0

[JBoss JIRA] Created: (JBIDE-1104) .sar file cannot be included in .ear file

by Juergen Zimmermann (JIRA)

.sar file cannot be included in .ear file ----------------------------------------- Key: JBIDE-1104 URL: http://jira.jboss.com/jira/browse/JBIDE-1104 Project: JBoss Tools Issue Type: Bug Components: JBossAS Affects Versions: 2.0.0.Beta4 Environment: JBoss Tools nightly build 20071017 Reporter: Juergen Zimmermann I need a .ear file which contains a .sar file (service archive for JBoss). Such a .sar file is declared in META-INF/jboss-app.xml of the EAR project "hska" as follows: <jboss-app> <security-domain>java:/jaas/hska</security-domain> <module> <service>hska.sar</service> </module> </jboss-app> I have a "General Project" named hskaSAR which has a META-INF subdirectory for the xml files of the .sar file. Creating hskaSAR/hska.sar via the "Project Archives" view of JBoss Tools works fine. However, there is no possibility to include the .sar file within the (exploded) .ear. I tried to edit and extend the file .settings/org.eclipse.wst.common.component within the EAR project as follows: <dependent-module deploy-path="/" handle="module:/classpath/lib/hskaSAR/hska.sar"> <dependency-type>uses</dependency-type> </dependent-module> However, this workaround doesn't work. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

6
23
0 / 0

[JBoss JIRA] Created: (JBIDE-4845) Introduce qualifier

by Pete Muir (JIRA)

Introduce qualifier ------------------- Key: JBIDE-4845 URL: https://jira.jboss.org/jira/browse/JBIDE-4845 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: webbeans Reporter: Pete Muir Ability to introduce a qualifier at an IP -- 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

14 years, 7 months

4
9
0 / 0

[JBoss JIRA] Created: (JBIDE-3883) Manifest cleanup

by Max Rydahl Andersen (JIRA)

Manifest cleanup ----------------- Key: JBIDE-3883 URL: https://jira.jboss.org/jira/browse/JBIDE-3883 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Build/Releng Affects Versions: 3.0.0.GA Reporter: Max Rydahl Andersen Fix For: 3.1.0 After JBIDE-3873 it is about time we find time to set: Bundle-Require-Execution-Environment minimum versions boundaries for dependencies (add more if needed) -- 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

14 years, 7 months

5
30
0 / 0

[JBoss JIRA] Created: (JBDS-606) When editing the node name in source view of jPDL the editor behaves abnormaly

by Somil Jain (JIRA)

When editing the node name in source view of jPDL the editor behaves abnormaly ------------------------------------------------------------------------------ Key: JBDS-606 URL: https://jira.jboss.org/jira/browse/JBDS-606 Project: Developer Studio Issue Type: Bug Affects Versions: 2.0.0.cr1, 2.0.0.beta1 Environment: Fedora 9 Reporter: Somil Jain In graphical process designer (jBPM process) using source view when you try to change the name of the node (the node ithat is being referenced in the process) "Backspace"/"Delete" key behaves weiredly, the cursor position is not at right position so it skips some of the text and when you try to type instead of outputing the text from left to right it outputs the text from right to left for example if you type "Hello" it will type as "olleH". -- 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

14 years, 7 months

5
19
0 / 0

[JBoss JIRA] Created: (JBIDE-4843) Ability to enable an alternative in context-sensitive menu

by Pete Muir (JIRA)

Ability to enable an alternative in context-sensitive menu ---------------------------------------------------------- Key: JBIDE-4843 URL: https://jira.jboss.org/jira/browse/JBIDE-4843 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Pete Muir Enable an alternative in beans.xml by right clicking on the @Alternatives -- 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

14 years, 7 months

5
10
0 / 0

[JBoss JIRA] Created: (JBIDE-873) Code assist does not work for style attribute of jsf tag

by Adrian Mitev (JIRA)

Code assist does not work for style attribute of jsf tag -------------------------------------------------------- Key: JBIDE-873 URL: http://jira.jboss.com/jira/browse/JBIDE-873 Project: JBoss Tools Issue Type: Bug Environment: rhds beta 1, jdk 1.5_0.12, windows xp Reporter: Adrian Mitev Priority: Minor In style attribute of normal html tags code assist works, in jsf tags it doesn't. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

6
12
0 / 0

[JBoss JIRA] Created: (JBIDE-3795) Hibernate Config view cannot create JPA based configuration with @GeneratedValue using a @GenericGenerator

by Bob Thule (JIRA)

Hibernate Config view cannot create JPA based configuration with @GeneratedValue using a @GenericGenerator ---------------------------------------------------------------------------------------------------------- Key: JBIDE-3795 URL: https://jira.jboss.org/jira/browse/JBIDE-3795 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.0.0.CR2 Environment: Hibernate Tools 3.2.4.GA-N200902101801, Java Persistence API Tools 2.1.0.v200812180210 Reporter: Bob Thule This may be related to issue JBIDE-3636. https://jira.jboss.org/jira/browse/JBIDE-3636 With a @GenericGenerator declared as: @GenericGenerator(name = "SeqBase",... ) //either in package-info.java or on the class and used with: @GeneratedValue(generator = "SeqBase") private Long id; when in the "Hibernate Config" view and the hibernate configuration is trying to be displayed or rebuilt, Eclipse gives the following exception: org.hibernate.console.HibernateConsoleRuntimeException: Could not create JPA based Configuration Could not create JPA based Configuration <No message> java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException: <no message> java.lang.reflect.InvocationTargetException javax.persistence.PersistenceException: org.hibernate.AnnotationException: Unknown Id.generator: SeqBase org.hibernate.AnnotationException: Unknown Id.generator: SeqBase org.hibernate.AnnotationException: Unknown Id.generator: SeqBase Unknown Id.generator: SeqBase -- 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

14 years, 7 months

4
21
0 / 0

[JBoss JIRA] Created: (JBDS-838) Find a better home for nightly and archiving of JBDS builds

by Max Rydahl Andersen (JIRA)

Find a better home for nightly and archiving of JBDS builds ----------------------------------------------------------- Key: JBDS-838 URL: https://jira.jboss.org/jira/browse/JBDS-838 Project: JBoss Developer Studio Issue Type: Task Components: Build Affects Versions: 3.0.0.M4 Reporter: Max Rydahl Andersen Assignee: Max Rydahl Andersen Priority: Critical For a while we have been archiving at an QA server located in ATL which is now in PHO but it only gives about 40 kb/s download from europe. Moving it to porkchop would help here since the main site has 80 kb/s and can be mirrored to Brno giving 120 kb/s. End result: 10-24hrs download times gets reduced to 1-2 hrs download for European devs. -- 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

14 years, 7 months

5
28
0 / 0

[JBoss JIRA] Created: (JBIDE-5284) Warning related to incorrect Seam project name don't appear

by Aliaksey Nis (JIRA)

Warning related to incorrect Seam project name don't appear ----------------------------------------------------------- Key: JBIDE-5284 URL: https://jira.jboss.org/jira/browse/JBIDE-5284 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.0.CR1 Environment: WindowsXP SP2 JBoss Tools Version: 3.1.0.CR1 eclipse-SDK-3.5RC3-win32.zip Build id: JBossTools-Update-3.1.0.v200911251807N-H130-RC1 JRE 1.6 Reporter: Aliaksey Nis Priority: Optional Attachments: NoWarningSeam.JPG Related to JBIDE-5223 EXECUTE: New Seam project. EXECUTE: Input name "blahblah+". EXECUTE: Press next few times. ASSERT: At step "Web module" button Next is in disable state, due to incorrect project name. FAILURE: No warning appears. It appears only if you press Back, then Next again. Screenshot attached. -- 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

14 years, 7 months

7
10
0 / 0

[JBoss JIRA] Created: (JBIDE-2242) Taglib declaration <%@ taglib uri="" is inserted after DnD tags from Pallete on some XHTML pages in default Seam web project.

by Anton Klimkovich (JIRA)

Taglib declaration <%@ taglib uri="" is inserted after DnD tags from Pallete on some XHTML pages in default Seam web project. ----------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-2242 URL: http://jira.jboss.com/jira/browse/JBIDE-2242 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 2.1.0.GA Reporter: Anton Klimkovich Assigned To: Maxim Areshkau Priority: Minor EXECUTE: Create default Seam project EXECUTE: Open menu.xhtml EXECUTE: Make DnD of JBoss Ajax4jsf tag on the page from Palette. FAILURE: <%@ taglib uri="http://java.sun.com/jsf/html" prefix="h"%> inserted instead of xmlns:h="http://java.sun.com/jsf/html" ASSERT: Seam gen should create xhtml pages with declaration that tells it's a XHTML. (<!DOCTYPE composition PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">) All pages w/o declaration are attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

6
9
0 / 0

[JBoss JIRA] Created: (JBDS-904) JBDS 2.1 GA, JBPM and Seam

by Gary Lamperillo (JIRA)

JBDS 2.1 GA, JBPM and Seam -------------------------- Key: JBDS-904 URL: https://jira.jboss.org/jira/browse/JBDS-904 Project: JBoss Developer Studio Issue Type: Bug Components: integration Affects Versions: 2.1.0 Environment: JBDS 2.1 GA, EAP 5 Beta 2, Seam 2.2 , jBPM Reporter: Gary Lamperillo The jBPM New Process Definition wizard will not create a process in the EAR level. According to the Seam Reference manual, it should go at the EAR level. The Process Definition created by the wizard creates 3 files in a directory. the components.xml can not use the directory for the process definition, you get the following on deploy: Caused by: org.jbpm.jpdl.JpdlException: [[ERROR] resource not found: /seam_drools10_15-ejb/jbpm_to_rules] at org.jbpm.graph.def.ProcessDefinition.parseXmlResource(ProcessDefinition.java:162) at org.jboss.seam.bpm.Jbpm.deployProcess(Jbpm.java:311) at org.jboss.seam.bpm.Jbpm.installProcessDefinitions(Jbpm.java:294) ... 85 more when using a location for the processdefinition.xml in this directory, you will get: Caused by: java.lang.RuntimeException: could not deploy a process definition at org.jboss.seam.bpm.Jbpm.installProcessDefinitions(Jbpm.java:300) at org.jboss.seam.bpm.Jbpm.startup(Jbpm.java:80) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.jboss.seam.util.Reflections.invoke(Reflections.java:22) at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:144) at org.jboss.seam.Component.callComponentMethod(Component.java:2249) at org.jboss.seam.Component.callCreateMethod(Component.java:2172) at org.jboss.seam.Component.newInstance(Component.java:2132) ... 75 more Caused by: org.jbpm.jpdl.JpdlException: [[ERROR] resource not found: /seam_drools10_15-ejb/jbpm_to_rules/processdefinition.xml] at org.jbpm.graph.def.ProcessDefinition.parseXmlResource(ProcessDefinition.java:162) at org.jboss.seam.bpm.Jbpm.deployProcess(Jbpm.java:311) at org.jboss.seam.bpm.Jbpm.installProcessDefinitions(Jbpm.java:294) ... 85 more Is the plan for this process definition editor to work with Seam? Is there something missing in this setup? -- 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

14 years, 7 months

7
23
0 / 0

[JBoss JIRA] Created: (JBIDE-1354) Runtimes should be configurable with respect to what jars to return for certain runtimes

by Max Andersen (JIRA)

Runtimes should be configurable with respect to what jars to return for certain runtimes ---------------------------------------------------------------------------------------- Key: JBIDE-1354 URL: http://jira.jboss.com/jira/browse/JBIDE-1354 Project: JBoss Tools Issue Type: Feature Request Components: JBossAS Reporter: Max Andersen Fix For: 2.1 deploy only runtime could have preferences to control which jars they would actually return for various facets etc. optimally these would actually work on on any of our runtimes and just use variables/clever-defaults depending and allow users to override them if necessary. The user should be able to point to jars in a project, workspace, filesystem, classpath library, maven/ivy dependency even ...etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

6
26
0 / 0

[JBoss JIRA] Created: (JBIDE-4127) "Add JSF-Capabilities" adds jsf-facelets.jar which is older than the one in .classpath

by Leiv Hellebo (JIRA)

"Add JSF-Capabilities" adds jsf-facelets.jar which is older than the one in .classpath -------------------------------------------------------------------------------------- Key: JBIDE-4127 URL: https://jira.jboss.org/jira/browse/JBIDE-4127 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.0.0.GA Environment: JBDS 2.0.GA Seam 2.1.X Reporter: Leiv Hellebo The Add JSF-Capabilities dialog makes it possible to shoot oneself in the foot: It will happily add jsf-facelets.jar with Implementation-Version: 1.1.11, even if the one mentioned in .classpath has Implementation-Version: 1.1.15.B1 AFAICS, when performing a redirect within a long-running conversation, this makes "DEBUG [org.jboss.seam.contexts.ServletLifecycle] >>> Begin re-initialization" disappear from server.log, and needed context vars are not initialized. I'd file this as an "Improvement", not a "Bug" if it was possible. You may want to say "PEBKAC" to this... -- 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

14 years, 7 months

5
7
0 / 0

[JBoss JIRA] Created: (JBIDE-1050) Add Capabilities to Struts 1.3 at struts Tools

by Hermes Waldemarin (JIRA)

Add Capabilities to Struts 1.3 at struts Tools ---------------------------------------------- Key: JBIDE-1050 URL: http://jira.jboss.com/jira/browse/JBIDE-1050 Project: JBoss Tools Issue Type: Bug Components: JBoss Tools Core Affects Versions: 2.0.0.Beta3 Environment: Eclipse 3.3 Europa, Windows XP Reporter: Hermes Waldemarin I`m use struts 1.3.x in my aplication. I need to use chains policies in struts config, but this implementation is in 1.3.x version. Can you add Struts 1.3.x capabilities for struts plugin? Thanks... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
3
0 / 0

[jbosside-issues] [JBoss JIRA] Created: (JBIDE-467) NullPointerException on ProjectChangeListener

by pchar (JIRA)

NullPointerException on ProjectChangeListener --------------------------------------------- Key: JBIDE-467 URL: http://jira.jboss.com/jira/browse/JBIDE-467 Project: JBoss IDE Issue Type: Bug Components: JBossIDE Core Affects Versions: 1.6 Environment: Eclipse Version: 3.2.2 Mac OS X Java 1.5 Reporter: pchar Assigned To: Marshall Culpepper There's a null pointer excetion on a lister here the stackstrace: !ENTRY org.eclipse.core.resources 4 2 2007-03-30 08:31:42.807 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources". !STACK 0 java.lang.NullPointerException at org.jboss.ide.eclipse.core.ProjectChangeListener.resourceChanged(ProjectChangeListener.java:46) at org.eclipse.core.internal.events.NotificationManager$2.run(NotificationManager.java:280) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:274) at org.eclipse.core.internal.events.NotificationManager.handleEvent(NotificationManager.java:246) at org.eclipse.core.internal.resources.Workspace.broadcastEvent(Workspace.java:250) at org.eclipse.core.internal.resources.Project.close(Project.java:186) at org.eclipse.ui.actions.CloseResourceAction.invokeOperation(CloseResourceAction.java:184) at org.eclipse.ui.actions.WorkspaceAction.execute(WorkspaceAction.java:134) at org.eclipse.ui.actions.WorkspaceAction$2.runInWorkspace(WorkspaceAction.java:429) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
2
0 / 0

[jbosside-issues] [JBoss JIRA] Created: (JBIDE-465) Problems occurred when invoking code from plug-in: "org.eclipse.jface".

by Mallika Guliani (JIRA)

Problems occurred when invoking code from plug-in: "org.eclipse.jface". ----------------------------------------------------------------------- Key: JBIDE-465 URL: http://jira.jboss.com/jira/browse/JBIDE-465 Project: JBoss IDE Issue Type: Bug Components: JBossIDE Core Affects Versions: 1.6 Environment: Win XP PRO Reporter: Mallika Guliani Assigned To: Marshall Culpepper I am not able to create Server configuration in Eclipse 3.2.2. I am using JBoss 1.6.0 GA. I get the following errors: Problems occurred when invoking code from plug-in: "org.eclipse.jface". Unhandled event loop exception - plug in - "org.eclipse.ui" I saw that this error is already logged but unable to find a solution. Could someone please provide step by step resolution? I would really appreciate your help. I have already spent a day trying out different versions of JBoss IDE but no result. I have JBoss - 4.0.2 AS. Thank You. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

5
6
0 / 0

[JBoss JIRA] Created: (JBIDE-599) Radio/check button labels should not have a colon (:) automatically added

by Max Andersen (JIRA)

Radio/check button labels should not have a colon (:) automatically added ------------------------------------------------------------------------- Key: JBIDE-599 URL: http://jira.jboss.com/jira/browse/JBIDE-599 Project: JBoss Tools Issue Type: Bug Components: JBoss Tools Core Affects Versions: ExadelStudioPro4 Reporter: Max Andersen Assigned To: Viacheslav Kabanovich Looks like labels always get a colon added when used in dialogs. That makes it look wrong for radio/checkbuttons. Attached screenshot showing one example of it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
3
0 / 0

[jbosside-issues] [JBoss JIRA] Created: (JBIDE-470) JBOSS-IDE is missing jboss-ejb3x.jar in "Jboss Ejb3 Libraries" when using JBAS 4.2CR2

by Perry Rhodan (JIRA)

JBOSS-IDE is missing jboss-ejb3x.jar in "Jboss Ejb3 Libraries" when using JBAS 4.2CR2 ------------------------------------------------------------------------------------- Key: JBIDE-470 URL: http://jira.jboss.com/jira/browse/JBIDE-470 Project: JBoss IDE Issue Type: Bug Components: JBossIDE Core Affects Versions: 2.0.0.Beta2 Reporter: Perry Rhodan Assigned To: Marshall Culpepper When selecting "Jboss EJB3 Libraries" in Eclipse-Project Build-path settings, while using Jboss 4.2CR2, the project cannot be build, cause there are build-path errors, cause of jboss-ide is missing the "jboss-ejb3x.jar". Reason: since Jboss 4.2CR2 the jboss-ejb3x.jar isn't anymore in the $SERVER_HOME/server/default/deploy/ejb3.deployer directory. It's now located in the $SERVER_HOME/server/default/lib directory. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-605) latest svn has various issues with xmodel ui's

by Max Andersen (JIRA)

latest svn has various issues with xmodel ui's ---------------------------------------------- Key: JBIDE-605 URL: http://jira.jboss.com/jira/browse/JBIDE-605 Project: JBoss Tools Issue Type: Bug Components: JBoss Tools Core Affects Versions: 2.0.0.Beta2 Reporter: Max Andersen Assigned To: Marshall Culpepper Attachments: rightclickprojectexplorer.png Not sure if these are all related, so please create separate issues if separate. They all started to happen after i updated from svn today: ORM Explorer gives me: java.lang.ClassNotFoundException: org.jboss.tools.hibernate.view.views.ExplorerClass at java.lang.ClassLoader.findClass(ClassLoader.java:358) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at org.eclipse.osgi.framework.internal.core.BundleLoader.findClassInternal(BundleLoader.java:429) at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:369) at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:357) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:83) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) Before it would show "No hibernate projects found" or the list of hibernate projects. Open a components.xml file and I get: java.lang.IllegalArgumentException: Argument not valid at org.eclipse.swt.SWT.error(SWT.java:3531) at org.eclipse.swt.SWT.error(SWT.java:3465) at org.eclipse.swt.SWT.error(SWT.java:3436) at org.eclipse.swt.graphics.GC.setFont(GC.java:3162) at org.eclipse.ui.forms.widgets.ExpandableComposite$ExpandableLayout.layout(ExpandableComposite.java:280) at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1311) at org.eclipse.swt.widgets.Composite.layout(Composite.java:876) at org.eclipse.swt.widgets.Composite.layout(Composite.java:841) at org.eclipse.swt.widgets.Composite.layout(Composite.java:811) at org.jboss.tools.common.editor.form.SampleErrorForm$ErrorLayout.layout(SampleErrorForm.java:359) at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1311) at org.eclipse.swt.widgets.Composite.layout(Composite.java:876) at org.eclipse.swt.widgets.Composite.layout(Composite.java:841) at org.jboss.tools.common.editor.form.SampleErrorForm.setVisible(SampleErrorForm.java:106) at org.jboss.tools.common.editor.TreeFormPage.doErrorMode(TreeFormPage.java:295) at org.jboss.tools.common.editor.TreeFormPage.setErrorMode(TreeFormPage.java:287) Right click on files in Project Explorer doesn't show any menu's anymore (not even on plain Dynamic web project). See attached screenshot - rightclick on test.txt doesn't do anything, same with web.xml. Right click on Seam components sometimes give an "Open" menu. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

4
10
0 / 0

[JBoss JIRA] Created: (JBIDE-649) rename a folder while files are open gives exceptions galore

by Max Andersen (JIRA)

rename a folder while files are open gives exceptions galore ------------------------------------------------------------ Key: JBIDE-649 URL: http://jira.jboss.com/jira/browse/JBIDE-649 Project: JBoss Tools Issue Type: Bug Components: JBoss Tools Core Reporter: Max Andersen Assigned To: Marshall Culpepper Fix For: 2.0.0.20070731 e.g. try and open some files in WebContent of a seam generated project and rename it to e.g. "view", I got the following exceptions: !ENTRY org.eclipse.core.resources 4 2 2007-08-02 15:41:39.045 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources". !STACK 0 java.lang.RuntimeException: FileSystemsRenameListenerContribution.getWebRootWTP(XModel model) migration to WTP I-build is needed. at org.jboss.tools.jst.web.project.FileSystemsRenameListenerContribution.getWebRootWTP(FileSystemsRenameListenerContribution.java:42) at org.jboss.tools.jst.web.project.FileSystemsRenameListenerContribution.pathRenamed(FileSystemsRenameListenerContribution.java:25) at org.jboss.tools.common.model.filesystems.impl.FileSystemsRenameListener.pathRenamed(FileSystemsRenameListener.java:119) at org.jboss.tools.common.model.filesystems.impl.FileSystemsRenameListener.checkFileSystemRename(FileSystemsRenameListener.java:49) at org.jboss.tools.common.model.filesystems.impl.FileSystemsImpl.resourceChanged(FileSystemsImpl.java:168) at org.eclipse.core.internal.events.NotificationManager$2.run(NotificationManager.java:282) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:276) at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:148) at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:311) at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1018) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1806) at org.eclipse.ui.ide.undo.AbstractWorkspaceOperation.execute(AbstractWorkspaceOperation.java:204) at org.eclipse.core.commands.operations.DefaultOperationHistory.execute(DefaultOperationHistory.java:511) at org.eclipse.ui.actions.RenameResourceAction$8.run(RenameResourceAction.java:641) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113) !ENTRY org.eclipse.ui.workbench 4 0 2007-08-02 15:41:39.280 !MESSAGE Invalid thread access !STACK 0 org.eclipse.swt.SWTException: Invalid thread access at org.eclipse.swt.SWT.error(SWT.java:3563) at org.eclipse.swt.SWT.error(SWT.java:3481) at org.eclipse.swt.SWT.error(SWT.java:3452) at org.eclipse.swt.widgets.Widget.error(Widget.java:438) at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:377) at org.eclipse.swt.widgets.Widget.getData(Widget.java:464) at org.eclipse.ui.internal.presentations.defaultpresentation.DefaultTabFolder.getTab(DefaultTabFolder.java:176) at org.eclipse.ui.internal.presentations.defaultpresentation.DefaultTabFolder.getItems(DefaultTabFolder.java:228) at org.eclipse.ui.internal.presentations.util.AbstractTabFolder.findItem(AbstractTabFolder.java:169) at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.getTab(PresentablePartFolder.java:373) at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.childPropertyChanged(PresentablePartFolder.java:301) at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.access$2(PresentablePartFolder.java:300) at org.eclipse.ui.internal.presentations.util.PresentablePartFolder$3.propertyChanged(PresentablePartFolder.java:81) at org.eclipse.ui.internal.presentations.PresentablePart.firePropertyChange(PresentablePart.java:136) at org.eclipse.ui.internal.presentations.PresentablePart$1.propertyChanged(PresentablePart.java:96) at org.eclipse.ui.internal.PartPane.firePropertyChange(PartPane.java:606) at org.eclipse.ui.internal.PartPane.propertyChanged(PartPane.java:611) at org.eclipse.ui.internal.WorkbenchPartReference.immediateFirePropertyChange(WorkbenchPartReference.java:568) at org.eclipse.ui.internal.WorkbenchPartReference.firePropertyChange(WorkbenchPartReference.java:561) at org.eclipse.ui.internal.WorkbenchPartReference.partPropertyChanged(WorkbenchPartReference.java:296) at org.eclipse.ui.internal.EditorReference.partPropertyChanged(EditorReference.java:497) at org.eclipse.ui.internal.WorkbenchPartReference$2.propertyChanged(WorkbenchPartReference.java:178) at org.eclipse.ui.part.WorkbenchPart.firePropertyChange(WorkbenchPart.java:128) at org.jboss.tools.common.model.ui.editor.EditorPartWrapper.access$0(EditorPartWrapper.java:1) at org.jboss.tools.common.model.ui.editor.EditorPartWrapper$PCL.propertyChanged(EditorPartWrapper.java:180) at org.eclipse.ui.part.WorkbenchPart.firePropertyChange(WorkbenchPart.java:128) at org.jboss.tools.common.editor.ObjectMultiPageEditor.setInput(ObjectMultiPageEditor.java:98) at org.jboss.tools.common.editor.ResourceChangeListener.resourceChanged(ObjectMultiPageEditor.java:1057) at org.eclipse.core.internal.events.NotificationManager$2.run(NotificationManager.java:282) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:276) at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:148) at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:311) at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1018) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1806) at org.eclipse.ui.ide.undo.AbstractWorkspaceOperation.execute(AbstractWorkspaceOperation.java:204) at org.eclipse.core.commands.operations.DefaultOperationHistory.execute(DefaultOperationHistory.java:511) at org.eclipse.ui.actions.RenameResourceAction$8.run(RenameResourceAction.java:641) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113) !ENTRY org.eclipse.ui.workbench 4 0 2007-08-02 15:41:39.282 !MESSAGE Invalid thread access !STACK 0 org.eclipse.swt.SWTException: Invalid thread access at org.eclipse.swt.SWT.error(SWT.java:3563) at org.eclipse.swt.SWT.error(SWT.java:3481) at org.eclipse.swt.SWT.error(SWT.java:3452) at org.eclipse.swt.widgets.Widget.error(Widget.java:438) at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:377) at org.eclipse.swt.widgets.Widget.getData(Widget.java:464) at org.eclipse.ui.internal.presentations.defaultpresentation.DefaultTabFolder.getTab(DefaultTabFolder.java:176) at org.eclipse.ui.internal.presentations.defaultpresentation.DefaultTabFolder.getItems(DefaultTabFolder.java:228) at org.eclipse.ui.internal.presentations.util.AbstractTabFolder.findItem(AbstractTabFolder.java:169) at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.getTab(PresentablePartFolder.java:373) at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.childPropertyChanged(PresentablePartFolder.java:301) at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.access$2(PresentablePartFolder.java:300) at org.eclipse.ui.internal.presentations.util.PresentablePartFolder$3.propertyChanged(PresentablePartFolder.java:81) at org.eclipse.ui.internal.presentations.PresentablePart.firePropertyChange(PresentablePart.java:136) at org.eclipse.ui.internal.presentations.PresentablePart$1.propertyChanged(PresentablePart.java:96) at org.eclipse.ui.internal.PartPane.firePropertyChange(PartPane.java:606) at org.eclipse.ui.internal.PartPane.propertyChanged(PartPane.java:611) at org.eclipse.ui.internal.WorkbenchPartReference.immediateFirePropertyChange(WorkbenchPartReference.java:568) at org.eclipse.ui.internal.WorkbenchPartReference.firePropertyChange(WorkbenchPartReference.java:561) at org.eclipse.ui.internal.WorkbenchPartReference.partPropertyChanged(WorkbenchPartReference.java:296) at org.eclipse.ui.internal.EditorReference.partPropertyChanged(EditorReference.java:497) at org.eclipse.ui.internal.WorkbenchPartReference$2.propertyChanged(WorkbenchPartReference.java:178) at org.eclipse.ui.part.WorkbenchPart.firePropertyChange(WorkbenchPart.java:128) at org.jboss.tools.common.editor.ObjectMultiPageEditor.setInput(ObjectMultiPageEditor.java:98) at org.jboss.tools.common.editor.ResourceChangeListener.resourceChanged(ObjectMultiPageEditor.java:1057) at org.eclipse.core.internal.events.NotificationManager$2.run(NotificationManager.java:282) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:276) at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:148) at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:311) at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1018) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1806) at org.eclipse.ui.ide.undo.AbstractWorkspaceOperation.execute(AbstractWorkspaceOperation.java:204) at org.eclipse.core.commands.operations.DefaultOperationHistory.execute(DefaultOperationHistory.java:511) at org.eclipse.ui.actions.RenameResourceAction$8.run(RenameResourceAction.java:641) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113) !ENTRY org.jboss.tools.common.model.ui 4 0 2007-08-02 15:41:39.285 !MESSAGE Invalid thread access !STACK 0 org.eclipse.swt.SWTException: Invalid thread access at org.eclipse.swt.SWT.error(SWT.java:3563) at org.eclipse.swt.SWT.error(SWT.java:3481) at org.eclipse.swt.SWT.error(SWT.java:3452) at org.eclipse.swt.widgets.Widget.error(Widget.java:438) at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:377) at org.eclipse.swt.widgets.Control.internal_new_GC(Control.java:2701) at org.eclipse.swt.graphics.GC.<init>(GC.java:146) at org.eclipse.swt.graphics.GC.<init>(GC.java:112) at org.eclipse.jface.text.source.LineNumberRulerColumn.computeIndentations(LineNumberRulerColumn.java:487) at org.eclipse.jface.text.source.LineNumberChangeRulerColumn.setRevisionInformation(LineNumberChangeRulerColumn.java:253) at org.eclipse.ui.internal.texteditor.LineNumberColumn.hideRevisionInformation(LineNumberColumn.java:762) at org.eclipse.ui.texteditor.AbstractDecoratedTextEditor.doSetInput(AbstractDecoratedTextEditor.java:1223) at org.eclipse.ui.editors.text.TextEditor.doSetInput(TextEditor.java:168) at org.eclipse.wst.sse.ui.StructuredTextEditor.doSetInput(StructuredTextEditor.java:2094) at org.jboss.tools.common.model.ui.texteditors.xmleditor.XMLTextEditor.doSetInput(XMLTextEditor.java:332) at org.eclipse.ui.texteditor.AbstractTextEditor.setInputWithNotify(AbstractTextEditor.java:3995) at org.eclipse.ui.texteditor.AbstractTextEditor.setInput(AbstractTextEditor.java:4017) at org.jboss.tools.common.editor.ResourceChangeListener.resourceChanged(ObjectMultiPageEditor.java:1061) at org.eclipse.core.internal.events.NotificationManager$2.run(NotificationManager.java:282) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:276) at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:148) at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:311) at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1018) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1806) at org.eclipse.ui.ide.undo.AbstractWorkspaceOperation.execute(AbstractWorkspaceOperation.java:204) at org.eclipse.core.commands.operations.DefaultOperationHistory.execute(DefaultOperationHistory.java:511) at org.eclipse.ui.actions.RenameResourceAction$8.run(RenameResourceAction.java:641) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113) !ENTRY org.eclipse.core.filebuffers 4 2 2007-08-02 15:41:39.565 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.filebuffers". !STACK 0 org.eclipse.wst.sse.core.internal.util.Assert$AssertionFailedException at org.eclipse.wst.sse.core.internal.util.Assert.isNotNull(Assert.java:124) at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl.releaseFromEdit(ModelManagerImpl.java:1380) at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl.releaseFromEdit(ModelManagerImpl.java:1345) at org.eclipse.wst.sse.core.internal.model.AbstractStructuredModel.releaseFromEdit(AbstractStructuredModel.java:1044) at org.eclipse.wst.xml.core.internal.document.DOMModelImpl.releaseFromEdit(DOMModelImpl.java:804) at org.eclipse.wst.sse.ui.StructuredTextEditor.doSetInput(StructuredTextEditor.java:2091) at org.jboss.tools.common.model.ui.texteditors.xmleditor.XMLTextEditor.doSetInput(XMLTextEditor.java:332) at org.eclipse.ui.texteditor.AbstractTextEditor.setInputWithNotify(AbstractTextEditor.java:3995) at org.eclipse.ui.texteditor.AbstractTextEditor.setInput(AbstractTextEditor.java:4017) at org.eclipse.ui.texteditor.AbstractTextEditor$7.run(AbstractTextEditor.java:478) at org.eclipse.ui.texteditor.AbstractTextEditor$ElementStateListener.execute(AbstractTextEditor.java:547) at org.eclipse.ui.texteditor.AbstractTextEditor$ElementStateListener.elementMoved(AbstractTextEditor.java:508) at org.eclipse.ui.editors.text.TextFileDocumentProvider$FileBufferListener.underlyingFileMoved(TextFileDocumentProvider.java:316) at org.eclipse.core.internal.filebuffers.TextFileBufferManager$6.run(TextFileBufferManager.java:676) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.internal.filebuffers.TextFileBufferManager.fireUnderlyingFileMoved(TextFileBufferManager.java:674) at org.eclipse.core.internal.filebuffers.ResourceFileBuffer.handleFileMoved(ResourceFileBuffer.java:463) at org.eclipse.core.internal.filebuffers.ResourceFileBuffer$3.execute(ResourceFileBuffer.java:162) at org.eclipse.core.internal.filebuffers.ResourceFileBuffer$SafeFileChange.run(ResourceFileBuffer.java:86) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3296) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2974) at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:158) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:326) at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:495) at org.eclipse.ui.internal.progress.ProgressMonitorJobsDialog.run(ProgressMonitorJobsDialog.java:268) at org.eclipse.ui.actions.WorkspaceAction.run(WorkspaceAction.java:311) at org.eclipse.ui.actions.RenameResourceAction.runWithNewPath(RenameResourceAction.java:488) at org.eclipse.ui.actions.RenameResourceAction$7.run(RenameResourceAction.java:525) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3296) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2974) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219) at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:504) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443) at org.eclipse.equinox.launcher.Main.run(Main.java:1169) !ENTRY org.eclipse.core.filebuffers 4 0 2007-08-02 15:41:39.567 !MESSAGE TextFileBufferManager failed to notify an ITextFileBufferListener !STACK 0 org.eclipse.wst.sse.core.internal.util.Assert$AssertionFailedException at org.eclipse.wst.sse.core.internal.util.Assert.isNotNull(Assert.java:124) at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl.releaseFromEdit(ModelManagerImpl.java:1380) at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl.releaseFromEdit(ModelManagerImpl.java:1345) at org.eclipse.wst.sse.core.internal.model.AbstractStructuredModel.releaseFromEdit(AbstractStructuredModel.java:1044) at org.eclipse.wst.xml.core.internal.document.DOMModelImpl.releaseFromEdit(DOMModelImpl.java:804) at org.eclipse.wst.sse.ui.StructuredTextEditor.doSetInput(StructuredTextEditor.java:2091) at org.jboss.tools.common.model.ui.texteditors.xmleditor.XMLTextEditor.doSetInput(XMLTextEditor.java:332) at org.eclipse.ui.texteditor.AbstractTextEditor.setInputWithNotify(AbstractTextEditor.java:3995) at org.eclipse.ui.texteditor.AbstractTextEditor.setInput(AbstractTextEditor.java:4017) at org.eclipse.ui.texteditor.AbstractTextEditor$7.run(AbstractTextEditor.java:478) at org.eclipse.ui.texteditor.AbstractTextEditor$ElementStateListener.execute(AbstractTextEditor.java:547) at org.eclipse.ui.texteditor.AbstractTextEditor$ElementStateListener.elementMoved(AbstractTextEditor.java:508) at org.eclipse.ui.editors.text.TextFileDocumentProvider$FileBufferListener.underlyingFileMoved(TextFileDocumentProvider.java:316) at org.eclipse.core.internal.filebuffers.TextFileBufferManager$6.run(TextFileBufferManager.java:676) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.internal.filebuffers.TextFileBufferManager.fireUnderlyingFileMoved(TextFileBufferManager.java:674) at org.eclipse.core.internal.filebuffers.ResourceFileBuffer.handleFileMoved(ResourceFileBuffer.java:463) at org.eclipse.core.internal.filebuffers.ResourceFileBuffer$3.execute(ResourceFileBuffer.java:162) at org.eclipse.core.internal.filebuffers.ResourceFileBuffer$SafeFileChange.run(ResourceFileBuffer.java:86) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3296) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2974) at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:158) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:326) at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:495) at org.eclipse.ui.internal.progress.ProgressMonitorJobsDialog.run(ProgressMonitorJobsDialog.java:268) at org.eclipse.ui.actions.WorkspaceAction.run(WorkspaceAction.java:311) at org.eclipse.ui.actions.RenameResourceAction.runWithNewPath(RenameResourceAction.java:488) at org.eclipse.ui.actions.RenameResourceAction$7.run(RenameResourceAction.java:525) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3296) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2974) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219) at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:504) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443) at org.eclipse.equinox.launcher.Main.run(Main.java:1169) !ENTRY org.jboss.tools.common.model.ui 1 0 2007-08-02 15:41:41.158 !MESSAGE ModelListener is disposed, but cannot removed from model!!!! !ENTRY org.jboss.tools.common.model.ui 1 0 2007-08-02 15:41:41.158 !MESSAGE ModelListener is disposed, but not removed from model!!!! !ENTRY org.jboss.tools.common.model.ui 1 0 2007-08-02 15:41:41.200 !MESSAGE ModelListener is disposed, but not removed from model!!!! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-803) Build error creating a new seam 2.0 project in RHDS Beta 1

by Gary Pinkham (JIRA)

Build error creating a new seam 2.0 project in RHDS Beta 1 ---------------------------------------------------------- Key: JBIDE-803 URL: http://jira.jboss.com/jira/browse/JBIDE-803 Project: JBoss Tools Issue Type: Bug Components: JBoss Tools Core Affects Versions: 2.0.0.Beta3 Environment: Windows XP SP2. Redhat Dev Studio Beta1, Seam 2.0, JDK 1.5.0.9 Reporter: Gary Pinkham Assigned To: Marshall Culpepper Priority: Minor Creating a new seam project using Seam 2.0 and Redhat Dev Studio Beta 1 creates a Component.XML with the following error: ERROR: 0.0 Unallowed child null:managed-persistence-context of components The error shows in the tree view in the Redhat XML Editor and in the Problems tab as it causes a build error. Modifying the Component.xml file (adding in entity-manager-factory="" to the "persistence:managed-persistence-context" tag and saving causes the build error to go away but the error still shows on the Tree view tab. I removed the entity-manager-factory="" from the file and re-saved. Build still works. If I reopen the file in Tree view mode the build error returns. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

5
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5026) Add JSF Capabilities are blocked with Eclipse by Updating maven dependences.

by Yura Zhishko (JIRA)

Add JSF Capabilities are blocked with Eclipse by Updating maven dependences. ---------------------------------------------------------------------------- Key: JBIDE-5026 URL: https://jira.jboss.org/jira/browse/JBIDE-5026 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.1.0.M4 Environment: Eclipse 3.5.1 with all required plug-ins installed. JBoos Tools installed from http://download.jboss.org/jbosstools/updates/nightly/trunk/ Reporter: Yura Zhishko Assignee: Alexey Kazakov Priority: Critical 1) Install Eclipse 3.5.1 with all required plug-ins. 2) Help -> Install New Software. 3) Install JBT using link from environment description. 4) Import attached project into workspace. 5) Wait until Updating Maven Dependencies doesn't start. 6) RMB on a project 7) JBoss Tools -> Add JSF Capabilities 8) Press Next > 9) Press Finish RESULT: Dialog and Eclipse are blocked for user actions while Updating is running (screenshot-1). -- 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

14 years, 8 months

4
10
0 / 0

[JBoss JIRA] Created: (JBIDE-4685) "Add JSF Capabilities" improvements proposals

by Maxim Areshkau (JIRA)

"Add JSF Capabilities" improvements proposals --------------------------------------------- Key: JBIDE-4685 URL: https://jira.jboss.org/jira/browse/JBIDE-4685 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor core Reporter: Maxim Areshkau Assignee: Maxim Areshkau Fix For: 3.1.0.M3 Add JSF Capabilities menu should be redesigned. -- 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

14 years, 8 months

7
23
0 / 0

[JBoss JIRA] Created: (JBIDE-1893) Can't add *.xhtml template using Preferenses -> JBossTools->Web->JSF->JSF Pages

by Anton Klimkovich (JIRA)

Can't add *.xhtml template using Preferenses -> JBossTools->Web->JSF->JSF Pages ------------------------------------------------------------------------------- Key: JBIDE-1893 URL: http://jira.jboss.com/jira/browse/JBIDE-1893 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 2.0.1 Reporter: Anton Klimkovich Priority: Minor EXECUTE: Create JSF with Facelets kickstart project EXECUTE: Create JSF1.2 kickstart project EXECUTE: Window->Preferenses -> JBossTools->Web->JSF->JSF Pages EXECUTE: Press Add button EXECUTE: Press Browse button ASSERT: Two projects available: JSF with Facelets and JSF1.2 kickstarts EXECUTE: Expand pages folder in JSF with Facelets project ASSERT: *.xhtml pages shoul be available . FAILURE: *.xhtml pages are not available . -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

4
5
0 / 0

[JBoss JIRA] Created: (RHDS-321) Warning in the case of incorrect bean references

by Florian Marwede (JIRA)

Warning in the case of incorrect bean references ------------------------------------------------ Key: RHDS-321 URL: http://jira.jboss.com/jira/browse/RHDS-321 Project: Red Hat Developer Studio Issue Type: Feature Request Reporter: Florian Marwede Priority: Minor See forum thread. The warning should behave like a eclipse warning (yellow underline in the editor and also appear in problem view). It must be configurable, so you can switch it off when you manage your beans in a way RHDS can't analyze. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

5
7
0 / 0

[JBoss JIRA] Created: (JBIDE-2438) Support for backing bean configuration in Spring application context

by Claus Nyhus (JIRA)

Support for backing bean configuration in Spring application context -------------------------------------------------------------------- Key: JBIDE-2438 URL: http://jira.jboss.com/jira/browse/JBIDE-2438 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jsp/jsf/xml source editing Reporter: Claus Nyhus Hi, When using Spring with JSF it is very compelling to define backing beans in Springs application context (either via XML configuration or annotations) rather than in faces-config.xml. The downside of this is that you cannot use completion on properties from the backing beans in JBoss tools when editing JSF pages (e.g. facelets files). It would be very nice if JBoss Tools could pick up backing beans from a Spring application context and treat them the same way backing beans from faces-config.xml is handled. Cheers /Claus References for defining backing beans in an Spring application context: http://prime.com.tr/cagataycivici/?p=92 http://prime.com.tr/cagataycivici/?p=94 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5358) Change how beans are expanded when added via the bean add dialog

by Tom Fennelly (JIRA)

Change how beans are expanded when added via the bean add dialog ---------------------------------------------------------------- Key: JBIDE-5358 URL: https://jira.jboss.org/jira/browse/JBIDE-5358 Project: Tools (JBoss Tools) Issue Type: Task Components: smooks Reporter: Tom Fennelly Fix For: 3.1.0.GA At the moment, we iterate down the object model and add all sub-objects etc. This is looking a bit messy because: 1. It requires the user to expand out a tree in the bottom half of the bean creation dialog, selecting the sub-domain objects he/she wants to be added. 2. The beans all land on the canvas at the one time, which requires a load of rearranging etc I think it would be nicer for the user if only the bean class entered in the Bean Creation wizard was dropped on the canvas, with all it's properties, but not drop in the sub-domain classes, wired together etc (as now). If some of the properties are for sub-domain objects, the user should be able to right-click and add, resulting in that sub-domain object being added etc etc. The user can expand it out as they want. -- 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

14 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5404) Smooks Drag and Drop Editor

by Jim Tyrrell (JIRA)

Smooks Drag and Drop Editor --------------------------- Key: JBIDE-5404 URL: https://jira.jboss.org/jira/browse/JBIDE-5404 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Jim Tyrrell Just saw a demo here: http://www.screencast.com/users/tfennelly/folders/Camtasia/media/4b184ca6... It would be nice to be able to reorder fields on either side of the graph when you are doing the Java Mapping. In other words it would be nice to not have to have lines cross if at all possible. It would be even better if this would be automatic that fields in an object would order the same way in both views. It would also be nice that dragging a field into a mapping would prompt for a dialogue box to ask/see if all the other like mappings should be applied rather then having to apply them. Quickstarts around the smooks editor that are easily importable into JBDS w/o any messing around with anything. -- 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

14 years, 8 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5294) Add ability to control output result types in Run Configuration

by Tom Fennelly (JIRA)

Add ability to control output result types in Run Configuration --------------------------------------------------------------- Key: JBIDE-5294 URL: https://jira.jboss.org/jira/browse/JBIDE-5294 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: smooks Reporter: Tom Fennelly Fix For: 3.1.0.GA At the moment, it's outputting everything, which can be information overload. -- 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

14 years, 8 months

2
6
0 / 0

[JBoss JIRA] Created: (JBIDE-5233) Move properties from the "Options" page into the Properties view

by Brian Fitzpatrick (JIRA)

Move properties from the "Options" page into the Properties view ---------------------------------------------------------------- Key: JBIDE-5233 URL: https://jira.jboss.org/jira/browse/JBIDE-5233 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: smooks Reporter: Brian Fitzpatrick Assignee: Brian Fitzpatrick Once we get JBIDE-5203 completed, we can add these optional/global options to the Properties view instead of taking up a page for them if we decided the page is overkill. But we need to have the whole editor wired to the Outline view and then wire the Properties pages to both objects in the editor and in the outline view to make this work. This is not for the JBDS 3.1 release. Future work. -- 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

14 years, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5203) Smooks editor - wire up non-source pages to Outline view

by Brian Fitzpatrick (JIRA)

Smooks editor - wire up non-source pages to Outline view -------------------------------------------------------- Key: JBIDE-5203 URL: https://jira.jboss.org/jira/browse/JBIDE-5203 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: smooks Affects Versions: 3.1.0.M4 Reporter: Brian Fitzpatrick Assignee: Brian Fitzpatrick Fix For: 3.1.0.CR1 Hook up the non-source pages to the Outline view This is a "nice to have" - but not critical for the first release. But it should be looked at in the future. -- 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

14 years, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5440) Update Smooks Examples to Minimize User Steps

by Brian Fitzpatrick (JIRA)

Update Smooks Examples to Minimize User Steps --------------------------------------------- Key: JBIDE-5440 URL: https://jira.jboss.org/jira/browse/JBIDE-5440 Project: Tools (JBoss Tools) Issue Type: Task Components: smooks Affects Versions: 3.1.0.GA Reporter: Brian Fitzpatrick Assignee: Tom Fennelly Fix For: 3.1.0.GA We have a bunch of quickstarts - but all the quickstarts require that you manually set the sample input data when you import them. can we tweak those to include the metadata for the sample input? This would include not only the samples from the Smooks project, but the ESB samples that include Smooks. This is basically just making sure that the sample input data is configured in the configuration so the user doesn't have to configure it by hand. -- 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

14 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-5295) Add ability to configure an Execution Report on Run Configurations

by Tom Fennelly (JIRA)

Add ability to configure an Execution Report on Run Configurations ------------------------------------------------------------------ Key: JBIDE-5295 URL: https://jira.jboss.org/jira/browse/JBIDE-5295 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: smooks Reporter: Tom Fennelly Fix For: 3.1.0.GA -- 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

14 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-3255) Unhelpful error message if users IDE doesn't define the "M2_REPO" variable

by Tom Fennelly (JIRA)

Unhelpful error message if users IDE doesn't define the "M2_REPO" variable -------------------------------------------------------------------------- Key: JBIDE-3255 URL: https://jira.jboss.org/jira/browse/JBIDE-3255 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Reporter: Tom Fennelly Assignee: Xue Peng Priority: Minor Fix For: 3.0.0.cr1 I created an eclipse project using maven, which links in the dependencies via the maven repo. It references the maven repo via the "M2_REPO" variable. When this variable wasn't set, I was unable to set the source and target java classes for the source and target models - just came back with an error ... "unable to load class ''" (i.e. empty quoted string). The classes I was trying to set were in the actual project source (i.e. not in any of the linked in dependecies), so I'm not sure what the issue was. Might be a good thing to ass this in a FAQ or Known Issues doc, or even as a "possible cause" message addition to the "unable to load class..." error message. -- 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

14 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-5563) Wrong context menu in "Selected Task Details" when xml model is selected

by Jiri Peterka (JIRA)

Wrong context menu in "Selected Task Details" when xml model is selected ------------------------------------------------------------------------ Key: JBIDE-5563 URL: https://jira.jboss.org/jira/browse/JBIDE-5563 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.1.0.CR1 Environment: Linux 64-bit, Sun JDK 1.6, JbossTools-3.1.0.v200912171816M-H185-RC1 Reporter: Jiri Peterka Fix For: 3.1.0.CR2 1. Have a smooks configuration 2. Define Input task and Java Mapping 3. In Java Mapping Selected Task Details 4. When click on blank are for adding java class, context menu is set for element Desired behaviour: Context menu with "Add Java Class" item should be available whenever user click on blank area no matter what -- 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

14 years, 8 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-4055) Bad warning for "Class not found" in Smooks Editor.

by Aliaksey Nis (JIRA)

Bad warning for "Class not found" in Smooks Editor. --------------------------------------------------- Key: JBIDE-4055 URL: https://jira.jboss.org/jira/browse/JBIDE-4055 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.1.0 Environment: WindowsXP SP2 JBoss Tools Version: 3.1.0 Build id: JBossTools-ALL-win32-3.1.0.Alpha1-N200903181801-H41 JRE 1.5_08 Reporter: Aliaksey Nis Priority: Optional EXECUTE: Create Smooks configuration file XML-to-Java. EXECUTE: Graph view. Press "target select" link. Choose Java. Press "Add class" button. EXECUTE: Select Authenticate - sun.text.ICUBinary. Press Finish. FAILURE: Look at screenshot. Bad warning in title appears. I think it will be better if warning will be more informative. -- 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

14 years, 8 months

5
12
0 / 0

[JBoss JIRA] Created: (JBIDE-5356) Unmapped Java bindings being added to to <bean> configs

by Tom Fennelly (JIRA)

Unmapped Java bindings being added to to <bean> configs ------------------------------------------------------- Key: JBIDE-5356 URL: https://jira.jboss.org/jira/browse/JBIDE-5356 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Reporter: Tom Fennelly Fix For: 3.1.0.CR1, 3.1.0.GA Bean value/wiring configs are added for all bean properties, even if no mappings were made onto the property e.g. <jb:bindings beanId="header" class="example.model.Header" createOnElement="json"> <jb:value property="date"/> </jb:bindings> Note... it is not mandatory for a mapping to be made onto a bean property!! -- 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

14 years, 8 months

4
11
0 / 0

[JBoss JIRA] Created: (JBIDE-3206) To test smooks tools with the smooks config file of ESB Quick Start example project

by Xue Peng (JIRA)

To test smooks tools with the smooks config file of ESB Quick Start example project ----------------------------------------------------------------------------------- Key: JBIDE-3206 URL: https://jira.jboss.org/jira/browse/JBIDE-3206 Project: Tools (JBoss Tools) Issue Type: Task Components: smooks Affects Versions: 3.0.0.cr1 Reporter: Xue Peng Assignee: Xue Peng Fix For: 3.0.0.cr1 To test smooks tools with the smooks config file of ESB Quick Start example project -- 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

14 years, 8 months

3
9
0 / 0

[JBoss JIRA] Created: (JBIDE-5156) Updates to the Smooks Config Editor source page need to be reflected in the editor pages

by Brian Fitzpatrick (JIRA)

Updates to the Smooks Config Editor source page need to be reflected in the editor pages ---------------------------------------------------------------------------------------- Key: JBIDE-5156 URL: https://jira.jboss.org/jira/browse/JBIDE-5156 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.1.0.M4 Reporter: Brian Fitzpatrick Assignee: Xue Peng Priority: Critical Fix For: 3.1.0.CR1 Updates to the source page need to be reflected in the editor pages. We need to be able to "round trip" between the source page and the rest of the editor. -- 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

14 years, 8 months

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-5428) support undo/redo in tasks map viewer.

by Xue Peng (JIRA)

support undo/redo in tasks map viewer. -------------------------------------- Key: JBIDE-5428 URL: https://jira.jboss.org/jira/browse/JBIDE-5428 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: smooks Affects Versions: 3.1.0.GA Reporter: Xue Peng Assignee: Xue Peng Fix For: 3.1.0.GA support undo/redo in tasks map viewer. -- 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

14 years, 8 months

3
9
0 / 0

[JBoss JIRA] Created: (JBIDE-5420) Keyboard navigation in Smooks Editor

by Brian Fitzpatrick (JIRA)

Keyboard navigation in Smooks Editor ------------------------------------ Key: JBIDE-5420 URL: https://jira.jboss.org/jira/browse/JBIDE-5420 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: smooks Affects Versions: 3.1.0.GA Reporter: Brian Fitzpatrick Assignee: Xue Peng Fix For: 3.1.1 Keyboard navigation is lacking in key parts of the editor. Though you can tab around the editor for the most part, you cannot tab into the graphical areas (i.e. the tasks graph, java mapping graph, or template graph) or navigate once you're there. We should also look at adding accelerators to commonly used menu items like Add and Delete for the popup menus on graphs. -- 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

14 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-4174) Create Action for "Param" element to add anytype nodes.

by Xue Peng (JIRA)

Create Action for "Param" element to add anytype nodes. ------------------------------------------------------- Key: JBIDE-4174 URL: https://jira.jboss.org/jira/browse/JBIDE-4174 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: smooks Affects Versions: 3.1.0 Reporter: Xue Peng Assignee: Xue Peng Fix For: 3.1.0 Create Action for "Param" element to add anytype nodes. -- 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

14 years, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-4217) Write unit tests for smooks configuration editor

by Xue Peng (JIRA)

Write unit tests for smooks configuration editor ------------------------------------------------ Key: JBIDE-4217 URL: https://jira.jboss.org/jira/browse/JBIDE-4217 Project: Tools (JBoss Tools) Issue Type: Task Components: smooks Reporter: Xue Peng Assignee: Xue Peng Write unit tests for smooks configuration editor. -- 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

14 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-3974) Use the shortes unique selector path instead of the full selector path

by Maurice Zeijen (JIRA)

Use the shortes unique selector path instead of the full selector path ---------------------------------------------------------------------- Key: JBIDE-3974 URL: https://jira.jboss.org/jira/browse/JBIDE-3974 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: smooks Affects Versions: 3.0.0.CR2 Reporter: Maurice Zeijen Currently the graph editor uses the full selector path. Always using the full selector path may seem the safest path but it can have serious performance implications for Smooks. A binding with a short selector is resolved faster then one with a long selector. It would be better if the graph editor would use the shortest unique selector path. Example: <order> <customer> <id>432</id> </customer> <order-items> <order-item> <id>111</id> <quantity>2</quantity> <price>8.90</price> </order-item> </order-items> </order> If you would bind the 'id' element of order-item to some bean then currently the following path would be generated by the graph editor: order order-items order-item id If the graph editor would generate the shortest unique path, then it would be: order-item id -- 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

14 years, 8 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-5525) AutoLayout speed is too slowly

by Xue Peng (JIRA)

AutoLayout speed is too slowly ------------------------------ Key: JBIDE-5525 URL: https://jira.jboss.org/jira/browse/JBIDE-5525 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.1.0.GA Environment: Fedora 11 Reporter: Xue Peng Assignee: Xue Peng Fix For: 3.1.0.GA Then autolayout the figures of mapping viewer , the movement speed of the figure is very very slow , it seems each auto layout action need 5+ seconds. This issue I found in fedora as far , in the windows vista or xp , it's OK. -- 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

14 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-4425) Create new poperty in bean

by Krasimir Goutcev (JIRA)

Create new poperty in bean -------------------------- Key: JBIDE-4425 URL: https://jira.jboss.org/jira/browse/JBIDE-4425 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: smooks Reporter: Krasimir Goutcev It will be useful when we select property for binding we have possibility to add/create a new one. See picture -- 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

14 years, 8 months

4
9
0 / 0

[JBoss JIRA] Created: (JBIDE-4753) Problems with Add JSF capabilites dialog

by Maxim Areshkau (JIRA)

Problems with Add JSF capabilites dialog ---------------------------------------- Key: JBIDE-4753 URL: https://jira.jboss.org/jira/browse/JBIDE-4753 Project: JBoss Tools Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.1.0.M3 Reporter: Maxim Areshkau Assignee: Viacheslav Kabanovich -- 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

14 years, 8 months

5
10
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 December 2009