> view could probably provide standard input fields based on the element’s
> properties and scope (fault contract vs. data contract vs. service
> contract).
>
> -
>
> 4. Enlarging the proposal’s scope by including wsimport and by adding a tool
> to
that is not part of an ongoing Apache project is not suitable for the
Apache Mentoring Programme: "The work of a mentee project can be code or
documentation, so long as it contributes to an existing Foundation
project. Individual research or prototyping projects are not acceptable
- working
+1 .. I think the main issue with docs is getting people to do it. While
Dublin Core has been around for a long time adoption in the Web services /
SOA worlds is minimal/non-existent. As such a tool that depends on those
annotations being present will likely see little use.
Marcel, I don't want to
Marcel,
After thinking a bit more about your proposal and combining your ideas
with findings I made some time ago when thinking about best practices
to add documentation to WSDL/XSDs, I would like to make the following
comments:
1. In its present form, your proposal neglects a fundamental
constra
>Two quick questions about your proposal:
>
>- Axis2 supports several binding styles. There is the classic code
>generator (wsdl2java) that supports different data bindings (the
>default ADB, xmlbeans, JIBX,...), but there is also support for JAX-WS
>artifacts generated by wsimport (which is not pa
On Thu, Apr 8, 2010 at 10:20, Heusinger, Marcel
wrote:
> Dear Axis2-developer community,
>
>
>
> some days ago I read about the Apache Mentoring Programme
> (http://community.apache.org/mentoringprogramme.html) and I thought it would
> be a chance to contribute to one of the
Dear Axis2-developer community,
some days ago I read about the Apache Mentoring Programme
(http://community.apache.org/mentoringprogramme.html
<http://community.apache.org/mentoringprogramme.html> ) and I thought it
would be a chance to contribute to one of the Apache projects. As I
