[Ws Wiki] Update of "FrontPage/WsFx/wss4jLonger" by werner

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ws Wiki" for change notification.

The following page has been changed by werner:
http://wiki.apache.org/ws/FrontPage/WsFx/wss4jLonger

New page:
= Long(er) term goals =

n this article we list and discuss new log-term features and enhancements or those
features or enhancements that need more discussion, thorough design, or
synhcronisation with associated project. The structure of this article is similiar
to the WSS4J FAQ: each feature gets a name, an entry in the table of contents, and a
detailed description followed by the discussion. Each detailed description and
discussion entry shall bear the author's name.

 1. [#api Consider enhancements to the APIs]
 1. [#jaxb Support JAX-B generated types from WS-Security schema]
 1. [#dom Study feasibility of signature/encr without need for DOM (stax?)]
 1. [#wspolicy Use WS-SecurityPolicy as a configuration API?]
 1. [#jceprovider Plugable JCE providers]
 1. [#callback Provide generic callback mechanism to support clients]

[[Anchor(api)]]
==== Consider enhancements to the APIs ====
Author: Fred (Fred Dushin)

Some description here.

[[Anchor(jaxb)]]
==== Support JAX-B generated types from WS-Security schema ====
Author: Fred (Fred Dushin)

Some description here.

[[Anchor(dom)]]
==== Study feasibility of signature/encr without need for DOM (stax?) ====
Author: Fred (Fred Dushin)

Some description here.

[[Anchor(wspolicy)]]
==== Use WS-SecurityPolicy as a configuration API? ====
Author: Fred (Fred Dushin)

Some description here.

[[Anchor(jceprovider)]]
==== Plugable JCE providers ====
Author: ??

Use other JCE providers than BC

[[Anchor(callback)]]
==== Provide generic callback mechanism to support clients ====
Author: George (George Stanchev), Fred

''George:'' Here is the use case - I have build a WS-Trust client and in some cases I need to be
able to refer from the body of the message to security tokens genarated by wss4j (for
example X509 certs in signature, username tokens, etc). The particular case I have is
the wst:On``Behalf``Of element which can either contain the token or have a 
wss:Security``Token``Reference pointing to the wsu:Id of the token. I think wss4j should
provide a way to either use pre-generated pool of wsu:Ids for identifying wss nodes
or has a callback may be that allows the client to supply wsu:Id at process time.

''Fred:'' I've been trying to think about a callback mechanism on the processing  
side, as well.  I see we've gotten a few requests for being able to  
track the data that's been signed or encrypted, and I think using  
callbacks gives the user a lot more flexibility than by providing data  
structures, after an event has occurred.

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@ws.apache.org
For additional commands, e-mail: general-help@ws.apache.org