White space error

Hi all,
I am getting White space error how to avoid it...
I found it was caused due to & symbol in the particular field.
Please suggest how to rectify this....
Regards
Rajesh

Hi all,
I am waiting for your reply...
Sample code of my error:
<ROW>
<GL_PRODUCT>0100</GL_PRODUCT>
<PRODUCT_LINE>0100</PRODUCT_LINE>
<CAMPAIGN_NUMBER>GB000563</CAMPAIGN_NUMBER>
<LEGACY_NUMBER>M6421</LEGACY_NUMBER>
<CAMPAIGN_DESCRIPTION>MINI BULK</CAMPAIGN_DESCRIPTION>
<NATURAL>5000</NATURAL>
<SOURCE>PROMOTION COSTING</SOURCE>
<ORG_ID>177</ORG_ID>
<TO_JUL>-14247.05</TO_JUL>
<TO_AUG>0</TO_AUG>
<TO_SEP>0</TO_SEP>
<TO_OCT>0</TO_OCT>
<TO_NOV>0</TO_NOV>
<TO_DEC>0</TO_DEC>
<TO_JAN>0</TO_JAN>
<TO_FEB>0</TO_FEB>
<TO_MAR>0</TO_MAR>
<TO_APR>0</TO_APR>
<TO_MAY>0</TO_MAY>
</ROW>
- <ROW>
<GL_PRODUCT>0100</GL_PRODUCT>
<PRODUCT_LINE>0100</PRODUCT_LINE>
<CAMPAIGN_NUMBER>GB000563</CAMPAIGN_NUMBER>
<LEGACY_NUMBER>M6421</LEGACY_NUMBER>
<CAMPAIGN_DESCRIPTION>MINI BULK</CAMPAIGN_DESCRIPTION>
<NATURAL>5004</NATURAL>
<SOURCE>PROMOTION COSTING</SOURCE>
<ORG_ID>177</ORG_ID>
<TO_JUL>-4864.22</TO_JUL>
<TO_AUG>0</TO_AUG>
<TO_SEP>0</TO_SEP>
<TO_OCT>0</TO_OCT>
<TO_NOV>0</TO_NOVThe XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.
End tag 'CAMP' does not match the start tag 'CAMPAIGN_DESCRIPTION'. Error processing resource 'http://.........
<CAMPAIGN_DESCRIPTION>MINI BULK</CAMP
-----------------------------------^
>
<TO_DEC>0</TO_DEC>
<TO_JAN>0</TO_JAN>
<TO_FEB>0</TO_FEB>
Please help to solve this issue...
Regards
Rajesh

Similar Messages

JDeveloper Error: White spaces are required between publicId and systemId.

I'm using JDeveloper 10.1.3.1.0.
This error is occurring in a BPEL process project.
With one particular web service I have, adding a Partner Link to the BPEL generates the following compile error:
Error: White spaces are required between publicId and systemId.
I can add Partner links from other web services and the BPEL will compile fine. The main difference I can see is that this web service supports WS-Addressing.
I have found one other reference to a similar (but not exactly the same) problem elsewhere in these forums but the fix is not really applicable. All of the wsdl files pass the "Validate WSDL" operation, and I don't see anything wrong with them.
When the error occurs and I select "Go To Source" it points back to the first line of the bpel file.
Can anyone help me out on this?
This is the wsdl for the web service, wsademo.wsdl:
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="wsademo"
targetNamespace="http://localhost:11001/wsademo.wsdl"
xmlns:tns="http://localhost:11001/wsademo.wsdl"
xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope"
xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
xmlns:ns="http://localhost:11001/wsademo.wsdl"
xmlns:SOAP="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:MIME="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:DIME="http://schemas.xmlsoap.org/ws/2002/04/dime/wsdl/"
xmlns:WSDL="http://schemas.xmlsoap.org/wsdl/"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<types>
<schema targetNamespace="http://localhost:11001/wsademo.wsdl"
xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope"
xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
xmlns:ns="http://localhost:11001/wsademo.wsdl"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="unqualified"
attributeFormDefault="unqualified">
<import namespace="http://schemas.xmlsoap.org/ws/2004/08/addressing"/>
<import namespace="http://www.w3.org/2003/05/soap-encoding"/>

<element name="wsademoResult">
<complexType>
<sequence>
<element name="out" type="xsd:string" minOccurs="0" maxOccurs="1" nillable="true"/>
</sequence>
</complexType>
</element>

<element name="wsademo">
<complexType>
<sequence>
<element name="in" type="xsd:string" minOccurs="0" maxOccurs="1" nillable="true"/>
</sequence>
</complexType>
</element>

<element name="wsademoResult">
<complexType>
<sequence>
<element name="out" type="xsd:string" minOccurs="0" maxOccurs="1" nillable="true"/>
</sequence>
</complexType>
</element>
</schema>
</types>
<message name="wsademoResult">
<part name="parameters" element="ns:wsademoResult"/>
</message>
<message name="wsademo">
<part name="parameters" element="ns:wsademo"/>
</message>
<message name="wsademoResult">
<part name="parameters" element="ns:wsademoResult"/>
</message>
<message name="wsademoHeader">
<part name="MessageID" element="wsa:MessageID"/>
<part name="RelatesTo" element="wsa:RelatesTo"/>
<part name="From" element="wsa:From"/>
<part name="ReplyTo" element="wsa:ReplyTo"/>
<part name="FaultTo" element="wsa:FaultTo"/>
<part name="To" element="wsa:To"/>
<part name="Action" element="wsa:Action"/>
</message>
<portType name="wsademoPort">
<operation name="wsademoResult">
<documentation>accepts a string value from a relayed response</documentation>
<input message="tns:wsademoResult"/>
</operation>
<operation name="wsademo">
<documentation>echos a string value and relays the response to the wsa replyTo address (if present)</documentation>
<input message="tns:wsademo"/>
<output message="tns:wsademoResult"/>
</operation>
</portType>
<binding name="wsademo" type="tns:wsademoPort">
<SOAP:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="wsademoResult">
<SOAP:operation soapAction="urn:wsademo/wsademoPort/wsademoResult"/>
<input>
<SOAP:body parts="parameters" use="literal"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="Action"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="To"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="FaultTo"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="ReplyTo"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="From"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="RelatesTo"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="MessageID"/>
</input>
</operation>
<operation name="wsademo">
<SOAP:operation soapAction="urn:wsademo/wsademoPort/wsademo"/>
<input>
<SOAP:body parts="parameters" use="literal"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="Action"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="To"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="FaultTo"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="ReplyTo"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="From"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="RelatesTo"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="MessageID"/>
</input>
<output>
<SOAP:body parts="parameters" use="literal"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="Action"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="To"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="FaultTo"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="ReplyTo"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="From"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="RelatesTo"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="MessageID"/>
</output>
</operation>
</binding>
<service name="wsademo">
<documentation>demonstrates WS-Addressing capabilities</documentation>
<port name="wsademo" binding="tns:wsademo">
<SOAP:address location="http://localhost:11001"/>
</port>
</service>
</definitions>
This is the wsdl that is generated by JDeveloper that contains the PartnerLinks and refernce back to the original wsdl file, wsademoRef.wsdl:
<definitions
name="wsademo"
targetNamespace="http://localhost:11001/wsademo.wsdl"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://localhost:11001/wsademo.wsdl"
xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>
<import namespace="http://localhost:11001/wsademo.wsdl" location="wsademo.wsdl"/>
<plnk:partnerLinkType name="wsademoPort_PL">
<plnk:role name="wsademoPort_Role">
<plnk:portType name="tns:wsademoPort"/>
</plnk:role>
</plnk:partnerLinkType>
</definitions>
And finally the is the BPEL, WSAtest3.bpel:
<?xml version="1.0" encoding="UTF-8"?>

<process name="WsaTest3" targetNamespace="http://xmlns.oracle.com/WsaTest3"
xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:xp20="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20"
xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:ns1="http://localhost:11001/wsademo.wsdl"
xmlns:ldap="http://schemas.oracle.com/xpath/extension/ldap"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:ns2="http://localhost:80/Service.wsdl"
xmlns:client="http://xmlns.oracle.com/WsaTest3"
xmlns:bpelx="http://schemas.oracle.com/bpel/extension/"
xmlns:ora="http://schemas.oracle.com/xpath/extension"
xmlns:orcl="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc">

<partnerLinks>

<partnerLink name="client" partnerLinkType="client:WsaTest3"
myRole="WsaTest3Provider"/>
<partnerLink name="wsademo" partnerLinkType="ns1:wsademoPort_PL"
myRole="wsademoPort_Role" partnerRole="wsademoPort_Role"/>
</partnerLinks>

<variables>

<variable name="inputVariable" messageType="client:WsaTest3RequestMessage"/>

<variable name="outputVariable"
messageType="client:WsaTest3ResponseMessage"/>
<variable name="Invoke_1_wsademo_InputVariable" messageType="ns1:wsademo"/>
<variable name="Invoke_1_wsademo_OutputVariable"
messageType="ns1:wsademoResult"/>
</variables>

<sequence name="main">

<receive name="receiveInput" partnerLink="client" portType="client:WsaTest3"
operation="process" variable="inputVariable" createInstance="yes"/>

<assign name="Assign_1">
<copy>
<from variable="inputVariable" part="payload"
query="/client:WsaTest3ProcessRequest/client:input"/>
<to variable="Invoke_1_wsademo_InputVariable" part="parameters"/>
</copy>
</assign>
<invoke name="Invoke_1" partnerLink="wsademo" portType="ns1:wsademoPort"
operation="wsademo" inputVariable="Invoke_1_wsademo_InputVariable"
outputVariable="Invoke_1_wsademo_OutputVariable"/>
<assign name="Assign_2">
<copy>
<from variable="Invoke_1_wsademo_OutputVariable" part="parameters"/>
<to variable="outputVariable" part="payload"
query="/client:WsaTest3ProcessResponse/client:result"/>
</copy>
</assign>
<reply name="replyOutput" partnerLink="client" portType="client:WsaTest3"
operation="process" variable="outputVariable"/>
</sequence>
</process>
-Wayne Stielau
Open Text Corporation
Irvine, CA

I have discovered two issues.
1. JDeveloper does not seem to like the SOAP 1.2 envelope and encoding namespaces. Is this a known limitation? Changed them to 1.1.
2. JDeveloper does not like the double definition of wsaDemoResult.
When these two items are changed, the bpel compiles clean. Now I've got to get the message header to populate correctly. There are no values assigned, only namespace definitions. This is the SOAP packet that is received at the web service.
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<env:Header>
<MessageID xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"/>
<From xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"/>
<RelatesTo xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"/>
<Action xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"/>
<ReplyTo xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"/>
<To xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"/>
<FaultTo xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"/>
</env:Header>
<env:Body>
<wsademo xmlns="http://localhost:11001/wsademo.wsdl">
<in xmlns="">hello</in>
</wsademo>
</env:Body>
</env:Envelope>

White spaces in token area of xsd - error when importing xsd as ext. def.

Hello,
we are not sure about this issue.
This is how an area of the xsd (unfortunately an xsd of a published standard message format of german government!)
is defined that we need to import as an external definition:
<xs:complexContent>
      <xs:restriction base="tns:WLT_String">
        <xs:sequence>
          <xs:element name="content">
            <xs:simpleType>
              <xs:restriction base="xs:token">
                <xs:enumeration value="Allgemeine Fahrerlaubnis (§ 5 StVZO) " />
                <xs:enumeration value="Dienstfahrerlaubnis-Klassen (bisheriger § 5 i. V. m. § 14 StVZO)" />
                <xs:enumeration value="Dienstfahrerlaubnis-Klassen (§ 6 i. V. m. § 26 FeV)" />
                <xs:enumeration value="Dienstfahrerlaubnis-Klassen Bundeswehr (bisheriger § 5 i. V. m. § 14 StVZO)" />
              </xs:restriction>
            </xs:simpleType>
          </xs:element>
        </xs:sequence>
        <xs:attribute name="wl_fassung" type="xs:string" use="optional" default="0" />
        <xs:attribute name="wl_version" type="xs:string" use="required" fixed="1.1" />
      </xs:restriction>
    </xs:complexContent>
So we can see this defintion:
              <xs:restriction base="xs:token">
which means per definition:
xsd:token: normalizedString w/o 2 white spaces succeeding and w/o white spaces at start and end.
But you can see that the enumerations contain 2 white spaces succeeding or white space at the end.
Impporting this xsd as an external definition into PI will fail.
So it looks like PI is doing a very restricitve check of the values against the token definition.
We would expect that any xml editor would do the same check but behaviour of xml editors is different means accepting this xsd.
So is it correct that PI is more restrictive at the latest during activation of such an xsd?
This results in the situation that official standard xsds will be used by governement with other tools but only interfaces with PI will fail..
Any ideas how to run with that issue?
Regards
Dirk

Hello,
Your issue looks like the one described in this page:
http://www.xmlplease.com/normalized
For reference purposes, here is the link for the supported schema and wsdl in PI 7.1
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00a9a425-1769-2a10-9196-bd8eeed72e4c
As a temporary work around, you can try editing the xsd by removing the spaces before importing it into PI.
Hope this helps,
Mark

Usemap error - extra white space after image -solved: area shape must be inline

When using image hotspots, if the <area shape= "rect" is not IMMEDIATELY after the <map name="Map">, then FF adds a white space (white horizontal line) after the image.
White space shows between shop_top.jpg and shop_mid.jpg:
<pre><nowiki><img src="images/shop_top.jpg" width="1022" height="259" border="0" usemap="#Map">
<map name="Map"><area shape="rect" coords="251,147,435,252" href="http://www.example.html">
<img src="images/shop_mid.jpg" width="1022" height="3250"></nowiki></pre>
Images are touching vertically (no space in between):
<pre><nowiki><img src="images/shop_top.jpg" width="1022" height="259" border="0" usemap="#Map"><map name="Map"><area shape="rect" coords="251,147,435,252" href="http://www.example.html">
<img src="images/shop_mid.jpg" width="1022" height="3250"></nowiki></pre>

Maybe Mozillazine's Web Devel / Standards Evangelism forums may help better.
* http://forums.mozillazine.org/viewforum.php?f=25

Remove white space nodes from jtree

I am trying to create jtree using XML DOM.
But I m not able to remove/ignore the white space elements from DOM.
I am getting output something like this
for example
Server
Text
node1
Text
I want something like this.
Server
node1
I tried all option for removeing the white space
Here I am posting the source
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.parsers.FactoryConfigurationError;
import javax.xml.parsers.ParserConfigurationException;
import org.xml.sax.SAXException;
import org.xml.sax.SAXParseException;
import java.io.File;
import java.io.IOException;
import org.w3c.dom.Document;
import org.w3c.dom.DOMException;
// Basic GUI components
import javax.swing.JFrame;
import javax.swing.JPanel;
import javax.swing.JScrollPane;
import javax.swing.JTree;
// GUI components for right-hand side
import javax.swing.JSplitPane;
import javax.swing.JEditorPane;
// GUI support classes
import java.awt.BorderLayout;
import java.awt.Dimension;
import java.awt.Toolkit;
import java.awt.event.WindowEvent;
import java.awt.event.WindowAdapter;
// For creating borders
import javax.swing.border.EmptyBorder;
import javax.swing.border.BevelBorder;
import javax.swing.border.CompoundBorder;
// For creating a TreeModel
import javax.swing.tree.*;
import javax.swing.event.*;
import java.util.*;
public class DomEcho02 extends JPanel
// Global value so it can be ref'd by the tree-adapter
static Document document;
static final int windowHeight = 460;
static final int leftWidth = 300;
static final int rightWidth = 340;
static final int windowWidth = leftWidth + rightWidth;
public DomEcho02()
// Make a nice border
EmptyBorder eb = new EmptyBorder(5,5,5,5);
BevelBorder bb = new BevelBorder(BevelBorder.LOWERED);
CompoundBorder cb = new CompoundBorder(eb,bb);
this.setBorder(new CompoundBorder(cb,eb));
// Set up the tree
JTree tree = new JTree(new DomToTreeModelAdapter());
// Iterate over the tree and make nodes visible
// (Otherwise, the tree shows up fully collapsed)
//TreePath nodePath = ???;
// tree.expandPath(nodePath);
// Build left-side view
JScrollPane treeView = new JScrollPane(tree);
treeView.setPreferredSize(
new Dimension( leftWidth, windowHeight ));
// Build right-side view
JEditorPane htmlPane = new JEditorPane("text/html","");
htmlPane.setEditable(false);
JScrollPane htmlView = new JScrollPane(htmlPane);
htmlView.setPreferredSize(
new Dimension( rightWidth, windowHeight ));
// Build split-pane view
JSplitPane splitPane =
new JSplitPane( JSplitPane.HORIZONTAL_SPLIT,
treeView,
htmlView );
splitPane.setContinuousLayout( true );
splitPane.setDividerLocation( leftWidth );
splitPane.setPreferredSize(
new Dimension( windowWidth + 10, windowHeight+10 ));
// Add GUI components
this.setLayout(new BorderLayout());
this.add("Center", splitPane );
} // constructor
public static void main(String argv[])
if (argv.length != 1) {
System.err.println("Usage: java DomEcho filename");
System.exit(1);
DocumentBuilderFactory factory =
DocumentBuilderFactory.newInstance();
//factory.setValidating(true);
//factory.setNamespaceAware(true);
try {
DocumentBuilder builder = factory.newDocumentBuilder();
document = builder.parse( new File(argv[0]) );
makeFrame();
} catch (SAXException sxe) {
// Error generated during parsing)
Exception x = sxe;
if (sxe.getException() != null)
x = sxe.getException();
x.printStackTrace();
} catch (ParserConfigurationException pce) {
// Parser with specified options can't be built
pce.printStackTrace();
} catch (IOException ioe) {
// I/O error
ioe.printStackTrace();
} // main
public static void makeFrame() {
// Set up a GUI framework
JFrame frame = new JFrame("DOM Echo");
frame.addWindowListener(
new WindowAdapter() {
public void windowClosing(WindowEvent e) {System.exit(0);}
// Set up the tree, the views, and display it all
final DomEcho02 echoPanel =
new DomEcho02();
frame.getContentPane().add("Center", echoPanel );
frame.pack();
Dimension screenSize =
Toolkit.getDefaultToolkit().getScreenSize();
int w = windowWidth + 10;
int h = windowHeight + 10;
frame.setLocation(screenSize.width/3 - w/2,
screenSize.height/2 - h/2);
frame.setSize(w, h);
frame.setVisible(true);
} // makeFrame
// An array of names for DOM node-types
// (Array indexes = nodeType() values.)
static final String[] typeName = {
"none",
"Element",
"Attr",
"Text",
"CDATA",
"EntityRef",
"Entity",
"ProcInstr",
"Comment",
"Document",
"DocType",
"DocFragment",
"Notation",
// This class wraps a DOM node and returns the text we want to
// display in the tree. It also returns children, index values,
// and child counts.
public class AdapterNode
org.w3c.dom.Node domNode;
// Construct an Adapter node from a DOM node
public AdapterNode(org.w3c.dom.Node node) {
domNode = node;
// Return a string that identifies this node in the tree
// *** Refer to table at top of org.w3c.dom.Node ***
public String toString() {
String s = typeName[domNode.getNodeType()];
String nodeName = domNode.getNodeName();
if (! nodeName.startsWith("#")) {
s += ": " + nodeName;
if (domNode.getNodeValue() != null) {
if (s.startsWith("ProcInstr"))
s += ", ";
else
s += ": ";
// Trim the value to get rid of NL's at the front
String t = domNode.getNodeValue().trim();
int x = t.indexOf("\n");
if (x >= 0) t = t.substring(0, x);
s += t;
return s;
* Return children, index, and count values
public int index(AdapterNode child) {
//System.err.println("Looking for index of " + child);
int count = childCount();
for (int i=0; i<count; i++) {
AdapterNode n = this.child(i);
if (child.domNode == n.domNode) return i;
return -1; // Should never get here.
public AdapterNode child(int searchIndex) {
//Note: JTree index is zero-based.
org.w3c.dom.Node node =
domNode.getChildNodes().item(searchIndex);
return new AdapterNode(node);
public int childCount() {
return domNode.getChildNodes().getLength();
// This adapter converts the current Document (a DOM) into
// a JTree model.
public class DomToTreeModelAdapter
implements javax.swing.tree.TreeModel
// Basic TreeModel operations
public Object getRoot() {
//System.err.println("Returning root: " +document);
return new AdapterNode(document);
public boolean isLeaf(Object aNode) {
// Determines whether the icon shows up to the left.
// Return true for any node with no children
AdapterNode node = (AdapterNode) aNode;
if (node.childCount() > 0) return false;
return true;
public int getChildCount(Object parent) {
AdapterNode node = (AdapterNode) parent;
return node.childCount();
public Object getChild(Object parent, int index) {
AdapterNode node = (AdapterNode) parent;
return node.child(index);
public int getIndexOfChild(Object parent, Object child) {
AdapterNode node = (AdapterNode) parent;
return node.index((AdapterNode) child);
public void valueForPathChanged(TreePath path, Object newValue) {
// Null. We won't be making changes in the GUI
// If we did, we would ensure the new value was really new,
// adjust the model, and then fire a TreeNodesChanged event.
* Use these methods to add and remove event listeners.
* (Needed to satisfy TreeModel interface, but not used.)
private Vector listenerList = new Vector();
public void addTreeModelListener(TreeModelListener listener) {
if ( listener != null
&& ! listenerList.contains( listener ) ) {
listenerList.addElement( listener );
public void removeTreeModelListener(TreeModelListener listener) {
if ( listener != null ) {
listenerList.removeElement( listener );
// Note: Since XML works with 1.1, this example uses Vector.
// If coding for 1.2 or later, though, I'd use this instead:
// private List listenerList = new LinkedList();
// The operations on the List are then add(), remove() and
// iteration, via:
// Iterator it = listenerList.iterator();
// while ( it.hasNext() ) {
// TreeModelListener listener = (TreeModelListener) it.next();
* Invoke these methods to inform listeners of changes.
* (Not needed for this example.)
* Methods taken from TreeModelSupport class described at
* http://java.sun.com/products/jfc/tsc/articles/jtree/index.html
* That architecture (produced by Tom Santos and Steve Wilson)
* is more elegant. I just hacked 'em in here so they are
* immediately at hand.
public void fireTreeNodesChanged( TreeModelEvent e ) {
Enumeration listeners = listenerList.elements();
while ( listeners.hasMoreElements() ) {
TreeModelListener listener =
(TreeModelListener) listeners.nextElement();
listener.treeNodesChanged( e );
public void fireTreeNodesInserted( TreeModelEvent e ) {
Enumeration listeners = listenerList.elements();
while ( listeners.hasMoreElements() ) {
TreeModelListener listener =
(TreeModelListener) listeners.nextElement();
listener.treeNodesInserted( e );
public void fireTreeNodesRemoved( TreeModelEvent e ) {
Enumeration listeners = listenerList.elements();
while ( listeners.hasMoreElements() ) {
TreeModelListener listener =
(TreeModelListener) listeners.nextElement();
listener.treeNodesRemoved( e );
public void fireTreeStructureChanged( TreeModelEvent e ) {
Enumeration listeners = listenerList.elements();
while ( listeners.hasMoreElements() ) {
TreeModelListener listener =
(TreeModelListener) listeners.nextElement();
listener.treeStructureChanged( e );
}

DocumentBuilderFactory can be configured to ignore white space.
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/parsers/DocumentBuilderFactory.html#setIgnoringElementContentWhitespace(boolean)

Placed Illustrator PDF has extra white space

Illustrator artwork saved as PDF, and placed on an InDesign page comes in with extra white space of around 1 1/3 mm on all
sides. I can't figure out what this unwanted white space is or how to avoid it. Can someone please tell me how to avoid the extra white space.

in which case - i can only apologise for the incorrect advice.
I've never had any problems with eps files - providing that the artwork is tidy.
And I've found loads of problems printing a placed pdf through a digital rip.
I'll leave it down to trial and error... and wish the best of luck.
cheers
re

Conditional text showing as white space w/ condition indicators On

We are using condition indicators with both a color
and an overline, underline, strikethrough, etc. When
we have the condition indcators on, and do Show All,
some text shows up as white space until we change
the indicators. Unfortunately, the behavior is not
consistent in that when I change an Overline to As Is
with some colors (like the standard Red or Blue),
the text remains whtte. It's only if I alaso change
the color to one of the custom colors we are using
for headings that we can actually see the text.
A similar disappearance is happening with cross
references that use a charaacter tag Hyperlink
with standard Blue as the color (no underline) in
the cross ref format. The text tagged with Hyperlink
disappears while black text (Default para font) shows
up. If we change the cross Ref format to use a different
character tag, it shows up.
Track changges is Off. It has neer been turned on.
Bug or feature?

Sodal, I tried and I got a "Missing arguments for command '\position'."
I had used a field on bottom of page 1 before but I got a "field not found on subform CONT" error.
Does anything else come to mind. Thanks!!

Validating XML and skipping new lines & white spaces ?

Hi everybody !
I'm currently developping a new application and the configuration is done within a XML file. My problem is that I'm using IP addresses and so users have to write things like this :
<agentIP>
132.137.43.2
</agentIP>
and I have a problem with the Java SAX parser : in fact I have declared the type of agentIP in a XML Schema like this :
<xs:simpleType name="IPAddress">
<xs:restriction base="xs:string">
<xs:pattern value="((1?[0-9]?[0-9]|2[0-4][0-9]|25[0-5]).){3}(1?[0-9]?[0-9]|2[0-4][0-9]|25[0-5])"/>
</xs:restriction>
</xs:simpleType>
and the problem is that if there are some white spaces before the IP or some new lines (in fact the user can format this XML file in different manners), I have a parsing error because the parser interprets these characters too.
Has somebody any idea how to tell the parser to skip these characters ???
for information here is my source code :
ErrorHandler errorHandler = new MyErrorHandler();
    content.setLength(0);
    agentTable = new AgentTable();
    SAXParserFactory factory = SAXParserFactory.newInstance();
    factory.setNamespaceAware(true);
    factory.setValidating(true);
    SAXParser saxParser = null;
    try {
      saxParser = factory.newSAXParser();
    catch (ParserConfigurationException ex1) {
      ex1.printStackTrace();
    catch (SAXException ex1) {
      ex1.printStackTrace();
    try {
      saxParser.setProperty(JAXP_SCHEMA_LANGUAGE, W3C_XML_SCHEMA);
      try {
        saxParser.setProperty(
            "http://java.sun.com/xml/jaxp/properties/schemaSource",
            new org.xml.sax.InputSource(jamap.share.Constants.networkMap));
      catch (SAXNotRecognizedException ex4) {
      catch (SAXNotSupportedException ex4) {
    catch (SAXNotSupportedException ex3) {
      ex3.printStackTrace();
    catch (SAXNotRecognizedException ex3) {
      ex3.printStackTrace();
    org.xml.sax.XMLReader xmlReader = null;
    try {
      xmlReader = saxParser.getXMLReader();
    catch (SAXException ex) {
      ex.printStackTrace();
    xmlReader.setContentHandler(this);
    xmlReader.setErrorHandler(errorHandler);
    //    xmlReader.setProperty(
    //      "http://apache.org/xml/properties/schema/external-schemaLocation",
    //    new File("http://localhost:8080/agentfile.xml"));
    //xmlReader.setErrorHandler (new (ErrorHandler()));
    try {
      xmlReader.parse(new org.xml.sax.InputSource(jamap.share.Constants.homeDir +
                                                  jamap.share.Constants.
                                                  AgentFile));
    catch (SAXException ex2) {
      ex2.printStackTrace();
      System.out.println("Please correct your XML file !");
    catch (IOException ex2) {
      ex2.printStackTrace();
      System.out.println("Error in parsing the agent.xml file");
    return agentTable;
public void startElement(java.lang.String uri,
                           java.lang.String localName,
                           java.lang.String qName,
                           Attributes attributes
                           ) throws
      SAXException {
    if (qName.equals("proxy")) {
      isAgentViaProxy = true;
    content.setLength(0);
public void characters(char[] chars, int start, int len) throws SAXException {
    content.append(chars, start, len);
public void ignorableWhitespace(char[] ch,
                                  int start,
                                  int length) throws SAXException {
    System.out.println("Some white spaces were ignored !");
}and here the XML Schema used:
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:simpleType name="IPAddress">
<xs:restriction base="xs:string">
    <xs:pattern value="((1?[0-9]?[0-9]|2[0-4][0-9]|25[0-5]).){3}(1?[0-9]?[0-9]|2[0-4][0-9]|25[0-5])"/>
</xs:restriction>
</xs:simpleType>
<xs:element name='networkMap'>
<xs:complexType>
   <xs:sequence>
     <xs:element ref='agent' minOccurs='0' maxOccurs='unbounded'/>
   </xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="agent">
<xs:complexType>
   <xs:sequence>
     <xs:element name="ipAddress" type="IPAddress" minOccurs="1" maxOccurs="1" />
     <xs:element name="proxy" type="IPAddress" minOccurs="0" maxOccurs="1" />
   </xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>THANK YOU...
PA

Hi !
I've found the solution finally and as nobody wrote me I'll explain it...
Basically to ignore white spaces you need to specify it within your XML Schema : here is an example of a possible description for an IPv6 address inside an XML schema :
<xs:simpleType name="IPv6Address">
<xs:restriction base="xs:string">
   <xs:whiteSpace value="collapse" fixed="true"/>
   <xs:pattern value="((1?[0-9]?[0-9]|2[0-4][0-9]|25[0-5]).){7}(1?[0-9]?[0-9]|2[0-4][0-9]|25[0-5])"/>
</xs:restriction>
</xs:simpleType>as you can see <xs:whiteSpace value="collapse" fixed="true"/> is solving the problem !!
Bye..
PA
http://www.doffoel.com

How to ignore white space when parse xml document using xerces 2.4.0

When I run the program with the xml given below the following error comes.
Problem parsing the file.java.lang.NullPointerExceptionjava.lang.NullPointerExce
ption
at SchemaTest.main(SchemaTest.java:25)
============================================================
My expectation is "RECEIPT". Pls send me the solution.
import org.apache.xerces.parsers.DOMParser;
import org.xml.sax.InputSource;
import java.io.*;
import org.xml.sax.ErrorHandler;
import org.w3c.dom.*;
public class SchemaTest {
public static void main (String args[])
try
FileInputStream is = new FileInputStream(new File("C:\\ADL\\imsmanifest.xml"));
InputSource in = new InputSource(is);
DOMParser parser = new DOMParser();
//parser.setFeature("http://xml.org/sax/features/validation", false);
//parser.setProperty("http://apache.org/xml/properties/schema/external-noNamespaceSchemaLocation", "memory.xsd");
//ErrorHandler errors = new ErrorHandler();
//parser.setErrorHandler(errors);
parser.parse(in);
Document manifest = parser.getDocument();
manifest.normalize();
NodeList nl = manifest.getElementsByTagName("organization");
System.out.println((((nl.item(0)).getChildNodes()).item(0)).getFirstChild().getNodeValue());
catch (Exception e)
System.out.print("Problem parsing the file."+e.toString());
e.printStackTrace();
<?xml version = '1.0'?>
<organizations default="detail">
<organization identifier="detail" isvisible="true">
<title>RECEIPT</title>
<item identifier="S100000" identifierref="R100000" isvisible="true">
<title>Basic Module</title>
<item identifier="S100001" identifierref="R100001" isvisible="true">
<title>Objectives</title>
<metadata/>
</item>
</item>
<metadata/>
</organization>
</organizations>
Is there a white space problem? How do I get rid from this problem.

ok now i really wrote the whole code, a bit scrolling in the API is to hard?
            DocumentBuilderFactory dbf = new DocumentBuilderFactory();
            DocumentBuilder db = dbf.newDocumentBuilder();
            dbf.setNamespaceAware(true); //or set false
            Document d = db.parse(inputstream);

Remove XML Tags with White space.

Hi All, I have a scenario like the below code where I have empty spaces in few columns of my tables. I create XML of the data and send it. There is a lot of code such and I can't add ISNULL() on each and every column. Is there any simple one line code working
with the XML so that I can remove the tags with only empty spaces. TIA.
DECLARE @xml1 VARCHAR(max)
DECLARE @xml2 VARCHAR(max)
set @xml1 = (SELECT 1 AS Col11, ' ' AS Col21, 'ABC' AS Col31 FOR XML RAW, ELEMENTS)
set @xml2 = (SELECT 2 AS Col12, ' ' AS Col22, 'ABC' AS Col32 FOR XML RAW, ELEMENTS)
DECLARE @xml xml;
SET @xml = Cast('<ROOT>' + ISNULL(@xml1, '') + ISNULL(@xml2, '') + '</ROOT>' as xml)
SET @xml.modify('delete //*[not(node())]');
-- Some Way to Remove the XML Tags with Empty space here.
select @xml as XMLString
/* Output of the Above script.
<ROOT>
<row>
<Col11>1</Col11>
<Col21> </Col21> -- This XML Tag with a white space should be removed
<Col31>ABC</Col31>
</row>
<row>
<Col12>2</Col12>
<Col22> </Col22> -- This XML Tag with a white space should be removed
<Col32>ABC</Col32>
</row>
</ROOT>
Welcome to MSDN Forums.
Feel free to ask your questions and Please Note to Vote all helpful topics and
Mark all answering posts.
You Value Community's efforts and Community values your faith.
- Arun Kumar Allu

It would have helped if there had been a trim() function in XQuery.
With some trial and error and inventive thinking I came up with this:
<span style="color:Blue">SET</span> @xml.modify(<span style="color:#A31515">'delete //*[. <= " "]'</span>);
As they say: it seems to work. But I leave no warranties.
Erland Sommarskog, SQL Server MVP, [email protected]
Wow Erland this
seems to work, I need to test it against my data and update on this. Thanks again.
Welcome to MSDN Forums.
Feel free to ask your questions and Please Note to Vote all helpful topics and
Mark all answering posts.
You Value Community's efforts and Community values your faith.
- Arun Kumar Allu

Need a chrome and safari hack to eliminate white space, or?

Hi,
This page renders fine in IE8 and Firefox, but in Chrome and Safari there is white space before the Welcome bar.
http://67.199.64.241/indexspry.asp
Any thoughts?
Thanks!
Here is my CSS -- the styling for the section with the welcome bar is highlighted:
margin:0;
padding:0;
body {
font-family:Verdana, Arial, Helvetica, sans-serif;
background-color: #F3D1D8;
font-size: .75em;
line-height: 2em;
color: #323532;
position: relative;
margin: 0;
padding: 0px;
text-align:center; /* for IE5 */
behavior: url("csshover3.htc"); /* makes hover class work in IE 6,7 and 8 */
#container {
width: 1000px;
background: #fff;
margin: 0 auto;
text-align:left;
# header {
background: #fff;
a {
text-decoration: none
/* Typography -------------------------------------------*/
.textbold {
font-weight: bold;
.ital {
font-style:italic;
line-height: 1.2em;
font-family: Georgia, "Times New Roman", Times, serif;
/* Headings -------------------------------------------*/
h1 {
margin: 0; /* 2 does not bring it down -- nor does adding a border*/
font-family:Verdana, Arial, Helvetica, sans-serif;
background-color: #323532;
color: #F4F4F4;
font-size: 2em;
font-weight: bold;
line-height: 2.5em;
h2 {
font-family:Verdana, Arial, Helvetica, sans-serif;
background-color: #4E2029; /*dark purple*/
color: #f4f4f4;
font-size: 1.5em;
font-weight: bold;
h3 {
font-family:Verdana, Arial, Helvetica, sans-serif;
background-color: #D5647C; /*dusty rose*/
color: #000000;
font-size: 1em;
font-weight: bold;
h4 {
font-family:Verdana, Arial, Helvetica, sans-serif;
color: #323532;
font-size: 1em;
font-weight: bold;
/* h5 is good for drawing a burgundy line */
h5 {
background-color: #4E2029;
font-size: .5em;
line-height: .5em;
/* h6 is good for drawing a line the same color as the background */
h6 {
font-family:Verdana, Arial, Helvetica, sans-serif;
background-color: #F3D1D8; /*pink*/
color: #f4f4f4;
font-size: .5em;
font-weight: bold;
border-top-width: medium;
border-top-style: solid;
border-top-color: #FFF;
line-height: .5em;
/* Links -------------------------------------------*/
a:link {
color: #d5647c;
font-weight: bold;
a:visited {
color: #8A2488;
font-weight: bold;
a:hover {
color: #684148;
font-weight: bold;
a:active {
color: #CC0000;
font-weight: bold;
/* Top Navigation -------------------------------------------*/
#navtop {
margin:0 0 2px;
padding: 0;
background: #4E2029; /* dark purple, pms 504 */
list-style-type: none;
width: 1000px; /*used to be 684 */
float: left; /*contain floated list items */
#navtop li {
margin: 0;
padding: 0;
float: left;
margin-left: 0px;
padding-left: 0px;
background: #4E2029; /* dark purple, pms 504 */
list-style-position: outside;
#navtop a {
float: left;
width: 170px;
color: #ffffff;
text-decoration: none;
line-height: 2.5;
text-align: center;
border-right: 1px solid #fff;
font-weight: bold;
#navtop #nav_don a {
border: none; /* take out line after last menu item */
#navtop a:hover {
background: #D5647C; /* dusty rose, pms 702 */
/* Lists ----------------------------------------------
/* This accounts for brower differences in handling left margin indentation */
ul {
margin: 0;
padding: 0;
list-style-type: none;
list-style-position: outside;
li {
background: url(/images/bulletpt.gif) no-repeat 0 9px;
margin-left: 5px;
padding-left: 15px;
list-style-position: outside;
/* other elements ------------------------- */
#boxx {
background: #323532; /*dark gray */
width: 200px;
float: right; /*contain floated list items */
z-index: 10;
padding: 0px 8px 0px 12px;
border-bottom:3px solid #323532;
border-top-width: 3 px;
border-top-style: solid;
border-top-color: #323532;
line-height: 1.4em;
margin: 2px;
#boxx li {
margin: auto;
color: #424642; /*med gray */
font-weight: bold;
float: left; /* this section corrects IE whitespace bug */
background: #F2DFE3; /*lt gray */
list-style-position: outside;
list-style-type: none;
width: 185px;
#boxx a {
color: #4E2029;
display: block;
text-decoration: none;
#boxx a:hover {
background: #B85067; /* dark pink*/
color: #FFFFFF;
#search {
float: right;
width: 200px;
padding: 0px 8px 0px 12px;
border-bottom:3px solid #323532;
border-top-width: 3 px;
border-top-style: solid;
border-top-color: #323532;
margin: 2px;
.graybox {
margin: 15px 0 0 0;
padding: 5px 0 0px 0;
background:url(/images/graychecks.gif);
.rosebox {
margin: 15px 0 0 0;
padding: 5px 0 0px 0;
background:url(/images/rosechecks.gif);
/* Need something for box styles, form styles and maybe graphical buttons. */
.checklist {
font-family:Verdana, Arial, Helvetica, sans-serif;
background-color: #ffffff;
font-size: 0.75em;
line-height: 1.2em;
color: #323532;
position: relative;
margin: 0;
padding: 0px;
list-style-type: circle;
.sig {
font-family: "Comic Sans MS", cursive;
font-weight: bold;
/* from main2col.css =---- */
margin:0;
padding:0;
/* Left Navigation-------------------------------------*/
#navleft {
/* position: absolute; */
left:0;
top: 185px;
/*margin:0 0 -750px; */
/*background: #323532; /* dark gray, pms 447 */
/*width: 170px;
color: #ffffff;
font-weight: bold;
float: left; /*contain floated list items */
/*#navleft ul {
list-style-type:none;
list-style: none;
margin: 0;
padding: 0;
/*#navleft li { */
/* float: left; *//* this section corrects IE whitespace bug */
/*width: 100%; */
/*list-style-position: outside;*/
/* position: relative;
list-style-type:none;
margin: 0;
padding: 0;
/*#navleft a {
display: block;
color: #ffffff;
text-decoration: none;
padding: 0 7px;
line-height: 2.5;
padding: 15 10 15 20;
border-bottom:1px solid #fff;
background: #4E2029; *//* dark purple, pms 504 */
/*#navleft #nav_news a {
border: none; *//* take out line after last menu item */
#navleft a:hover {
background: #D5647C;*/ /* dusty rose, pms 702 */ /*
/* for submenus */
/*#navleft ul ul ul {
position: absolute;
top: 0;
left: 100%;
width: 100%;
#optionalmenupicture {
width: 14em;
#navoptional {
/*position: relative;
left:0;
top: 0;
margin:0;
padding: 0; */
background: #58DA2C; /*med lime green */
list-style-type: none;
width: 155px;
color: #ffffff; /* white */
font-weight: bold;
float: left; /*contain floated list items */
#navoptional li {
margin: 2px;
padding: 0;
float: left; /* this section corrects IE whitespace bug */
width: 100%;
background: #D5647C; /*dark rose */
list-style-position: outside;
list-style-type: square;
#navoptional a {
display: block;
text-decoration: none;
padding: 0 10px;
line-height: 2;
border-bottom:1px solid #323532;
/* #navoptional #nav_news a {
border: none; /* take out line after last menu item */
#navoptional a:hover {
background: #4e2029; /* dark purple */
/* Main Content ---------------------------------------*/
#primaryContent {
background: #fff;
float: left;
margin-left: 172px;
padding: 0;
position:relative;
top: -334px;
/* footer --------------------------------- */
#footer {
padding: 0 10px; /* this padding matches the left alignment of the elements in the divs that appear above it. */
background:#ffffff;
.hide {
font-size: 0em;
line-height: 0em;
.box {
margin: 15px 0 0 0;
padding: 5px 0 0px 0;
background:url(/images/ltchecks.gif);
.mogul {
font-family:Andale Mono, Trebuchet MS, Comic Sans MS, Impact;
font-size: xx-small;
/* Forms ---------------------- */
input {
background-color: #f5f5f5;
color: #4E2029;
font: Verdana, Arial, Helvetica, sans-serif;
font-size:12px;
textarea {
background-color: #f5f5f5;
color: #4E2029;
width: 300px;
height: 100px;
font: Verdana, Arial, Helvetica, sans-serif;
font-size:12px;
/* from Adobe */
.fltrt { /* this class can be used to float an element right in your page. The floated element must precede the element it should be next to on the page. */
float: right;
margin-left: 8px;
.fltlft { /* this class can be used to float an element left in your page */
float: left;
margin-right: 8px;
.clearfloat { /* this class should be placed on a div or break element and should be the final element before the close of a container that should fully contain a float */
clear:both;
    height:0;
    font-size: 1px;
    line-height: 0px;

You've got a bigger problem. See attached screenshot from Firefox when text size is increased in browser (Zoom, text only)
Start by using the code valiation tools below and fix reported errors. 90% of browser rendering problems are code related. If your code is clean, chances are good that your pages will perform reasonably well in all the major browsers.
HTML Validator - http://validator.w3.org
CSS Validator - http://jigsaw.w3.org/css-validator/
HTML & CSS Tutorials - http://w3schools.com/
Conditional Comments are only recognized by MS Internet Explorer. You can't use CCs to target other browsers. But this is a moot point since your problem isn't caused by bugs in either Safari or Chrome.
Nancy O.
Alt-Web Design & Publishing
Web | Graphics | Print | Media Specialists
www.alt-web.com/
www.twitter.com/altweb
www.alt-web.blogspot.com

Scan From String White Space

i all,
I'm trying to use Scan From String in order to parse some data coming in from UDP.
Input String: ASCII [00 01 02 03 ... FF]
What I want: s[00 .. 30] d[12], d[34], d[56] leftover s[37 38 39 ... FF]
ATTEMPT1
Format String: %49s%2d%2d%2d
What I get: s[00-09] RUNTIME ERROR!
ATTEMPT2
Format String: %49[^]%2d%2d%2d
What I get: Only allows first output. Will error out if I use any additional outputs from Scan From String
ATTEMPT3
Format String: %49[^(0xFF)]%2d%2d%2d Value in () is ASCII character FF.
What I get: s[00 .. 30] d[12], d[34], d[56] leftover s[37 38 39 ... FF]
It appears as though when I use %##[^] it thinks I'm looking for the ENTIRE string so it will not let me add any more Formatting. If I add a delimiter other than ^ it will run, and it will work presuming that character isn't within the first 49 characters... and I can't guarentee that it won't.
I'm aware I can parse my string using subsets and whatnot... but Scan From String is so elegant. It would be great if %S allowed for white space... or if $##[^] would simply take the first ## characters and allow me to Format after that.
Is there a simple, elegant way to do this? I wish my dataset was only 3-4 outputs. It'd be ideal if I could. Thanks.
Edit:
It might be more helpful if I provide a less abstract example:
I have an ASCII Header (Finite Length String), a Sender IP (Finite Length String), a Timestamp, a Message ID (Finite Length Decimal), A Message in ASCII ( '1' actually means 0x31, not 0x01) And for some ungodly reason... no delimiters.
So I was HOPING %##s%##s%<%H:%M:%s>t%##d (With leftover string to be my message) would work, but if any white space is contained within there... it messes up.

I cannot provide exact strings because the string is actually ASCII characters, most of which aren't displayable.
I have a string where I have:
24 ASCII Characters representing 6x U32 Header Data
13 ASCII characters represening the sender IP (string)
12 ASCII Characters representing the name of the message (String)
12 ASCII Characters representing 3x U32 Data
12 ASCII Characters represneting the name of packet (String)
12 ASCII Characters representing 12x U8 Data
256 ASCII Characters represening 256x U8 Data
etc...
It would be ideal to simply Scan from the string and output the data with the appropriate data types already assigned instead of splitting string and type casting each individualy. But if, for example, my header starts with an ASCII representation of a U32 of 2560(decimal) it would look like this: [00][00][0A][00]. ASCII 0A is considered white space. So my header would only contain 2 ASCII characters instead of the desired 24.

White space in parm files foils query for dp export

Hi,
The data pump QUERY option does very strange things with extra white space in parameter files.
If I have any space or a tab between the table name and the colon e.g.
QUERY=UTL_DATA_SYS.LOG_SYSTEM_ERROR :"WHERE 1=2"
I get the following error:
ORA-39001: invalid argument value
ORA-31658: specifying a schema name requires a table name
If I put the white space after the colon, it applies the filter to EVERY TABLE !!!! e.g.
QUERY=UTL_DATA_SYS.LOG_SYSTEM_ERROR: "WHERE 1=2"
. . exported "UTL_DATA_SYS"."SSO_AUDIT_LOG_ARCHIVE" 8.640 KB 0 rows
. . exported "UTL_DATA_SYS"."LOG_SYSTEM_ERROR" 8.921 KB 0 rows
. . exported "UTL_DATA_SYS"."APEX_META_DATA" 7.492 KB 0 rows
. . exported "UTL_DATA_SYS"."SSO_AUDIT_LOG" 8.632 KB 0 rows
. . exported "UTL_DATA_SYS"."LOG_APEX_ACTIVITY_ARCHIVE" 11.92 KB 0 rows
. . exported "UTL_DATA_SYS"."LOG_APEX_ACTIVITY_PG_DAY_SUM" 18.06 KB 0 rows
. . exported "UTL_DATA_SYS"."LOG_APEX_ACTIVITY_USR_WK_SUM" 9.054 KB 0 rows
. . exported "UTL_DATA_SYS"."APEX_IR_COLUMN" 6.515 KB 0 rows
. . exported "UTL_DATA_SYS"."APEX_ITEM_USE" 7.273 KB 0 rows
. . exported "UTL_DATA_SYS"."ALL_WBT_TABLES" 9.617 KB 0 rows
. . exported "UTL_DATA_SYS"."ALL_WBT_USERS" 5.25 KB 0 rows
. . exported "UTL_DATA_SYS"."APEX_META_DATA_KEYWORD" 5.257 KB 0 rows
. . exported "UTL_DATA_SYS"."APPLICATION_PARAMETER" 6.625 KB 0 rows
. . exported "UTL_DATA_SYS"."A_APPLICATION_PARAMETER" 7.929 KB 0 rows
. . exported "UTL_DATA_SYS"."STANDARD_ABBREVIATION" 5.242 KB 0 rows
. . exported "UTL_DATA_SYS"."SYSTEM_LOG_LEVEL_DEF" 5.914 KB 0 rows
. . exported "UTL_DATA_SYS"."APEX_APPL_DETAIL" 0 KB 0 rows
. . exported "UTL_DATA_SYS"."APEX_OBJECT_REL" 0 KB 0 rows
. . exported "UTL_DATA_SYS"."APEX_WBT_INVALID_REFER" 0 KB 0 rows
Master table "SYSTEM"."SYS_EXPORT_SCHEMA_04" successfully loaded/unloaded
If I get everything JUST RIGHT e.g.
QUERY=UTL_DATA_SYS.LOG_SYSTEM_ERROR:"WHERE 1=2"
I DO get the desired result
Processing object type SCHEMA_EXPORT/POST_SCHEMA/PROCOBJ
. . exported "UTL_DATA_SYS"."SSO_AUDIT_LOG_ARCHIVE" 402.1 MB 5121006 rows
. . exported "UTL_DATA_SYS"."LOG_SYSTEM_ERROR" 8.921 KB 0 rows
. . exported "UTL_DATA_SYS"."APEX_META_DATA" 188.5 MB 1472587 rows
. . exported "UTL_DATA_SYS"."SSO_AUDIT_LOG" 82.19 MB 895951 rows
. . exported "UTL_DATA_SYS"."LOG_APEX_ACTIVITY_ARCHIVE" 28.49 MB 177253 rows
etc
Is it unreasonable to ask Oracle to trim white space before it processes these commands? I really appreciate all the power of the data pump, but this is one area that some added work would be appreciated to reduce fragility and avoid unexpected behavior.
Thanks
Steve

Sounds reasonable to file a bug.
Dean

White space under table on page how to get rid of it

I created a new page, inserted a table to fill the page and
put in a background color. When I look at the page in Dreamweaver,
there is no white space under the table at the bottom of the page.
When I preview the page in a browser, the table ends about an inch
from the bottom of the page and I have about an inch of white space
under the table. Does anyone have an idea why this is happening?
Thanks for any help you can give. I'm going crazy trying to
get rid of it.
Diane

Fix up the errors with your html firstly - then see where you
are at with
the page....
The first thing to do would be to get rid of the table
heights - it's
invalid and won't render cross browser anyway. Error:
http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fhome.comcast.net%2F~moordian%2F
PS: Are you working on a PC or a Mac?
Nadia
Adobe® Community Expert : Dreamweaver
http://www.DreamweaverResources.com
|Tutorials|SEO |CSS Templates
http://www.csstemplates.com.au
http://www.adobe.com/devnet/dreamweaver/css.html
CSS Tutorials for Dreamweaver
"diane7" <[email protected]> wrote in
message
news:efa1h5$o12$[email protected]..
> When I am working on the page in Dreamweaver, I can't
add content any
> lower
> than the gold bar at the bottom. In fact, none of the
white under the
> gold bar
> shows up in Dreamweaver, when I'm working on the page.
It only shows up
> when I
> preview it or publish it. That's why I'm so baffled. The
gold bar should
> be
> the bottom of my index page but that white shows up in
the published
> version
> underneath it. My page properties are set to 0 margins
on all four sides
> of
> the page and the table is set to 0 padding and 0 cell
spacing, so I don't
> think
> that's it.
> Diane
>

Extra white-space after page proccess

I am trying to suppress white-spaces after the page is
processed.
Usually it doesn't bother me, but it does bother javascript.
Explanation:
1. I am sending an xmlhttp request to coldfusion to process.
2. Coldfusion runs a stored procedure on an oracle database
that returns the results as XML.
3. Coldfusion returns the XML back to the client:
<cfoutput>#XmlParse(ajaxXML)#</cfoutput>.
4. The client (Javascript) runs the function that handle the
data and returns an error because: "
xml declaration not at start of external entity".
I have tried using cfsetting with the attribute:
enablecfoutputonly="yes", but still the result is the same.
Any idea or lead in the right direction would be greatly
appreciated.

The XML that the DB returns, looks like this:
<?xml version="1.0"?>
<rowset>
<row>
<column_name>value</column_name>
<column_name>value</column_name>
</row>
</rowset>
After playing with code for a while now, I believe that the
problem is not with the returned XML.
The page that runs the SP is the page that call the SP. What
means that the white-spaces are the code that the Coldfusion engine
has already processed (although, the condition that checks whether
the form variable that Ajax request, exist. Is the first thing on
the page). to my understanding, the returned XML should be at the
top of the page.
I hope that I was clear enough.
Thank you.

White space error

Similar Messages

Maybe you are looking for