I found the issue here, and fixed it. I need to check to ensure that the change doesn't affect the wire protocol - I'm _fairly_ sure it doesn't, but we'd need to discuss how to handle it, if it did. I should have a PR up for review later today.
Jon On Tue, Dec 11, 2018 at 2:34 PM Jonathan Gallimore < [email protected]> wrote: > I added a comment to the JIRA, but I'll follow up here too. I started > writing a test for this, and made a couple of small changes: > > * flipped your beans from remote to local > * added a servlet rather than a main > * introduced <ejb-local-ref> in ejb-jar.xml and web.xml so they can be > looked up via java:comp/env as opposed to the global JNDI name > put everything in a .war as opposed to .ear > > ... and it works. > > Generated .war file and source attached. I'm not entirely sure which of my > changes has enabled it to work - my current guess is its the remote -> > local change, but I'll dig into each one. > > Interesting problem - thanks for reporting it! > > Jon > > On Mon, Dec 10, 2018 at 7:43 PM Jonathan Gallimore < > [email protected]> wrote: > >> Hi all >> >> I noticed this come in on JIRA: >> https://issues.apache.org/jira/browse/TOMEE-2234 >> >> Seems we have an issue returning more than 256 entities from a BMP >> finder. Given that I've worked in and around this area, I'd like to work on >> it. I'll assign it to me, but if you had a burning desire to tackle it, let >> me know. >> >> Thanks >> >> Jon >> >
