March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13631) URL for embedded cartridges is empty

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13631?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-13631: ------------------------------------------------- Hou Jianwei <jhou(a)redhat.com> made a comment on [bug 923442|https://bugzilla.redhat.com/show_bug.cgi?id=923442] Verified with li/misc/maintenance/bin/migrate-2.0.25.1 Steps: 1. On an old devenv-stage_326 instance, create several scalable apps with mysql/mongo/postgresql cartridges 2. Go to https://broker/datastore , update the connection urls of these apps to the old fashioned way( eg: change mongodb://$OPENSHIFT_MONGODB_DB_HOST:$OPENSHIFT_MONGODB_DB_PORT to mongodb://myapp-mydomain.rhcloud.com:48681 ) 3. Upgrade server to latest 4. On broker execute the migrate-2.0.25.1 to fix the connection urls 5. On client, retrieve app info The db connections are updated to format like: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/ mongodb://$OPENSHIFT_MONGODB_DB_HOST:$OPENSHIFT_MONGODB_DB_PORT/ postgresql://$OPENSHIFT_POSTGRESQL_DB_HOST:$OPENSHIFT_POSTGRESQL_DB_PORT/ 6. SSH into gear, connect to db cartridges Was able to connect to all db cartridges. > URL for embedded cartridges is empty > ------------------------------------ > > Key: JBIDE-13631 > URL: https://issues.jboss.org/browse/JBIDE-13631 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.0.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha2 > > Attachments: existing-application.json, mysql-url-after-creation.png, mysql-url-at-creation.png, mysql-url-listed.png, new-user-creation-dialog.png, new-user-mongo-url-listed.png, new-user-mysql-url-listed.png, no-url.png > > > Embedded cartridges for OpenShift application have an URL property. Currently JBDS/JBT doesn't show any, all URLs are blank -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13631) URL for embedded cartridges is empty

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13631?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-13631: ------------------------------------------------- Hou Jianwei <jhou(a)redhat.com> changed the Status of [bug 923442|https://bugzilla.redhat.com/show_bug.cgi?id=923442] from ON_QA to VERIFIED > URL for embedded cartridges is empty > ------------------------------------ > > Key: JBIDE-13631 > URL: https://issues.jboss.org/browse/JBIDE-13631 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.0.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha2 > > Attachments: existing-application.json, mysql-url-after-creation.png, mysql-url-at-creation.png, mysql-url-listed.png, new-user-creation-dialog.png, new-user-mongo-url-listed.png, new-user-mysql-url-listed.png, no-url.png > > > Embedded cartridges for OpenShift application have an URL property. Currently JBDS/JBT doesn't show any, all URLs are blank -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13861) Server should be automatically added to list after a "Download"

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-13861: -------------------------------------- Summary: Server should be automatically added to list after a "Download" Key: JBIDE-13861 URL: https://issues.jboss.org/browse/JBIDE-13861 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers Affects Versions: 4.1.0.Alpha1 Reporter: Mickael Istria Assignee: Rob Stryker When Downloading a new Server (in Preferences > JBoss Tools Runtimes > Download...), this server should automatically be added to the available servers. I add to click "Add" after "Download..." completed. Also, the only feedback that server is downloading is in Eclipse status bar. It's not quite visible. A pop-up with a progress bar would be more explicit. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13813) BrowserSim: need Web SQL API for Cordova Simulator

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13813?page=com.atlassian.jira.plugi... ] Yahor Radtsevich commented on JBIDE-13813: ------------------------------------------ [Blackberry's tests for Web SQL API|https://github.com/yradtsevich/pure-js-websql/blob/master/js/purejswe...]. Now most of them pass for our implementation, except: * {{executesql-accepts-only-one-statement.html}} * {{test-authorizer.html}} * {{read-transactions-running-concurrently.html}} > BrowserSim: need Web SQL API for Cordova Simulator > -------------------------------------------------- > > Key: JBIDE-13813 > URL: https://issues.jboss.org/browse/JBIDE-13813 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: Visual Page Editor core > Reporter: Yahor Radtsevich > Assignee: Yahor Radtsevich > Fix For: 4.1.0.Beta1 > > > Cordova's Storage API is based on Web SQL API. This API is widely used in Cordova-based applications. > The problem is that Safari's Web SQL API is not available in SWT Browser on Windows. A way to provide this API is needed. > *Update:* > Yahor [created|https://github.com/yradtsevich/pure-js-websql] a basic Web SQL API implementation based on [SQL.js|https://github.com/kripken/sql.js]. Demo is [here|http://htmlpreview.github.com/?https://github.com/yradtsevich/pure-j...]. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13827) CDI Beans created in newly created CDI project are not compilable

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13827?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-13827: ------------------------------------- Currently, projects targeting eap6.1 do not have ANY jars added to the their classpath, because we have been informed that reaching in to a jboss installation for jars is pretty much unacceptable. Until this issue is resolved, we can't move on this. > CDI Beans created in newly created CDI project are not compilable > ----------------------------------------------------------------- > > Key: JBIDE-13827 > URL: https://issues.jboss.org/browse/JBIDE-13827 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Environment: JBDS 6.0.1.CR1, JBDS 7.0.0.Alpha, EAP 6.1.0.ER3 > Reporter: Tomas Remes > Assignee: Rob Stryker > Fix For: 4.1.0.Alpha2 > > > It is not possible to create valid Named Bean, Interceptor,etc. using EAP 6.1 Runtime, because it cannot find packages javax.inject.*, javax.interceptor.*, etc. I guess that's related to changed modules directory structure in EAP. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13733) Clean up JBossASHandler

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13733?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-13733. --------------------------------- Resolution: Done pushed to master. To test this, please use an environment WITH esb and drools tools. Verify the following: 1) If AS Handler is disabled, a search of a soa-p folder does return a standalone drools runtime 2) If AS Handler is disabled, a search of a soa-p folder does return a standalone esb runtime 3) If AS Handler is enabled, but others disabled, ONLY an astools runtime is located 4) If all handlers are enabled, an AS runtime is found, with nested runtimes fo esb and drools. > Clean up JBossASHandler > ----------------------- > > Key: JBIDE-13733 > URL: https://issues.jboss.org/browse/JBIDE-13733 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: JBossAS/Servers > Affects Versions: 4.1.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.1.0.Alpha2 > > > JBossASHandler is a pretty messy class with many confusing parts to it. Several things need to be changed. > 1) Why are default names for server required in this class? Don't runtime type and server type already do this in getDefaults() when the working copy is created? > 2) The code to check for nested runtimes is very messy and hard to understand. > 3) Why are ESB and Drools added separately? Shouldn't the check for all nested runtimes using all handlers be able to find this itself? It seems drools and esb have their own detectors. So why is this required here? > 4) The drools runtime seems to be not added to any model at all. It seems to just be returned. Is this only cosmetic? What is the purpose here? The drools detector would be adding this to the drools model, but we do not add it to any model, so what is the purpose? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-10588) Installing on top of plain Eclipse IDE JBoss Maven Seam Integration plugin breaks Maven integration for WTP

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10588?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-10588. --------------------------------- Fix Version/s: 4.1.0.Alpha2 (was: 3.3.x) Resolution: Done Fixed with commit https://github.com/jbosstools/jbosstools-central/commit/1dd4232bec7d3af22... Tested on Eclipse Classic Kepler M6 + JBoss Maven Seam Integration > Installing on top of plain Eclipse IDE JBoss Maven Seam Integration plugin breaks Maven integration for WTP > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-10588 > URL: https://issues.jboss.org/browse/JBIDE-10588 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 3.3.0.M5 > Environment: Eclipse 3.7.1.20110916-0149, m2e 1.0.100.20110804-1717, m2e-wtp 0.14.0.20110928-2045 > Reporter: Rafal Krzewski > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.1.0.Alpha2 > > Attachments: JBIDE-10588-test-setup.p2f > > > After installing istalling JBoss Maven Seam Integration plugin from http://download.jboss.org/jbosstools/updates/development/indigo/ m2e-wtp configurator stopped working. Running Maven > Update Configuration produces to following error on any project that is using war or ejb packaging (ear is OK): > Project configurator "org.jboss.tools.maven.seam.configurator" is not available. To enable full functionality, install the project configurator and run Maven->Update Project Configuration. > Additionally, maven-ejb-plugin and maven-war-plugin executions are reported as not covered by by lifecycle configuration. > I've checked with OSGi host console and org.jboss.tools.maven.seam bundle is deployed: > osgi> ss org.jboss.tools.maven.seam > id State Bundle > 774 ACTIVE org.jboss.tools.maven.seam_1.3.0.v20111209-0524-H40-M5 > The configurator extension is also deployed: > osgi> pt -v org.eclipse.m2e.core.projectConfigurators > Extension(s): > ------------------- > null [from org.jboss.tools.maven.seam] > <configurator> > id = org.jboss.tools.maven.seam.configurator > class = org.jboss.tools.maven.seam.configurators.SeamProjectConfigurator > name = Seam > secondaryTo = org.maven.ide.eclipse.configuration.wtp.configurator > </configurator> > Alas, the configurator class cannot be instantiated. Eclipse error log contains the following: > Plug-in "org.jboss.tools.maven.seam" was unable to instantiate class "org.jboss.tools.maven.seam.configurators.SeamProjectConfigurator". > An exception stack trace is not available. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13715) soa-p 5.3 is incorrectly detected as 5.2

by Petr Suchý (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13715?page=com.atlassian.jira.plugi... ] Petr Suchý commented on JBIDE-13715: ------------------------------------ It should be verified in JBDS 7.0.0.Alpha2 as well, so I cloned this issue to JBIDE-13860 for master. > soa-p 5.3 is incorrectly detected as 5.2 > ---------------------------------------- > > Key: JBIDE-13715 > URL: https://issues.jboss.org/browse/JBIDE-13715 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.0.0.Final, 4.1.0.Alpha1 > Reporter: Martin Malina > Assignee: Snjezana Peco > Labels: respin-a > Fix For: 4.0.1.Final, 4.1.0.Alpha2 > > Attachments: 601_CR1a_Screenshot.png, Screenshot.png > > > When you use the runtime detection feature to add a soa-p 5.3.1 server it is detected as SOA-P version 5.2. > When you add the server manually, there is no server type soa-p, so there you have to choose EAP 5.x anyway and so this issue is not present there. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13860) soa-p 5.3 is incorrectly detected as 5.2 (master)

by Petr Suchý (JIRA)

Petr Suchý created JBIDE-13860: ---------------------------------- Summary: soa-p 5.3 is incorrectly detected as 5.2 (master) Key: JBIDE-13860 URL: https://issues.jboss.org/browse/JBIDE-13860 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtime-detection Affects Versions: 4.0.0.Final, 4.1.0.Alpha1 Reporter: Petr Suchý Assignee: Snjezana Peco Fix For: 4.0.1.Final, 4.1.0.Alpha2 When you use the runtime detection feature to add a soa-p 5.3.1 server it is detected as SOA-P version 5.2. When you add the server manually, there is no server type soa-p, so there you have to choose EAP 5.x anyway and so this issue is not present there. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13860) soa-p 5.3 is incorrectly detected as 5.2 (master)

by Petr Suchý (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13860?page=com.atlassian.jira.plugi... ] Petr Suchý updated JBIDE-13860: ------------------------------- Fix Version/s: (was: 4.0.1.Final) > soa-p 5.3 is incorrectly detected as 5.2 (master) > ------------------------------------------------- > > Key: JBIDE-13860 > URL: https://issues.jboss.org/browse/JBIDE-13860 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.0.0.Final, 4.1.0.Alpha1 > Reporter: Petr Suchý > Assignee: Snjezana Peco > Labels: respin-a > Fix For: 4.1.0.Alpha2 > > > When you use the runtime detection feature to add a soa-p 5.3.1 server it is detected as SOA-P version 5.2. > When you add the server manually, there is no server type soa-p, so there you have to choose EAP 5.x anyway and so this issue is not present there. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
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 2013