Hi Angel , In the coming hackathon we will make sure NOT to do anymore API changes , package changes , and configuration file changes (so what we have in Axis2 1.2 will be there in Axis2 1.3 as well). In the meantime we will address the issue like not meaningfully exception , java comments etc etc. , and most importantly we will fix critical JIRAs as well.
Thanks Deepal > Hi all, > > apart from the "interface change" problem, which is maybe the biggest > issue we have with Axis2 , and our organization is forced to create > wrapper APIs to protect internal products from having to change their > code, I would add that there are many classes in Axis2 that have to be > marked as "abstract" , but are not. Another issue we encountered is > the very big latency when loading modules from the repository, when it > is supplied as a parameter to the AxisConfigurationContext . I agree > that the documentation is quite poor. Another problem , apart from the > lack of meaningful exceptions is the hardcoding of some values in the > code, instead of having them defined in a resource properties or a > constants class. > > To cut the long story short - the Axis2 team should just agree on and > stabilize the basic architecture (mostly interfaces & abstract > classes), and not induce big incompatibilities in future releases , > the same applies for configuration files and the like. > > Regards, > Angel > > On 6/7/07, *Michele Mazzucco* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > Dims, > > here we go: > - Documentation is poor: correct, especially for what concerns the > javadoc > - Exceptions are quite obscure: that's why I've created JIRA 2229. > Furthermore sometimes spurious errors occur ( i.e. I remember once > I go a > missing ResourceBundle problem and I spent several days to find > out what > was wrong - and as I understand from the mailing list other people got > similar issues) > - After upgrading from 1.0 to 1.1, config files were not compliant any > more: correct > > and finally I would add: > - Interfaces change even between the same release > - You tend to use reflection even where it's not necessary. This is > painful during the configuration as well as during the debug > > > Michele > > On Wed, 2007-06-06 at 22:31 -0400, Davanum Srinivas wrote: > > Folks, > > > > FYI, > http://www.theserverside.com/discussions/thread.tss?thread_id=45716 > > Please take it with a pinch of salt. There was exactly one question > > from the guy on the mailing list [1] and absolutely no JIRA's > AFAICT. > > > > Guess, it's time to take stock. What say you folks? What are > your pain > > point(s). Am asking because we have to plan for a 1.3 release and > > we'll try to incorporate the feedback from you all for that. > > > > thanks, > > dims > > > > [1] http://marc.info/?l=axis-user&w=2&r=1&s=roch&q=b > <http://marc.info/?l=axis-user&w=2&r=1&s=roch&q=b> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]> > > -- Thanks, Deepal ................................................................ "The highest tower is built one brick at a time" --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
