Re: [ohf-dev] OHF and Corona project

[Grahame Grieve <grahame@xxxxxxxxxxxxxx>]

Hi Eishay

a couple of questions. 

They want to expose OSGi plugins as web services, but if
their timelines don't suit, then we will continue with
the current OSGi/Server implementation. I'm confused - are
they setting themselves up in competition with the current
work, or are they going to extend it? I don't really 
understand that choice you propose that we make.

The second question is more general. Web Services are supposed
to be fairly coarse interfaces, whereas plug-in's generally 
are pretty fine. Also, there's things you can pass across a 
plug-in boundary that don't map into a web services paradigm. 
So presumably you'd design a plug-in rather differently to be 
able to publish it as a web service. Does this have design 
implications for us now?

This reminds me of a discussion I had with some folks who were
going to write a webservice tool that helped you construct
HL7 messages - it turned out to be rather circular because 
that's fundamentally a fine grained concept, whereas web 
services means messages, and defining the messages you use 
to build a message turned out to be a fruitless exercise.

Grahame



Eishay Smith wrote:
> I've talked with the Corona team today.
> http://www.eclipse.org/proposals/corona/
>
> Their project is about exposing OSGi Plugins as web services, which is what
> we wish to do.
> Since we wish to focus on healthcare and reuse as much 3'rd party code as
> we can, I think we should try to use their code.
> They are very interested to work with us, but only in the next week they
> will have a good knowledge of their time tables.
> We decided we'll talk next week and see if we can plan on collaboration.
>
> I told them about our plans to have SOAP interfaces to our plugins by
> August, and start integration with EMR vendors by then.
> If they will be able to commit to that, I assume we should work with them.
> If not, we better continue with the current OSGi on Server implementation
> and re-evaluate their work next year.
>
> Other pros in working with them are that they will work closely with the
> STP (SOA Tools Project), they intend to make use of SCA components by next
> year, and we are not the only user they will have this year.
>
> If anyone wants to join future calls with them, please let me know.
>
> Eishay
>
> _______________________________________________
> ohf-dev mailing list
> ohf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ohf-dev

--
Grahame Grieve
CTO, Jiva Medical       Software Integration Tools
CTO, Kestral Computing  Healthcare Applications