June 2009 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-4080) Internal error in Drools Plugin: is occured if empty rule.package is opened on ReteTree tab.

by Anton Klimkovich (JIRA)

Internal error in Drools Plugin: is occured if empty rule.package is opened on ReteTree tab. --------------------------------------------------------------------------------------------- Key: JBIDE-4080 URL: https://jira.jboss.org/jira/browse/JBIDE-4080 Project: Tools (JBoss Tools) Issue Type: Bug Components: drools Affects Versions: 3.0.0.GA Reporter: Anton Klimkovich Priority: Minor EXECUTE: Create new Guided Rule file EXECUTE: Open rule.package on ReteTree tab. FAILURE: java.lang.Exception: Unable to parse rules to show RETE view! at org.drools.eclipse.editors.rete.ReteViewer.loadReteModel(ReteViewer.java:161) at org.drools.eclipse.editors.DRLRuleEditor2$3.run(DRLRuleEditor2.java:244) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:1 java.lang.NullPointerException at org.drools.common.AbstractRuleBase.addPackages(AbstractRuleBase.java:451) at org.drools.reteoo.ReteooRuleBase.addPackage(ReteooRuleBase.java:481) at org.drools.eclipse.editors.rete.ReteViewer.getRuleBase(ReteViewer.java:129) at org.drools.eclipse.editors.rete.ReteViewer.loadReteModel(ReteViewer.java:159) at org.drools.eclipse.editors.DRLRuleEditor2$3.run(DRLRuleEditor2.java:244) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) -- 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
3
0 / 0

[JBoss JIRA] Created: (JBIDE-4120) On a mac during installation have you have to select the soa-p radio button in the installer wizard/process before selecting the browse button to find the SOA-P instance you wish to use.

by Jim Tyrrell (JIRA)

On a mac during installation have you have to select the soa-p radio button in the installer wizard/process before selecting the browse button to find the SOA-P instance you wish to use. ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Key: JBIDE-4120 URL: https://jira.jboss.org/jira/browse/JBIDE-4120 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Jim Tyrrell -- 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
4
0 / 0

[JBoss JIRA] Created: (JBDS-745) Cannot Cancel Validation

by Shaun Appleton (JIRA)

Cannot Cancel Validation ------------------------ Key: JBDS-745 URL: https://jira.jboss.org/jira/browse/JBDS-745 Project: Developer Studio Issue Type: Bug Affects Versions: 2.0.0.GA Environment: Red Hat CSB Reporter: Shaun Appleton Priority: Minor Customer reports that they cannot cancel validation. I verified this on my machine (using above env). Steps to reproduce this - a) Ensure Validation is on and you have a large enough project that will take at least a few seconds to validate. b) Select a project right click and select validate. c) A progress bar should appear with a red square on the right-hand side. d) If you select the red square to stop/cancel validation then validation carries on until finished. So you cannot stop it. -- 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: (JBDS-716) Why do EPP, SOA-P and EAP deploy applications in different ways.

by Jim Tyrrell (JIRA)

Why do EPP, SOA-P and EAP deploy applications in different ways. ---------------------------------------------------------------- Key: JBDS-716 URL: https://jira.jboss.org/jira/browse/JBDS-716 Project: Developer Studio Issue Type: Feature Request Reporter: Jim Tyrrell EPP this needs a better easier way to create a new project!!! When it is deployed it is not placed in the deploy directory as projects are in/with the SOA-P and EPP? Why is this the case? I am now in some inconsistent state and can not republish w/o restarting the server. All of the products need to use the exact same way of deploying a new application w/o exception. -- 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-4359) Error calling delegate ModuleFactory[org.jboss.tools.esb.project.core.moduleFactory] is occured when create JSF project after renaming ESB project

by Anton Klimkovich (JIRA)

Error calling delegate ModuleFactory[org.jboss.tools.esb.project.core.moduleFactory] is occured when create JSF project after renaming ESB project -------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-4359 URL: https://jira.jboss.org/jira/browse/JBIDE-4359 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb, JSF Affects Versions: 3.1.0.M1 Reporter: Anton Klimkovich Priority: Minor EXECUTE: Create ESB project EXECUTE: Rename ESB project EXECUTE: New -> JSF 1.2 KickStart project - > Press Finish button FAILURE: java.lang.NullPointerException at org.jboss.tools.esb.core.module.JBossESBModule.getModuleType(JBossESBModule.java:56) at org.eclipse.wst.server.core.internal.ModuleFactory.hasInvalidModules(ModuleFactory.java:169) at org.eclipse.wst.server.core.internal.ModuleFactory.getModules(ModuleFactory.java:132) at org.eclipse.wst.server.core.ServerUtil.getModules(ServerUtil.java:96) at org.jboss.tools.jst.web.server.RegistrationHelper.findModule(RegistrationHelper.java:190) at org.jboss.tools.jst.web.server.RegistrationHelper$RegisterServerJob.run(RegistrationHelper.java:226) 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: 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
5
0 / 0

[JBoss JIRA] Created: (JBIDE-4065) Add option to 'auto arrange' diagram in GPD Editor

by Joao Paulo Viragine (JIRA)

Add option to 'auto arrange' diagram in GPD Editor -------------------------------------------------- Key: JBIDE-4065 URL: https://jira.jboss.org/jira/browse/JBIDE-4065 Project: Tools (JBoss Tools) Issue Type: Feature Request Environment: JBDS 2.0.0.CR2 Reporter: Joao Paulo Viragine Priority: Minor -- 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
4
0 / 0

[JBoss JIRA] Created: (JBIDE-4388) The installable unit org.jboss.tools.jmx.ui.test.translated_host_properties is missing the filename property.

by Nick Boldt (JIRA)

The installable unit org.jboss.tools.jmx.ui.test.translated_host_properties is missing the filename property. ------------------------------------------------------------------------------------------------------------- Key: JBIDE-4388 URL: https://jira.jboss.org/jira/browse/JBIDE-4388 Project: Tools (JBoss Tools) Issue Type: Bug Components: jmx Affects Versions: 3.1.0.M1 Reporter: Nick Boldt Assignee: Rob Stryker I've been seeing a lot of these warnings in the build. I suspect users will see them in their console / error log too. Can they be suppressed? Where are these *.translated_host_properties files coming from, and why are they missing their filename properties? -------- [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-05-27 15:37:21.431 [java] !MESSAGE The installable unit org.jboss.tools.jmx.ui.test.translated_host_properties is missing the filename property. [java] [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-05-27 15:37:21.525 [java] !MESSAGE The installable unit org.eclipse.test.performance.win32.translated_host_properties is missing the filename property. [java] [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-05-27 15:37:21.995 [java] !MESSAGE The installable unit org.jboss.tools.jmx.ui.test.translated_host_properties is missing the filename property. [java] [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-05-27 15:37:21.997 [java] !MESSAGE The installable unit org.eclipse.test.performance.win32.translated_host_properties is missing the filename property. [java] [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-05-27 15:37:23.351 [java] !MESSAGE The installable unit org.jboss.tools.jmx.ui.test.translated_host_properties is missing the filename property. [java] [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-05-27 15:37:23.352 [java] !MESSAGE The installable unit org.eclipse.test.performance.win32.translated_host_properties is missing the filename property. [java] [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-05-27 15:37:23.387 [java] !MESSAGE The installable unit org.jboss.tools.jmx.ui.test.translated_host_properties is missing the filename property. [java] [java] !ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-05-27 15:37:23.388 [java] !MESSAGE The installable unit org.eclipse.test.performance.win32.translated_host_properties is missing the filename property. -- 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
3
0 / 0

[JBoss JIRA] Updated: (JBIDE-351) Clean out bad exception handling

by Denis Golovin (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-351?page=com.atlassian.jira.plug... ] Denis Golovin updated JBIDE-351: -------------------------------- Fix Version/s: 3.1.0.M3 (was: 3.1.0.M2) > Clean out bad exception handling > -------------------------------- > > Key: JBIDE-351 > URL: https://jira.jboss.org/jira/browse/JBIDE-351 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Cleanup > Affects Versions: 2.0.0.GA > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 3.1.0.M3 > > > weed out all ex.printStackTrace() by either > a) remove them (and their catch clause) > b) replace them with log to the error log > There is waay to many of them ;) -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-4393) Seam validator should complain about two components with the same name which are defined by @Name and <component/>

by Alexey Kazakov (JIRA)

Seam validator should complain about two components with the same name which are defined by @Name and <component/> ------------------------------------------------------------------------------------------------------------------ Key: JBIDE-4393 URL: https://jira.jboss.org/jira/browse/JBIDE-4393 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Seam Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.1.0.M2 EXECUTE: Create Seam Ear project EXECUTE: Add string <component class="org.domain.<seam-project-name>.session.Authenticator" name="authenticator"/> into components.xml ASSERT: There should be two error markes on components.xml and Authenticator.java - Two components with the same name and precedence. -- 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
7
0 / 0

[JBoss JIRA] Updated: (JBIDE-4287) javax.management.MBeanException is occured while hot publishing of pages.xml to the server.

by Max Rydahl Andersen (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-4287?page=com.atlassian.jira.plu... ] Max Rydahl Andersen updated JBIDE-4287: --------------------------------------- Fix Version/s: 3.1.0.M2 Assignee: Rob Stryker Assumed fixed since the stacktrace is indicating we are trying to register the deploymentscanner which does not exist in AS 5.0 (it was brought back for 5.1) Rob - fixed or current broken behavior? > javax.management.MBeanException is occured while hot publishing of pages.xml to the server. > ------------------------------------------------------------------------------------------- > > Key: JBIDE-4287 > URL: https://jira.jboss.org/jira/browse/JBIDE-4287 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS > Affects Versions: 3.1.0.M1 > Reporter: Anton Klimkovich > Assignee: Rob Stryker > Fix For: 3.1.0.M2 > > > EXECUTE: Create seam 21.1GA project > EXECUTE: Run on JBoss AS 5GA > ASSERT: Application should start successfully. > EXECUTE: Open pages.xml > EXECUTE: Add new page on Graphical tab > EXECUTE: Save file > FAILURE: javax.management.MBeanException is occured while hot publishing of pages.xml to the server. > javax.management.MBeanException > at org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:184) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:165) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) > at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) > at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) > at org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:216) > at sun.reflect.GeneratedMethodAccessor265.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:157) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) > at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) > at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140) > at org.jboss.jmx.connector.invoker.SerializableInterceptor.invoke(SerializableInterceptor.java:74) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) > at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180) > at sun.reflect.GeneratedMethodAccessor264.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:157) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) > 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:668) > at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855) > at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422) > at sun.reflect.GeneratedMethodAccessor263.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294) > at sun.rmi.transport.Transport$1.run(Transport.java:153) > at java.security.AccessController.doPrivileged(Native Method) > at sun.rmi.transport.Transport.serviceCall(Transport.java:149) > at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466) > at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707) > at java.lang.Thread.run(Thread.java:595) > Caused by: javax.management.InstanceNotFoundException: jboss.deployment:flavor=URL,type=DeploymentScanner is not registered. > at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:529) > at org.jboss.mx.server.registry.BasicMBeanRegistry.getValue(BasicMBeanRegistry.java:567) > 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:157) > ... 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/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 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 June 2009