March 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBDS-1006) How to write documentation wiki article update

by Svetlana mukhina (JIRA)

How to write documentation wiki article update ----------------------------------------------- Key: JBDS-1006 URL: https://jira.jboss.org/jira/browse/JBDS-1006 Project: JBoss Developer Studio Issue Type: Task Components: documentation Affects Versions: 2.1.0 Reporter: Svetlana mukhina Assignee: Anastasiya Bogachuk Fix For: 2.1.0-doc Update the article - http://community.jboss.org/wiki/HowtowritedocumentationforJBDSandJBossTools in the following way: Docteam notes section should be split onto separate articles published under the main one (HowtowritedocumentationforJBDSandJBossTools) , e.g.: Project structure schema, Images, etc, Some paragraphs should be moved to other section (e.g. everything about jira - move to Doc JIRA) New articles should be added e.g. Highlighting, Capitalizing, Abbreviations, Syntax (contact Mukhina for more detailes) -- 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

3
5
0 / 0

[JBoss JIRA] Created: (JBDS-931) VPE error message are made more information and user friendly

by Svetlana mukhina (JIRA)

VPE error message are made more information and user friendly ------------------------------------------------------------- Key: JBDS-931 URL: https://jira.jboss.org/jira/browse/JBDS-931 Project: JBoss Developer Studio Issue Type: Task Components: Doc - VisualWebTools Affects Versions: 2.1.0 Reporter: Svetlana mukhina Assignee: Anastasiya Bogachuk Fix For: 2.1.0-doc check the screens of the vpe sections of editors chapter, make sure the messages are seen on the screens, have a look at the first issue of http://docs.jboss.org/tools/whatsnew/vpe/vpe-news-3.1.0.M2.html -- 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

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6117) JBOSS tools native support for code gen in Groovy, and new Groovy seam project

by William Woodman (JIRA)

JBOSS tools native support for code gen in Groovy, and new Groovy seam project ------------------------------------------------------------------------------ Key: JBIDE-6117 URL: https://jira.jboss.org/jira/browse/JBIDE-6117 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Seam Affects Versions: 3.1.0.GA Environment: eclipse 3.5 with jboss tools 3.1 GA Reporter: William Woodman Trying to use Groovy with Jboss tools and i'm having to hand craft all the files. Essentially i have to generate the types in the IDE, then cut/copy the code back into groovy files and save. also have to install groovy IDE files separately and then enable grrovy support fr the project and set the j2ee module dependencies to get the deployed build to work. Groovy is actually really nice for the entity builds (so much less clutter) and closure features etc are nice in the language. What i'd like is that rather than just jboss tools being flexible to knit groovy in - it should have first class support in the jboss tools. I'm using seam so lets lay out thje basic requirement 1. future near build of jboss tools to provide install support for groovy. Create seam project and in wizard indicate that that you default code gen to be groovy or java. if groovy - inlude the latest groovy all jar in the ejb/war projects and automatically include the J2ee module dependency so that groovy files work when exporting project to server. 2. do some integration work with the groovy IDE guys, or duplicate equivalent builders into the JBOSS tools standard download. 3. when user selects new entity, form, conversation, etc show the default class gen type (from startup wizard) but let a user overwrite in the wizard (allows mixed mode working - with default for project as set at startup). 4. if groovy selected ensure that full debug support included for groovy files. This would be a fabulous improvement. At present although i can build a grooy project its very manually intensive and I have to do all the hard work by hand/cut copy etc . would be fabulous if jboss tools fully supported this natively. Also with seam v3 on the build, ensuring that groovy option is included into weld/seam v3 would be a plus also -- 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

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5873) Attributes in Notifier target tag removed (required for NotifyEmail)

by Bill Matson (JIRA)

Attributes in Notifier target tag removed (required for NotifyEmail) -------------------------------------------------------------------- Key: JBIDE-5873 URL: https://jira.jboss.org/jira/browse/JBIDE-5873 Project: Tools (JBoss Tools) Issue Type: Bug Components: XML Structured Editor Affects Versions: 3.1.0.CR1 Environment: JBoss ESB 4.5, tried on both the CR1 version of tools and the current trunk build. Reporter: Bill Matson The NotifyEmail notification target takes much of its configuration from attributes on the <target> tag. The 3.1 version of the tools appears to not support attributes on the <target> tag inside of a notifier action. They can be entered in the XML by hand, however they do not appear to be maintained when changes are made using the graphical editor. Since the NotifySqlTable is also configured via attributes on the <target> tag, it probably exhibits the same behavior (I haven't tested this one).... Sample one-action ESB service below. If you do the following you'll see the behavior: 1) Copy and paste ESB config into the XML editor. 2) Switch to the Tree view and change pretty much anything (i.e. change the name of the action from "TestNotifier" to anything else) and save 3) Switch back to XML view and that attributes on the <target> tag are gone. Sample ESB: <?xml version="1.0"?> <jbossesb parameterReloadSecs="5" xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..." xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml... http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem..."> <services> <service category="TestCategory" description="Test" invmScope="GLOBAL" name="TestService"> <actions> <action class="org.jboss.soa.esb.actions.Notifier" name="TestNotifier"> <property name="destinations"> <NotificationList type="OK"> <target class="NotifyEmail" sendTo="someone(a)somewhere.com" subject="test" from="other(a)somewhere.com" /> </NotificationList> </property> </action> </actions> </service> </services> </jbossesb> -- 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
8
0 / 0

[JBoss JIRA] Created: (JBIDE-4352) OldGraphVisitor either redundan't either must declare methods as public

by Dmitry Geraskov (JIRA)

OldGraphVisitor either redundan't either must declare methods as public ----------------------------------------------------------------------- Key: JBIDE-4352 URL: https://jira.jboss.org/jira/browse/JBIDE-4352 Project: Tools (JBoss Tools) Issue Type: Task Components: Hibernate Affects Versions: 3.1.0.M1 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Priority: Optional Fix For: 3.1.0.M2 OldGraphVisitor used as superclass for DummyEdgeCreator, but DummyEdgeCreator can't override methods visible in other package only. Also there is not any reference to OldGraphVisitor in code(except that one extending)... Need to refactor code. -- 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

1
4
0 / 0

[JBoss JIRA] Created: (JBDS-980) VPE toolbar icons are redesigned

by Svetlana mukhina (JIRA)

VPE toolbar icons are redesigned --------------------------------- Key: JBDS-980 URL: https://jira.jboss.org/jira/browse/JBDS-980 Project: JBoss Developer Studio Issue Type: Task Components: Doc - VisualWebTools Affects Versions: 2.1.0 Reporter: Svetlana mukhina Assignee: Anastasiya Bogachuk Fix For: 2.1.0-doc update VPE section in Editors chapter in VWT guide -- 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

3
6
0 / 0

[JBoss JIRA] Created: (JBDS-1065) "Add" button is added to the VPE templates for unknown tags preferences page

by Svetlana mukhina (JIRA)

"Add" button is added to the VPE templates for unknown tags preferences page ---------------------------------------------------------------------------- Key: JBDS-1065 URL: https://jira.jboss.org/jira/browse/JBDS-1065 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Components: Doc - VisualWebTools, Doc - RHDS GSG Affects Versions: 3.0.0.CR1 Reporter: Svetlana mukhina Assignee: Svetlana mukhina Fix For: 3.0.0.CR2-doc Investigate the functionality, Update screens with VPE Templates Preferences Page and Edit tag dialog in the 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

1
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6108) Delete related projects when deleting Seam project

by Vlado Pakan (JIRA)

Delete related projects when deleting Seam project -------------------------------------------------- Key: JBIDE-6108 URL: https://jira.jboss.org/jira/browse/JBIDE-6108 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Seam Affects Versions: 3.1.0.GA Reporter: Vlado Pakan Fix For: 3.2.next Delete related projects when Seam project is deleted. When Seam project is created there are created additional projects (e.i. test project, ear project, esb project...). When Seam project is deleted by user only one project is deleted and all the related projects are not. It should be possible to delete also related projects anyways they are useless when main Seam project is deleted. Maybe there should be added check box with possibility to decide to delete related projects or not at least when deleting via Web Projects view. Probably when deleting via Package explorer this functionality can be omitted. -- 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

2
1
0 / 0

[JBoss JIRA] Created: (JBDS-1080) Unclear text in GettingStartetGuide documentation

by Tihomir Surdilovic (JIRA)

Unclear text in GettingStartetGuide documentation -------------------------------------------------- Key: JBDS-1080 URL: https://jira.jboss.org/jira/browse/JBDS-1080 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Doc - JBossAS Affects Versions: 3.0.0.CR1 Reporter: Tihomir Surdilovic In the GettingStartedDocs (http://docs.jboss.org/tools/3.1.0.CR1/en/GettingStartedGuide/html/manage....) it states: ***** JBoss Developer Studio 2.1.0.GA is shipped with JBoss EAP 5 . When you followed the default installation of JBoss Developer Studio, you should already have a JBoss EAP 5 Server installed and defined. To run JBoss AS you need JDK 1.5, JDK 6 is not formally supported yet, although you may be able to start the server with it. ***** This sentence should be changed to note that JBoss EAP 5 (and 4.3 CP02+ are supported on JDK 6 and that JBDS 2.0 and 2.1 are only officially supported to run with JDK 5. You can however use any JDK with JBDS as long as the underlying Eclipse version supports it. So you can run JBDS with JDK 5 but you can run your EAP server with a different JDK (also point to docs where it shows this configuration or create it if it does not exist). -- 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

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-2551) Exceptions appears connected with <rich:inplaceSelect>

by Andrei Scherbovich (JIRA)

Exceptions appears connected with <rich:inplaceSelect> ------------------------------------------------------ Key: JBIDE-2551 URL: https://jira.jboss.org/jira/browse/JBIDE-2551 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Affects Versions: 3.0.0.alpha Reporter: Andrei Scherbovich Assignee: Eugene Stherbin Steps: EXECUTE: Open ATTACHED JSP FILE in studio FAILURE: exception appears (SEE ERROR LOG "log1.txt" ATTACHED) EXECUTE: Add "defaultLabel" attribute into <rich:inplaceSelect> component FAILURE: other exceptions appears (SEE ERROR LOG "log2.txt" and "log3.txt" ATTACHED) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

4
6
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 March 2010