AW: Dropdown window bug

2016-08-17 Thread Rade, Joerg / Kuehne + Nagel / Ham GI-DP 
Hi Hector,

according to [1] the state of the component (as of 2015-12-13) didn’t justify 
the effort.

-j

[1] https://issues.apache.org/jira/browse/ISIS-1225
Von: Hector Fabio Meza [mailto:hector.m...@smartools.com.co]
Gesendet: Donnerstag, 18. August 2016 03:45
An: Users
Betreff: Dropdown window bug


Hi,

I found this conversation about the dropdown window bug appearing on the left 
side of the screen some times: 
http://users.isis.apache.narkive.com/qco5fzuW/dropdown-window-bug-in-1-10-0

I do agree it's more annoying than critical, but just wanted to know if there's 
a timeline for the switch to 7.2.0, and/or if switching to the new selectize 
component is still on the plan.

Screenshot of the issue added for context: 
http://picpaste.com/pics/desplazListaEjercicioAE-VkppCaQA.1471484649.png

Thank you.
--
Hector Fabio Meza
R&D Lead smartools
(57) 300 2254455
Skype: hectorf.meza
www.smartools.com.co

[cid:image001.jpg@01D1F92E.7DF2C8D0]

Kühne + Nagel (AG & Co.) KG
Rechtsform: Kommanditgesellschaft, Bremen HRA 21928, USt-IdNr.: DE 812773878.
Geschäftsleitung Kühne + Nagel (AG & Co.) KG: Yngve Ruud (Vors.), Martin 
Brinkmann, Matthias Heimbach, Jan-Hendrik Köstergarten, Nicholas Minde, Michael 
Nebel, Lars Wedel.
Persönlich haftende Gesellschafterin: Kühne & Nagel A.G., Rechtsform: 
Aktiengesellschaft nach luxemburgischem Recht, HR-Nr.: B 18745, 
Geschäftsführendes Verwaltungsratsmitglied: Karl Gernandt.
Geschäftsleitung Region Westeuropa: Yngve Ruud (Vors.), Diederick de Vroet, 
Dominic Edmonds, Thierry Held, Uwe Hött, Richard Huhn, Björn Johansson, Holger 
Ketz, Jan Kunze.

Wir arbeiten ausschließlich auf Grundlage der Allgemeinen Deutschen 
Spediteurbedingungen 2016 (ADSp 2016). Die ADSp 2016 beschränken in Ziffer 23 
die gesetzliche Haftung für Güterschäden in Höhe von 8,33 SZR/kg je Schadenfall 
bzw. je Schadenereignis auf 1 Million bzw. 2 Millionen Euro oder 2 SZR/kg, je 
nachdem, welcher Betrag höher ist, und bei multimodalen Transporten unter 
Einschluss einer Seebeförderung generell auf 2 SZR/kg. Den vollständigen Text 
der ADSp 2016 übersenden wir Ihnen gerne auf Anfrage und können Sie auch unter 
http://www.kuehne-nagel.com einsehen.

Dropdown window bug

2016-08-17 Thread Hector Fabio Meza 
 

Hi, 

I found this conversation about the dropdown window bug appearing on the
left side of the screen some times:
http://users.isis.apache.narkive.com/qco5fzuW/dropdown-window-bug-in-1-10-0
[1] 

I do agree it's more annoying than critical, but just wanted to know if
there's a timeline for the switch to 7.2.0, and/or if switching to the
new selectize component is still on the plan. 

Screenshot of the issue added for context:
http://picpaste.com/pics/desplazListaEjercicioAE-VkppCaQA.1471484649.png


Thank you. 
-- 

Hector Fabio Meza

R&D LEAD SMARTOOLS 
(57) 300 2254455 [2] 
Skype: hectorf.meza 
www.smartools.com.co [3] 

 

Links:
--
[1]
http://users.isis.apache.narkive.com/qco5fzuW/dropdown-window-bug-in-1-10-0
[2] tel:%2857%29%20300%206815404
[3] http://www.smartools.com.co/

Fwd: N+1 problem in restful object viewer

2016-08-17 Thread José Alejandro Manaure Martinez 
Hi guys
I have a similar problem exposed by Paul. Anyone have an answer to this?

-- Forwarded message --
From: Paul Escobar 
Date: 2016-08-11 15:58 GMT-05:00
Subject: N+1 problem in restful object viewer
To: users@isis.apache.org


Hi Everyone,

I have a N+1 query problem using a method in a Domain Service. The method
(invoked from postman):

*public List listarSolicitudesTramite(final
@ParameterLayout(named="Tramite") String tramite) {*

* PersistenceManager persistenceManager =
isisJdoSupport.getJdoPersistenceManager();*
* persistenceManager.getFetchPlan().addGroup("sucursales");*
* final Query query = persistenceManager.newQuery(Solicitud.class);*
* query.setFilter( inTramites( tramite ) );*
* query.setOrdering("fechaCierre DESC");*
* List solicitudesFiltradas = (List) query.execute();*
* return solicitudesFiltradas;*
* }*


The Solicitud Class:

*@FetchGroup(name="sucursales", members={@Persistent(name="sucursal")})*
*@DatastoreIdentity(strategy=IdGeneratorStrategy.IDENTITY,
column="idSucursal")*
*public class Solicitud implements  Comparable {*
*.*
*.*
*.*

* private Sucursal sucursal;*
* private NivelEscalamiento nivelEscalamiento;*
* private Compania compania;*
* private Canal canal;*
*...*
*}*

The line: List solicitudesFiltradas = (List)
query.execute(); execute this query:

*SELECT *
*DISTINCT 'domainapp.dom.mesaAyudaPrestadores.Solicitud' AS NUCLEUS_TYPE,*
*A0.correoContacto,*
*A0.descripcion,*
*A0.extension,*
*A0.fechaCierre,*
*A0.fechaCreacion,*
*A0.fechaInicioCreacion,*
*A0.nombreBeneficiario,*
*A0.nombreSolicitante,*
*A0.numDocBeneficiario,*
*A0.numDocSolicitante,*
*C0.descSucursal,*
*C0.idSucursal,*
*A0.telefonoContacto,*
*A0.usuario,*
*A0.usuarioAsignado*
*,A0.idSolicitud,*
*A0.fechaCierre AS NUCORDER0 *
*FROM TBL_SOLICITUD A0 *
*LEFT OUTER JOIN TBL_SUCURSAL B0 ON A0.sucursal_idSucursal_OID =
B0.idSucursal *
*LEFT OUTER JOIN TBL_SUCURSAL C0 ON A0.sucursal_idSucursal_OID =
C0.idSucursal *
*WHERE *
*B0.descSucursal = 'Principal Antioquia' ORDER BY NUCORDER0 DESC*

It is fine!, because I need just Solicitud data plus Sucursal data (just
this one related entity, not the other relationships), but after method
return this other queries are run to fill the another relationships (N+1
problem):


*SELECT B0.descNivel,B0.idNivelEscalamiento FROM TBL_SOLICITUD A0 LEFT
OUTER JOIN TBL_NIVEL_ESCALAMIENTO B0 ON
A0.nivelEscalamiento_idNivelEscalamiento_OID = B0.idNivelEscalamiento WHERE
A0.idSolicitud = <1>*


*SELECT B0.descCanal,B0.idCanal FROM TBL_SOLICITUD A0 LEFT OUTER JOIN
TBL_CANAL B0 ON A0.canal_idCanal_OID = B0.idCanal WHERE A0.idSolicitud =
<1>*

*SELECT B0.descCompania,B0.idCompania FROM TBL_SOLICITUD A0 LEFT OUTER JOIN
TBL_COMPANIA B0 ON A0.compania_idCompania_OID = B0.idCompania WHERE*
* A0.idSolicitud = <1>*


How can I avoid this N+1 problem? I thought that using FetchPlan and Groups
was enough to do it.


PD: isis.viewer.restfulobjects.honorUiHints is false and no
x-ro-follow-links query parameter is used.


Thanks,


--
Paul Escobar Mossos
skype: paulescom
telefono: +57 1 3006815404



-- 
[image: Logo]

José Alejandro Manaure
*Project Manager*
Tel: (57) 1 703 17 77
Cel: (57) 312 5476188
E-mail: jose.mana...@ticxar.com
Calle 93 # 19b - 66 Ofc 202
Bogotá D.C., Colombia
www.ticxar.com
  [image: facebook]
 [image:
twitter]  [image: linkedIn]

Re: Apache ISIS - Shiro - CAS Authentication

2016-08-17 Thread Martin Grigorov 
Hi,

On Tue, Aug 16, 2016 at 10:16 PM, David Tildesley <
davo...@yahoo.co.nz.invalid> wrote:

> Hi Uma,
> Just an idea: you could extend  org.apache.isis.viewer.wicket.
> viewer.integration.wicket.WebRequestCycleForIsis
> 1. Check for a Wicket Session: org.apache.wicket.protocol.
> http.WebSession.get();
>

Small correction.
Session#get() acts as "get or create".
Use Session#exists() to check whether there is a session or not.


> 2. If none, assume the "container" has authenticated the user so then
> check HttpServletRequest for a remote user (getRemoteUser();)
> 3. If remote user exists then set the user in wicket:
> org.apache.wicket.authroles.authentication.AuthenticatedWebSession.get(0.signIn(username,
> ""):
>
> No doubt a few other things to take care of but may be a good starting
> point.
>
> David.
>
> On Tuesday, 16 August 2016 5:04 PM, uma narayan
>  wrote:
>
>
>  Hi,
> I need to integrate apache isis with shiro-cas. With shiro-cas I was able
> to authenticate and authorize successfully but still isis login page is
> presented is to me.
>
> Summarizing my application flow:1. CAS filter re-directs to CAS Login
> 2. CAS Realm performs authentication and authorization3. Then, apache isis
> login page is presented again.
>
> On analyzing the source code found that AuthenticatedWebSession is not
> created. Please provide me a solution to resolve this issue.
> Thanks for your help,Uma
>
>
>
>
>