[JBoss JIRA] Created: (SWITCHYARD-226) Camel Component interface handling
by Daniel Bevenius (JIRA)
Camel Component interface handling
----------------------------------
Key: SWITCHYARD-226
URL: https://issues.jboss.org/browse/SWITCHYARD-226
Project: SwitchYard
Issue Type: Task
Components: component-camel
Reporter: Daniel Bevenius
Assignee: Daniel Bevenius
The Camel component will look at the ServiceReference when creating a SwitchYard Exchange. It will look use the output type of the target service operation.
This task should make sure that this works for all types of interfaces. Currently this has only been tested with a Java Interface and we need to verify how this should behave when you have a soap binding for example.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] Created: (SWITCHYARD-223) Config Descriptor classpath resource properties not visible across Model creations in AS7
by David Ward (JIRA)
Config Descriptor classpath resource properties not visible across Model creations in AS7
-----------------------------------------------------------------------------------------
Key: SWITCHYARD-223
URL: https://issues.jboss.org/browse/SWITCHYARD-223
Project: SwitchYard
Issue Type: Bug
Components: configuration, deployment
Reporter: David Ward
Assignee: David Ward
Fix For: 0.1
IRC discussion...
magesh
kcbabo: Do you if the Descriptor's maps are kept as instance variables,
Is this by design? Something like for each Config Model the maps can
vary or should it be static?
kcbabo: (Do you know)
8:04
kcbabo
magesh: not sure ... looking
8:05
magesh
kcbabo: I get successfull deployment with them being static
8:05
kcbabo
magesh: haha!
8:05
magesh
kcbabo: Modular as it can be
8:07
kcbabo
magesh: ok, see what you are talking about now
magesh: interesting that making them static fixes the issue
8:08
magesh
kcbabo: Basically for each Model Configuration, a new Descriptor is
attached, say for example core, bean, transformer, soap etc.,
kcbabo: And each these Descriptors have only access to core swyd config
properties and nothing else
8:10
kcbabo
magesh: can you see a way where this might work with ServiceLoader?
magesh: not saying that's the ultimate answer, but that begins to move
us in the right direction
8:10
magesh
kcbabo: By making them static all properties are visible to all models
8:10
kcbabo
magesh: in that the core configuration parser can lookup implementations
of a configuration interface
8:10
magesh
kcbabo: That could be possible too
8:10
kcbabo
magesh: if we could get there, I think that would solve the immediate
problem
magesh: if it works for activators anyway
8:11
magesh
kcbabo: It already works for activators
8:11
kcbabo
magesh: and that method should still work for the universal classpath
environment
magesh: k
magesh: so my guess is that Classes.getResources() needs to change
magesh: perhaps hide it behind a resolver interface
8:12
magesh
kcbabo: yeah, possible
8:12
kcbabo
magesh: and there could be an implementation which uses normal classpath
resolution
magesh: or service loader
magesh: or maybe both
8:12
magesh
kcbabo: resolving them is not an issue
kcbabo: I added a deployment processor that can resolve these
dynamically added component resources
8:13
kcbabo
magesh: so then what's missing?
8:13
magesh
kcbabo: It is just that the resource properties are not visible universally
kcbabo: across model creations
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months