[JBoss Microcontainer Development POJO Server] - Re: Seam deployments and hot deployments in AS 5.1.0
by jeff.haynes@q9.com
I was experiencing the same problem as described in this thread, but I think there's a pretty simple workaround that I'm now using (until the 5.2 comes out with the new deployers code). I'm also deploying my exploded war file using Eclipse and was seeing the *.jsfdia and *.spdia files being deployed to my WEB-INF directory along with everything else.
The simple workaround? Just put an exclude directive in your build.xml to make sure the *.jsfdia and *.spdia files are not being deployed with your exploded application. I'm using an Eclipse project that I set up using seamgen, but for anyone else using something different, I'm sure you can use a similar approach.
Here's the appropriate portion of my build.xml file:
| <target name="war" depends="compile"
| description="Build the WAR structure in a staging directory">
|
| . . .
|
| <copy todir="${war.dir}/WEB-INF">
| <fileset dir="${basedir}/resources/WEB-INF">
| <include name="*.*"/>
| <exclude name="*.*dia"/>
| <include name="classes/**/*.*"/>
| <exclude name="classes/**/*.class"/>
| </fileset>
| </copy>
|
| . . .
|
| </target>
|
My environment:
jdk1.6.0_16
Eclipse 3.4.2
JBoss AS 5.1.0.GA
Seam 2.2.0.GA
RichFaces 3.3.1.GA
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257985#4257985
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257985
15 years, 2 months
[JBoss XML Binding Development] - Re: XB profiling during the AS start-up
by jason.greene@jboss.com
"adrian(a)jboss.org" wrote : "jason.greene(a)jboss.com" wrote : and it can do direct method invocation as opposed to reflection which is definitely faster.
|
| I think you'll find that that is probably not as relevant as you think.
| This is a similar problem to Serialization.
|
| The time it takes to
|
| 1) decide what to do - typically a string comparison on an element or attribute name
| 2) coerce xml data into non-string types
|
| will likely "swamp" the small amount of extra time it takes to invoke a setter via reflection,
| most of which is the construction of an Object array to pass to Method.invoke().
|
| That's not to say the difference is unimportant.
| If you have to parse lots of xml, it will definitely add up over time.
|
Yes you have a point, it may not be that faster for one parse. However, reflection does involve all kinds of initial caching on the first invocation, so maybe it will have some small but measurable impact. It should definitely not be slower though which is really what i was driving at.
anonymous wrote :
| e.g. See my 0.4 seconds from 2.4 seconds estimate above (which is probably not
| all reflection overhead anyway?)
Right, the binding is really what I was thinking would be the actual area to improve on. You are definitely correct that with only 30% of the time being binding we may be disappointed. However, I suspect that the parsing time portion of the pie is off because of schema validation. That is known to be slow. We should try disabling that and see what we get.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257956#4257956
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257956
15 years, 2 months