[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
|
Re: [ohf-dev] Plan for 2006
|
- From: Eishay Smith <eishays@xxxxxxxxxx>
- Date: Tue, 7 Mar 2006 22:35:56 -0800
- Delivered-to: ohf-dev@eclipse.org
ohf-dev-bounces@xxxxxxxxxxx wrote on 03/07/2006 05:15:39 PM:
> > Yes, I think its right. Let me say it in other words:
> > We are going to create OSGi/Servlet extensions that will make the XDS
> > client (I Include here the PIX too) plugins available using SOAP. The
same
> > plugins will be available both as regular Eclipse plugins, and using
the
> > OSGi/Server extensions as Web Services.
>
> hmm. So we're not yet at the point of me writing a plug-in the
> depends on the IBM XDS plug-in, and being able to deploy that
> plug-in on either client or server and expose it as a web
> service? or we are? I'm still not sure what this beast is yet.
We're not yet at the point of you using them, this will be our deliverable
this year.
The XDS plugins will use the HL7 OHF plugins being developed now ;), and
the code base of the components IBM used to pass the IHE connectathon this
year.
They will be deployable on both client and server side. On the client side
you will be able to use them like you use any other Eclipse plugin in an
RCP.
On the Server side we're working on a way to create OSGi environment and
deploy the OHF components. We must also create a way for none OSGi
components (EJBs, .Not, PHP etc) to use them outside the OSGi environment,
if we won't do it then what's the point in them being deployed on a
server... This will be done by a "server side plugin" that bridge between
the web container & SOAP parser, and the regular plugin extension.
Eishay