Hi,
I've just committed basic version of logbrowser [1] (described by my proposal).
I also created sample application [2] for easy testing all parts of
the project.
However it's more or less what user have to do to integrate logbrowser
into his application.
Detailed description, how to run sample
What are the current WSDLPublish capabilities in CXF? Obviously WSDL can be
obtained by adding ?wsdl to a service URL, but I was wondering if it is
possible to configure CXF to have a separate port dedicated to serving WSDL
information. This is particularly useful when serving up WSDL for a secu
Jim,
My gut feeling is that this validation and exception belong in the
MAPAggregator, not the PolicyInInterceptor. If Addressing is required, the
addressing layer should throw the appropriate addressing fault.
Dan
On Jul 5, 2010, at 4:02 AM, jim ma wrote:
> Hi all ,
>
> When I ran a serv
On Wed, Jul 7, 2010 at 8:48 AM, Daniel Kulp wrote:
> Jim,
>
> My gut feeling is that this validation and exception belong in the
> MAPAggregator, not the PolicyInInterceptor.
The validation part is in PolicyVerificationInterceptor not
PolicyInInterceptor.
The MAPAgggregator tracks the adderssin
Sorry, was reading it on my iPhone and the traces didn't display very well.
I would challenge the test. There isn't anything in the spec that says the
addressing stuff needs to be processed before calling the handlers. (example:
addressing COULD be implemented as handlers) Thus, the handl
I've restructured the JiBX code generation from schema to make it easier
to use from other tools. Nilupa, you should be able to use this to
integrate JiBX code and binding generation in with CXF's code generation
from WSDL.
JiBX code generation still uses the org.jibx.schema.codegen.CodeGen
c
