Yes, with current CXF generation codes, I could see only in/out jaxb
classes are generated in WrapperClassGenerator (if I did not miss anything
here ;-))
But, think that it is required to generate the fault jaxb class per the
description in 3.7 Service Specific Exception, XmlAccessType.FIELD will
Yeah, I must admit CXF does't exactly follow the JAXWS spec 3.7, that's could
be issues when use code-first way with exception.
Could you please create a jira to track this issue, and patch are welcomed, as
always.
Thanks
Freeman
－
Freeman(Yue) Fang
Red Hat, Inc.
FuseSource is now
Hi,
There is a concern that these temporary files are written out to the
file system without any protection. And I was wondering if we can add
an option to enable encryption for the stream output and keep the key
in the COS instance so that only that COS instance can later read the
data from the
Hi Aki,
Basically I'm +1 for this good idea. Just a little bit concern about the
performance impact.
Could we add a flag to enable this encryption behavior? By default the value is
false, so keep same behavior as is, and users can explicitly enable it if they
need a higher secure runtime.
Hi Freeman,
yes. This should be an option and disabled by default.
I am thinking about introducing a system property
org.apache.cxf.io.CachedOutputStream.something to set the cipher
transformation name to enable this option.
regards, aki
2012/10/18 Freeman Fang freeman.f...@gmail.com:
Hi Aki,
Using the system property will effect CXF instance across the JVM.
It could be good if we can do it on the bus level.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com
Yeah, endpoint property should be good.
－
Freeman(Yue) Fang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://fusesource.com | http://www.redhat.com/
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
http://blog.sina.com.cn/u/1473905042
weibo:
On Oct 18, 2012, at 8:31 AM, Aki Yoshida elak...@gmail.com wrote:
Hi,
There is a concern that these temporary files are written out to the
file system without any protection. And I was wondering if we can add
an option to enable encryption for the stream output and keep the key
in the COS
Hi,
but using a bus or EP prop, we will need a new method in COS to pass
this encryption option. And we will need to change the current code in
many places to make sure that this new method is used to prevent an
unintended plain output written from somewhere. So, I see some
drawbacks. Maybe, we
On 18/10/12 15:38, Aki Yoshida wrote:
Hi,
but using a bus or EP prop, we will need a new method in COS to pass
this encryption option. And we will need to change the current code in
many places to make sure that this new method is used to prevent an
unintended plain output written from
Hi all
The following issues were fixed:
FEDIZ-17Current Fediz STS exposes SOAP 1.1 end point
FEDIZ-18Make supported claims configurable in FileClaimsHandler
FEDIZ-25Look for fediz_config.xml in catalina base too
FEDIZ-20Maintain authentication state (Prevents using the same Fediz
+1
Freeman
－
Freeman(Yue) Fang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://fusesource.com | http://www.redhat.com/
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
http://blog.sina.com.cn/u/1473905042
weibo: http://weibo.com/u/1473905042
On 2012-10-18, at
Hi Oliver
I have make Fediz working long time ago. But I still can not figured out
why do I need to generate so many SSL certs. How do you explain this when
you are facing the people like me. Any document improvement release?
Regards,
Hua Jie
On Fri, Oct 19, 2012 at 2:02 AM, Oliver Wulff
13 matches
Mail list logo
