|
- [CONF] Apache Sling > YAMF - Yet Another Mo... Justin Edelson (Confluence)
- [CONF] Apache Sling > YAMF - Yet Another Mo... Justin Edelson (Confluence)
- [CONF] Apache Sling > YAMF - Yet Another Mo... Justin Edelson (Confluence)
- [CONF] Apache Sling > YAMF - Yet Another Mo... Justin Edelson (Confluence)
- [CONF] Apache Sling > YAMF - Yet Another Mo... Justin Edelson (Confluence)
- [CONF] Apache Sling > YAMF - Yet Another Mo... Vasily Lazerko (Confluence)
- [CONF] Apache Sling > YAMF - Yet Another Mo... Vasily Lazerko (Confluence)
- [CONF] Apache Sling > YAMF - Yet Another Mo... Justin Edelson (Confluence)
- [CONF] Apache Sling > YAMF - Yet Another Mo... Justin Edelson (Confluence)
- [CONF] Apache Sling > YAMF - Yet Another Mo... Justin Edelson (Confluence)
- [CONF] Apache Sling > YAMF - Yet Another Mo... Justin Edelson (Confluence)
- [CONF] Apache Sling > YAMF - Yet Another Mo... Justin Edelson (Confluence)
- [CONF] Apache Sling > YAMF - Yet Another Mo... Justin Edelson (Confluence)
- [CONF] Apache Sling > YAMF - Yet Another Mo... Justin Edelson (Confluence)
- [CONF] Apache Sling > YAMF - Yet Another Mo... Justin Edelson (Confluence)
Hi Vasily Lazerko, these questions are better posted to the sling-dev or sling-users mailing lists.
I'm not sure what you mean by "TLD is not ready". There's no TLD for YAMF and there shouldn't need to be one. This would violate one of the design goals ("Client doesn't know/care that YAMF is involved")
Your description is a bit vague and references a class which doesn't exist. Can you explain in a bit more detail? Is anything logged?