[ https://jira.jboss.org/jira/browse/JBSEAM-3449?page=com.atlassian.jira.pl... ] Scott Olcott updated JBSEAM-3449: --------------------------------- Description: The latest beta is beta-8 (was: The latest beta os beta-8) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3449?page=com.atlassian.jira.pl... ] Scott Olcott updated JBSEAM-3449: --------------------------------- Component/s: WS -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3449?page=com.atlassian.jira.pl... ] ajordens commented on JBSEAM-3449: ---------------------------------- Any idea on the future of this? I'm actively using both RESTeasy and Seam 2.1.0.SP1, it sure would be nice to realize some of the newer JAX-RS items. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3449?page=com.atlassian.jira.pl... ] ajordens commented on JBSEAM-3449: ---------------------------------- I didn't want to run with the snapshot, so what I ended up doing was re-implementing the seam-resteasy integration in the project with the patch applied. It's only 4 files and seems to work quite nicely. I'm trusting that the seam developers will get a suitable copy of the patch integrated and I can remove the custom seam-resteasy component. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3449?page=com.atlassian.jira.pl... ] Scott Olcott commented on JBSEAM-3449: -------------------------------------- It seems like injection using javax.ws.rs.core.Context is not working with this patch. For example in the following uriInfo always seems to be null: @javax.ws.rs.core.Context javax.ws.rs.core.UriInfo uriInfo -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3449?page=com.atlassian.jira.pl... ] Jeremy Norris commented on JBSEAM-3449: --------------------------------------- Xiaofeng, thanks for your note. You've saved me a couple days of digging since I have this same problem. With JBoss 2.1.1.CR1 and a default resteasy (beta5), this bug exists - nevername the patch introducing it. Perhaps a new bug should be logged to fix this @Startup dependency? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3449?page=com.atlassian.jira.pl... ] Jozef Hartinger updated JBSEAM-3449: ------------------------------------ Fix Version/s: 2.1.2.GA -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3449?page=com.atlassian.jira.pl... ] Work on JBSEAM-3449 started by Jozef Hartinger. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3449?page=com.atlassian.jira.pl... ] John Sublette commented on JBSEAM-3449: --------------------------------------- After doing that patch, I noticed several additional bugs. For the Resteasy client interface, you can share an interface and implement it in a class without the tags and it should find it. The code as it existed with my patch would break if it found tags on interfaces, and wouldn't register tagless classes that implement tagged interfaces. The resteasy bootstrapper uses Scannotation to search and find them, and that worked for me, though I cludged it in a bit poorly. Also, I had difficulty trying to get two web-applications to use Seam+Resteasy, only the last web-application worked. I had to make a ResteasyProviderFactory in the mold of ThreadLocalResteasyProviderFactory that used Component to retrieve the right Application scoped ResteasyDispatcher, where I stored the providerFactory that should be used in that application. Then I had to change the ResteasyDispatcher.onStartup() to register my factory with the Resteasy library, and to provide access to the stored instance of ResteasyProviderFactory. In order to do this, though I had to replicate all seam and resteasy libraries in each application's WEB-INF/lib directory. I couldn't seem to get things to go into Tomcat's common library directory and still work - it would get the last loaded's context. I probably have to understand Seam's library structure better. e.g.: **ResteasyDispatcher** .... @Create public void onStartup() { log.debug("assigning registered RESTEasy resources and providers"); providerFactory = new ResteasyProviderFactory(); ResteasyProviderFactory providerFactory = new SeamApplicationLocalResteasyProviderFactory(); ResteasyProviderFactory.setInstance(providerFactory); // This is really necessary .... public ResteasyProviderFactory getProviderFactory() { return providerFactory; } **SeamApplicationLocalResteasyProviderFactory** public class SeamApplicationLocalResteasyProviderFactory extends ResteasyProviderFactory public ResteasyProviderFactory getDelegate() { ResteasyDispatcher dispatcher = (ResteasyDispatcher)Component.getInstance(ResteasyDispatcher.class, ScopeType.APPLICATION); if (dispatcher == null) return defaultFactory; return dispatcher.getProviderFactory(); } ... ...(Everything else is pretty much identical to ThreadLocalResteasyProviderFactory) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3449?page=com.atlassian.jira.pl... ] Balazs Pataki commented on JBSEAM-3449: --------------------------------------- Hi, Are there any plans for adding asynchronous HTTP processing support for next edition of Seam+RESTeasy? http://www.jboss.org/file-access/default/members/resteasy/freezone/docs/1... For plain RESTeasy oen has to use a special servlet: org.jboss.resteasy.plugins.server.servlet.Tomcat6CometDispatcherServlet. In Seam it may be a little bit more tricky, but I'm not sure. Any hints about this would be highly welcome. By the way, are there any dates for the 2.1.2 RC release including updated RESTeasy support? Thanks, --- balazs -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3449?page=com.atlassian.jira.pl... ] Jozef Hartinger commented on JBSEAM-3449: ----------------------------------------- Balazs, thanks for your comments regarding asynchronous HTTP. Please open a separate issue for this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3449?page=com.atlassian.jira.pl... ] Jozef Hartinger closed JBSEAM-3449. ----------------------------------- Fix Version/s: 2.1.2.CR1 (was: 2.1.2.GA) Resolution: Done -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3449?page=com.atlassian.jira.pl... ] Christian Bauer updated JBSEAM-3449: ------------------------------------ Summary: Upgrade to latest RESTEasy (was: Upgrade to latest RestEasy beta) Fix Version/s: 2.1.2.CR2 (was: 2.1.2.CR1) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3449?page=com.atlassian.jira.pl... ] Jozef Hartinger reopened JBSEAM-3449: ------------------------------------- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira