Re: Q: S2 REST vs JAXRS or S2-JAX-RS plugins

2012-08-25 Thread Frans Thamura
right now, we create /extend the REST plugiin, s2restplugins.java.net raise the JAX-RS issue , want to know the feedback. F On 8/25/12, Dave Newton wrote: > On Sat, Aug 25, 2012 at 11:30 AM, Frans Thamura wrote: > >> [...] if we use JAX-RS, that means S2 is not relevant anymore. >> > > That's

Re: Q: S2 REST vs JAXRS or S2-JAX-RS plugins

2012-08-25 Thread Dave Newton
On Sat, Aug 25, 2012 at 11:30 AM, Frans Thamura wrote: > [...] if we use JAX-RS, that means S2 is not relevant anymore. > That's kind of like saying "if I use phillips-head screws my slotted screwdriver is not relevant anymore". It's not relevant until you need a slotty screw. As more function

Re: Q: S2 REST vs JAXRS or S2-JAX-RS plugins

2012-08-25 Thread Frans Thamura
as n'importe quel effet légalement obligatoire. Étant donné que les email > peuvent facilement être sujets à la manipulation, nous ne pouvons accepter > aucune responsabilité pour le contenu fourni. > >> Date: Sat, 25 Aug 2012 08:16:05 +0700 >> Subject: RE: Q: S2 REST vs JAXRS

RE: Q: S2 REST vs JAXRS or S2-JAX-RS plugins

2012-08-25 Thread Martin Gainty
manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. > Date: Sat, 25 Aug 2012 08:16:05 +0700 > Subject: RE: Q: S2 REST vs JAXRS or S2-JAX-RS plugins > From: fr...@meruvian.org > To: user@struts.apache.org > > if jaxrs produce html. can it render in v

RE: Q: S2 REST vs JAXRS or S2-JAX-RS plugins

2012-08-24 Thread Frans Thamura
x27;importe quelle diffusion non autorisée ou la copie > de ceci est interdite. Ce message sert à l'information seulement et n'aura > pas n'importe quel effet légalement obligatoire. Étant donné que les email > peuvent facilement être sujets à la manipulation, nous ne pouvons

RE: Q: S2 REST vs JAXRS or S2-JAX-RS plugins

2012-08-24 Thread Martin Gainty
quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. . > Date: Fri, 24 Aug 2012 09:46:22 +0700 > Subject: RE: Q: S2 REST vs JAXRS or S2-JAX-RS plugins > From: f

RE: Spam: RE: Q: S2 REST vs JAXRS or S2-JAX-RS plugins

2012-08-24 Thread Martin Gainty
> > ..place longwinded disclaimer here... > > > > > >> From: jmoc...@velti.com > >> To: user@struts.apache.org > >> Subject: Re: Q: S2 REST vs JAXRS or S2-JAX-RS plugins > >> Date: Thu, 23 Aug 2012 18:06:24 +

Re: Spam: RE: Q: S2 REST vs JAXRS or S2-JAX-RS plugins

2012-08-24 Thread Frans Thamura
On Aug 23, 2012, at 11:21 AM, Martin Gainty wrote: > >> >> JBoss or Tomcat? >> >> Martin >> __ >> ..place longwinded disclaimer here... >> >> >>> From: jmoc...@velti.com >>> To: user@strut

Re: Spam: RE: Q: S2 REST vs JAXRS or S2-JAX-RS plugins

2012-08-24 Thread Joseph Mocker
uts.apache.org >> Subject: Re: Q: S2 REST vs JAXRS or S2-JAX-RS plugins >> Date: Thu, 23 Aug 2012 18:06:24 + >> >> �I agree, don't quite understand when you could use RESTeasy or Jersey in >> conjunction with Struts in the same web app. >> &

RE: Q: S2 REST vs JAXRS or S2-JAX-RS plugins

2012-08-23 Thread Frans Thamura
on non autorisée ou la copie > de ceci est interdite. Ce message sert à l'information seulement et n'aura > pas n'importe quel effet légalement obligatoire. Étant donné que les email > peuvent facilement être sujets à la manipulation, nous ne pouvons accepter > au

RE: Q: S2 REST vs JAXRS or S2-JAX-RS plugins

2012-08-23 Thread Martin Gainty
Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. > Date: Fri, 24 Aug 2012 03:17:05 +0700 > Subject: Re: Q: S2 REST vs JAXRS or S2-JAX-RS plugins > From: fr...@meruvian.org > To: user@struts

Re: Q: S2 REST vs JAXRS or S2-JAX-RS plugins

2012-08-23 Thread Frans Thamura
any idea to use resteasy with s2? esp to use the url pattern of rest (blabla/blabla) with Action On Aug 23, 2012 12:53 PM, "Lukasz Lenart" wrote: > But I think you can always use RESTeasy and get the same value without > needs for custom plugin. I don't see a point to have another JAX-RS > imple

RE: Q: S2 REST vs JAXRS or S2-JAX-RS plugins

2012-08-23 Thread Martin Gainty
JBoss or Tomcat? Martin __ ..place longwinded disclaimer here... > From: jmoc...@velti.com > To: user@struts.apache.org > Subject: Re: Q: S2 REST vs JAXRS or S2-JAX-RS plugins > Date: Thu, 23 Aug 2012 18:06:24 + > > �I

Re: Q: S2 REST vs JAXRS or S2-JAX-RS plugins

2012-08-23 Thread Joseph Mocker
I agree, don't quite understand when you could use RESTeasy or Jersey in conjunction with Struts in the same web app. I had written previously that we have a Jersey + Struts2 app running nicely. --joe Joseph Mocker | Velti | Senior Software Architect t +1.650.566.7033 m +1.408.676.

Re: Q: S2 REST vs JAXRS or S2-JAX-RS plugins

2012-08-22 Thread Lukasz Lenart
But I think you can always use RESTeasy and get the same value without needs for custom plugin. I don't see a point to have another JAX-RS implementation on the market. Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ 2012/8/21 Frans Thamura : > yes > > righr now the syntax is @res

Re: Q: S2 REST vs JAXRS or S2-JAX-RS plugins

2012-08-21 Thread Frans Thamura
yes righr now the syntax is @result and @action i think if we have more like @get etc that make it more powerfull On Aug 22, 2012 3:01 AM, "Łukasz Lenart" wrote: > Hi, > > I'm not sure if I understand, you just want implement JAX-RS as a > Struts 2 plugin ? > > > Regards > -- > Łukasz > mobile

Re: Q: S2 REST vs JAXRS or S2-JAX-RS plugins

2012-08-21 Thread Łukasz Lenart
Hi, I'm not sure if I understand, you just want implement JAX-RS as a Struts 2 plugin ? Regards -- Łukasz mobile +48 606 323 122 http://www.lenart.org.pl/ Warszawa JUG conference - Confitura http://confitura.pl/ - To unsubscri

Q: S2 REST vs JAXRS or S2-JAX-RS plugins

2012-08-16 Thread Frans Thamura
hi all we are try to adopt the JAX-RS standard to our Struts2 Plugins , http://s2restplugins.java.net our team discover the REST plugin development using JAX-RS is more easy because REST way, and yes, our solution now all REST, with Struts2 inside, but several syntax still using the S2 REST plugi