In comp.lang.java.advocacy, A Leaf Blower and A Geode Discussing Politics
<
[email protected]>
wrote
Today I wrote a c# service that read and parsed and XML file and manipulated
other services based on using the values in the XML to evaluate http calls.
The application uses the ThreadPool to make simultaneous http calls.
What did you do today?
Feh. JBoss does most of the parsing and threadpooling. Dunno regarding
the details of the Enterprise Service Bus, as one of the requirements
thereof is *partial parsing of an XML file*. However, using SAX to
clip out part of the file might be easy enough, or one can just write
XSL to find the tag of interest and copy the subtree thereof to
the output, using XSLT (Xalan, perhaps). DOM nowadays is a bit heavy.
I can't say I've played with custom tags but presumably JSP + custom tags
is a now outdated but still effective solution for various problems.
JSP makes hooking up forms to beans simple, although it doesn't
help with the Javascript. (There are times I think Javascript
is beyond help, though. Yuck.)
Or one can go through a SOAP service. I have a very small prototype,
for example, that is basically a "cookbook" therefor -- it's a little
complicated for my liking but it works and answers the question
"What time is it". I'll have to work on integrating it with JNDI,
admittedly -- or just go full EJB with the silly thing hooking SOAP
in as a vector to a stateless or stateful session bean. Presumably
that sort of stuff should be simple, although EJB tends to specify
everything more than once, mostly because the initial setup of EJB
assumed that developer-run tools would do most of the XML generation;
I would highly prefer a more Smalltalk-like system where one can
simply make a call and it either works or it doesn't, coupled with
the ability to inquire as to what calls are available, with
parameters, documentation, and other requirements.
Another issue with EJB is that it uses binary RMI; I'd prefer JAXRPC.
But that's a minor complaint at this point, because EJB is an
established service.
I should mention JMX -- it's nice but incomplete; it needs to be
remotable. (Maybe 1.1 has that capability now?) I've not played
with JMS or JCA but know they exist.
But do feel free to try again to impress us.
As for "HTTP calls" -- no such thing. Http requests, maybe.
SOAP calls, maybe.