January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2856) Encrypted passwords in the change-set.xml

by Alessandro Lazarotti (JIRA)

Encrypted passwords in the change-set.xml ----------------------------------------- Key: JBRULES-2856 URL: https://issues.jboss.org/browse/JBRULES-2856 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 5.1.1.FINAL Environment: fedora 12, jdk 1.6, drools 5.1.0 expert Reporter: Alessandro Lazarotti Assignee: Mark Proctor Currently the drools client API access Guvnor by creditials declared as plain-text in change-set.xml or property files. This is a security problem for many companies. Is very important develop a mechanism to obfuscate the password -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
7
0 / 0

[JBoss JIRA] (AS7-3431) Add "ShutdownInProgress" event to the ServiceContainer.TerminateListener

by Ramesh Reddy (JIRA)

Ramesh Reddy created AS7-3431: --------------------------------- Summary: Add "ShutdownInProgress" event to the ServiceContainer.TerminateListener Key: AS7-3431 URL: https://issues.jboss.org/browse/AS7-3431 Project: Application Server 7 Issue Type: Enhancement Components: Server Reporter: Ramesh Reddy Assignee: Jason Greene Currently the ServiceContainer.TerminateListener only notifies the listener after all the services are down notifying that Server is completely shutdown, However, it would be beneficial for services that are listening to event to get notified when the server is starting the shutdown cycle and after it completes. usecase: in Teiid we differentiate between a undeploy event because of the undeploy, undeploy due to the shutdown to clean up cache entries, currently I see no way differentiate between two. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JASSIST-144) ProxyObject#setHandler interferes with business methods of the same name

by Steve Ebersole (JIRA)

ProxyObject#setHandler interferes with business methods of the same name ------------------------------------------------------------------------ Key: JASSIST-144 URL: https://issues.jboss.org/browse/JASSIST-144 Project: Javassist Issue Type: Feature Request Affects Versions: 3.12.0.GA Reporter: Steve Ebersole Assignee: Shigeru Chiba Being reported by Hibernate/JPA users -> https://hibernate.onjira.com/browse/HHH-5731 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
13
0 / 0

[JBoss JIRA] Created: (AS7-830) using JMSQueueService to create and bind queues to new contexts with previously-non-existant-parents causes MockContext/BindingTrap/HornetQ to get confused on context heritage

by Bob McWhirter (JIRA)

using JMSQueueService to create and bind queues to new contexts with previously-non-existant-parents causes MockContext/BindingTrap/HornetQ to get confused on context heritage ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: AS7-830 URL: https://issues.jboss.org/browse/AS7-830 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.0.0.Beta3 Reporter: Bob McWhirter Assignee: Jason Greene If I hijack JMSQueueService, and attempt to bind the queue as queue/foo/bar/baz/tacos/someQueue, it may work the first time, but subsequent created queues end up with a duplicated section in the resulting path. Trying to bind to queue/foo/bar/baz/gouda/anotherQueue might result in queue/foo/bar/baz/tacos/gouda/anotherQueue. Seems some stack doesn't get completely popped when HornetQ goes creating parent contexts in order to plant the leaf resource. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

5
6
0 / 0

[JBoss JIRA] Created: (HIBERNATE-100) All versions of hibernate-tools packages are broken on eclipse-3.4

by solid Iduncare (JIRA)

All versions of hibernate-tools packages are broken on eclipse-3.4 ------------------------------------------------------------------ Key: HIBERNATE-100 URL: http://jira.jboss.com/jira/browse/HIBERNATE-100 Project: Hibernate Issue Type: Bug Environment: Reproducable on Linux, Windows and Mac OSX Reporter: solid Iduncare Assigned To: Steve Ebersole All versions of the Jboss hibernate-tools eclipse plugin fail in various ways on eclipse-3.4 (Ganymede). I have obtained various versions of the plugin via the eclipse update sites (both stable and dev) and all have various problems. I first attempted to download the latest from the stable update link (http://download.jboss.org/jbosstools/updates/stable/) . I selected the hibernate tools package for install only. It installs but is unusable. It seems to have no ill effects otherwise. When you attempt to add a hibernate configuration in the hibernate console, you get an exception similar to the followng: java.lang.NoClassDefFoundError: org/eclipse/ui/internal/util/SWTResourceUtil at org.hibernate.eclipse.console.workbench.xpl.AnyAdaptableLabelProvider.getImage(AnyAdaptableLabelProvider.java:166) at org.eclipse.jface.viewers.WrappedViewerLabelProvider.getImage(WrappedViewerLabelProvider.java:117) at org.eclipse.jface.viewers.WrappedViewerLabelProvider.update(WrappedViewerLabelProvider.java:165) at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:145) at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:932) at org.eclipse.jface.viewers.AbstractTreeViewer$UpdateItemSafeRunnable.run(AbstractTreeViewer.java:102) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:880) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:1012) at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:466) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:880) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:2041) at org.eclipse.jface.viewers.AbstractTreeViewer.createTreeItem(AbstractTreeViewer.java:827) at org.eclipse.jface.viewers.AbstractTreeViewer.createAddedElements(AbstractTreeViewer.java:340) at org.eclipse.jface.viewers.AbstractTreeViewer.internalAdd(AbstractTreeViewer.java:270) at org.eclipse.jface.viewers.TreeViewer.internalAdd(TreeViewer.java:652) at org.hibernate.eclipse.console.viewers.xpl.MTreeViewer.add(MTreeViewer.java:106) at org.eclipse.ui.progress.DeferredTreeContentManager$3.runInUIThread(DeferredTreeContentManager.java:353) at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:94) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:133) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3800) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) I googled this error and it brought me to a hibernate jira page hosted by atlasian. That Jira page recommended using the latest hibernate tools plugin from the dev update site(http://download.jboss.org/jbosside/hibernatetools/updates/development/) so I did. Now this is where all hell brakes loose. After installing the latest version from this site and restarting eclipse, the JEE perspective is completely disabled. JSP files open in a regular text editor and all attempts to update eclipse fail with this exception: Cannot complete the request. See the details. Cannot find a solution where both Match[requiredCompatibility: org.eclipse.equinox.p2.iu/org.eclipse.emf.ecore.xml/[2.1.0,2.1.0]] and Match[requiredCompatability: .... In short there is no usable version of hibernate tools for eclipse-3.4. -- 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

13 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (AS7-947) server:reload() exception

by Heiko Braun (JIRA)

server:reload() exception ------------------------- Key: AS7-947 URL: https://issues.jboss.org/browse/AS7-947 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry Priority: Critical Fix For: 7.0.0.CR1 Reloading yields an exception: /host=local/server=server-one:reload {noformat} [Host Controller] 12:32:50,188 ERROR [org.jboss.as.host.controller] (pool-1-thread-24) Could not start server Server:server-one: java.lang.IllegalArgumentException: A node is already registered at '(server => server-one)' [Host Controller] at org.jboss.as.controller.registry.NodeSubregistry.registerProxyController(NodeSubregistry.java:89) [jboss-as-controller-7.0.0.Beta4-SNAPSHOT.jar:7.0.0.Beta4-SNAPSHOT] {noformat} A second operation request results in "broken pipe": {noformat} [Host Controller] 12:33:03,025 ERROR [org.jboss.as.protocol] (ModelControllerClient-thread - 1) Failed to close resource org.jboss.as.protocol.SimpleByteDataOutput@37c398e: java.net.SocketException: Broken pipe {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

8
10
0 / 0

[JBoss JIRA] Created: (JBRULES-2699) OSGi support for Drools Planner

by Geoffrey De Smet (JIRA)

OSGi support for Drools Planner ------------------------------- Key: JBRULES-2699 URL: https://jira.jboss.org/browse/JBRULES-2699 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-planner Affects Versions: 5.1.1.FINAL Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Priority: Optional Fix For: FUTURE Asked on twitter by Wouter Horré. If there's more demand, I'll look into supporting in our builds, until then they'll have to manage it themselves :/ Patches welcome too of course. -- 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

13 years, 11 months

1
1
0 / 0

[JBoss JIRA] (AS7-2984) Add wait attribute to rehashing element of distributed caches

by Tristan Tarrant (Created) (JIRA)

Add wait attribute to rehashing element of distributed caches ------------------------------------------------------------- Key: AS7-2984 URL: https://issues.jboss.org/browse/AS7-2984 Project: Application Server 7 Issue Type: Enhancement Components: Clustering Affects Versions: 7.1.0.Beta1b Reporter: Tristan Tarrant Assignee: Tristan Tarrant Priority: Minor Fix For: 7.1.0.CR1 Infinispan 5.1.0 has introduced the wait attribute for rehashing. Make sure the Infinispan subsystem supports it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
26
0 / 0

[JBoss JIRA] (JBRULES-3302) Unwanted type coersion of String to float values when using "in" keyword LHS

by Troy Parrish (Created) (JIRA)

Unwanted type coersion of String to float values when using "in" keyword LHS ---------------------------------------------------------------------------- Key: JBRULES-3302 URL: https://issues.jboss.org/browse/JBRULES-3302 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler (expert) Affects Versions: 5.3.0.Final, 5.2.0.Final Environment: Windows 7, Rational Application Developer 7.5, Eclipse Helios Service Release 2 Reporter: Troy Parrish Assignee: Mark Proctor String values get treated as float values even when fact declares the property as a String when using the "in" keyword to evaluate a String value against a set of values in the lhs of the rule. Example: input into session : "10.5" will match against all of the following values "10.5", "10.50", "10.500" etc when in this format: when Fact(string in ("11.5", "10.50", "11.500")) then This problem behavior occurs in 5.3.0Final, 5.2.0.Final but not in 5.1.0Final, this is when Expert went from using mvel 2.0.16 to mvel 2.1.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

6
19
0 / 0

[JBoss JIRA] (AS7-2667) Applications cannot use Hibernate hibernate.session_factory_name

by Scott Marlow (Created) (JIRA)

Applications cannot use Hibernate hibernate.session_factory_name ---------------------------------------------------------------- Key: AS7-2667 URL: https://issues.jboss.org/browse/AS7-2667 Project: Application Server 7 Issue Type: Sub-task Components: Naming Affects Versions: 7.1.0.Alpha1, 7.0.1.Final, 7.0.0.Beta2 Reporter: Scott Marlow Assignee: John Bailey Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

8
11
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2012