Thanks for the reply David! Comments inline... David E Jones wrote:
1. if you're doing a custom servlet you could even just do a ControlServlet request event, and then all of the OFBiz context stuff (service/entity engines, etc) is already setup for you
I considered that, but all I needed in the end was the delegator, so I C&P the ControlServlet code to get that. The iCalendar servlet is around 100 lines, and I guessed a new request handler might take more than that. *shrug* Six of one, half a dozen of the other.
2. the idea of following the fixed assets and finding more work effort records to include is interesting, but I'm not sure about it
Maybe because we see different applications. Example: I'm a maintenance person in charge of a piece of equipment and I want to add it to my calendar so I can see when it is being used for production runs and when maintenances are due.
3. I have more significant doubts about following the party and finding other work efforts; what I'm thinking is that people will have calendar events associated directly with them (ie with a WorkEffortPartyAssign) and they will select events from all of their events and add them to one of their calendars; in other words, when looking at a single calendar they will just want to see events in that calendar and not every event associated with that party; in other words, my vote is that we do not lookup all parties associated with the calendar work effort and then look for events associated with the parties
That could be done too. I was looking at it more from the perspective of someone wanting to "throw a switch" to allow others to see their calendar. I can create a setting that will make it work either way.
Good thoughts on your part - I appreciate your comments! -Adrian
