October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Moved: (GPD-175) jBPM Process Designer fails with class cast exception

by Koen Aers (JIRA)

[ http://jira.jboss.com/jira/browse/GPD-175?page=all ] Koen Aers moved JBIDE-523 to GPD-175: ------------------------------------- Project: JBoss jBPM GPD (was: JBoss Tools) Key: GPD-175 (was: JBIDE-523) Component/s: jpdl (was: jbpm) Fix Version/s: jBPM jPDL Designer 3.1.0.SP1 (was: 2.0.0.CR1) > jBPM Process Designer fails with class cast exception > ----------------------------------------------------- > > Key: GPD-175 > URL: http://jira.jboss.com/jira/browse/GPD-175 > Project: JBoss jBPM GPD > Issue Type: Bug > Components: jpdl > Environment: Fedora Core 6 with Sun's Java 1.5.0_12 > Lenovo ThinkPad T60 > 2GB RAM > Reporter: Micah Modell > Assigned To: Koen Aers > Fix For: jBPM jPDL Designer 3.1.0.SP1 > > Attachments: processdefinition.xml > > > I get the following error when I attempt to open the attached file (from the demo station) in Eclipse from File->Open: > java.lang.ClassCastException: org.eclipse.ui.internal.editors.text.JavaFileEditorInput > at org.jbpm.ui.editor.DesignerEditor.init(Unknown Source) > at org.eclipse.ui.internal.EditorManager.createSite(EditorManager.java:842) > at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:583) > at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:372) > at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:566) > at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:290) > at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:140) > at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:268) > at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65) > at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:394) > at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1144) > at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1097) > at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1311) > at org.eclipse.ui.internal.PartStack.add(PartStack.java:455) > at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:102) > at org.eclipse.ui.internal.PartStack.add(PartStack.java:441) > at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:111) > at org.eclipse.ui.internal.EditorSashContainer.addEditor(EditorSashContainer.java:60) > at org.eclipse.ui.internal.EditorAreaHelper.addToLayout(EditorAreaHelper.java:217) > at org.eclipse.ui.internal.EditorAreaHelper.addEditor(EditorAreaHelper.java:207) > at org.eclipse.ui.internal.EditorManager.createEditorTab(EditorManager.java:822) > at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:721) > at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:682) > at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2593) > at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2528) > at org.eclipse.ui.internal.WorkbenchPage.access$10(WorkbenchPage.java:2520) > at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:2505) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67) > at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2500) > at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2477) > at org.eclipse.ui.internal.editors.text.OpenExternalFileAction.run(OpenExternalFileAction.java:132) > at org.eclipse.ui.internal.editors.text.OpenExternalFileAction.run(OpenExternalFileAction.java:100) > at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:254) > at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:229) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:539) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488) > at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1085) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3180) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2856) > at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1930) > at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1894) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:422) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95) > at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177) > 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.eclipse.core.launcher.Main.invokeFramework(Main.java:336) > at org.eclipse.core.launcher.Main.basicRun(Main.java:280) > at org.eclipse.core.launcher.Main.run(Main.java:977) > at org.eclipse.core.launcher.Main.main(Main.java:952) -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBAS-1627) Evaluate and implement missing JSR-88 functionality

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1627?page=all ] Max Andersen reopened JBAS-1627: -------------------------------- wrong bug ;) > Evaluate and implement missing JSR-88 functionality > --------------------------------------------------- > > Key: JBAS-1627 > URL: http://jira.jboss.com/jira/browse/JBAS-1627 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Deployment services > Affects Versions: JBossAS-4.0.1 Final > Environment: deployment module > Reporter: Dimitris Andreadis > Assigned To: Dimitris Andreadis > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-1627) Evaluate and implement missing JSR-88 functionality

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1627?page=all ] Max Andersen closed JBAS-1627. ------------------------------ Resolution: Rejected > Evaluate and implement missing JSR-88 functionality > --------------------------------------------------- > > Key: JBAS-1627 > URL: http://jira.jboss.com/jira/browse/JBAS-1627 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Deployment services > Affects Versions: JBossAS-4.0.1 Final > Environment: deployment module > Reporter: Dimitris Andreadis > Assigned To: Dimitris Andreadis > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-1121) Operator field and the fact's variable field required in the "then" part of the rule

by sreeni sabapathy (JIRA)

Operator field and the fact's variable field required in the "then" part of the rule ------------------------------------------------------------------------------------ Key: JBRULES-1121 URL: http://jira.jboss.com/jira/browse/JBRULES-1121 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-brms, Eclipse IDE Affects Versions: 4.0.0.GA Environment: drools-jbrms stand alone and Eclipse drools-4.0.0 Reporter: sreeni sabapathy Assigned To: Mark Proctor Priority: Minor Fix For: FUTURE In the drools-jbrms standalone and even in the eclipse plugin version of "New guided drl file" the "then" part of the rule has the limitation of assigning the fixed value to the fact's variable. But in many condition the the value of the variable depends upon the value of another variable. I have taken a simple example for explanation. For calcluating simple interest SI = P*T*R/100 Now in the rule file if the "when" condition as the check of " Calcluation type (simple ineterst or compound interest)" "then" part having SI, At the present drool-jbrms definition the "then" part has SI = text field. But my requirement is to look up the class variable "principle", "Time" and the "Rate" and then calculate, not just assign some fixed values. In a simple sentence I would appreciate if the drools- jbrms has the options related to "when" in the "then" part of the rule also. -- 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, 11 months

3
7
0 / 0

[JBoss JIRA] Created: (JBAS-4059) JBoss5 RARDeployer deploys RAR's twice

by Weston Price (JIRA)

JBoss5 RARDeployer deploys RAR's twice -------------------------------------- Key: JBAS-4059 URL: http://jira.jboss.com/jira/browse/JBAS-4059 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-5.0.0.Beta1 Reporter: Weston Price Assigned To: Weston Price Fix For: JBossAS-5.0.0.Beta2 Because of the new deployment structure in JBoss5, the RAR deployer is now deploying RAR's twice. I assume this has to do with the RARDeployer using a deprecated API of the DeploymentUnit. As a result, the JMX console records deployments such as: # name='jboss-ha-local-jdbc.rar#jboss-ha-local-jdbc.rar',service=RARDeployment # name='jboss-ha-local-jdbc.rar',service=RARDeployment This is causing issues with programmatic deployment, as well as the new metadata repository. -- 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, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-4720) Ensure security-domain is picked up by JCA Deployer

by Anil Saldhana (JIRA)

Ensure security-domain is picked up by JCA Deployer --------------------------------------------------- Key: JBAS-4720 URL: http://jira.jboss.com/jira/browse/JBAS-4720 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Anil Saldhana Assigned To: Weston Price Fix For: JBossAS-5.0.0.Beta3 Ensure that the security-domain settings are read into the metadata to be used by ConnectionManager. -- 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, 11 months

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1268) Activation.remove() is removing the WRONG activation

by Michael Neale (JIRA)

Activation.remove() is removing the WRONG activation ---------------------------------------------------- Key: JBRULES-1268 URL: http://jira.jboss.com/jira/browse/JBRULES-1268 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Reteoo Affects Versions: 4.0.2 Reporter: Michael Neale Assigned To: Mark Proctor Fix For: 4.1.0 Check out FIXME_testActivationCancellation in MiscTest.java. It shows how a call to activation.remove() for a given rule (in an event) actually removed the wrong rule. The reason for this is that fireNextItem in DefaultAgenda uses BinaryHeapQueueAgendaGroup.getNext(). This poorly named "getNext()" actually calls dequeue on the queue, so when the event is called, the activation has ALREADY been dequeued. Not sure of best solution, other then a queue "peek()" and then dequeue() to be called after then event is fired (if it wasn't called already). -- 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, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (JBRULES-1270) Tool friendly MVEL features for MVEl 2.0

by Philippe Ombredanne (JIRA)

Tool friendly MVEL features for MVEl 2.0 ---------------------------------------- Key: JBRULES-1270 URL: http://jira.jboss.com/jira/browse/JBRULES-1270 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Reporter: Philippe Ombredanne Assigned To: Mark Proctor Fix For: FUTURE Here are a couple request for MVEl 2.0: - keeping something like an ast (may be with a compile flag) that is close to the actual expression text - producing compiled expression even of there were some errors (ie keep on trucking) (optional flag for that too) - being able to extend the ast with completion information (ie attach completion stuffs directly as a decoration of node in the parse tree -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (SECURITY-83) Maven sub-module jbosssx in the project

by Anil Saldhana (JIRA)

Maven sub-module jbosssx in the project --------------------------------------- Key: SECURITY-83 URL: http://jira.jboss.com/jira/browse/SECURITY-83 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Repository Affects Versions: 2.0.1-BETA2 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.1-GA projects/security/security-jboss-sx/trunk needs to have two submodules jbosssx jbosssx-client -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAOP-478) ClassCastException on AnnotatedParameterAdviceInfo

by Flavia Rainone (JIRA)

ClassCastException on AnnotatedParameterAdviceInfo -------------------------------------------------- Key: JBAOP-478 URL: http://jira.jboss.com/jira/browse/JBAOP-478 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Flavia Rainone Assigned To: Flavia Rainone This is what happens when line 464 of AnnotatedAdviceInfo is executed with a method that returns a parameterized type: java.lang.ClassCastException: sun.reflect.generics.reflectiveObjects.ParameterizedTypeImpl at org.jboss.aop.advice.annotation.AnnotatedParameterAdviceInfo$SingleParameterType.internalValidate(AnnotatedParameterAdviceInfo.java:464) at org.jboss.aop.advice.annotation.AnnotatedParameterAdviceInfo$ParameterAnnotationType.validate(AnnotatedParameterAdviceInfo.java:374) at org.jboss.aop.advice.annotation.AnnotatedParameterAdviceInfo.matches(AnnotatedParameterAdviceInfo.java:124) at org.jboss.aop.advice.annotation.AdviceMethodFactory.bestValidAdvice(AdviceMethodFactory.java:412) at org.jboss.aop.advice.annotation.AdviceMethodFactory.findAdviceMethod(AdviceMethodFactory.java:291) at org.jboss.aop.instrument.JoinPointGenerator$AdviceSetups.<init>(JoinPointGenerator.java:1532) at org.jboss.aop.instrument.JoinPointGenerator.initialiseAdviceInfosAndAddFields(JoinPointGenerator.java:550) at org.jboss.aop.instrument.JoinPointGenerator.generateJoinpointClass(JoinPointGenerator.java:399) at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:276) at org.jboss.aop.instrument.JoinPointGenerator.access$100(JoinPointGenerator.java:75) at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$1$1.run(JoinPointGenerator.java:1630) at java.security.AccessController.doPrivileged(Native Method) at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$1.generateJoinPointClass(JoinPointGenerator.java:1626) at org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:244) at org.jboss.aop.GeneratedClassAdvisor.generateJoinPointClass(GeneratedClassAdvisor.java:1017) at org.jboss.test.aop.annotatedAdviceParams.ReturnInvalidPOJO$ReturnInvalidPOJOAdvisor.methodGenericsAfter54841465230530634828(ReturnInvalidPOJO$Retu rnInvalidPOJOAdvisor.java) This task includes a check on the code to see if the error is repeated in other code lines. -- 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, 11 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2007