[jboss-dev-forums] [Deployers on JBoss (Deployers/JBoss)] - Re: Deployer order solely based on inputs/outputs now?

[adrian@jboss.org]

"bill.burke at jboss.com" wrote : anonymous wrote : he real solution is to create your own DependencyItem implementation
  |   | like I've been telling you to over a year now. 
  | 
  | And I've been telling you that EE injection requirements are not simple...
  | 

I know.

anonymous wrote : 
  | Are you sure the DependencyItem stuff will work since EJB and PC ref's metadata may be incomplete or even ambiguous?  Does a DependencyItem get queried EVERY TIME any arbitrary thing is deployed or when ANY arbitrary thing changes state within the MC?  I also worry about a dependency item matching and picking up the wrong reference because an inner deployment scope hasn't been processed/deployed yet.
  | 

You can make a DependencyItem do whatever you like, e.g. just delegate
to the EJBContainer to do all the work.

anonymous wrote : 
  | I don't understand why I have to add the dependencies to the deployment to make this work.    The subdeployments of an EAR are not going to be deployed piecemeal.
  | 

EAR subdeployments are always going to piecemeal unless you make
them wait for their dependencies.
If its non-deterministic then nothing is going to work, its just random.

anonymous wrote : 
  | Also, we're not going to make configuration more complicated for the user for the edge cases 90% of people don't care about.  Meaning, we're not going to require a mapped-name with @EJB or @PersistenceContext refs.  i.e. requiring them to specify a mapped-name.
  | 

I'm not saying you should. I'm saying you create a dependency that is relevant
to what the user requests. If they say mapped-name then that is more specific
and should respected over whatever heuristic rules you use otherwise.

anonymous wrote : 
  | Where is there documentation on how dependency items work?  The Javadoc isn't very helpful ;-)

Not done, yet...
http://jira.jboss.com/jira/browse/JBMICROCONT-81
Ales has been concentrating on what most people will actually use
in the documentation.

There's many examples though, e.g. the deployment dependencies
I added for OSGi a few weeks ago:

http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas?view=rev&revision=64469

Mapping of OSGi requirement to MC dependency (currently only modules and packages
are implemented as requirements)
http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/projects/microcontainer/trunk/deployers-impl/src/main/org/jboss/deployers/plugins/classloading/RequirementDependencyItem.java?view=markup&pathrev=64469

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082223#4082223

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082223