May 2013 - seam-issues - Jboss List Archives

[JBoss JIRA] (JBSEAM-5096) Switch Quartz example to use EJBTimer

by Tomas Remes (JIRA)

Tomas Remes created JBSEAM-5096: ----------------------------------- Summary: Switch Quartz example to use EJBTimer Key: JBSEAM-5096 URL: https://issues.jboss.org/browse/JBSEAM-5096 Project: Seam 2 Issue Type: Task Reporter: Tomas Remes Assignee: Tomas Remes Fix For: 2.3.2.CR1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (JBSEAM-3726) Methods with an "InvocationContext" parameter annotated with "javax.ejb.PostActivate" cause a validation exception in WebSphere v7.0

by Joe Maglio (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-3726?page=com.atlassian.jira.plugi... ] Joe Maglio commented on JBSEAM-3726: ------------------------------------ Hello - Which version should I use to avoid this warning? We are currently using: Seam-Version: 2.1.0.GA and I have tried: Seam-Version: 2.2.1.Final We are upgrading from WAS 6.1.0.35 to 8.5.01. IBM has indicated that this is an application issue rather than a Websphere issue. We are not using EJBs and there does not seem to be any issue running the app. I realize this is an old thread and closed issue, but I have recently come across this, and would like to avoid this warning during deployment. Thanks for your help. com.ibm.wsspi.amm.validate.ValidationException: For method, org.jboss.seam.intercept.SessionBeanInterceptor.prePassivate(Ljavax/interceptor/InvocationContext;)V[com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl@16d3046], parameters were specified, but null was the expected comparison > Methods with an "InvocationContext" parameter annotated with "javax.ejb.PostActivate" cause a validation exception in WebSphere v7.0 > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBSEAM-3726 > URL: https://issues.jboss.org/browse/JBSEAM-3726 > Project: Seam 2 > Issue Type: Bug > Components: Platform interoperability > Affects Versions: 2.1.1.CR2 > Environment: WebSphere v7.0 > Reporter: Denis Forveille > Assignee: Pete Muir > Priority: Critical > Fix For: 2.1.2.CR1 > > Attachments: jbseam-3726.patch, jbseam-3726_2.patch, traceback.txt > > > When starting our app in WebSphere v7.0 with seam v2.1.0.SP1, we receive the exception below > Is it possible that annotation "javax.ejb.PostActivate" is used instead of "org.jboss.seam.annotations.intercept.PostActivate" annotation and that the former does not accept any parameter for the annotated method (At least in WebSphere v7.0) and the latter does... > The method in question is declared as > @PostActivate > public void postActivate(InvocationContext invocation) throws Exception > This method signature is present in classes SessionBeanInterceptor, EntityManagerProxyInterceptor and HibernateSessionProxyInterceptor > Exception: > [18/11/08 16:17:51:537 EST] 0000001a annotations E AnnotativeMetadataManagerImpl merge Caught exception while merging > com.ibm.wsspi.amm.validate.ValidationException: For method, org.jboss.seam.persistence.EntityManagerProxyInterceptor.postActivate(Lorg/jboss/seam/intercept/InvocationContext;)V\[com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl@1b8e1b8e\], parameters were specified, but null was the expected comparison -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5084) seam-gen dependency management with ivy is not updated

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5084?page=com.atlassian.jira.plugi... ] Marek Novotny closed JBSEAM-5084. --------------------------------- Assignee: Marek Novotny Resolution: Done ivy dependency management in seam-gen was removed as useless. > seam-gen dependency management with ivy is not updated > ------------------------------------------------------ > > Key: JBSEAM-5084 > URL: https://issues.jboss.org/browse/JBSEAM-5084 > Project: Seam 2 > Issue Type: Bug > Components: Tools > Affects Versions: 2.3.0.Final > Reporter: Marek Novotny > Assignee: Marek Novotny > Fix For: 2.3.1.CR1 > > > The seam-gen ivy setup is not totally updated and do not use Seam BOM. > Version 2.3.0 of Ivy could manage the dependency management from Seam BOM. > Old behavior of ivy extension is documented here http://in.relation.to/Bloggers/ManagingTheDependenciesOfASeamgenProjectWi... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5091) SeamInterceptor doesn't work on EJB @Schedule methods

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5091?page=com.atlassian.jira.plugi... ] Marek Novotny resolved JBSEAM-5091. ----------------------------------- Resolution: Done fixed by https://github.com/seam2/jboss-seam/commit/dd2515beaaae23f5314d2f1d0da42e... > SeamInterceptor doesn't work on EJB @Schedule methods > ----------------------------------------------------- > > Key: JBSEAM-5091 > URL: https://issues.jboss.org/browse/JBSEAM-5091 > Project: Seam 2 > Issue Type: Bug > Components: EJB3 > Affects Versions: 2.3.0.Final > Reporter: Marek Schmidt > Assignee: Marek Novotny > Fix For: 2.3.1.CR1 > > > Description of problem: > Having a > @Scope(ScopeType.APPLICATION) > @Singleton > @Name("statistics") > public class Statistics > { > @In(create=true) > Foo foo; > > @Schedule(hour="*", minute="*", second="*/10", info="every tenth") > public void generateReport(Timer timer) { > // do stuff with foo > } > } > gets NullPointerException accessing "foo". Seam interceptors doesn't seem to work on time-out methods. The problem seems to be that the SessionBeanInterceptor doesn't implement the @AroundTimeout method. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5093) Seam produces malformed partial response on ViewExpiredException with Ajax

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5093?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBSEAM-5093: ------------------------------------------------- Marek Novotny <mnovotny(a)redhat.com> changed the Status of [bug 952571|https://bugzilla.redhat.com/show_bug.cgi?id=952571] from ASSIGNED to MODIFIED > Seam produces malformed partial response on ViewExpiredException with Ajax > -------------------------------------------------------------------------- > > Key: JBSEAM-5093 > URL: https://issues.jboss.org/browse/JBSEAM-5093 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.3.0.Final > Environment: Seam 2.3.1-SNAPSHOT 2013-05-02 082f3b3459893b1c4200b7bd8ce99556f87f0dd0 > Reporter: Marek Schmidt > Assignee: Marek Novotny > Fix For: 2.3.1.CR1 > > > When ViewExpiredException occurs in an Ajax request, the response is malformed, containing duplicate partial-response element. This results in the response not being parsed (and in this case, redirect not being followed). > {noformat} > <?xml version='1.0' encoding='UTF-8'?> > <partial-response><redirect url="/seam-booking/home.seam?cid=22"></redirect></partial-response><?xml version="1.0" encoding="UTF-8"?> > <partial-response><redirect url="/seam-booking/home.seam?cid=22"/></partial-response> > {noformat} > This seems to happen, because there are two rules for the redirection in pages.xml: > - main.xhtml has login required, handled in Pages.redirectToLoginView() > <page view-id="/main.xhtml" login-required="true"> > - exception handler for ViewExpiredException, handled in ExceptionFilter > <exception class="javax.faces.application.ViewExpiredException"> > <redirect view-id="/home.xhtml"> > ... > </exception> > None of the Seam's components involved (ExceptionFilter, Pages, Exceptions, RedirectHandler, MockExternalContext, ... ?) checks whether the response has already been written and the redirect partial response gets written twice. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5093) Seam produces malformed partial response on ViewExpiredException with Ajax

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5093?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBSEAM-5093: ------------------------------------------------- Marek Novotny <mnovotny(a)redhat.com> made a comment on [bug 952571|https://bugzilla.redhat.com/show_bug.cgi?id=952571] wrong bz # in commit's comment references but it is fixed by https://source.jboss.org/changelog/Seam?cs=15494 > Seam produces malformed partial response on ViewExpiredException with Ajax > -------------------------------------------------------------------------- > > Key: JBSEAM-5093 > URL: https://issues.jboss.org/browse/JBSEAM-5093 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.3.0.Final > Environment: Seam 2.3.1-SNAPSHOT 2013-05-02 082f3b3459893b1c4200b7bd8ce99556f87f0dd0 > Reporter: Marek Schmidt > Assignee: Marek Novotny > Fix For: 2.3.1.CR1 > > > When ViewExpiredException occurs in an Ajax request, the response is malformed, containing duplicate partial-response element. This results in the response not being parsed (and in this case, redirect not being followed). > {noformat} > <?xml version='1.0' encoding='UTF-8'?> > <partial-response><redirect url="/seam-booking/home.seam?cid=22"></redirect></partial-response><?xml version="1.0" encoding="UTF-8"?> > <partial-response><redirect url="/seam-booking/home.seam?cid=22"/></partial-response> > {noformat} > This seems to happen, because there are two rules for the redirection in pages.xml: > - main.xhtml has login required, handled in Pages.redirectToLoginView() > <page view-id="/main.xhtml" login-required="true"> > - exception handler for ViewExpiredException, handled in ExceptionFilter > <exception class="javax.faces.application.ViewExpiredException"> > <redirect view-id="/home.xhtml"> > ... > </exception> > None of the Seam's components involved (ExceptionFilter, Pages, Exceptions, RedirectHandler, MockExternalContext, ... ?) checks whether the response has already been written and the redirect partial response gets written twice. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5083) SeamViewHandler adds conversation id even if conversation is not long running

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5083?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBSEAM-5083: ------------------------------------------------- Marek Novotny <mnovotny(a)redhat.com> made a comment on [bug 921660|https://bugzilla.redhat.com/show_bug.cgi?id=921660] backported from upstream as https://source.jboss.org/changelog/Seam?cs=15491 > SeamViewHandler adds conversation id even if conversation is not long running > ----------------------------------------------------------------------------- > > Key: JBSEAM-5083 > URL: https://issues.jboss.org/browse/JBSEAM-5083 > Project: Seam 2 > Issue Type: Bug > Components: JSF Integration > Reporter: Marek Schmidt > Assignee: Marek Novotny > Fix For: 2.3.1.CR1 > > > Seam adds a conversation id even if the conversation is not long running into URL. > Note that the way how seam propagates conversation id has changed since Seam 2.2, so that now it uses the cid= in places where Seam2.2 would use the page context, so in some cases the "cid" parameter would be correctly present in a Seam2.3 application even if it was not present in the same Seam 2.2 application. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5083) SeamViewHandler adds conversation id even if conversation is not long running

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5083?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBSEAM-5083: ------------------------------------------------- Marek Novotny <mnovotny(a)redhat.com> changed the Status of [bug 921660|https://bugzilla.redhat.com/show_bug.cgi?id=921660] from ASSIGNED to MODIFIED > SeamViewHandler adds conversation id even if conversation is not long running > ----------------------------------------------------------------------------- > > Key: JBSEAM-5083 > URL: https://issues.jboss.org/browse/JBSEAM-5083 > Project: Seam 2 > Issue Type: Bug > Components: JSF Integration > Reporter: Marek Schmidt > Assignee: Marek Novotny > Fix For: 2.3.1.CR1 > > > Seam adds a conversation id even if the conversation is not long running into URL. > Note that the way how seam propagates conversation id has changed since Seam 2.2, so that now it uses the cid= in places where Seam2.2 would use the page context, so in some cases the "cid" parameter would be correctly present in a Seam2.3 application even if it was not present in the same Seam 2.2 application. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5095) ResourceRequestEnvironment should use a proper servlet context when available

by Marek Schmidt (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5095?page=com.atlassian.jira.plugi... ] Marek Schmidt updated JBSEAM-5095: ---------------------------------- Fix Version/s: 2.3.2.CR1 > ResourceRequestEnvironment should use a proper servlet context when available > ----------------------------------------------------------------------------- > > Key: JBSEAM-5095 > URL: https://issues.jboss.org/browse/JBSEAM-5095 > Project: Seam 2 > Issue Type: Bug > Affects Versions: 2.3.0.Final > Reporter: Marek Schmidt > Assignee: Marek Schmidt > Fix For: 2.3.2.CR1 > > > ResourceRequestEnvironment uses MockServletContext, which doesn't work incontainer on AS7. > ResourceRequestEnvironment should use proper servlet context if available in JUnitSeamTest -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5095) ResourceRequestEnvironment should use a proper servlet context when available

by Marek Schmidt (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5095?page=com.atlassian.jira.plugi... ] Marek Schmidt updated JBSEAM-5095: ---------------------------------- Affects Version/s: 2.3.0.Final > ResourceRequestEnvironment should use a proper servlet context when available > ----------------------------------------------------------------------------- > > Key: JBSEAM-5095 > URL: https://issues.jboss.org/browse/JBSEAM-5095 > Project: Seam 2 > Issue Type: Bug > Affects Versions: 2.3.0.Final > Reporter: Marek Schmidt > Assignee: Marek Schmidt > > ResourceRequestEnvironment uses MockServletContext, which doesn't work incontainer on AS7. > ResourceRequestEnvironment should use proper servlet context if available in JUnitSeamTest -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues May 2013