Win a copy of Testing JavaScript Applications this week in the HTML Pages with CSS and JavaScript forum!

Dianne Spillers

Greenhorn
+ Follow
since Mar 05, 2001
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
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 Dianne Spillers

It's expensive but worth it if you ask me. If you price out Rational Rose plus an IDE it works out to be comparable. Also, Together Soft has floating Desktop licenses.
Has anyone out there used it for Java development. We are thinking of moving from Visual Age, WebSphere App Studio to Together Soft. I would love to hear pros and cons
Allan. Thank you.
Your other thread was just what I needed. I too use VisualAge and that input was great. Think I'll try it and see how it works for me
Thanks Michael.
Do you ever change the log behavior on the fly??? and have you done any customization to it??
We are thinking of using Log4J for an application. Does anyone have any experience with it??? Likes/Dislikes any feedback would be greatly appreciated
Okay I give...I am having alot of trouble with a certain method in my application and I finally give and am asking for help. A little background might help. This is a problem mangement system. This method picks up a message off of MQ and goes through this routine to determine if a ticket needs to be opened or an existing ticket should be updated. There are certain events that come over with the action of update, these events sometimes warrant a ticket and sometimes can be dropped and no action taken. This is where I am having trouble...WHat I seem to have a mental block with is droppping the event that meets the following criteria: No UniquiePICID and older then 24 hours.
Here is a portion of the method: The beginning of this method determines the different delimiters within the message and gets the fields from the message: Here is the beginning of the code that is causing me problems:
// Do other work here
// Check to see if ID already exists
// if does not exist, create new ticket unless action=update
// if does exist and action = update or create/update then update ticket, unless tkt is older than 24 hrs then drop event
// if does exist and action = create then create a new ticket
// if no action is sent then assume action = update/create and do accordingly
tktnumber = correlateTivoliID(uniquePICID);
if (tktnumber == 0) {
if (action == null | | action.toUpperCase().indexOf("CREATE") != -1) {

tkt.setTicketNumber("" + getTicketNumber());
System.out.println("New tkt number" + tktnumber);
newTicket = true;
try {
insertTivUniqueID(uniquePICID, tkt.getTicketNumber());
} catch (shared.DatabaseException e) {
e.printStackTrace();
// Do something here to notify somebody that tivoli ticket insert
// failed...
return;
}
}
} else {
// if this ticket is 24hrs old and the action is update, do the
// stuff below
// need to handle when this returns null
//System.out.println("**** UPDATE CURRENT TICKET"+tktnumber);
Ticket tempTicket = getTicket("" + tktnumber);
System.out.println("*****Ticket Number Passed" + tktnumber);
java.util.Date tktDate = new java.util.Date(tempTicket.getTicketOpenDateAndTime());
System.out.println("Old Ticket Date/Time" + tempTicket.getTicketOpenDateAndTime());
if (new java.util.Date().getTime() - tktDate.getTime() > (24 * 3600 * 1000) && action.toUpperCase().indexOf("UPDATE") != -1) {// 24 hrs * 3600 seconds * 1000 ms
System.out.println("Dropped Tivoli event - Harmless event - To Be Dropped");
return;


} else
if (action == null | | action.toUpperCase().indexOf("UPDATE") != -1) {
tkt.setTicketNumber("" + tktnumber);
newTicket = false;
System.out.println("**** IN THE UPDATE IF OF UPDATE ");
} else
if (action.toUpperCase().equals("CREATE")) {
tkt.setTicketNumber("" + tktnumber);
newTicket = false;
System.out.println("**** IN THE CREATE IF OF UPDATE");
/*try {
insertTivUniqueID(uniquePICID, tkt.getTicketNumber());
} catch (shared.DatabaseException e) {
e.printStackTrace();
// Do something here to notify somebody that tivoli ticket insert
// failed...
return;
}*/
}
}
THere is more code in this block but only fills other fields in the ticket.
if (newTicket) {
try {
//insertTicket(tkt);
insertTivoliTicket(tkt);
tkt = PagingManager.process(tkt);
} catch (shared.DatabaseException e) {
e.printStackTrace();
// Do something here to indicate tivoli ticket insert failed!



}return;

} else {
try {
//updateTicket(tkt);
updateTivoliTicket(tkt);
} catch (shared.DatabaseException e) {
e.printStackTrace();
// Do something here to indicate that tivoli ticket update
// failed!
return;
}
18 years ago
I am hoping someone can shed some light for me. Our application runs as an applet using RMI running on UNIX to bind to. We have lots of Swing components and have had to use X11 Windows Display. My problem is that when there is an X11 Windows failure RMI halts. My first inidcation that a failure is in process is the clients not getting connected. I understand the client not being able to use the Windows Display but why does RMI fail so hard when it loses the X11 windows display and does anyone know how I can set up a failover for the X11 windows display. The variable is not set in our code it is set in Unix scripts at startup.
18 years ago
I agree with Frank on the cultural thing. I don't not work for an IT compnay but an manufacturing company with a large IT department. It is rare around here to see all IT workers go home on time. Most of us work 45-50 hours a week and don't bat an eye. 60 hour weeks are common around here too but it is the culture of our environment. If the systems come down the plants and distribution centers are down. Not really good for business.
From the development side, there is alot of focus put on time lines and features. I believe that XP tells us that more features require more time. Sometimes we get the more features but not the more time as a resource which in turn causes the developers to work the extra time to get it done on time. Viscious circle, huh?? My biggest issue with my current project is the constant adding of features but my timeline not getting any longer.
I agree with you Martin, that pair programming isn't all about mentoring. Having a newbie asking you a hundred 'why' questions leads to different new ideas and apporaches to the same methods and forces some more experienced programmer to take a fresher view and what they were convinced was the only way to do things.
I am new by comparision to others to the programming world but I would like to share my recent experience with pair programming and XP.
Our company took on the task of writing an application for problem, change and inventory management about 1 1/2 years ago. I got involved in the project about 6 months after it started and was introduced to XP. Since I was a relatively inexperienced Java programmer at the time, I looked forward to being able to learn from some of my more experienced Java developers. After reading XP Explained and getting management to buy off on the paradigm, we got down to the task of coding. Things rocked along very well at first. Everyone felt very comfortable in their roles that they had given themselves and our coding efforts as pairs were producing very logical easy to read code, that anyone could have come behind us and understood. I learned alot of new skills and language with the pair programming we were doing and was feeling more and more comfortable with Java. Then our dynamics changed. Our coach got very disgruntled with the project and it started to trickle down through the rest of the group. Pair programming came to a halt and in my opinion, the project started to suffer greatly. We went from alot of discussion/sharing our code to the attitude that I wrote that you can't touch it!
I think that pair programming has merit. It takes your more inexperienced coders and gives them a chance to be better with out the cost of formal training. It also gives your experienced coders an opportunity to share their knowledge and experience. There just seems to be one caveat to me. The coach's role in this process is very very important to the cohesion of the team. The person filling this role needs to be able to put aside any ego issues and really fill the role as coach. In my experience with XP, this is the most singlely important role on the team.
I am happy to report that because of the pair programming that was utilized in the beginning, I am well on my way to finishing not only the application but getting my certification.