|
|
|
|
Re: Nested XWT [message #525876 is a reply to message #525838] |
Thu, 08 April 2010 07:23 |
Sebastian Messages: 61 Registered: March 2010 |
Member |
|
|
Hi Yves,
I will check this next week (have more time due to vacation
Thanks a lot for your efforts.
However, I'm kind of irritated. Since both java classes and XTWs are in the same package of the same bundle.
Could this be a class loader issue, still? Obviuosly, yes!
But anyhow, in my opinion it makes no sense to be forced to add an own class loader to make things work out right.
Or to say it another way around, to be able using nested XWTs it seems odd to me having to add a class loader, although both XWTs and classes remain in the same bundle and even in the same package/namespace.
In a java app I would expect the java interpreter to find these files, since they're within the same classpath, as an anaolgy.
Please don't hesitate to ask if I expressed myself unclearly
Regards
Sebastian
|
|
|
Re: Nested XWT [message #526007 is a reply to message #525876] |
Thu, 08 April 2010 14:17 |
Yves YANG Messages: 688 Registered: July 2009 |
Senior Member |
|
|
Hi Sebastian,
The loading operation occurs in XWT bundle.By default, the class loader
context is XWT bundle. Your class and resources are located in a different
bundle, which are not found.
Best regards
Yves YANG
"Sebastian" <laluz@gateway23.de> wrote in message
news:hpk09v$5g7$1@build.eclipse.org...
> Hi Yves,
>
> I will check this next week (have more time due to vacation :)
> Thanks a lot for your efforts.
>
> However, I'm kind of irritated. Since both java classes and XTWs are in
> the same package of the same bundle.
>
> Could this be a class loader issue, still? Obviuosly, yes!
> But anyhow, in my opinion it makes no sense to be forced to add an own
> class loader to make things work out right.
> Or to say it another way around, to be able using nested XWTs it seems odd
> to me having to add a class loader, although both XWTs and classes remain
> in the same bundle and even in the same package/namespace.
>
> In a java app I would expect the java interpreter to find these files,
> since they're within the same classpath, as an anaolgy.
>
> Please don't hesitate to ask if I expressed myself unclearly
> Regards
> Sebastian
|
|
|
|
|
|
Re: Nested XWT [message #573446 is a reply to message #525838] |
Thu, 08 April 2010 07:23 |
Sebastian Messages: 61 Registered: March 2010 |
Member |
|
|
Hi Yves,
I will check this next week (have more time due to vacation :)
Thanks a lot for your efforts.
However, I'm kind of irritated. Since both java classes and XTWs are in the same package of the same bundle.
Could this be a class loader issue, still? Obviuosly, yes!
But anyhow, in my opinion it makes no sense to be forced to add an own class loader to make things work out right.
Or to say it another way around, to be able using nested XWTs it seems odd to me having to add a class loader, although both XWTs and classes remain in the same bundle and even in the same package/namespace.
In a java app I would expect the java interpreter to find these files, since they're within the same classpath, as an anaolgy.
Please don't hesitate to ask if I expressed myself unclearly
Regards
Sebastian
|
|
|
Re: Nested XWT [message #573495 is a reply to message #573446] |
Thu, 08 April 2010 14:17 |
Yves YANG Messages: 688 Registered: July 2009 |
Senior Member |
|
|
Hi Sebastian,
The loading operation occurs in XWT bundle.By default, the class loader
context is XWT bundle. Your class and resources are located in a different
bundle, which are not found.
Best regards
Yves YANG
"Sebastian" <laluz@gateway23.de> wrote in message
news:hpk09v$5g7$1@build.eclipse.org...
> Hi Yves,
>
> I will check this next week (have more time due to vacation :)
> Thanks a lot for your efforts.
>
> However, I'm kind of irritated. Since both java classes and XTWs are in
> the same package of the same bundle.
>
> Could this be a class loader issue, still? Obviuosly, yes!
> But anyhow, in my opinion it makes no sense to be forced to add an own
> class loader to make things work out right.
> Or to say it another way around, to be able using nested XWTs it seems odd
> to me having to add a class loader, although both XWTs and classes remain
> in the same bundle and even in the same package/namespace.
>
> In a java app I would expect the java interpreter to find these files,
> since they're within the same classpath, as an anaolgy.
>
> Please don't hesitate to ask if I expressed myself unclearly
> Regards
> Sebastian
|
|
|
|
Powered by
FUDForum. Page generated in 0.04447 seconds