May 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14664) Wrong description in server creation wizard

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBIDE-14664: ----------------------------------------- Summary: Wrong description in server creation wizard Key: JBIDE-14664 URL: https://issues.jboss.org/browse/JBIDE-14664 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.1.0.Beta1 Reporter: Andrej Podhradsky Priority: Trivial Attachments: runtime1.png, runtime2.png During creating a runtime for EAP 6.1 (SOA 6.0) the wizard changes a version in a description. See the attachments. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14661) IEmbeddedCartidge: add missinging #getApplication

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14661?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-14661. ------------------------------------ nothing for QE to verify since this is only about the client library > IEmbeddedCartidge: add missinging #getApplication > ------------------------------------------------- > > Key: JBIDE-14661 > URL: https://issues.jboss.org/browse/JBIDE-14661 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Beta2 > > > An embedded cartridge is embedded to an application. Thus EmbeddedCartridgeResource offers #getApplication which returns the application the cartridge is embedded into. The method is simply missing from IEmbeddedCartridge -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12015) OpenShift Wizard - Use Default Location is confusing

by Stefan Bunciak (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12015?page=com.atlassian.jira.plugi... ] Stefan Bunciak closed JBIDE-12015. ---------------------------------- Verified in JBoss Developer Studio 7.0.0.Beta1a > OpenShift Wizard - Use Default Location is confusing > ---------------------------------------------------- > > Key: JBIDE-12015 > URL: https://issues.jboss.org/browse/JBIDE-12015 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.Beta3 > Reporter: Burr Sutter > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.0.Beta1 > > Attachments: git-clone-destination.png, Screen Shot 2012-05-25 at 10.57.18 AM.png > > > The Cloning Settings: Use default location - suggests that the end-user needs to put in his Git location - users have been trying to use "C:\Program Files (x86)\Git" and that causes some other errors. This is also not the end-user's project directory. We should find a way to better explain what is being asked for here. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13975) Import wizard: wrong connection selected when importing from OpenShift Explorer

by Stefan Bunciak (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13975?page=com.atlassian.jira.plugi... ] Stefan Bunciak closed JBIDE-13975. ---------------------------------- Verified in JBoss Developer Studio 7.0.0.Beta1a > Import wizard: wrong connection selected when importing from OpenShift Explorer > ------------------------------------------------------------------------------- > > Key: JBIDE-13975 > URL: https://issues.jboss.org/browse/JBIDE-13975 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Beta1 > > Attachments: wrong-connection-selected-in-dialog.png > > -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14658) Management poller too slow for synchronous polling, should be disabled

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14658?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-14658: ------------------------------------- The PR has been updated. The solution now involves the following: 1) Adding getProperty method to the IAS7ManagementDetails, which is a parameter to all management requests. This allows for extendability of future enhancements, which can then be served via a property key. 2) Adding a new PROPERTY_TIMEOUT string constant to serve as a property key 3) Synchronous state requests now force a timeout of less than 1 second. The getProperty interface method returns an Object to ensure that if in the future more complex additions are required, they can all be added via property keys without necessitating future api changes... only key additions. Each key should declare what type of values are acceptable for the given key. > Management poller too slow for synchronous polling, should be disabled > ---------------------------------------------------------------------- > > Key: JBIDE-14658 > URL: https://issues.jboss.org/browse/JBIDE-14658 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.0.Beta1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.1.0.Beta2 > > > The management poller has a timeout of 5000 ms deep in the app server client jar code. I haven't figured out how to isolate it yet, or to change the timeout value, and so until that can be done, it'd be better to ensure that the management poller is disabled for synchronous calls when the server is likely down (ie during a 'startup' call) until that can be figured out. > This would have the effect of the web port poller being used for such synchronous calls. This could be reversed once sufficient api was discovered / added to control the timeouts. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14663) Source lookup dialog shown twice on maven projects

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-14663: ----------------------------------- Summary: Source lookup dialog shown twice on maven projects Key: JBIDE-14663 URL: https://issues.jboss.org/browse/JBIDE-14663 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: maven Affects Versions: 4.1.0.Beta1 Reporter: Fred Bricon Assignee: Snjezana Peco Fix For: 4.1.0.Beta1 Source lookup dialog is shown twice on maven projects : http://screencast.com/t/3yESat96FIw I think our source lookup should ignore projects with the maven nature, since a m2e's source lookup mechanism is already running in the background. If maven nature is enabled AND source is set but missing THEN, it'd be ok to show our own stuff -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13434) BrowserSim: Take Screenshot action capture only part of the window

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13434?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-13434: ------------------------------------- No "shaking" screen doesn't fix screenshot > BrowserSim: Take Screenshot action capture only part of the window > ------------------------------------------------------------------ > > Key: JBIDE-13434 > URL: https://issues.jboss.org/browse/JBIDE-13434 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Fix For: 4.1.0.Beta2 > > Attachments: browsersim-screenshot-feature.png, iPadMini.png, samsungGalaxySIII.png, uncompletebrowsersim.png, uncompletescreenshot.png > > > BrowserSim should be able to take screenshot(skin + rendered page). -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2646) Cannot deploy created Seam2.2 project to EAP 5.2

by Tomas Remes (JIRA)

Tomas Remes created JBDS-2646: --------------------------------- Summary: Cannot deploy created Seam2.2 project to EAP 5.2 Key: JBDS-2646 URL: https://issues.jboss.org/browse/JBDS-2646 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: seam Affects Versions: 7.0.0.Beta1 Reporter: Tomas Remes Cannot deploy created Seam2.2 project to EAP 5.2, because of following exception, which is caused by wrong web.xml webapps tag values: {noformat} org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/home/tremes/EAP/ER6/jboss-eap-5.2/jboss-as/server/default/deploy/testproject.war/ at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:362) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:322) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:294) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:234) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1454) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1172) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1113) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:789) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:699) at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:409) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:294) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722) Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Element {http://xmlns.jcp.org/xml/ns/javaee}web-app is not bound as a global element. at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203) at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168) at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:189) at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:166) at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:137) at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:121) at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:304) at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:286) at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:203) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:348) ... 27 more Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Element {http://xmlns.jcp.org/xml/ns/javaee}web-app is not bound as a global element. at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:660) at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source) at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199) ... 36 more {noformat} -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14300) CordovaSim: need to implement phonegap's Capture.getFormatData() method

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14300?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-14300: ------------------------------------- Please provide steps how to verify this Jira > CordovaSim: need to implement phonegap's Capture.getFormatData() method > ----------------------------------------------------------------------- > > Key: JBIDE-14300 > URL: https://issues.jboss.org/browse/JBIDE-14300 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: browsersim > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.1.0.Beta1 > > > Capture.getFormatData method (http://docs.phonegap.com/en/2.6.0/cordova_media_capture_capture.md.html#M...) isn't implemented in the original ripple emulator. Need to implement it via javax.servlet API in conjunction with jetty server -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14362) CordovaSim: need to implement Phonegap's Barcode Scanner plugin

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14362?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-14362: ------------------------------------- Could you please provide more specific steps how to verify this Jira? How to import and run demo application within CordovaSim? > CordovaSim: need to implement Phonegap's Barcode Scanner plugin > ---------------------------------------------------------------- > > Key: JBIDE-14362 > URL: https://issues.jboss.org/browse/JBIDE-14362 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: browsersim > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.1.0.Beta1 > > > Here is a description of Barcode Scanner plugin - https://github.com/phonegap/phonegap-plugins/tree/master/iOS/BarcodeScanner, https://github.com/phonegap/phonegap-plugins/tree/master/Android/BarcodeS... > *4QAs* > An application to test with: https://github.com/wildabeast/BarcodeDemo -- 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

12 years, 11 months

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 May 2013