November 2010 - jbosstools-issues

[JBoss JIRA] Commented: (JBDS-1402) When publishing a file to ModeShape using JBDS, there should be the option to specifiy the "workspacepath", because this path is what the server looks for when determining what to sequence.

by Brian Fitzpatrick (JIRA)

[ https://jira.jboss.org/browse/JBDS-1402?page=com.atlassian.jira.plugin.sy... ] Brian Fitzpatrick commented on JBDS-1402: ----------------------------------------- This seems pretty critical - Dan has a fix he's going to get in on 16-NOV for Beta2. Approved for Beta2 by me. > When publishing a file to ModeShape using JBDS, there should be the option to specifiy the "workspacepath", because this path is what the server looks for when determining what to sequence. > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-1402 > URL: https://jira.jboss.org/browse/JBDS-1402 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: Modeshape > Affects Versions: 4.0.0.Beta2 > Reporter: Van Halbert > Assignee: Max Andersen > > When using the JBDS to publish to ModeShape, the option should be available to specify the "workspacepath". This path is what the server looks for when determining what to sequence. > The publish example in SOA specifies this argument and when the files are published, the sequenced information is appropriately seen in the expected tables (i.e., model:xmi). -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-7604) Update CodeGeneration in external process to use FakeTransactionManagerLookup

by Vitali Yemialyanchyk (JIRA)

Update CodeGeneration in external process to use FakeTransactionManagerLookup ----------------------------------------------------------------------------- Key: JBIDE-7604 URL: https://jira.jboss.org/browse/JBIDE-7604 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Hibernate Affects Versions: 3.2.0.Beta2 Reporter: Vitali Yemialyanchyk Assignee: Vitali Yemialyanchyk Priority: Minor Fix For: 3.2.0.CR1 in case - if hibernate.transaction.manager_lookup_class property empty - Hibernate Tools for Eclipse console configuration using org.hibernate.console.FakeTransactionManagerLookup class; to have the same functionality with code generation in external process - this update is necessary. the issue JBIDE-7562 - is one example without this update. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-7602) Create JUint test to check necessity to move FakeTransactionManagerLookup from Tools UI to Core

by Vitali Yemialyanchyk (JIRA)

Create JUint test to check necessity to move FakeTransactionManagerLookup from Tools UI to Core ----------------------------------------------------------------------------------------------- Key: JBIDE-7602 URL: https://jira.jboss.org/browse/JBIDE-7602 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Hibernate Affects Versions: 3.2.0.Beta2 Reporter: Vitali Yemialyanchyk Assignee: Vitali Yemialyanchyk Priority: Minor Fix For: 3.2.0.CR1 the junit test should fail in case if JBIDE-7441 not fixed -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBIDE-7406) DeltaCloud UI does not store cloud type

by Andre Dietisheim (JIRA)

DeltaCloud UI does not store cloud type --------------------------------------- Key: JBIDE-7406 URL: https://jira.jboss.org/browse/JBIDE-7406 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Andre Dietisheim The current implementation of the deltacloud UI does not store the cloud type correctly. It does not pass the type parameter in constructors: class DeltaCloud: public DeltaCloud(String name, String url, String username, String passwd) throws MalformedURLException { this(name, url, username, passwd, null, false, IImageFilter.ALL_STRING, IInstanceFilter.ALL_STRING); ^^^^ } Therefore, when a cloud is edited, a bad type is extracted from the settings (a String "null"). Either the type shall not stored at all and calculated on each connection edit (by querying the server) or it shall be stored and displayed without server query. -- 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

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-7484) DeltaCloudClient: remove instance related actions

by Andre Dietisheim (JIRA)

DeltaCloudClient: remove instance related actions ------------------------------------------------- Key: JBIDE-7484 URL: https://jira.jboss.org/browse/JBIDE-7484 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Andre Dietisheim The DeltaCloudClient currently has duplicate implementations of instance related functionalities (start, stop, destroy, reboot). I'll remove the deprecated methods: Mail with Jeff Johnson on the 29th of Oct: >> I discovered another possible duplication: >> >> DeltaCloudClient#performInstanceAction allows you to perfom START, STOP, >> REBOOT, DESTROY (Instance#Action) >> >> On the other hand most of these actions also have their own method in >> DeltaCloudClient: >> >> startInstance >> shutdownInstance (=STOP) >> rebootInstance >> destroyInstance >> >> Is there any reason for this duplication? Which one would you remove >> (the performaAction or the individual methods)? >> >> Thanks! >> André >I would remove the individual methods. Remember that I copied and hacked an ancient version of this code so some methods that Martin thought > might be useful were never used. I didn't go about pruning them. -- 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
13
0 / 0

[JBoss JIRA] Created: (JBIDE-7366) Properties Viewer doesn't show keyname for RUNNING instances after refresh or initial start-up

by Jeff Johnston (JIRA)

Properties Viewer doesn't show keyname for RUNNING instances after refresh or initial start-up ---------------------------------------------------------------------------------------------- Key: JBIDE-7366 URL: https://jira.jboss.org/browse/JBIDE-7366 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.2.0.Beta1 Reporter: Jeff Johnston Fix For: 3.2.0.Beta2 If an instance is running and Deltacloud tools are brought up, the keyname is missing in the Properties viewer. The same occurs if the list of instances is refreshed. The keyname should be shown. -- 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

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-7260) Links in EC2 wizard are linking to the amazone console instead of to the relevant section

by Max Andersen (JIRA)

Links in EC2 wizard are linking to the amazone console instead of to the relevant section ----------------------------------------------------------------------------------------- Key: JBIDE-7260 URL: https://jira.jboss.org/browse/JBIDE-7260 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Reporter: Max Andersen -- 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

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-7596) Cannot generate entities properly with Seam Generate Entities command

by Martin Gencur (JIRA)

Cannot generate entities properly with Seam Generate Entities command ---------------------------------------------------------------------- Key: JBIDE-7596 URL: https://jira.jboss.org/browse/JBIDE-7596 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: LATER Environment: JBDS 4.0.0.Beta2-201011130005N-H27, Seam2 in EAP 4.3 CP09 CR2 Reporter: Martin Gencur Assignee: Alexey Kazakov Steps to reproduce the bug: 1) Create New Seam Web Project 2) Reverse engineer entities from database (Person,Vehicle) from : jdbc:mysql://vmg08.mw.lab.eng.bos.redhat.com:3306/seam3 (credential will be in private comment) 3) deploy the application 4) Click the "Vehicle list" link at the top, now you can see the error in the attached screenshot (javax.el.ELException: /VehicleList.xhtml @54,60 rendered="#{empty vehicleList.resultList}": Error reading 'resultList' on type org.domain.newwarproject.session.VehicleList_$$_javassist_seam_9) - that's because VehicleList really doesn't contain resultsList method -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-7284) the connection wizard does not disable the finish button if you change the url to an invalid one

by Andre Dietisheim (JIRA)

the connection wizard does not disable the finish button if you change the url to an invalid one ------------------------------------------------------------------------------------------------ Key: JBIDE-7284 URL: https://jira.jboss.org/browse/JBIDE-7284 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.Beta1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.0.Beta2 1) enter name, VALID Url, user and pw 2) correct the Url to get invalid. result: finish-button is enabled expected behavior: finish-button should be disabled -- 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
2
0 / 0

[JBoss JIRA] Created: (JBIDE-7307) user should be able to add new cloud connection in the context menu

by Andre Dietisheim (JIRA)

user should be able to add new cloud connection in the context menu ------------------------------------------------------------------- Key: JBIDE-7307 URL: https://jira.jboss.org/browse/JBIDE-7307 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: deltacloud Affects Versions: 3.2.0.Beta1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.0.Beta2 A user intuitively expects to be able to add a new cloud connection in the context menu of the cloud viewer. -- 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
3
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 November 2010