Cannot resolve space issue ...

Poster Content
nk4um User
Posts: 37
October 4, 2013 17:31

Obviously was a mistmatch between the meta/identity/uri and rootspace/uri ...

Sorry for bothering you with this ...

Anyway, I think the error messaging could be improved to notify about this kind of "missconfiguration".

Like · Post Reply
1 person likes this post
nk4um User
Posts: 37
October 4, 2013 14:32

Remaned the first module from

urn:com:neodonis:scheduler:services

in

urn:com:neodonis:scheduler.services

and the include uri from

urn:com:neodonis:scheduler:services

to

urn:com:neodonis:scheduler

and now the problem does not appear.

(Actually I found that the problem was caused by a commit that fixed the typo and incomplete import!).

I don't understand why this happens.

Can anyone help me about ?!

Thanks,

Radu

Like · Post Reply
nk4um User
Posts: 37
October 4, 2013 09:30Cannot resolve space issue ...

I had two modules - one normal:

urn:com:neodonis:scheduler:services

and other for tests

urn:com:neodonis:scheduler:testservices

The second imports the first one in its rootspace.

The problem is that the import statement

<rootspace>
  <import>
    <uri>urn:com:neodonis:scheduler:services&lt;/uri&gt;
  &lt;/import&gt; ....
&lt;/rootspace&gt;

it is ignored completely.

When I start the netkernel instance I saw a warning message:

W 12:15:10 Import        Import [urn:com:neodonis:scheduler:services] in [Tests for Neodonis Scheduler /rootspace] cannot be resolved

and also the testservices module becomes red and the import statement was red too and I clicked on it I receive:

Import [urn:com:neodonis:scheduler:services] in [Tests for Neodonis Scheduler /rootspace] cannot be resolved

I could play using Request Trace Tool with the first module (that cannot be resolved).

If someone encountered such an issue please advice what to do.

Kind regards,

Radu

Like · Post Reply