ansaurus

Question

Spring Open JPA

Answer 1

+1 A:

Ok, so stack trace doesn't specify the actual file name but it looks like one of OpenJPA mapping files.

"No Content allowed in Prolog" exception is usually thrown when there's anything in xml file prior to <?xml declaration - you'll need to look through your files and make sure that's not the case.

Another possible issue that has been known to cause this is when xml encoding is specified as "utf-16" (certain XML tools like to do that). Changing it back to "utf-8" tends to resolve the problem.

ChssPly76 2009-08-04 20:17:34

@ChssPly76I dont have the xml files with me right now to post but I have already tried out these options. <?xml are the first characters in the file and I also use utf-8 and also tried removing it. Actually I tried removing the property tags for the persistence unit so as to see if it could parse the xml and point out the missing information. It did. I found out that if I remove the class entry froom persistence unit this error does not come up. I will post the xml files at the earliest.

Barun 2009-08-05 02:55:53

So you're saying that if you remove one particular class entry from persistence.xml, everything works (well, the class is not getting mapped but I this error doesn't occur)? Perhaps there's something weird is going on with that specific class? Stack trace looks as if repository were trying to obtain metadata for that class but couldn't do it via annotations and was looking for XML version in /WEB-INF/classes...

ChssPly76 2009-08-05 04:28:22

Answer 2

+1 A:

Taking a look at the source and your stack trace (looking at source code can reveal a lot) it seems to be that one of your xml mapping files is where the problem lies.

If you turn on openjpa.MetaData to TRACE level you will see in which file it occurs.

I think you do this by specifying openjpa.Log=openjpa.MetaData=TRACE as a property... though I'm not sure since I specify this via spring and not plain jpa.

It will tell you what file it is processing when the error occurs though I suspect you won't find anything wrong that you can see and there will be strange characters (that you can't see) in the "prolog".

Michael Wiles 2009-08-05 10:47:22

@MichaelHi after setting the openjpa.MetaData to TRACE level I got the logs but still am unable to locate the issue as it is not giving a specific file name but generally referring to the classes folder as a whole. I have updated my post with the updated error log and also my mapping.xml. Can you help me on this?

Barun 2009-08-06 06:40:04

sounds like you need to add the open jpa source, run the system in debug mode and put break points close to where it falls over so you can see what it is doing.

Michael Wiles 2009-08-06 08:54:30

i am currently doing that trying to run in debug mode. But strangely the same war file with the same xmls is working fine in Websphere 7. But in JBoss 5 this error is coming. Now while we use Websphere in production we use JBoss on developer machines. So it needs to work on both the environments. What can be different in the two servers?

Barun 2009-08-06 09:25:09

I share your pain. We did the same thing, dev on jboss, deploy on WAS and there were a handful of instances where they behaved differently! In this case, it probably has something to do with classpath/classloaders in jboss and websphere.

Michael Wiles 2009-08-07 11:11:47

Answer 3

A:

I've seen this recently with JBoss AS 5. The problem was that some component was trying to access a XML file through the VFS (virtual file system), but the path given was a directory. So instead of SAXParser exception, FileNotFound should be thrown.

Check your config, something causes that the wrong path is given to the SAXParser.

Ondra Žižka 2010-06-18 17:01:09

ansaurus

tags:

views:

answers:

Spring Open JPA

related questions