[
https://issues.apache.org/jira/browse/S4-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13171977#comment-13171977
]
Leo Neumeyer commented on S4-5:
-------------------------------
It's a two step process.
If there is no ambiguity (one stream field per event type) the assignment is
done based on type.
Otherwise, the user provides the PE class field name for the stream using
withField() as follows:
{code}
pey.emit(EventA.class).withField("stream3").onKey(new
DurationKeyFinder()).to(pez);
{code}
If the ambiguity is not resolved, the program exits with an error message.
The problem is that using a stream entity to define the graph makes it hard to
visualize the connections. pe2stream -> stream2pe as opposed to pe2pe. With
lots of PEs removing the intermediate should make the code cleaner, I think.
Anyway, let's play a bit with some variations and talk more on Tue.
> Prototype app builder
> ---------------------
>
> Key: S4-5
> URL: https://issues.apache.org/jira/browse/S4-5
> Project: Apache S4
> Issue Type: New Feature
> Affects Versions: 0.5
> Reporter: Leo Neumeyer
> Priority: Minor
> Fix For: 0.5
>
>
> Extend Guice AbstractModule to create a simple application builder layer. The
> idea is to evaluate if we can use Guice to do all the wiring including PEs
> and Streams and Apps.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
