[JBoss JIRA] (GTNPORTAL-3255) Quickstarts: Modify GAV to use org.jboss.quickstarts.jpp
by Sande Gilda (JIRA)
Sande Gilda created GTNPORTAL-3255:
--------------------------------------
Summary: Quickstarts: Modify GAV to use org.jboss.quickstarts.jpp
Key: GTNPORTAL-3255
URL: https://issues.jboss.org/browse/GTNPORTAL-3255
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Sande Gilda
As part of the BOM, Stacks, Archetypes, and Quickstarts reorganization process, we are standardizing on the quickstarts GAV to use 'org.jboss.quickstarts.<product-name>.
Could you change the Gatein Portal quickstarts GAV from 'org.gatein.portal.quickstarts' to 'org.jboss.quickstarts.jpp'?
This can be done at a time that works best with your release schedule.
--
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
10 years, 8 months
[JBoss JIRA] (GTNPORTAL-3230) 508 compliancy changes doesn't properly 'hide' elements for rtl languages
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3230?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration commented on GTNPORTAL-3230:
----------------------------------------------------
Honza Fnukal <hfnukal(a)redhat.com> changed the Status of [bug 990161|https://bugzilla.redhat.com/show_bug.cgi?id=990161] from MODIFIED to ON_QA
> 508 compliancy changes doesn't properly 'hide' elements for rtl languages
> -------------------------------------------------------------------------
>
> Key: GTNPORTAL-3230
> URL: https://issues.jboss.org/browse/GTNPORTAL-3230
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Mobile, User Interface
> Reporter: Matt Wringe
> Assignee: Matt Wringe
> Fix For: 3.6.3.Final
>
>
> The 508 changes to "hide" content off to a negative left position is incorrect when handling rtl languages. For rtl languages it should be placed at a negative right position instead.
> With older android browsers there is an issue where it expect a _positive_ right position for this hack to work. A work around will have to be done to deal with this situation.
> Without these changes it causes the browser to render the page as it if is extremely wide(10 000px). Some browsers cannot handle this and it causes strange behaviours such as links no longer functioning.
--
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
10 years, 8 months
[JBoss JIRA] (GTNPORTAL-3243) Exceptions are swallowed in PicketLinkIDMOrganizationServiceImpl flush and endRequest
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3243?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration commented on GTNPORTAL-3243:
----------------------------------------------------
Honza Fnukal <hfnukal(a)redhat.com> changed the Status of [bug 998885|https://bugzilla.redhat.com/show_bug.cgi?id=998885] from MODIFIED to ON_QA
> Exceptions are swallowed in PicketLinkIDMOrganizationServiceImpl flush and endRequest
> -------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-3243
> URL: https://issues.jboss.org/browse/GTNPORTAL-3243
> Project: GateIn Portal
> Issue Type: Bug
> Components: Identity integration
> Affects Versions: 3.6.0.Final
> Reporter: Martin Weiler
> Assignee: Marek Posolda
> Fix For: 3.6.3.Final
>
>
> IDM operations are invoked from a WS facade in our environment, and not from the GUI. Therefore, we have overridden PicketLinkIDMOrganizationServiceImpl.recoverFromIDMError to just let any errors bubble up and let the upper layer handle it, instead of rolling back + restarting the transaction.
> But here's the place the exception handling is not working as expected. The issue is in PicketLinkIDMOrganizationServiceImpl.flush():
> {code}
> public void flush() {
> try {
> if (configuration.isUseJTA()) {
> if (traceLoggingEnabled) {
> log.trace("Flushing UserTransaction in method flush");
> }
> // Complete restart of JTA transaction don't have good performance. So we will only sync identitySession (same
> // as for non-jta environment)
> // finishJTATransaction();
> // beginJTATransaction();
> if (jtaTransactionLifecycleService.getUserTransaction().getStatus() == Status.STATUS_ACTIVE) {
> idmService_.getIdentitySession().save();
> }
> } else {
> try {
> if (idmService_.getIdentitySession().getTransaction().isActive()) {
> 166: idmService_.getIdentitySession().save();
> }
> } catch (Exception e) {
> log.error(e.getMessage(), e);
> 170: recoverFromIDMError(e);
> }
> }
> 174: } catch (Exception e) {
> 175: log.error(e.getMessage(), e);
> }
> }
> {code}
> Let's assume there is an exception at session.save() in line 166. This exception is then handled by the recoverFromIDMError method in line 170. In our environment, this method is overridden and throws an Exception.
> But the initial goal of overriding this method, which was to have this exception propagated to the caller, is not reached here, as there is an outer try..catch block in the PicketLinkIDMOrganizationServiceImpl.flush() method which just logs the error.
> The outer try..catch block should be removed in flush() and endRequest().
--
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
10 years, 8 months