seam-issues September 2015

seam-issues@lists.jboss.org

1 participants
14 discussions

[JBoss JIRA] (JBSEAM-4809) seam-resteasy integration conflicts with resteasy deployer on JBoss AS 6

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-4809?page=com.atlassian.jira.plugi... ] Jozef Hartinger reassigned JBSEAM-4809: --------------------------------------- Assignee: (was: Jozef Hartinger) > seam-resteasy integration conflicts with resteasy deployer on JBoss AS 6 > ------------------------------------------------------------------------ > > Key: JBSEAM-4809 > URL: https://issues.jboss.org/browse/JBSEAM-4809 > Project: Seam 2 > Issue Type: Bug > Components: WS > Affects Versions: 2.2.2.Final > Reporter: Jozef Hartinger > Fix For: The future > > > As a result of auto-scanning performed by the resteasy-deployer, resources not intended to be registered are registered within RESTEasy which causes redirect loops breaking the entire application. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SOLDER-258) Test Seam Servlet in an EAR with multiple web apps

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/SOLDER-258?page=com.atlassian.jira.plugin... ] Jozef Hartinger reassigned SOLDER-258: -------------------------------------- Assignee: (was: Jozef Hartinger) > Test Seam Servlet in an EAR with multiple web apps > -------------------------------------------------- > > Key: SOLDER-258 > URL: https://issues.jboss.org/browse/SOLDER-258 > Project: Solder > Issue Type: Feature Request > Components: Compliance, Servlet, Test Suite > Reporter: Dan Allen > Fix For: Future > > > We want to verify that we haven't broken any assumptions, such as whether the correct ServletContext is injected. Should be relatively easy to solve with Arquillian. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-3938) Seam's Resteasy implementation does not support tagged interfaces, nor classes that implement them.

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-3938?page=com.atlassian.jira.plugi... ] Jozef Hartinger reassigned JBSEAM-3938: --------------------------------------- Assignee: (was: Jozef Hartinger) > Seam's Resteasy implementation does not support tagged interfaces, nor classes that implement them. > --------------------------------------------------------------------------------------------------- > > Key: JBSEAM-3938 > URL: https://issues.jboss.org/browse/JBSEAM-3938 > Project: Seam 2 > Issue Type: Bug > Components: WS > Affects Versions: 2.1.1.GA > Environment: SEAM 2.1.1.GA with seam-resteasy patch described in https://jira.jboss.org/jira/browse/JBSEAM-3449, and RestEasy 1.0.1.GA. > Reporter: John Sublette > Priority: Minor > Labels: RestEasy > > Seam's Resteasy implementation does not support tagged interfaces, nor classes that implement them as described in RestEasy's documentation (section 28.2 - Sharing an interface...). An interface with tagged @Path throws an exception when it is registered - because an interface doesn't have a constructor. > See org.jboss.resteasy.plugins.server.servlet.ResteasyBootstrap Line 112 through 138 for how RestEasy handles this by default - (using Scannotation) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SEAMREST-6) ExceptionMapper classes should be moved to api to support only relying on api jar at compile time

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/SEAMREST-6?page=com.atlassian.jira.plugin... ] Jozef Hartinger reassigned SEAMREST-6: -------------------------------------- Assignee: (was: Jozef Hartinger) > ExceptionMapper classes should be moved to api to support only relying on api jar at compile time > ------------------------------------------------------------------------------------------------- > > Key: SEAMREST-6 > URL: https://issues.jboss.org/browse/SEAMREST-6 > Project: Seam REST > Issue Type: Bug > Components: Client > Affects Versions: 3.0.0.Alpha1 > Reporter: Jason Porter > Fix For: Future > > > Currently SeamExceptionMapper and ValidationExceptionMapper are in the impl class. Unless we provide our own Application subclass (which should also be in the api jar) users can subclass and add to our classes they must include the impl jar as a runtime dependency. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

← Newer
1
2
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues September 2015