[JBoss JIRA] (GTNPORTAL-3110) IDM DAO classes are only catching IdentityExceptions
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3110?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration commented on GTNPORTAL-3110:
----------------------------------------------------
Tomas Kyjovsky <tkyjovsk(a)redhat.com> changed the Status of [bug 973039|https://bugzilla.redhat.com/show_bug.cgi?id=973039] from ON_QA to VERIFIED
> IDM DAO classes are only catching IdentityExceptions
> ----------------------------------------------------
>
> Key: GTNPORTAL-3110
> URL: https://issues.jboss.org/browse/GTNPORTAL-3110
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Identity integration
> Affects Versions: 3.6.0.Beta02
> Reporter: Martin Weiler
> Assignee: Marek Posolda
> Fix For: 3.6.0.Final
>
>
> In some IDM DAO classes, such as GroupDAOImpl, MembershipDAOImpl and UserProfileDAOImpl all IDM calls are wrapped with try..catch(Exception e) blocks, which ensures that not only IdentityException, but also Hibernate exceptions are caught and recovered with rollback().
> But in UserDAOImpl only "IdentityException e" instances are caught. So HibernateException are not handled, which can result in transaction errors. Additionally, in MembershipTypeDAOImpl the IDM calls are not wrapped with any catch blocks, which also needs to be fixed.
--
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, 4 months
[JBoss JIRA] (GTNPORTAL-3110) IDM DAO classes are only catching IdentityExceptions
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3110?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration commented on GTNPORTAL-3110:
----------------------------------------------------
Tomas Kyjovsky <tkyjovsk(a)redhat.com> made a comment on [bug 973039|https://bugzilla.redhat.com/show_bug.cgi?id=973039]
Verified in 6.1.0.ER02.
> IDM DAO classes are only catching IdentityExceptions
> ----------------------------------------------------
>
> Key: GTNPORTAL-3110
> URL: https://issues.jboss.org/browse/GTNPORTAL-3110
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Identity integration
> Affects Versions: 3.6.0.Beta02
> Reporter: Martin Weiler
> Assignee: Marek Posolda
> Fix For: 3.6.0.Final
>
>
> In some IDM DAO classes, such as GroupDAOImpl, MembershipDAOImpl and UserProfileDAOImpl all IDM calls are wrapped with try..catch(Exception e) blocks, which ensures that not only IdentityException, but also Hibernate exceptions are caught and recovered with rollback().
> But in UserDAOImpl only "IdentityException e" instances are caught. So HibernateException are not handled, which can result in transaction errors. Additionally, in MembershipTypeDAOImpl the IDM calls are not wrapped with any catch blocks, which also needs to be fixed.
--
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, 4 months
[JBoss JIRA] (GTNPORTAL-3236) Wrong content type on file download
by Ruslan Baskou (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3236?page=com.atlassian.jira.pl... ]
Ruslan Baskou updated GTNPORTAL-3236:
-------------------------------------
Description: And response implementation org.gatein.pc.portlet.impl.jsr168.api.ActionResponseImpl (for JSF context FacesContext.getCurrentInstance().getExternalContext().getResponse()) does not implements javax.portlet.ResourceResponse interface. (was: And response implementation org.gatein.pc.portlet.impl.jsr168.api.ActionResponseImpl (for JSF context FacesContext.getCurrentInstance().getExternalContext().getResponse()) does not implement javax.portlet.ResourceResponse interface.)
> Wrong content type on file download
> -----------------------------------
>
> Key: GTNPORTAL-3236
> URL: https://issues.jboss.org/browse/GTNPORTAL-3236
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Java API
> Affects Versions: 3.6.0.Final
> Reporter: Ruslan Baskou
> Labels: eap, jsf
> Attachments: test-ear.zip
>
>
> And response implementation org.gatein.pc.portlet.impl.jsr168.api.ActionResponseImpl (for JSF context FacesContext.getCurrentInstance().getExternalContext().getResponse()) does not implements javax.portlet.ResourceResponse interface.
--
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, 5 months
[JBoss JIRA] (GTNPORTAL-3236) Wrong content type on file download
by Ruslan Baskou (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3236?page=com.atlassian.jira.pl... ]
Ruslan Baskou updated GTNPORTAL-3236:
-------------------------------------
Description: And response implementation org.gatein.pc.portlet.impl.jsr168.api.ActionResponseImpl (for JSF context FacesContext.getCurrentInstance().getExternalContext().getResponse()) does not implement javax.portlet.ResourceResponse interface.
> Wrong content type on file download
> -----------------------------------
>
> Key: GTNPORTAL-3236
> URL: https://issues.jboss.org/browse/GTNPORTAL-3236
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Java API
> Affects Versions: 3.6.0.Final
> Reporter: Ruslan Baskou
> Labels: eap, jsf
> Attachments: test-ear.zip
>
>
> And response implementation org.gatein.pc.portlet.impl.jsr168.api.ActionResponseImpl (for JSF context FacesContext.getCurrentInstance().getExternalContext().getResponse()) does not implement javax.portlet.ResourceResponse interface.
--
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, 5 months
[JBoss JIRA] (GTNPORTAL-3194) TestPlainCookieTokenService sometimes fails randomly
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3194?page=com.atlassian.jira.pl... ]
Trong Tran resolved GTNPORTAL-3194.
-----------------------------------
Resolution: Done
> TestPlainCookieTokenService sometimes fails randomly
> ----------------------------------------------------
>
> Key: GTNPORTAL-3194
> URL: https://issues.jboss.org/browse/GTNPORTAL-3194
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.6.0.Final
> Reporter: Trong Tran
> Assignee: Hai Nguyen
> Priority: Optional
> Labels: backlogs, done
> Fix For: 3.7.0.Final
>
> Original Estimate: 4 hours
> Time Spent: 2 hours
> Remaining Estimate: 2 hours
>
> 1 tests failed.
> REGRESSION: org.exoplatform.web.security.TestPlainCookieTokenService.testCleanExpiredTokens
> Error Message:
> expected:<0> but was:<1>
> Stack Trace:
> junit.framework.AssertionFailedError: expected:<0> but was:<1>
> at junit.framework.Assert.fail(Assert.java:50)
> at junit.framework.Assert.failNotEquals(Assert.java:287)
> at junit.framework.Assert.assertEquals(Assert.java:67)
> at junit.framework.Assert.assertEquals(Assert.java:134)
> at junit.framework.Assert.assertEquals(Assert.java:140)
> at org.exoplatform.web.security.AbstractCookieTokenServiceTest.testCleanExpiredTokens(AbstractCookieTokenServiceTest.java:89)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at junit.framework.TestCase.runTest(TestCase.java:168)
> at junit.framework.TestCase.runBare(TestCase.java:134)
> at org.exoplatform.component.test.AbstractGateInTest.runBare(AbstractGateInTest.java:81)
> at junit.framework.TestResult$1.protect(TestResult.java:110)
> at junit.framework.TestResult.runProtected(TestResult.java:128)
> at junit.framework.TestResult.run(TestResult.java:113)
> at junit.framework.TestCase.run(TestCase.java:124)
> at junit.framework.TestSuite.runTest(TestSuite.java:243)
> at junit.framework.TestSuite.run(TestSuite.java:238)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
--
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, 5 months