[ http://issues.apache.org/jira/browse/AXIS2-655?page=comments#action_12377559 ]
Frank Cornelis commented on AXIS2-655: -------------------------------------- Ajith, Last minute features indeed make up for an unnecessary risk. I'm using the SVN anyway, so if it's available in SVN then I can do my thing. Until 1.0 has been released, the availability of a patch would be nice so I can put in this feature again in my source tree. Thanks. What I'm a little worried about is that such a feature wouldn't make it into a 1.0.x, but will be postponed until a 1.1, which can take a while. In the meanwhile JAX-WS is offering this feature... and for production systems this really makes the difference when there is the need to choose between JAX-WS or Axis2. I can only hope for a frequence release schedule for Axis2 to keep up with other WS frameworks... Axis2 has a superior design... thus it would be a waste if people had to wait too long for a certain feature to make it into a release. Anyway, it's your call. I'm just an outsider, making some noise every now and then. :) BTW: same interface feature could be applied to the generated xxxCallbackHandler class at the client-side. > Generated Skeleton difficult to use > ----------------------------------- > > Key: AXIS2-655 > URL: http://issues.apache.org/jira/browse/AXIS2-655 > Project: Apache Axis 2.0 (Axis2) > Type: Improvement > Reporter: Frank Cornelis > > When generating code starting from a WSDL you end up with a Skeleton. The > idea is to use this 'xxxSkeleton' to create your own 'xxxImpl', hence the > name skeleton I guess... > But, the problem with this is that this generated skeleton class is hardcoded > in a cast in in the generated xxxMessageReceiverInOut. So copying the > skeleton to your own Impl and letting services.xml point to this new Impl > 'ServiceClass' simply won't work. It really has to be 'xxxSkeleton'. So why > make it configurable in services.xml if it's hardcoded anyway? I also don't > thing I should manually change 'xxxMessageReceiverInOut' for each new 'Impl' > class I want to try out. Also, each time I run my codegen, the skeleton is > overwritten... is simply doesn't work this skeleton thing... it's pointless... > Also, it would be much better if you would have a nicely generated interface > to implement, instead of that skeleton thingy. The generated skeleton should > implement this interface. The 'xxxMessageReceiverInOut' should cast to the > interface type instead of cast to the 'skeleton'. That way you can point to > whatever 'xxxImpl' you want to, as long as you implement the correct > interface. Another benefit of using this interface approach is that a change > in the WSDL is directly reflected in a change of the interface you have to > implement. Thus you detect required changes in the 'Impl' during compilation > instead of runtime. > The above issues are really critical for Axis2 to be fully usable in a > production environment. If JAX-WS can do it, Axis2 should too. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
