October 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-7442) Make QueryExporter configurable to execute queries with and without transaction

by Vitali Yemialyanchyk (JIRA)

Make QueryExporter configurable to execute queries with and without transaction ------------------------------------------------------------------------------- Key: JBIDE-7442 URL: https://jira.jboss.org/browse/JBIDE-7442 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Hibernate Affects Versions: 3.2.0.Beta2 Reporter: Vitali Yemialyanchyk Assignee: Max Andersen Priority: Minor Fix For: 3.2.0.Beta2 add a flag for QueryExporter which handle creation of transaction for queries. -- 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, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-111) JBDS40_023 Post-installation of application server

by Isaac Rooskov (JIRA)

JBDS40_023 Post-installation of application server --------------------------------------------------- Key: TOOLSDOC-111 URL: https://jira.jboss.org/browse/TOOLSDOC-111 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: Uncommitted -- 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, 5 months

2
7
0 / 0

[JBoss JIRA] Created: (JBIDE-6975) Could not publish to the server.

by Alexey Kazakov (JIRA)

Could not publish to the server. -------------------------------- Key: JBIDE-6975 URL: https://jira.jboss.org/browse/JBIDE-6975 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.2.0.M2 Reporter: Alexey Kazakov Assignee: Rob Stryker 1. Create a seam web project. Use JBoss AS 5.0 or 6.0 (didn't try others) as target servers. 2. Run the application on the server. 3. Error window appears with message that there is a problem with publishing. 4. See the log: java.lang.NullPointerException at org.jboss.ide.eclipse.as.core.publishers.PublishUtil.getResources(PublishUtil.java:231) at org.jboss.ide.eclipse.as.core.publishers.AbstractServerToolsPublisher.fullPublish(AbstractServerToolsPublisher.java:154) at org.jboss.ide.eclipse.as.core.publishers.AbstractServerToolsPublisher.publishModule(AbstractServerToolsPublisher.java:93) at org.jboss.ide.eclipse.as.core.publishers.AbstractPublishMethod.publishModule(AbstractPublishMethod.java:77) at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:67) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1016) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1106) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:939) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:775) at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2888) at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:337) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) It seems that the project has been published correctly in spite of the error message. Rob, let me know if you can't reproduce it. I will try to get more details. -- 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, 5 months

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-7424) Update visual editor palette to RichFaces 4.0

by Jay Balunas (JIRA)

Update visual editor palette to RichFaces 4.0 --------------------------------------------- Key: JBIDE-7424 URL: https://jira.jboss.org/browse/JBIDE-7424 Project: Tools (JBoss Tools) Issue Type: Task Components: JSF, Visual Page Editor core, Visual Page Editor Templates Reporter: Jay Balunas Assignee: Alexey Kazakov Fix For: 3.2.0.Beta2 The RichFaces team would like to work with the tools team on upgrading the JBoss IDE visual editor palette to include updated functionality and components for RichFaces 4.0. There is obviously some overlap to RichFaces 3.3, but there is also wide spread changes such as attribute names, and conventions. I will attach the current list of planned components, and we can discuss differences as needed. -- 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, 5 months

4
14
0 / 0

[JBoss JIRA] Created: (JBIDE-7431) testing connection credentials reports an error when creating/editing a connection

by Andre Dietisheim (JIRA)

testing connection credentials reports an error when creating/editing a connection ---------------------------------------------------------------------------------- Key: JBIDE-7431 URL: https://jira.jboss.org/browse/JBIDE-7431 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.Beta2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.0.Beta2 Attachments: Screenshot.png steps to reproduce: 1) have a mock server running 2) create a new connection to it 3) give it a name 4) set "mockuser" as user, "mockpassword" as password 5) test the connection by hitting the "Test" button Result: an error dialog pops up that reports that the instance "madeupValue" was not found Expected Result: The test succeeds -- 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, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-7437) cannot get hardware profiles on deltacloud mock server 0.0.8

by Andre Dietisheim (JIRA)

cannot get hardware profiles on deltacloud mock server 0.0.8 ------------------------------------------------------------ Key: JBIDE-7437 URL: https://jira.jboss.org/browse/JBIDE-7437 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Reporter: Andre Dietisheim Assignee: Andre Dietisheim Requests to list hardware profiles get responded correctly but the HardwareProfiles returned are not unmarshalled correctly. The accessors (getMemory() etc.) return null). -- 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, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-7401) deltacloud client cannot start/stop instances with deltacloud 0.0.8

by Andre Dietisheim (JIRA)

deltacloud client cannot start/stop instances with deltacloud 0.0.8 ------------------------------------------------------------------- Key: JBIDE-7401 URL: https://jira.jboss.org/browse/JBIDE-7401 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 The current client cannot start nor stop instances when running against deltacloud 0.0.8. The deltacloud server answers with 404. -- 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, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-7259) Cannot create a connection to the deltacloud server

by Andre Dietisheim (JIRA)

Cannot create a connection to the deltacloud server --------------------------------------------------- Key: JBIDE-7259 URL: https://jira.jboss.org/browse/JBIDE-7259 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.M2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim I cannot create a connection to a local deltacloud server v0.0.7. The wizard reports that the URL (http://localhost:3001) is not a valid Deltacloud instance. The server throws an error 500: RuntimeError - Invalid header value: "*; q=.2": /usr/lib/ruby/gems/1.8/gems/rack-accept-0.4.3/lib/rack/accept/header.rb:19:in `parse' /usr/lib/ruby/gems/1.8/gems/rack-accept-0.4.3/lib/rack/accept/header.rb:13:in `each' /usr/lib/ruby/gems/1.8/gems/rack-accept-0.4.3/lib/rack/accept/header.rb:13:in `parse' /usr/lib/ruby/gems/1.8/gems/rack-accept-0.4.3/lib/rack/accept/header.rb:70:in `initialize' /usr/lib/ruby/gems/1.8/gems/rack-accept-0.4.3/lib/rack/accept/media_type.rb:49:in `initialize' /usr/lib/ruby/gems/1.8/gems/rack-accept-0.4.3/lib/rack/accept/request.rb:16:in `new' /usr/lib/ruby/gems/1.8/gems/rack-accept-0.4.3/lib/rack/accept/request.rb:16:in `media_type' ./lib/sinatra/respond_to.rb:103:in `registered' /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:461:in `instance_eval' /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:461:in `before_filter!' /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:461:in `each' /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:461:in `before_filter!' /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:600:in `dispatch!' /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:411:in `call!' /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:566:in `instance_eval' /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:566:in `invoke' /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:566:in `catch' /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:566:in `invoke' /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:411:in `call!' /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:399:in `call' /usr/lib/ruby/gems/1.8/gems/rack-accept-0.4.3/lib/rack/accept/context.rb:22:in `call' /usr/lib/ruby/gems/1.8/gems/rack-1.1.0/lib/rack/methodoverride.rb:24:in `call' /usr/lib/ruby/gems/1.8/gems/rack-1.1.0/lib/rack/commonlogger.rb:18:in `call' /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:979:in `call' /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:1005:in `synchronize' /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:979:in `call' /usr/lib/ruby/gems/1.8/gems/thin-1.2.7/lib/thin/stats.rb:24:in `call' /usr/lib/ruby/gems/1.8/gems/thin-1.2.7/lib/thin/stats.rb:33:in `log' /usr/lib/ruby/gems/1.8/gems/thin-1.2.7/lib/thin/stats.rb:24:in `call' /usr/lib/ruby/gems/1.8/gems/thin-1.2.7/lib/thin/connection.rb:76:in `pre_process' /usr/lib/ruby/gems/1.8/gems/thin-1.2.7/lib/thin/connection.rb:74:in `catch' /usr/lib/ruby/gems/1.8/gems/thin-1.2.7/lib/thin/connection.rb:74:in `pre_process' /usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1060:in `call' /usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1060:in `spawn_threadpool' /usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1057:in `initialize' /usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1057:in `new' /usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1057:in `spawn_threadpool' /usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1049:in `defer' /usr/lib/ruby/gems/1.8/gems/thin-1.2.7/lib/thin/connection.rb:54:in `process' /usr/lib/ruby/gems/1.8/gems/thin-1.2.7/lib/thin/connection.rb:42:in `receive_data' /usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in `run_machine' /usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in `run' /usr/lib/ruby/gems/1.8/gems/thin-1.2.7/lib/thin/backends/base.rb:57:in `start' /usr/lib/ruby/gems/1.8/gems/thin-1.2.7/lib/thin/server.rb:156:in `start' /usr/lib/ruby/gems/1.8/gems/thin-1.2.7/lib/thin/controllers/controller.rb:80:in `start' /usr/lib/ruby/gems/1.8/gems/thin-1.2.7/lib/thin/runner.rb:177:in `send' /usr/lib/ruby/gems/1.8/gems/thin-1.2.7/lib/thin/runner.rb:177:in `run_command' /usr/lib/ruby/gems/1.8/gems/thin-1.2.7/lib/thin/runner.rb:143:in `run!' /usr/lib/ruby/gems/1.8/gems/thin-1.2.7/bin/thin:6 /usr/bin/thin:19:in `load' /usr/bin/thin:19 127.0.0.1 - - [05/Oct/2010 16:32:01] "GET /api.xml HTTP/1.1" 500 30 0.1516 If I connect to the same instance with a browser by slightly chaning the requested URL, I can get the API: http://localhost:3001/api?format=xml -> <api driver='mock' version='0.1'> <link href='http://localhost:3001/api/images' rel='images'> </link> <link href='http://localhost:3001/api/storage_volumes' rel='storage_volumes'> </link> <link href='http://localhost:3001/api/hardware_profiles' rel='hardware_profiles'> </link> <link href='http://localhost:3001/api/instance_states' rel='instance_states'> </link> <link href='http://localhost:3001/api/realms' rel='realms'> </link> <link href='http://localhost:3001/api/instances' rel='instances'> <feature name='hardware_profiles'></feature> <feature name='user_name'></feature> </link> <link href='http://localhost:3001/api/storage_snapshots' rel='storage_snapshots'> </link> </api> According to the deltacloud guys, a recent API change disabled content negotiation, so requesting .xml does not work any more. The content type has to be indicated in a url parameter (format=). Furthermore the deltacloud server seems no to be able to process a accept-header the tools use: "*; q=.2": -- 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, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-7193) Need to add new parameters for BusinessRulesProcessor action in ESB Editor

by Brian Fitzpatrick (JIRA)

Need to add new parameters for BusinessRulesProcessor action in ESB Editor -------------------------------------------------------------------------- Key: JBIDE-7193 URL: https://jira.jboss.org/browse/JBIDE-7193 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.2.0.Beta1 Reporter: Brian Fitzpatrick Assignee: Brian Fitzpatrick Fix For: 3.2.0.Beta2 BusinessRulesProcessor will need a couple of new parameters for JBESB-3403. More details forthcoming. -- 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, 5 months

4
9
0 / 0

[JBoss JIRA] Created: (JBIDE-7062) usage report should track eclipse sessions

by Andre Dietisheim (JIRA)

usage report should track eclipse sessions ------------------------------------------ Key: JBIDE-7062 URL: https://jira.jboss.org/browse/JBIDE-7062 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: usage Affects Versions: 3.2.0.M2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim There are 2 levels of uniqueness: - session (aka work session in Eclipse) -> reported as "page view" / "unique page view" - Eclipse instance -> reported as "New Visitor" / "Returning Visitor" Eclipse instances are trackable by querying the stats for 'Visitor Type' and the value 'New Visitor'/'Returning Visitor'. My plugin currently counts visits and GA recognizes this and reports accordingly. It would be nice to have a match towards the sessions, too. Unfortunately I'm still not 100% sure how this stuff works. There are cookies for this (utmb, utmc) but no spec that details the values. -- 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, 5 months

2
2
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 October 2010