"adrian(a)jboss.org" wrote :
|
| No I was talking about something like:
|
|
| | <bean code="...ManagedObjectDefinition">
| | <property name="type">org.jboss.jms.server.destination.QueueService</property>
| | <property name="builder">
| | <javabean xmlns="..." class="...QueueMOBuilder"/>
| | <property>
| | </bean>
| |
|
Now that I refresh my memory on how this works. :-)
You also need to be able to specify the ManagedObjectPopulator as well.
The Builder defines what goes in the ManagedObject (i.e. it is like the class)
(and whether it should even be a ManagedObject ;-)
The Populator fills in the underlying data for a given object (i.e. for the instance)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191284#4191284
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191284
A lot of the minor tasks are done already...
I have just a point regarding the corrupt pages. I'm going to measure if concurrent writes, and if they are, we still need to deal with holes (even on NIO).
Only thing is I need to add a counter per page, not just a global counter any more, same way we do on the journal.
But if we disable concurrent writes this is moot. Let me check it first.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191280#4191280
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191280
| +
| + /**
| + * Add builder to factory.
| + */
| + public void start()
| + {
| + if (factory == null)
| + throw new IllegalArgumentException("Missing managed object factory");
| + if (type == null)
| + throw new IllegalArgumentException("Missing type");
| + if (builder == null)
| + throw new IllegalArgumentException("Missing builder");
| +
| + factory.setBuilder(type, builder);
| + }
|
You should just use the singleton if they don't provide a managed object factory.
ManagedObjectFactoryBuilder.create();
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191278#4191278
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191278
Can you set the output directory to target/classes via outputDirectory? Actually, they show that in the usage page:
"rmic plugin usage" wrote :
| Including the stub classes in the main project jar
|
| Output is by default written to the directory target/rmi-classes. Using this default behavior the stub classes will not be included in the main project artifact. To include the stubs in the main project jar the outputDirectory can be set to ${project.build.outputDirectory}.
|
| Similarly, to include the stubs in the test jar the testOutputDirectory should be set to ${project.build.testOutputDirectory}
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191277#4191277
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191277