Message Boards

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

Encoding problem

Combination View Flat View Tree View
Threads [ Previous | Next ]
toggle
Encoding problem
Answer
3/8/13 10:33 AM
Hello,

I'm facing a problem with the encoding. I created an XSL file to generate the XMLPF files from XML files I've but the problem is I have this problem

the war file deploys and I can see it form the Liferay Portal but when I try to add something I've this message:

No CategoryTypes exists with the primary key 0

and when i browse the database I find the row was successfully inserted

My JBoss debug

""

ERROR [http--127.0.0.1-8080-5][Bea nPropertiesImpl:337]
jodd.bean.BeanException: Simple property not found: astring Invalid
property: 'test#astring ' (actual:'test#astring ',
forced=false)
13:54:34,304 INFO  (http--127.0.0.1-8080-5)
jodd.bean.BeanException: Simple property not found: astring Invalid
property: 'test#astring ' (actual:'test#astring ',
forced=false)
""

After verifying the encoding from Notepad++ I found that the generated XML file has UTF-8 encoding and the XML file created from the create.bat is UTF-8 without BOM
Is there any way to make it ? only The dateTime works !!

PS: attached the source xml file "test-T.xml"
the xsl file : test.xsl
the result file : result.xml ( the UTF-8 problem)

Thanks alot
Attachments: result.xml (1.2k), test.xml (0.3k), test.xsl (2.7k)
Flag

RE: Encoding problem
Answer
3/8/13 11:17 AM as a reply to Mido Me.
      Hola Mido,

                 I have tested result.xml and seems to be Ok, don't see any coding issue and sintax is Ok also.  This jodd bean Exception, I have seen it before and dont look to have something to do with encoding.  I will try to see this weekend what it is.

     Saludos, Jack.
Flag

RE: Encoding problem
Answer
3/8/13 1:08 PM as a reply to Jack A. Rider.
ok thanks alot
and please let me be updated when you find anything emoticon
Flag

RE: Encoding problem
Answer
3/9/13 8:46 PM as a reply to Mido Me.
   Hola Mido,

         Finally seems that the only problem was that you used a reserved word in an field name "string". Just changed it for "myTestString" and everything worked like a charm.

       Find attached the changes. Let me know how it went.

     Saludos, Jack.
Attachments: result.xml (1.2k)
Flag

RE: Encoding problem
Answer
3/12/13 1:12 PM as a reply to Jack A. Rider.
Hii,
Thanks alot for your answer. Actually, it works now ^^ but I have another question ( I know I'm bothering you alot emoticon )

For the database names can I use special caracters like "_" or it has to be 100% pure text ? because I had alot of problems when I give names to  <name> that contains _

Thanks again
Flag