July 2009 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-4549) HibernateConsoleMessages - Find Broken Externalized Strings (and clean them up)

by Sean Flanigan (JIRA)

HibernateConsoleMessages - Find Broken Externalized Strings (and clean them up) ------------------------------------------------------------------------------- Key: JBIDE-4549 URL: https://jira.jboss.org/jira/browse/JBIDE-4549 Project: Tools (JBoss Tools) Issue Type: Sub-task Reporter: Sean Flanigan -- 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

16 years, 3 months

2
7
0 / 0

[JBoss JIRA] Created: (JBIDE-4531) ClassNotFoundException "org.hibernate.eclipse.launch.SeamUtil" when generating entities

by Julien Kronegg (JIRA)

ClassNotFoundException "org.hibernate.eclipse.launch.SeamUtil" when generating entities --------------------------------------------------------------------------------------- Key: JBIDE-4531 URL: https://jira.jboss.org/jira/browse/JBIDE-4531 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.1.0.M2 Environment: JBossTools-ALL-win32-3.1.0.M2-N200906241801-H293.zip; Eclipse 3.5; Seam 2.1.2.GA Reporter: Julien Kronegg Priority: Critical When using Jboss Tools's "Generate Entities", a ClassCastException occurs and the entities cannot be generated when clicking on the "Finish" button (see screenshot). The exception message is: "org.hibernate.tool.hbm2x.ExporterException: Exception when instantiating tool hibernatetool.util.toolclass with org.hibernate.eclipse.launch.SeamUtil". The root cause seems that the org.hibernate.eclipse.launch.SeamUtil class could not be found (ClassNotFoundException). In JBossTools-ALL-win32-3.0.1.GA-R200905070146-H18.zip, there was a SeamUtil class in "eclipse\plugins\org.hibernate.eclipse_3.2.4.GA-R200905070146-H18\org.hibernate.eclipse.jar\org\hibernate\eclipse\launch\" In JBossTools-ALL-win32-3.1.0.M2-N200906241801-H293.zip, this is not the case anymore: the "launch" package is no more in "eclipse\plugins\org.hibernate.eclipse_3.3.0.M2-N200906241801-H293\org.hibernate.eclipse.jar\org\hibernate\eclipse\" Since there is a workaround, I set the severity to "Critical" rather than "Blocker". -- 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

16 years, 3 months

4
12
0 / 0

[JBoss JIRA] Created: (JBIDE-4146) "Persistence unit" in create/edit HibernateCC - should provide selection control to simple select from available PU

by Vitali Yemialyanchyk (JIRA)

"Persistence unit" in create/edit HibernateCC - should provide selection control to simple select from available PU ------------------------------------------------------------------------------------------------------------------- Key: JBIDE-4146 URL: https://jira.jboss.org/jira/browse/JBIDE-4146 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.0.0.GA Reporter: Vitali Yemialyanchyk Assignee: Vitali Yemialyanchyk Priority: Minor Fix For: 3.1.0 "Persistence unit" in create/edit HibernateCC is a simple text field - should be a more convenient way to edit this. -- 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

16 years, 3 months

3
14
0 / 0

[JBoss JIRA] Created: (JBIDE-4548) Cannot build two builds at the same time due to conflicts in using return.properties in shared requirements folder

by Denis Golovin (JIRA)

Cannot build two builds at the same time due to conflicts in using return.properties in shared requirements folder ------------------------------------------------------------------------------------------------------------------ Key: JBIDE-4548 URL: https://jira.jboss.org/jira/browse/JBIDE-4548 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.1.0.M2 Reporter: Denis Golovin Assignee: Denis Golovin Priority: Critical Fix For: 3.1.0.M3 -- 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

16 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBIDE-3222) Add support for <rich:state>, <rich:states> in VPE

by Yura Zhishko (JIRA)

Add support for <rich:state>, <rich:states> in VPE -------------------------------------------------- Key: JBIDE-3222 URL: https://jira.jboss.org/jira/browse/JBIDE-3222 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor Templates Affects Versions: 3.0.0.beta1 Reporter: Yura Zhishko Assignee: Maxim Areshkau -- 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

16 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-4557) Work of Filter in Properties Editor is incorrect.

by Anton Klimkovich (JIRA)

Work of Filter in Properties Editor is incorrect. ------------------------------------------------- Key: JBIDE-4557 URL: https://jira.jboss.org/jira/browse/JBIDE-4557 Project: Tools (JBoss Tools) Issue Type: Bug Components: XML Structured Editor Reporter: Anton Klimkovich Assignee: Alexey Kazakov Priority: Minor EXECUTE: Create JSF 1.2 KickStart project EXECUTE: Open Messages.prpoperties file in Properties Editor EXECUTE: Expand Filter and input "hello" in Value field ASSERT: Hello Demo Application and Hello values should be found FAILURE: Hello Demo Application and Hello values aren't found. Filter shouldn't be sensible for Upper case letters. The same for Name field. For example: Open "Open Resource" wizard (Ctrl + Shift + R) and input some values with Upper and Lower cases. The result will be equal in both variants. -- 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

16 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-2484) java.lang.NullPointerException when select Validate from context menu in Package Explorer

by Anton Klimkovich (JIRA)

java.lang.NullPointerException when select Validate from context menu in Package Explorer ----------------------------------------------------------------------------------------- Key: JBIDE-2484 URL: http://jira.jboss.com/jira/browse/JBIDE-2484 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.0.alpha Environment: WinXP 200807071935-nightly Reporter: Anton Klimkovich Assigned To: Alexey Kazakov EXECUTE: Create Seam War web project or JSF web project EXECUTE: Select Validate from context menu in Package Explorer for created project FAILURE: java.lang.NullPointerException at org.eclipse.jpt.core.internal.validation.JpaValidator.validationMessages(JpaValidator.java:55) at org.eclipse.jpt.core.internal.validation.JpaValidator.validate(JpaValidator.java:48) at org.eclipse.jpt.core.internal.validation.JpaValidator.validateInJob(JpaValidator.java:77) at org.eclipse.wst.validation.internal.core.ValidatorLauncher.start(ValidatorLauncher.java:78) at org.eclipse.wst.validation.Validator$V1.validate(Validator.java:689) at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:559) at org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:523) at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:662) at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:527) at org.eclipse.wst.validation.internal.ValidationRunner.execute(ValidationRunner.java:100) at org.eclipse.wst.validation.internal.ValidationRunner.validate(ValidationRunner.java:60) at org.eclipse.wst.validation.ui.internal.ManualValidationRunner.runInWorkspace(ManualValidationRunner.java:83) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) -- 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

16 years, 4 months

5
7
0 / 0

[JBoss JIRA] Created: (JBIDE-2512) Problem with referencing libaries

by Marcin M (JIRA)

Problem with referencing libaries ---------------------------------- Key: JBIDE-2512 URL: http://jira.jboss.com/jira/browse/JBIDE-2512 Project: Tools (JBoss Tools) Issue Type: Bug Components: libmanagement Affects Versions: 2.1.2 Environment: Ububtu Linux 8.04 Reporter: Marcin M Fix For: 2.1.3 <?xml version="1.0" encoding="UTF-8"?> <application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd" version="5"> <display-name>SymNet-ear</display-name> <module> <web> <web-uri>SymNet.war</web-uri> <context-root>/SymNet</context-root> </web> </module> <module> <ejb>SymNet-ejb.jar</ejb> </module> <module> <ejb>jboss-seam.jar</ejb> </module> </application> such application.xml will work after patching the eclipse installation by mentioned in the thread patch. but if you want to have your librarites to be put inside a folder (eg. lib) the problem remains <?xml version="1.0" encoding="UTF-8"?> <application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd" version="5"> <display-name>SymNet-ear</display-name> <module> <web> <web-uri>SymNet.war</web-uri> <context-root>/SymNet</context-root> </web> </module> <module> <ejb>lib/SymNet-ejb.jar</ejb> </module> <module> <ejb>jboss-seam.jar</ejb> </module> </application> 15:41:21,000 ERROR [MainDeployer] Could not initialise deployment: file:/D:/Java/jboss-4.2.2.GA/serv er/default/deploy/SymNet-ear.ear/ org.jboss.deployment.DeploymentException: url file:/D:/Java/jboss-4.2.2.GA/server/default/deploy/Sym Net-ear.ear/jboss-seam.jar could not be opened, does it exist? at org.jboss.deployment.DeploymentInfo.<init>(DeploymentInfo.java:214) at org.jboss.deployment.EARDeployer.init(EARDeployer.java:288) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:872) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:809) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.ja va:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentSc anner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.ja va:336) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) 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:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.ja va:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) at org.jboss.Main.boot(Main.java:200) at org.jboss.Main$1.run(Main.java:508) at java.lang.Thread.run(Thread.java:595) -- 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

16 years, 4 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-3374) Verify JBoss 5.0 support

by Rob Stryker (JIRA)

Verify JBoss 5.0 support ------------------------- Key: JBIDE-3374 URL: https://jira.jboss.org/jira/browse/JBIDE-3374 Project: Tools (JBoss Tools) Issue Type: Task Components: JBossAS Reporter: Rob Stryker Assignee: Rob Stryker Priority: Critical Fix For: 3.0.0.GA -- 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

16 years, 4 months

4
11
0 / 0

[JBoss JIRA] Created: (JBIDE-4421) jmx-invoker-service.xml server for DatabaseModuleLogin credentials not "accepted"

by Stelios Koussouris (JIRA)

jmx-invoker-service.xml server for DatabaseModuleLogin credentials not "accepted" --------------------------------------------------------------------------------- Key: JBIDE-4421 URL: https://jira.jboss.org/jira/browse/JBIDE-4421 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.0.0.GA Reporter: Stelios Koussouris Priority: Minor Setup the following authentication policy <application-policy name="CLSIS-Security"> <authentication> <login-module code="org.jboss.security.auth.spi.DatabaseServerLoginModule" flag = "required"> <module-option name="unauthenticatedIdentity">guest</module-option> <module-option name="dsJndiName">java:/DefaultDS</module-option>  <module-option name = "principalsQuery">SELECT PASSWD FROM JBM_USER WHERE USER_ID=?</module-option> <module-option name = "rolesQuery">SELECT ROLE_ID, 'Roles' FROM JBM_ROLE WHERE USER_ID=?</module-option> </login-module> </authentication> </application-policy> and for jmx-console.war set the jaas policy in jboss-web.xml <?xml version="1.0" encoding="UTF-8"?> <jboss-web> <resource-ref> <res-ref-name>jdbc/DefaultDS</res-ref-name> <res-type>javax.sql.DataSource</res-type> <jndi-name>java:/DefaultDS</jndi-name> </resource-ref> <security-domain>java:/jaas/CLSIS-Security</security-domain> </jboss-web> finally setting the web-app with role "john" and user/pass guest/guest OPTION A: left deploy/jmx-invoker-service.xml unchanged with default policy "jmx-console" Back in JBDS, Open Server View Right click on server --> Open In Overview set the Server Credentials to admin/admin Start the server and all is well OPTION B: left deploy/jmx-invoker-service.xml change the policy to "CLSIS-Security" Back in JBDS, Open Server View Right click on server --> Open In Overview set the Server Credentials to admin/admin Start the server pop-up comes up asking for the correct credentials enter guest/guest and all is well OPTION B1: all as in OPTION B but In Overview set the Server Credentials to guest/guest Start the server and expect that since the correct credentials for the DB policy held in deploy/jmx-invoker-service.xml are given no pop-up will appear BUT pop-up appears pre-populated with guest/guest I enter guest/guest and it keeps popping up (why?) if I choose "ignore" it does so server starts and JMX-CONSOLE is available via http://localhost:8080/jmx-console but JBDS is showing in Server View next to the server "Starting .... Synchnonized" then after 450 secs the JBDS throws an error popup and the server stops (why?) -- 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

16 years, 4 months

3
7
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2009