Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » OSEE » Demodata Initialization Problem Must be one current state. Found 0 for DBJ3X
Demodata Initialization Problem Must be one current state. Found 0 for DBJ3X [message #16120] Mon, 29 June 2009 04:46 Go to next message
Andreas Graf is currently offline Andreas Graf
Messages: 151
Registered: July 2009
Senior Member
Hi group,

when running the Demo Data Action from the John Hopkins example I get the
attached error. My system is still populated at least with some
requirements. Does anybody have an idea about what's wrong?

Thx,

Andreas

Must be one current state. Found 0 for DBJ3X
Must be one current state. Found 0 for DBJ3X

org.eclipse.osee.ats.util.widgets.XCurrentStateDam.getState( XCurrentStateDam.java:37)

org.eclipse.osee.ats.util.StateManager.getCurrentStateName(S tateManager.java:116)
org.eclipse.osee.ats.editor.SMAManager.isCompleted(SMAManage r.java:703)

org.eclipse.osee.ats.editor.SMAManager.isCancelledOrComplete d(SMAManager.java:711)

org.eclipse.osee.ats.artifact.StateMachineArtifact.getPercen tCompleteSMATotal(StateMachineArtifact.java:1168)

org.eclipse.osee.ats.util.widgets.XCurrentStateDam.logMetric s(XCurrentStateDam.java:63)

org.eclipse.osee.ats.util.widgets.XCurrentStateDam.updateMet rics(XCurrentStateDam.java:51)

org.eclipse.osee.ats.util.StateManager.updateMetrics(StateMa nager.java:137)

org.eclipse.osee.ats.util.StateManager.updateMetrics(StateMa nager.java:132)

org.eclipse.osee.ats.artifact.TeamWorkflowManager.setEndorse Data(TeamWorkflowManager.java:110)

org.eclipse.osee.ats.artifact.TeamWorkflowManager.transition To(TeamWorkflowManager.java:49)

org.eclipse.osee.ats.config.demo.config.PopulateDemoActions. createActions(PopulateDemoActions.java:406)

org.eclipse.osee.ats.config.demo.config.PopulateDemoActions. run(PopulateDemoActions.java:123)

org.eclipse.osee.ats.config.demo.config.PopulateDemoActions. run(PopulateDemoActions.java:92)

org.eclipse.osee.framework.ui.skynet.widgets.xnavigate.XNavi gateComposite.handleDoubleClick(XNavigateComposite.java:214)

org.eclipse.osee.ats.navigate.AtsNavigateComposite.handleDou bleClick(AtsNavigateComposite.java:92)

org.eclipse.osee.ats.navigate.AtsNavigateComposite.handleDou bleClick(AtsNavigateComposite.java:60)

org.eclipse.osee.framework.ui.skynet.widgets.xnavigate.XNavi gateComposite$3.handleEvent(XNavigateComposite.java:100)
org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :84)
org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3823)
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3422)
org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2382)
org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
org.eclipse.ui.internal.Workbench.access$4(Workbench.java:21 98)
org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)

org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:288)

org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:488)
org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)

org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.java:113)

org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)

org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)

org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)

org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:386)

org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:597)
org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549)
org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
org.eclipse.equinox.launcher.Main.run(Main.java:1236)
Re: Demodata Initialization Problem Must be one current state. Found 0 for DBJ3 [message #17022 is a reply to message #16120] Fri, 24 July 2009 15:50 Go to previous messageGo to next message
Nirmal Sasidharan
Messages: 120
Registered: July 2009
Location: Germany
Senior Member
Hello Andreas,

This is a bug in OSEE. OSEE doesn't seem to handle locale correctly. The
bug happens with German Locale settings in your OS. You could get over
this bug by passing "-nl en" argument to eclipse when you start the OSEE
client (if you are using oseeLocal.exe, add the argument to
oseeLocal.ini).

This bug causes OSEE to crash not only during Demo data population but at
many other places too.

OSEE is storing the Workflow Action States in the following format in the
database and tokening it later I guess.

<Action State>;<<Responsible Name>>;<Time taken>;<Percent complete>
For example, Authorize;<Joe Smith>;10.00;30

On the German Locale the third token 10.00 gets written as 10,00 and I
guess the tokeniser is broken here.

Also repeat a database intialisation, so that any corrupt values are
removed.

Somwehere OSEE is giving me a scare with such bugs!

See you in office on Monday ;)

Nirmal
Re: Demodata Initialization Problem Must be one current state. Found 0 for DBJ3 [message #17051 is a reply to message #17022] Mon, 27 July 2009 07:54 Go to previous messageGo to next message
Mark D-B is currently offline Mark D-B
Messages: 188
Registered: July 2009
Senior Member
The comma versus stop for decimal point problem is very common in software
that was originally written for a user base outside continental Europe. In
fairness to OSEE's developers, it is only as users in this area start
using the tool (with a geographic locale set, given that many users do not
use the full locale in order to avoid problems with other tools), that
such issues will manifest. OSEE is far from unique in not having tested
for this.
It will be interesting to see, when one of you has submitted this to OSEE
Bugzilla, whether the fault is in OSEE itself or another Eclipse component.
Re: Demodata Initialization Problem Must be one current state. Found 0 for DBJ3 [message #17080 is a reply to message #17051] Mon, 27 July 2009 10:33 Go to previous messageGo to next message
Nirmal Sasidharan
Messages: 120
Registered: July 2009
Location: Germany
Senior Member
Hi Mark,

Just did that today morning
https://bugs.eclipse.org/bugs/show_bug.cgi?id=284725.

Maybe I was a bit cruel to OSEE committers here,all though I didnt mean it
that way. I do appreciate the good work they are doing. Perhaps, I am a
bit bugged that I cant use OSEE on my Mac and have to fall back to a
Windows virtual machine.

Nirmal
Re: Demodata Initialization Problem Must be one current state. Found 0 for DBJ3 [message #479328 is a reply to message #17080] Mon, 10 August 2009 13:13 Go to previous message
Ryan Schmitt is currently offline Ryan Schmitt
Messages: 16
Registered: July 2009
Junior Member
This particular bug has been fixed (see bug 284725), although localization
has a long way to go.
Re: Demodata Initialization Problem Must be one current state. Found 0 for DBJ3 [message #574762 is a reply to message #16120] Fri, 24 July 2009 15:50 Go to previous message
Nirmal Sasidharan
Messages: 120
Registered: July 2009
Location: Germany
Senior Member
Hello Andreas,

This is a bug in OSEE. OSEE doesn't seem to handle locale correctly. The
bug happens with German Locale settings in your OS. You could get over
this bug by passing "-nl en" argument to eclipse when you start the OSEE
client (if you are using oseeLocal.exe, add the argument to
oseeLocal.ini).

This bug causes OSEE to crash not only during Demo data population but at
many other places too.

OSEE is storing the Workflow Action States in the following format in the
database and tokening it later I guess.

<Action State>;<<Responsible Name>>;<Time taken>;<Percent complete>
For example, Authorize;<Joe Smith>;10.00;30

On the German Locale the third token 10.00 gets written as 10,00 and I
guess the tokeniser is broken here.

Also repeat a database intialisation, so that any corrupt values are
removed.

Somwehere OSEE is giving me a scare with such bugs!

See you in office on Monday ;)

Nirmal
Re: Demodata Initialization Problem Must be one current state. Found 0 for DBJ3 [message #574788 is a reply to message #17022] Mon, 27 July 2009 07:54 Go to previous message
Mark D-B is currently offline Mark D-B
Messages: 188
Registered: July 2009
Senior Member
The comma versus stop for decimal point problem is very common in software
that was originally written for a user base outside continental Europe. In
fairness to OSEE's developers, it is only as users in this area start
using the tool (with a geographic locale set, given that many users do not
use the full locale in order to avoid problems with other tools), that
such issues will manifest. OSEE is far from unique in not having tested
for this.
It will be interesting to see, when one of you has submitted this to OSEE
Bugzilla, whether the fault is in OSEE itself or another Eclipse component.
Re: Demodata Initialization Problem Must be one current state. Found 0 for DBJ3 [message #574802 is a reply to message #17051] Mon, 27 July 2009 10:33 Go to previous message
Nirmal Sasidharan
Messages: 120
Registered: July 2009
Location: Germany
Senior Member
Hi Mark,

Just did that today morning
https://bugs.eclipse.org/bugs/show_bug.cgi?id=284725

Maybe I was a bit cruel to OSEE committers here,all though I didnt mean it
that way. I do appreciate the good work they are doing. Perhaps, I am a
bit bugged that I cant use OSEE on my Mac and have to fall back to a
Windows virtual machine.

Nirmal
Re: Demodata Initialization Problem Must be one current state. Found 0 for DBJ3 [message #574860 is a reply to message #17080] Mon, 10 August 2009 13:13 Go to previous message
Ryan Schmitt is currently offline Ryan Schmitt
Messages: 16
Registered: July 2009
Junior Member
This particular bug has been fixed (see bug 284725), although localization
has a long way to go.
Previous Topic:No effect when importing OseeClientProjectSet.psf
Next Topic:No effect when importing OseeClientProjectSet.psf
Goto Forum:
  


Current Time: Thu Aug 21 19:59:05 EDT 2014

Powered by FUDForum. Page generated in 0.04735 seconds