[jira] [Created] (SYNCOPE-385) NPE when reading user assigned to resource with no mapping

2013-06-03 Thread JIRA
Francesco Chicchiriccò created SYNCOPE-385:
--

 Summary: NPE when reading user assigned to resource with no mapping
 Key: SYNCOPE-385
 URL: https://issues.apache.org/jira/browse/SYNCOPE-385
 Project: Syncope
  Issue Type: Bug
  Components: core
Affects Versions: 1.1.1
Reporter: Francesco Chicchiriccò
Assignee: Francesco Chicchiriccò
 Fix For: 1.1.2, 1.2.0


1. create a resource without any (user, role) mapping
2. create a user with that resource associated
3. enable DEBUG logging on core
4. get NPE (with HTTP 500) on logs due to null account id mapping item

--
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


[jira] [Resolved] (SYNCOPE-385) NPE when reading user assigned to resource with no mapping

2013-06-03 Thread JIRA

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò resolved SYNCOPE-385.


Resolution: Fixed

1_1_X: http://svn.apache.org/r1488862
trunk: http://svn.apache.org/r1488863

> NPE when reading user assigned to resource with no mapping
> --
>
> Key: SYNCOPE-385
> URL: https://issues.apache.org/jira/browse/SYNCOPE-385
> Project: Syncope
>  Issue Type: Bug
>  Components: core
>Affects Versions: 1.1.1
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 1.1.2, 1.2.0
>
>
> 1. create a resource without any (user, role) mapping
> 2. create a user with that resource associated
> 3. enable DEBUG logging on core
> 4. get NPE (with HTTP 500) on logs due to null account id mapping item

--
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


Re: CXF problem deploying Syncope in Glasshfish

2013-06-03 Thread Francesco Chicchiriccò

On 03/06/2013 08:47, Jan Bernhardt wrote:

Hi Massimiliano,

I'm glad to see you found the solution yourself. Good job!

I'm currently working on SYNCOPE-286 to remove Spring MVC, my problem here is 
that it looks like that a couple of recent changes to trunk have broken the cxf 
build / tests.
I hope to resolve these issues by tomorrow.


Hi Jan,
which errors are you getting with CXF on trunk? I've just checked and 
don't have any error when building "mvn -Pjaxrs" on core (either trunk 
and 1_1_X) with both OpenJDK 1.6 and 1.7 on GNU / Linux.


Regards.

--
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/



[jira] [Commented] (SYNCOPE-385) NPE when reading user assigned to resource with no mapping

2013-06-03 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/SYNCOPE-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13672871#comment-13672871
 ] 

Hudson commented on SYNCOPE-385:


Integrated in Syncope-1_1_X #55 (See 
[https://builds.apache.org/job/Syncope-1_1_X/55/])
[SYNCOPE-385] Checking null before further processing (Revision 1488862)

 Result = SUCCESS
ilgrosso : 
Files : 
* 
/syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/rest/controller/ResourceController.java


> NPE when reading user assigned to resource with no mapping
> --
>
> Key: SYNCOPE-385
> URL: https://issues.apache.org/jira/browse/SYNCOPE-385
> Project: Syncope
>  Issue Type: Bug
>  Components: core
>Affects Versions: 1.1.1
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 1.1.2, 1.2.0
>
>
> 1. create a resource without any (user, role) mapping
> 2. create a user with that resource associated
> 3. enable DEBUG logging on core
> 4. get NPE (with HTTP 500) on logs due to null account id mapping item

--
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


[jira] [Commented] (SYNCOPE-385) NPE when reading user assigned to resource with no mapping

2013-06-03 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/SYNCOPE-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13672872#comment-13672872
 ] 

Hudson commented on SYNCOPE-385:


Integrated in Syncope-trunk #229 (See 
[https://builds.apache.org/job/Syncope-trunk/229/])
[SYNCOPE-385] Checking null before further processing (Revision 1488863)

 Result = SUCCESS
ilgrosso : 
Files : 
* /syncope/trunk
* 
/syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/ResourceController.java


> NPE when reading user assigned to resource with no mapping
> --
>
> Key: SYNCOPE-385
> URL: https://issues.apache.org/jira/browse/SYNCOPE-385
> Project: Syncope
>  Issue Type: Bug
>  Components: core
>Affects Versions: 1.1.1
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 1.1.2, 1.2.0
>
>
> 1. create a resource without any (user, role) mapping
> 2. create a user with that resource associated
> 3. enable DEBUG logging on core
> 4. get NPE (with HTTP 500) on logs due to null account id mapping item

--
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


RE: CXF problem deploying Syncope in Glasshfish

2013-06-03 Thread Jan Bernhardt
Hi Francesco,

My issue here is that not all services are running normally with xml encoding. 
Only JSON is working without problems. One example is WorkflowService:

/**
 * @param kind Kind can be USER or ROLE only!
 * @return Returns existing tasks for matching kind.
 */
@GET
@Path("tasks")
List getDefinedTasks(@PathParam("kind") AttributableType kind);


List is not supported as a XML response for a webservice request, 
because JAX-B does not know how to marshal this kind of primitive data type 
(String does not contain any JAX-B annotations).

It looks like that the UnitTest is only testing JSON encoding.

To verify my issue, just take a look at:

http://localhost:9080/syncope/cxf/workflows/USER/tasks.xml

You will get a response like this:

No message body writer has been found for response class ArrayList.


Best regards.
Jan


> -Original Message-
> From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
> Sent: Montag, 3. Juni 2013 09:08
> To: dev@syncope.apache.org
> Subject: Re: CXF problem deploying Syncope in Glasshfish
> 
> On 03/06/2013 08:47, Jan Bernhardt wrote:
> > Hi Massimiliano,
> >
> > I'm glad to see you found the solution yourself. Good job!
> >
> > I'm currently working on SYNCOPE-286 to remove Spring MVC, my problem
> here is that it looks like that a couple of recent changes to trunk have 
> broken
> the cxf build / tests.
> > I hope to resolve these issues by tomorrow.
> 
> Hi Jan,
> which errors are you getting with CXF on trunk? I've just checked and don't
> have any error when building "mvn -Pjaxrs" on core (either trunk and 1_1_X)
> with both OpenJDK 1.6 and 1.7 on GNU / Linux.
> 
> Regards.
> 
> --
> Francesco Chicchiriccò
> 
> ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
> http://people.apache.org/~ilgrosso/



Re: CXF problem deploying Syncope in Glasshfish

2013-06-03 Thread Francesco Chicchiriccò

On 03/06/2013 10:28, Jan Bernhardt wrote:

Hi Francesco,

My issue here is that not all services are running normally with xml encoding. 
Only JSON is working without problems. One example is WorkflowService:

/**
  * @param kind Kind can be USER or ROLE only!
  * @return Returns existing tasks for matching kind.
  */
 @GET
 @Path("tasks")
 List getDefinedTasks(@PathParam("kind") AttributableType kind);


List is not supported as a XML response for a webservice request, 
because JAX-B does not know how to marshal this kind of primitive data type (String 
does not contain any JAX-B annotations).

It looks like that the UnitTest is only testing JSON encoding.

To verify my issue, just take a look at:

http://localhost:9080/syncope/cxf/workflows/USER/tasks.xml

You will get a response like this:

No message body writer has been found for response class ArrayList.


Ah ok,
but AFAIK this (XML) has always been problematic, even before 1.1.0: 
Sergey, can you confirm?


Regards.


-Original Message-
From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
Sent: Montag, 3. Juni 2013 09:08
To: dev@syncope.apache.org
Subject: Re: CXF problem deploying Syncope in Glasshfish

On 03/06/2013 08:47, Jan Bernhardt wrote:

Hi Massimiliano,

I'm glad to see you found the solution yourself. Good job!

I'm currently working on SYNCOPE-286 to remove Spring MVC, my problem

here is that it looks like that a couple of recent changes to trunk have broken
the cxf build / tests.

I hope to resolve these issues by tomorrow.

Hi Jan,
which errors are you getting with CXF on trunk? I've just checked and don't
have any error when building "mvn -Pjaxrs" on core (either trunk and 1_1_X)
with both OpenJDK 1.6 and 1.7 on GNU / Linux.

Regards.


--
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/



RE: CXF problem deploying Syncope in Glasshfish

2013-06-03 Thread Jan Bernhardt
Hi Francesco this is correct. We had a couple of other issues with XML but 
mainly because of the parallel usage of Spring MVC. After removing Spring MVC 
(and fixing current workarounds), we should be able to get CXF running 100% 
compatible with JSON and XML.

For example I will have to refactor:

List getDefinedTasks(@PathParam("kind") AttributableType kind);

To something like this:

List getDefinedTasks(@PathParam("kind") AttributableType kind);

Best regards.
Jan


> -Original Message-
> From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
> Sent: Montag, 3. Juni 2013 10:35
> To: dev@syncope.apache.org
> Subject: Re: CXF problem deploying Syncope in Glasshfish
> 
> On 03/06/2013 10:28, Jan Bernhardt wrote:
> > Hi Francesco,
> >
> > My issue here is that not all services are running normally with xml
> encoding. Only JSON is working without problems. One example is
> WorkflowService:
> >
> > /**
> >   * @param kind Kind can be USER or ROLE only!
> >   * @return Returns existing tasks for matching kind.
> >   */
> >  @GET
> >  @Path("tasks")
> >  List getDefinedTasks(@PathParam("kind") AttributableType
> > kind);
> >
> >
> > List is not supported as a XML response for a webservice request,
> because JAX-B does not know how to marshal this kind of primitive data type
> (String does not contain any JAX-B annotations).
> >
> > It looks like that the UnitTest is only testing JSON encoding.
> >
> > To verify my issue, just take a look at:
> >
> > http://localhost:9080/syncope/cxf/workflows/USER/tasks.xml
> >
> > You will get a response like this:
> >
> > No message body writer has been found for response class ArrayList.
> 
> Ah ok,
> but AFAIK this (XML) has always been problematic, even before 1.1.0:
> Sergey, can you confirm?
> 
> Regards.
> 
> >> -Original Message-
> >> From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
> >> Sent: Montag, 3. Juni 2013 09:08
> >> To: dev@syncope.apache.org
> >> Subject: Re: CXF problem deploying Syncope in Glasshfish
> >>
> >> On 03/06/2013 08:47, Jan Bernhardt wrote:
> >>> Hi Massimiliano,
> >>>
> >>> I'm glad to see you found the solution yourself. Good job!
> >>>
> >>> I'm currently working on SYNCOPE-286 to remove Spring MVC, my
> >>> problem
> >> here is that it looks like that a couple of recent changes to trunk
> >> have broken the cxf build / tests.
> >>> I hope to resolve these issues by tomorrow.
> >> Hi Jan,
> >> which errors are you getting with CXF on trunk? I've just checked and
> >> don't have any error when building "mvn -Pjaxrs" on core (either
> >> trunk and 1_1_X) with both OpenJDK 1.6 and 1.7 on GNU / Linux.
> >>
> >> Regards.
> 
> --
> Francesco Chicchiriccò
> 
> ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
> http://people.apache.org/~ilgrosso/



Re: CXF problem deploying Syncope in Glasshfish

2013-06-03 Thread Francesco Chicchiriccò

On 03/06/2013 10:45, Jan Bernhardt wrote:

Hi Francesco this is correct. We had a couple of other issues with XML but 
mainly because of the parallel usage of Spring MVC. After removing Spring MVC 
(and fixing current workarounds), we should be able to get CXF running 100% 
compatible with JSON and XML.

For example I will have to refactor:

List getDefinedTasks(@PathParam("kind") AttributableType kind);

To something like this:

List getDefinedTasks(@PathParam("kind") AttributableType kind);


Understood: this wrapping has been done for other methods, so +1 for me.

Regards.


-Original Message-
From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
Sent: Montag, 3. Juni 2013 10:35
To: dev@syncope.apache.org
Subject: Re: CXF problem deploying Syncope in Glasshfish

On 03/06/2013 10:28, Jan Bernhardt wrote:

Hi Francesco,

My issue here is that not all services are running normally with xml

encoding. Only JSON is working without problems. One example is
WorkflowService:

/**
   * @param kind Kind can be USER or ROLE only!
   * @return Returns existing tasks for matching kind.
   */
  @GET
  @Path("tasks")
  List getDefinedTasks(@PathParam("kind") AttributableType
kind);


List is not supported as a XML response for a webservice request,

because JAX-B does not know how to marshal this kind of primitive data type
(String does not contain any JAX-B annotations).

It looks like that the UnitTest is only testing JSON encoding.

To verify my issue, just take a look at:

http://localhost:9080/syncope/cxf/workflows/USER/tasks.xml

You will get a response like this:

No message body writer has been found for response class ArrayList.

Ah ok,
but AFAIK this (XML) has always been problematic, even before 1.1.0:
Sergey, can you confirm?

Regards.


-Original Message-
From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
Sent: Montag, 3. Juni 2013 09:08
To: dev@syncope.apache.org
Subject: Re: CXF problem deploying Syncope in Glasshfish

On 03/06/2013 08:47, Jan Bernhardt wrote:

Hi Massimiliano,

I'm glad to see you found the solution yourself. Good job!

I'm currently working on SYNCOPE-286 to remove Spring MVC, my
problem

here is that it looks like that a couple of recent changes to trunk
have broken the cxf build / tests.

I hope to resolve these issues by tomorrow.

Hi Jan,
which errors are you getting with CXF on trunk? I've just checked and
don't have any error when building "mvn -Pjaxrs" on core (either
trunk and 1_1_X) with both OpenJDK 1.6 and 1.7 on GNU / Linux.

Regards.


--
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/



[jira] [Created] (SYNCOPE-386) Database sync (no full reconciliation) fails with "Unsupported object class"

2013-06-03 Thread JIRA
Francesco Chicchiriccò created SYNCOPE-386:
--

 Summary: Database sync (no full reconciliation) fails with 
"Unsupported object class"
 Key: SYNCOPE-386
 URL: https://issues.apache.org/jira/browse/SYNCOPE-386
 Project: Syncope
  Issue Type: Bug
  Components: core
Affects Versions: 1.1.1
Reporter: Francesco Chicchiriccò
Assignee: Francesco Chicchiriccò
 Fix For: 1.1.2, 1.2.0


When attempting an actual synchronization (not a full reconciliation) against 
an external database, an error is returned from the underlying connector about 
the fact that the only ObjectClass supported is ACCOUNT.

--
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


[jira] [Resolved] (SYNCOPE-386) Database sync (no full reconciliation) fails with "Unsupported object class"

2013-06-03 Thread JIRA

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò resolved SYNCOPE-386.


Resolution: Fixed

1_1_X: http://svn.apache.org/r1488907
trunk: http://svn.apache.org/r1488909

> Database sync (no full reconciliation) fails with "Unsupported object class"
> 
>
> Key: SYNCOPE-386
> URL: https://issues.apache.org/jira/browse/SYNCOPE-386
> Project: Syncope
>  Issue Type: Bug
>  Components: core
>Affects Versions: 1.1.1
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 1.1.2, 1.2.0
>
>
> When attempting an actual synchronization (not a full reconciliation) against 
> an external database, an error is returned from the underlying connector 
> about the fact that the only ObjectClass supported is ACCOUNT.

--
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


[jira] [Commented] (SYNCOPE-386) Database sync (no full reconciliation) fails with "Unsupported object class"

2013-06-03 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/SYNCOPE-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13672952#comment-13672952
 ] 

Hudson commented on SYNCOPE-386:


Integrated in Syncope-trunk #230 (See 
[https://builds.apache.org/job/Syncope-trunk/230/])
[SYNCOPE-386] Checking mapping of the given kind (user, role) before 
attempting to get latest sync token (Revision 1488909)

 Result = SUCCESS
ilgrosso : 
Files : 
* /syncope/trunk
* 
/syncope/trunk/core/src/main/java/org/apache/syncope/core/sync/impl/SyncJob.java


> Database sync (no full reconciliation) fails with "Unsupported object class"
> 
>
> Key: SYNCOPE-386
> URL: https://issues.apache.org/jira/browse/SYNCOPE-386
> Project: Syncope
>  Issue Type: Bug
>  Components: core
>Affects Versions: 1.1.1
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 1.1.2, 1.2.0
>
>
> When attempting an actual synchronization (not a full reconciliation) against 
> an external database, an error is returned from the underlying connector 
> about the fact that the only ObjectClass supported is ACCOUNT.

--
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


[jira] [Commented] (SYNCOPE-386) Database sync (no full reconciliation) fails with "Unsupported object class"

2013-06-03 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/SYNCOPE-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13672962#comment-13672962
 ] 

Hudson commented on SYNCOPE-386:


Integrated in Syncope-1_1_X #56 (See 
[https://builds.apache.org/job/Syncope-1_1_X/56/])
[SYNCOPE-386] Checking mapping of the given kind (user, role) before 
attempting to get latest sync token (Revision 1488907)

 Result = SUCCESS
ilgrosso : 
Files : 
* 
/syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/sync/impl/SyncJob.java


> Database sync (no full reconciliation) fails with "Unsupported object class"
> 
>
> Key: SYNCOPE-386
> URL: https://issues.apache.org/jira/browse/SYNCOPE-386
> Project: Syncope
>  Issue Type: Bug
>  Components: core
>Affects Versions: 1.1.1
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 1.1.2, 1.2.0
>
>
> When attempting an actual synchronization (not a full reconciliation) against 
> an external database, an error is returned from the underlying connector 
> about the fact that the only ObjectClass supported is ACCOUNT.

--
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


[jira] [Created] (SYNCOPE-387) Unable to synchronize deleted objects from OpenDJ

2013-06-03 Thread JIRA
Francesco Chicchiriccò created SYNCOPE-387:
--

 Summary: Unable to synchronize deleted objects from OpenDJ
 Key: SYNCOPE-387
 URL: https://issues.apache.org/jira/browse/SYNCOPE-387
 Project: Syncope
  Issue Type: Bug
  Components: core
Affects Versions: 1.1.1
Reporter: Francesco Chicchiriccò
 Fix For: 1.1.2, 1.2.0


While performing actual synchronization (no full reconciliation) from OpenDJ, 
deleted objects (user and groups) cause NPE at SyncopeSyncResultHandler:826, 
barely because the ConnId LDAP connector returns a null object upon sync(), for 
deleted entries (meaning delta.getObject() is null).

--
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


[jira] [Updated] (SYNCOPE-387) Unable to synchronize deleted objects from OpenDJ

2013-06-03 Thread JIRA

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-387:
---

Description: 
While performing actual synchronization (no full reconciliation) from OpenDJ, 
deleted objects (user and groups) cause NPE at SyncopeSyncResultHandler:826, 
barely because the ConnId LDAP connector returns a null object upon sync(), for 
deleted entries (meaning delta.getObject() is null).

Linked issue on ConnId: https://connid.atlassian.net/browse/LDAP-8

  was:While performing actual synchronization (no full reconciliation) from 
OpenDJ, deleted objects (user and groups) cause NPE at 
SyncopeSyncResultHandler:826, barely because the ConnId LDAP connector returns 
a null object upon sync(), for deleted entries (meaning delta.getObject() is 
null).


> Unable to synchronize deleted objects from OpenDJ
> -
>
> Key: SYNCOPE-387
> URL: https://issues.apache.org/jira/browse/SYNCOPE-387
> Project: Syncope
>  Issue Type: Bug
>  Components: core
>Affects Versions: 1.1.1
>Reporter: Francesco Chicchiriccò
> Fix For: 1.1.2, 1.2.0
>
>
> While performing actual synchronization (no full reconciliation) from OpenDJ, 
> deleted objects (user and groups) cause NPE at SyncopeSyncResultHandler:826, 
> barely because the ConnId LDAP connector returns a null object upon sync(), 
> for deleted entries (meaning delta.getObject() is null).
> Linked issue on ConnId: https://connid.atlassian.net/browse/LDAP-8

--
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


[jira] [Commented] (SYNCOPE-377) Exporting configuration via console causes exceptions to be thrown

2013-06-03 Thread Nik Tetteh-Lartey (JIRA)

[ 
https://issues.apache.org/jira/browse/SYNCOPE-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673202#comment-13673202
 ] 

Nik Tetteh-Lartey commented on SYNCOPE-377:
---

I rebuilt the project this morning. I'm still getting the exceptions:

Unexpected RuntimeException

Last cause: 
javax.ws.rs.core.Response.getHeaderString(Ljava/lang/String;)Ljava/lang/String;
WicketMessage: Method onLinkClicked of interface 
org.apache.wicket.markup.html.link.ILinkListener targeted at [Link [Component 
id = dbExportLink]] on component [Link [Component id = dbExportLink]] threw an 
exception

Stacktrace

Root cause:

java.lang.NoSuchMethodError: 
javax.ws.rs.core.Response.getHeaderString(Ljava/lang/String;)Ljava/lang/String;
at 
org.apache.syncope.console.commons.HttpResourceStream.(HttpResourceStream.java:49)
at 
org.apache.syncope.console.pages.Configuration$4.onClick(Configuration.java:341)
at org.apache.wicket.markup.html.link.Link.onLinkClicked(Link.java:190)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
org.apache.wicket.RequestListenerInterface.internalInvoke(RequestListenerInterface.java:258)
at 
org.apache.wicket.RequestListenerInterface.invoke(RequestListenerInterface.java:216)
at 
org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.invokeListener(ListenerInterfaceRequestHandler.java:240)
at 
org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:226)
at 
org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:861)
at 
org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
at org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:261)
at 
org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:218)
at 
org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:289)
at 
org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:259)
at 
org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:201)
at org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:282)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:256)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:217)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:279)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:655)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:595)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:161)
at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:331)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:231)
at 
com.sun.enterprise.v3.services.impl.ContainerMapper$AdapterCallable.call(ContainerMapper.java:317)
at 
com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195)
at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:849)
at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:746)
at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1045)
at 
com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:228)
at 
com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
at 
com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
at 
com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
at 
com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
at java.lang.Thread.run(Thread.java:662)

Complete stack:

org.apache.wicket.WicketRuntimeException: Method onLinkClicked of interface 
org.apache.wicket.markup.html.link.ILinkListener targeted at [Link [Component 
id = dbExportLink]] on component [Link [Component id = dbExportLink]] threw an 
exception
at 
org.apache.wicket.RequestListenerInterface.internalInvoke(RequestListenerInterface.java:268)
at 
org.apache.wicket.RequestListenerInterface.invoke(RequestListenerInterface.java:216)
at 
org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.invokeListener(ListenerInterfaceRequestHandler.java:240)
at 
org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:226)
a

[jira] [Commented] (SYNCOPE-377) Exporting configuration via console causes exceptions to be thrown

2013-06-03 Thread JIRA

[ 
https://issues.apache.org/jira/browse/SYNCOPE-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673205#comment-13673205
 ] 

Francesco Chicchiriccò commented on SYNCOPE-377:


[~ntlartey], 

> java.lang.NoSuchMethodError: 
> javax.ws.rs.core.Response.getHeaderString(Ljava/lang/String;)Ljava/lang/String;

means you are still using the wrong dependency in glassfish: have you checked

1. that you have [1] in your project? if this is missing, this is due to the 
fact that you generated your project before it was added to Syncope; anyway, 
just download it and copy it under console/src/main/webapp

2. that the running glassfish instance has the 
"-Dcom.sun.enterprise.overrideablejavaxpackages=javax.ws.rs,javax.ws.rs.core,javax.ws.rs.ext
" JVM option?

HTH

[1] 
https://svn.apache.org/repos/asf/syncope/branches/1_1_X/console/src/main/webapp/WEB-INF/glassfish-web.xml
[2] 
https://cwiki.apache.org/confluence/display/SYNCOPE/Run+Syncope+in+real+environments#RunSyncopeinrealenvironments-AddJVMoption

> Exporting configuration via console causes exceptions to be thrown
> --
>
> Key: SYNCOPE-377
> URL: https://issues.apache.org/jira/browse/SYNCOPE-377
> Project: Syncope
>  Issue Type: Bug
>  Components: console, core
>Affects Versions: 1.1.2
> Environment: Glassfish
>Reporter: Nik Tetteh-Lartey
>Assignee: Massimiliano Perrone
> Fix For: 1.1.2, 1.2.0
>
>
> Exception is thrown by console when the export DB symbol is pushed from 
> Console->Confugurations->export symbol
> Unexpected RuntimeException
> Last cause: 
> javax.ws.rs.core.Response.getHeaderString(Ljava/lang/String;)Ljava/lang/String;
> WicketMessage: Method onLinkClicked of interface 
> org.apache.wicket.markup.html.link.ILinkListener targeted at [Link [Component 
> id = dbExportLink]] on component [Link [Component id = dbExportLink]] threw 
> an exception
> Stacktrace
> Root cause:
> java.lang.NoSuchMethodError: 
> javax.ws.rs.core.Response.getHeaderString(Ljava/lang/String;)Ljava/lang/String;
> at 
> org.apache.syncope.console.commons.HttpResourceStream.(HttpResourceStream.java:49)
> at 
> org.apache.syncope.console.pages.Configuration$4.onClick(Configuration.java:341)
> at org.apache.wicket.markup.html.link.Link.onLinkClicked(Link.java:190)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at 
> org.apache.wicket.RequestListenerInterface.internalInvoke(RequestListenerInterface.java:258)
> at 
> org.apache.wicket.RequestListenerInterface.invoke(RequestListenerInterface.java:216)
> at 
> org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.invokeListener(ListenerInterfaceRequestHandler.java:240)
> at 
> org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:226)
> at 
> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:861)
> at 
> org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
> at org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:261)
> at 
> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:218)
> at 
> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:289)
> at 
> org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:259)
> at 
> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:201)
> at 
> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:282)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:256)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:217)
> at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:279)
> at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
> at 
> org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:655)
> at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:595)
> at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:161)
> at 
> org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:331)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:231)
> at 
> com.sun.enterprise.v3.services.impl.ContainerMapper$AdapterCallable.call(ContainerMapper.java:317)
> at 
> com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195)
> at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:849)
> at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:746)
> at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1045)
>

[jira] [Updated] (SYNCOPE-382) Core hangs for a very long time (1h+ and then resumes) after a CLI role create and list

2013-06-03 Thread Nik Tetteh-Lartey (JIRA)

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nik Tetteh-Lartey updated SYNCOPE-382:
--

Attachment: jstack.out

> Core hangs for a very long time (1h+ and then resumes) after a CLI role 
> create and list
> ---
>
> Key: SYNCOPE-382
> URL: https://issues.apache.org/jira/browse/SYNCOPE-382
> Project: Syncope
>  Issue Type: Bug
>  Components: core
>Affects Versions: 1.1.1
> Environment: Glassfish
>Reporter: Nik Tetteh-Lartey
>Assignee: Massimiliano Perrone
> Fix For: 1.1.2, 1.2.0
>
> Attachments: jstack.out, jstack.out, jstack.out2
>
>
> syncope stops responding for 1h+ and then resumes after a CLI role create and 
> list:
> (The syncope console remains unreachable see jstack.out2 attached)
> [nik@anvil idmRBAC]$ curl -u admin:passwoX POST 
> http://10.0.0.183:9090/syncope/cxf/roles --data 
> "babar6" -H "Content-type: application/xml"  -D 
> /tmp/headers 
> 
> 
> 
> 117
> 
> 
> 
> 
> false
> false
> false
> false
> false
> false
> babar6
> 0
> 
> [nik@anvil idmRBAC]$ curl -u admin:password -H "Content-Type: 
> application/json" -X GET http://10.0.0.183:9090/syncope/cxf/roles/{117}
> 
> 
> 
> 
> 117
> 
> 
> 
> 
> false
> false
> false
> false
> false
> false
> babar6
> 0
> 
> [nik@anvil idmRBAC]$ curl -u admin:password -H "Content-Type: 
> application/json" -X GET http://10.0.0.183:9090/syncope/cxf/roles/{117}
> curl: (52) Empty reply from server
> [nik@anvil idmRBAC]$
> 2013-05-31 12:31:40.190+0200 (21) StandardWrapperValve[CXFServlet]: PWC1406: 
> Servlet.service() for servlet CXFServlet threw exception
> java.lang.NoSuchMethodError: 
> javax.ws.rs.ClientErrorException.validate(Ljavax/ws/rs/core/Response;Ljavax/ws/rs/core/Response$Status$Family;)Ljavax/ws/rs/core/Response;
> at javax.ws.rs.ClientErrorException.(ClientErrorException.java:101)
> at 
> org.apache.cxf.jaxrs.utils.InjectionUtils.handleParameter(InjectionUtils.java:368)
> at 
> org.apache.cxf.jaxrs.utils.InjectionUtils.createParameterObject(InjectionUtils.java:859)
> at 
> org.apache.cxf.jaxrs.utils.JAXRSUtils.readFromUriParam(JAXRSUtils.java:1133)
> at 
> org.apache.cxf.jaxrs.utils.JAXRSUtils.createHttpParameterValue(JAXRSUtils.java:825)
> at 
> org.apache.cxf.jaxrs.utils.JAXRSUtils.processParameter(JAXRSUtils.java:800)
> at 
> org.apache.cxf.jaxrs.utils.JAXRSUtils.processParameters(JAXRSUtils.java:747)
> at 
> org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.processRequest(JAXRSInInterceptor.java:240)
> at 
> org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.handleMessage(JAXRSInInterceptor.java:100)
> at 
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
> at 
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
> at 
> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
> at 
> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
> at 
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
> at 
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
> at 
> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:158)
> at 
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:243)
> at 
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:168)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
> at 
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:219)
> at 
> org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1542)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:343)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:217)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
> at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118)
> at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at 
> org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslat

[jira] [Commented] (SYNCOPE-382) Core hangs for a very long time (1h+ and then resumes) after a CLI role create and list

2013-06-03 Thread Nik Tetteh-Lartey (JIRA)

[ 
https://issues.apache.org/jira/browse/SYNCOPE-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673208#comment-13673208
 ] 

Nik Tetteh-Lartey commented on SYNCOPE-382:
---

rebuilt my project this morning and I still get a hang after I try to export DB.
See attached jstack.out.

> Core hangs for a very long time (1h+ and then resumes) after a CLI role 
> create and list
> ---
>
> Key: SYNCOPE-382
> URL: https://issues.apache.org/jira/browse/SYNCOPE-382
> Project: Syncope
>  Issue Type: Bug
>  Components: core
>Affects Versions: 1.1.1
> Environment: Glassfish
>Reporter: Nik Tetteh-Lartey
>Assignee: Massimiliano Perrone
> Fix For: 1.1.2, 1.2.0
>
> Attachments: jstack.out, jstack.out, jstack.out2
>
>
> syncope stops responding for 1h+ and then resumes after a CLI role create and 
> list:
> (The syncope console remains unreachable see jstack.out2 attached)
> [nik@anvil idmRBAC]$ curl -u admin:passwoX POST 
> http://10.0.0.183:9090/syncope/cxf/roles --data 
> "babar6" -H "Content-type: application/xml"  -D 
> /tmp/headers 
> 
> 
> 
> 117
> 
> 
> 
> 
> false
> false
> false
> false
> false
> false
> babar6
> 0
> 
> [nik@anvil idmRBAC]$ curl -u admin:password -H "Content-Type: 
> application/json" -X GET http://10.0.0.183:9090/syncope/cxf/roles/{117}
> 
> 
> 
> 
> 117
> 
> 
> 
> 
> false
> false
> false
> false
> false
> false
> babar6
> 0
> 
> [nik@anvil idmRBAC]$ curl -u admin:password -H "Content-Type: 
> application/json" -X GET http://10.0.0.183:9090/syncope/cxf/roles/{117}
> curl: (52) Empty reply from server
> [nik@anvil idmRBAC]$
> 2013-05-31 12:31:40.190+0200 (21) StandardWrapperValve[CXFServlet]: PWC1406: 
> Servlet.service() for servlet CXFServlet threw exception
> java.lang.NoSuchMethodError: 
> javax.ws.rs.ClientErrorException.validate(Ljavax/ws/rs/core/Response;Ljavax/ws/rs/core/Response$Status$Family;)Ljavax/ws/rs/core/Response;
> at javax.ws.rs.ClientErrorException.(ClientErrorException.java:101)
> at 
> org.apache.cxf.jaxrs.utils.InjectionUtils.handleParameter(InjectionUtils.java:368)
> at 
> org.apache.cxf.jaxrs.utils.InjectionUtils.createParameterObject(InjectionUtils.java:859)
> at 
> org.apache.cxf.jaxrs.utils.JAXRSUtils.readFromUriParam(JAXRSUtils.java:1133)
> at 
> org.apache.cxf.jaxrs.utils.JAXRSUtils.createHttpParameterValue(JAXRSUtils.java:825)
> at 
> org.apache.cxf.jaxrs.utils.JAXRSUtils.processParameter(JAXRSUtils.java:800)
> at 
> org.apache.cxf.jaxrs.utils.JAXRSUtils.processParameters(JAXRSUtils.java:747)
> at 
> org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.processRequest(JAXRSInInterceptor.java:240)
> at 
> org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.handleMessage(JAXRSInInterceptor.java:100)
> at 
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
> at 
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
> at 
> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
> at 
> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
> at 
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
> at 
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
> at 
> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:158)
> at 
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:243)
> at 
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:168)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
> at 
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:219)
> at 
> org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1542)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:343)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:217)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
> at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118)
> at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilte

[jira] [Commented] (SYNCOPE-382) Core hangs for a very long time (1h+ and then resumes) after a CLI role create and list

2013-06-03 Thread JIRA

[ 
https://issues.apache.org/jira/browse/SYNCOPE-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673211#comment-13673211
 ] 

Francesco Chicchiriccò commented on SYNCOPE-382:


See my comment at SYNCOPE-377 - it should be the same thing.

> Core hangs for a very long time (1h+ and then resumes) after a CLI role 
> create and list
> ---
>
> Key: SYNCOPE-382
> URL: https://issues.apache.org/jira/browse/SYNCOPE-382
> Project: Syncope
>  Issue Type: Bug
>  Components: core
>Affects Versions: 1.1.1
> Environment: Glassfish
>Reporter: Nik Tetteh-Lartey
>Assignee: Massimiliano Perrone
> Fix For: 1.1.2, 1.2.0
>
> Attachments: jstack.out, jstack.out, jstack.out2
>
>
> syncope stops responding for 1h+ and then resumes after a CLI role create and 
> list:
> (The syncope console remains unreachable see jstack.out2 attached)
> [nik@anvil idmRBAC]$ curl -u admin:passwoX POST 
> http://10.0.0.183:9090/syncope/cxf/roles --data 
> "babar6" -H "Content-type: application/xml"  -D 
> /tmp/headers 
> 
> 
> 
> 117
> 
> 
> 
> 
> false
> false
> false
> false
> false
> false
> babar6
> 0
> 
> [nik@anvil idmRBAC]$ curl -u admin:password -H "Content-Type: 
> application/json" -X GET http://10.0.0.183:9090/syncope/cxf/roles/{117}
> 
> 
> 
> 
> 117
> 
> 
> 
> 
> false
> false
> false
> false
> false
> false
> babar6
> 0
> 
> [nik@anvil idmRBAC]$ curl -u admin:password -H "Content-Type: 
> application/json" -X GET http://10.0.0.183:9090/syncope/cxf/roles/{117}
> curl: (52) Empty reply from server
> [nik@anvil idmRBAC]$
> 2013-05-31 12:31:40.190+0200 (21) StandardWrapperValve[CXFServlet]: PWC1406: 
> Servlet.service() for servlet CXFServlet threw exception
> java.lang.NoSuchMethodError: 
> javax.ws.rs.ClientErrorException.validate(Ljavax/ws/rs/core/Response;Ljavax/ws/rs/core/Response$Status$Family;)Ljavax/ws/rs/core/Response;
> at javax.ws.rs.ClientErrorException.(ClientErrorException.java:101)
> at 
> org.apache.cxf.jaxrs.utils.InjectionUtils.handleParameter(InjectionUtils.java:368)
> at 
> org.apache.cxf.jaxrs.utils.InjectionUtils.createParameterObject(InjectionUtils.java:859)
> at 
> org.apache.cxf.jaxrs.utils.JAXRSUtils.readFromUriParam(JAXRSUtils.java:1133)
> at 
> org.apache.cxf.jaxrs.utils.JAXRSUtils.createHttpParameterValue(JAXRSUtils.java:825)
> at 
> org.apache.cxf.jaxrs.utils.JAXRSUtils.processParameter(JAXRSUtils.java:800)
> at 
> org.apache.cxf.jaxrs.utils.JAXRSUtils.processParameters(JAXRSUtils.java:747)
> at 
> org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.processRequest(JAXRSInInterceptor.java:240)
> at 
> org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.handleMessage(JAXRSInInterceptor.java:100)
> at 
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
> at 
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
> at 
> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
> at 
> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
> at 
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
> at 
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
> at 
> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:158)
> at 
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:243)
> at 
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:168)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
> at 
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:219)
> at 
> org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1542)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:343)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:217)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
> at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118)
> at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.ja

[jira] [Comment Edited] (SYNCOPE-382) Core hangs for a very long time (1h+ and then resumes) after a CLI role create and list

2013-06-03 Thread JIRA

[ 
https://issues.apache.org/jira/browse/SYNCOPE-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673211#comment-13673211
 ] 

Francesco Chicchiriccò edited comment on SYNCOPE-382 at 6/3/13 3:43 PM:


See my comment at SYNCOPE-377 [1] - it should be the same thing.

[1] 
https://issues.apache.org/jira/browse/SYNCOPE-377?focusedCommentId=13673205&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13673205

  was (Author: ilgrosso):
See my comment at SYNCOPE-377 - it should be the same thing.
  
> Core hangs for a very long time (1h+ and then resumes) after a CLI role 
> create and list
> ---
>
> Key: SYNCOPE-382
> URL: https://issues.apache.org/jira/browse/SYNCOPE-382
> Project: Syncope
>  Issue Type: Bug
>  Components: core
>Affects Versions: 1.1.1
> Environment: Glassfish
>Reporter: Nik Tetteh-Lartey
>Assignee: Massimiliano Perrone
> Fix For: 1.1.2, 1.2.0
>
> Attachments: jstack.out, jstack.out, jstack.out2
>
>
> syncope stops responding for 1h+ and then resumes after a CLI role create and 
> list:
> (The syncope console remains unreachable see jstack.out2 attached)
> [nik@anvil idmRBAC]$ curl -u admin:passwoX POST 
> http://10.0.0.183:9090/syncope/cxf/roles --data 
> "babar6" -H "Content-type: application/xml"  -D 
> /tmp/headers 
> 
> 
> 
> 117
> 
> 
> 
> 
> false
> false
> false
> false
> false
> false
> babar6
> 0
> 
> [nik@anvil idmRBAC]$ curl -u admin:password -H "Content-Type: 
> application/json" -X GET http://10.0.0.183:9090/syncope/cxf/roles/{117}
> 
> 
> 
> 
> 117
> 
> 
> 
> 
> false
> false
> false
> false
> false
> false
> babar6
> 0
> 
> [nik@anvil idmRBAC]$ curl -u admin:password -H "Content-Type: 
> application/json" -X GET http://10.0.0.183:9090/syncope/cxf/roles/{117}
> curl: (52) Empty reply from server
> [nik@anvil idmRBAC]$
> 2013-05-31 12:31:40.190+0200 (21) StandardWrapperValve[CXFServlet]: PWC1406: 
> Servlet.service() for servlet CXFServlet threw exception
> java.lang.NoSuchMethodError: 
> javax.ws.rs.ClientErrorException.validate(Ljavax/ws/rs/core/Response;Ljavax/ws/rs/core/Response$Status$Family;)Ljavax/ws/rs/core/Response;
> at javax.ws.rs.ClientErrorException.(ClientErrorException.java:101)
> at 
> org.apache.cxf.jaxrs.utils.InjectionUtils.handleParameter(InjectionUtils.java:368)
> at 
> org.apache.cxf.jaxrs.utils.InjectionUtils.createParameterObject(InjectionUtils.java:859)
> at 
> org.apache.cxf.jaxrs.utils.JAXRSUtils.readFromUriParam(JAXRSUtils.java:1133)
> at 
> org.apache.cxf.jaxrs.utils.JAXRSUtils.createHttpParameterValue(JAXRSUtils.java:825)
> at 
> org.apache.cxf.jaxrs.utils.JAXRSUtils.processParameter(JAXRSUtils.java:800)
> at 
> org.apache.cxf.jaxrs.utils.JAXRSUtils.processParameters(JAXRSUtils.java:747)
> at 
> org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.processRequest(JAXRSInInterceptor.java:240)
> at 
> org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.handleMessage(JAXRSInInterceptor.java:100)
> at 
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
> at 
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
> at 
> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
> at 
> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
> at 
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
> at 
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
> at 
> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:158)
> at 
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:243)
> at 
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:168)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
> at 
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:219)
> at 
> org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1542)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:343)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:217)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
> at 
> org.springframework.securi

[jira] [Commented] (SYNCOPE-382) Core hangs for a very long time (1h+ and then resumes) after a CLI role create and list

2013-06-03 Thread Nik Tetteh-Lartey (JIRA)

[ 
https://issues.apache.org/jira/browse/SYNCOPE-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673230#comment-13673230
 ] 

Nik Tetteh-Lartey commented on SYNCOPE-382:
---

was the missing JVM option, Francesco.

Glassfish seems to be working now as good a tomcat for the stuff I have tested.
Thank you and Massi for your efforts.

rgds,
Nik

> Core hangs for a very long time (1h+ and then resumes) after a CLI role 
> create and list
> ---
>
> Key: SYNCOPE-382
> URL: https://issues.apache.org/jira/browse/SYNCOPE-382
> Project: Syncope
>  Issue Type: Bug
>  Components: core
>Affects Versions: 1.1.1
> Environment: Glassfish
>Reporter: Nik Tetteh-Lartey
>Assignee: Massimiliano Perrone
> Fix For: 1.1.2, 1.2.0
>
> Attachments: jstack.out, jstack.out, jstack.out2
>
>
> syncope stops responding for 1h+ and then resumes after a CLI role create and 
> list:
> (The syncope console remains unreachable see jstack.out2 attached)
> [nik@anvil idmRBAC]$ curl -u admin:passwoX POST 
> http://10.0.0.183:9090/syncope/cxf/roles --data 
> "babar6" -H "Content-type: application/xml"  -D 
> /tmp/headers 
> 
> 
> 
> 117
> 
> 
> 
> 
> false
> false
> false
> false
> false
> false
> babar6
> 0
> 
> [nik@anvil idmRBAC]$ curl -u admin:password -H "Content-Type: 
> application/json" -X GET http://10.0.0.183:9090/syncope/cxf/roles/{117}
> 
> 
> 
> 
> 117
> 
> 
> 
> 
> false
> false
> false
> false
> false
> false
> babar6
> 0
> 
> [nik@anvil idmRBAC]$ curl -u admin:password -H "Content-Type: 
> application/json" -X GET http://10.0.0.183:9090/syncope/cxf/roles/{117}
> curl: (52) Empty reply from server
> [nik@anvil idmRBAC]$
> 2013-05-31 12:31:40.190+0200 (21) StandardWrapperValve[CXFServlet]: PWC1406: 
> Servlet.service() for servlet CXFServlet threw exception
> java.lang.NoSuchMethodError: 
> javax.ws.rs.ClientErrorException.validate(Ljavax/ws/rs/core/Response;Ljavax/ws/rs/core/Response$Status$Family;)Ljavax/ws/rs/core/Response;
> at javax.ws.rs.ClientErrorException.(ClientErrorException.java:101)
> at 
> org.apache.cxf.jaxrs.utils.InjectionUtils.handleParameter(InjectionUtils.java:368)
> at 
> org.apache.cxf.jaxrs.utils.InjectionUtils.createParameterObject(InjectionUtils.java:859)
> at 
> org.apache.cxf.jaxrs.utils.JAXRSUtils.readFromUriParam(JAXRSUtils.java:1133)
> at 
> org.apache.cxf.jaxrs.utils.JAXRSUtils.createHttpParameterValue(JAXRSUtils.java:825)
> at 
> org.apache.cxf.jaxrs.utils.JAXRSUtils.processParameter(JAXRSUtils.java:800)
> at 
> org.apache.cxf.jaxrs.utils.JAXRSUtils.processParameters(JAXRSUtils.java:747)
> at 
> org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.processRequest(JAXRSInInterceptor.java:240)
> at 
> org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.handleMessage(JAXRSInInterceptor.java:100)
> at 
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
> at 
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
> at 
> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
> at 
> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
> at 
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
> at 
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
> at 
> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:158)
> at 
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:243)
> at 
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:168)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
> at 
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:219)
> at 
> org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1542)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:343)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:217)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
> at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118)
> at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84)
> at 
>

[jira] [Commented] (SYNCOPE-377) Exporting configuration via console causes exceptions to be thrown

2013-06-03 Thread Nik Tetteh-Lartey (JIRA)

[ 
https://issues.apache.org/jira/browse/SYNCOPE-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673239#comment-13673239
 ] 

Nik Tetteh-Lartey commented on SYNCOPE-377:
---

[1] was as expected after the project rebuild.
it was the missing JVM option Francesco [2].

Glassfish seems to be working as good a tomcat for the stuff I have tested.
Thank you and Massi for your efforts.

rgds,
Nik

> Exporting configuration via console causes exceptions to be thrown
> --
>
> Key: SYNCOPE-377
> URL: https://issues.apache.org/jira/browse/SYNCOPE-377
> Project: Syncope
>  Issue Type: Bug
>  Components: console, core
>Affects Versions: 1.1.2
> Environment: Glassfish
>Reporter: Nik Tetteh-Lartey
>Assignee: Massimiliano Perrone
> Fix For: 1.1.2, 1.2.0
>
>
> Exception is thrown by console when the export DB symbol is pushed from 
> Console->Confugurations->export symbol
> Unexpected RuntimeException
> Last cause: 
> javax.ws.rs.core.Response.getHeaderString(Ljava/lang/String;)Ljava/lang/String;
> WicketMessage: Method onLinkClicked of interface 
> org.apache.wicket.markup.html.link.ILinkListener targeted at [Link [Component 
> id = dbExportLink]] on component [Link [Component id = dbExportLink]] threw 
> an exception
> Stacktrace
> Root cause:
> java.lang.NoSuchMethodError: 
> javax.ws.rs.core.Response.getHeaderString(Ljava/lang/String;)Ljava/lang/String;
> at 
> org.apache.syncope.console.commons.HttpResourceStream.(HttpResourceStream.java:49)
> at 
> org.apache.syncope.console.pages.Configuration$4.onClick(Configuration.java:341)
> at org.apache.wicket.markup.html.link.Link.onLinkClicked(Link.java:190)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at 
> org.apache.wicket.RequestListenerInterface.internalInvoke(RequestListenerInterface.java:258)
> at 
> org.apache.wicket.RequestListenerInterface.invoke(RequestListenerInterface.java:216)
> at 
> org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.invokeListener(ListenerInterfaceRequestHandler.java:240)
> at 
> org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:226)
> at 
> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:861)
> at 
> org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
> at org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:261)
> at 
> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:218)
> at 
> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:289)
> at 
> org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:259)
> at 
> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:201)
> at 
> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:282)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:256)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:217)
> at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:279)
> at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
> at 
> org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:655)
> at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:595)
> at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:161)
> at 
> org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:331)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:231)
> at 
> com.sun.enterprise.v3.services.impl.ContainerMapper$AdapterCallable.call(ContainerMapper.java:317)
> at 
> com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195)
> at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:849)
> at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:746)
> at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1045)
> at 
> com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:228)
> at 
> com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
> at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
> at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
> at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
> at 
> com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
> at 
> com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
> at com.sun.griz

Syncope User & Role entitlements (role management delegation)

2013-06-03 Thread James Flemer
Hi,

I have a use case for role management delegation.  The desired use case is:
  A given user, "the Manager", is permitted to add and remove other users
from a set of one or more "managed roles", but is not permitted to modify
role membership for other roles.

NOTE: All following comments apply to Syncope 1.1.0 / 1.1.x.

The current USER_* and ROLE_* entitlements are somewhat confusing (perhaps
incomplete), and unfortunately do not support the use case above.

The USER_LIST entitlement actually behaves like:
  "allow listing all users who's set of roles is a subset of my role
entitlements"
In other words, a user (with USER_LIST) cannot see other users if they have
a role that the user does not have an entitlement to.  I would have
expected that USER_LIST would allow listing of all users, or I would expect
another entitlement like USER_LIST_ALL to cover that case.  The "list
users" capability is needed for the use case above, the manager needs the
ability to see all users.

The USER_UPDATE and USER_READ entitlements seems to be unconditional, they
are NOT limited according to Role as USER_LIST is.  This is inconsistent.
 Additionally, USER_LIST and USER_READ are somewhat overlapping.  Listing
user includes all the detail in USER_READ.  However, USER_LIST doesn't
allow reading user by id or username (even though list provides this data).

There is no ROLE_LIST entitlement, and it appears that roles can be listed
(in full detail) without any authentication or authorization.  Although
this doesn't break the use case above, it doesn't seem that roles should be
listable without authn/authz.  Again this is inconsistent with ROLE_READ
which is required to read a role by id, even though list provides the same
detail.

Some suggestions, or a starting point for discussion:

   1. Change USER_LIST to permit listing of *ALL* users (regardless of
   roles).
   2. Create ROLE_LIST, and make it required to list roles.
   3. Allow USER_LIST in all places where USER_READ+ROLE_x is required
   (i.e. USER_LIST is a superset of USER_READ).
   4. Require USER_UPDATE+ROLE_x entitlement to add/delete role "x" from a
   user.

I'm not sure the above mods are the correct approach.  These suggestions
still leave a bit of ambiguity, and likely conflict with the needs for
other use cases.  However, I think the use case where "the Manager" who is
permitted to control the membership of a sub-set of roles is quite common.
 With the above, the following example should work (names used instead of
numbers for clarity):

Role "foo-mgr" has entitlement "USER_LIST, USER_READ, USER_UPDATE,
ROLE_LIST, ROLE_READ, ROLE_foo1, ROLE_foo2".
User "themgr" has role "foo-mgr"
User "joe" has role "bar1".
Then, "themgr" can log in, find "joe" and add (or remove) "joe" from the
"foo1" and/or "foo2" roles.

However, "themgr" cannot remove "joe" from "bar1" (because "themgr" does
not have the "ROLE_bar1" entitlement).


Regards,

James Flemer