This week's book giveaway is in the Spring forum.
We're giving away four copies of Spring Boot in Practice and have Somnath Musib on-line!
See this thread for details.
Win a copy of Spring Boot in Practice this week in the Spring forum!

Mario Kerk

Greenhorn
+ Follow
since Jun 13, 2005
Mario likes ...
Android Java Ubuntu
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
1
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Mario Kerk

Dannyf Soon wrote:Anybody can tell me what pattern is used for the two SLSBs BidManager and AvailabilityManager in Cad Class Diagram & Sequqnce Diagram in Chapter 9? From my point of view, it's neither Business Delegate nor Session Facade. Any comments on this?



I'm not sure I agree. I think the Manager classes ARE an example of the Session Facade pattern. I re-read the description of the pattern in the (older) version of the "core J2EE patterns" and I think they match the pattern: The Manager classes "provide a simpler interface to the client by hiding all the complex interactions between other business components" (such as the DAOs in this case) and "reduce the number of business objects that are exposed to the client" (the web layer in this case).




Usman Ibrahim wrote:I am also thinking of avoiding interfaces for SLSB to keep my class diagram simple and add a note that these will be accessed by Local/Remote interface. If anyone think this is not the best way, please voice out.



I agree, and that's the way I'm also planning to proceed. I did not think too much about it though I admit. This is how I would do it in real life and that's how it is shown in Cade/Sheils 's example, so that was enough for me.

Krishna Jonnalagadda wrote:
How should we represent a local state less and a remote state less. Will it be some thing like this : <<local stateless>> or <<remote stateless>>
Can any one please clarify this ...?



I think that UML allows the flexibility to introduce your own stereotype names, like "local stateless" or "remote stateless" as you have suggested. I don't remember of ever coming across the specific names, probably because it usually is not necessary to go into so much detail in a class diagram. But that's just the way I see it, I guess.

Luay Abdulraheem wrote:Dear All,

What is the right way to represent a stateless session bean in Class diagram, stereotype <<@Stateless>> or <<Stateless>> ? same to <<@Entity>> or <<Entity>> ?
With or without '@' ?



I think the most common way would be without the @ symbol (i.e. <<Statelss>>, <<Entity>>).

The @ symbol reminds me of Cades/Sheils's chapter 9 class diagrams where "annotations" (and not stereotypes) were used to show the same information. In that case the annotation was added inside a parenthesis next to the class name (e.g. "Bid (@Entity)") , so this might have been what confused you.

Ranganathan Kaliyur Mannar wrote:Bad idea. Bad idea to 'extend' or 'create' new use cases. In the sequence diagrams, you can try and show when that 'entity' is created (maybe as part of creation of 'related' or 'parent' entity).



Thanks for the reply. I really appreciate it.

I also found this older post where another rancher was asking more or less the same thing. One of the responses there also suggested that it might be OK to completely leave out an entity from the sequence diagrams if it's not mentioned in the use cases (but not from the class diagrams of course).

I think I'll go with your suggestion and try and fit the entity's creation along with one of the parent entities and document this as an assumption.
Thanks again!

Ps. If anyone else has an opinion or past experience on this issue, I'd still be interested to know.

Andrew Monkhouse wrote:For the SCEA/OCMJEA exams, you do not need to go so deeply into the APIs. You might want to take a higher level view.



Hi Andrew,
I'm a bit confused by your reply.

Do you mean that it in a SCEA assignment it would not be important to show how a recurring Timer would be initially scheduled as part of the design OR that we should not worry too much about known shortcomings of this feature (such as the ones mentioned in the other thread I referenced)?

Btw, I should note that in real life projects I have only used quartz, because I've read too many posts on the tricks required to set up Timers properly in clusters, but mostly because quartz always fit the bill better in the end.

Nevertheless, for my SCEA assignment I am considering of suggesting the use of a Timer for a simple polling job to avoid having to introduce an external library in the design. But because even my SCEA project is supposed to be deployable in a cluster, I can't help but wonder if I would need to demonstrate that I'm aware of all this... But then again I'm probably over-thinking

Hello fellow ranch-ers!

I have been re-reading my part 2 assignment over and over again, but there is still one thing I cannot get straight: There is one type of object in the given business domain model that is not directly referred to by any of the use cases I am asked to support in my implementation.

So far I have added this as an entity in my class diagram (it is clearly related to other persistent entities) , but I'm not sure what I should do about the sequence diagrams.

I think I have three choices here:

1. Make assumptions about the given use-cases that would justify the use of this additional class in them.
My instinct tells me this is probably the best choice, since the general instructions clearly say that we should address all objects and relationships in our design. However I'm a bit worried because the assumptions I would have to make would introduce more classes and additional steps in the existing use-cases, so there is a risk of over-complicating the solution.

2. Assume that the entity is involved in another completely new use case and provide sequence diagrams for that use case as well.
Not sure if this would be a good idea. nor how I would justify this.

3. Assume the entity is involved in another use case that I'm not supposed to deliver as part of the assignment and ignore it in all other diagrams (but document the reason I am doing it).
This also does not feel right, as that would mean that I would be submitting only part of the architecture of the complete system.

Any thoughts or suggestions on this?
I would be especially interested to know if you had to face a similar issue in your assignment. Did you use all objects from the Business model in your sequence diagrams? Do you think it is a good idea to "extend" use cases (for e.g. by assuming that one step of the use-case implies several others?).

Thanks a lot in advance for your advice!

Devashish Bansal wrote:I also have the same Beta stuff with a different assignment named "Retire Early".
I guess they are providing all new assignments starting this month, as these are new assignments they cannot decide on passing marks yet same as with all Beta exams from Sun/Oracle, so they are going to analyse results of all these new assignments and then decide upon passing marks, hence called Beta.
I also checked if oracle launched Beta Architect exam for J2EE 6 but cannot find anything on oracle's site.



Same thing in my case and the "Gemstone" assignment. However I don't think that these are new or that the grading requirements will be different. They are just probably recycling some very old ones from the time the JEE5 architect exam was still in beta phase. (For e.g. I remember seeing a reference to both "gemstone" and "retire early" assignments in some very old posts in this forum).

Kumar Amit wrote:I was talking about client code to invoke the method to trigger the timer. What is the best way to invoke the method on the bean which will create/trigger the timer (timerService.createTimer() etc). Should I use Startup servlet that will invoke this startTimer() method on the bean or something else?



Here's another example that uses a ServletContextListener to start up a Timer.
However, I also recommend reading this thread as well, because it mentions some of the common "gotchas" to keep in mind when using EJB 3.0 timers.

Dear all,

I�ve been trying to migrate my struts-tiles application to JavaServer Faces using the struts-faces library. I downloaded the latest nightly build from http://cvs.apache.org/builds/jakarta-struts/nightly/struts-faces/ , but the provided struts/tiles example application does not work (though it can be deployed without problem on my Tomcat 5.0.28).

Can anyone else please confirm this?

In particular, it seems that replacing the struts <html:form> tag with the library's <s:form> tag totally ruins the rendered html code. For example, while <html:form action="/myAction.do"> translates to sth like <FORM name="myActionFormBeanName" action="/contextPath/myAction.do" method="post">, <s:form action="/myAction.do"> yields <FORM name="myActionFormBeanName" action="/path/to/layout/tile/with/suffix/replaced.do">.

It seems strange that the example applications don't work, so i am might be missing out on something here. Has anyone been able to successfully use this integration library?

Any comments will be greatly appreciated!
Thanx in advance,
Mario
17 years ago
JSF