I badly want to get out a new version of JibxSoap, but it's been delayed
by other responsibilities. My goal right now is to get out the JiBX 1.0
RC1 within the next week, then go back to extending JibxSoap after that.
The main goal for an initial beta release is automatic support for
"wrapped" doc/lit. I can certainly include changes to make the servlet
more extensible, though I don't understand the issue you mentioned -
multiple servlets are not a problem, as far as I know. I'm not likely
to add logging to the framework, though. I really find logging code a
major distraction from the point of the code. Here again, perhaps
there's a way to handle this by defining extension points where logging
could plug into the framework.
- Dennis
Aaron Smuts wrote:
Are you planning on releasing another version of jibx
soap?
I like what's there. It's really fast.
I've been trying it out and have had to add lots of
logging and timing. It is awful trying to debug
something with no logging. . . . I'm using
commons-logging as I do on JCS.
Also, I had to change the way it determines the
service. I don't use the servlet path, but the last
part of the url, since I want to have multiple
servlets. If the get service name had been in a
method I could have just extended the servlet . . .
My changes could be absorbed back. I'm considering
just making my own version of some of the classes. .
. .
Aaron Smuts
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
jibx-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jibx-users
