Community
Participate
Working Groups
If I choose to create both query and registration service, and set the package name to a.b.c, only the query service class is created under the package name I supplied. The registration service class is created under com.myCompany.
Thanks for catching, Hubert. It's nice to have other people using the toolkit, so it can be correct and usable. I'll fix this, and introduce a case in the JUnit to handle this situation. I think my JUnit only checks the package is respected for the query service case currently.
The problem was that we had setup the wizard page for the query service facet only. If you enable the wizard page for the registration service facet as well, you end up with 2 copies of the same page. If you don't, then the config contains default values. The workaround for this that I came up with was to store a .metadata file in the generated project containing the MDR name and package name. This file gets created when the query service facet is installed. When the registration service facet is later installed, the file is read, and the config is updated to match the values for the query service facet. This ensures there is only one wizard page, and the two services are installed in the same package and share the same prefix. Hubert, please confirm after the next build that the fix works well for you.
closing to cleanup bugzilla
