How to debug XML&&XSLT?

Now I use XSLT to transform xml.I meet many problem.I can't find a best way to debug my program.
who can help me? thanks.

A lot of people use XMLSpy, I hear.

Similar Messages

How To Debug XML Serialization Error while deploy web services

My Scenario
I've created a Java Projects with a Class. From there I convert it to Web Service by creating the virtual interface, the web services definition and the web service configuration. After that I deploy to the SAP WAS (SP11). At this instant I only try to deploy the web services with the intension to modify it later for GP to invoke.
Result
When deployment the Web Service I get an XML Deserialization error. Error text is below.
Question
How do I go about debugging this? What logs are good starting point? Can I capture the entire SOAP response message somehow?
Thanks

Error Test
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.XmlUnmarshalException: XML Deserialization Error. XML Node [VirtualInterface.Functions][http://xml.sap.com/2002/10/metamodel/vi] have minOccurs>0 in schema definition but is missing in node [VirtualInterface][http://xml.sap.com/2002/10/metamodel/vi].
 at com.sap.engine.services.webservices.jaxrpc.encoding.GeneratedComplexType._loadInto(GeneratedComplexType.java:1197)
 at com.sap.engine.services.webservices.jaxrpc.encoding.GeneratedComplexType.deserialize(GeneratedComplexType.java:945)
 at com.sap.engine.services.webservices.server.deploy.descriptors.vi.VInterfaceParser.getVInterface(VInterfaceParser.java:46)
 at com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseVI(WSDefinitionFactory.java:920)
 ... 27 more
 at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:681)
 at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1278)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
 at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
 at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
 Caused by: java.lang.Exception: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common deployment exception! The reason is: Error occurred, trying to update web services for application sap.com/TimeoffService. . Additional info: none
 at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:164)
 at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:118)
 at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:86)
 at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateManager.makeUpdate(WSUpdateManager.java:52)
 at com.sap.engine.services.webservices.server.deploy.WSDeployer.makeUpdate(WSDeployer.java:274)
 at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:400)
 at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
 at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:164)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:669)
 at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1278)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
 at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
 at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
 Caused by: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices deployment exception! The reason is: Error occurred, trying to generate web services deployment files for application sap.com/TimeoffService. . The error refers to application: none, jar: , web service: .
 at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.generateDeployFiles(WSUpdateProcessor.java:296)
 at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.deployWebServices(WSUpdateProcessor.java:262)
 at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:155)
 ... 21 more
 Caused by: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common deployment exception! The reason is: Error occurred, parsing com.sap.engine.services.webservices.server.deploy.descriptors.sapwebservices.WSDescriptor descriptor, application sap.com/TimeoffService, web service timeoffServiceConfig, location message: type: jar file, location: E:\usr\sap\SIC\DVEBMGS01\j2ee\cluster\server0\.\temp\deploy\work\deploying\reader1186995503687\TimeoffService.wsar . . Additional info:
 at com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDescriptor(WSDefinitionFactory.java:907)
 at com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.loadWebService(WSDefinitionFactory.java:176)
 at com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.loadWebServices(WSDefinitionFactory.java:158)
 at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.generateDeployFiles(WSUpdateProcessor.java:284)
 ... 23 more
 Caused by: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common deployment exception! The reason is: Error occurred, trying to parse source type: zip entry, zip file location: E:\usr\sap\SIC\DVEBMGS01\j2ee\cluster\server0\.\temp\deploy\work\deploying\reader1186995503687\TimeoffService.wsar, entry: dsta/timeoff/test/business/TimeoffServiceVI.videf . Additional info:
 at com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseVI(WSDefinitionFactory.java:925)
 at com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDescriptor(WSDefinitionFactory.java:817)
 ... 26 more
 Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.XmlUnmarshalException: XML Deserialization Error. XML Node [VirtualInterface.Functions][http://xml.sap.com/2002/10/metamodel/vi] have minOccurs>0 in schema definition but is missing in node [VirtualInterface][http://xml.sap.com/2002/10/metamodel/vi].
 at com.sap.engine.services.webservices.jaxrpc.encoding.GeneratedComplexType._loadInto(GeneratedComplexType.java:1197)
 at com.sap.engine.services.webservices.jaxrpc.encoding.GeneratedComplexType.deserialize(GeneratedComplexType.java:945)
 at com.sap.engine.services.webservices.server.deploy.descriptors.vi.VInterfaceParser.getVInterface(VInterfaceParser.java:46)
 at com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseVI(WSDefinitionFactory.java:920)
 ... 27 more
 at com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException.writeReplace(WSDeploymentException.java:64)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:896)
 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1011)
 at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
 at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
 at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
 at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
 at com.sap.engine.services.rmi_p4.DispatchImpl.throwException(DispatchImpl.java:144)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:322)
 ... 8 more

Hi Paul..
 This is a common problem when you are working with webservices, i have worked with them and not always the response of the ws comes like de wsdl says, depends of your wsdl provider.
 I suggest you that checks your response of your webservice with the Enterprise Portal Web Services Checker View
For see this view in NetWeaver go to Window > Show View > Other > Enterprise Portal Web Services Checker
Put the wsdl url definition in wsdl url textbox
and the click in the letter W, this procedure brings you all methods and everything for play with the WEB Services.. and you can check the response of you webservices call funtion, checks that all the tags comes like says in the wsdl
Good luck
Joshua

How to debug AIA XSLT transformation in Jdeveloper ?

Hi AIA forum members,
I need to Test and debug an AIA XSL transformation. Can i use Jdeveloper to do this ?
I understand that we can test by right clicking and using the "Test" option but then again it fails while processing the XSL as it is unable to execute lookupXRef, lookupDVM and also is not able to recognise the oracle xpath extension functions.
Rgds,
Vik

Hi Vik,
If you are on 10g, I suggest you run a search on Metalink for AIA Jdeveloper Patch download. Install the patch for Jdeveloper on windows and then you should be able to test the XSLs.
If its on 11g, am not sure, as I have just started looking for that patch.
Cheers,
- AR

How to debug XSLT in BPEL

Hello,
I am getting issue in BPEL code while executing XSLT file. If I have performed the 10 mappings in XSLT file and one of them has error in assigning source to target values. Its just mentioned that following XSLT file has error and doesn't mention the exact line where the error has been occured.
Any best way to debug XSLT so it can provide the exact error ?
Thanks

Yes, It is the part of BPEL. But I am using Oracle SOA 10 g. Can you please elaborate how can I debug the XSLT is BPEL using BPEL Console in 10g ?? Actually when I am getting issue in XSLT, it's hard to find out where I am having the problem. If I am performing more than 20 transformation in XSLT file it's impossible for me to highlight the exact line where I have an issue.
Thanks

How To: Debug missing Drivers in MDT

The definitive post on missing drivers in MDT (most comprehensive list I've done so far)…
Please to NOT post questions from this thread, instead create a new thread.
How to debug Network Driver Problems
One of the earliest hurdles an MDT administrator will come across is the management of device drivers, specifically networking drivers. With most other drivers, like Audio, printer, and video drivers, a quick call to Windows Update or install over the network
will resolve the Installation. However unless the Network (and storage) Drivers are installed into Windows from the start, it will be much more difficult to install the rest of the system.
This post should help you get started if you find a machine that did not install a device driver properly, and you want to know how to find and import the correct drivers.
Installing network drivers in the
full OS
Step 1 - Try network connection again
It's possible that you might get a DHCP error from MDT, but when you try again later to connect the Deployment Share it works! This may be caused by a slow or malfunctioning DHCP server in your network. Re-check your DHCP servers, ensure that PortFast is enabled
on your routers. If all else fails get your network administrators to document the DHCP delay. A long delay in modern networks is unnecessary.
Step 2 - Verify connectivity
You may not have a driver problem but a network problem. Check the physical connection on the computer (Network installs on MDT *REQUIRE* a wired network connection, no Wi-Fi). Open a web browser. Check the IP Address (ipconfig.exe /all). Ping the Deployment
Server, manually connect to the Deployment Share. IF you can't connect to the Deployment Share, neither can MDT.
Step 3 - Find the Correct Driver Package
Before you load the driver into MDT, first verify that you have the correct driver. There are scenarios where you may *think* you have the correct driver, but the driver will never run because the package is designed for a different OS/SKU/Platform/whatever.
Install the driver package by:
  ○ Open the Device Manager (devmgmt.msc).
  ○ Find the network device in the list (ensure this is the wired device, not the wireless device)
  ○ Right click on "Properties" and click on the "Details" tab.
  ○ From the "Details" tab, select the property "Hardware Ids" select all the values, and copy to the clipboard, it would be a good idea to save for later. Should look something like:
      PCI\VEN_8086&DEV_1502&SUBSYS_21F317AA&REV_04
      PCI\VEN_8086&DEV_1502&SUBSYS_21F317AA
      PCI\VEN_8086&DEV_1502&CC_020000
      PCI\VEN_8086&DEV_1502&CC_0200
  ○ From the "Driver" tab, click on "Update Driver…", click on "Browse my computer for driver software" locate the driver package on the local machine or USB Drive, and install the package.
  ○ You should get a confirmation that the driver package was installed.
  ○ IF you do not get confirmation, MDT driver installation may not work.
Windows will install the driver starting with the *.inf install package, and will typically include a *.sys (binary) and a *.cat (digital Signature). If the driver package has been re-packaged into a *.cab, *.zip, or other compressed *.exe file, the
package must be extracted first. This is a hard requirement for any driver used by MDT and/or SCCM. All driver packages that are signed by Microsoft (WHQL) will be installed from the *.inf file, and you should only use devices that have the Microsoft WHQL
Logo as a sign of quality.
If you need a help on where to find driver packages for your devices, the 3 largest Computer OEM manufacturers supply drivers grouped by Make and Model that are easily imported into MDT and SCCM. See:
http://deploymentbunny.com/2014/07/08/back-to-basicwhere-to-find-drivers-for-servers-and-clients/
Step 4 - Load driver into MDT
If you have more than 20 driver packages, or if you anticipate you will have more than 20 drivers, you should start grouping your drivers in sub-folders for organization. One popular method is to group by Computer Make and Model. Ensure that you are using the
correct Driver Selection Profile in your task sequence. If you are unsure, disable any selection profile(s) to ensure the driver is installed correctly.
Step 5 - Run the full MDT installation
During installation MDT will perform the following:
  ○ Run the PNPEnum.exe utility and capture output to PnPEnum.xml. The VEN_Xxxx and DEV_Yyyy from the "HardwareIDs" property above must be present in this list. Otherwise we won't have a match.
  ○ Search through the %DeployRoot%\control\drivers.xml file looking for a match for the HardwareID. MDT may filter the search based on the folder search type.
  ○ MDT will copy each matching driver to the local c:\drivers directory using the xcopy.exe command. You can search (grep) for the string "xcopy" in the ZTIDrivers.log file, that will get you list of all driver packages matched by MDT.
  ○ MDT will allow the machine to boot into the NEW OS, and Driver Installation will begin in the OS. IF there are multiple drivers found and copied locally, the Windows (not MDT) will determine the best one. The c:\windows\inf\SetupAPI.*.log files
will detail which drivers copied locally were installed (or *not* installed).
Installing Network Drivers in
WinPE
Step 6 - Try the network connection again
(See above
Step 7 - Verify Connectivity from within WinPE
Verifying network connectivity will be a bit more difficult in WinPE, since we have a limited User Interface, so all investigation must be done in the debugging mode (Press F8) cmd.exe
  ○ Try connecting to the Deployment Share:
  c:\> net use * \\MDT\DeploymentShare$ /u:UserDomain\UserName *
  ○ Try pinging the Deployment Server:
  c:\> Ping.exe MDT.Corp.contoso.com
  ○ Verify that you have an IP address ( ipconfig /all ) If you have an AutoConfiguration address - Driver OK - WinPE can't reach the DHCP server. If you have "Media Disconnected" - Driver OK - Physical adapter not plugged to network. If
no devices are listed - Driver bad - Driver not installed.
  ○ Check the x:\windows\system32\WpeInit.log - This log will show the network driver (if found) being installed.
Step 8 - Verify driver packages are getting included into WinPE
Firstly, verify the correct driver package from within the full OS above. By default MDT will import *all* Storage and Networking drivers into your WinPE image. However it is possible to change the subset of files copied via "Selection Profile" or
other method. Cross check your WinPE Driver Settings.
  ○ From within the MDT console, right click on the root of your Deployment Share and select properties.
  ○ Click on the "Windows PE" tab, and the "Drivers and Patches" sub tab for both x86 and x64.
  ○ Your Network Drivers package must be in the "Selection Profile" if enabled.
Finally verify that the correct Network Driver package is being copied to WinPE. If necessary this may include setting up a debugger to watch the MDT Provider build the WinPE Image from scratch. My preference is to use the SysInternals
http://live.sysinternals.com/Dbgview.exe tool.
  ○ Open up the MDT console.
  ○ Download and run the DbgView.exe tool.
  ○ Update the deployment share in question.
  ○ The DbgView tool should show what drivers were copied to each WinPE Image.
Other
Whenever you add a driver into the MDT console, you must update the deployment share for that drivers to be added to your WinPE Image. If you are unsure, select "Completely regenerate the boot images." to ensure the drivers is imported. Additionally,
you must copy the updated LitetouchPE_x??.wim and *.iso files to the other consumers of the WinPE image like WDS/PXE and or any USB offline media.
Note that some Broadcom NetXtreme class of drivers have a multi-function driver architecture that may have difficulty loading in WinPE. Ensure that you load the "RIS" class of drivers from Broadcom in your MDT environment.
Note that by default MDT does *NOT* support the installation of Windows over Wireless network devices (Wi-Fi). The MDT installation sources must either be available through wired networking, or offline (USB Flash) media.
This post does not discuss origination of drivers within MDT ( Chaos vs. Total Control ), that is a different topic.
http://www.deploymentresearch.com/Research/tabid/62/EntryId/112/MDT-2013-Lite-Touch-Driver-Management.aspx
Further Help
If you are still having problems with drivers in via MDT, ask the experts in the MDT Technet Forum:
Include a short description of the problem. Including the Make/Mode if necessary.
Include the HardwareIDs from the Device Manager (Devmgmt.msc) into the post (from above).
Copy your known good driver package (step 3 above) to OneDrive.
Copy the following log files to a public site like OneDrive and include the link:
  ○ PnpEnum.xml (from Client)
  ○ Bdd.log (From Client) - or at least the ZTIDrivers.log file.
  ○ c:\windows\inf\SetupAPI.*.log (from client)
  ○ %DeployRoot%\control\Driver*.xml
  ○ %DeployRoot%\control\SelectionProfile*.xml
  ○ %DeployRoot%\control\settings.xml (if problems in WinPE)
  ○ x:\windows\System32\WpeInit.log (if problems in WinPE)
  ○ If the MDT server is not including your driver package in WinPE include the DBGView log.
This post is by Keith Garner - Keith was a developer on the MDT team where he developed the ZTIDrivers.wsf script, he also worked for the Windows Hardware Quality Labs as a technical PM on Driver Quality, and developed samples for the
Microsoft Device Driver Kit (DDK) specifically around the area of Device Driver installation in the OS (Windows NT 5.0, 2000 and Windows XP). (So yes, I know drivers :^).
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

OK. I have redone the drivers for WinPE which has reduced the image size by about 200MB. Unfortunately the problem persists.
Is there anyway to turn on some sort of boot logging so I can see what driver it is failing on?
I am also still seeing the weird behavior of it working over PXE but blue screens when booting from USB. Can anyone explain that?
JJ

How to debug adapter module in PI 7.1

Hello all,
I am trying to figure out how to debug adapter module in PI 7.1.
I guess runtime debugging ( switch AS java in debug mode and attach NWDS to the AS Java to debug as module is being executed) is not possible with adapter module. Please let me know if this is indeed possible and how to enable it.
The only option is to send debug information to log file. So in the module code like:
audit.addAuditLogEntry(key, status, message);
location.debugT(SIGNATURE, message);
I've read that for PI 7.0, you need to add log-configuration.xml to meta-inf. Is this still required for PI 7.1?
My next question is how to read the log in audit log and in location. I've read that the audit log can be read in .../MessagingSystem/monitor/monitor.jsp, under which section of the page I can read the audit log? I can't see any of my log there.
For log in location, I guess I need to go to NWA, can you please share the path (navigation) in NWA to see the location?
Thanks
Jayson

> I guess runtime debugging ( switch AS java in debug mode and attach NWDS to the AS Java to debug as module is being executed) is not possible with adapter module. Please let me know if this is indeed possible and how to enable it.
It is possible for adapter modules as well. I know this from our developers
It should work like this:
/people/christian.drumm/blog/2008/09/30/debugging-java-mappings-using-sap-netweaver-developer-studio
> The only option is to send debug information to log file. So in the module code like:
> audit.addAuditLogEntry(key, status, message);
> location.debugT(SIGNATURE, message);
> My next question is how to read the log in audit log and in location. I've read that the audit log can be read in .../MessagingSystem/monitor/monitor.jsp, under which section of the page I can read the audit log?
In the RWB under Message Monitoring for Adapter, or try the shortcut
http://server:port/mdt

HELP: JSP + XML + XSLT = HTML?

Hello, all.
I am trying out Weblogic 6 and I am trying to get the JSP + XML + XSLT =>
HTML chain working.
I am coming from using Orion and SAXON.. and in that situation I had a JSP
that contained XML tags... they were filled in at runtime and then using
Servlet-Chaining was passed along to the SAXON XSLT Processer. SAXON checked
for the inline XSL specified and then used that to transform the document
into HTML.
It worked well, but there were some other features missing/not documented
that we now need.
With Weblogic I am trying to use the XSLT Tag Library that comes with the
distribution, but it seems to be very finicky. I followed the directions and
I got it to do a sort of roundabout transformation. But it doesn't seem to
work quite right.
The best I can get is the following:
I have an 'xslt' directory url-pattern-mapped to xslt.jsp (as instructed)...
but can't figure out how to specify the xsl file on-the-fly... that is, if I
don't hard-code the XSL file in the x:xslt element in the xslt.jsp it
complains about some XML file not having a root element.
Ideal situation:
1. I have a JSP that includes XML elements.
2. It is filled from a database at runtime and specifys (using a PI) what
XSL stylesheet it is to be processed with.
3. Somehow (fingers crossed) the XML is processed and transformed into HTML
by the appropriate XSL file.
I think I am mostly stuck moving between steps 2 and 3.
Can anyone give me some hints? Are there some Weblogic specific
elements/tags that I have to include in the XML file that Weblogic will
catch and re-direct to the XSL Parser?
Please, anyone, if you have some information, I would much appreciate it.
Dylan Parker
PS - I apologize for the cross-post, I hope it doesn't cause too much
traffic.

Craig,
I've since discovered how to do it with the WL Taglibrary... and have
moved on =)
It has to do with the EXTREMELY BADLY documented x:xml tag that can
appear within the x:xslt tag body...
So the WL Tag Library allows something like the following.
(Please note, angled brackets are omitted in this post to prevent html
parsing)
[x:xslt stylesheet="sheet.xsl"]
[x:xml]
Here is the XML to run the sheet on.
This should have all relevant XML syntax: the PIs, the doctype,
root elements etc...
[x:xml]
[x:xslt]
And that DOES work. But not very well. WL, a little prematurely
incorporated versions 1.2 of Xerces and Xalan in their product -- and
these versions have some irritating bugs.
Also -- There tag library doesn't copy the source XML across as UTF-8
.. so a lot of the Japanese I have embedded there (from a DB) gets
mangled somewhere in their code...
AND -- If you hammer a little bit on an JSP/XML that uses the WL Tag
Library (eg clicking refresh lots of times in IE)... I get huge
amounts of irritating exceptions appearing in the log files.
NullPointerExceptions
XSL Parsing Exceptions
XML Parsing Exceptions
but completely unpredictably...
In my eyes.. the WL XML/XSL Tag Library using the incorporated and
untouchable Xalan and Xerces (v1.2) is virtually unusable.
What a pain.
BUT! Apache offers a similar OPEN SOURCE XSL Tag Library available
here:
http://jakarta.apache.org/taglibs/doc/xsl-doc/intro.html
And it uses the standard, non-weblogic-incorporated, Xerces and Xalan
(which means you can provide whatever version you want).. and it works
impressively well.
It has almost identical performance as the WL Taglib, and without all
of the bizarre exceptions being thrown.
And it does proper passing of the character encoding type!
If only the taglib did caching though =(
The performance hit over pure JSP is huge. Almost two orders of
magnitude. On my desktop box I can get around 500Requests/Sec if I am
returning HTML direct from a JSP... while if I produce XML that gets
processed by XSL into HTML the Requests/Sec drops to 5!!!!
Caching. Caching. And more Caching. A lot of DiskIO is going on with
the XML/XSL/XHTML chain of events.
I hope this helps!
I'd be curious as to what you find out as well.
Dylan Parker
On 5 Mar 2001 07:20:00 -0800, "Craig Macha"
<[email protected]> wrote:
>
Yep, I feel Dylan's pain.
I am trying to accomplish the same thing. A JSP page generating
dynamic XML content and then utilizing an XSLT stylesheet to transform
all the content into XHTML.
Does anyone have some examples that show exactly how to accomplish
this? Can I do this with WLS and the XML taglib that comes with
it? Or do I have to move on to something like Cocoon to get this
capability?
Any insight would be greatly appreciated.
Thanks,
Craig Macha
"Dylan Parker" <[email protected]> wrote:
Hello, all.
I am trying out Weblogic 6 and I am trying to get the
JSP + XML + XSLT =>
HTML chain working.
I am coming from using Orion and SAXON.. and in that situation
I had a JSP
that contained XML tags... they were filled in at runtime
and then using
Servlet-Chaining was passed along to the SAXON XSLT Processer.
SAXON checked
for the inline XSL specified and then used that to transform
the document
into HTML.
It worked well, but there were some other features missing/not
documented
that we now need.
With Weblogic I am trying to use the XSLT Tag Library
that comes with the
distribution, but it seems to be very finicky. I followed
the directions and
I got it to do a sort of roundabout transformation. But
it doesn't seem to
work quite right.
The best I can get is the following:
I have an 'xslt' directory url-pattern-mapped to xslt.jsp
(as instructed)...
but can't figure out how to specify the xsl file on-the-fly...
that is, if I
don't hard-code the XSL file in the x:xslt element in
the xslt.jsp it
complains about some XML file not having a root element.
Ideal situation:
1. I have a JSP that includes XML elements.
2. It is filled from a database at runtime and specifys
(using a PI) what
XSL stylesheet it is to be processed with.
3. Somehow (fingers crossed) the XML is processed and
transformed into HTML
by the appropriate XSL file.
I think I am mostly stuck moving between steps 2 and 3.
Can anyone give me some hints? Are there some Weblogic
specific
elements/tags that I have to include in the XML file that
Weblogic will
catch and re-direct to the XSL Parser?
Please, anyone, if you have some information, I would
much appreciate it.
Dylan Parker
PS - I apologize for the cross-post, I hope it doesn't
cause too much
traffic.

HOw to update XML file residing in DAM by component JSP in run-time?

i have made a component which reads xml file residing in DAM.
Content Author can fill some values in dialog of this component, as soon as author provide the values,i have to update these values in XML file and component reloadsby reading the updated xml file.
i am trying to achieve this by making object of XML file and giving it's path., but i ma unable to access the XML file.
Can anyone help me out to how to update XML file by component JSP in run-time?

Now the changed data must be exported back into the XML file, meaning that the content of certain elements must be updated. How can this be done with XSLT?
XSLT approach: check these online tutorial
http://www.xml.com/pub/a/2000/08/02/xslt/index.html
http://www.xml.com/pub/a/2000/06/07/transforming/index.html
ABAP approach:
for example you have the xml (original) in a string called say xml_out .
data: l_xml type ref to cl_xml_document ,
        node type ref to if_ixml_node .
create object l_xml.
call method l_xml->parse_string
exporting
    stream = xml_out.
node = l_xml->find_node(
    name   = 'IDENTITY'
   ROOT   = ROOT
l_xml->set_attribute(
    name    = 'Name'
    value   = 'Charles'
    node    = node
(the above example reads the element IDENTITY and sets attribute name/value to the same)
like wise you can add new elements starting from IDENTITY using various methods available in class CL_XML_DOCUMENT
so how do I access the XML file in order to update it?
you have already read this XML into a ABAP variable right?
Sorry couldnt understand your whole process, why do you need to read local XML file?
Raja

How to open XML file in Netscape

How to open XML file in Netscape.....
XML file is opening correctly in IE, but giving error in Netscape.Error is
Error loading stylesheet: Parsing and XSLT stylesheet failed....
Reply me soon..............

You may check these tips:
How to Access Local File Systems from J2ME devices using FileConnection API
http://www.java-tips.org/content/view/109/73/
Opening and reading a file on the mobile device
http://www.java-tips.org/content/view/352/73/

JSP vs. XML/XSLT

Hi all!
I'm in a bit of a dilema. As the least knowledgable member of our small development group (3 people incl. me) I'm caught in the middle of a pretty fierce debate over whether or not to we should implement JSP.
Currently to seperate business logic from presentation we have our servlets pass XML to the browser and then the browser renders the HTML using the appropriate .xsl (sometimes we use server-side transformation).
Now one of the guys wants to use MVC/Struts and JSPs in order to create a much needed UI for an application. The plan is to not put any Java code in the JSP (seperation of logic and presentation - good, business logic in both the JSP and Servlet - bad.) but the other guy is still vehemently against it.
He says that anything JSP can do we can already do with XML/XSLT and to add JSP to our environment would complicate things.
And while I agree with him there, there are some things that when you do them with JSPs make the code more readable and transparent.
If you had to take a side, which one would you choose?
Has anyone else out there already gone through this debate? I'd be interested in knowing the outcome.
Thanks,
John

I have a couple of comments.
1> "XML to the browser and then the browser renders the HTML using the appropriate .xsl"
I all cases you should do the transformations on the server. Lot of browser do not know how to
do a xsl transform. And since you can do it some time why not do it not everytime?
2> "business logic in both the JSP and Servlet"
Business logic should neither be in servlets nor in jsp. I think they should be in business logic beans.
3> "anything JSP can do we can already do with XML/XSLT "
Although anything can be done using xml/xsl or jsp there are a bit of differences where struts-jsp architecture is more perferable.
Imaging a web site which has lots of online forms(with textfiedls, checkboxes, select lists, etc) which are to be validated and if some validation fails the same form is to be shown with the values already submitted prefilled. Doing this with xml/xsl or even simple jsp could be a nightmare.
But if you use struts MVC architecture with jsp and struts taglib this will be very very simple.
Introducing struts-jsp will not complicate things and if the scnario described above is there or could arise in your application then you should seriously think about using struts+jsp. That does not mean you will have to scrap you xml+xsl architecture. You can still generate the xml using your action bean , put the xml in request and forward it to you jsp for rendetion. The jsp page could then use a taglib which has the xsl transformation code to do the xslt transformation.
The above comments are not just my thoughts but i have also implemented/experienced the above during various projects and they have proved to be useful.
Cheers!

How to Debug - Badi BBP_SAPXML1_IN_BADI

Hello Experts,
Could you please guide me that how to debug this badi - BBP_SAPXML1_IN_BADI.
Will this badi works for Schedule agreement release?
Thanks in advance.
Aakash

you have to use the transaction sxi_support to debug the inbound xml document.
get the xml document , insert the payload , use /h for debugging , place the breakpoint and execute.

Turning XML/XSLT files into a working Web Template

I've scoured these and other forums for this small piece of information, so I apologize if it's been answered already, but I can't find it.
I understand that the web templates in Lightroom are done in XML/XSLT, with the XML file named galleryMaker.xml and the XSLT file named transformer.xslt. However, I cannot figure out how to get these files to show up as a template in Lightroom.
I am on a Windows XP machine, and all the templates show up in Application Data/Lightroom/Web Templates, but they are all of the type *.lrtemplate. Is there a way to convert the XML/XSLT set of files into an lrtemplate file? Or is there something else I'm supposed to do?

Splatt42 wrote:
I have an executable binary program (that runs just fine on it's own) that I needed to turn into a service (call it "foo"). I did so using the .xml file below, and it does indeed start up at boot, runs in the background,When you run your program (/usr/bin/foo), does it daemonize itself (kind of like running /usr/sbin/sshd), or would you have to do it yourself if run from the shell ('/usr/bin/foo &')?
and does everything it should. I've noticed a couple of problems, though. If I execute an init 0, the system hangs and never gets to the OK prompt. If I disable my service, an init 0 completes without any problems. An init 5 works OK, as does a shutdown from the desktop. I'm not sure what could be causing this. I thought maybe because the service was restarted over and over again...?
I gave my service a timeout value of "0", as I found that when I gave it any other value the service stopped running when the timeout expired. A seeming side effect is that my service is never listed as running, as it's start method (itself) hasn't yet completed.The manifest doesn't really want your binary as the start method. It wants to run something that starts the service, and will exit with status 0 if the startup was successful, and non-zero if the startup was unsuccessful. So you might want to write a small wrapper script (like an init.d startup script).
Take a look at the sshd.xml manifest. It doesn't start sshd, it runs '/lib/svc/method/sshd start', which is responsible for starting sshd.
Darren

How to debug a runtime stack underflow error?

I'm really struggling to resolve a stack underflow that I'm getting. The traceback I get at runtime is:
VerifyError: Error #1024: Stack underflow occurred.
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at flash.net::URLLoader/onComplete()
This is particularly difficult to debug because when I run in debug mode it does not happen at all. It only happens when compiled as a release.
Does anyone have any tips on how to debug a Stack Underflow? Are have a clean explanation of what that means for Flash?
In case it helps, this error is occurring when I click a button whose handler makes an RPC call, which uses a URLLoader, an AsyncToken, and then invokes the set of AsyncResponder instances associated with the AsyncToken. With some server-side logging as well as some logging hacked into the swf, I know that the UrlLoader is successfully doing and GET'ing a crossdomain.xml file, is correctly processing it (if I wreck it, I get a security error), and is also successfully completing the "load" request (the server sends the data)... the underflow seems to be happening in the Event.COMPLETE listening/handling process (as is, of course, implied by the traceback as well).
mxmlc used = from flex_sdk_4.5.0.20967
Example player (I've tried a few) = 10.2.153.1

Peter Blazejewicz wrote:
crossposted:
http://stackoverflow.com/questions/6270837/how-to-debug-a-runtime-stac k-underflow-error
Yes... I intended to say so here but didn't get to it yet. View traffic was extremely low here and I thought I'd see how stackoverflow compared. I tend to check there first for most languages usually, but thought I'd try here as well to see if I should break that habit.
As per the SO post, my specific problem was resolved by switching my variable initialization routine from the "initialize" application event, to the onCompletion event. Although I am obviously "happy" about this since this issue cost me a lot of time and hair, it does not really indicate how I would go about debugging such an internal error in the future, so the question is technically unanswered.
As to the question from Flex harUI, I am compiling indirectly via the MXMLC in the SDK, through the Amethyst Visual Studio plugin (which I'm auditioning). The only libraries involved are from the flex_sdk_4.5.0.20967 SDK. The project is quite small (a test project), consisting only of 1 MXML file and 2x .AS files.

How to convert xml data into html format in bpel

Hi ,
Can any one tel me how to conevrt xml into html in oracle bpel.
Does bpel support this functionality or not.
Regards,
Ana
Edited by: user10181991 on Apr 5, 2009 11:16 PM

Ana,
We are doing the same thing--using one variable with the schema as the source of the .xsl and assigning the resulting html to another variable--the content body of the email, in our case. I just posted how we did it here: Re: Using XSLT to generate the email HTML body
Let me know if this helps.

How to read XML message present in Table using PL/SQL?

Hi,
How to read XML content present in Table using PL/SQL .And is it possible to parse the xml uisng xslt and insert xml output in same table again ?
Thanks!

Late reply, but hopefully better late than never.
You can possibly do it all via a single SQL statement, such as {message:id=4232077}
XMLTable Syntax can be found at http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/functions228.htm#CIHGGHFB (for 10.2 users) else find your correct version at http://www.oracle.com/technology/documentation/index.html

How to debug XML&&XSLT?

Similar Messages

Maybe you are looking for