you are right
both
http://localhost:5080/openmeetings/services/services
and
http://localhost:5080/openmeetings/services/services/
display the list of SOAP services but zero REST services :(
would appreciate any help on resolving this :(
OK, I'll try I'm in Novosibirsk GMT+7
will check freenode
Hi
On 19/08/16 17:50, Maxim Solodovnik wrote:
you are right
both
http://localhost:5080/openmeetings/services/services
and
http://localhost:5080/openmeetings/services/services/
display the list of SOAP services but zero REST services :(
would appreciate any help on resolving this :(
try adding
Hi Max
To have WADL links you need to add cxf-rt-rs-service-description
Can you try again please with 3.1.8-SNAPSHOT
Cheers, Sergey
On 19/08/16 04:15, Maxim Solodovnik wrote:
hmm,
just have tested, not working :( details:
libraries in classpath
I'm not sure how much the ext and the core loggers are out of sync by
now to be honest but the one thing I've spotted is that yes the ext
loggers will log the binary blobs - while the core interceptors disable
it by default,
see 'showBinaryContent' (default is false) - the interceptors will
you can download binary snapshot from here
https://builds.apache.org/view/M-R/view/OpenMeetings/job/Openmeetings%203.2.x/146/
extract it to some new folder
run red5.sh (red5.bat) (or red5-debug.sh (red5-debug.bat))
go to http://localhost:5080/openmeetings/services/
this will result empty page
Hi Max
On 19/08/16 13:56, Maxim Solodovnik wrote:
you can download binary snapshot from here
https://builds.apache.org/view/M-R/view/OpenMeetings/job/Openmeetings%203.2.x/146/
extract it to some new folder
run red5.sh (red5.bat) (or red5-debug.sh (red5-debug.bat))
go to
Can you open some jiras to document the requirements that are not
implemented now?
How should logging the binary contents work? As a switch or should we
simply never log binaries?
Christian
On 19.08.2016 11:42, Sergey Beryozkin wrote:
Hi Christian
As discussed on IRC, IMHO marking core
Vassilis,
Thank you for the input, I resolved this already thanks to Sergey - you
simply have to cleanup really all JaxRS annotations from the
implementing class/methods/parameters etc., then it is working as desired!
I accidentally left the @QueryParam at the last parameter and that
caused
Hi Christian
As discussed on IRC, IMHO marking core LoggingInterceptors as deprecated
in 3.2.0 (which is what you suggested below) can be very reasonable.
The problem I've spotted now is that the ext/'new' interceptors do not
support some features that the core/'old' interceptors do, which
just have tried:
webapps/openmeetings/WEB-INF/lib/cxf-core-3.1.8-SNAPSHOT.jar
webapps/openmeetings/WEB-INF/lib/cxf-rt-bindings-soap-3.1.8-SNAPSHOT.jar
webapps/openmeetings/WEB-INF/lib/cxf-rt-bindings-xml-3.1.8-SNAPSHOT.jar
for some unknown reason d != null in this line :(
d == ServletDestination
endpointInfo == BindingQName={http://apache.org/cxf/binding/jaxrs}binding,
ServiceQName=, QName={
http://webservice.openmeetings.apache.org/}CalendarWebService
path == "/"
not sure why endpointInfo is like this :(
On
OK, I have tried one of the demos we ship with CXF,
jax_rs/description_swagger2_web which uses Tomcat 7 plugin, its
CXFServlet has "/app/*".
If I try:
http://localhost:9000/app/services/
then I do get the services page back but I also see in the logs:
WARNING: Can't find the the request for
Hi,
We have a requirement to apply XSLT to incoming request XML and outgoing
response XML within CXF interceptors (to avoid changes to the endpoint code).
We have used the following approach to modify the response XML and would
appreciate your comments to see whether this is an acceptable
Actually I can see no difference between
http://localhost:5080/openmeetings/services
and
http://localhost:5080/openmeetings/services/
The weird thing is: CalendarWebService has annotation
@Path("/calendar")
BUT
http://localhost:5080/openmeetings/services/calendar?_wadl
results to d== null
id
I have CXFServlet configured in web.xml [1]
and spring config: [2]
Additionally each service has annotations (for ex: [3])
something like this
[1]
https://github.com/apache/openmeetings/blob/3.2.x/openmeetings-web/src/main/webapp/WEB-INF/web.xml#L32
[2]
Hmm...,
On 19/08/16 16:51, Maxim Solodovnik wrote:
Actually I can see no difference between
http://localhost:5080/openmeetings/services
and
http://localhost:5080/openmeetings/services/
The weird thing is: CalendarWebService has annotation
@Path("/calendar")
can you remind me please how you set
Right so in [2] this is what I meant, you have a CXF Destination
available at "/" - JAX-RS takes care of selecting the right class/method
at a later stage.
I'm not sure now what to do there. In my demo I saw no warning without a
trailing slash and all worked well but in your case you are
both 3.1.7 and 3.1.8-SNAPSHOT behave the same
http://localhost:5080/openmeetings/services/services (and
http://localhost:5080/openmeetings/services/services/)
has the full list of SOAP services and following block for REST
Available RESTful services:
Endpoint address:
18 matches
Mail list logo