SOAP interface for kernel modules

Wednesday 02 April 2003 1:34:48 am

In the sdk documentation i read that for each kernel modules are currently available two interfaces: web and soap.
For the content module i should find two sub.directories: /kernel/content/web and kernel/content/soap.
In the current distribution I can only find /kernel/content without subdirectories.
What does it mean ? Sould I soon aspect a soap implementation in the next release ? Or the idea of multiple interfaces has been abandoned ?

Friday 11 April 2003 7:48:19 am

Any idea when this will be available? It a very useful feature that we could use right about now.

Tony Wood : twitter.com/tonywood
Vision with Technology
Experts in eZ Publish consulting & development

Power to the Editor!

Free eZ Training : http://www.VisionWT.com/training
eZ Future Podcast : http://www.VisionWT.com/eZ-Future

Friday 11 April 2003 8:15:49 am

> I've just been doing some reading and it appears a part of >soap is implemented >http://ez.no/developer/ez_publish_3/forum/developer/using_ez_soap_with_a_proxy
>
>All we need right now is ther client to go and get some infor >from another (non eZ) server and then incorporate that info >into the eZ page template.. Is this possible now?
>
>tia

>Tony

Hello Tony and others,

Some clarifications are necessary I think :)

The SOAP interfaces to the ezp modules are still to be written by the ezp team ;-)) .

What we (Hans, a thesis-student named Tom [who does most of the work] and myself) are doing is to write a ezp SOAP (client) module to a SOAP service ( which we are also implementing) to "refdb", a bibliographic reference database system (see rfdb.sf.net to learn more about refdb). Refdb uses its own db and has a small, but very active team of programmers.

Technically, its a challenging but nice thing to do from an architecture viewpoint. The bibliographic references will be available inside ezp3; the datastore is virtual: instead of using the ezp db it is implemented with SOAP services.

That's the way we try to integrate "third party" applications with ezp.

Another smaller project underway is a glossary operator which would highlight words in plain/xml text fields and link them to the corresponding entries in a glossary tree. This will be configurable in some ini file as well as with parametres inside templates.

Comments wellcome

tia

Paul

eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans

Friday 11 April 2003 1:06:48 pm

>I'd like to follow the progress of this project

You mean the glossary? That will be more or less quick to implement (but has lower priorities). Part of the code can be recuperated from the 2.2.x glossary module we never released (the part about avoiding messing up urls if a glossary entry is coincidentalyy part of it). For the rest, it is (seems) much simpler in 3.0

>As for eZp soap... will you be posting it here? The project i am
>looking at will need to go and get some information from a >exposed soap interface and then use it to populate a class tpl. I
>am guessing, I need to do it all in php and then pass to eZ
>somehow... hmmmm... This is not going to be as straight
>forward as i first thought.... Do you have any pointers?

No (not yet), I suggested our team to see if a new datatype could be matched against a soap request, but this turned out to become too complex. Hence the route now to map it to a (special) class.

Paul

eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans