Quantcast

should we create a groovyws client plugin?

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

should we create a groovyws client plugin?

rhodebump-2
I am using groovyws in an application using the groovyws standalone jar.  Unfortunately, since this jar cannot be loaded by tomcat (chokes because it contains javax.servlet stuff), I need to be a little more specific about the jars that I include.

There's a listing of dependencies listed on this post:
http://groovy.codehaus.org/Using+WSClient+in+Grails

Anyway, I was thinking that I could create a plugin and bundle these jars into the plugin so if someone else wanted to use the GroovyWs client, they could just install the plugin.

Any thoughts on this?  
Thanks.



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


tog
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: should we create a groovyws client plugin?

tog
I used to deliver 3 versions (and can actually still do so):
  1- a standalone groovy version (the one you are mentioning)
  2- a very lean one containing only the grovyws classes
  3- an intermediate version containing groovyws + cxf + it's dependencies.

My position today (but I can change) is to only deliver (2) + guideline on how to integrate into grails because option 3 was also causing jar hell problems depending on your container :)
For example, cxf comes with geronimo mail jar while some prefer to use SUN implementation ...

The dependency list is so important that I think that at some point the developer has to make choice unless with could do something with OGSi but I am not yet familiar with the technology.
A better choice from my point of view would be to be able to use @Grab from grails but as far as I know this is not yet possible

Comments welcome

Guillaume


On Thu, May 7, 2009 at 9:22 PM, Phillip Rhodes <[hidden email]> wrote:
I am using groovyws in an application using the groovyws standalone jar.  Unfortunately, since this jar cannot be loaded by tomcat (chokes because it contains javax.servlet stuff), I need to be a little more specific about the jars that I include.

There's a listing of dependencies listed on this post:
http://groovy.codehaus.org/Using+WSClient+in+Grails

Anyway, I was thinking that I could create a plugin and bundle these jars into the plugin so if someone else wanted to use the GroovyWs client, they could just install the plugin.

Any thoughts on this?
Thanks.



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email





--

PGP KeyID: 1024D/47172155
FingerPrint: C739 8B3C 5ABF 127F CCFA  5835 F673 370B 4717 2155

http://cheztog.blogspot.com
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: should we create a groovyws client plugin?

rhodebump-2
I definitely appreciated the guidelines you gave.

What I ended up doing was creating maven war project (using an archetype) and adding the groovyws minimal as a dependency, along with those different repositories.

This created my webapp with a lib full of all the transitive dependencies.  Talk about a lot of jars!  Anyway, I copied some of these into my grails app lib directory.  It was easier doing this than poking through an entire maven repo.

I will check in my maven war project into the stitches google code project as this will allow me to keep the stitches client in sync with the groovyws project.


Thanks.

-----Original Message-----
From: "tog" <[hidden email]>
Sent: Friday, May 8, 2009 7:43am
To: [hidden email]
Subject: Re: [grails-user] should we create a groovyws client plugin?

I used to deliver 3 versions (and can actually still do so):
  1- a standalone groovy version (the one you are mentioning)
  2- a very lean one containing only the grovyws classes
  3- an intermediate version containing groovyws + cxf + it's dependencies.

My position today (but I can change) is to only deliver (2) + guideline on
how to integrate into grails because option 3 was also causing jar hell
problems depending on your container :)
For example, cxf comes with geronimo mail jar while some prefer to use SUN
implementation ...

The dependency list is so important that I think that at some point the
developer has to make choice unless with could do something with OGSi but I
am not yet familiar with the technology.
A better choice from my point of view would be to be able to use @Grab from
grails but as far as I know this is not yet possible

Comments welcome

Guillaume


On Thu, May 7, 2009 at 9:22 PM, Phillip Rhodes <[hidden email]>wrote:

> I am using groovyws in an application using the groovyws standalone jar.
>  Unfortunately, since this jar cannot be loaded by tomcat (chokes because it
> contains javax.servlet stuff), I need to be a little more specific about the
> jars that I include.
>
> There's a listing of dependencies listed on this post:
> http://groovy.codehaus.org/Using+WSClient+in+Grails
>
> Anyway, I was thinking that I could create a plugin and bundle these jars
> into the plugin so if someone else wanted to use the GroovyWs client, they
> could just install the plugin.
>
> Any thoughts on this?
> Thanks.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>


--

PGP KeyID: 1024D/47172155
FingerPrint: C739 8B3C 5ABF 127F CCFA  5835 F673 370B 4717 2155

http://cheztog.blogspot.com



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


tog
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: should we create a groovyws client plugin?

tog
Can you point me to your google code project so that I can have a look to what you did ?
Would it help if I was distributing a zip (not a jar) with cxf and all dependencies ?

On Fri, May 8, 2009 at 10:20 PM, Phillip Rhodes <[hidden email]> wrote:
I definitely appreciated the guidelines you gave.

What I ended up doing was creating maven war project (using an archetype) and adding the groovyws minimal as a dependency, along with those different repositories.

This created my webapp with a lib full of all the transitive dependencies.  Talk about a lot of jars!  Anyway, I copied some of these into my grails app lib directory.  It was easier doing this than poking through an entire maven repo.

I will check in my maven war project into the stitches google code project as this will allow me to keep the stitches client in sync with the groovyws project.


Thanks.

-----Original Message-----
From: "tog" <[hidden email]>
Sent: Friday, May 8, 2009 7:43am
To: [hidden email]
Subject: Re: [grails-user] should we create a groovyws client plugin?

I used to deliver 3 versions (and can actually still do so):
 1- a standalone groovy version (the one you are mentioning)
 2- a very lean one containing only the grovyws classes
 3- an intermediate version containing groovyws + cxf + it's dependencies.

My position today (but I can change) is to only deliver (2) + guideline on
how to integrate into grails because option 3 was also causing jar hell
problems depending on your container :)
For example, cxf comes with geronimo mail jar while some prefer to use SUN
implementation ...

The dependency list is so important that I think that at some point the
developer has to make choice unless with could do something with OGSi but I
am not yet familiar with the technology.
A better choice from my point of view would be to be able to use @Grab from
grails but as far as I know this is not yet possible

Comments welcome

Guillaume


On Thu, May 7, 2009 at 9:22 PM, Phillip Rhodes <[hidden email]>wrote:

> I am using groovyws in an application using the groovyws standalone jar.
>  Unfortunately, since this jar cannot be loaded by tomcat (chokes because it
> contains javax.servlet stuff), I need to be a little more specific about the
> jars that I include.
>
> There's a listing of dependencies listed on this post:
> http://groovy.codehaus.org/Using+WSClient+in+Grails
>
> Anyway, I was thinking that I could create a plugin and bundle these jars
> into the plugin so if someone else wanted to use the GroovyWs client, they
> could just install the plugin.
>
> Any thoughts on this?
> Thanks.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>


--

PGP KeyID: 1024D/47172155
FingerPrint: C739 8B3C 5ABF 127F CCFA  5835 F673 370B 4717 2155

http://cheztog.blogspot.com



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email





--

PGP KeyID: 1024D/47172155
FingerPrint: C739 8B3C 5ABF 127F CCFA  5835 F673 370B 4717 2155

http://cheztog.blogspot.com
tog
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: should we create a groovyws client plugin?

tog
Oops, just realize that stitches is the name of the project !

On Fri, May 8, 2009 at 11:03 PM, tog <[hidden email]> wrote:
Can you point me to your google code project so that I can have a look to what you did ?
Would it help if I was distributing a zip (not a jar) with cxf and all dependencies ?


On Fri, May 8, 2009 at 10:20 PM, Phillip Rhodes <[hidden email]> wrote:
I definitely appreciated the guidelines you gave.

What I ended up doing was creating maven war project (using an archetype) and adding the groovyws minimal as a dependency, along with those different repositories.

This created my webapp with a lib full of all the transitive dependencies.  Talk about a lot of jars!  Anyway, I copied some of these into my grails app lib directory.  It was easier doing this than poking through an entire maven repo.

I will check in my maven war project into the stitches google code project as this will allow me to keep the stitches client in sync with the groovyws project.


Thanks.

-----Original Message-----
From: "tog" <[hidden email]>
Sent: Friday, May 8, 2009 7:43am
To: [hidden email]
Subject: Re: [grails-user] should we create a groovyws client plugin?

I used to deliver 3 versions (and can actually still do so):
 1- a standalone groovy version (the one you are mentioning)
 2- a very lean one containing only the grovyws classes
 3- an intermediate version containing groovyws + cxf + it's dependencies.

My position today (but I can change) is to only deliver (2) + guideline on
how to integrate into grails because option 3 was also causing jar hell
problems depending on your container :)
For example, cxf comes with geronimo mail jar while some prefer to use SUN
implementation ...

The dependency list is so important that I think that at some point the
developer has to make choice unless with could do something with OGSi but I
am not yet familiar with the technology.
A better choice from my point of view would be to be able to use @Grab from
grails but as far as I know this is not yet possible

Comments welcome

Guillaume


On Thu, May 7, 2009 at 9:22 PM, Phillip Rhodes <[hidden email]>wrote:

> I am using groovyws in an application using the groovyws standalone jar.
>  Unfortunately, since this jar cannot be loaded by tomcat (chokes because it
> contains javax.servlet stuff), I need to be a little more specific about the
> jars that I include.
>
> There's a listing of dependencies listed on this post:
> http://groovy.codehaus.org/Using+WSClient+in+Grails
>
> Anyway, I was thinking that I could create a plugin and bundle these jars
> into the plugin so if someone else wanted to use the GroovyWs client, they
> could just install the plugin.
>
> Any thoughts on this?
> Thanks.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>


--

PGP KeyID: 1024D/47172155
FingerPrint: C739 8B3C 5ABF 127F CCFA  5835 F673 370B 4717 2155

http://cheztog.blogspot.com



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email





--

PGP KeyID: 1024D/47172155
FingerPrint: C739 8B3C 5ABF 127F CCFA  5835 F673 370B 4717 2155

http://cheztog.blogspot.com



--

PGP KeyID: 1024D/47172155
FingerPrint: C739 8B3C 5ABF 127F CCFA  5835 F673 370B 4717 2155

http://cheztog.blogspot.com
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: should we create a groovyws client plugin?

rhodebump-2
In reply to this post by tog
I uploaded that maven webapp project that I mentioned here:  http://stitches.googlecode.com/svn/trunk/my-webapp/  As the readme.txt states, i just used it so I could get all the groovyws dependencies into a single folder so I could more easier integrate it into my grails project.

BTW, the google code repo contains just the client side of stitches.   The server-side is in the plugin repo.

Lastly.  I found this weird thing with groovyws, where you cannot create multiple proxies.  I have a full write-up here.  http://www.philliprhodes.com/content/groovyws-too-much-good-thing-bad


Thanks for your attention!


On May 8, 2009, at 11:03 AM, tog wrote:

Can you point me to your google code project so that I can have a look to what you did ?
Would it help if I was distributing a zip (not a jar) with cxf and all dependencies ?

On Fri, May 8, 2009 at 10:20 PM, Phillip Rhodes <[hidden email]> wrote:
I definitely appreciated the guidelines you gave.

What I ended up doing was creating maven war project (using an archetype) and adding the groovyws minimal as a dependency, along with those different repositories.

This created my webapp with a lib full of all the transitive dependencies.  Talk about a lot of jars!  Anyway, I copied some of these into my grails app lib directory.  It was easier doing this than poking through an entire maven repo.

I will check in my maven war project into the stitches google code project as this will allow me to keep the stitches client in sync with the groovyws project.


Thanks.

-----Original Message-----
From: "tog" <[hidden email]>
Sent: Friday, May 8, 2009 7:43am
To: [hidden email]
Subject: Re: [grails-user] should we create a groovyws client plugin?

I used to deliver 3 versions (and can actually still do so):
 1- a standalone groovy version (the one you are mentioning)
 2- a very lean one containing only the grovyws classes
 3- an intermediate version containing groovyws + cxf + it's dependencies.

My position today (but I can change) is to only deliver (2) + guideline on
how to integrate into grails because option 3 was also causing jar hell
problems depending on your container :)
For example, cxf comes with geronimo mail jar while some prefer to use SUN
implementation ...

The dependency list is so important that I think that at some point the
developer has to make choice unless with could do something with OGSi but I
am not yet familiar with the technology.
A better choice from my point of view would be to be able to use @Grab from
grails but as far as I know this is not yet possible

Comments welcome

Guillaume


On Thu, May 7, 2009 at 9:22 PM, Phillip Rhodes <[hidden email]>wrote:

> I am using groovyws in an application using the groovyws standalone jar.
>  Unfortunately, since this jar cannot be loaded by tomcat (chokes because it
> contains javax.servlet stuff), I need to be a little more specific about the
> jars that I include.
>
> There's a listing of dependencies listed on this post:
> http://groovy.codehaus.org/Using+WSClient+in+Grails
>
> Anyway, I was thinking that I could create a plugin and bundle these jars
> into the plugin so if someone else wanted to use the GroovyWs client, they
> could just install the plugin.
>
> Any thoughts on this?
> Thanks.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>


--

PGP KeyID: 1024D/47172155
FingerPrint: C739 8B3C 5ABF 127F CCFA  5835 F673 370B 4717 2155

http://cheztog.blogspot.com



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email





--

PGP KeyID: 1024D/47172155
FingerPrint: C739 8B3C 5ABF 127F CCFA  5835 F673 370B 4717 2155

http://cheztog.blogspot.com

Loading...