The issue is not do we temp or not.
And controlling this is not hard or hacky. ;-)
e.g. simple jboss-structure.xml will do
or adding a simple ModificationTypeMatcher.
The real issue is why this worked before,
when we always temped everything.
Which is exactly what we do here - we temp - but it doesn't work.
So far I got zero useful information from JBossWeb, old WarDeployer authors, ...
"jason.greene(a)jboss.com" wrote :
| However, I can make a very good educated guess, that tomcat just calls getResource on a standard xhtml request, which is of course going to point to the tmp.
|
Where is this piece of code?
Or where does TC/JBW do a check for if the resource has changed?
That's all I need to know, and I'll dig it up from there.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223990#4223990
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223990
Ales,
I am not completely familiar with the MC internals, but i guess there might be some place where MC already does annotation scanning (for some other requirement maybe) on the MC bean. Maybe MC could at that point itself "register" appropriate annotation plugins on finding the annotation? Is this possible or is CommonAnnotationAdapter the place where this annotation scanning happens for the first time (the only time?).
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223983#4223983
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223983
The moment I have a reponse that matches the following statement, I don't need any more responses. No need to keep list of responses.
lookupSucceeded = (response != null) && !(response instanceof Exception) && !(response instanceof NoHandlerForRPC);
Hence, currently my only state is a boolean arising from that statement and in needMoreResponses(), all I do is return:
return !(lookupSucceeded);
Hence, having response and address in needMoreResponses() would avoid me having to cache that boolean because right now, I only have access to the response in isAcceptable.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223978#4223978
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223978
Ive updated the JBM 2 libs. I would recommend deleting your thirdparty dir.
I can probably reduce these again by removing commom-core and adding the individual libs, but since time is short I'll look at this after Beta.
Also, a few of the new libs are only at CR so these will need updating once A 5.1 is released.
Regarding Maven, if we have to support updating the old repos everytime we need new libs it might be worth while. Maven also lets you download specific jars from a project so it would make our distro smaller. We could still use Ant as the build just have a pom instead of a build-thirdparty.xml. Maybe after Beta.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223948#4223948
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223948