Il giorno 07/mar/2013, alle ore 04.53, Edward Siewick ha scritto:
Hi.
Just a note to report a bizarre error impacting the identity matching.
I noticed bug #317. So I:
Toggled off Update matched identities Synchronization tasks / Edit / Task
screen for the MySQL resource.
Toggled on
[
https://issues.apache.org/jira/browse/SYNCOPE-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595689#comment-13595689
]
fabio martelli commented on SYNCOPE-198:
I'm going to implement a bulk method for
Hi,
Problem is occuring for syncope-core context path is wrong. When you
change the context path to syncope everything work fine. Developer must
change context-path enviorements for application server or may be it will
be done in maven settings.
Murat ÇOLAK
The Apache Jenkins build system has built Syncope-trunk (build #135)
Status: Failure
Check console output at https://builds.apache.org/job/Syncope-trunk/135/ to
view the results.
Hi all,
I have just noticed that the root XML element when listing policies via
CXF is
policys
instead of
policies
I couldn't easily (= grep) find how to change this: anyone can provide
some hint?
Regards.
--
Francesco Chicchiriccò
ASF Member, Apache Syncope PMC chair, Apache Cocoon
The Apache Jenkins build system has built Syncope-trunk (build #136)
Status: Still Failing
Check console output at https://builds.apache.org/job/Syncope-trunk/136/ to
view the results.
The Apache Jenkins build system has built Syncope-trunk (build #137)
Status: Aborted
Check console output at https://builds.apache.org/job/Syncope-trunk/137/ to
view the results.
The Apache Jenkins build system has built Syncope-trunk (build #138)
Status: Failure
Check console output at https://builds.apache.org/job/Syncope-trunk/138/ to
view the results.
The Apache Jenkins build system has built Syncope-trunk (build #140)
Status: Failure
Check console output at https://builds.apache.org/job/Syncope-trunk/140/ to
view the results.
The Apache Jenkins build system has built Syncope-trunk (build #141)
Status: Still Failing
Check console output at https://builds.apache.org/job/Syncope-trunk/141/ to
view the results.
Hi,
I am currently working on a JAAS based authentication for the CXF Secure
Token Service. Colm had already built custom login code for STS. So
after the switch to JAAS I wonder if there would be interest in a
general JAAS login module that talks to Syncope as backend?
We could implement
There could be some overlap but I am not sure how much. The issues in
the roadmap sound mostly like authentication to access syncope.
What I have in mind is authentication for other apps with syncope as a
auth backend.
Of course you might want to investigate using JAAS for authentication to
Hi Francesco,
I'm not sure what you're referring to - could you be more specific?
Colm.
On Thu, Mar 7, 2013 at 12:45 PM, Francesco Chicchiriccò ilgro...@apache.org
wrote:
Hi all,
I have just noticed that the root XML element when listing policies via
CXF is
policys
instead of
You can use some regex for changing all the xml tags
Murat ÇOLAK
2013/3/7 Francesco Chicchiriccò ilgro...@apache.org
Hi all,
I have just noticed that the root XML element when listing policies via
CXF is
policys
instead of
policies
I couldn't easily (= grep) find how to change
Have just spotted it,
I think it is the side-effect of using explicit collections as
responses, example,
@GET
ListPolicy getPolicies() {}
The provider has to guess the name, by default it adds 's' to the class
name, and in this case it ends up being Policys.
One other reason why
Policies
Hi Francesco,
As Sergei already explained, JAXB produces this name from annotation
@XmlRootElement(name = policy) in PolicyTO class.
In case of ListT extends PolicyTO it adds s suffix to root element name.
I will care about the solution.
Regards,
Andrei.
-Original Message-
From:
16 matches
Mail list logo
