Hi Francesco,
np, I did not have a chance to test yesterday too, thanks for a test on
your end,
I suspect a new type has been introduced in one of the other Syncope
services which is added to the collection of types for JAXBContext and
the JAXB context creation fails.
Can you please give me a favor and list all other beans explicitly, I
guess that will not work, and then we can check which service bean is
'to blame' ? If you are busy with something else: then please type the
complete list of beans in the jaxrs:endpoint - I'll have a look right
now then...
Sergey
On 30/04/15 09:06, Francesco Chicchiriccò wrote:
Hi Sergey,
sorry for late notice; I've tested two different configurations on master:
1. untouched configuration, CXF 3.0.4
same situation, empty <grammars/>
2. CXF 3.0.5-SNAPSHOT, applying this patch to
core/rest-cxf/src/main/resources/restCXFContext.xml
Konsole output <jaxrs:server id="restContainer" address="/"
- basePackages="org.apache.syncope.common.rest.api.service,
org.apache.syncope.core.rest.cxf.service"
staticSubresourceResolution="true">
+ <jaxrs:serviceBeans>
+ <ref bean="userServiceImpl"/>
+ </jaxrs:serviceBeans>
e.g. configuring the sole UserService: I confirm it works, as in your case.
Any hint of what I am doing wrong? Thanks.
Regards.
On 29/04/2015 18:48, Sergey Beryozkin wrote:
I've built the master branch, will be looking the first thing tomorrow
morning, should have time before a release...
Thanks, Sergey
On 29/04/15 15:08, Francesco Chicchiriccò wrote:
On 29/04/2015 15:57, Sergey Beryozkin wrote:
Hi Francesco
I've done a local test by copying UserService, AbstractServiceImpl,
UserServiceImpl and keeping read() and list() methods, and also
copying PagedResult, UserTO, and AbstractSubjectTO (and stopping there
are adapting PagedResult accordingly), and I'm seeing a schema being
generated. I think the code I did few days ago is fine, it should only
make the generation better, so I wonder where the problem is.
Can you give me a favor and remind how can I run Syncope in a debug
mode from Maven so that I can hit a breakpoint in WADLGenerator ? this
For Syncope 2.0.0-SNAPSHOT (master branch) - not yet documented,
slightly different than before - you need to
1. mvn -PskipTests from root directory
2. cd fit/core-reference
3. mvn -Pdebug
At this point you can point your browser to
http://localhost:9080/syncope/rest/?_wadl
Or may be you can try and isolate where the problem is, example, does
it get generated for your env if only UserServiceImpl rest service is
registered ?
I'll try and let you know.
By the way I thought you had WADL prepared during a build time ?
In Syncope 1.2.X, WADL is made available at runtime and also generated
at release time, for website publishing at
http://syncope.apache.org/rest/1.2/index.html
In Syncope 2.0.0 we still need to port this latter feature.
Regards.
On 29/04/15 13:30, Sergey Beryozkin wrote:
Hi Francesco
I wonder if it is related somehow to
https://fisheye6.atlassian.com/changelog/cxf?cs=300ace67c507c551b37ba4d99e6863b67bf871f8
I did few days back. Though I'm not immediately seeing how.
I'll have a look shortly, will try to reproduce with a simlplified
version of
https://github.com/apache/syncope/blob/master/core/rest-cxf/src/main/java/org/apache/syncope/core/rest/cxf/service/UserServiceImpl.java
with its list() method only...
Cheers, Sergey
On 29/04/15 12:51, Francesco Chicchiriccò wrote:
Hi,
when using the latest CXF 3.0.5-SNAPSHOT and this configuration [1] I
get an empty
<grammars/>
element when accessing ?_wadl
With 3.0.4 everything works, instead: any relevant configuration
change?
Thanks,
Regards.
[1]
https://github.com/apache/syncope/blob/master/core/rest-cxf/src/main/resources/restCXFContext.xml#L81-L89
