[JBoss Seam] - Re: Deployment Scanner framework
by colintoal
Cool - I'm glad its on the plan for the future - as the Scanner facility is nice.
One thought I had is to use a meta-annotation to represent "scan discoverable".
One could annotate the annotation that indicates why the class is being discovered with it.
I'm imagining something like:
| public @interface @ScanDiscoverable
| {
| String value() default ""; // resource token ? like seam.properties ? necessary ?
| }
|
| ...
| // Seam example
| @ScanDiscoverable
| public @interface Name
| ...
|
This provides the ability to extend the Scanner's discoverable classes with new annotations (like my @JCRContentItem annotation).
Then the Scanner could be extended with Pre and Post Scan hooks (also discovered during scanning):
public @interface ExecutePostScan
| {
| Annotation discoverable();
| }
Methods (or Classes ? I'm not quite sure yet) bearing this annotation would have to implement a contract like
| @ExecutePostScan(discoverable=JCRContentItem)
| public void executePostInitializeScan ( ServletContext ctx, Set<Class<Object>> )
This would give the new @ScanDiscoverable annotation implementor a clean post Scan hook.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059360#4059360
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059360
16Â years, 9Â months
[Persistence, JBoss/CMP, Hibernate, Database] - Re: GC problem ?
by vettori
I updated Jboss to 4.2.0GA that has hibernate 3.2.3 (3.2.1 entitymanager).
Running the app three times now gives :
[INFO ][memory ] 3.737-3.893: GC 456014K->4945K (5242880K), 155.649 ms
[INFO ][memory ] 542.299: parallel nursery GC 1483183K->695999K (5242880K), 379.253 ms
[INFO ][memory ] 2113.122: parallel nursery GC 1862122K->1075130K (5242880K), 536.939 ms
[INFO ][memory ] 2732.543-2732.669: GC 1568837K->85502K (5242880K), 126.728 ms
[INFO ][memory ] 5160.667: parallel nursery GC 1543572K->760980K (5242880K), 867.616 ms
[INFO ][memory ] 5191.217: parallel nursery GC 1916236K->1131836K (5242880K), 811.969 ms
[INFO ][memory ] 5222.067: parallel nursery GC 1916236K->1182604K (5242880K), 807.395 ms
[INFO ][memory ] 5256.562: parallel nursery GC 2294636K->1509980K (5242880K), 813.308 ms
[INFO ][memory ] 5358.185: parallel nursery GC 2589543K->1807080K (5242880K), 826.695 ms
[INFO ][memory ] 5377.246: parallel nursery GC 2589480K->1857368K (5242880K), 832.857 ms
[INFO ][memory ] 5396.206: parallel nursery GC 2902380K->2119980K (5242880K), 818.478 ms
[INFO ][memory ] 5417.744: parallel nursery GC 3136880K->2352224K (5242880K), 826.093 ms
[INFO ][memory ] 5506.212: parallel nursery GC 3347309K->2564781K (5242880K), 827.195 ms
[INFO ][memory ] 5525.118: parallel nursery GC 3537258K->2777114K (5242880K), 829.615 ms
[INFO ][memory ] 5543.997: parallel nursery GC 3729963K->3010539K (5242880K), 836.042 ms
[INFO ][memory ] 5564.356: parallel nursery GC 3938352K->3239969K (5242880K), 833.441 ms
so it's a lot better.
I don't know if this is because of hibernate 3.2.3 or jboss and i really like to know.
Can anybody help me to understand ?
thank you
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059351#4059351
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059351
16Â years, 9Â months