reverseengineering problem

[jetzzz]

I am useing eclipse 3.1.2, jboss 4.0.4RC1 and seam 1.0 beta2

and try to use the reverseengineering, just downloaded nightly build 200603141225.

but whenever I want to create hibernate consloe config, eclipse pop out error window with title Hibernate Console

Error
Reason: <no message>

Details
java.lang.NullPointerException
java.lang.NullPointerException:<no message>
java.lang.NullPointerException

I know it really no help to trace the source, but this problem doesn't appear if I use hibernate-tools beta4. anyone has similar problem?

[maxandersen]

please show the full stack trace from the Error Log view.

[destiny84]

I have it too...

I can't create a console configuration anymore either.... :( . Also get the nullpointer exception as soon as I hit the finish button in the console configuration window.

[maxandersen]

stacktrace guys, stacktrace from the error log view

[destiny84]

here it is...sorry, not that used to using eclipse.....

java.lang.NullPointerException
at org.hibernate.tool.hbm2x.XMLPrettyPrinter.prettyPrintFile(XMLPrettyPrinter.java:89)
at org.hibernate.tool.hbm2x.ArtifactCollector.formatXml(ArtifactCollector.java:69)
at org.hibernate.tool.hbm2x.ArtifactCollector.formatFiles(ArtifactCollector.java:59)
at org.hibernate.tool.hbm2x.AbstractExporter.start(AbstractExporter.java:96)
at org.hibernate.eclipse.console.wizards.NewConfigurationWizard.openContentStream(NewConfigurationWizard.java:195)
at org.hibernate.eclipse.console.wizards.NewConfigurationWizard.createHibernateCfgXml(NewConfigurationWizard.java:161)
at org.hibernate.eclipse.console.wizards.NewConfigurationWizard.access$0(NewConfigurationWizard.java:155)
at org.hibernate.eclipse.console.wizards.NewConfigurationWizard$1.run(NewConfigurationWizard.java:111)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113)

[benders]

I had the same problem.
Now I am using an older nightly-build and it is working fine.
I am using:
IDE 200603131851
Hibernate Tool 200603102022

[maxandersen]

fixed the error - will be fixed in an upcoming nightly build (if I can get the stuff committed)