[Riyad Kalla]

… did you just rename the dir or reinstall Java entirely?

If you just renamed the dir I would encourage you to totally uninstall the JDK and reinstall it… your registry values (HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft) are probably all wrong if you just renamed the dir.

[elmilo]

Well,

I just ran JBoss 4 from eclipse instead, pointing at my JBoss 3 installation, and that worked first time using the same JDK 😀

No idea why 3 doesn’t work, but as long as i can debug and deploy to try this out that’s fine for the time being.

But would be nice to know what this problem is?

cheers
Paul

[elmilo]

Hey,

sorry, replied to the wrong thread a second ago!!

I’ve just run JBoss 4 from eclipse, pointing to my JBoss 3 installation, and it works fine first time using the same JDK!

If you find any reason why this didn’t work it would be great to know what the problem is. Wrong xml parser assigned to the 3 installation?

cheers

[Riyad Kalla]

Paul,
This was a strange one to say the least… I’ll send it off to the dev team to see what the issue was, I guess something changed in the last release of JBoss 3.2.5 that broke the connector.

I really appreciate you hanging in there so long and trying so many things, I’m glad you got it figured out.

[Scott Anderson]

Elmilo,

Which version of MyEclipse are you running? I just tried the internal 3.8 GA release candidate on JBoss 3.2.5 and it works just fine. However, changes to the JBoss connector were made for JBoss 3.2.4 and those changes are available in 3.8 Beta 2.

[Author]

Posts