Create static inner implementation classes for pageObject interfaces defined in classes

[tobiasstamann]

To prevent naming conflicts it could be great if page object implementations for page object interfaces defined inside a class would also be created as static inner classes .

for example:

PageObjectClass.InnerPageObjectInterface would be created as PageObjectClassImpl.InnerPageObjectInterfaceImpl

This usually shouldn't affect users of the framework. There's just one exception if Implementation Classnames are used explicitely in default methods of PageObject

[tobiasstamann]

Doing this really blows complexity up. Perhaps it's easier to prefix the implementations class name with the embedding class name. By doing this the main requirement - having unique non conflicting implementation class names - would be achieved.
Nevertheless, it also has a drawback : Implementation class names cannot easily be guessed if you need to manually create an instance of a PageObject or a DataObject.
One thing to circumvent this could be by providing a method to create an instance for an interface class.