RE: .wsdl for example....

2008-08-18 Thread Lance Norskog
Various Java web service libraries come with 'wsdl2java' and 'java2wsdl'
programs. You just run 'java2wsdl' on the Java soap description. 

-Original Message-
From: Ryan McKinley [mailto:[EMAIL PROTECTED] 
Sent: Monday, August 18, 2008 6:53 PM
To: solr-user@lucene.apache.org
Subject: Re: .wsdl for example

check SolrSharp
http://wiki.apache.org/solr/SolrSharp


On Aug 18, 2008, at 9:23 PM, Norberto Meijome wrote:

> 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.




Re: .wsdl for example....

2008-08-18 Thread Ryan McKinley

check SolrSharp
http://wiki.apache.org/solr/SolrSharp


On Aug 18, 2008, at 9:23 PM, Norberto Meijome wrote:


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.




Re: .wsdl for example....

2008-08-18 Thread Norberto Meijome
On Tue, 19 Aug 2008 11:23:48 +1000
Norberto Meijome <[EMAIL PROTECTED]> wrote:

> 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

To be clear, i don't suggest we should have a .wsdl for example, simply asking 
if there would be any use in having one.

but given the responses I got, I'm curious now to understand what I have gotten 
wrong :)

Best,
B
_
{Beto|Norberto|Numard} Meijome

 I sense much NT in you.
 NT leads to Bluescreen.
 Bluescreen leads to downtime.
 Downtime leads to suffering.
 NT is the path to the darkside.
 Powerful Unix is.

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.


Re: .wsdl for example....

2008-08-18 Thread Norberto Meijome
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.


Re: .wsdl for example....

2008-08-18 Thread Alexander Ramos Jardim
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.

2008/8/18 Norberto Meijome <[EMAIL PROTECTED]>

> hi :)
>
> does anyone have a .wsdl definition for the example bundled with SOLR?
>
> if nobody has it, would it be useful to have one ?
>
> cheers,
> B
> _
> {Beto|Norberto|Numard} Meijome
>
> Intelligence: Finding an error in a Knuth text.
> Stupidity: Cashing that $2.56 check you got.
>
> 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.
>



-- 
Alexander Ramos Jardim


Re: .wsdl for example....

2008-08-18 Thread Erik Hatcher


On Aug 18, 2008, at 11:27 AM, Norberto Meijome wrote:

does anyone have a .wsdl definition for the example bundled with SOLR?


WSDL?   surely you jest.

Erik



.wsdl for example....

2008-08-18 Thread Norberto Meijome
hi :)

does anyone have a .wsdl definition for the example bundled with SOLR? 

if nobody has it, would it be useful to have one ?

cheers,
B
_
{Beto|Norberto|Numard} Meijome

Intelligence: Finding an error in a Knuth text.
Stupidity: Cashing that $2.56 check you got.

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.