Hi,
I proposed not to remove InternalView class but only modify
ViewHandlerImpl in trinidad-impl - not a public part.
But you probably mean that users use the functionality of registering
InternalView in
org.apache.myfaces.trinidad.render.InternalView.properties and method
Martin,
InternalView is a part of Trinidad's public API, and we cannot just get
rid of it (there are many customers already using it).
So the InternalView is here to stay... We may be able to adapt
InternalView instances to the instances of VDL in the future, but
the most expedient and simple
Hi,
I've created https://issues.apache.org/jira/browse/TRINIDAD-1598
Problem described there was introduced with JSF 2.0 - specification
cleary says that exactly two types of VLD are supported with
implementation : JSP and Facelets.
Trinidad dialog uses a java code for component tree creation
