Well, its good to hear things are working on Derby.
Now, I'm assuming the content is displaying correctly. The CMSPortlet has this in it:
String title = (file.getContent().getTitle() != null) ? file.getContent().getTitle() : file.getContent().getName();
So it will display the title of the page, if exists, or show the name of the page. You can specify a title when you edit the content.
How cool is that! I looked in the CMSPortlet source as well - must have missed it. I will try it out later.
Although ... it looks like the title can only be specified from the content file here ... it might be good to allow the CMSPortlet the option to override the title and display the one from the portlet.xml in preference to any set up for content in CMS. My CMSPortlet is displaying some 40 'pages' of html for a training course - and I don't want to have to name each page individually - or have to tell editors to remember to name pages. For this use case I would like to just create the portlet instance and give it a title of "Course: Blah blah" or whatever. I can probably change the code myself - but it might be a useful feature to build in ...
The whole Derby integration has not been too painful - thanks to hibernate for that I guess. Although I have been spotting a few errors and warnings that might be related to Derby in the logs - but they don't seem to be affecting functionality so far - so I'm saving them up for a rainy day ;-)
Yes. I think that logic may work better. Use the title attribute in the repository, and if not use the one from the portlet.xml.
I will create a task for it.