That's a good point. By default, services start as internal until we demonstrate a need for them to be public, as public implies that they are long-lived and stable. The interface is public, the implementation is not, and with the new @Contribute annotation, its possible to contribute to a service without knowing if it is public or internal. Chances are, we just need to update the documentation.
On Sun, May 6, 2012 at 7:44 AM, piotrek <[email protected]> wrote: > hi, > > i'm new to tapestry. here: http://tapestry.apache.org/principles.html i've > read that users should not be forced to use internal api. however here: > http://tapestry.apache.org/beaneditform-guide.html example shows how to > contribute to DefaultDataTypeAnalyzer which is in package > org.apache.tapestry5.*internal*.services > > apparently something is wrong > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/tutorial-breaks-tapestry-s-3rd-principle-tp5689323.html > Sent from the Tapestry - Dev mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
