Eclipse Community Forums: Newcomers » Where to suggest EE4J JPA documentation enhancements

Help

Home

Home » Newcomers » Newcomers » Where to suggest EE4J JPA documentation enhancements

Show: Today's Messages :: Show Polls :: Message Navigator

Where to suggest EE4J JPA documentation enhancements [message #1789912]

Thu, 31 May 2018 17:45

Karl-Philipp Richter

Messages: 2
Registered: May 2018

Junior Member

Hi,
I noticed that JPA implementation treat `0` passed to `Query.setMaxResults(int)` as unlimited result which makes sense since negative values cause an `IllegalArgumentException` and fetching 0 results means that the query has no purpose. However, the documentation on the interface doesn't mention this use of `0`, so that I'd like to propose it to go into a future API release.

Please note that I'm not looking to discuss my proposal here unless it's clearly non-constructive. The question is where to report the request.

-Kalle

[Updated on: Thu, 31 May 2018 18:57]

Report message to a moderator

Re: Where to suggest EE4J JPA documentation enhancements [message #1789954 is a reply to message #1789912]

Fri, 01 June 2018 07:50

Ed Merks

Messages: 33264
Registered: July 2009

Senior Member

I believe you're referring to the implementation provided by EclipseLink. There project page is https://www.eclipse.org/eclipselink/ and the "More" Nav menu has instructions for checking out the source and for contributing. Perhaps the project already supports Gerrit contributions. You can ask for more details on their specific forum: https://www.eclipse.org/forums/index.php?t=thread&frm_id=111

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: Where to suggest EE4J JPA documentation enhancements [message #1789982 is a reply to message #1789954]

Fri, 01 June 2018 14:33

Karl-Philipp Richter

Messages: 2
Registered: May 2018

Junior Member

> I believe you're referring to the implementation provided by EclipseLink.

No, I mean the Java Persistence _API_ since this is the one people are accessing the methods through. If the change isn't done in the API, it's of no use for this case. Note that I'm aware of the fact that this is not a critical bug or anything and I'm not seeking support, I really just want to contribute an improvement. It has to be to the API documentation/interface specification, though, which would than be implemented by all implementations (including EclipseLink) for the next 9.x or 10.x release.

Report message to a moderator