You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by Daniel Kulp <dk...@apache.org> on 2010/10/08 19:04:43 UTC
Musings for 2.4
OK. Now that 2.3 is up for a vote, time to start thinking about 2.4 a bit.
Here are some of my thoughts of things to work on:
1) Updates to newer versions of XmlSchema and WSS4J. I'd like to work closely
with those folks to get XmlSchema 2 and WSS4J 1.6 ready for use with CXF.
XmlSchema 2 would allow removal of some of our hacks. WSS4J 1.6 would allow
us to fix some of the JIRA issues as well as introduce some new API's and such
for performance and possible REST uses.
2) Integration of the GSoC projects - the GSoC projects produced some good
code and ideas and I'd like to get them into a release. They just were not
QUITE ready for 2.3.
3) OSGi things - I have a git branch that started turning all the modules into
OSGi fragments so we could use those instead of the big bundle depending on
what people needed. That could be a good start. Also, the "OSGiBus" thing
could be discussed more.
4) The HTTP async client stuff that I stuck on a branch. That could help with
Camel/SMX integration and other async usecases. Needs some more work though.
What other thoughts do people have?
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
Re: AW: Musings for 2.4
Posted by Harmanpreet Singh <ha...@gmail.com>.
Sent from my Palm Pre on the Now Network from Sprint
On Oct 8, 2010 1:42 PM, Oliver Wulff <oliver.wulff@sopera.com> wrote:
- STS support on the server side
- Enhanced security token processing in WSS4J (custom BinarySecurityTokens, Kerberos)
- SAML 1.1 / 2.0 (signed, unsigned assertions)
- WSDL 2.0, enhanced MEP (like Robust In-Only)
- Load balancing features (similar to FailoverStrategy)
Cheers
Oli
________________________________________
Von: Daniel Kulp [dkulp@apache.org]
Gesendet: Freitag, 8. Oktober 2010 19:04
An: dev@cxf.apache.org
Betreff: Musings for 2.4
OK. Now that 2.3 is up for a vote, time to start thinking about 2.4 a bit.
Here are some of my thoughts of things to work on:
1) Updates to newer versions of XmlSchema and WSS4J. I'd like to work closely
with those folks to get XmlSchema 2 and WSS4J 1.6 ready for use with CXF.
XmlSchema 2 would allow removal of some of our hacks. WSS4J 1.6 would allow
us to fix some of the JIRA issues as well as introduce some new API's and such
for performance and possible REST uses.
2) Integration of the GSoC projects - the GSoC projects produced some good
code and ideas and I'd like to get them into a release. They just were not
QUITE ready for 2.3.
3) OSGi things - I have a git branch that started turning all the modules into
OSGi fragments so we could use those instead of the big bundle depending on
what people needed. That could be a good start. Also, the "OSGiBus" thing
could be discussed more.
4) The HTTP async client stuff that I stuck on a branch. That could help with
Camel/SMX integration and other async usecases. Needs some more work though.
What other thoughts do people have?
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
AW: Musings for 2.4
Posted by Oliver Wulff <ol...@sopera.com>.
- STS support on the server side
- Enhanced security token processing in WSS4J (custom BinarySecurityTokens, Kerberos)
- SAML 1.1 / 2.0 (signed, unsigned assertions)
- WSDL 2.0, enhanced MEP (like Robust In-Only)
- Load balancing features (similar to FailoverStrategy)
Cheers
Oli
________________________________________
Von: Daniel Kulp [dkulp@apache.org]
Gesendet: Freitag, 8. Oktober 2010 19:04
An: dev@cxf.apache.org
Betreff: Musings for 2.4
OK. Now that 2.3 is up for a vote, time to start thinking about 2.4 a bit.
Here are some of my thoughts of things to work on:
1) Updates to newer versions of XmlSchema and WSS4J. I'd like to work closely
with those folks to get XmlSchema 2 and WSS4J 1.6 ready for use with CXF.
XmlSchema 2 would allow removal of some of our hacks. WSS4J 1.6 would allow
us to fix some of the JIRA issues as well as introduce some new API's and such
for performance and possible REST uses.
2) Integration of the GSoC projects - the GSoC projects produced some good
code and ideas and I'd like to get them into a release. They just were not
QUITE ready for 2.3.
3) OSGi things - I have a git branch that started turning all the modules into
OSGi fragments so we could use those instead of the big bundle depending on
what people needed. That could be a good start. Also, the "OSGiBus" thing
could be discussed more.
4) The HTTP async client stuff that I stuck on a branch. That could help with
Camel/SMX integration and other async usecases. Needs some more work though.
What other thoughts do people have?
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
Re: Musings for 2.4
Posted by Benson Margulies <bi...@gmail.com>.
? are we sure it isn't '3.0' ?
On Fri, Oct 8, 2010 at 1:04 PM, Daniel Kulp <dk...@apache.org> wrote:
>
> OK. Now that 2.3 is up for a vote, time to start thinking about 2.4 a bit.
> Here are some of my thoughts of things to work on:
>
> 1) Updates to newer versions of XmlSchema and WSS4J. I'd like to work closely
> with those folks to get XmlSchema 2 and WSS4J 1.6 ready for use with CXF.
> XmlSchema 2 would allow removal of some of our hacks. WSS4J 1.6 would allow
> us to fix some of the JIRA issues as well as introduce some new API's and such
> for performance and possible REST uses.
>
> 2) Integration of the GSoC projects - the GSoC projects produced some good
> code and ideas and I'd like to get them into a release. They just were not
> QUITE ready for 2.3.
>
> 3) OSGi things - I have a git branch that started turning all the modules into
> OSGi fragments so we could use those instead of the big bundle depending on
> what people needed. That could be a good start. Also, the "OSGiBus" thing
> could be discussed more.
>
> 4) The HTTP async client stuff that I stuck on a branch. That could help with
> Camel/SMX integration and other async usecases. Needs some more work though.
>
> What other thoughts do people have?
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://dankulp.com/blog
>