core icon indicating copy to clipboard operation
core copied to clipboard

Wicketstuff console doesn't work on tomcat

Open kathuriasumit opened this issue 12 years ago • 4 comments

I am trying to launch scala REPL using console project in wicket application(tomcat container) and getting the following error.

Failed to initialize compiler: object scala not found. ** Note that as of 2.8 scala does not assume use of the java classpath. ** For the old behavior pass -usejavacp to scala, or if using a Settings ** object programatically, settings.usejavacp.value = true.

settings.usejavacp.value = true is already getting set in ScalaEngine class. Can someone please help me in resolving this issue?

kathuriasumit avatar Jan 11 '13 09:01 kathuriasumit

Which part of the console do you need ? It provides integration with several languages. Maybe you can just disable the broken Scala engine. Or you need specifically Scala ?

martin-g avatar Jan 11 '13 10:01 martin-g

It's been quite some time since I developed the wicket console (and I'm a bit out of the wicket community nowadays), but if I remember correctly, there were some serious classpath issues, so I was not able to get it running on Tomcat (Jetty worked fine). I would have thought I had documented that somewhere.

Maybe somebody could try to migrate it to a newer Scala version, but I guess it'll be quite some work, as they changed the Scala compiler/interpreter implementation in Scala 3.

Sorry. Maybe you could use Jetty or Groovy.

Nick

2013/1/11 Martin Grigorov [email protected]

Which part of the console do you need ? It provides integration with several languages. Maybe you can just disable the broken Scala engine. Or you need specifically Scala ?

— Reply to this email directly or view it on GitHubhttps://github.com/wicketstuff/core/issues/187#issuecomment-12138121.

cretzel avatar Jan 11 '13 11:01 cretzel

And with "so I was not able to get it running on Tomcat" I just meant the Scala interpreter. To be clear, the wicket console as a whole runs on Tomcat, and the exception is thrown just when the Scala interpreter is executed explicitely.

2013/1/11 Nick Wiedenbrück [email protected]

so I was not able to get it running on Tomcat

cretzel avatar Jan 11 '13 11:01 cretzel

Documentation of this issue can now be found here: https://github.com/wicketstuff/core/wiki/Console

2013/1/11 Nick Wiedenbrück [email protected]

And with "so I was not able to get it running on Tomcat" I just meant the Scala interpreter. To be clear, the wicket console as a whole runs on Tomcat, and the exception is thrown just when the Scala interpreter is executed explicitely.

2013/1/11 Nick Wiedenbrück [email protected]

so I was not able to get it running on Tomcat

cretzel avatar Jan 11 '13 11:01 cretzel