[JBoss ESB Development] - Re: SOAPProxy+AS5: INVM contract unavailable w/classpath URI
by dward
"Kevin.Conner(a)jboss.com" wrote : First, only when WSDL is exposed through the HTTP/JBR endpoints should the contract publisher be registered. https://jira.jboss.org/jira/browse/JBESB-2913 seems to cover this.
I spent a good amount of time digging through when/how/why publishers are added to ServicePublisher, as well as when/how/why EPRs are registered in the Registry, as well as how/why the contract JSP application exposes contracts. Basically, there are two kinds of Publishers: ContractPublishers and ContractReferencePublishers. When you are talking about EBWS or SOAPProxy, a ContractReferencePublisher is added, and they do not require an EPR registered in the Registry. However, everything else (like SOAPProducer) requires an EPR registered in the Registry for them to display properly in the contract JSP application.
You can't not register their EPRs, just so the contract JSP app won't display them. Reason is that a particular Service might have multiple Listeners configured, for example a mix of JMS and HTTP (JBR or HttpGateway), and not registering the non-HTTP EPRs would mean the ServiceInvoker would have nothing to load balance across. Because of this, I believe the best route to take is to change the contract JSP app so that it lists all Services, but only provides contract links to WSDL for HTTP (or HTTPS) endpoints.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4270282#4270282
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4270282
14 years, 4 months
[JBoss Microcontainer Development] - Re: Supporting qualifiers in MC
by kabir.khan＠jboss.com
Note to self :-)
This pushes (un)install method annotations to the MDR
https://jira.jboss.org/jira/browse/JBKERNEL-68
"kabir.khan(a)jboss.com" wrote :
| 1) PreInstallAction describeVisits the BeanMetaData as before
| 2) Determine the relevant parent nodes in AbstractInjectionValueMetaData during describeVisit().
| 3) Either
| a) See if I can get rid of SearchClassContextDependencyItem, since it should just be a special case of a qualifier dependency item with no qualifiers.
| b) Create dependency items as before
| Stash the nodes determined in 1) into the dependency item
| 4) PreInstallAction populates the MDR as before
| 5) Extend this step to look at all the dependency items. For the relevant ones (SearchClassContextDependencyItem/qualifier dependency item) check the parent nodes for qualifiers and add to the dependency item.
|
| Is this too much of a hack? At least this way we don't have to go through everything again.
This is now working with
| <inject/>
|
However, I undid the stuff I did in the InjectAnnotationPlugin, so @Inject + qualifiers is broken. The problem is that 5) happens during PRE_INSTALL and the annotation plugins kick in during DESCRIBE so the annotation plugins need to pick up the qualifiers as before. I'll readd the stuff I did in InjectAnnotationPlugin on Monday.
Also, I need to test field properties and see if something can be done with ValueFactories
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4270264#4270264
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4270264
14 years, 4 months