slub.team team mailing list archive

[Matthias Ronge <matthias.ronge@xxxxxxxxxxxx>]

Review: Resubmit

> 1- Can you append a short description of the use case?

These outputs shall provide sufficient information to sensibly parameterise Active MQ tickets to create new processes using the Active MQ interface. (They shall contain the same information which was generated from the JSP files which once were part of the Active MQ implementation but were rejected in favour of using the Jersey API for this.)

> 2- […] for Java Beans it should be possible to instantiate plain objects and
> use setters for setup. Constructors should IMHO not throw exceptions in this
> case.

Done. However, one might discuss wether this is a case of ‘speculative generality’. See: http://xp.c2.com/YouArentGonnaNeedIt.html Maybe this aren’t “beans” in terms of the specification, but just other crumbs of code? Regrettably, I observed that working with Jersey (that is, with JAXB in general, I think) seems to raise numerous cases where you need to implement such crumbs. Might it be better to leave the classes as-is and, to be clear, simply put them somewhere outside the “beans” package?

-- 
https://code.launchpad.net/~zeutschel/goobi-production/extended-jersey-api/+merge/133640
Your team Saxon State Library Team is subscribed to branch lp:goobi-production.