March 2009 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-3457) Generate hbm.xml file should generate default mapping for selected class(id, properties, etc)

by Dmitry Geraskov (JIRA)

Generate hbm.xml file should generate default mapping for selected class(id, properties, etc) --------------------------------------------------------------------------------------------- Key: JBIDE-3457 URL: https://jira.jboss.org/jira/browse/JBIDE-3457 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.0.0.cr1 Reporter: Dmitry Geraskov Assignee: Max Rydahl Andersen Now it generates only the following stub: <hibernate-mapping> <class name="MyBean"> </class> </hibernate-mapping> -- 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, 9 months

3
27
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, 9 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, 9 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, 9 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, 9 months

4
11
0 / 0

[JBoss JIRA] Created: (JBIDE-3562) Open-Ons for Seam 2.1

by Victor Rubezhny (JIRA)

Open-Ons for Seam 2.1 --------------------- Key: JBIDE-3562 URL: https://jira.jboss.org/jira/browse/JBIDE-3562 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jsp/jsf/xml source editing Reporter: Victor Rubezhny Assignee: Victor Rubezhny Fix For: 3.1.0 Review existing and add new Open-Ons for Seam 2.1 -- 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, 9 months

5
8
0 / 0

[JBoss JIRA] Created: (JBIDE-2899) Allow export of server definitions without resetting launch config

by Gabriele Garuglieri (JIRA)

Allow export of server definitions without resetting launch config ------------------------------------------------------------------ Key: JBIDE-2899 URL: https://jira.jboss.org/jira/browse/JBIDE-2899 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Affects Versions: 3.0.0.alpha Reporter: Gabriele Garuglieri Priority: Minor Currently we can export a JBoss Tools server definition using the default WTP server panel. There right clicking on the server opens a context menu whose last item is "Properties". Clicking it opens a panel where the "Switch Location" button cause the server definition to be exported from workspace metadata to "Servers" project. The problem is that doing so resets the launch configuration to the default values loosing any customization the user could have done. The "Switch Location" function for JBoss Tools server definition should not loose launch config customizations. (This is not strictly related but while you are at it, in the "Export Launch Configurations" panel the "JBoss Application Server Startup Configurations" items are missing the icons). -- 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, 9 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-3897) Creation of core module

by Rob Stryker (JIRA)

Creation of core module ----------------------- Key: JBIDE-3897 URL: https://jira.jboss.org/jira/browse/JBIDE-3897 Project: Tools (JBoss Tools) Issue Type: Task Components: core Affects Versions: 3.0.0.GA, 3.0.1.GA Reporter: Rob Stryker Assignee: Nick Boldt Fix For: 3.1.0 Time to recreate the core module. Tasks are as follows: 1) The module folder, with plugins / features / test category 2) an (empty) test plugin 3) an empty core plugin 4) an empty ui plugin 5) a feature 6) properly added into build 7) properly added to build download page 8) properly added to update site The purpose of this module will be to hold common well-designed multi-functional classes that will be usable by others. This will help reduce dependencies between modules by providing a common base. -- 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, 9 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-3837) Move classpath providers into some common area

by Rob Stryker (JIRA)

Move classpath providers into some common area ---------------------------------------------- Key: JBIDE-3837 URL: https://jira.jboss.org/jira/browse/JBIDE-3837 Project: Tools (JBoss Tools) Issue Type: Task Reporter: Rob Stryker Creation of common area is important. Whether it gets its own module or just its own plugin in as is debatable. This "core" must have zero dependencies on anything not wtp-related. The scope of this core (if located in the AS module) could also be a home for any and all overridden or borrowed WTP code that we find unsuitable in its current form, or any code that could have a common use but interfaces with WTP via extension points or subclassing. -- 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, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-4056) cooperation with mylyn?

by arne anka (JIRA)

cooperation with mylyn? ----------------------- Key: JBIDE-4056 URL: https://jira.jboss.org/jira/browse/JBIDE-4056 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 3.0.0.GA Reporter: arne anka Priority: Minor Attachments: jboss.png i work on two projects alternately, one is a jboss seam project (say, A), one is totally unrelated (say, B). both projects are, in eclipse terms, always open. i swotch between them by using mylyn and working sets. the last week i worked on B and frequently experienced rather heavy resource usage because jboss tools did some operations, which were unnecessary because nothing changed in in A. looking into the progress view there was an entry about building workspace, "invoking JProject ARchives Builder on A", "System: Jboss Tools Update" (see attached screenshot). i don't know, if there's a more intelligent way, but maybe jboss tools could try to detect if the project is part of the mylyn task currently active and if not, stop any activity? -- 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, 9 months

3
16
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 2009