Hi, Sorry once again I missed the call. There was a company meeting yesterday.
2006-10-03 - John will post to the dev list with information about > signing releases. > Note: Chinthaka posted the following link after the meeting: > http://wiki.apache.org/ws/FrontPage/Axis2/releases/steps > 2006-10-10 > John: No status. > 2006-10-17 > John: Chinthaka posted an Axis wiki page. I found an Apache page that > I'll post to the list. > Lawrence: Should we all have keys? > John: Yes. Every artifact that Apache distributes should be signed. All the contributors may not have keys, but the release manager (I assume John) must have keys ready. And it is better if his key is signed by various parties so that the trustability of his key is high. This is required as when people download releases they have to make sure they got it from the right trust-worthy party. > 2. Milestone (M7) Status - John Kaputin > > John: Chinthaka asked about Woden serialization. We may need to add this > to M7. > Lawrence: I think this should be deferred unless it's an absolute > requirement for Axis2. We may need to get a resource from Axis2 to help > with this work or we'll have to drop some other items from the plan. Well, let me explain why we need this. When there is a service deployed with a wsdl in it, we create the woden model and we keep a pointer to that within the service. When there is a request to display the original wsdl, for example we get ?wsdl2 request, then we need to serialize the woden model. I wouldn't make this a blocker for Axis2 but it is critical. Getting resource from Axis2 these days will be bit difficult as we are working hard for the release these days. I hope Oshani can give a helping hand a bit here as she was working with wsdl -> Woden part and it is the exact opposite. -- Chinthaka
signature.asc
Description: OpenPGP digital signature
