> Any suggestions on how to proceed?
I probably messed something up in wssec11 while working on the trust/sec-conv
stuff. I committed more changes this morning. I just ran the wssec11 UX
test and it completed fine. Thus, if you could give it another try, that
would be great.
Thanks!
Dan
The easiest way is in your interceptor, do:
private SOAPMessage getSOAPMessage(Message msg) {
SOAPMessage doc = msg.getContent(SOAPMessage.class);
if (doc == null) {
new SAAJInInterceptor().handleMessage(msg);
doc = msg.getContent(SOAPMessage.class);
We have +1 votes from:
dkulp, bharath, bmagulies, eglynn, seanoc, davidb, willem, ffang, cschneider,
ubhole, jgenender, jgawor, sberyozkin
and no other votes. That's 13 +1 votes. Thus, this vote passes. I'll
get the artifacts released to central.
Dan
On Thu February 5 2009 3:27:52
Actually, didn't see +1 votes from jgenender and sberyozkin. Thus, there are
12 +1 votes.
Dan
On Mon February 9 2009 2:02:54 pm Daniel Kulp wrote:
> We have +1 votes from:
>
> dkulp, bharath, bmagulies, eglynn, seanoc, davidb, willem, ffang,
> cschneider, ubhole
>
> and no other votes. That
We have +1 votes from:
dkulp, bharath, bmagulies, eglynn, seanoc, davidb, willem, ffang, cschneider,
ubhole
and no other votes. That's 10 +1 votes. Thus, this vote passes. I'll
get the artifacts released to central.
Dan
On Thu February 5 2009 3:27:16 pm Daniel Kulp wrote:
> (The is
Hi Andy
many thanks - it's much, much easier to navigate now. I hope you can agree that eventually we migth want to split the current JAXRS
page into subpages when much more content gets added to it (multuiparts, client api, etc, etc), but at the moment it looks
perfect
Cheers, Sergey
-
I was my suspicion too and it really was problem. To close discussion I
encouraged myself and introduced {toc} plus renamed page to get rid of
parens. Now it is: http://cwiki.apache.org/CXF20DOC/jax-rs.html
There was only one incoming reference so I changed it too. In case of any
external incomin
Hmm
The toc macro works fine for the FAQ:
http://cxf.apache.org/faq.html
My gut feeling says it's an issue with the title on that page have parens and
stuff in it. I wonder if you tried renaming the page (well, try copying the
page first) to one with a "cleaner" name if it would work
Hi Andy
I like table of contents too , so I guess if Confluence can support large pages then we can indeed avoid creating additional custom
entry pages. I've seen your original update with the TOC and it looked good so if that can be made to work then it would be cool.
That said, over time, we
Hi Sergey,
In opposite to approach you've mentioned, when working with confluence I
heavily rely on {toc} and other automation macros: once you have your titles
as headers (h1, h2...) its for free to get them dynamically computed and
listed using this simple magic spell -- manual TOC creation gets
Hi Andy
I've never used a {toc} macro so I can't comment. But it looks like, if we look
at say
http://cwiki.apache.org/CXF20DOC/jax-ws.html
that a pattern which has been followed so far is to introduce an entry page
which repersents the content and then
each link links to a seperate pageS
Hi all, I try this example
(http://www.jroller.com/0xcafebabe/entry/securing_spring_ws_client_with1)
but I don't know how can it works!
Can you help me?
Kid_79 wrote:
>
> Hi all,
> I'm trying to use cxf and xwss for security.
> In the my example, on cliend side I'm using an interceptor to ap
12 matches
Mail list logo