-
15. Re: What happened to the custom gateway configuration?
"colsona" wrote:
It looks like the gateways are hard coded.if(listener.getIsGateway()) { listenerNode.setAttribute("gatewayClass", FileGatewayListener.class.getName());
This is after all properties are mapped so it doesn't appear that it can be overridden.
This presents a problem in that now I can't use the ESB to detect incoming files as I am constrained.
Asa
Asa, you always have the option of using the base provider, bus and listener config types. This should give you full control of the Gateway configurations etc.
As an example, see jbossesb_config_01.xml and jbossesb_config_02.xml. jbossesb_config_01.xml uses the specialised types and jbossesb_config_02.xml uses the base types, yet they are functionally equivalent as far as the core ESB is concerned. In jbossesb_config_02.xml, check out how the "Bank-JMS-Gateway" is configured.
I haven't looked at the FileGatewayListener code, but you may be able to extend it to add the default behavior you're looking for and then use the base types to configure your own gateway impl. This might get you out until 454 is resolved, at which point you can revert back to using the specialised config types.
As Kurt said, the down side to all this is that it's not as easy to use (less helpful auto-completion when editing the config) and is also more weakly validated. -
16. Re: What happened to the custom gateway configuration?
In config 02 you have a gateway class defined. I thought this isn't supported anymore. Am I wrong? Is this feautre still available?
- <listener name="Bank-JMS-Gateway" busidref="server1-jms" maxThreads="1" is-gateway="true"> <property name="gatewayClass" value="org.jboss.soa.esb.listeners.gateway.JmsGatewayListener" /> </listener> <listener name="Bank-Listener" busidref="local-jms" maxThreads="2" />
-
17. Re: What happened to the custom gateway configuration?
AFAIK, this feature is still supported - unless someone disabled it.
This was exactly the point of my post.... if you use the base , and config types, you can use a custom listener. You might be able to extend the existing FileGateway and add the default behavior you're looking for. Give it a try and let us know :-) -
18. Re: What happened to the custom gateway configuration?
Grrr - it didn't escape the markup tags for me.
"if you use the base , and config types, you can use a custom listener..." should have been "if you use the base [provider], [bus] and [listener] config types, you can use a custom listener..." -
19. Re: What happened to the custom gateway configuration?
Ok I will try it. I have to admit I read the code and felt it wouldn't work anymore not bothering to try it. Hopefully I missed something when I read the code. I will give it a try. If not I downloaded the source last night and have made the changes proposed by Kurt so I can continue developing while I await the official fix.
Asa -
20. Re: What happened to the custom gateway configuration?
Give it a whirl and let us know.
Based on the unit tests, it should still work - see GeneratorUnitTest.test_generate_files().
That test takes both those config files and asserts that the generated configs are identical.
T.