Message Boards

« Back to 2.- Usage ( From Xml file to CRUD Portlet)

Why is the classDef restricted to start with lowercase

Combination View Flat View Tree View
Threads [ Previous | Next ]
toggle
This leads to lowercase classnames which is not against the java codeconventions?

Is there a way to customize this behaviour ?

Thanx
Dieter

RE: Why is the classDef restricted to start with lowercase
Answer
12/1/11 8:03 PM as a reply to Dieter Engelhardt.
Hello Dieter,

True, true, true. Historical, reasons, I dont like this either, and I will try to solveit this weekend .


Saludos, Jack.

RE: Why is the classDef restricted to start with lowercase
Answer
12/1/11 8:44 PM as a reply to Jack A. Rider.
Hi Jack,
this would be great.

By the way,
are you looking for some help?

I might support you with your work.

I checked out the Projekt and i think already found the Problem in xmlportletfactory.xsd:

<xs:element name="fileDef">
<xs:complexType>
<xs:all>
<xs:element name="name" nillable="false">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:minLength value="3"/>
<xs:whiteSpace value="collapse"/>
<xs:pattern value="[a-z]{1}[a-zA-Z0-9]*"/>
</xs:restriction>

Is this the solution???

Thanx,
Dieter

RE: Why is the classDef restricted to start with lowercase
Answer
12/1/11 9:23 PM as a reply to Dieter Engelhardt.
Thanks Dieter,


Your help is needed and greatly apreciated, I will get in touch with you via mail so we can coordinate, and get you up to date on ongoing works.

On the other hand, <xs:pattern value="[a-z]{1}[a-zA-Z0-9]*"/> is there so no body can start with upper case, there are some velocity templates that generate wrong code if so.

The thing I plan to do is to change the xsd so can use uppercase, generate diferents proyects, that have all the diferent functions and field types, and correct problems as arise. Simple but little boring.

Saludos, Jack.

[SOLVED]RE: Why is the classDef restricted to start with lowercase
Answer
12/10/11 6:21 PM as a reply to Dieter Engelhardt.
Hello Dieter,

I forgot to reply the post, and community may not be aware, but as we already spoked this should be resolved with version v1.9 already uploaded to Sourceforge.net, december 4.

See annoucement: New XMLPortletFactory version on SourceForge (December 4, 2011)

Saludos, Jack.