On Mon, 18 Aug 2008 19:08:24 -0300
"Alexander Ramos Jardim" <[EMAIL PROTECTED]> wrote:
> Do you wanna a full web service for SOLR example? How a .wsdl will help you?
> Why don't you use the HTTP interface SOLR provides?
>
> Anyways, if you need to develop a web service (SOAP compliant) to access
> SOLR, just remember to use an embedded core on your webservice.
On Mon, 18 Aug 2008 15:37:24 -0400
Erik Hatcher <[EMAIL PROTECTED]> wrote:
> WSDL? surely you jest.
>
> Erik
:D I obviously said something terribly stupid, oh well, not the first time and
most likely wont be the last one either.
Anyway, the reason for my asking is :
- I've put together a SOLR search service with a few cores. Nothing fancy, it
works great as is.
- the .NET developer I am working with on this asked for a .wsdl (or .asmx)
file to import into Visual Studio ... yes, he can access the service directly,
but he seems to prefer a more 'well defined' interface (haven't really decided
whether it is worth the effort, but that is another question altogether)
The way I see it, SOLR is a RESTful service. I am not looking into wrapping
the whole thing behind SOAP ( I actually much prefer REST than SOAP, but that
is entering into quasi-religious grounds...) - which should be able to be
defined with a .wsdl ( v 1.1 should suffice as only GET + POST are supported in
SOLR anyway).
Am I missing anything here ?
thanks in advance for your time + thoughts ,
B
_________________________
{Beto|Norberto|Numard} Meijome
"He has no enemies, but is intensely disliked by his friends."
Oscar Wilde
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
