[Design of JBoss Build System] - Re: Getting aop 2.0.0.CR10 jars into AS
by kabir.khan＠jboss.com
I tried deleting my local copy of the plugin
| [kabir(a)~/.m2/repository/org/jboss/maven/plugins]
| $rm -r maven-buildmagic-thirdparty-plugin/
|
Following an unsuccessful build
| [kabir(a)~/sourcecontrol/thirdparty/legacy/jboss/aop/2.0.0.CR10]
| $mvn org.jboss.maven.plugins:maven-buildmagic-thirdparty-plugin:maven-deploy -Durl=file:///Users/kabir/sourcecontrol/thirdparty/maven2/[INFO] Scanning for projects...
| [INFO] artifact org.jboss.maven.plugins:maven-buildmagic-thirdparty-plugin: checking for updates from central
| [INFO] ------------------------------------------------------------------------
| [ERROR] BUILD ERROR
| [INFO] ------------------------------------------------------------------------
| [INFO] The plugin 'org.jboss.maven.plugins:maven-buildmagic-thirdparty-plugin' does not exist or no valid version could be found
| [INFO] ------------------------------------------------------------------------
| [INFO] For more information, run Maven with the -e switch
| [INFO] ------------------------------------------------------------------------
| [INFO] Total time: < 1 second
| [INFO] Finished at: Wed May 28 10:04:42 BST 2008
| [INFO] Final Memory: 1M/2M
| [INFO] ------------------------------------------------------------------------
|
I get a maven-metadata-central.xml
| [kabir(a)~/.m2/repository/org/jboss/maven/plugins]
| $ls maven-buildmagic-thirdparty-plugin/
| maven-metadata-central.xml
| [kabir(a)~/.m2/repository/org/jboss/maven/plugins]
| $more maven-buildmagic-thirdparty-plugin/maven-metadata-central.xml
| <?xml version="1.0" encoding="UTF-8"?><metadata>
| <groupId>org.jboss.maven.plugins</groupId>
| <artifactId>maven-buildmagic-thirdparty-plugin</artifactId>
| </metadata>
|
Apart from that nothing is downloaded
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153878#4153878
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4153878
17 years, 7 months
[Design of EJB 3.0] - Re: Feature: MC Equivalent of @Service
by alesj
"ALRubinger" wrote :
| We've currently got @Service, which deploys a Singleton EJB and exposes a JMX View. Oftentimes this is used strictly to get a hook into a Lifecycle (ie. "I want a callback for when my JAR is deployed"). And JMX exposure is not necessarily desired.
|
@Service ~ MC's @JMX
MC beans are 'singletons' in MC (not prototypes). And you can of course code it via factory instantiation to be 'real' singletons (one per CL ... dunno how you achieve that for VM though).
"ALRubinger" wrote :
| I'd like to introduce the notion of an MC EJB, which would have the following features:
|
| 1) Full EJB (Tx, Security, etc)
| 2) @Singleton (Same model following EJB3.1 with regards to concurrency)
| 3) POJO w/ annotations to denote Callbacks (@Service requires Management interface)
| 4) Proxy is installed into MC and therefore becomes a valid MC Bean; though when MC POJOs invoke on the EJB MC Bean, a typical EJB call starts.
|
1) If you have matching aspects for it (@Tx --> Tx aspect, ...) this comes out-of-the-box in MC ... the bean will be aspectized - a JBossAop proxy.
Or you can install it into MC with already created instance, as we've discussed it before.
2) As explained above
3) Annotation handling is pluggable; e.g. ejb's @Create can be mapped to MC's create notion ... see how we handle MC's @Create
4) Sure, once it's in MC anyone can invoke it ... if the injection happens by name, then you might consider On_Demand mode.
Or perhaps my Lazy hack - we can discuss this further, if previous solutions don't work for you.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153874#4153874
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4153874
17 years, 7 months
[Design the new POJO MicroContainer] - Re: Multiple parsing implementation in RARDeployer
by vickyk
"alesj" wrote :
| I have refactored the code, so you can now easily add your MultipleOMFD.
| - http://anonsvn.jboss.org/repos/jbossas/projects/jboss-deployers/trunk/dep...
Ales , you are on fire ;)
I am still trying to see how this can be used .
We have 2 ObjectModel factories which are
1) ResourceAdapterObjectModelFactory , this creates the ObjectModel for the ra.xml file .
2) JBossRAObjectModelFactory , this creates the ObjectModel for the jboss-ra.xml file.
I am not able to find out where in I can pass the ObjectModelFactories and do the merging of MetaData to the required MetaData Object .
I was able to write it with SRD as
public class RARParserDeployer extends JBossExtensionDeployer<ConnectorMetaData, JBossRAMetaData, RARDeploymentMetaData>
| {
| /** The metadata repsoitory */
| private JCAMetaDataRepository metaDataRepository;
|
| /**
| * Create a new RARParserDeployer.
| */
| public RARParserDeployer()
| {
| //super(ConnectorMetaData.class);
| //setName("ra.xml");
| super(RARDeploymentMetaData.class, "ra.xml", ConnectorMetaData.class, "jboss-ra.xml", JBossRAMetaData.class);
| }
|
| public JCAMetaDataRepository getMetaDataRepository()
| {
| return metaDataRepository;
| }
|
| public void setMetaDataRepository(JCAMetaDataRepository metaDataRepository)
| {
| this.metaDataRepository = metaDataRepository;
| }
|
| /*
| protected ObjectModelFactory getObjectModelFactory(ConnectorMetaData root)
| {
| return new ResourceAdapterObjectModelFactory();
| }
| */
|
|
|
| //@Override // Check this STUFF
| protected void init(VFSDeploymentUnit unit, ConnectorMetaData cmd, VirtualFile file) throws Exception
| {
| cmd.setURL(file.toURL());
| VFSDeploymentUnit parent = unit.getParent();
| String name = unit.getSimpleName();
| if( parent != null )
| name = parent.getSimpleName() + "#" + name;
| metaDataRepository.addConnectorMetaData(name, cmd);
| }
|
| private ConnectorMetaData specMetaData;
| private JBossRAMetaData jbossSpecificMetaData;
|
|
|
| protected RARDeploymentMetaData mergeMetaData(VFSDeploymentUnit unit, ConnectorMetaData specMetaData, JBossRAMetaData jbossSpecificMetaData) throws Exception
| {
| this.specMetaData = specMetaData;
| this.jbossSpecificMetaData = jbossSpecificMetaData;
|
| RARDeploymentMetaData deployment = new RARDeploymentMetaData();
| if (specMetaData != null)
| {
| deployment.setConnectorMetaData(specMetaData);
| }
| if (jbossSpecificMetaData != null)
| {
| deployment.setRaXmlMetaData(jbossSpecificMetaData);
| }
|
| return deployment;
| }
|
| public ConnectorMetaData getSpecMetaData()
| {
| return specMetaData;
| }
|
| public JBossRAMetaData getJbossSpecificMetaData()
| {
| return jbossSpecificMetaData;
| }
|
| }
Ales , can you give me some outline for OMFD scenario ?
I will take it from there .
PS: The SRD is just a raw outline as I felt OMFD will make life simpler .
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153836#4153836
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4153836
17 years, 7 months