This is one of the most intimiating a learning expriences I have had in a very long time. I want to keep from going down the wrong path.
QUESTION)I know what the buisness requirements would be, for a valid soap message. So It makes sense for me to start by building a progam, that will create a soap message, send the soap message some where that trigger some action. Then figure you how what I need to do to register my service somewhere on my network.
YES/NO???
QUESTION)I can easily chose to send my soap message to a
servlet over HTTP.
Why would I choose a statless
EJB? (I want to use an EJB for the experience but I would need to justify the an ejb container)
QUESTION) Registrys. What are my options? Since my company does not have a commitment to any particular registry implementations. Any recommendtions.
Currently I have written a
java application that will create some
test soap message, envelope, and body, and I can write that soap message to the file system.
QUESTION) Is there some "SOAP message format" for dummies
Question) in the soap body I add a header and some text. In the example code I used both header and made body elements :
header.addHeaderElement(envelope.createName("manufacturer")).addTextNode("ford");
or
name= SOAPFactory.newInstance().createName("manufacturer");
bodyElement= body.addBodyElement(name);
bodyElement.addTextNode("ford");
what the program generates is:
"<manufacturer xmlns="">ford</manufacturer>"
Why does the xmlns occur here???
Why would I declare a name space?
Very LONG SHOT but hope someone knows. some of the buisnesses calling this busness process have/use IBM mainframes using cobal and RPG. Apparently enabling AS400's or 390's to do HTML requests is very expensive.
Any suggestions on how to enable a remote mainframe contact my service.
The other limitation is that the remote mainframe has very limited programmer staff and almost none of it has java exprience.