I assume the extension runs on Jetty. If not make sure it runs there first.

Hi Ralph,

I followed Lab 6.1 several times, with the same "could not load bundle result".

I did not test the plug in on Jetty because i was unable create the Project Area (Lab 2.4) it resulted in some initialization errors as far as i remember (did it some weeks ago).

Is there another way to test it, other then using Jetty; or another way to create the Project Area? We tried installing the RTC Development environment on another machine too, but again without Jetty...

You might be able to get it running without Jetty. Good luck with that. It will probably cost 10 times the effort compared to Jetty. And no one will be able to help.

The project area for the lab is based on a standard template. There is no reason why you should not be able to create it. I'd suggest to delete the temporary server folder (parallel to your workspace) and setup for Jetty (Lab 1) again. Then try to create the project again.

Hi Ralph,

It is not that i prefer running it without Jetty, i want to use Jetty, it just did not work :).
I tried it again and have the same problems when creating the Project area (step 2.4).
When deploying the process templates, I get the following error:
Problem(s) occurred deploying process definitions.
Could not locate storage service from https://localhost:7443/jazz/rootservices. Make sure that server property Public URI Root is correct.

I checked the public uri in https://localhost:7443/jazz/admin, and it is set to https://localhost:7443/jazz.

I also tried to ignore the process template deployment and create a new one, but it only got me to errors of the project area initialization:
Problem occurred initializing project area.
Could not locate storage service from https://localhost:7443/jazz/rootservices. Make sure that server property Public URI Root is correct.

Thank You very much for Your help!

Throw the current development server setup away and re-run the JUnit test to setup the test database in Lab 1.

I forgot to explicitly mention that I also deleted the temporary server folder and did the set up for Jetty again :)

What language setting does your machine have?

I have been always able to get the Jetty Server up and running. In the worst case, set up a new workspace in parallel to your current one and do a new setup of the SDK. Make sure to follow the steps and add -Duser.language=en to your server startup and the Eclipse ini.

Make sure to have the workspace set to UTF 8.

I don't know what the problem is. I have set this up many, many times - too often really and I always got this working.

Also, do you work in a VMWare (port issues)? How much RAM do you have?

I have an English language machine, 8 GB RAM and not in a virtual machine.

I think the problem is that I am missing the xml files you mentioned. Which xml files do I have to copy over?

Hi Ralph,

Thank You! I managed now to use Jetty.
I am debugging my plugin and the issue that i have is a FileNotFound Exception.
I have a config.property file for this plugin.
The property file was found while testing with JUnit. Do property files need a different approach in plug-ins? I am sorry to disturb with these simple questions, but I am new to this plug-in development and just trying to get it to work.

I am using URL to get to the file:
    private final String FILE_NAME = "resources/config.properties";
    private final URL url = Thread.currentThread().getContextClassLoader().getResource(FILE_NAME);
(...)
input = new FileInputStream(url.getPath());
Properties props = new Properties();
props.load(input);

The error appears in the bold line.

Thank You!