Note that there are some explanatory texts on larger screens.

plurals
  1. USHelter Scelter
    primarykey
    data
    text
    plurals
    1. COwith respect to the option of having a set of (N) parallel consumers (EventProcessor) doing batching. one thing you must watch out for (at least with the 2.10.x version -- I've not dug through 3.x yet) is that when you split the work across N consumers you cannot rely on endOfBatch being processed by each consumer; it will only be noticed by the ONE consumer set to process the sequence where endOfBatch happens to be true (unless you cheat and look for endOfBatch on all sequences). if there is any lull in events, the other consumers may not see an endOfBatch=true for quite some time.
      singulars
    2. COI thought I was confirming your idea and suspicion. building a long -cp argument seems to be the only nice way to do what you want. you could also possibly create a java -jar launcher which would spawn another "java -cp <many classes go here> some.package.Main" using a system exec. That would allow you to skip the script, at the expense of spawning or forking a new process.
      singulars
    3. CObut the definition of the DD1 element as both a simple type (string) and a complex type is really what prevents you from overcoming your issue in this case. I can't think of a way around this other than to follow my other suggestion from the other answer, which is to generate your JAXB stubs separately for each schema, and attempt to parse your message using both JAXB contexts with validation enabled.. it's not clean by any means, but it might allow you to deal with this situation better than trying to munge the schemas into some semblance of unity. square peg, round hole know what I mean?
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload