[JBoss JIRA] Created: (JBIDE-9658) jboss remote launch debug have a badly/noninformative preference on launch configuration
by Max Rydahl Andersen (JIRA)
jboss remote launch debug have a badly/noninformative preference on launch configuration
----------------------------------------------------------------------------------------
Key: JBIDE-9658
URL: https://issues.jboss.org/browse/JBIDE-9658
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Reporter: Max Rydahl Andersen
Assignee: Snjezana Peco
Priority: Critical
Fix For: 3.3.0.M4
The "JBoss Preferences" / JBoss Remote Configuration under "Remote Java Application" aren't very selfexplanatory or natural.
Need to find a better name or if they are actually relevant to have visible in UI:
Does this preference have to be visible ? Can I use selecting one of them as a way to say it should be considered ?
Then something like "Use for automatically detected applications" could be relevant - and title could be "Autodetection"
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] Created: (JBIDE-9587) Obsolete verify-errors of faces-config.xml after classpathchanges
by Peter Rader (JIRA)
Obsolete verify-errors of faces-config.xml after classpathchanges
-----------------------------------------------------------------
Key: JBIDE-9587
URL: https://issues.jboss.org/browse/JBIDE-9587
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Eclipse Migration
Affects Versions: 3.2.1.Final
Reporter: Peter Rader
Assignee: Max Rydahl Andersen
Priority: Minor
The verification of faces-config.xml does not run after Classpathchanges.
On an jsf-project without jsf-librarys, the error occources correctly "error: Attribute converter-class references to XXX that does not implement interface javax.faces.convert.Converter".
Then, if you add the jsf-librarys to the classpath, the "Verification Problem" "error: Attribute converter-class references to XXX that does not implement interface javax.faces.convert.Converter" is NOT removed!
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] Created: (JBDS-1509) JBDS thread looping after call to OS - Seen in DTP connection profile-setting
by Paul Nittel (JIRA)
JBDS thread looping after call to OS - Seen in DTP connection profile-setting
-----------------------------------------------------------------------------
Key: JBDS-1509
URL: https://issues.jboss.org/browse/JBDS-1509
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: integration
Affects Versions: 4.0.0.CR1
Environment: JBDS 4.0 H65 CR1, Fedora 12, Java SE Runtime Environment (build 1.6.0_21-b06)
Reporter: Paul Nittel
While testing Teiid Designer, I found the software wold go into a loop when I was interacting with the new connection profile process. The point at which the looping started was sonewhat variable, but seemed repeatable within the new CP set of dialogs. To simplify things, I started JBDS and went to the Database Development perspective (rather than Teiid Designer) and stepped through the new CP process. While completing the database connection information, the looping began. Here's part of the stack trace from running it in debug:
Thread [main] (Suspended)
OS.Call(int, int, int, int) line: not available [native method]
Display.sleep() line: 4021
WizardDialog(Window).runEventLoop(Shell) line: 826
WizardDialog(Window).open() line: 801
NewProfileAction(AddProfileViewAction).run() line: 246
NewProfileAction(Action).runWithEvent(Event) line: 498
ActionContributionItem.handleWidgetSelection(Event, boolean) line: 584
ActionContributionItem.access$2(ActionContributionItem, Event, boolean) line: 501
ActionContributionItem$5.handleEvent(Event) line: 411
EventTable.sendEvent(Event) line: 84
MenuItem(Widget).sendEvent(Event) line: 1258
Display.runDeferredEvents() line: 3540
Display.readAndDispatch() line: 3161
Workbench.runEventLoop(Window$IExceptionHandler, Display) line: 2640
Workbench.runUI() line: 2604
Workbench.access$4(Workbench) line: 2438
Workbench$7.run() line: 671
Realm.runWithDefault(Realm, Runnable) line: 332
Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 664
PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 149
IDEApplication.start(IApplicationContext) line: 115
EclipseAppHandle.run(Object) line: 196
EclipseAppLauncher.runApplication(Object) line: 110
EclipseAppLauncher.start(Object) line: 79
EclipseStarter.run(Object) line: 369
EclipseStarter.run(String[], Runnable) line: 179
NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method]
NativeMethodAccessorImpl.invoke(Object, Object[]) line: 39
DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25
Method.invoke(Object, Object...) line: 597
Main.invokeFramework(String[], URL[]) line: 619
Main.basicRun(String[]) line: 574
Main.run(String[]) line: 1407
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] Created: (JBDS-1600) Creating mysql data source creates wrong JAR reference
by Peter Larsen (JIRA)
Creating mysql data source creates wrong JAR reference
------------------------------------------------------
Key: JBDS-1600
URL: https://issues.jboss.org/browse/JBDS-1600
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Environment: RHEL6
Reporter: Peter Larsen
Fix For: 4.0.0.GA
When adding a driver, for instance mySQL, to JBDS, the dialog puts a wrong reference to the JAR file which needs to be corrected by the user.
If there's no automatic way to detect the location my the driver file, I suggest changing the dialog so the user is told to locate the file instead of hiding the option and having the user correct auto-generated material.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] Created: (JBDS-1557) Errors in JBoss Server Manager Reference Guide
by Vlado Pakan (JIRA)
Errors in JBoss Server Manager Reference Guide
----------------------------------------------
Key: JBDS-1557
URL: https://issues.jboss.org/browse/JBDS-1557
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: Doc - JBossAS
Affects Versions: 4.0.0.CR1
Reporter: Vlado Pakan
There are these errors in JBoss Server Manager Reference Guide http://download.jboss.org/jbosstools/nightly-docs/en/as/html/index.html:
Chapter 1.1 - wrong link label "runtimes_servers"
Chapter 2.1.2. - wrong screenshot dialog UI was changed update also related text of chapter
Missing icon after "Reset Default Button " above Figure 2.12.
Figure 2.13 - Added Group "Server Behaviour" add also related descritpion
Figure 3.15., 3.16., 3.20. - obsolete screenshots add description of changes
Figure 4.1. - obsolete new tree item "Filter" added
Figure 4.3. - new facesets added update also descritpion
Figure 4.4. - new facesets
Figure 5.5. - there is no menu item "Deploy To Server" in package explorer
Chapter 5.1.2. - Deploying single files is maybe obsolete
Chapter 6.1 - link to JBoss TPTP profile feature at http://www.jboss.org/tools/download/stable is not working there is no update site on mentioned URL
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] Created: (JBIDE-9758) Seam DVD example does not work with JBoss AS 4.2
by Jaroslav Jankovič (JIRA)
Seam DVD example does not work with JBoss AS 4.2
------------------------------------------------
Key: JBIDE-9758
URL: https://issues.jboss.org/browse/JBIDE-9758
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam 2
Affects Versions: 3.2.2.M1
Reporter: Jaroslav Jankovič
Assignee: Alexey Kazakov
Fix For: 3.2.2.M1
Seam DVD Store Example should work with JBoss AS 4.2.x as written in description of this example (JBoss EAP 4.3/JBoss AS 4.2.x). However, during deploying application on JBoss AS 4.2.3, exception is thrown and deployment fails. Deployment on JBoss EAP 4.3 passes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months