Eclipse Community Forums: Remote Application Platform (RAP)

Help

Home

Home » Eclipse Projects » Remote Application Platform (RAP) » Fragments and RAP projects

Show: Today's Messages :: Show Polls :: Message Navigator

Fragments and RAP projects [message #498326]

Mon, 16 November 2009 13:46

Charlie Kelly

Messages: 276
Registered: July 2009

Senior Member

(This question does not apply only to RAP projects.)

I'm following the RAP examples using fragments.

I've used the PDE wizard to create a fragment project,
and listed its host project.

However, the host project generates compile errors (xxx cannot be
resolved to a type) when it references the classes from the fragment
project. Similar errors are reported for import statements.

Does the host project need to be modified to find classes from the
fragemnt? If yes, how?

If not, I will appreciate suggestions on how to solve the problem.

Thanks

Charlie

Report message to a moderator

Re: Fragments and RAP projects [message #498329 is a reply to message #498326]

Mon, 16 November 2009 13:58

Benjamin Muskalla

Messages: 338
Registered: July 2009

Senior Member

Hi,

the intention of a fragment is not to expand the classpath of the host
bundle. Means: you're not allowed to call from the host to the fragment,
only the other way around. Take a look at the single sourcing webinar or
the guide. There we explain how you can use fragments + a delegate
pattern to single source your applications.

Regards,
Ben

Charlie Kelly wrote:
> (This question does not apply only to RAP projects.)
>
> I'm following the RAP examples using fragments.
>
> I've used the PDE wizard to create a fragment project,
> and listed its host project.
>
> However, the host project generates compile errors (xxx cannot be
> resolved to a type) when it references the classes from the fragment
> project. Similar errors are reported for import statements.
>
> Does the host project need to be modified to find classes from the
> fragemnt? If yes, how?
>
> If not, I will appreciate suggestions on how to solve the problem.
>
> Thanks
>
> Charlie

--
Benjamin Muskalla | EclipseSource Karlsruhe
http://www.eclipsesource.com | http://twitter.com/eclipsesource

Report message to a moderator

Re: Fragments and RAP projects [message #498356 is a reply to message #498329]

Mon, 16 November 2009 15:08

Jochen Krause

Messages: 4
Registered: July 2009

Junior Member

There is a way to "extend" the API of the host bundle. It is not OSGi standard compliant and should only be used in special cases.

MANIFEST.MF parameter:
Eclipse-ExtensibleAPI: true

E.g. SWT (and RWT) are providing this capability.

The best practice is using an interface or abstract class in the host bundle as described in the RAP single sourcing webinar.

Jochen
http://eclipsesource.com/

Report message to a moderator

Re: Fragments and RAP projects [message #498375 is a reply to message #498356]

Mon, 16 November 2009 16:34

Benjamin Muskalla

Messages: 338
Registered: July 2009

Senior Member

Yes but this only allows you to extend the API from the host. But I
think Charlie is trying to "access" fragment classes from the host
bundle itself. This only works trough reflection as a host bundle
doesn't know anything about it's fragments (that's also the way we
describe in the webinar/single sourcing guide).

Regards,
Ben

Jochen Krause wrote:
> There is a way to "extend" the API of the host bundle. It is not OSGi
> standard compliant and should only be used in special cases.
>
> MANIFEST.MF parameter:
> Eclipse-ExtensibleAPI: true
>
> E.g. SWT (and RWT) are providing this capability.
>
> The best practice is using an interface or abstract class in the host
> bundle as described in the RAP single sourcing webinar.
>
> Jochen
> http://eclipsesource.com/

--
Benjamin Muskalla | EclipseSource Karlsruhe
http://www.eclipsesource.com | http://twitter.com/eclipsesource

Report message to a moderator