Michael Dean

This is my take on the big "bang" of SOAP/XML over HTTP...am I missing the really important stuff?
From what I've seen, the Web Services model using UDDI, SOAP, WSDL provides arguable advantages in terms of network/transport:
Security/firewall: by using a text-based protocol such as SOAP over HTTP, all traffic can go over port 80 (normally, firewalls limit port access)...this infers several things:
1) Maintaining a of port numbers between producer/consumer not required
2) A single "pinch point" for control of network traffic. Running from behind a firewall becomes much less of a security issue
3) text-based traffic is easily monitored (Note: HTTP messages *can* contain binary streams coded directly into the document using Base 64 encoding)
>Complete with servlet/JSP?
Eventually, it may compete but right now it can complement. Because only one browser(to my knowledge) parses XML and it is buggy (msxml.dll), the standard approach is to use XML as a platform-neutral data format processed @ the servlet layer, which then renders HTML to the GUI layer. The Servlet/JSP model is not precluded when XML is simply the p/n data format. Thus, you still write your servlets in Java...with XML you get a neutral data format and with SOAP, you get a special type of HTTP/MIME "message type for XML-tagged data interchange.
Best Regards,
Michael Dean
Sun Certified Programmer for the Java 2 Platform
OMNI Project
Washington State Department of Corrections

From what I've seen, the Web Services model using UDDI, SOAP, WSDL provides arguable advantages in terms of network/transport:
Security/firewall: by using a text-based protocol such as SOAP over HTTP, all traffic can go over port 80 (normally, firewalls limit port access)...this infers several things:
1) Maintaining a of port numbers between producer/consumer not required
2) A single "pinch point" for control of network traffic. Running from behind a firewall becomes much less of a security issue
3) text-based traffic is easily monitored (Note: HTTP messages *can* contain binary streams coded directly into the document using Base 64 encoding)
>Complete with servlet/JSP?
Eventually, it may compete but right now it can complement. Because only one browser(to my knowledge) parses XML and it is buggy (msxml.dll), the standard approach is to use XML as a platform-neutral data format processed @ the servlet layer, which then renders HTML to the GUI layer. The Servlet/JSP model is not precluded when XML is simply the p/n data format. Thus, you still write your servlets in Java...with XML you get a neutral data format and with SOAP, you get a special type of HTTP/MIME "message type for XML-tagged data interchange.
Best Regards,
Michael Dean
Sun Certified Programmer for the Java 2 Platform
OMNI Project
Washington State Department of Corrections

Originally posted by Prashanth Joisha:
Hi,
How would you represent inner classes/static
inner classes in UML.
TIA,
PJ

As inner classes/nested classes (static) are simply an implementation choice for a logical member of a class/entity, no special graphical artifacts are needed. IMHO, you'd simply depict the class using standard UML representation, then an instance of the class as member. You could assign stereotype of inner class or static inner-class in your specification-level UML (code from)...

Angela: modify your code as follows:
st = new StringTokenizer(sb.toString(),":");
StringTokenizer takes arguments of type String, not StringBuffer...
HTH,
Michael

Tips:
Code and test every LEGAL configuration of a "for" loop. Understand how each will perform...(trying not to skirt the confidentiality agreement)

Write lots of code, tweak it and see how it changes
*****
I recommend the Study Notes by Velmurugan, they are incredibly detailed and identify many subtle features of the language I found nowhere else. They are an excellent crib review right before the exam.
I completed the first pass of the "fabulous 59" in 1:25. I spent the remaining 35 minutes reviewing all questions "Marked" during the exam (I estimate that I marked about 75% of the questions for review)
Total prep time, over 90 days, is estimated @ 120 hours.
Best Regards,
Michael Dean
Sun Certified Programmer for the Java 2 Platform
OMNI Project
Washington State Department of Corrections

I have seen something like this in two different places. I have tried compiling these examples in VAJ 3.0 (JDK 1.1.7a)and JBuilder 3.0 (JDK 1.2)...in both cases I get:
ERROR - <Identifier> expected...
int arrayOfNums[][]; // Construct
arrayOfNums = new int[3][]; // Declare
arrayOfNums[0] = new int[2]; // Initialize
arrayOfNums[1] = new int[3]; // ""
arrayOfNums[2] = new int[4]; // ""
What is the problem in defining and initializing an MD array
in this fashion?

Even IBM is on-board...they have a new set of classes for IMS 7.0 called IMS Java for accessing IMS via DLI or Applications....these packages include a some trace classes which generate XML in their output. It is my understanding that IBM Websphere and possibly the HTTP server are also configured using XML. No more Babel of proprietary scripting and binary languages for configuring various similar products such as web servers, application servers, etc. With a single set of agreed upon tags...the world becomes much easier even on the Big Iron...
------------------

Originally posted by Carl Trusiak:
We are giving away four copies of "The Pattern Almanac 2000" and the author Linda Rising, is Here! Everyone give her a warm welcome!
See our Book Giveaway Page for details.
[This message has been edited by Carl Trusiak (edited January 30, 2001).]

I would very much like a copy of this book. Another good resource is Bruce Eckel's "Thinking in Patterns" for Java

------------------

Originally posted by Simon Xu:
hi,
I am confused about the position of sequence diagram. it belongs to problem or solution domain? different books have diff answer.
Please clear up,
Simon

The beauty of Object/Entity Diagrams and Sequence Diagrams is that they can be used at any stage of development. You just need to consider the perspective: Conceptual, Specification orImplementation.
From "UML Distilled 2nd Edition" Fowler and Scott, Addison-Wesley,2000

Conceptual: ..you draw a diagram that represents the concepts in the problem domain...
Specification: Now we are looking at software, but we are looking at interfaces, not implementation
Implementation: now we really do have classes and are laying bare the implementation.
You can denote the perspective taken using stereotypes in your UML drawings...<<implmementation class>> for Implementation perspective and <<type>> for Conceptual and Specification
BTW: I HIGHLY recommend this book...
Best Regards

------------------