Hi Jostein,
Here is a possible solution:
Oxygen uses Apache Log4j to log various aspects of its internal functionality + it also logs all the HTTP conversations.
I'm attaching a file called "log4j.properties". If you copy it to the OXYGEN_INSTALL_DIR and start Oxygen using the "oxygen.bat" start up script instead of "oxygen.exe" you should receive in the console all the conversations between HTTP client and Server.
You can also direct the log4j messages to a file and thus get the entire conversation recorded in that file.
We'll consider adding a Network monitoring console view to Oxygen in a future version.
Regards,
Radu
Radu Coravu
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com
On 12/21/2011 10:32 PM, Jostein Austvik Jacobsen wrote:
_______________________________________________Think about the developer tools you have in your browser. Especially the
"Network" tab (I'm in Chromium but most browsers have equivalents)...
I'm currently running an XProc script which takes a lot of time
(compiling a catalogue). It makes thousands of HTTP-requests using
p:http-request, as well as a p:load and a p:store.
So I was thinking; wouldn't it be cool if I could monitor the progress
of my script by looking at the network traffic? Of course, I could use
Wireshark (or similar), and I'll probably do so as well. But if it were
more tightly integrated into oXygen like it is with browser developer
tools, I might be able to trace the request and response back to which
XProc line made the request etc. Just an idea...
Regards
Jostein
oXygen-user mailing list
oXygen-user@oxygenxml.com
http://www.oxygenxml.com/mailman/listinfo/oxygen-user
_______________________________________________
oXygen-user mailing list
oXygen-user@oxygenxml.com
http://www.oxygenxml.com/mailman/listinfo/oxygen-user