IndexOutOfBoundsException with calculator-osgi example
------------------------------------------------------
Key: TUSCANY-3567
URL: https://issues.apache.org/jira/browse/TUSCANY-3567
Project: Tuscany
Issue Type: Bug
Components: Java SCA Samples
Affects Versions: Java-SCA-2.0-M4
Environment: Apache Felix as OSGi Environment (configured according
to: http://tuscany.apache.org/documentation-2x/running-tuscany-sca-2x-with-equin
ox-and-felix.html)
Reporter: Alexander Blotny
Fix For: Java-SCA-2.0-M5
The calculator-osgi example from the samples folder of the distribution started
in a stand-alone OSGi container (Felix) throws following exception:
-> start
file:/Users/alb/Development/Tuscany/tuscany-sca-2.0-M4/samples/calculator-osgi/target/sample-calculator-osgi.jar
21.05.2010 16:21:29 org.apache.tuscany.sca.node.impl.NodeImpl start
INFO: Starting node: http://tuscany.apache.org/sca/1.1/nodes/default7 domain:
tuscany.apache.org
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.RangeCheck(ArrayList.java:547)
at java.util.ArrayList.get(ArrayList.java:322)
at
org.apache.tuscany.sca.node.osgi.impl.OSGiNodeFactoryImpl.getNodeKey(OSGiNodeFactoryImpl.java:129)
at
org.apache.tuscany.sca.node.impl.NodeFactoryImpl.addNode(NodeFactoryImpl.java:113)
at org.apache.tuscany.sca.node.impl.NodeImpl.start(NodeImpl.java:115)
at calculator.CalculatorActivator.start(CalculatorActivator.java:41)
at
org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:661)
at org.apache.felix.framework.Felix.activateBundle(Felix.java:1756)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1678)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:905)
at
org.apache.felix.shell.impl.StartCommandImpl.execute(StartCommandImpl.java:114)
at
org.apache.felix.shell.impl.Activator$ShellServiceImpl.executeCommand(Activator.java:286)
at
org.apache.felix.shell.tui.Activator$ShellTuiRunnable.run(Activator.java:184)
at java.lang.Thread.run(Thread.java:637)
The testcases with maven and ant work correctly.
So it could be a problem with the way the bundle is started in the Bundle
Activator Class.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
