September 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-1420) Hibernate Configuration Wizard: add "Test Connection" button and validate driver class, URL, user, pwd etc.

by Alexander Chabatar (JIRA)

Hibernate Configuration Wizard: add "Test Connection" button and validate driver class, URL, user, pwd etc. ----------------------------------------------------------------------------------------------------------- Key: JBIDE-1420 URL: http://jira.jboss.com/jira/browse/JBIDE-1420 Project: JBoss Tools Issue Type: Feature Request Components: Hibernate Affects Versions: LATER Reporter: Alexander Chabatar Assigned To: Alexander Chabatar Priority: Minor Fix For: LATER 1) add Test Connection button - should be helpful. 2) Finish button is always enabled. For example if Database dialect is selected but no driver class, no URL, user. Validation might show a warning. -- 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

15 years, 3 months

5
47
0 / 0

[JBoss JIRA] Created: (JBDS-1230) JBoss Developer 3.0 Installing in a a newly installed RHEL 5.4 does not show up in the applications menu

by Jim Tyrrell (JIRA)

JBoss Developer 3.0 Installing in a a newly installed RHEL 5.4 does not show up in the applications menu -------------------------------------------------------------------------------------------------------- Key: JBDS-1230 URL: https://jira.jboss.org/browse/JBDS-1230 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Affects Versions: 3.0.0.GA Environment: RHEL 5.4 with Sun JDK 5.4 Reporter: Jim Tyrrell When going through the installer on a clean RHEL 5.4 system, the Programming Tools Listing under the Applications in the main menu bar does not show up until a reboot. Once it has been installed at least once, this does not seem to be a problem -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

4
5
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-114) JBDS40_037 Keep reference guide documentation up to date

by Isaac Rooskov (JIRA)

JBDS40_037 Keep reference guide documentation up to date -------------------------------------------------------- Key: TOOLSDOC-114 URL: https://jira.jboss.org/browse/TOOLSDOC-114 Project: Documentation for JBoss Tools/Developer Studio Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Isaac Rooskov Assignee: Isaac Rooskov Tracker for this issue. Status: Partial -> only looking at reference documentation and not tutorial documentation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6588) BPEL deployment to ODE running in Tomcat

by Gary Brown (JIRA)

BPEL deployment to ODE running in Tomcat ---------------------------------------- Key: JBIDE-6588 URL: https://jira.jboss.org/browse/JBIDE-6588 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: bpel Reporter: Gary Brown Currently the BPEL plugins in JBoss Tools support deployment of a BPEL process and ODE deployment descriptor to RiftSaw (ODE running in JBossAS). It may be useful to allow users to also deploy the same processes to ODE running inside Tomcat. This would enable existing ODE/Tomcat users to benefit from a supported version of the BPEL editor, and easily switch to using RiftSaw if they wanted. The Eclipse BPEL project already provides a deploy for ODE in Tomcat. The only change that would be required is to change the bpel-deploy.xml to deploy.xml during deployment, as ODE does not recognize bpel-deploy.xml. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

6
18
0 / 0

[JBoss JIRA] Created: (JBIDE-5829) Update BPEL deployment plug-ins with JBoss-specific IDs

by Brian Fitzpatrick (JIRA)

Update BPEL deployment plug-ins with JBoss-specific IDs ------------------------------------------------------- Key: JBIDE-5829 URL: https://jira.jboss.org/jira/browse/JBIDE-5829 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpm Reporter: Brian Fitzpatrick Assignee: Max Rydahl Andersen Priority: Critical Fix For: 3.1.0.CR2 While reviewing the state of the BPEL editor, it came up that the deployment plug-ins (the o.e.bpel.apache.ode.* plugins), though they included JBoss Riftsaw-specific code, were still the same plug-in IDs & project names as were in the BPEL project at Eclipse.org. These need to change so we don't run into conflicts with the Eclipse 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

15 years, 4 months

4
22
0 / 0

[JBoss JIRA] Created: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester

by Brian Fitzpatrick (JIRA)

Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester ---------------------------------------------------------------------------------------------------------- Key: JBIDE-6450 URL: https://jira.jboss.org/browse/JBIDE-6450 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.M1 Reporter: Brian Fitzpatrick Assignee: Brian Fitzpatrick Priority: Critical Fix For: 3.2.0.M1 Finally got to the heart of the java.lang.VerifyError issue I've been running into with the WS Tester. javax.xml.soap (1.2) is an old-school plug-in jar wrapper that takes saaj.jar and exposes it in Eclipse. javax.xml.soap (1.3) is a new-school OSGI-compatible wrapper that builds the individual saaj classes and wraps them to expose them in Eclipse. As Nick said in a recent IRC chat - ".jar!/org/whatever/*.class is better than .jar!foo.jar". But in my case, it causes the lovely java.lang.VerifyError when I try to use a utility class that takes advantage of classes from javax.xml.soap. After doing some digging, it turns out the javax.xml.soap (1.3) plug-in is coming from the Atlassian update site for the latest & greatest version of their JIRA/Mylyn plug-ins. Without Atlassian JIRA connectors installed, it runs just fine. So this presents an issue... If we're meant to certify against Atlassian JIRA connectors, this is going to come up again. So how do we work around it? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

4
29
0 / 0

[JBoss JIRA] Created: (JBIDE-6606) Unable to specify styleClass attribute for selected tag when used CSS class contains @CHARSET "UTF-8"; at keyword.

by Vlado Pakan (JIRA)

Unable to specify styleClass attribute for selected tag when used CSS class contains @CHARSET "UTF-8"; at keyword. ------------------------------------------------------------------------------------------------------------------ Key: JBIDE-6606 URL: https://jira.jboss.org/browse/JBIDE-6606 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.2.0.M1 Environment: JBDS Version: 4.0.0.M1 Build id: v201007091251N Build date: 201007091354 Linux 32bit Java Sun JDK 1.6 Reporter: Vlado Pakan Assignee: Maxim Areshkau Steps to reproduce: 1. Create new JSF project 2. Create and open new CSS file test,css in the <jsf project>/WebContent/pages/ directory: Menu File > New > Others > Css File. It should has content @CHARSET "UTF-8"; 3. Open <jsf project>/WebContent/pages/inputUserName.jsp and insert "link href="test.css" type="text/css"/>" after "<body>" tag. 4. Open Properties view: Window > Show View > Properties 5. Select "h:outputText" tag within source pane of opened page 6. Select styleClass property within Properties view and choose button with label "..." trying to specify styleClass property No dialog is displayed and in Error Log is this error: java.lang.ClassCastException: org.eclipse.wst.css.core.internal.document.CSSCharsetRuleImpl cannot be cast to org.eclipse.wst.css.core.internal.provisional.document.ICSSStyleRule at org.jboss.tools.jst.jsp.outline.cssdialog.cssselector.model.CSSSelectorTreeModel.initModel(CSSSelectorTreeModel.java:52) at org.jboss.tools.jst.jsp.outline.cssdialog.cssselector.model.CSSSelectorTreeModel.<init>(CSSSelectorTreeModel.java:37) at org.jboss.tools.jst.jsp.outline.cssdialog.cssselector.model.CSSJSPRecognizer.getCssStyleClassTreeModel(CSSJSPRecognizer.java:163) at org.jboss.tools.jst.jsp.outline.cssdialog.cssselector.model.CSSJSPRecognizer.getCssStyleClassTreeModel(CSSJSPRecognizer.java:169) at org.jboss.tools.jst.jsp.outline.cssdialog.cssselector.CSSSelectorPartComposite.initDefaultContent(CSSSelectorPartComposite.java:133) at org.jboss.tools.jst.jsp.outline.cssdialog.cssselector.CSSSelectorPartComposite.creatSelectorPart(CSSSelectorPartComposite.java:116) at org.jboss.tools.jst.jsp.outline.cssdialog.cssselector.CSSSelectorPartComposite.<init>(CSSSelectorPartComposite.java:108) at org.jboss.tools.jst.jsp.outline.cssdialog.cssselector.CSSStyleClassSelector.createCSSClassComposite(CSSStyleClassSelector.java:62) at org.jboss.tools.jst.jsp.outline.cssdialog.cssselector.CSSStyleClassSelector.createControlComposite(CSSStyleClassSelector.java:49) at org.jboss.tools.jst.jsp.outline.cssdialog.AbstractCSSDialog.createControlPane(AbstractCSSDialog.java:118) at org.jboss.tools.jst.jsp.outline.cssdialog.AbstractCSSDialog.createDialogArea(AbstractCSSDialog.java:88) at org.jboss.tools.jst.jsp.outline.cssdialog.cssselector.CSSStyleClassSelector.createDialogArea(CSSStyleClassSelector.java:91) at org.eclipse.jface.dialogs.TitleAreaDialog.createContents(TitleAreaDialog.java:155) at org.jboss.tools.jst.jsp.outline.cssdialog.cssselector.CSSStyleClassSelector.createContents(CSSStyleClassSelector.java:57) at org.eclipse.jface.window.Window.create(Window.java:431) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089) at org.eclipse.jface.window.Window.open(Window.java:790) at org.jboss.tools.jst.jsp.outline.JSPDialogCellEditor.openDialogBox(JSPDialogCellEditor.java:141) at org.eclipse.jface.viewers.DialogCellEditor$2.widgetSelected(DialogCellEditor.java:244) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1234) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3159) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2629) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2593) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) 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:369) 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:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-4809) Creating application.xml, jboss-app.xml and datasource files when importing Maven EAR project

by Snjezana Peco (JIRA)

Creating application.xml, jboss-app.xml and datasource files when importing Maven EAR project --------------------------------------------------------------------------------------------- Key: JBIDE-4809 URL: https://jira.jboss.org/jira/browse/JBIDE-4809 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: maven Affects Versions: 3.1.0.M2 Reporter: Snjezana Peco Assignee: Snjezana Peco See https://jira.jboss.org/jira/browse/JBIDE-4736?focusedCommentId=12481300#a... and http://archive.codehaus.org/lists/org.codehaus.m2eclipse.user/msg/4A8A60A... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

4
16
0 / 0

[JBoss JIRA] Created: (JBIDE-6879) BPEL deployer should not be using PublishCopyUtili.java in JBoss as.core package

by Robert (Bob) Brodt (JIRA)

BPEL deployer should not be using PublishCopyUtili.java in JBoss as.core package -------------------------------------------------------------------------------- Key: JBIDE-6879 URL: https://jira.jboss.org/browse/JBIDE-6879 Project: Tools (JBoss Tools) Issue Type: Task Components: bpel Affects Versions: 3.2.0.M2 Reporter: Robert (Bob) Brodt Assignee: Robert (Bob) Brodt Fix For: 3.2.0.M2 Like the comments in PublishCopyUtili say: * This class/interface is part of an interim API that is still under development and expected to * change significantly before reaching stability. It is being made available at this early stage to solicit feedback * from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken * (repeatedly) as the API evolves. the bpel deployer package probably shouldn't be using this class, but should be using the standard WTP API instead. I've made a quick fix for now to get us through M2, but this needs to be addressed before final release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
7
0 / 0

[JBoss JIRA] Created: (JBIDE-7107) Problems when creating BPEL Correlation Set

by Robert (Bob) Brodt (JIRA)

Problems when creating BPEL Correlation Set ------------------------------------------- Key: JBIDE-7107 URL: https://jira.jboss.org/browse/JBIDE-7107 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Reporter: Robert (Bob) Brodt Assignee: Robert (Bob) Brodt Fix For: 3.2.0.CR1 I discovered several issues during testing: 1. The WSDL property is created correctly but the PropertySelectorDialog does not detect the message part. This leads to "missing "type" or "element" attribute" validation error 2. The messages.properties file in the org.eclipse.bpel.validator.vprop package (used for error message localization) is empty 3. WSDL validator does not detect duplicate definitions of <property name="foo"> 4. The message "Structure" tree widget in EditPropertyAliasDialog is only one line high - should display more of message structure 5. The overall workflow for creating correlation sets is overly complicated! This needs to be reworked. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
12
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 September 2010