glassfishrobot

@glassfishrobot Commented reza_rahman said: Would you still think it will be a bloated interface if it was something like: CargoRepository.find(TrackingId, LOADING_STRATEGY->[MINIMAL|DEFAULT|COMPLETE])? It's certainly not necessarily always the case, but what...

@glassfishrobot Commented danpeter said: If the Project have very few lazy loaded Collections the least complex solution is preferred, in such a case a loading strategy is fine. For more...

@glassfishrobot Commented reza_rahman said: Sorry for the belated response to this - I just came back from a pretty hectic trip to India... First a few comments on the code...

@glassfishrobot Commented danpeter said: Hi, thanks for looking into the code. I think that Adam Bien describes it better than me here: [http://www.adam-bien.com/roller/abien/entry/building_perfect_anti_facades_almost](http://www.adam-bien.com/roller/abien/entry/building_perfect_anti_facades_almost) he also mentions it as a good...

@glassfishrobot Commented reza_rahman said: As much as I respect Adam, in this case, the empty save() method is unfortunately erroneous since it likely dependent upon implementation specific behavior (I am...

@glassfishrobot Commented Was assigned to reza_rahman

@glassfishrobot Commented This issue was imported from java.net JIRA CARGOTRACKER-33

* **Issue Imported From:** https://github.com/javaee/cargotracker/issues/13 * **Original Issue Raised By:**@glassfishrobot * **Original Issue Assigned To:** @glassfishrobot

@glassfishrobot Commented Reported by reza_rahman

@glassfishrobot Commented Was assigned to reza_rahman