October 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-1546) Adjust selection repaint

by Maxim Areshkau (JIRA)

Adjust selection repaint ------------------------ Key: JBIDE-1546 URL: http://jira.jboss.com/jira/browse/JBIDE-1546 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Affects Versions: 2.0.0.GA Reporter: Maxim Areshkau Assigned To: Maxim Areshkau Fix For: LATER inIFlasher doesn't repaint content when we scrool page. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
15
0 / 0

[JBoss JIRA] Created: (JBIDE-4915) Add the VPE Toolbar to the Preview tab

by Yahor Radtsevich (JIRA)

Add the VPE Toolbar to the Preview tab -------------------------------------- Key: JBIDE-4915 URL: https://jira.jboss.org/jira/browse/JBIDE-4915 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor core Affects Versions: 3.1.0.M2 Reporter: Yahor Radtsevich Assignee: Maxim Areshkau It would be good, if the VPE Preview tab had the same toolbar as the Visual/Source tab. For example, Someone edit a CSS file and want to have an affected page to be shown in the VPE (see screenshot-1.png). Of course, he wants to see the changes on the page, but he can't - there is no refresh button. -- 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

15 years, 2 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-7412) Deploy only server needs rse support

by Rob Stryker (JIRA)

Deploy only server needs rse support ------------------------------------ Key: JBIDE-7412 URL: https://jira.jboss.org/browse/JBIDE-7412 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Affects Versions: 3.2.0.Beta1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.2.0.Beta2 -- 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, 2 months

3
11
0 / 0

[JBoss JIRA] Created: (JBIDE-7199) Seam 2.2.1CR1 + JBDS4M2 + AS6M5 = SHA1 digest error for jdtCompilerAdapter.jar

by Burr Sutter (JIRA)

Seam 2.2.1CR1 + JBDS4M2 + AS6M5 = SHA1 digest error for jdtCompilerAdapter.jar ------------------------------------------------------------------------------ Key: JBIDE-7199 URL: https://jira.jboss.org/browse/JBIDE-7199 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.2.0.M2 Environment: Win 7 Java 1.6 32-bit Reporter: Burr Sutter Assignee: Alexey Kazakov Attachments: boot.log, server.log New Seam Web Project - using Seam 2.2.1CR1 to target JBoss AS6 M5, it fails on deployment. 10:06:23,314 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Real: name=vfs:///D:/servers/jboss-6.0.0.20100911-M5/server/default/deploy/SeamWebProject1.war state=PreReal mode=Manual requiredState=Real: org.jboss.deployers.spi.DeploymentException: Failed to create web module at org.jboss.web.deployers.AbstractWarDeployer.deploy(AbstractWarDeployer.java:461) [:6.0.0.20100911-M5] at org.jboss.web.deployers.AbstractWarDeployer.deploy(AbstractWarDeployer.java:106) [:6.0.0.20100911-M5] at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62) [:2.2.0.Alpha7] at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55) [:2.2.0.Alpha7] at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) [:2.2.0.Alpha7] at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1832) [:2.2.0.Alpha7] at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1550) [:2.2.0.Alpha7] at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1491) [:2.2.0.Alpha7] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:1983) [:2.2.0.Alpha7] at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1076) [:2.2.0.Alpha7] at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679) [:2.2.0.Alpha7] at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.process(MainDeployerPlugin.java:106) [:6.0.0.20100911-M5] at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.process(ProfileControllerContext.java:130) [:0.1.0.Alpha1] at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.deploy(HDScanner.java:240) [:0.1.0.Alpha1] at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.complete(HDScanner.java:192) [:0.1.0.Alpha1] at org.jboss.profileservice.management.TwoPCActionWrapper.doComplete(TwoPCActionWrapper.java:59) [:0.1.0.Alpha1] at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.complete(AbstractTwoPhaseModificationAction.java:74) [:0.1.0.Alpha1] at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.prepare(AbstractTwoPhaseModificationAction.java:94) [:0.1.0.Alpha1] at org.jboss.profileservice.management.ModificationSession.prepare(ModificationSession.java:87) [:0.1.0.Alpha1] at org.jboss.profileservice.management.AbstractActionController.internalPerfom(AbstractActionController.java:234) [:0.1.0.Alpha1] at org.jboss.profileservice.management.AbstractActionController.performWrite(AbstractActionController.java:213) [:0.1.0.Alpha1] at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:150) [:0.1.0.Alpha1] at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:135) [:0.1.0.Alpha1] at org.jboss.profileservice.deployment.hotdeploy.HDScanner.scan(HDScanner.java:146) [:0.1.0.Alpha1] at org.jboss.profileservice.deployment.hotdeploy.HDScanner.run(HDScanner.java:90) [:0.1.0.Alpha1] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_20] at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) [:1.6.0_20] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) [:1.6.0_20] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) [:1.6.0_20] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) [:1.6.0_20] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) [:1.6.0_20] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_20] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_20] at java.lang.Thread.run(Thread.java:619) [:1.6.0_20] Caused by: java.lang.SecurityException: SHA1 digest error for jdtCompilerAdapter.jar at sun.security.util.ManifestEntryVerifier.verify(ManifestEntryVerifier.java:192) [:1.6.0_20] at java.util.jar.JarVerifier.processEntry(JarVerifier.java:212) [:1.6.0_20] at java.util.jar.JarVerifier.update(JarVerifier.java:199) [:1.6.0_20] at java.util.jar.JarVerifier$VerifierStream.read(JarVerifier.java:449) [:1.6.0_20] at java.io.InputStream.read(InputStream.java:85) [:1.6.0_20] at org.jboss.vfs.VFSUtils.copyStream(VFSUtils.java:439) [jboss-vfs.jar:3.0.0.CR5] at org.jboss.vfs.VFSUtils.copyStreamAndClose(VFSUtils.java:398) [jboss-vfs.jar:3.0.0.CR5] at org.jboss.vfs.VFSUtils.copyStreamAndClose(VFSUtils.java:383) [jboss-vfs.jar:3.0.0.CR5] at org.jboss.vfs.spi.JavaZipFileSystem.getFile(JavaZipFileSystem.java:157) [jboss-vfs.jar:3.0.0.CR5] at org.jboss.vfs.VirtualFile.getPhysicalFile(VirtualFile.java:261) [jboss-vfs.jar:3.0.0.CR5] at org.jboss.web.deployers.AbstractWarDeployer$1.visit(AbstractWarDeployer.java:795) [:6.0.0.20100911-M5] at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:407) [jboss-vfs.jar:3.0.0.CR5] at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:409) [jboss-vfs.jar:3.0.0.CR5] at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:409) [jboss-vfs.jar:3.0.0.CR5] at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:409) [jboss-vfs.jar:3.0.0.CR5] at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:395) [jboss-vfs.jar:3.0.0.CR5] at org.jboss.web.deployers.AbstractWarDeployer.getExplodedWarUrl(AbstractWarDeployer.java:808) [:6.0.0.20100911-M5] at org.jboss.web.deployers.AbstractWarDeployer.deploy(AbstractWarDeployer.java:374) [:6.0.0.20100911-M5] ... 41 more -- 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, 2 months

5
18
0 / 0

[JBoss JIRA] Created: (JBDS-1114) Provide JBDS update site zip for offline updates

by Nick Boldt (JIRA)

Provide JBDS update site zip for offline updates ------------------------------------------------ Key: JBDS-1114 URL: https://jira.jboss.org/jira/browse/JBDS-1114 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: updatesite Affects Versions: 3.0.1.GA Reporter: Nick Boldt Assignee: Nick Boldt Priority: Minor Fix For: LATER >> For now, updatesite zip distro for JBDS is not supported since it haven't >> been tested how the branding and the runtime integration plugins we have done >> works from the updatesite zip. (and it would need documentation too) >> /max Two issues here are: 1) having the branded fragments/binary pieces on the site, which we don't include today 2) documenting how to do an install/upgrade from update site or site zip -- 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

15 years, 2 months

7
18
0 / 0

[JBoss JIRA] Created: (JBDS-1375) Welcome page options should better represent SOA Platform technologies

by Ken Johnson (JIRA)

Welcome page options should better represent SOA Platform technologies ---------------------------------------------------------------------- Key: JBDS-1375 URL: https://jira.jboss.org/browse/JBDS-1375 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Affects Versions: 4.0.0.Beta1 Environment: RHEL 6, Sun JDK Reporter: Ken Johnson Priority: Minor On the Welcome page (Help->Welcome), there are several options. SOA/integration technologies are not well represented. For example: Create New.. -- should offer options to create other JBoss project types like Drools, ESB and Data Services Perspectives -- should include Drools and Teiid Designer perspectives -- 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, 2 months

5
14
0 / 0

[JBoss JIRA] Created: (JBDS-1355) Import ESB examples - JBDS complains about runtime name - even if the name is what the error messge specifies

by Len DiMaggio (JIRA)

Import ESB examples - JBDS complains about runtime name - even if the name is what the error messge specifies ------------------------------------------------------------------------------------------------------------- Key: JBDS-1355 URL: https://jira.jboss.org/browse/JBDS-1355 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Affects Versions: 4.0.0.Beta1 Environment: Version: 4.0.0.Beta1 Build id: v201010052359R Build date: 201010060016 Reporter: Len DiMaggio Priority: Minor See the attached screen shot - the run time was named just as JBDS specified - but the error is still seen -- 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, 2 months

5
17
0 / 0

[JBoss JIRA] Created: (JBDS-1357) Deploy an .esb project to a server in JBDS results in log error

by Len DiMaggio (JIRA)

Deploy an .esb project to a server in JBDS results in log error --------------------------------------------------------------- Key: JBDS-1357 URL: https://jira.jboss.org/browse/JBDS-1357 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: integration Affects Versions: 4.0.0.Beta1 Environment: Version: 4.0.0.Beta1 Build id: v201010052359R Build date: 201010060016 Reporter: Len DiMaggio The project is created - but an error is logged -- 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, 2 months

4
11
0 / 0

[JBoss JIRA] Created: (JBDS-942) JBDS 2.1 GA on a Mac performs very slowly

by Jim Tyrrell (JIRA)

JBDS 2.1 GA on a Mac performs very slowly ----------------------------------------- Key: JBDS-942 URL: https://jira.jboss.org/jira/browse/JBDS-942 Project: JBoss Developer Studio Issue Type: Feature Request Affects Versions: 2.1.0 Environment: Mac with Snow Leopard Reporter: Jim Tyrrell Starting the embedded EAP 5 instance included in the JBDS 2.1 build jbdevstudio-eap-macosx-carbon-2.1.0.v200909250150R-H168-GA.jar takes a long time. About 1 minute once, and mostly 3-5 mins. It does not seem to change or become different based on the number of other applications I have running. Double clicking on a .xhtml file and bringing up the embedded two paned JSF editor also can take minutes to come up. Shutting down the embedded EAP server, or closing out of eclipse can take minutes. I have also experienced 3-4 crashes in about 5-6 times running this and can not seem to isolate it to a specific set of actions. I have run a version on Linux and do not experience any of the same symptoms as noted above. Wondering out loud if JDK 6 on Snow Leopard is not something that would be recommended or creates some of these gremlins. Macintosh-75:Downloads jimtyrrell$ java -version java version "1.6.0_15" Java(TM) SE Runtime Environment (build 1.6.0_15-b03-219) Java HotSpot(TM) 64-Bit Server VM (build 14.1-b02-90, mixed mode) -- 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

15 years, 2 months

7
20
0 / 0

[JBoss JIRA] Created: (JBIDE-6368) Should nest categories in update site

by John Verhaeg (JIRA)

Should nest categories in update site ------------------------------------- Key: JBIDE-6368 URL: https://jira.jboss.org/browse/JBIDE-6368 Project: Tools (JBoss Tools) Issue Type: Task Components: updatesite Affects Versions: 3.2.next Reporter: John Verhaeg Assignee: Nick Boldt As discussed somewhat in JBIDE-4859, it seems like we should nest our categories in our update site. So, instead of having lots of sibling categories for the various tools in JBT alongside a sibling "All JBoss Tools" category, the latter should be promoted to a parent category for the others (dropping the "All" prefix). For example: - JBoss Tools - SOA Development - JBoss ESB Tools - Drools Core ... - Data Services - Hibernate - ModeShape - Smooks - Teiid Data Tools Connectivity - Teiid Designer Design-Time - Teiid Designer Runtime BTW, IMO having features in multiple categories blows. I don't like seeing this with other Eclipse projects either. Just my 2 cents. -- 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, 2 months

5
17
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