[wsas-java-dev] Re: Sandesha persistence

[Afkham Azeez]

The separation between these projects may not be 100% clear in all
instances. In such a case, the issues should be reported against WSAS.

Basically, the COMMONS project contains Sandesha2 Persistence and the
Admin UI framework. The Admin UI framework is a common framework which
is shared by WSAS & ESB.

WSFJAVA contains components common across several projects
(WSAS, ESB etc), plus the WSF SDK(this has not been developed yet). The
components we have the moment in WSFJAVA are,
1. tracer - SOAP Message tracing
2. statistics - Statistics gathering and retrieving
3. throttle - Access throttling
4. mex - WS-MetaDataExchange implementation
5. codegen - Generate Java & AJAX clients

Any issues in WSAS which cannot be specifically attributed to WSF or
COMMON should go into WSAS.

Azeez


Paul Fremantle wrote:
> Azeez
> 
> Can you please clear up in my mind what should go into each of the three
> JIRAs:
> 
> http://www.wso2.org/jira/browse/WSAS
> http://www.wso2.org/jira/browse/WSFJAVA
> http://www.wso2.org/jira/browse/COMMONS
> 
> Paul
> 
> 
> Afkham Azeez wrote:
>> We have added a new WSO2 Commons project [1] to JIRA. Please report this
>> issue under the Sandesha2 Persistence component.
>>
>> [1] http://www.wso2.org/jira/secure/project/ViewProject.jspa?pid=10031
>>
>> Paul Fremantle wrote:
>>  
>>> Tijs
>>>
>>> Thanks very much for the feedback.
>>>
>>> We have just set up the infrastructure for you to report bugs:
>>> http://www.wso2.org/jira/browse/WSFJAVA
>>>
>>> The contact is Chamikara who I have copied.
>>>
>>> I believe that the reason we have not committed the code is because it
>>> uses the Hibernate libraries and cannot therefore be committed for legal
>>> reasons. (Apache doesn't accept LGPL code).
>>>
>>> You also might want to look at the WSO2 Web Services Application Server
>>> and WSO2 ESB which both offer the persistent version of Sandesha2 and
>>> are both Apache Licensed Open Source code.
>>>
>>> Paul
>>>
>>> t.rademakers at chello.nl wrote:
>>>    
>>>> Hi Asankha, Paul
>>>>
>>>> I have been looking at the WSO2 Sandesha2 persistence implementation.
>>>> It is looking good to my opinion. But I am getting a few null pointer
>>>> exceptions when running it as-is. With two null checks this was
>>>> resolved, but now I am wondering, is this code ready to test simple
>>>> cases with? As I can't retrieve from the WSO2 website where I can
>>>> report JIRA issues for the Sandesha2 persistence project I am asking
>>>> you this. Is there a contact person within WSO2 for this project?
>>>> By the way, is there an intention to commit the source to the
>>>> Sandesha2 project?
>>>>
>>>> Thanks,
>>>>
>>>> Tijs
>>>>
>>>>
>>>>         
>>
>>
>>  
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Wsas-java-dev mailing list
>> Wsas-java-dev at wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev
>>   
> 


-- 
Afkham Azeez
GPG Fingerprint: 643F C2AF EB78 F886 40C9  B2A2 4AE2 C887 665E 0760

http://www.wso2.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 254 bytes
Desc: OpenPGP digital signature
Url : http://wso2.org/pipermail/wsas-java-dev/attachments/20070101/ac40b4ce/signature.pgp