December 2009 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-4402) Some input files use unchecked or unsafe operations. Recompile with -Xlint:unchecked for details.

by Nick Boldt (JIRA)

Some input files use unchecked or unsafe operations. Recompile with -Xlint:unchecked for details. ------------------------------------------------------------------------------------------------- Key: JBIDE-4402 URL: https://jira.jboss.org/jira/browse/JBIDE-4402 Project: Tools (JBoss Tools) Issue Type: Task Affects Versions: 3.1.0.M1 Reporter: Nick Boldt http://hudson.qa.jboss.com/hudson/view/DevStudio/job/devstudio-nightly-2.... [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. Suggest reviewing your sources w/ PDE API Tools and compiling locally to see what these unsafe/unchecked operations are. -- 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

16 years, 4 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-5274) Copy/Move JBT project configuration dialogs to Project->Configure menu.

by Alexey Kazakov (JIRA)

Copy/Move JBT project configuration dialogs to Project->Configure menu. ----------------------------------------------------------------------- Key: JBIDE-5274 URL: https://jira.jboss.org/jira/browse/JBIDE-5274 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.1.0.CR1 -- 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

16 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBDS-1003) the latest builds of JBDS RC1 are broken. EAP 5 isn't included in build.

by Anton Klimkovich (JIRA)

the latest builds of JBDS RC1 are broken. EAP 5 isn't included in build. ------------------------------------------------------------------------- Key: JBDS-1003 URL: https://jira.jboss.org/jira/browse/JBDS-1003 Project: JBoss Developer Studio Issue Type: Bug Components: Build Affects Versions: 3.0.0.CR1 Environment: jbdevstudio-eap-win32-3.0.0.v200912042231M-H29-RC1 Reporter: Anton Klimkovich Priority: Critical Builds from http://reports.qa.atl.jboss.com/binaries/RHDS/builds/release/3.0.0.RC1 are broken. EAP 5 isn't included in build jbdevstudio-eap-win32-3.0.0.v200912042231M-H29-RC1 Start splashscreen with logo is missed. Seam perspective isn't loaded by default. -- 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

16 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-5574) XPCOM exception under Linux 64 after closing a file

by Yura Zhishko (JIRA)

XPCOM exception under Linux 64 after closing a file --------------------------------------------------- Key: JBIDE-5574 URL: https://jira.jboss.org/jira/browse/JBIDE-5574 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.1.0.CR1 Reporter: Yura Zhishko Assignee: Yura Zhishko Fix For: 3.1.0.CR2 After closing a file in Linux 64 I've got the next exception: org.mozilla.xpcom.XPCOMException: The function "removeProgressListener" returned an error condition (0x80004005) at org.mozilla.xpcom.internal.XPCOMJavaProxy.callXPCOMMethod(Native Method) at org.mozilla.xpcom.internal.XPCOMJavaProxy.invoke(XPCOMJavaProxy.java:143) at $Proxy6.removeProgressListener(Unknown Source) at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor$2.widgetDisposed(XulRunnerEditor.java:171) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:117) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1200) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1185) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1025) at org.eclipse.swt.browser.Mozilla$6.handleEvent(Mozilla.java:1484) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1200) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1181) at org.eclipse.swt.widgets.Widget.release(Widget.java:1044) at org.eclipse.swt.widgets.Control.release(Control.java:3293) at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1185) at org.eclipse.swt.widgets.Widget.release(Widget.java:1047) at org.eclipse.swt.widgets.Control.release(Control.java:3293) at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1185) at org.eclipse.swt.widgets.Widget.release(Widget.java:1047) at org.eclipse.swt.widgets.Control.release(Control.java:3293) at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1185) at org.eclipse.swt.widgets.Widget.release(Widget.java:1047) at org.eclipse.swt.widgets.Control.release(Control.java:3293) at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1185) at org.eclipse.swt.widgets.Widget.release(Widget.java:1047) at org.eclipse.swt.widgets.Control.release(Control.java:3293) at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1185) at org.eclipse.swt.widgets.Widget.release(Widget.java:1047) at org.eclipse.swt.widgets.Control.release(Control.java:3293) at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1185) at org.eclipse.swt.widgets.Widget.release(Widget.java:1047) at org.eclipse.swt.widgets.Control.release(Control.java:3293) at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1185) at org.eclipse.swt.widgets.Widget.release(Widget.java:1047) at org.eclipse.swt.widgets.Control.release(Control.java:3293) at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1185) at org.eclipse.swt.widgets.Widget.release(Widget.java:1047) at org.eclipse.swt.widgets.Control.release(Control.java:3293) at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1185) at org.eclipse.swt.widgets.Widget.release(Widget.java:1047) at org.eclipse.swt.widgets.Control.release(Control.java:3293) at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1185) at org.eclipse.swt.widgets.Widget.release(Widget.java:1047) at org.eclipse.swt.widgets.Control.release(Control.java:3293) at org.eclipse.swt.widgets.Widget.dispose(Widget.java:446) at org.eclipse.ui.internal.PartPane.dispose(PartPane.java:180) at org.eclipse.ui.internal.WorkbenchPartReference.dispose(WorkbenchPartReference.java:681) at org.eclipse.ui.internal.WorkbenchPage.disposePart(WorkbenchPage.java:1715) at org.eclipse.ui.internal.WorkbenchPage.handleDeferredEvents(WorkbenchPage.java:1422) at org.eclipse.ui.internal.WorkbenchPage.deferUpdates(WorkbenchPage.java:1406) at org.eclipse.ui.internal.WorkbenchPage.closeEditors(WorkbenchPage.java:1380) at org.eclipse.ui.internal.WorkbenchPage.closeEditor(WorkbenchPage.java:1435) at org.eclipse.ui.internal.EditorPane.doHide(EditorPane.java:61) at org.eclipse.ui.internal.PartStack.close(PartStack.java:543) at org.eclipse.ui.internal.EditorStack.close(EditorStack.java:206) at org.eclipse.ui.internal.PartStack$1.close(PartStack.java:122) at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation$1.handleEvent(TabbedStackPresentation.java:83) at org.eclipse.ui.internal.presentations.util.AbstractTabFolder.fireEvent(AbstractTabFolder.java:270) at org.eclipse.ui.internal.presentations.util.AbstractTabFolder.fireEvent(AbstractTabFolder.java:279) at org.eclipse.ui.internal.presentations.defaultpresentation.DefaultTabFolder.access$1(DefaultTabFolder.java:1) at org.eclipse.ui.internal.presentations.defaultpresentation.DefaultTabFolder$1.closeButtonPressed(DefaultTabFolder.java:70) at org.eclipse.ui.internal.presentations.PaneFolder.notifyCloseListeners(PaneFolder.java:626) at org.eclipse.ui.internal.presentations.PaneFolder$3.close(PaneFolder.java:206) at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:2199) at org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFolder.java:327) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3493) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3112) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) 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:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) at org.eclipse.equinox.launcher.Main.main(Main.java:1287) -- 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

16 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5569) Issues around Autocreation of hibernate console config on seam+jpa projects

by Max Rydahl Andersen (JIRA)

Issues around Autocreation of hibernate console config on seam+jpa projects --------------------------------------------------------------------------- Key: JBIDE-5569 URL: https://jira.jboss.org/jira/browse/JBIDE-5569 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.0.CR1 Reporter: Max Rydahl Andersen Assignee: Dmitry Geraskov Fix For: 3.1.0.CR2 >From JBIDE-4985: The location of the .launch is only different when JPA facet is selected and hibernate platform enabled. We need to look at that for CR2. For CR1 not important. Issue is to get uniform projects so locations of file should be stable as possible. In CR2 possibly introduce an option about hat behavior we 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

16 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5496) new runtime wizard very annoying, version not updated

by Rob Stryker (JIRA)

new runtime wizard very annoying, version not updated ----------------------------------------------------- Key: JBIDE-5496 URL: https://jira.jboss.org/jira/browse/JBIDE-5496 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.1.0.M4 Reporter: Rob Stryker Assignee: Denny Xu Fix For: 3.1.0.CR1 When creating a new runtime, if I point to soa-p-4.3.0 directory, and select 4.7 as the version, it rpesents an error and tells me the version is wrong. But it does not select the correct one. So then I try to set version to 4.6, and it still says error, so I try 4.5, and still error, and so I try 4.4 and it works. This is very annoying for the user -- 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

16 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5410) Can not deploy ESB 4.7 project to server using Run As -> Run on Server

by Denny Xu (JIRA)

Can not deploy ESB 4.7 project to server using Run As -> Run on Server ---------------------------------------------------------------------- Key: JBIDE-5410 URL: https://jira.jboss.org/jira/browse/JBIDE-5410 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.1.0.M4 Reporter: Denny Xu Assignee: Denny Xu Fix For: 3.1.0.CR1 I created a new ESB Project using latest nightly build of JBoss Tools and selected 4.7 as the JBoss ESB version and Target Runtime of JBoss 5.1 Runtime. When I try to deploy the project on the server (Run As -> Run on Server) I get the message " The selection is not within a valid module". -- 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

16 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5453) When initializer is created, it appears to be selected but its text is not displayed

by Brad Maxwell (JIRA)

When initializer is created, it appears to be selected but its text is not displayed ------------------------------------------------------------------------------------ Key: JBIDE-5453 URL: https://jira.jboss.org/jira/browse/JBIDE-5453 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpm Affects Versions: 3.1.0.M4 Environment: Eclipse 3.5 jee-galileo-SR1 + JBossTools 3.1 v1.0.0.v200912010817N-H2-RC1 Reporter: Brad Maxwell Priority: Minor 1) Add an Assign 2) Click Details for the Assign 3) Click new to create a new mapping 4) Map input.payload/input to output.payload/result 5) Click away 6) It will ask you if you want to create an initializer 7) Click Yes 8) It will create a mapping above the "Variable to Variable" called "Fixed Value to Variable" 9) The "Fixed Value to Variable" appears to be selected / highlighted, however what is displayed in the text box is the text for the "Variable to Variable" It should either update the text box to show the "Fixed Value to Variable" or it should show the "Variable to Variable" selected. -- 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

16 years, 4 months

2
6
0 / 0

[JBoss JIRA] Created: (JBDS-729) generate plugin dependencies in eclipse.ini/config.ini rather than hardcoding versions

by Nick Boldt (JIRA)

generate plugin dependencies in eclipse.ini/config.ini rather than hardcoding versions -------------------------------------------------------------------------------------- Key: JBDS-729 URL: https://jira.jboss.org/jira/browse/JBDS-729 Project: Developer Studio Issue Type: Bug Affects Versions: 2.0.1 Reporter: Nick Boldt Assignee: Denis Golovin >From Denis: > Bumped in JBDS launch problem, the reason is - migration to Eclipse 3.5 wasn't done for installer. Fixed for linux version, but need find a way to update original config.ini/eclipse.ini files during build adding xsl.transformation plug-ins in it without keeping a copies of ini files -- 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

16 years, 4 months

3
22
0 / 0

[JBoss JIRA] Created: (JBDS-1017) Deleted Server Runtimes appear in Seam Wizard

by Joshua Wulf (JIRA)

Deleted Server Runtimes appear in Seam Wizard --------------------------------------------- Key: JBDS-1017 URL: https://jira.jboss.org/jira/browse/JBDS-1017 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 3.0.0.M4, 3.0.0.CR1 Environment: Fedora 12 32-bit x86 Reporter: Joshua Wulf After deleting a server from the Servers or JBoss Server View window, that server's runtime still appears in the Seam Web Project wizard. This is persistent, even after JBDS / Eclipse is closed down and restarted. -- 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

16 years, 4 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-4985) New seam projects should configure hibernate tools with the DTP connection

by Max Rydahl Andersen (JIRA)

New seam projects should configure hibernate tools with the DTP connection -------------------------------------------------------------------------- Key: JBIDE-4985 URL: https://jira.jboss.org/jira/browse/JBIDE-4985 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate, Seam Reporter: Max Rydahl Andersen Assignee: Alexey Kazakov Fix For: 3.1.0.M4, 3.1.0.CR1 Now that hibernate console supports DTP connection profiles shouldn't we start using that for our Seam projects ? Removing the need to have connection info in the hibernate-console.properties ? (the other fields related to tx and others still need to there though) -- 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

16 years, 4 months

4
17
0 / 0

[JBoss JIRA] Created: (JBIDE-5555) SSH server has TODO in server editor

by Max Rydahl Andersen (JIRA)

SSH server has TODO in server editor ------------------------------------ Key: JBIDE-5555 URL: https://jira.jboss.org/jira/browse/JBIDE-5555 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Reporter: Max Rydahl Andersen Assignee: Rob Stryker Priority: Blocker Fix For: 3.1.0.CR1 -- 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

16 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBDS-962) Unable to find feature.xml in directory when JBDS start .

by Svetlana Yasenovich (JIRA)

Unable to find feature.xml in directory when JBDS start . --------------------------------------------------------- Key: JBDS-962 URL: https://jira.jboss.org/jira/browse/JBDS-962 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 3.0.0.M4 Environment: WindowsXP SP2 JBoss Developer Studio Version: 3.0.0.M4 Build id:jbdevstudio-eap-win32-3.0.0.v200911180352M-H96-M4 JRE 1.6 Reporter: Svetlana Yasenovich EXECUTE: Start JBDS. FAILURE: Exception related to missed feature thrown in error log: Unable to find feature.xml in directory: C:\jbdevstudio\studio\eclipse\features\com.jboss.jbds.product.feature_3.1.0.v200911180352M-H96-M4 -- 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

16 years, 4 months

3
9
0 / 0

[JBoss JIRA] Created: (JBIDE-4611) To aid in test automation - always have a descriptive title for dialogs

by Len DiMaggio (JIRA)

To aid in test automation - always have a descriptive title for dialogs ----------------------------------------------------------------------- Key: JBIDE-4611 URL: https://jira.jboss.org/jira/browse/JBIDE-4611 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: QA Reporter: Len DiMaggio Fix For: 2.1.3 I'm developing EGT tests for JBDS-BRMS and have hit a limitation with SWTBot - the tool can only extract title text from eclipse dialogs. As a result, any dialogs that have blank title text cannot be reliably located. See the attached screenshots - the 'error' dialog has a title that can be found by SWTBot - but a better title would make test automation easier. The properties dialog has blank text in its title. -- 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

16 years, 4 months

4
14
0 / 0

[JBoss JIRA] Created: (JBIDE-5423) Smooks editor takes up too much room on screen

by Brian Fitzpatrick (JIRA)

Smooks editor takes up too much room on screen ---------------------------------------------- Key: JBIDE-5423 URL: https://jira.jboss.org/jira/browse/JBIDE-5423 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.GA Reporter: Brian Fitzpatrick Assignee: Xue Peng Fix For: 3.1.0.GA Size issues in the Task configuration area need to be resolved (by GA if possible, by 3.1.1 if not) - Remove unnecessary fields - Simplify CSV configuration (JBIDE-5422) - All "Input Configuration" panels need to be scrollable - sometimes they are and sometimes they're not, which is confusing -- 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

16 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5399) Update CA-related JUnit tests due to satisfy changes made in JBIDE-4877 for CA

by Victor Rubezhny (JIRA)

Update CA-related JUnit tests due to satisfy changes made in JBIDE-4877 for CA ------------------------------------------------------------------------------- Key: JBIDE-5399 URL: https://jira.jboss.org/jira/browse/JBIDE-5399 Project: Tools (JBoss Tools) Issue Type: Task Reporter: Victor Rubezhny CA-related JUnit tests are to be updated due to satisfy changes made in JBIDE-4877 for CA -- 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

16 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5211) Same letter shortcut in import dialog

by Jiri Peterka (JIRA)

Same letter shortcut in import dialog -------------------------------------- Key: JBIDE-5211 URL: https://jira.jboss.org/jira/browse/JBIDE-5211 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Jiri Peterka Priority: Minor Steps: Import -> Imporj JSF In "Import JSF Project" (ImportProjectWizad) there are buttons &Back and &Browse which share the same "B' shortcut. It should be modified. -- 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

16 years, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-5268) Same letter shortcut in Hibernate Configuration File Dialog

by Jiri Peterka (JIRA)

Same letter shortcut in Hibernate Configuration File Dialog ------------------------------------------------------------ Key: JBIDE-5268 URL: https://jira.jboss.org/jira/browse/JBIDE-5268 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.1.0.CR1 Environment: Linux 32,64 Reporter: Jiri Peterka Assignee: Viacheslav Kabanovich Priority: Minor Fix For: 3.1.0.GA Steps: Import -> Import JSF In "Import JSF Project" (ImportProjectWizad) there are buttons &Back and &Browse which share the same "B' shortcut. It should be modified. -- 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

16 years, 4 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-5477) Seam 1.2 WAR project context error during deployment

by Jiri Peterka (JIRA)

Seam 1.2 WAR project context error during deployment ---------------------------------------------------- Key: JBIDE-5477 URL: https://jira.jboss.org/jira/browse/JBIDE-5477 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.0.CR1 Environment: Linux 64, Version: 3.1.0.v200912141523M-H176-RC1 Reporter: Jiri Peterka Fix For: 3.1.0.CR1 Create Seam 1.2 WAR Project Deploy on EAP 4.3 You will see: 9:23:26,552 ERROR [viewhandler] Error Rendering View[/home.xhtml] java.lang.IllegalStateException: No active application context at org.jboss.seam.core.Pages.instance(Pages.java:470) at org.jboss.seam.ui.HtmlLink.encodeBegin(HtmlLink.java:98) at org.ajax4jsf.framework.renderer.RendererBase.renderChild(RendererBase.java:280) at org.richfaces.renderkit.html.ToolBarGroupRenderer.encodeChildren(ToolBarGroupRenderer.java:68) at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837) at org.ajax4jsf.framework.renderer.RendererBase.renderChild(RendererBase.java:282) at org.richfaces.renderkit.html.ToolBarRendererBase.encodeChildren(ToolBarRendererBase.java:81) at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:837) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:930) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:933) at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:571) at org.ajax4jsf.framework.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108) at org.ajax4jsf.framework.ajax.AjaxViewHandler.renderView(AjaxViewHandler.java:229) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:110) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:63) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:57) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:60) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:79) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:84) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:96) at org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:220) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:636) -- 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

16 years, 4 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5553) ESB Editor - SOAP Proxy Action needs the clientCredentialsRequired property to appear

by Brian Fitzpatrick (JIRA)

ESB Editor - SOAP Proxy Action needs the clientCredentialsRequired property to appear ------------------------------------------------------------------------------------- Key: JBIDE-5553 URL: https://jira.jboss.org/jira/browse/JBIDE-5553 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.1.0.GA Reporter: Brian Fitzpatrick Assignee: Viacheslav Kabanovich For the SOAP Proxy Action, we need to show the optional clientCredentialsRequired property in the UI. The default is "true". >From the Programmer's Guide: * clientCredentialsRequired (optional; default is "true"): Whether the Basic Auth credentials are required to come from the end client, or if the credentials specified inside file can be used instead. -- 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

16 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5539) War Security

by Burr Sutter (JIRA)

War Security ------------ Key: JBIDE-5539 URL: https://jira.jboss.org/jira/browse/JBIDE-5539 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Environment: jbdevstudio-win32-3.0.0.v200912111227M-H41-RC1 Windows Vista 64-bit Reporter: Burr Sutter Attachments: War_Security.jpg "War" should be "WAR" Or perhaps simply "Web" in this case, See screenshot -- 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

16 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5502) New ESB File wizard still uses old (Seam?!) icon

by Max Rydahl Andersen (JIRA)

New ESB File wizard still uses old (Seam?!) icon ------------------------------------------------ Key: JBIDE-5502 URL: https://jira.jboss.org/jira/browse/JBIDE-5502 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.1.0.CR1 Reporter: Max Rydahl Andersen Assignee: Denny Xu Priority: Critical Fix For: 3.1.0.GA JBIDE-4730 only seem to have updated the new esb project wizard, not the ESB File wizard. Should also check if there are other ESB related wizards within the editor that should be updated to use the ESB icon and not just the non-related Seam icon! -- 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

16 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5523) In the Details property tab of onMessage element, there are reduplicate variable combo boxes

by Feng Qian (JIRA)

In the Details property tab of onMessage element, there are reduplicate variable combo boxes -------------------------------------------------------------------------------------------- Key: JBIDE-5523 URL: https://jira.jboss.org/jira/browse/JBIDE-5523 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpm Reporter: Feng Qian Assignee: Feng Qian Fix For: 3.1.0.GA In the Details property tab of onMessage element, there are two variable combo boxes. should remove one. -- 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

16 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5503) Module Assembly Add Reference is broken

by Max Rydahl Andersen (JIRA)

Module Assembly Add Reference is broken --------------------------------------- Key: JBIDE-5503 URL: https://jira.jboss.org/jira/browse/JBIDE-5503 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.1.0.CR1 Reporter: Max Rydahl Andersen Assignee: Rob Stryker Priority: Blocker Fix For: 3.1.0.GA Using Module Assembly on an EAR clickin add reference creates multiple errors. See attached screenshot. java.lang.NullPointerException at org.jboss.ide.eclipse.as.wtp.ui.propertypage.DependencyPageExtensionManager$ReferenceExtension.getImage(DependencyPageExtensionManager.java:109) at org.jboss.ide.eclipse.as.wtp.ui.propertypage.NewReferenceRootWizardFragment$2.getImage(NewReferenceRootWizardFragment.java:101) at org.eclipse.jface.viewers.WrappedViewerLabelProvider.getImage(WrappedViewerLabelProvider.java:117) at org.eclipse.jface.viewers.WrappedViewerLabelProvider.update(WrappedViewerLabelProvider.java:165) at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:145) at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:932) at org.eclipse.jface.viewers.AbstractTreeViewer$UpdateItemSafeRunnable.run(AbstractTreeViewer.java:102) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) .. ps. TODO text needs to go away ASAP! -- 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

16 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-5497) ESB classpath container page should have a button to manage ESB runtimes

by Rob Stryker (JIRA)

ESB classpath container page should have a button to manage ESB runtimes ------------------------------------------------------------------------ Key: JBIDE-5497 URL: https://jira.jboss.org/jira/browse/JBIDE-5497 Project: Tools (JBoss Tools) Issue Type: Task Components: esb Affects Versions: 3.1.0.M4 Reporter: Rob Stryker Assignee: Denny Xu Fix For: 3.1.0.CR1 When i'm modifying a project's build path and see an ESB runtime classpath entry which doesn't exist, I go to edit that and am brought to a screen with all possible ESB runtimes. If my workspace has none, this page is useless and I must close out the wizard, then the project preferences, then load up workspace preferences, find esb runtimes page, then add a new esb runtime. That;'s a lot of work. This page should bring me directly to the esb runtimes if I need it -- 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

16 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5087) NullPointerException when do JBoss server publish once the name of the project is changed

by Denny Xu (JIRA)

NullPointerException when do JBoss server publish once the name of the project is changed ----------------------------------------------------------------------------------------- Key: JBIDE-5087 URL: https://jira.jboss.org/jira/browse/JBIDE-5087 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.1.0.M4 Reporter: Denny Xu Assignee: Rob Stryker Fix For: 3.1.0.CR1 To produce: 1. create a WTP project, such as Web project, add to JBoss Server adapter and then publish it, it works. 2. rename the project and republish the project, got the NullPointerException: java.lang.NullPointerException at org.jboss.ide.eclipse.as.core.publishers.PublishUtil.getResources(PublishUtil.java:171) at org.jboss.ide.eclipse.as.core.publishers.PublishUtil.getResources(PublishUtil.java:175) at org.jboss.ide.eclipse.archives.webtools.modules.LocalZippedPublisherUtil.fullPublish(LocalZippedPublisherUtil.java:186) at org.jboss.ide.eclipse.archives.webtools.modules.LocalZippedPublisherUtil.publishModule(LocalZippedPublisherUtil.java:62) at org.jboss.ide.eclipse.archives.webtools.modules.WTPZippedPublisher.publishModule(WTPZippedPublisher.java:50) at org.jboss.ide.eclipse.as.core.publishers.LocalPublishMethod.publishModule(LocalPublishMethod.java:71) at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:65) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:948) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1038) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:872) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:708) at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2690) at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:272) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) -- 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

16 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-4825) Replace "Apache ODE " from all labels in BPEL plugin code with "JBoss BPEL "

by Denny Xu (JIRA)

Replace "Apache ODE " from all labels in BPEL plugin code with "JBoss BPEL " ----------------------------------------------------------------------------- Key: JBIDE-4825 URL: https://jira.jboss.org/jira/browse/JBIDE-4825 Project: Tools (JBoss Tools) Issue Type: Task Components: bpm Reporter: Denny Xu Assignee: Denny Xu Fix For: 3.1.0.M3 -- 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

16 years, 4 months

5
8
0 / 0

[JBoss JIRA] Created: (JBIDE-5506) Cannot publish ESB to server

by Max Rydahl Andersen (JIRA)

Cannot publish ESB to server ---------------------------- Key: JBIDE-5506 URL: https://jira.jboss.org/jira/browse/JBIDE-5506 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb, JBossAS Affects Versions: 3.1.0.CR1 Reporter: Max Rydahl Andersen Assignee: Denny Xu Priority: Blocker Fix For: 3.1.0.CR1 I cannot publish nor export any ESB archives. I get several errors: Dragging an .esb file to a Deploy only server or AS 5 gives me: Invalid matching rules used: 4.7/4 At deploy: java.lang.NullPointerException at org.jboss.ide.eclipse.as.core.server.internal.DeployableServer.getRuntime(DeployableServer.java:169) at org.jboss.ide.eclipse.as.core.server.internal.DeployableServer.getDeployFolder(DeployableServer.java:117) at org.jboss.ide.eclipse.as.core.publishers.PublishUtil.getDeployPath(PublishUtil.java:102) at org.jboss.ide.eclipse.as.core.publishers.JstPublisher.fullPublish(JstPublisher.java:104) at org.jboss.ide.eclipse.as.core.publishers.JstPublisher.publishModule(JstPublisher.java:93) at org.jboss.ide.eclipse.as.core.publishers.LocalPublishMethod.publishModule(LocalPublishMethod.java:71) at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:65) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:948) at org.eclipse.wst.server.core.model.ServerBe And export I simply couldn't get to work! Which combination is supposed to 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

16 years, 4 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-5199) ESB Editor - Changes for ESB 4.7

by Brian Fitzpatrick (JIRA)

ESB Editor - Changes for ESB 4.7 -------------------------------- Key: JBIDE-5199 URL: https://jira.jboss.org/jira/browse/JBIDE-5199 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: esb Affects Versions: 3.1.0.M4 Reporter: Brian Fitzpatrick Assignee: Viacheslav Kabanovich Fix For: 3.1.0.CR1 To support ESB 4.7, we have several new actions, providers, and so on that should be available in the ESB editor. 1- new provider/bus <http-provider name="HTTP-PROVIDER"> <http-bus busid="HTTP-BUS" transportGuarantee="CONFIDENTIAL"> <allowed-roles> <role name="friend" /> </allowed-roles> </http-bus> </http-provider> 2- new gateway: http-gateway (shown in webservice_proxy_security) <listeners> <http-gateway name="HTTP-GATEWAY" busidref="HTTP-BUS" urlPattern="ProxyWS/*" /> </listeners> 3- new action: org.jboss.soa.esb.actions.soap.proxy.SOAPProxy - (shown in quickstarts\webservice_proxy_basic) <action name="proxy" class="org.jboss.soa.esb.actions.soap.proxy.SOAPProxy"> <property name="wsdl" value="https://localhost:8443/webservice_proxy_security/HelloWorldWS?wsdl"/> <property name="endpointUrl" value="https://localhost:8443/webservice_proxy_security/HelloWorldWS"/> <property name="file" value="/META-INF/httpclient-8443.properties"/> </action> 4- security changes (shown in webservice_proxy_security): <globals>  <war-security method="BASIC" domain="JBossWS" />  </globals> 5- new action: xsltaction (shown in webservice_proxy_versioning) - this one should allow opening the templateFile with the XSLT editor now included in JBT/JBDS and browsing for the file <action name="proxy-transform-old-to-new" class="org.jboss.soa.esb.actions.transformation.xslt.XsltAction"> <property name="templateFile" value="/Proxy_Versioning_RequestTransform.xsl"/> <property name="failOnWarning" value="true"/> <property name="resultType" value="STRING"/> </action> 6- changes to the ContentBasedRouterAction (shown in the ESB4.7 fun_cbr) <action class="org.jboss.soa.esb.actions.ContentBasedRouter" name="ContentBasedRouter"> <property name="cbrAlias" value="Regex"/> <property name="ruleSet" value="/regex-rules.properties"/> <property name="ruleReload" value="true"/> <property name="destinations"> <route-to destination-name="blue" service-category="BlueTeam" service-name="GoBlue" /> <route-to destination-name="red" service-category="RedTeam" service-name="GoRed" /> <route-to destination-name="green" service-category="GreenTeam" service-name="GoGreen" /> </property> </action> and <action class="org.jboss.soa.esb.actions.ContentBasedRouter" name="ContentBasedRouter"> <property name="cbrAlias" value="XPath"/> <property name="destinations"> <namespace prefix="ord" uri="http://org.jboss.soa.esb/Order" /> <route-to service-category="BlueTeam" service-name="GoBlue" expression="/ord:Order[@statusCode='0']" /> <route-to service-category="RedTeam" service-name="GoRed" expression="/ord:Order[@statusCode='1']" /> <route-to service-category="GreenTeam" service-name="GoGreen" expression="/ord:Order[@statusCode='2']" /> </property> </action> -- 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

16 years, 4 months

5
17
0 / 0

[JBoss JIRA] Created: (JBDS-987) Demos size reduce

by Svetlana mukhina (JIRA)

Demos size reduce ------------------ Key: JBDS-987 URL: https://jira.jboss.org/jira/browse/JBDS-987 Project: JBoss Developer Studio Issue Type: Task Components: documentation Affects Versions: 2.1.0 Reporter: Svetlana mukhina Assignee: Svetlana mukhina Fix For: 2.1.0-doc Reduce all demos size using "Save Compressed option", check the quality of the resulted demos. -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-3690) Incorrect styleClass is applying for the tags, which use <span> wrapping

by Yura Zhishko (JIRA)

Incorrect styleClass is applying for the tags, which use <span> wrapping ------------------------------------------------------------------------ Key: JBIDE-3690 URL: https://jira.jboss.org/jira/browse/JBIDE-3690 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Templates Affects Versions: 3.0.0.CR2 Reporter: Yura Zhishko Assignee: Maxim Areshkau 1) Insert next source code into source path: <%@ taglib uri="http://richfaces.org/rich" prefix="rich"%> <%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %> <%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %> <%@ taglib uri="http://richfaces.org/a4j" prefix="a4j" %> <html> <head> <style type="text/css"> span{ color: yellow; background-color:green; } </style> </head> <body style="text-align: center"> <f:view> <h:form id="form1"> <h:outputText value="Command Link"></h:outputText> <f:verbatim>Exit</f:verbatim> <a4j:commandLink action="None" value="Begining"/> <a4j:htmlCommandLink value="Going throw"></a4j:htmlCommandLink> <h:message for="form1" /> <h:messages /> </h:form> </f:view> </body> </html> 2) Compare Visual representation in VPE to Server side (see screenshot-1). RESULT: This difference occurs due to wrapping with <span> tag of current tags. And our VPE renders this style OK. But browser doesn't wrap this tag in <span>. -- 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

16 years, 4 months

5
20
0 / 0

[JBoss JIRA] Created: (JBDS-986) In the jboss-esb.xml editor can both lists be the same order

by Jim Tyrrell (JIRA)

In the jboss-esb.xml editor can both lists be the same order ------------------------------------------------------------ Key: JBDS-986 URL: https://jira.jboss.org/jira/browse/JBDS-986 Project: JBoss Developer Studio Issue Type: Feature Request Reporter: Jim Tyrrell When right clicking on the Provider -> new I am presented a list. The order of this does not match the right click on Listner -> new List. -- 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

16 years, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-5541) Add JSF Capabilities dialog has no name and description in header if Struts Tools are not installed

by Denis Golovin (JIRA)

Add JSF Capabilities dialog has no name and description in header if Struts Tools are not installed --------------------------------------------------------------------------------------------------- Key: JBIDE-5541 URL: https://jira.jboss.org/jira/browse/JBIDE-5541 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.1.0.CR1 Reporter: Denis Golovin Assignee: Viacheslav Kabanovich Fix For: 3.1.0.CR2 If you have JBossTools installed from update site, uninstall Struts Tools to reproduce problem If you are going to test it from development environment just close all struts projects and start JBossTools -- 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

16 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5526) Attributes and Variables are not displayed in Form tree for TLD files

by Yura Zhishko (JIRA)

Attributes and Variables are not displayed in Form tree for TLD files --------------------------------------------------------------------- Key: JBIDE-5526 URL: https://jira.jboss.org/jira/browse/JBIDE-5526 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.1.0.CR1 Reporter: Yura Zhishko Assignee: Alexey Kazakov Attachments: ADD_ATTRIBUTE.jpg, ADD_TAG.jpg 1) Create a tld file 2) Open it with JBoss Tools Tag Library Editor 3) Right mouse button click on the taglib in the form tree 4) Add a new tag (ADD_TAG screenshot) 5) Right mouse button click on created tag 6) Add a new attribute (ADD_ATTRIBUTE screenshot) 7) In the emergent dialog set the Name of the feature attribute, press Finish ASSERT: The new attribute should appear in the form tree of JBT TL Editor as a child of created tag. ASSERT FAILED: The Outline shows that the attribute was successfully created but there is no any attribute for the tag if JBT Editor's form tree (NO_ATTR screenshot). P. S. The same thing happens with tag's variables. -- 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

16 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBDS-985) New ESB Project Wizard why isn't the JBoss ESB Version selected for me

by Jim Tyrrell (JIRA)

New ESB Project Wizard why isn't the JBoss ESB Version selected for me ---------------------------------------------------------------------- Key: JBDS-985 URL: https://jira.jboss.org/jira/browse/JBDS-985 Project: JBoss Developer Studio Issue Type: Feature Request Reporter: Jim Tyrrell Fix For: 3.0.0.M4 When I click a runtime why can't the ESB Version already be configured for me. How are customers supposed to know which version makes up our Productized products. For example if I am picking SOA-P 4.3 should this default to 4.4 or 4.3. -- 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

16 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5409) Replace XML Serialized Objects with something easier to read

by Brian Fitzpatrick (JIRA)

Replace XML Serialized Objects with something easier to read ------------------------------------------------------------ Key: JBIDE-5409 URL: https://jira.jboss.org/jira/browse/JBIDE-5409 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: smooks Affects Versions: 3.1.0.GA Reporter: Brian Fitzpatrick Assignee: Tom Fennelly Fix For: 3.1.0.GA To improve usability/readability, change the way objects are serialized in the console output for the Smooks Run Configuration to make the text easier to read. -- 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

16 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5449) Unnecessary JSF EL expression proposal in CA for non web JSF project

by Maxim Areshkau (JIRA)

Unnecessary JSF EL expression proposal in CA for non web JSF project -------------------------------------------------------------------- Key: JBIDE-5449 URL: https://jira.jboss.org/jira/browse/JBIDE-5449 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.1.0.CR1 Reporter: Maxim Areshkau Assignee: Alexey Kazakov Fix For: 3.1.0.GA #1 import https://svn.jboss.org/repos/jbosstools/trunk/documentation/whatsnew #2 call CA on line 64 There will be NEW JSF EL expression proposal. But it's not JSF project and this proposal is unnecessary -- 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

16 years, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-4946) Tool tip for tag/attributes in XHTML editor.

by Alexey Kazakov (JIRA)

Tool tip for tag/attributes in XHTML editor. -------------------------------------------- Key: JBIDE-4946 URL: https://jira.jboss.org/jira/browse/JBIDE-4946 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jsp/jsf/xml source editing Reporter: Alexey Kazakov Assignee: Victor Rubezhny Fix For: 3.1.0.M4 The idea is adding tool tips for tags/attributes in XHTM editor as WTP does for JSP editor. We can get info for tool tips from KB. -- 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

16 years, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5536) New context menu is very wide

by Burr Sutter (JIRA)

New context menu is very wide ----------------------------- Key: JBIDE-5536 URL: https://jira.jboss.org/jira/browse/JBIDE-5536 Project: Tools (JBoss Tools) Issue Type: Bug Environment: jbdevstudio-win32-3.0.0.v200912111227M-H41-RC1 Windows Vista 64-bit, Java 1.6 Reporter: Burr Sutter When working in the src folder of a Dynamic Web Project, right-click to bring up the New context menu. The New menu is very wide, looks odd. See screenshot. -- 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

16 years, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-5455) XPath 2.0 should be an option when creating an expression

by Brad Maxwell (JIRA)

XPath 2.0 should be an option when creating an expression --------------------------------------------------------- Key: JBIDE-5455 URL: https://jira.jboss.org/jira/browse/JBIDE-5455 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpm Affects Versions: 3.1.0.M4 Environment: Eclipse 3.5 jee-galileo-SR1 + JBossTools 3.1 v1.0.0.v200912010817N-H2-RC1 Reporter: Brad Maxwell I've noticed when creating an expression, you can only select XPATH 1.0, I believe XPATH 2 is supposed to also be an option. From the Riftsaw quickstarts, if I open one of them, they have XPATH 2 selected because they were created by hand and have XPATH 2.0 specified in the *.bpel file. -- 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

16 years, 4 months

4
3
0 / 0

[JBoss JIRA] Created: (JBDS-981) ESB Editor - linking in other editors is appropriate

by Svetlana mukhina (JIRA)

ESB Editor - linking in other editors is appropriate ---------------------------------------------------- Key: JBDS-981 URL: https://jira.jboss.org/jira/browse/JBDS-981 Project: JBoss Developer Studio Issue Type: Task Components: Doc - ESB Affects Versions: 2.1.0 Reporter: Svetlana mukhina Assignee: Svetlana mukhina Fix For: 2.1.0-doc see the linked issue -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5031) Add the ability to explicitly close the database connection

by Christian Daszenies (JIRA)

Add the ability to explicitly close the database connection ----------------------------------------------------------- Key: JBIDE-5031 URL: https://jira.jboss.org/jira/browse/JBIDE-5031 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Environment: Eclipse 3.5.0/Linux,Hibernate Tools for Eclipse Version: 3.3.0.v200909110340M-H277-M3 Reporter: Christian Daszenies We are frequently doing a full database refresh of our development instance (delete the user and associated objects on oracle-db, rebuild the user, objects...). This fails if the db-user has any open connections. After using hibernate tools we have to close eclipse to get rid of the open connection. -- 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

16 years, 4 months

3
7
0 / 0

[JBoss JIRA] Created: (JBDS-984) web.xml editor

by Jim Tyrrell (JIRA)

web.xml editor -------------- Key: JBDS-984 URL: https://jira.jboss.org/jira/browse/JBDS-984 Project: JBoss Developer Studio Issue Type: Feature Request Reporter: Jim Tyrrell Fix For: 3.0.0.M4 Can the Servlet Mapping editor have an arrow or dropdown to fill in the Servlet-Name. In other words having to type this in or cut and paste it seems like a little too much like worrk -- 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

16 years, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBDS-1009) Web Servlet Mapping Dialog should have drop-down list box for Servlet-Name

by Burr Sutter (JIRA)

Web Servlet Mapping Dialog should have drop-down list box for Servlet-Name -------------------------------------------------------------------------- Key: JBDS-1009 URL: https://jira.jboss.org/jira/browse/JBDS-1009 Project: JBoss Developer Studio Issue Type: Feature Request Affects Versions: 3.0.0.CR1 Reporter: Burr Sutter Priority: Minor Attachments: Web_Servlet_Mapping.jpg The Web Servlet Mapping dialog (see screenshot) should have a drop-down list box for Servlet-Name, after all I just entered the servlet into the web.xml using 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

16 years, 4 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-5516) Taglibs which registred in web.xml using javax.faces.FACELETS_LIBRARIES context param not shows in web project view

by Maxim Areshkau (JIRA)

Taglibs which registred in web.xml using javax.faces.FACELETS_LIBRARIES context param not shows in web project view ------------------------------------------------------------------------------------------------------------------- Key: JBIDE-5516 URL: https://jira.jboss.org/jira/browse/JBIDE-5516 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.1.0.CR1 Reporter: Maxim Areshkau Assignee: Maxim Areshkau Priority: Minor Fix For: 3.1.0.GA Taglibs which registred in web.xml using javax.faces.FACELETS_LIBRARIES context param not shows in web project 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5474) CDATA section declaration displays as UNKNOWN symbol in JBoss Tools Tag Library Editor

by Maxim Areshkau (JIRA)

CDATA section declaration displays as UNKNOWN symbol in JBoss Tools Tag Library Editor -------------------------------------------------------------------------------------- Key: JBIDE-5474 URL: https://jira.jboss.org/jira/browse/JBIDE-5474 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.1.0.CR1 Reporter: Maxim Areshkau Assignee: Maxim Areshkau Priority: Minor Fix For: 3.1.0.GA import https://svn.jboss.org/repos/jbosstools/trunk/jsf/tests/org.jboss.tools.js... project open html_basic.tld see any attribute for any tag. See description field. Here exist UNKNOW SYMBOL which is realy CDATA section declaration -- 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

16 years, 4 months

2
10
0 / 0

[JBoss JIRA] Created: (JBDS-1005) Guide structure article

by Svetlana mukhina (JIRA)

Guide structure article ------------------------ Key: JBDS-1005 URL: https://jira.jboss.org/jira/browse/JBDS-1005 Project: JBoss Developer Studio Issue Type: Sub-task Components: documentation Affects Versions: 2.1.0 Reporter: Svetlana mukhina Assignee: OLga Chikvina Fix For: 2.1.0-doc Provide a wiki article (http://community.jboss.org/wiki/HowtowritedocumentationforJBDSandJBossTools) describing a new structure for Jboss Tools/JBDS guides. -- 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

16 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5519) Problem in upstream AddComponentToEnterpriseApplicationDataModelProvider

by Rob Stryker (JIRA)

Problem in upstream AddComponentToEnterpriseApplicationDataModelProvider ------------------------------------------------------------------------ Key: JBIDE-5519 URL: https://jira.jboss.org/jira/browse/JBIDE-5519 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb, UpStream Affects Versions: 3.1.0.M4 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.1.0.CR1 The upstream AddComponentToEnterpriseApplicationDataModelProvider refuses to recognize that the child project you're linking to might want to be published under a different name. For example, MyEar references SomeESB, but wants to publish it as OtherESB.esb. This is impossible. Must override those entry points so our custom ModuleAssembly page does not do this stupidity until upstream fixes. -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5518) NPE during Seam Validation JUnit test running.

by Alexey Kazakov (JIRA)

NPE during Seam Validation JUnit test running. ---------------------------------------------- Key: JBIDE-5518 URL: https://jira.jboss.org/jira/browse/JBIDE-5518 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.0.GA Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.1.0.GA !MESSAGE Resource '/invalidParentProjectName' does not exist. [java] !STACK 1 [java] org.eclipse.core.internal.resources.ResourceException: Resource '/invalidParentProjectName' does not exist. [java] at org.eclipse.core.internal.resources.Resource.checkExists(Resource.java:319) [java] at org.eclipse.core.internal.resources.Resource.checkAccessible(Resource.java:196) [java] at org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:113) [java] at org.eclipse.core.internal.resources.Resource.findMarkers(Resource.java:911) [java] at org.jboss.tools.jst.web.kb.internal.KbProject.getOwnedMarkers(KbProject.java:945) [java] at org.jboss.tools.jst.web.kb.internal.KbProject.checkKBBuilderInstalled(KbProject.java:920) [java] at org.jboss.tools.seam.internal.core.validation.SeamCoreValidator.getSeamValidatingProjects(SeamCoreValidator.java:112) [java] at org.jboss.tools.seam.internal.core.validation.SeamCoreValidator.getValidatingProjects(SeamCoreValidator.java:100) [java] at org.jboss.tools.jst.web.kb.internal.validation.ValidationContext.<init>(ValidationContext.java:89) [java] at org.jboss.tools.jst.web.kb.internal.validation.ContextValidationHelper.getValidationContext(ContextValidationHelper.java:109) [java] at org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.validateInJob(ValidatorManager.java:58) [java] at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78) [java] at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) And org.eclipse.core.internal.resources.ResourceException: Resource '/JBossWSTestProject' does not exist. [java] at org.eclipse.core.internal.resources.Resource.checkExists(Resource.java:319) [java] at org.eclipse.core.internal.resources.Resource.checkAccessible(Resource.java:196) [java] at org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:113) [java] at org.eclipse.core.internal.resources.Project.hasNature(Project.java:489) [java] at org.jboss.tools.seam.internal.core.validation.SeamCoreValidator.shouldValidate(SeamCoreValidator.java:141) [java] at org.jboss.tools.jst.web.kb.internal.validation.ValidationContext.<init>(ValidationContext.java:84) [java] at org.jboss.tools.jst.web.kb.internal.validation.ContextValidationHelper.getValidationContext(ContextValidationHelper.java:109) [java] at org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.validateInJob(ValidatorManager.java:58) [java] at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78) [java] at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5419) Provide xulrunner eclipse bundle for OSX cocoa x86

by Denis Golovin (JIRA)

Provide xulrunner eclipse bundle for OSX cocoa x86 -------------------------------------------------- Key: JBIDE-5419 URL: https://jira.jboss.org/jira/browse/JBIDE-5419 Project: Tools (JBoss Tools) Issue Type: Sub-task Affects Versions: 3.1.0.M4 Reporter: Denis Golovin Fix For: 3.1.0.CR1, 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

16 years, 4 months

1
5
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