resteasy-users — A general discussion list for the projects end users of RESTEasy.

[Resteasy-users] Resteasy authentication

[Federico G. <fed...@te...>]

Hi everyone,

I have been reading Resteasy doc: 
http://docs.jboss.org/resteasy/docs/2.0.0.GA/userguide/html/Authentication.html 
about auth.
It says it is not proper for production. I have checked if there was any 
other solution for auth, but i haven't found anything related.
Could anyone help me?

Best,
Fede.

[Resteasy-users] hi

[<sea...@gm...>]

Hi  i finaly have the upperhand http://santaclaritabus.com/redirect.php?to=aHR0cDovL3d3dy5jbmJjNy5jb20vP3BpZD0xMjQyNDg=

Re: [Resteasy-users] Processing multipart/form-data input: input stream truncated after 1024 bytes

[ujay68 <uj...@gm...>]

Maybe I'm a little closer to an explanation: the
org.jboss.resteasy.plugins.providers.DataSourceProvider#readDataSource
method <http://resteasy.svn.sourceforge.net/viewvc/resteasy/trunk/jaxrs/resteasy-jaxrs/src/main/java/org/jboss/resteasy/plugins/providers/DataSourceProvider.java?revision=1349&view=markup>
first tries to read 4096 bytes from the given stream, then checks
in.available() to decide if there is more to write to a temp file.
This is wrong, because java.io.InputStream.available only returns a
guess if there are more bytes available. Here, the given InputStream
ist a java.io.SequenceInputStream that returns 0 after the first chunk
even if more chunks with more bytes are available. The
readDataSourceMethod must continue reading until EOF.

I'll add an issue to the bug tracker:
https://issues.jboss.org/browse/RESTEASY-545

Regards, Jay

Re: [Resteasy-users] Processing multipart/form-data input: input stream truncated after 1024 bytes

[Bill B. <bb...@re...>]

Can you try out 2.2-beta-1 please?  I think I fixed something in 
multipart then.  Also try not using a DataSource and getting the raw 
input stream.

On 5/18/11 9:36 AM, ujay68 wrote:
> Hi,
>
> I'm trying to process a file upload with the multipart/form-data
> facility like this:
>
> @POST
> @Path("/upload")
> @Consumes(MediaType.MULTIPART_FORM_DATA)
> public Object upload(MultipartFormDataInput formData) throws IOException {
>      InputPart part = formData.getFormDataMap().get("file").get(0); //
> "file" is the name of the browser's input field
>      DataSource dataSource = part.getBody(new GenericType<DataSource>() { });
>      InputStream in = dataSource.getInputStream();
>      // ... read from input stream
>      return Response.ok().build();
> }
>
> The data source has the correct content type, so the setup seems to be
> generally right.
>
> But when I read from the input stream, I get only 1024 bytes even if
> the uploaded file is longer.
>
> Just a guess: The InputPart is implemented by
> org.jboss.resteasy.plugins.providers.multipart.MultipartInputImpl.PartImpl.
> When I look into that PartImpl's part.bodyPart.body with a debugger,
> it looks like there is some storage provider behind the scenes
> implemented by a
> org.apache.james.mime4j.storage.ThresholdStorageProvider. That
> provider has a head of 1024 bytes and a tail with the rest of the
> bytes. That tail seems to be lost. Could be something else entirely,
> of course.
>
> I'm using v2.1.0.GA.
>
> Is this a bug? Am I doing something wrong here? Does someone know a
> workaround (apart from parsing with my own code)?
>
> Thanks, Jay
>
> ------------------------------------------------------------------------------
> What Every C/C++ and Fortran developer Should Know!
> Read this article and learn how Intel has extended the reach of its
> next-generation tools to help Windows* and Linux* C/C++ and Fortran
> developers boost performance applications - including clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> Resteasy-users mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/resteasy-users

-- 
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com

[Resteasy-users] Processing multipart/form-data input: input stream truncated after 1024 bytes

[ujay68 <uj...@gm...>]

Hi,

I'm trying to process a file upload with the multipart/form-data
facility like this:

@POST
@Path("/upload")
@Consumes(MediaType.MULTIPART_FORM_DATA)
public Object upload(MultipartFormDataInput formData) throws IOException {
    InputPart part = formData.getFormDataMap().get("file").get(0); //
"file" is the name of the browser's input field
    DataSource dataSource = part.getBody(new GenericType<DataSource>() { });
    InputStream in = dataSource.getInputStream();
    // ... read from input stream
    return Response.ok().build();
}

The data source has the correct content type, so the setup seems to be
generally right.

But when I read from the input stream, I get only 1024 bytes even if
the uploaded file is longer.

Just a guess: The InputPart is implemented by
org.jboss.resteasy.plugins.providers.multipart.MultipartInputImpl.PartImpl.
When I look into that PartImpl's part.bodyPart.body with a debugger,
it looks like there is some storage provider behind the scenes
implemented by a
org.apache.james.mime4j.storage.ThresholdStorageProvider. That
provider has a head of 1024 bytes and a tail with the rest of the
bytes. That tail seems to be lost. Could be something else entirely,
of course.

I'm using v2.1.0.GA.

Is this a bug? Am I doing something wrong here? Does someone know a
workaround (apart from parsing with my own code)?

Thanks, Jay

Re: [Resteasy-users] @Context injection doesn't work in JAX-RS/EJB bean

[henk de w. <hen...@ho...>]

(sorry the previous version didn't looked too good in text, let's try again, sorry for the noise)
Using JBoss AS 6, I have a JAX-RS resource that's also an EJB bean (also see http://community.jboss.org/message/599737). EJB injections work and the methods are correctly mapped to the declared URLs, but it seems that REST injections do not take place if RestEasy looks up the bean via JNDI. The following bean is defined in a separate EJB module, and it's JNDI name is declared via the resteasy.jndi.resources context param in web.xml of a web module:
@Produces("application/xml")@Path("xxx")@Statelesspublic class TestResource {   @Context  private SecurityContext security;   @EJB  private SomeEJB someEJB;   @GET  @Path("bla")  public User getTest() {     return "<hi>hi!</hi>";  } }

What happens is:  * When invoking localhost:8080/myroot/xxx/bla, getTest() is correctly called. * someEJB has a correct stub reference * security remains null If I put a similar bean directly in the web module and omit the EJB annotations, the SecurityContext is correctly injected:
@Produces("application/xml")@Path("yyy")public class TestWebResource {   @Context  private SecurityContext security;   @GET  @Path("bla")  public User getTest() {     return "<hi>hi!</hi>";  } }
>From some old posts (e.g. http://stackoverflow.com/questions/1765766/jax-rs-interface-markup-and-context-injection) I learned this was a known problem in the past (2009), but would be fixed with the upcoming Java EE 6/JAX-RS integration. Am I doing something wrong or has this integration never been done for RestEASY? 		 	   		  

[Resteasy-users] @Context injection doesn't work in JAX-RS/EJB bean

[henk de w. <hen...@ho...>]

Using JBoss AS 6, I have a JAX-RS resource that's also an EJB bean (also see http://community.jboss.org/message/599737). EJB injections work and the methods are correctly mapped to the declared URLs, but it seems that REST injections do not take place if RestEasy looks up the bean via JNDI. The following bean is defined in a separate EJB module, and it's JNDI name is declared via the resteasy.jndi.resources context param in web.xml of a web module:
@Produces("application/xml")@Path("xxx")@Statelesspublic class TestResource {   @Context  private SecurityContext security;   @EJB  private SomeEJB someEJB;   @GET  @Path("bla")  public User getTest() {     return "<hi>hi!</hi>";  } }

What happens is:  * When invoking localhost:8080/myroot/xxx/bla, getTest() is correctly called. * someEJB has a correct stub reference * security remains null If I put a similar bean directly in the web module and omit the EJB annotations, the SecurityContext is correctly injected:
@Produces("application/xml")@Path("yyy")public class TestWebResource {   @Context  private SecurityContext security;   @GET  @Path("bla")  public User getTest() {     return "<hi>hi!</hi>";  } }
>From some old posts (e.g. http://stackoverflow.com/questions/1765766/jax-rs-interface-markup-and-context-injection) I learned this was a known problem in the past (2009), but would be fixed with the upcoming Java EE 6/JAX-RS integration. Am I doing something wrong or has this integration never been done for RestEASY? 		 	   		  

Re: [Resteasy-users] Failed processing arguments for DELETE

[Ted J. <te...@re...>]

Upgrading RESTEasy solved my issue.

----- Original Message -----
From: "Ted Jones" <te...@re...>
To: res...@li...
Sent: Thursday, April 14, 2011 10:57:13 AM
Subject: [Resteasy-users] Failed processing arguments for DELETE

I have a method to handle DELETE requests that looks like this:

@DELETE
@Path("{isbn}")
@Produces("application/xml")
public String deleteBook(@PathParam("isbn") String isbn) {
	...
}


This results in a 400 error with the message: The request sent by the client was syntactically incorrect (Failed processing arguments of public java.lang.String org.teiid.rest.services.BookResource.deleteBook(java.lang.String)).


The underlying exception is this:  
Caused by: java.lang.NullPointerException
10:36:20,468 ERROR [STDERR] at org.jboss.resteasy.core.PathParamInjector.inject(PathParamInjector.java:74)

My URL passed in is this: http://localhost:8080/simple/teiid-rest/book/1

I have a GET operation with the same signature that works as expected.

Any thoughts on why I might be getting this error?

Thanks,
Ted

------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
Resteasy-users mailing list
Res...@li...
https://lists.sourceforge.net/lists/listinfo/resteasy-users

[Resteasy-users] Failed processing arguments for DELETE

[Ted J. <te...@re...>]

I have a method to handle DELETE requests that looks like this:

@DELETE
@Path("{isbn}")
@Produces("application/xml")
public String deleteBook(@PathParam("isbn") String isbn) {
	...
}


This results in a 400 error with the message: The request sent by the client was syntactically incorrect (Failed processing arguments of public java.lang.String org.teiid.rest.services.BookResource.deleteBook(java.lang.String)).


The underlying exception is this:  
Caused by: java.lang.NullPointerException
10:36:20,468 ERROR [STDERR] at org.jboss.resteasy.core.PathParamInjector.inject(PathParamInjector.java:74)

My URL passed in is this: http://localhost:8080/simple/teiid-rest/book/1

I have a GET operation with the same signature that works as expected.

Any thoughts on why I might be getting this error?

Thanks,
Ted

Re: [Resteasy-users] JBoss AS 6.0 Final: @Path annotated class not recognized

[Oliver V. <oli...@go...>]

Hi,

I finally found the problem. It was a bad directory hierarchy within my 
WAR file. The class-files must be stored under /WEB-INF/classes/, but I 
placed them directly at the root of the WAR file. Fixing this issue made 
the RESTful service work as expected.

-Oliver

04.04.2011 14:42, Oliver Vesper:
>> I'm trying to deploy a small and simple restful service to a fresh
>> installation of JBoss AS 6.0 FINAL (running the default configuration
>> which includes the resteasy-deployers). My WAR file (RestTest.war)
>> contains the following two files:
>> - WEB-INF/web.xml
>> - test/resteasy/MyService.class

Re: [Resteasy-users] JBoss AS 6.0 Final: @Path annotated class not recognized

[Oliver V. <oli...@go...>]

David,

thanks for replying to my request. Unfortunately your suggestion didn't 
work out either... I still get a 404:

HTTP Status 404 - /RestTest/test/foo
type Status report
message /RestTest/test/foo
description The requested resource (/RestTest/test/foo) is not available.
JBoss Web/3.0.0-CR1

I'm afraid my annotated service-class is not being recognized but I 
cannot figure out what's the missing part.

Is it correct that it is not required to provide any servlet-information 
within the web.xml descriptor? I guess the annotations should be 
sufficient but it's not working...

-Oliver


04.04.2011 14:21, David Haynes:
> I bet it you try http://localhost/RestTest/test/foo you will get what
> you expected.
> The @Path sets the prefix for the method but you have to reference the
> method too.
>
> -david-
>
> On Sun, Apr 3, 2011 at 12:45 PM, Oliver Vesper
> <oli...@go... <mailto:oli...@go...>> wrote:
>
>     Hi,
>
>     first of all: I am totally new to RESTEasy!
>
>     I'm trying to deploy a small and simple restful service to a fresh
>     installation of JBoss AS 6.0 FINAL (running the default configuration
>     which includes the resteasy-deployers). My WAR file (RestTest.war)
>     contains the following two files:
>     - WEB-INF/web.xml
>     - test/resteasy/MyService.class
>
>     The web.xml looks like this:
>
>     <web-app version="3.0" xmlns="http://java.sun.com/xml/ns/javaee"
>     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>     xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
>     http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd">
>     </web-app>
>
>     The source-code for MyService-class as follows:
>
>     package test.resteasy;
>     import javax.ws.rs.GET;
>     import javax.ws.rs.Path;
>     @Path("test")
>     public class MyService {
>         @GET
>         public String foo() {
>            return "Hello World";
>         }
>     }
>
>     As I haven't annotated the foo-method with another @Path-annotation I
>     assume it should be accessible by the following URL:
>     http://localhost:8080/RestTest/test
>
>     But I only get a HTTP-404-error.
>
>     I debugged into ResteasyScannerDeployer (and also
>     ResteasyIntegrationDeployer) and it looks like my @Path-annotated class
>     is not being recognized. It looks like the scan-method of
>     ResteasyScannerDeployer tries to find those classes which are annotated
>     with @Path:
>
>     Set<Element<Path, Class<?>>> resources = null;
>     Set<Element<Provider, Class<?>>> providers = null;
>     if (resteasyDeploymentData.isScanResources())
>     {
>         resources = env.classIsAnnotatedWith(Path.class);
>     }
>
>     But after calling "classIsAnnotatedWith(Path.class)" the
>     resources-variable is set to an empty collection.
>
>     I would really appreciate anybody giving me a hint to what I'm doing
>     wrong. Thanks a lot!
>
>     -Oliver
>
>     ------------------------------------------------------------------------------
>     Create and publish websites with WebMatrix
>     Use the most popular FREE web apps or write code yourself;
>     WebMatrix provides all the features you need to develop and
>     publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
>     _______________________________________________
>     Resteasy-users mailing list
>     Res...@li...
>     <mailto:Res...@li...>
>     https://lists.sourceforge.net/lists/listinfo/resteasy-users
>
>

[Resteasy-users] JBoss AS 6.0 Final: @Path annotated class not recognized

[Oliver V. <oli...@go...>]

Hi,

first of all: I am totally new to RESTEasy!

I'm trying to deploy a small and simple restful service to a fresh 
installation of JBoss AS 6.0 FINAL (running the default configuration 
which includes the resteasy-deployers). My WAR file (RestTest.war) 
contains the following two files:
- WEB-INF/web.xml
- test/resteasy/MyService.class

The web.xml looks like this:

<web-app version="3.0" xmlns="http://java.sun.com/xml/ns/javaee" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee 
http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd">
</web-app>

The source-code for MyService-class as follows:

package test.resteasy;
import javax.ws.rs.GET;
import javax.ws.rs.Path;
@Path("test")
public class MyService {
    @GET
    public String foo() {
       return "Hello World";
    }
}

As I haven't annotated the foo-method with another @Path-annotation I 
assume it should be accessible by the following URL:
http://localhost:8080/RestTest/test

But I only get a HTTP-404-error.

I debugged into ResteasyScannerDeployer (and also 
ResteasyIntegrationDeployer) and it looks like my @Path-annotated class 
is not being recognized. It looks like the scan-method of 
ResteasyScannerDeployer tries to find those classes which are annotated 
with @Path:

Set<Element<Path, Class<?>>> resources = null;
Set<Element<Provider, Class<?>>> providers = null;
if (resteasyDeploymentData.isScanResources())
{
    resources = env.classIsAnnotatedWith(Path.class);
}

But after calling "classIsAnnotatedWith(Path.class)" the 
resources-variable is set to an empty collection.

I would really appreciate anybody giving me a hint to what I'm doing 
wrong. Thanks a lot!

-Oliver

Re: [Resteasy-users] "Could not find resource for relative" driving me mad....

[Frans v. N. <fra...@gm...>]

Ah, ok.

Have you tried to add a @Path on the method as well?


On 23 March 2011 20:37, Toby O'Rourke <to...@ga...> wrote:

> Hi,
>
> That would be default Jetty behaviour, It is taking the artefact name from
> the pom
> http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin#MavenJettyPlugin-WebappConfiguration
>
> Thanks for having a stab tho :)
>
> Toby.
>
> <http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin#MavenJettyPlugin-WebappConfiguration>
> On 23 Mar 2011, at 18:31, Frans van Niekerk wrote:
>
> This is a bit of a shot in the dark. I see your root context is
> /history-service but I don't see anything that indicates it being set?
>
> On 23 March 2011 15:35, Toby O'Rourke <to...@ga...> wrote:
>
>> Hi,
>>
>> I'm getting the following errors when I try and hit my resource...
>>
>> Could not find resource for relative : /history of full path: http://localhost:8064/history-service/history
>>
>>
>> Relevant snippets below...
>>
>> web.xml:
>>
>> <web-app>
>>
>>     <context-param>
>>         <param-name>contextConfigLocation</param-name>
>>         <param-value>classpath:META-INF/applicationContext-web.xml</param-value>
>>     </context-param>
>>
>>     <listener>
>>         <listener-class>org.jboss.resteasy.plugins.server.servlet.ResteasyBootstrap</listener-class>
>>     </listener>
>>
>>     <listener>
>>         <listener-class>org.jboss.resteasy.plugins.spring.SpringContextLoaderListener</listener-class>
>>     </listener>
>>
>>     <servlet>
>>         <servlet-name>Resteasy</servlet-name>
>>         <servlet-class>org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher
>>         </servlet-class>
>>     </servlet>
>>
>>     <servlet-mapping>
>>         <servlet-name>Resteasy</servlet-name>
>>         <url-pattern>/*</url-pattern>
>>     </servlet-mapping>
>>
>> </web-app>
>>
>> --------------------------------
>>
>> applicationContext-web.xml:
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <beans xmlns="http://www.springframework.org/schema/beans"
>>     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>     xmlns:p="http://www.springframework.org/schema/p"
>>     xmlns:context="http://www.springframework.org/schema/context"
>>     xsi:schemaLocation="
>>         http://www.springframework.org/schema/beans
>>         http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
>>         http://www.springframework.org/schema/context
>>         http://www.springframework.org/schema/context/spring-context-3.0.xsd">
>>
>>     <bean id="RESTeasyProviderFactory" class="org.springframework.web.context.support.ServletContextAttributeFactoryBean">
>> 		<property name="attributeName" value="org.jboss.resteasy.spi.ResteasyProviderFactory" />
>> 	</bean>
>>
>>
>> 	<bean id="RESTeasyRegistry" class="org.springframework.web.context.support.ServletContextAttributeFactoryBean">
>> 		<property name="attributeName" value="org.jboss.resteasy.spi.Registry" />
>> 	</bean>
>>
>>
>> 	<bean id="RESTeasyBeanPostProcessor" class="org.jboss.resteasy.plugins.spring.SpringBeanProcessor">
>> 		<constructor-arg ref="RESTeasyRegistry" />
>> 		<constructor-arg ref="RESTeasyProviderFactory" />
>> 	</bean>
>>
>> </beans>
>>
>> ---------------------------------
>>
>> pom.xml:
>>
>> ...
>>
>>        <plugin>
>>                 <groupId>org.mortbay.jetty</groupId>
>>                 <artifactId>maven-jetty-plugin</artifactId>
>>                 <version>6.1.23</version>
>>                 <configuration>
>>                     <connectors>
>>                         <connector implementation="org.mortbay.jetty.nio.SelectChannelConnector">
>>                             <port>8064</port>
>>                             <maxIdleTime>60000</maxIdleTime>
>>                         </connector>
>>                     </connectors>
>>                 </configuration>
>>             </plugin>
>> ...
>>     <dependencies>
>>         <dependency>
>>             <groupId>org.jboss.resteasy</groupId>
>>             <artifactId>resteasy-jaxrs</artifactId>
>>             <version>2.1.0.GA</version>
>>         </dependency>
>> 		<dependency>
>> 			<groupId>org.jboss.resteasy</groupId>
>> 			<artifactId>resteasy-jaxb-provider</artifactId>
>> 			<version>2.1.0.GA</version>
>> 		</dependency>
>>         <dependency>
>>             <groupId>org.jboss.resteasy</groupId>
>>             <artifactId>resteasy-spring</artifactId>
>>             <version>2.1.0.GA</version>
>>         </dependency>
>>         <dependency>
>>             <groupId>org.springframework</groupId>
>>             <artifactId>spring-jdbc</artifactId>
>>             <version>3.0.5.RELEASE</version>
>>         </dependency>
>>         <dependency>
>>             <groupId>org.springframework</groupId>
>>             <artifactId>spring-web</artifactId>
>>             <version>3.0.5.RELEASE</version>
>>         </dependency>
>>     </dependencies>
>>
>> ...
>>
>> -------------------------
>>
>> HistoryResource.java:
>>
>> @Path("/history")
>> public interface HistoryResouce {
>>
>>     @GET
>>     String sayHello();
>> }
>>
>> ----------------------------
>>
>> HistoryResourceImpl.java:
>>
>> public class HistoryResourceImpl implements HistoryResource {
>>
>>     public String sayHello() {
>>         return String.format("Hello, World!");
>>     }
>> }
>>
>>
>> As you can see, this is at the hello world stage at the moment - I'm
>> stumped! Grateful for any help,
>>
>> Cheers,
>>
>> Toby.
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Enable your software for Intel(R) Active Management Technology to meet the
>> growing manageability and security demands of your customers. Businesses
>> are taking advantage of Intel(R) vPro (TM) technology - will your software
>> be a part of the solution? Download the Intel(R) Manageability Checker
>> today! http://p.sf.net/sfu/intel-dev2devmar
>> _______________________________________________
>> Resteasy-users mailing list
>> Res...@li...
>> https://lists.sourceforge.net/lists/listinfo/resteasy-users
>>
>>
>
>

Re: [Resteasy-users] "Could not find resource for relative" driving me mad....

[Toby O'R. <to...@ga...>]

Hi,

That would be default Jetty behaviour, It is taking the artefact name from the pom http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin#MavenJettyPlugin-WebappConfiguration

Thanks for having a stab tho :)

Toby.
<http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin#MavenJettyPlugin-WebappConfiguration>
On 23 Mar 2011, at 18:31, Frans van Niekerk wrote:

This is a bit of a shot in the dark. I see your root context is /history-service but I don't see anything that indicates it being set?

On 23 March 2011 15:35, Toby O'Rourke <to...@ga...<mailto:to...@ga...>> wrote:
Hi,

I'm getting the following errors when I try and hit my resource...


Could not find resource for relative : /history of full path: http://localhost:8064/history-service/history


Relevant snippets below...

web.xml:

<web-app>

    <context-param>
        <param-name>contextConfigLocation</param-name>
        <param-value>classpath:META-INF/applicationContext-web.xml</param-value>
    </context-param>

    <listener>
        <listener-class>org.jboss.resteasy.plugins.server.servlet.ResteasyBootstrap</listener-class>
    </listener>

    <listener>
        <listener-class>org.jboss.resteasy.plugins.spring.SpringContextLoaderListener</listener-class>
    </listener>

    <servlet>
        <servlet-name>Resteasy</servlet-name>
        <servlet-class>org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher
        </servlet-class>
    </servlet>

    <servlet-mapping>
        <servlet-name>Resteasy</servlet-name>
        <url-pattern>/*</url-pattern>
    </servlet-mapping>

</web-app>

--------------------------------

applicationContext-web.xml:

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:p="http://www.springframework.org/schema/p"
    xmlns:context="http://www.springframework.org/schema/context"
    xsi:schemaLocation="
        http://www.springframework.org/schema/beans
        http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
        http://www.springframework.org/schema/context
        http://www.springframework.org/schema/context/spring-context-3.0.xsd">

    <bean id="RESTeasyProviderFactory" class="org.springframework.web.context.support.ServletContextAttributeFactoryBean">
                <property name="attributeName" value="org.jboss.resteasy.spi.ResteasyProviderFactory" />
        </bean>


        <bean id="RESTeasyRegistry" class="org.springframework.web.context.support.ServletContextAttributeFactoryBean">
                <property name="attributeName" value="org.jboss.resteasy.spi.Registry" />
        </bean>


        <bean id="RESTeasyBeanPostProcessor" class="org.jboss.resteasy.plugins.spring.SpringBeanProcessor">
                <constructor-arg ref="RESTeasyRegistry" />
                <constructor-arg ref="RESTeasyProviderFactory" />
        </bean>

</beans>

---------------------------------

pom.xml:

...

       <plugin>
                <groupId>org.mortbay.jetty</groupId>
                <artifactId>maven-jetty-plugin</artifactId>
                <version>6.1.23</version>
                <configuration>
                    <connectors>
                        <connector implementation="org.mortbay.jetty.nio.SelectChannelConnector">
                            <port>8064</port>
                            <maxIdleTime>60000</maxIdleTime>
                        </connector>
                    </connectors>
                </configuration>
            </plugin>
...
    <dependencies>
        <dependency>
            <groupId>org.jboss.resteasy</groupId>
            <artifactId>resteasy-jaxrs</artifactId>
            <version>2.1.0.GA<http://2.1.0.GA/></version>
        </dependency>
                <dependency>
                        <groupId>org.jboss.resteasy</groupId>
                        <artifactId>resteasy-jaxb-provider</artifactId>
                        <version>2.1.0.GA<http://2.1.0.GA/></version>
                </dependency>
        <dependency>
            <groupId>org.jboss.resteasy</groupId>
            <artifactId>resteasy-spring</artifactId>
            <version>2.1.0.GA<http://2.1.0.GA/></version>
        </dependency>
        <dependency>
            <groupId>org.springframework</groupId>
            <artifactId>spring-jdbc</artifactId>
            <version>3.0.5.RELEASE</version>
        </dependency>
        <dependency>
            <groupId>org.springframework</groupId>
            <artifactId>spring-web</artifactId>
            <version>3.0.5.RELEASE</version>
        </dependency>
    </dependencies>

...

-------------------------

HistoryResource.java:

@Path("/history")
public interface HistoryResouce {

    @GET
    String sayHello();
}

----------------------------

HistoryResourceImpl.java:

public class HistoryResourceImpl implements HistoryResource {

    public String sayHello() {
        return String.format("Hello, World!");
    }
}

As you can see, this is at the hello world stage at the moment - I'm stumped! Grateful for any help,

Cheers,

Toby.


------------------------------------------------------------------------------
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software
be a part of the solution? Download the Intel(R) Manageability Checker
today! http://p.sf.net/sfu/intel-dev2devmar
_______________________________________________
Resteasy-users mailing list
Res...@li...<mailto:Res...@li...>
https://lists.sourceforge.net/lists/listinfo/resteasy-users

Re: [Resteasy-users] "Could not find resource for relative" driving me mad....

[Frans v. N. <fra...@gm...>]

This is a bit of a shot in the dark. I see your root context is
/history-service but I don't see anything that indicates it being set?

On 23 March 2011 15:35, Toby O'Rourke <to...@ga...> wrote:

> Hi,
>
> I'm getting the following errors when I try and hit my resource...
>
> Could not find resource for relative : /history of full path: http://localhost:8064/history-service/history
>
>
> Relevant snippets below...
>
> web.xml:
>
> <web-app>
>
>     <context-param>
>         <param-name>contextConfigLocation</param-name>
>         <param-value>classpath:META-INF/applicationContext-web.xml</param-value>
>     </context-param>
>
>     <listener>
>         <listener-class>org.jboss.resteasy.plugins.server.servlet.ResteasyBootstrap</listener-class>
>     </listener>
>
>     <listener>
>         <listener-class>org.jboss.resteasy.plugins.spring.SpringContextLoaderListener</listener-class>
>     </listener>
>
>     <servlet>
>         <servlet-name>Resteasy</servlet-name>
>         <servlet-class>org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher
>         </servlet-class>
>     </servlet>
>
>     <servlet-mapping>
>         <servlet-name>Resteasy</servlet-name>
>         <url-pattern>/*</url-pattern>
>     </servlet-mapping>
>
> </web-app>
>
> --------------------------------
>
> applicationContext-web.xml:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <beans xmlns="http://www.springframework.org/schema/beans"
>     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>     xmlns:p="http://www.springframework.org/schema/p"
>     xmlns:context="http://www.springframework.org/schema/context"
>     xsi:schemaLocation="
>         http://www.springframework.org/schema/beans
>         http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
>         http://www.springframework.org/schema/context
>         http://www.springframework.org/schema/context/spring-context-3.0.xsd">
>
>     <bean id="RESTeasyProviderFactory" class="org.springframework.web.context.support.ServletContextAttributeFactoryBean">
> 		<property name="attributeName" value="org.jboss.resteasy.spi.ResteasyProviderFactory" />
> 	</bean>
>
>
> 	<bean id="RESTeasyRegistry" class="org.springframework.web.context.support.ServletContextAttributeFactoryBean">
> 		<property name="attributeName" value="org.jboss.resteasy.spi.Registry" />
> 	</bean>
>
>
> 	<bean id="RESTeasyBeanPostProcessor" class="org.jboss.resteasy.plugins.spring.SpringBeanProcessor">
> 		<constructor-arg ref="RESTeasyRegistry" />
> 		<constructor-arg ref="RESTeasyProviderFactory" />
> 	</bean>
>
> </beans>
>
> ---------------------------------
>
> pom.xml:
>
> ...
>
>        <plugin>
>                 <groupId>org.mortbay.jetty</groupId>
>                 <artifactId>maven-jetty-plugin</artifactId>
>                 <version>6.1.23</version>
>                 <configuration>
>                     <connectors>
>                         <connector implementation="org.mortbay.jetty.nio.SelectChannelConnector">
>                             <port>8064</port>
>                             <maxIdleTime>60000</maxIdleTime>
>                         </connector>
>                     </connectors>
>                 </configuration>
>             </plugin>
> ...
>     <dependencies>
>         <dependency>
>             <groupId>org.jboss.resteasy</groupId>
>             <artifactId>resteasy-jaxrs</artifactId>
>             <version>2.1.0.GA</version>
>         </dependency>
> 		<dependency>
> 			<groupId>org.jboss.resteasy</groupId>
> 			<artifactId>resteasy-jaxb-provider</artifactId>
> 			<version>2.1.0.GA</version>
> 		</dependency>
>         <dependency>
>             <groupId>org.jboss.resteasy</groupId>
>             <artifactId>resteasy-spring</artifactId>
>             <version>2.1.0.GA</version>
>         </dependency>
>         <dependency>
>             <groupId>org.springframework</groupId>
>             <artifactId>spring-jdbc</artifactId>
>             <version>3.0.5.RELEASE</version>
>         </dependency>
>         <dependency>
>             <groupId>org.springframework</groupId>
>             <artifactId>spring-web</artifactId>
>             <version>3.0.5.RELEASE</version>
>         </dependency>
>     </dependencies>
>
> ...
>
> -------------------------
>
> HistoryResource.java:
>
> @Path("/history")
> public interface HistoryResouce {
>
>     @GET
>     String sayHello();
> }
>
> ----------------------------
>
> HistoryResourceImpl.java:
>
> public class HistoryResourceImpl implements HistoryResource {
>
>     public String sayHello() {
>         return String.format("Hello, World!");
>     }
> }
>
>
> As you can see, this is at the hello world stage at the moment - I'm
> stumped! Grateful for any help,
>
> Cheers,
>
> Toby.
>
>
>
> ------------------------------------------------------------------------------
> Enable your software for Intel(R) Active Management Technology to meet the
> growing manageability and security demands of your customers. Businesses
> are taking advantage of Intel(R) vPro (TM) technology - will your software
> be a part of the solution? Download the Intel(R) Manageability Checker
> today! http://p.sf.net/sfu/intel-dev2devmar
> _______________________________________________
> Resteasy-users mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/resteasy-users
>
>

[Resteasy-users] "Could not find resource for relative" driving me mad....

[Toby O'R. <to...@ga...>]

Hi,

I'm getting the following errors when I try and hit my resource...


Could not find resource for relative : /history of full path: http://localhost:8064/history-service/history


Relevant snippets below...

web.xml:

<web-app>

    <context-param>
        <param-name>contextConfigLocation</param-name>
        <param-value>classpath:META-INF/applicationContext-web.xml</param-value>
    </context-param>

    <listener>
        <listener-class>org.jboss.resteasy.plugins.server.servlet.ResteasyBootstrap</listener-class>
    </listener>

    <listener>
        <listener-class>org.jboss.resteasy.plugins.spring.SpringContextLoaderListener</listener-class>
    </listener>

    <servlet>
        <servlet-name>Resteasy</servlet-name>
        <servlet-class>org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher
        </servlet-class>
    </servlet>

    <servlet-mapping>
        <servlet-name>Resteasy</servlet-name>
        <url-pattern>/*</url-pattern>
    </servlet-mapping>

</web-app>

--------------------------------

applicationContext-web.xml:

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:p="http://www.springframework.org/schema/p"
    xmlns:context="http://www.springframework.org/schema/context"
    xsi:schemaLocation="
        http://www.springframework.org/schema/beans
        http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
        http://www.springframework.org/schema/context
        http://www.springframework.org/schema/context/spring-context-3.0.xsd">

    <bean id="RESTeasyProviderFactory" class="org.springframework.web.context.support.ServletContextAttributeFactoryBean">
                <property name="attributeName" value="org.jboss.resteasy.spi.ResteasyProviderFactory" />
        </bean>


        <bean id="RESTeasyRegistry" class="org.springframework.web.context.support.ServletContextAttributeFactoryBean">
                <property name="attributeName" value="org.jboss.resteasy.spi.Registry" />
        </bean>


        <bean id="RESTeasyBeanPostProcessor" class="org.jboss.resteasy.plugins.spring.SpringBeanProcessor">
                <constructor-arg ref="RESTeasyRegistry" />
                <constructor-arg ref="RESTeasyProviderFactory" />
        </bean>

</beans>

---------------------------------

pom.xml:

...

       <plugin>
                <groupId>org.mortbay.jetty</groupId>
                <artifactId>maven-jetty-plugin</artifactId>
                <version>6.1.23</version>
                <configuration>
                    <connectors>
                        <connector implementation="org.mortbay.jetty.nio.SelectChannelConnector">
                            <port>8064</port>
                            <maxIdleTime>60000</maxIdleTime>
                        </connector>
                    </connectors>
                </configuration>
            </plugin>
...
    <dependencies>
        <dependency>
            <groupId>org.jboss.resteasy</groupId>
            <artifactId>resteasy-jaxrs</artifactId>
            <version>2.1.0.GA</version>
        </dependency>
                <dependency>
                        <groupId>org.jboss.resteasy</groupId>
                        <artifactId>resteasy-jaxb-provider</artifactId>
                        <version>2.1.0.GA</version>
                </dependency>
        <dependency>
            <groupId>org.jboss.resteasy</groupId>
            <artifactId>resteasy-spring</artifactId>
            <version>2.1.0.GA</version>
        </dependency>
        <dependency>
            <groupId>org.springframework</groupId>
            <artifactId>spring-jdbc</artifactId>
            <version>3.0.5.RELEASE</version>
        </dependency>
        <dependency>
            <groupId>org.springframework</groupId>
            <artifactId>spring-web</artifactId>
            <version>3.0.5.RELEASE</version>
        </dependency>
    </dependencies>

...

-------------------------

HistoryResource.java:

@Path("/history")
public interface HistoryResouce {

    @GET
    String sayHello();
}

----------------------------

HistoryResourceImpl.java:

public class HistoryResourceImpl implements HistoryResource {

    public String sayHello() {
        return String.format("Hello, World!");
    }
}

As you can see, this is at the hello world stage at the moment - I'm stumped! Grateful for any help,

Cheers,

Toby.

[Resteasy-users] RESTEasy - CDI Integration: ContextNotActiveException while using a @ConversationScoped bean within a resource class

[Robert R. <rob...@go...>]

Hi all,

i'm using RESTEasy inside JBoss AS6 Final. When trying to inject and use a @ConversationScoped bean inside my JAX-RS resource class the following exception is thrown:

2011-03-09 08:07:08,687 ERROR Servlet.service() for servlet default threw exception: org.jboss.resteasy.spi.UnhandledException: org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope type javax.enterprise.context.ConversationScoped
...
Caused by: org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope type javax.enterprise.context.ConversationScoped
      at org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:643) [:6.0.0.Final]
      at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:77) [:6.0.0.Final]
      at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:87) [:6.0.0.Final]

Is this a Bug or is the usage of ConversationScoped beans currently not supported? Is there a workaround to get an active transient ConversationContext inside my JAX-RS resource to prevent the exception? I'm not trying to establish a long running conversation using REST so a transient conversation would be sufficient. The @ConversationScoped is solely present/required because i'm reusing business logic that is also used via Web-UI.

Below is a small Testcase (derived from the resteasy-cdi-test module in the source distribution) demonstrating the scenario

Any help would be appreciated
Thanks, Robert

----------------------------------------

package org.jboss.resteasy.cdi.test.basic;

import javax.inject.Inject;
import javax.ws.rs.*;

import org.jboss.resteasy.cdi.test.ConverstationalCat;

@Path("/resource")
@Produces("text/plain")
public class TestResource {
 @Inject
 private ConverstationalCat cCat;

 @GET
 @Path("/fieldInjection")
 public String fieldInjection()
 {
	  return cCat.sayHello(); //throws org.jboss.weld.context.ContextNotActiveException
 }

}

// -------------------------------------------------------------------------------------------------------------------

package org.jboss.resteasy.cdi.test;

import java.io.Serializable;
import javax.enterprise.context.ConversationScoped;

@ConversationScoped
public class ConverstationalCat implements Serializable
{
 private static final long serialVersionUID = 5875753813720411262L;

 public String sayHello() {
	   return "hello conversational cat";
 }
}

[Resteasy-users] Fwd: Problems unmarshalling atom response

[Birgit M. <bi...@kn...>]

Hi All,
I am trying to use a 3rd party API that returns an atom-formatted xml
response. I am able to send the request using ProxyFactory and I am
trying to extract my JAXB Object by using
content.getJAXBObject(ContactList.class);
My ContactList class is a JAXB annotated class, namespace is properly
set. It has a bunch of elements and one attribute.When I try to access
my ContactList instance only the attribute is properly populated, all
elements are still null. Any ideas why this seems to only partially
unmarshall?

Here's my ContactList class:
@XmlRootElement(name = "ContactList", namespace = "{namespace}")
@XmlAccessorType(XmlAccessType.PROPERTY)
public class ContactList {

   @XmlAttribute
   public String id;
   .....
   @XmlElement  (name="Name")
   public String name;
   ......


}

Here's the Service that I am calling using ProxyFactory
public interface ContactListService {

  @GET
  @Path("lists/{id}")
  @Produces("application/atom+xml")
  public Entry getListById(@PathParam("id") String id);


....
}

and here's the call to the proxy:

ContactListService  client = ProxyFactory.create(ContactListService
.class, API_BASE + contactListResource, clientExecutor);
Content content = client.getListById("2").getContent();
ContactList list = content.getJAXBObject(ContactList.class);

--> now list.id is properly populated but list.name=null

The returned XML looks like this:



<?xml version="1.0" encoding="UTF-8"?>
<entry xmlns="http://www.w3.org/2005/Atom">
<link href="{some link}" rel="edit"></link>
 <id>{some link}</id>
<title type="text">{some text}</title>
<updated>2011-03-08T21:44:28.155Z</updated>
<author>
<name>{some text}</name>
 </author>
<content type="application/vnd.ctct+xml">16:44:25.992
 <ContactList xmlns="{some namespace}" id="{some text}">
 <OptInDefault>false</OptInDefault>
<Name>birgit test</Name>
<ShortName>birgit test</ShortName>
</ContactList>
</content>
<source>
<id>{some text}</id>
<title type="text">{some text}</title>
<link href="lists"></link>

<link href="lists" rel="self"></link>
<author>
<name>{some text}</name>
</author>
<updated>2011-03-08T21:44:28.155Z</updated>
</source>
</entry>





Any help greatly appreciated!
Thanks, Birgit

Re: [Resteasy-users] Strange warnings when accessing my RESTeasy services

[Michael M. <mmu...@re...>]

Did you manage to resolve your issue?

I know the response is somewhat delayed but the reason for the warnings 
is that you have registered a synchronisation with the transaction using:

javax.transaction.Transaction.registerSynchronization(Synchronisation sync)

and your implementation of sync.afterCompletion() has thrown an exception.

When I say "your implementation" that could also include usages of 
javax.ejb.SessionSynchronisation (does your bean implement that). Do you 
have any logs that could indicate why the Synchronisation implementation 
is throwing the exception?

Mike

> Hi!
>
> First of all let me show the strange warnings I get when I access my API.
>
> 2010-11-18 11:39:26,574 WARN  [arjLoggerI18N ] (http-0.0.0.0-80-1) 
> [com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator_4] 
> TwoPhaseCoordinator.afterCompletion - returned failure for 
> com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple@c851c3
> 2010-11-18 11:39:33,466 WARN  [arjLoggerI18N ] (http-0.0.0.0-80-1) 
> [com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator_4] 
> TwoPhaseCoordinator.afterCompletion - returned failure for 
> com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple@1289d03
> 2010-11-18 11:39:47,005 WARN  [arjLoggerI18N ] (http-0.0.0.0-80-1) 
> [com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator_4] 
> TwoPhaseCoordinator.afterCompletion - returned failure for 
> com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple@1631f82
> 2010-11-18 11:39:49,785 WARN  [arjLoggerI18N ] (http-0.0.0.0-80-1) 
> [com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator_4] 
> TwoPhaseCoordinator.afterCompletion - returned failure for 
> com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple@dd8d64
> 2010-11-18 11:39:51,341 WARN  [arjLoggerI18N ] (http-0.0.0.0-80-1) 
> [com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator_4] 
> TwoPhaseCoordinator.afterCompletion - returned failure for 
> com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple@abbebb
> 2010-11-18 11:39:52,428 WARN  [arjLoggerI18N ] (http-0.0.0.0-80-1) 
> [com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator_4] 
> TwoPhaseCoordinator.afterCompletion - returned failure for 
> com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple@14419ee
> 2010-11-18 11:39:53,296 WARN  [arjLoggerI18N ] (http-0.0.0.0-80-1) 
> [com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator_4] 
> TwoPhaseCoordinator.afterCompletion - returned failure for 
> com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple@339c2f
> 2010-11-18 11:39:54,074 WARN  [arjLoggerI18N ] (http-0.0.0.0-80-1) 
> [com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator_4] 
> TwoPhaseCoordinator.afterCompletion - returned failure for 
> com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple@477d3a
> 2010-11-18 11:39:54,745 WARN  [arjLoggerI18N ] (http-0.0.0.0-80-1) 
> [com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator_4] 
> TwoPhaseCoordinator.afterCompletion - returned failure for 
> com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple@4bbc8b
>
> I get a warning for each http call to my service. Each get, post, put, 
> causes a warning. It seems like some sort of jboss transaction problems.
>
> Now to my environment. I use RESTeasy 2.0.0GA, JBoss AS 5.1GA. My 
> application is an ear, containing two wars and one ejb jar. one of the 
> wars is the entry point for my resteasy services. My resources are 
> modelled as stateless session beans. In the methods of my service, I 
> make according calls to methods of my DAO layers. My DAOs are also 
> stateless session beans. Does anyone have a clue what is going on here?
>
> Best regards. btw RESTeasy is awesome!
>
>
> ------------------------------------------------------------------------------
> Protect Your Site and Customers from Malware Attacks
> Learn about various malware tactics and how to avoid them. Understand
> malware threats, the impact they can have on your business, and how you
> can protect your company and customers by using code signing.
> http://p.sf.net/sfu/oracle-sfdevnl
>
>
> _______________________________________________
> Resteasy-users mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/resteasy-users

[Resteasy-users] Resteasy and Jackson JsonView

[green p. <one...@gm...>]

Hi,

We are working on a JEE project with Resteasy.

We want to use Jackson JsonView to control the information on the wire.
However, in order to do so, we have to instruct the resteasy
serializer/deserializer to use the specific JsonView. Is there an
integration point provided for this purpose? Any examples?

Thank you very much,
GP

[Resteasy-users] Couldn't update http response header in PostProcessInterceptor

[green p. <one...@gm...>]

 Hi,

We want to use Resteasy PostProcessInterceptor to set http response header.

The postProcess() method got invoked (we saw the log). However, we couldn't
set the response header.

We didn't find any API in ServerResponse that allow us to set a header. Then
we tried the following code, it didn't work either.

        ResponseBuilder builder = ServerResponse.fromResponse(response);
        builder.cookie(new NewCookie("lcast", "asdfasdfasdf"));
        builder.header("a", "bbbccd");

Anyone got a working example? This is an urgent issue.

We appreciate your help.

Thank you very much,
gp

[Resteasy-users] empty list is not generated on json

[f c. <fil...@gm...>]

Hi !
i´m using resteasy to generate json to integrate the backend with the ui;

now my problem is that one of the objects has a list; and when the list is
empty the json data is not generated for that data;

example:

@XmlRootElement(name = "CWebAssetsFilters")
@XmlAccessorType(XmlAccessType.FIELD)
@NoJackson
public class CWebAssetsFilterList {

    private List<TWebassetsfilter> cWebAssetsFilters = new
ArrayList<TWebassetsfilter>();

    private long totalrecord;

getter,,,,setter...




generator
    @GET
    @Path("/cWebAssetsFilters/readAssetFilters")
    @Produces("application/json")
    public CWebAssetsFilterList readAssetsFilter(@QueryParam("start") int
start,@QueryParam("limit") int limit){
        return new CWebAssetsFilterList();
    }



this will return only the totalcount attribute on json;
no cWebAssetsFilters attribute is generated;


do i have an annotation to tell that is madattory to generate all attributes
?


best
Filipe

[Resteasy-users] RESTEasy CDI integration

[<gen...@li...>]

Dear RESTeasy users,
I'm interested to learn more about REST-CDI integration.
I've set up a simple front-end with JSF 

 <h:form action="restservice">
 <h:outputText value="Enter your name:" />
 <h:inputText id="username" value="#{user.name}"/> 
 <h:inputText id="password" value="#{user.password}"/>
 <h:commandButton  />
 
 <h:messages/>
</h:form>  

This should consume a service defined in a CDI Bean

@Named
@Stateless
@Path("/")
public class Example {
 
 @Inject User user;
 
. . . . .
 @Path("restservice")
 @POST
 @GET
 public String login() {   
	 return "Logged with " + user.getName() + " " + user.getPassword();
 } 
}

However I can see that JSF simply does not bind the form to the REST service 
("restservice"), I guess the JSF lifecycle  prevents to reach the Web service.
am I choosing the wrong approach to integrate CDI and REST services ? 
Any help would be highly appreciated.
john

Re: [Resteasy-users] test

[Michael M. <mmu...@re...>]

It is but it wasn't immediately obvious what your issue was and I was 
quite busy. Sorry.

Mike

> is this working?
>
>
> ------------------------------------------------------------------------------
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
>
>
> _______________________________________________
> Resteasy-users mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/resteasy-users

[Resteasy-users] test

[f c. <fil...@gm...>]

is this working?