Hi Fred,
I think that is great. We also wrapped wss4j [1] for our WSO2 Data
services [2] product. But there we embedded the dependencies and some of the
dependancies was also exported via the wss4j bundle . But when we are
releasing wss4j as a OGSi bundle, we have to import the dependancies rather
than emdedding them. I was working on that for issue WSS-110, so I commited
the initial work I did for WSS-110 to the trunk. I think we can continue
from there.
thanks,
nandana
[1] - https://wso2.org/repos/wso2/trunk/carbon-orbit/org.wso2.carbon.wss4j/
[2] - http://wso2.org/projects/solutions/data-services/java
[3] - http://issues.apache.org/jira/browse/WSS-110
On Thu, Nov 6, 2008 at 5:57 PM, Fred Dushin <[EMAIL PROTECTED]> wrote:
> One other thing that came up, which I'm looking into today: use the maven
> bind plugin to build an OSGI bundle for WSS4J -- some projects downstream of
> wss4j (CXF, ServiceMix) are adopting OSGI, and rather than having them
> rebundle wss4j, it's probably more correct for WSS4J to do that, itself.
> 3rd party jars are another matter, but I'll investigate that today.
> -Fred
>
>
> On Nov 6, 2008, at 4:50 AM, Nandana Mihindukulasooriya wrote:
>
> I made a good few updates to the webpage that haven't been put online
>> yet. Maybe we should regenerate the website and put it online, given
>> that the online version hasn't been updated in ages?
>>
>
> +1. I think we should fix the point 4.) mentioned by Glen too.
>
> thanks,
> nandana
>
> -----Original Message-----
>> From: Glen Mazza [mailto:[EMAIL PROTECTED]
>> Sent: 05 November 2008 13:40
>> To: [email protected]
>> Subject: Re: svn commit: r711454 - in /webservices/wss4j/tags/1_5_5:
>> pom.xml xdocs/index.xml
>>
>>
>> Thanks, four more things:
>>
>> 1.) On the main page[1], it would be good to remove the reference to
>> the
>> "Axis Deployment Tutorial" at the bottom of the page (and its
>> corresponding
>> skeleton page it links to)--nothing is come of it for years, it is just
>> a
>> dead link.
>>
>> 2.) Also on the main page, to remove the reference to the "API overview"
>> and
>> its corresponding skeleton page after it--the links are all dead.
>>
>> 3.) Also on the main page, to update the Contents section at the top of
>> the
>> page (WS-Security Features and WSS4J Use Cases)--the bottom two links
>> there
>> are dead, and the new info at the bottom needs to be added.
>>
>> 4.) For the "What is WSS4J" section--do you guys implement V1.1 of
>> those
>> specifications also? If so, it would probably be good to switch the
>> links
>> to the PDFs for the 1.1 versions:
>>
>> http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wss#technical
>>
>> Regards,
>> Glen
>>
>> [1] http://ws.apache.org/wss4j/
>>
>>
>>
>> Fred Dushin-4 wrote:
>> >
>> > Author: fadushin
>> > Date: Tue Nov 4 14:36:28 2008
>> > New Revision: 711454
>> >
>> > Merged Colm's POM fixes, and incorporated Glen's web site suggestions.
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/svn-commit%3A-r711454---in--webservices-wss4j-tags
>> -1_5_5%3A-pom.xml-xdocs-index.xml-tp20332821p20341872.html<http://www.nabble.com/svn-commit%3A-r711454---in--webservices-wss4j-tags-1_5_5%3A-pom.xml-xdocs-index.xml-tp20332821p20341872.html>
>> Sent from the WSS4J mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
