Jan-Kees van Andel schrieb:
I think I found the problem Matthias referred to. On line 139 in
GroovyWeaver.groovy, I see the following line:
WeavingContext.getRefreshContext().setRecompileRecommended(ScriptingConst.ENGINE_TYPE_JAVA,
Boolean.FALSE);
If I change it into:
Bernhard Huemer schrieb:
If you compile and refresh asynchronously without having old states
of the objects not only the classes you basically exchange classes
and objects in the middle of a request. Ok granted this does not
happen to often but it can happen!
So what happens, is that
Hi Jan I fixed that about two days ago, it should have gone in with the
latest commit.
Bernhard is merging his compiler stuff to clean up that code part a
little bit.
But for me everything for now works.
So give the latest codebase a try.
The fix is absolutely correct. The code was written
Hey,
As promised, I've been testing on my Vista machine. Bernhard was right
about the slashes. I needed to double escape them on some places.
I also changed the paths in my web.xml to point to my workspace, but
I'm not sure what this does, since these are also the default paths
(at least, that's
I think I found the problem Matthias referred to. On line 139 in
GroovyWeaver.groovy, I see the following line:
WeavingContext.getRefreshContext().setRecompileRecommended(ScriptingConst.ENGINE_TYPE_JAVA,
Boolean.FALSE);
If I change it into:
Bernhard Huemer schrieb:
I´d rather have a single pretictable triggering point than having
the compiler being triggered continously in unpredictable manner.
A standalone developer can code and save and can cause continous
errors. But at the time he hits refresh, he can be pretty sure that
his
Under normal no locking circumstances, the beans get
replaced in the middle of the request because someone
else triggered it for the application singleton, which
is probably fine but somewhat dirty because in some
cases this might end up with a temporary classcast
exception which is
Bernhard Huemer schrieb:
Under normal no locking circumstances, the beans get
replaced in the middle of the request because someone
else triggered it for the application singleton, which
is probably fine but somewhat dirty because in some
cases this might end up with a temporary
If you compile and refresh asynchronously without having old states
of the objects not only the classes you basically exchange classes
and objects in the middle of a request. Ok granted this does not
happen to often but it can happen!
So what happens, is that a) the user has to wait in the
What about following hypothetical case
private void doSomething() {
.. long running
C myVar = appContext.getBean(C);
.. long running
}
Okay, first of all, yes, that will eventually result in a
ClassCastException, but there is a different reason for that. If you
circumvent
Jan-Kees van Andel schrieb:
Yeah, so do I, but at work I have to use Windows (at least I have
Cygwin installed) and at home I also like to play recent games. ;-)
But if it's only a file separator issue, I can maybe fix it myself and
build from the sources. (and of course commit it)
Sorry for
I have a Vista workstation at home. I might have some spare time on
Sunday. I'll take a look at it.
/JK
2009/12/11 Werner Punz werner.p...@gmail.com:
Jan-Kees van Andel schrieb:
Yeah, so do I, but at work I have to use Windows (at least I have
Cygwin installed) and at home I also like to
Hey,
but there is another issue regarding Windows yet, I
also have not set the mutexes in the compiler parts
to avoid windows filelocking if more than one user
hits the server.
now I'm not entirely sure anymore what you think this module's usage is
intended to be like or maybe I'm just
Werner, do you know if ext-scripting will work in Mojarra?
---
Kito D. Mann | twitter: kito99 | Author, JSF in Action
Virtua, Inc. | http://www.virtua.com | JSF/Java EE training and consulting
http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info | twitter:
jsfcentral
+1 203-404-4848 x3
Bernhard Huemer schrieb:
Hey,
but there is another issue regarding Windows yet, I
also have not set the mutexes in the compiler parts
to avoid windows filelocking if more than one user
hits the server.
now I'm not entirely sure anymore what you think this module's usage is
intended to
No ext-scripting uses some myfaces impl internals,
the 1.0 version definitely will not work in Mojarra.
The reason for now is we use internals of the impl, to get things going
like the bean reloading of application and session scoped beans.
Those parts are not big and maybe in the end can be
Btw. regarding Bernhard, he is working on similar things
aka dynamic java recompilation - for Spring ...
Since Spring already has Groovy support it does not make
sense to do it again.
;-)
Werner
Bernhard Huemer schrieb:
Hey,
but there is another issue regarding Windows yet, I
also
I´d rather have a single pretictable triggering point than having
the compiler being triggered continously in unpredictable manner.
A standalone developer can code and save and can cause continous
errors. But at the time he hits refresh, he can be pretty sure that
his code should work (well often
Jan-Kees van Andel schrieb:
You rock Werner! If I have the time, I'm gonna give it a try this week!
/JK
Hi Jan it currently works only on the unix side of things,
and you have to adjust the source pickup paths in the web.xml.
(you can locate them easily)
Outside of that it should work out of
So it doesn't work on Windows at all? I currently don't have a Unix
workstation available. :-(
/JK
2009/12/10 Werner Punz werner.p...@gmail.com:
Jan-Kees van Andel schrieb:
You rock Werner! If I have the time, I'm gonna give it a try this week!
/JK
Hi Jan it currently works only on the
https://issues.apache.org/jira/browse/EXTSCRIPT-27
generally, I absolutely prefer linux/unix for development.
windoze is my email device :-)
On Thu, Dec 10, 2009 at 4:11 PM, Jan-Kees van Andel
jankeesvanan...@gmail.com wrote:
So it doesn't work on Windows at all? I currently don't have a Unix
Yeah, so do I, but at work I have to use Windows (at least I have
Cygwin installed) and at home I also like to play recent games. ;-)
But if it's only a file separator issue, I can maybe fix it myself and
build from the sources. (and of course commit it)
/JK
2009/12/10 Matthias Wessendorf
Hello everyone I just wanted to give a small report regarding ext-scripting.
The status looks very good, I am getting very close to a possible alpha
release, I have two big open things (and a handful of minor ones, like
dropping qdox and and class rewriting, and finally fixing the dreaded
+1
regards,
gerhard
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
2009/12/9 Werner Punz werner.p...@gmail.com
Hello everyone I just wanted to give a small report regarding
ext-scripting.
You rock Werner! If I have the time, I'm gonna give it a try this week!
/JK
2009/12/9 Gerhard Petracek gerhard.petra...@gmail.com:
+1
regards,
gerhard
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for
25 matches
Mail list logo
