WS-compensation is a subpart of ws-transaction where we need to have compensation mechanisms in the web service. That is true if you are building the web service so that you can develop specific compensating mechanisms. But in this case, the inventory system is outside your control, you can only use it with its existing interface. I have made it an WS asynchronous call.
Another of the confussing bits of this project is when it talks about the performance requirements ("speed of any API integration mechanisms").
For me this can be understood in 2 different ways. First, it could refer to the API integration with the Inventory System. In this case, Pratik�s idea of an asynch-WS would be ideal. But to be honest, why should the suppliers care about how you schedule your own work??
Second, it could mean that you must provide some sort of integration API, like giving away a WS Session Fa�ade? There is no other bit of text leading to the same conclusion, so I�m not sold about it either!
To R GSN, There is no time limit to submit the assignment. But you have to complete and submit part 2 and take part 3, only then SUN will start grading your assignment.
FYI, this assignment is an Individual effort, you cannot share or talk about your solution in detail in this forum. The idea is that we work on it individually and if we stuck on certain issues, we can ask for suggestions without going too much into the details of our assignment.
I wanted to show the validation and current bids (to support open auction) to bidders and would like to use AJAX. Don�t know how to show it in sequence diagram and even in the component diagram, let me know if you guys have any idea.
I got the Dreamcar assignment also and will start working on it intensely next week (first week of November 2008 -- got a week off work). My email address is firstname.lastname@example.org Anyone who is interested in talking things through (on the level allowed by the SCEA contract) is very welcome to get in touch. Sometime that's very motivating. Also anyone interested in exchanging book/tool recommendations related to the SCEA. (I'm using MagicDraw for the UML part)
I'm also woking on Part 2 - Dream Car Assignment. I have completed Class/Seq/Deployment Diagram. And I'm stuck in Component Diagram. I have not done Component Diagram before. As SUN has instructed to include (servlets, jsp, pojo, design pattern implementation) in the Component Diagram, what do you advice?
1. Is it enough to have one Component Diagram? In that case the no of components will be more (so as to include servlet, jsp, pojo, BusinessDelegate, DAO, Entities, SessionFacade).
2. Mark Cade, Simon Roberts book shows multiple Component Diagrams. - But I really cant digest Component Diagrams for every usecase. Sequence Diagrams do that job.
I also read that "a Component has a encapsulated independent units that provide/implement one or more interfaces". Based on this definition, we can only think of SessionBean as a component, because only they have and implement remote interface, and we can use the lollipup notation between the components. But what about servlets, jsp, pojo, DAO and Entities. They dont even have any (provided) interface? So, how do we show them? Just use dottled line to show the dependency between other components? In that case a component Diagram will look a lot similar to Class Diagram with various components (servlets, jsp, DAO, SessionBean, Entities, BusinessDelegate) and the dependency between them.
So, what do you guys suggest? Please give me some advice, as there are very little document available in the internet for component diagram for J2EE.
I hope I'm not discussing anything illegal (portion of the real assignment) and my question is very generic and I hope this conversation will be useful to all those who are doing Part 2.
I got the dreamcar assignment and after looking at the requirements - All of these objects and the relationships between them should be addressed in your design and implementation. I am confused what kind of relationship will be between suspension and request? Break disks has many-to-many with request. If we have to design a generic extensible solution then ideally request could be raised against any item (base class) and subclass being suspension, Breakdisks, Break pads.
Is it possible to have multiple PO against one request?
Is it possible to have a supplier that bids for partial items?