[Design of POJO Server] - Re: HDScanner scanPeriod
by alesj
"pete.muir(a)jboss.org" wrote : Ales has recently updated the hot deployment scanner so that it is also responsible for updating the temp copy of existing apps - people use this for being able to copy a new JSF etc. page and have the app show it without restarting the app.
It's actually not hd scanner that has been updated,
it's this piece of configuration that does it (in profile.xml):
| <!-- The structure modification cache and checker -->
| <bean name="StructureModCache" class="org.jboss.deployers.vfs.spi.structure.modified.DefaultStructureCache">
| <destroy method="flush"/>
| </bean>
|
| <!-- This just checks metadata locations -->
| <bean name="MetaDataStructureModificationChecker" class="org.jboss.deployers.vfs.spi.structure.modified.MetaDataStructureModificationChecker">
| <constructor>
| <parameter><inject bean="MainDeployer" /></parameter>
| </constructor>
| <property name="cache"><inject bean="StructureModCache" /></property>
| <property name="filter"><bean class="org.jboss.system.server.profile.basic.XmlIncludeVirtualFileFilter" /></property>
| </bean>
|
| <!-- Synchs modifed files -->
| <bean name="SynchAdapter" class="org.jboss.deployers.vfs.spi.structure.modified.OverrideSynchAdapter"/>
|
| <!-- We just visit wars, but exclude classes, lib, dev dirs -->
| <bean name="WebVisitorAttributes" class="org.jboss.system.server.profile.basic.IncludeExcludeVisitorAttributes">
| <constructor>
| <parameter>
| <set>
| <value>.war</value>
| </set>
| </parameter>
| <parameter>
| <set>
| <value>WEB-INF/classes</value>
| <value>WEB-INF/lib</value>
| <value>WEB-INF/dev</value>
| </set>
| </parameter>
| </constructor>
| </bean>
|
| <bean name="StructureModificationChecker" class="org.jboss.deployers.vfs.spi.structure.modified.SynchWrapperModificationChecker">
| <constructor>
| <parameter><inject bean="MetaDataStructureModificationChecker"/></parameter>
| <parameter><inject bean="SynchAdapter"/></parameter>
| </constructor>
| <property name="originalAttributes"><inject bean="WebVisitorAttributes"/></property>
| <property name="tempAttributes"><inject bean="WebVisitorAttributes"/></property>
| </bean>
|
HDScanner then asks Profiles for modified deployments,
which eventually ask MDSMChecker for real modifications.
If a deployment is not modified and is temped,
we go and check for any updates with SynchWSMChecker.
If it's modified then there is no need to check since it's gonna be updated anyway.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226150#4226150
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226150
16 years, 11 months
[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Large messages broken
by timfox
I have spent a couple of hours this morning finishing off the LargeMessageExample:
1) The explanation in the readme was very poor. The standard of documentation really needs to rise.
2) The example didn't output much so it was hard to see if anything was happening
3) I limited *both* the client *and* the server to run in 50MB as we discussed previously.
4) I changed the message size to 256MB since we are running in a server with 50MB and want the example to run more quickly.
5) The header comment in the example was for a different example
6) The readme steps did not match the code.
7) I added a step to stop and start the server so we can demonstrate the large message survives a restart.
Some other questions:
a) why the casting to get the input and outputstream - I thought you were going to allow these to be set via a JMS_JBM jms property as we discussed?
b) Is setting Input and Ouput streams only allowed on BytesMessage s ? If not, why are you using a BytesMessage.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226137#4226137
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226137
16 years, 11 months