April 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13061) Freemarker ui tests are failing on JDK 1.7

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-13061: ------------------------------------ Summary: Freemarker ui tests are failing on JDK 1.7 Key: JBIDE-13061 URL: https://issues.jboss.org/browse/JBIDE-13061 Project: Tools (JBoss Tools) Issue Type: Bug Components: QA Affects Versions: 4.0.0.Beta2 Reporter: Jiri Peterka Assignee: Jiri Peterka Fix For: 4.0.0.Beta2 There is a profile wrongly set AWT toolkit in https://github.com/jbosstools/jbosstools-integration-tests/blob/master/te... -- 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

1 week, 1 day

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6878) Seam does not work with JSF 2.0 faces-config.xml

by Alexey Kazakov (JIRA)

Seam does not work with JSF 2.0 faces-config.xml ------------------------------------------------ Key: JBIDE-6878 URL: https://jira.jboss.org/browse/JBIDE-6878 Project: Tools (JBoss Tools) Issue Type: Bug Components: UpStream Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.2.x This is an issue of Seam runtime. See https://jira.jboss.org/browse/JBSEAM-4637 But let's have a duplicate it in JBT JIRA to track JBSEAM-4637 -- 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

3 weeks, 6 days

3
5
0 / 0

[JBoss JIRA] Created: (JBDS-983) Console not showing up when staritng a EAP/SOA-P Instance

by Jim Tyrrell (JIRA)

Console not showing up when staritng a EAP/SOA-P Instance --------------------------------------------------------- Key: JBDS-983 URL: https://jira.jboss.org/jira/browse/JBDS-983 Project: JBoss Developer Studio Issue Type: Feature Request Affects Versions: 3.0.0.M4 Reporter: Jim Tyrrell For some reason starting a SOA-P instance by right clicking in the server view does not start/open the console for the output of the server as it is starting. For EAP and Seam projects this does not seem to be the case as often, but I think I have seen it. The current JBDS 3.0 M4 release does seem to not show the console unless I open the console via the Window -> Show View -> General -> Console and then I have to click an icon to enable the "Java Stack Trace Console". Once I have setup the console once as just noted even if I close it it will open as I expect. If I close JBDS and make sure that the console was not left open, I get the same behaviour when I try to right click on the SOA-P instance. -- 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

3 months, 1 week

5
8
0 / 0

[JBoss JIRA] Created: (JBIDE-5287) Block comment doesn't remove if code selected by 'Ctrl+A' for xhtml file.

by Svetlana Yasenovich (JIRA)

Block comment doesn't remove if code selected by 'Ctrl+A' for xhtml file. ------------------------------------------------------------------------- Key: JBIDE-5287 URL: https://jira.jboss.org/jira/browse/JBIDE-5287 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Environment: JBoss Developer Studio Version: 3.0.0.M4 Build id: v200911180352M Reporter: Svetlana Yasenovich Priority: Minor 1. Open .xhtml file. 2. click 'Ctrl+A' -> all code selected 3. click 'Ctrl+Shift+/' (Source->Add Block Comment) ->all code commented 4. click 'Ctrl+A' 5. click 'Ctrl+Shift+\' (Source->Remove Block Comment) -> nothing happened Expected Result : Remove Block Comment for all code -- 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

11 months, 1 week

3
7
0 / 0

[JBoss JIRA] (JBIDE-14359) Add BrowserSim into "Show in" sub-menu for server module in Servers View

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-14359: ------------------------------------- Summary: Add BrowserSim into "Show in" sub-menu for server module in Servers View Key: JBIDE-14359 URL: https://issues.jboss.org/browse/JBIDE-14359 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: browsersim, server Affects Versions: 4.1.0.Alpha2 Reporter: Denis Golovin -- 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-13159) gwt-kitchensink fails to deploy - class not found

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13159?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-13159: --------------------------------------- @[~mmalina]: GWT configurator doesn't help. What do help is changing OpenJDK 7 to 6. > gwt-kitchensink fails to deploy - class not found > ------------------------------------------------- > > Key: JBIDE-13159 > URL: https://issues.jboss.org/browse/JBIDE-13159 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: GWT, maven > Affects Versions: 4.0.0.CR1 > Environment: JBDS 6.0.0.CR1a B133 > JBT 4.0.0.CR1a B97 > OS X 10.8.2 > Oracle Java 1.7 > Reporter: Martin Malina > Assignee: Snjezana Peco > Fix For: 4.1.0.Beta1 > > > When you try to deploy the gwt project from Central, it fails to deploy with the following error: > {code} > 15:27:18,698 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found jboss-gwt-webapp.war in deployment directory. To trigger deployment create a file called jboss-gwt-webapp.war.dodeploy > 15:27:18,713 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "jboss-gwt-webapp.war" > 15:27:20,830 INFO [org.jboss.as.jpa] (MSC service thread 1-3) JBAS011401: Read persistence.xml for primary > 15:27:20,978 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.jboss-gwt-webapp.war" is using a private module ("org.jboss.as.naming:main") which may be changed or removed in future versions without notice. > 15:27:20,979 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.jboss-gwt-webapp.war" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice. > 15:27:21,021 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002: Processing weld deployment jboss-gwt-webapp.war > 15:27:21,301 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016005: Starting Services for CDI deployment: jboss-gwt-webapp.war > 15:27:21,332 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900 1.1.5 (AS71) > 15:27:21,364 INFO [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011402: Starting Persistence Unit Service 'jboss-gwt-webapp.war#primary' > 15:27:21,461 INFO [org.hibernate.annotations.common.Version] (MSC service thread 1-1) HCANN000001: Hibernate Commons Annotations {4.0.1.Final} > 15:27:21,467 INFO [org.hibernate.Version] (MSC service thread 1-1) HHH000412: Hibernate Core {4.0.1.Final} > 15:27:21,469 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-1) HHH000206: hibernate.properties not found > 15:27:21,473 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-1) HHH000021: Bytecode provider name : javassist > 15:27:21,490 INFO [org.hibernate.ejb.Ejb3Configuration] (MSC service thread 1-1) HHH000204: Processing PersistenceUnitInfo [ > name: primary > ...] > 15:27:21,499 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.persistenceunit."jboss-gwt-webapp.war#primary": org.jboss.msc.service.StartException in service jboss.persistenceunit."jboss-gwt-webapp.war#primary": Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_07] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_07] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_07] > Caused by: java.lang.RuntimeException: error trying to scan <jar-file>: vfs:/Users/rasp/jbossqa/runtimes/jboss-as-7.1.1.Final/standalone/deployments/jboss-gwt-webapp.war/WEB-INF/classes/ > at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:854) > at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:596) > at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:72) > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:162) > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.start(PersistenceUnitServiceImpl.java:85) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > ... 3 more > Caused by: java.lang.RuntimeException: JBAS011431: Could not load entity class 'org.jboss.errai.marshalling.server.impl.ServerMarshallingFactoryImpl$30' with PersistenceUnitInfo.getClassLoader() > at org.jboss.as.jpa.hibernate4.HibernateAnnotationScanner.getPackagesInJar(HibernateAnnotationScanner.java:175) > at org.hibernate.ejb.Ejb3Configuration.addScannedEntries(Ejb3Configuration.java:489) > at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:851) > ... 9 more > Caused by: java.lang.ClassNotFoundException: org.jboss.errai.marshalling.server.impl.ServerMarshallingFactoryImpl$30 from [Module "deployment.jboss-gwt-webapp.war:main" from Service Module Loader] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) > at org.jboss.as.jpa.hibernate4.HibernateAnnotationScanner.getPackagesInJar(HibernateAnnotationScanner.java:171) > ... 11 more > 15:27:21,714 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "jboss-gwt-webapp.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.persistenceunit.\"jboss-gwt-webapp.war#primary\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"jboss-gwt-webapp.war#primary\": Failed to start service"}} > 15:27:21,742 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment jboss-gwt-webapp.war in 27ms > 15:27:21,743 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report > JBAS014777: Services which failed to start: service jboss.persistenceunit."jboss-gwt-webapp.war#primary": org.jboss.msc.service.StartException in service jboss.persistenceunit."jboss-gwt-webapp.war#primary": Failed to start service > 15:27:21,745 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.persistenceunit.\"jboss-gwt-webapp.war#primary\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"jboss-gwt-webapp.war#primary\": Failed to start service"}}}} > {code} -- 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-13415) Report a better error when using wrong project type to create WS Client

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13415?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick resolved JBIDE-13415. --------------------------------------- Resolution: Duplicate Issue Duplicated by JBIDE-14358 > Report a better error when using wrong project type to create WS Client > ----------------------------------------------------------------------- > > Key: JBIDE-13415 > URL: https://issues.jboss.org/browse/JBIDE-13415 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Webservices > Affects Versions: 4.0.0.Final > Reporter: Mustafa Musaji > Assignee: Brian Fitzpatrick > Fix For: 4.1.0.Beta1 > > Attachments: Screenshot_error.png > > > If you try and use a standard Java Project to create WS Client from a WSDL, you get a NPE thrown. But an error stating that the project type expected is a Dynamic Web Project would be much more appropriate. > !Screenshot_error.png|thumbnail! -- 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-13415) Report a better error when using wrong project type to create WS Client

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13415?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-13415: ------------------------------------------- This actually has nothing to do with the project type. The problem was with how we were getting the default runtime from the preferences. That has been fixed with the pull request for JBIDE-14339 & JBIDE-14358. Same issue, just hit from a slightly different direction. > Report a better error when using wrong project type to create WS Client > ----------------------------------------------------------------------- > > Key: JBIDE-13415 > URL: https://issues.jboss.org/browse/JBIDE-13415 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Webservices > Affects Versions: 4.0.0.Final > Reporter: Mustafa Musaji > Assignee: Brian Fitzpatrick > Fix For: 4.1.0.Beta1 > > Attachments: Screenshot_error.png > > > If you try and use a standard Java Project to create WS Client from a WSDL, you get a NPE thrown. But an error stating that the project type expected is a Dynamic Web Project would be much more appropriate. > !Screenshot_error.png|thumbnail! -- 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-13414) No Error reported when WS Client code generation fails

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13414?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-13414: ------------------------------------------- That's interesting. With the most recent code on Kepler, I'm seeing an exception pop up in a dialog: {code} Error: Could not import. (use --verbose to see full traces) java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.RangeCheck(ArrayList.java:547) at java.util.ArrayList.get(ArrayList.java:322) at org.apache.cxf.tools.common.ToolException.printStackTrace(ToolException.java:120) at org.apache.cxf.tools.common.ToolException.printThrowable(ToolException.java:126) at org.apache.cxf.tools.common.ToolException.printStackTrace(ToolException.java:121) at org.apache.cxf.tools.common.ToolException.printStackTrace(ToolException.java:104) at org.jboss.wsf.stack.cxf.tools.CXFConsumerImpl.consume(CXFConsumerImpl.java:291) at org.jboss.ws.tools.cmd.WSConsume.importServices(WSConsume.java:279) at org.jboss.ws.tools.cmd.WSConsume.mainInternal(WSConsume.java:104) at org.jboss.ws.tools.cmd.WSConsume.main(WSConsume.java:92) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.modules.Module.run(Module.java:262) at org.jboss.modules.Main.main(Main.java:329) {code} > No Error reported when WS Client code generation fails > ------------------------------------------------------ > > Key: JBIDE-13414 > URL: https://issues.jboss.org/browse/JBIDE-13414 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Reporter: Mustafa Musaji > Assignee: Brian Fitzpatrick > Labels: web_service_client > Fix For: 4.1.0.Beta1 > > Attachments: echoService.wsdl > > > If you have a WSDL which would normally fail because of JAXB collision. From command line you would get an error like this: > Failed to invoke WSDLToJava > org.apache.cxf.tools.common.ToolException: Thrown by JAXB: > Thrown by JAXB: > Two declarations cause a collision in the ObjectFactory class. > ... > However, in JBDS you don't get any error. It just doesn't create any sources and there is no indication of what the issue is. -- 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-13414) No Error reported when WS Client code generation fails

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13414?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick updated JBIDE-13414: -------------------------------------- Fix Version/s: 4.1.0.Beta1 > No Error reported when WS Client code generation fails > ------------------------------------------------------ > > Key: JBIDE-13414 > URL: https://issues.jboss.org/browse/JBIDE-13414 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Reporter: Mustafa Musaji > Assignee: Brian Fitzpatrick > Labels: web_service_client > Fix For: 4.1.0.Beta1 > > Attachments: echoService.wsdl > > > If you have a WSDL which would normally fail because of JAXB collision. From command line you would get an error like this: > Failed to invoke WSDLToJava > org.apache.cxf.tools.common.ToolException: Thrown by JAXB: > Thrown by JAXB: > Two declarations cause a collision in the ObjectFactory class. > ... > However, in JBDS you don't get any error. It just doesn't create any sources and there is no indication of what the issue is. -- 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 April 2013