January 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-3235) Missing properties view for servers elements

by Max Rydahl Andersen (JIRA)

Missing properties view for servers elements -------------------------------------------- Key: JBIDE-3235 URL: https://jira.jboss.org/jira/browse/JBIDE-3235 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Reporter: Max Rydahl Andersen Fix For: 3.0.0.cr1 Before I could directly edit properties for ports in properties view. Now I need to right click and choose Change Value and get a non-standard edit in the tree. This I could probably live with if I could just double click the value and edit it like in properties view. Properties view was though also nice to give other details than just access to edit. i.e.. I could copy values to get the value of file names etc. I can't copy elements from the tree and get a textual representation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

5
11
0 / 0

[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

3
4
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-140) Document Externilize string wizard for JSF pages

by Maxim Areshkau (JIRA)

Document Externilize string wizard for JSF pages ------------------------------------------------ Key: TOOLSDOC-140 URL: https://issues.jboss.org/browse/TOOLSDOC-140 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JSF Tools Reference Guide Affects Versions: 3.x-Helios Reporter: Maxim Areshkau Assignee: Isaac Rooskov Externilize string wizard has been added to jsf tools. So this should be documented https://issues.jboss.org/browse/JBIDE-6287 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

6
6
0 / 0

[JBoss JIRA] Created: (JBIDE-4167) Add support for RestEasy as a Project Facet

by Joao Paulo Viragine (JIRA)

Add support for RestEasy as a Project Facet ------------------------------------------- Key: JBIDE-4167 URL: https://jira.jboss.org/jira/browse/JBIDE-4167 Project: Tools (JBoss Tools) Issue Type: Feature Request Environment: JBDS 2.0.0.GA Reporter: Joao Paulo Viragine Priority: Minor If project is a Dinamic Web Project, JBDS should include all required libs and all modification in web.xml (as described here: http://www.jboss.org/file-access/default/members/resteasy/freezone/docs/1...) If project is a Seam Web Project, include required libs as described here: http://docs.jboss.com/seam/2.1.1.GA/reference/en-US/html_single/#d0e21523 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6488) dashboard for jboss.org projects

by Dan Allen (JIRA)

dashboard for jboss.org projects -------------------------------- Key: JBIDE-6488 URL: https://jira.jboss.org/browse/JBIDE-6488 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 3.1.1 Reporter: Dan Allen Create a dashboard view for JBoss.org projects. This feature request is inspired by the Kenai.com dashboard view in NetBeans (screenshot attached). The general idea is to provide a view within the IDE of the JBoss.org projects (perhaps even other conforming projects). The view provides information about the project such as: = title = description = project members = source control = recent issues = blog feed (titles w/ summary and link) = ... You would then be able to interact with the form to pull the source into your IDE workspace and build it. That way, we can get new developers started as simple as possible and consistently across all projects. The key is that it's simple to get started, and we start the developer in JBoss Tools, then get them into the code. Most of the info could be extracted from the poms in the Nexus repo, and know URL patterns on jboss.org. http://netbeans.org/kb/docs/ide/kenai-create-project.html What would be stunning is if we could also tie this into collaborative editing in the IDE. -- 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

14 years, 4 months

4
5
0 / 0

[JBoss JIRA] Created: (JBDS-1449) Merge runtime related features from JBDS installer to runtime plug-in and reuse runtime plug-in binaries in installer

by Denis Golovin (JIRA)

Merge runtime related features from JBDS installer to runtime plug-in and reuse runtime plug-in binaries in installer --------------------------------------------------------------------------------------------------------------------- Key: JBDS-1449 URL: https://jira.jboss.org/browse/JBDS-1449 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Components: installer, runtime Affects Versions: 4.0.0.Beta2 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 4.0.0.CR1 Now server search and validation for "server configuration dialog" in installer are duplicated in runtime plugin. That makes difficult to keep them in sync and that's why sometimes installer complains that version of selected server is not supported, but runtime plugin is actually can handle this version in a right way see JBDS-1380 as example. The idea is merge all what installer has in runtime and/or jbossas adapter plugin and use these plugins in installer to keep all code in one place. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

6
10
0 / 0

[JBoss JIRA] Created: (JBDS-1266) Credentials entered to test jBPM process deployment are cached - not over-ridden if user enters different credentials to deploy a process

by Len DiMaggio (JIRA)

Credentials entered to test jBPM process deployment are cached - not over-ridden if user enters different credentials to deploy a process ----------------------------------------------------------------------------------------------------------------------------------------- Key: JBDS-1266 URL: https://jira.jboss.org/browse/JBDS-1266 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: runtime, SOA Platform Affects Versions: 3.0.0.GA Environment: Version: 3.0.0.GA Build id: v201003100055R Build date: 201003100222 Reporter: Len DiMaggio Attachments: Screenshot-1.png, Screenshot-2.png, Screenshot.png The sequence of events is: 1) Create a jBPM project 2) Successfully test the connection to a SOA-P server 3) Select credentials checkbox - enter invalid credentials 4) Deploy the jBPM project process - the deployment will use the credentials previously used during the test -- 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

14 years, 5 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-4093) Project archive isn't published to the deploy folder after changing temporary deploy directory.

by Anton Klimkovich (JIRA)

Project archive isn't published to the deploy folder after changing temporary deploy directory. ----------------------------------------------------------------------------------------------- Key: JBIDE-4093 URL: https://jira.jboss.org/jira/browse/JBIDE-4093 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0 Reporter: Anton Klimkovich Priority: Minor EXECUTE: Create seam web project EXECUTE: Open Server Overview EXECUTE: Set checkbox to Use workspace metadata EXECUTE: Add project to the server ASSERT: Project is deployed to \ws3\.metadata\.plugins\org.jboss.ide.eclipse.as.core\jboss-soa-p.4.3.0\deploy\ EXECUTE: Open Server Overview EXECUTE: Set checkbox to Use a custom deploy folder or Use the JBoss deploy folder. Save changes. EXECUTE: Press Publish to the server button FAILURE: Only seam-ds.xml is published. Seam.war isn't published to the deploy folder. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-3663) Show a warning when the user tries to open the launch configuration but the server editor is dirty

by Adrian Mitev (JIRA)

Show a warning when the user tries to open the launch configuration but the server editor is dirty -------------------------------------------------------------------------------------------------- Key: JBIDE-3663 URL: https://jira.jboss.org/jira/browse/JBIDE-3663 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Affects Versions: 3.0.0.CR2 Environment: JBT N200901190612, java 1.5, windows XP Reporter: Adrian Mitev Something like "Server is not saved yet - the console configuration might be out of date. Do you want to save the serrver before opening the launch configuration ?" when users click the "open launch config". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

5
8
0 / 0

[JBoss JIRA] Created: (JBIDE-4185) Simpler load time weaving configuration

by Galder Zamarreño (JIRA)

Simpler load time weaving configuration --------------------------------------- Key: JBIDE-4185 URL: https://jira.jboss.org/jira/browse/JBIDE-4185 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Reporter: Galder Zamarreño Assignee: Rob Stryker Right now, if you wanna use load time weaving, you need to modify jboss.aop:service=AspectManager MBean to have EnableLoadtimeWeaving to true and you need to pass the pluggable instrumentor in the VM parameters, i.e. -javaagent:/home/galder/access/eap-rel/4.3.0.ga.cp04/server/279798/deploy/jboss-aop-jdk50.deployer/pluggable-instrumentor.jar >From JBDS, you need to put the full path to this, whereas if running standalone, you can just do: JAVA_OPTS="$JAVA_OPTS -javaagent:server/279798/deploy/jboss-aop-jdk50.deployer/pluggable-instrumentor.jar" Now, it'd be really helpful if the JBoss AS/EAP server had an option that added did this (at least the javaagent part) if load time weaving was enabled (a new option server configuration window (i.e. double click server name)) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

4
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 January 2011