|
|
|
| Re: importing packages [message #131671 is a reply to message #131652] |
Sun, 24 May 2009 11:00   |
 Dann Martens
Messages: 65
Registered: July 2009 |
Member |
|
|
Hi Andrea,
Your description is a bit cryptic, but I assume you're trying to explain
that you're having a problem with one particular OSGi bundle, that you
don't have any compile-time issues, but are experiencing run-time issues.
I would help if you could give some additional information:
- are you on 3.4 Ganymede, or any of the 3.5 Galileo milestones?
- are you trying to mix pure OSGi bundles with RCP plug-ins?
- can you create two example projects (bundles, or RCP plugins if that
applies) which reproduce the problem and offer them on-line somewhere?
The first thing I would check out is the state of your problem bundle,
at the OSGi console. Use 'ss' in the Console View, once your application
is run.
Best,
Dann
andrea wrote:
> Thx for your message.
>
>> In standard eclipse plugins, all of the .java files and resources
>> related to i18n are in the <proj>/src directory, and eclipse copies
>> the resources to the <proj>/bin directory when it compiles the .java
>> files.
>
> Yes, that's what occurs in my case too.
>
>> Are you saying you can't launch your app from within eclipse, or you
>> cannot deploy and run your bundle in an existing app?
>
> What I'm trying to say is that when I launch a plugin PLG in a OSGI way,
> PLG will work well, (for instance writing a sentence contained in start
> method) but the same PLG will not if I import a package pack.x.
> I want underline that only when pack.x is installed I can write code
> using pack.x's classes. This is the reason that make me suspect a kind
> of "splitted" behaviour: code works fine while launching plugin does not.
>
> Thx again
> Andrea
>
>
>
>
>
>> PW
>
>
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.03759 seconds
] 
Search
Help
Register
Login
Home
