|
Hi All
I was having some problem in using Helma's library. The javac couldn't compile my program.
Can anyone help me out or provide a sample programs used to call a remote procedure in an existing server.
Following error messages are displayed--
=========================================================================
.\java\nio\DirectByteBuffer.java:59: cannot resolve symbol
symbol : method assert (boolean)
location: class java.nio.DirectByteBuffer.Deallocator
assert (address != 0);
^
.\java\nio\DirectByteBuffer.java:165: cannot resolve symbol
symbol : method assert (boolean)
location: class java.nio.DirectByteBuffer
assert (pos <= lim);
^
.\java\nio\DirectByteBufferR.java:165: warning: as of release 1.4, assert is a k
eyword, and may not be used as an identifier
assert (pos <= lim);
^
.\java\nio\DirectByteBufferR.java:479: warning: as of release 1.4, assert is a k
eyword, and may not be used as an identifier
assert (off <= lim);
^
.\java\nio\DirectByteBufferR.java:570: warning: as of release 1.4, assert is a k
eyword, and may not be used as an identifier
assert (off <= lim);
^
.\java\nio\DirectByteBufferR.java:661: warning: as of release 1.4, assert is a k
eyword, and may not be used as an identifier
assert (off <= lim);
^
.\java\nio\DirectByteBufferR.java:752: warning: as of release 1.4, assert is a k
eyword, and may not be used as an identifier
assert (off <= lim);
^
.\java\nio\DirectByteBufferR.java:843: warning: as of release 1.4, assert is a k
eyword, and may not be used as an identifier
assert (off <= lim);
^
.\java\nio\DirectByteBufferR.java:934: warning: as of release 1.4, assert is a k
eyword, and may not be used as an identifier
assert (off <= lim);
^
.\java\nio\DirectByteBuffer.java:217: cannot resolve symbol
symbol : method assert (boolean)
location: class java.nio.DirectByteBuffer
assert (pos <= lim);
^
.\java\nio\DirectByteBuffer.java:269: cannot resolve symbol
symbol : method assert (boolean)
location: class java.nio.DirectByteBuffer
assert (spos <= slim);
^
.\java\nio\DirectByteBuffer.java:274: cannot resolve symbol
symbol : method assert (boolean)
location: class java.nio.DirectByteBuffer
assert (pos <= lim);
^
.\java\nio\DirectByteBuffer.java:286: cannot resolve symbol
symbol : method assert (boolean)
location: class java.nio.DirectByteBuffer
assert (spos <= slim);
^
.\java\nio\DirectByteBuffer.java:307: cannot resolve symbol
symbol : method assert (boolean)
location: class java.nio.DirectByteBuffer
assert (pos <= lim);
^
.\java\nio\DirectByteBuffer.java:332: cannot resolve symbol
symbol : method assert (boolean)
location: class java.nio.DirectByteBuffer
assert (pos <= lim);
^
.\java\nio\DirectByteBuffer.java:479: cannot resolve symbol
symbol : method assert (boolean)
location: class java.nio.DirectByteBuffer
assert (off <= lim);
^
.\java\nio\ByteBufferAsCharBufferB.java:34: warning: as of release 1.4, assert i
s a keyword, and may not be used as an identifier
assert (pos <= cap);
^
.\java\nio\ByteBufferAsCharBufferB.java:57: warning: as of release 1.4, assert i
s a keyword, and may not be used as an identifier
assert (pos <= lim);
^
.\java\nio\ByteBufferAsCharBufferB.java:123: warning: as of release 1.4, assert
is a keyword, and may not be used as an identifier
assert (pos <= lim);
^
.\java\nio\ByteBufferAsCharBufferB.java:173: warning: as of release 1.4, assert
is a keyword, and may not be used as an identifier
assert (pos <= len);
^
.\java\nio\ByteBufferAsCharBufferL.java:34: warning: as of release 1.4, assert i
s a keyword, and may not be used as an identifier
assert (pos <= cap);
^
.\java\nio\ByteBufferAsCharBufferL.java:57: warning: as of release 1.4, assert i
s a keyword, and may not be used as an identifier
assert (pos <= lim);
^
.\java\nio\ByteBufferAsCharBufferL.java:123: warning: as of release 1.4, assert
is a keyword, and may not be used as an identifier
assert (pos <= lim);
^
.\java\nio\ByteBufferAsCharBufferL.java:173: warning: as of release 1.4, assert
is a keyword, and may not be used as an identifier
assert (pos <= len);
^
.\java\nio\DirectCharBufferU.java:165: warning: as of release 1.4, assert is a k
eyword, and may not be used as an identifier
assert (pos <= lim);
^
.\java\nio\DirectCharBufferU.java:217: warning: as of release 1.4, assert is a k
eyword, and may not be used as an identifier
assert (pos <= lim);
^
.\java\nio\DirectCharBufferU.java:269: warning: as of release 1.4, assert is a k
eyword, and may not be used as an identifier
assert (spos <= slim);
^
.\java\nio\DirectCharBufferU.java:274: warning: as of release 1.4, assert is a k
eyword, and may not be used as an identifier
assert (pos <= lim);
^
.\java\nio\DirectCharBufferU.java:286: warning: as of release 1.4, assert is a k
eyword, and may not be used as an identifier
assert (spos <= slim);
^
.\java\nio\DirectCharBufferU.java:307: warning: as of release 1.4, assert is a k
eyword, and may not be used as an identifier
assert (pos <= lim);
^
.\java\nio\DirectCharBufferU.java:332: warning: as of release 1.4, assert is a k
eyword, and may not be used as an identifier
assert (pos <= lim);
^
.\java\nio\DirectCharBufferU.java:378: warning: as of release 1.4, assert is a k
eyword, and may not be used as an identifier
assert (pos <= len);
^
.\java\nio\DirectCharBufferS.java:165: warning: as of release 1.4, assert is a k
eyword, and may not be used as an identifier
assert (pos <= lim);
^
.\java\nio\DirectCharBufferS.java:217: warning: as of release 1.4, assert is a k
eyword, and may not be used as an identifier
assert (pos <= lim);
^
.\java\nio\DirectCharBufferS.java:269: warning: as of release 1.4, assert is a k
eyword, and may not be used as an identifier
assert (spos <= slim);
^
.\java\nio\DirectCharBufferS.java:274: warning: as of release 1.4, assert is a k
eyword, and may not be used as an identifier
assert (pos <= lim);
^
.\java\nio\DirectCharBufferS.java:286: warning: as of release 1.4, assert is a k
eyword, and may not be used as an identifier
assert (spos <= slim);
^
.\java\nio\DirectCharBufferS.java:307: warning: as of release 1.4, assert is a k
eyword, and may not be used as an identifier
assert (pos <= lim);
^
.\java\nio\DirectCharBufferS.java:332: warning: as of release 1.4, assert is a k
eyword, and may not be used as an identifier
assert (pos <= lim);
^
.\java\nio\DirectCharBufferS.java:378: warning: as of release 1.4, assert is a k
eyword, and may not be used as an identifier
assert (pos <= len);
^
.\java\nio\DirectByteBuffer.java:570: cannot resolve symbol
symbol : method assert (boolean)
location: class java.nio.DirectByteBuffer
assert (off <= lim);
^
.\java\nio\ByteBufferAsShortBufferB.java:34: warning: as of release 1.4, assert
is a keyword, and may not be used as an identifier
assert (pos <= cap);
^
.\java\nio\ByteBufferAsShortBufferB.java:57: warning: as of release 1.4, assert
is a keyword, and may not be used as an identifier
assert (pos <= lim);
^
.\java\nio\ByteBufferAsShortBufferB.java:123: warning: as of release 1.4, assert
is a keyword, and may not be used as an identifier
assert (pos <= lim);
^
.\java\nio\ByteBufferAsShortBufferL.java:34: warning: as of release 1.4, assert
is a keyword, and may not be used as an identifier
assert (pos <= cap);
^
.\java\nio\ByteBufferAsShortBufferL.java:57: warning: as of release 1.4, assert
is a keyword, and may not be used as an identifier
assert (pos <= lim);
^
.\java\nio\ByteBufferAsShortBufferL.java:123: warning: as of release 1.4, assert
is a keyword, and may not be used as an identifier
assert (pos <= lim);
^
.\java\nio\DirectShortBufferU.java:165: warning: as of release 1.4, assert is a
keyword, and may not be used as an identifier
assert (pos <= lim);
^
.\java\nio\DirectShortBufferU.java:217: warning: as of release 1.4, assert is a
keyword, and may not be used as an identifier
assert (pos <= lim);
^
.\java\nio\DirectShortBufferU.java:269: warning: as of release 1.4, assert is a
keyword, and may not be used as an identifier
assert (spos <= slim);
^
.\java\nio\DirectShortBufferU.java:274: warning: as of release 1.4, assert is a
keyword, and may not be used as an identifier
assert (pos <= lim);
^
.\java\nio\DirectShortBufferU.java:286: warning: as of release 1.4, assert is a
keyword, and may not be used as an identifier
assert (spos <= slim);
^
.\java\nio\DirectShortBufferU.java:307: warning: as of release 1.4, assert is a
keyword, and may not be used as an identifier
assert (pos <= lim);
^
.\java\nio\DirectShortBufferU.java:332: warning: as of release 1.4, assert is a
keyword, and may not be used as an identifier
assert (pos <= lim);
^
.\java\nio\DirectShortBufferS.java:165: warning: as of release 1.4, assert is a
keyword, and may not be used as an identifier
assert (pos <= lim);
^
.\java\nio\DirectShortBufferS.java:217: warning: as of release 1.4, assert is a
keyword, and may not be used as an identifier
assert (pos <= lim);
^
.\java\nio\DirectShortBufferS.java:269: warning: as of release 1.4, assert is a
keyword, and may not be used as an identifier
assert (spos <= slim);
^
.\java\nio\DirectShortBufferS.java:274: warning: as of release 1.4, assert is a
keyword, and may not be used as an identifier
assert (pos <= lim);
^
.\java\nio\DirectShortBufferS.java:286: warning: as of release 1.4, assert is a
keyword, and may not be used as an identifier
assert (spos <= slim);
^
.\java\nio\DirectShortBufferS.java:307: warning: as of release 1.4, assert is a
keyword, and may not be used as an identifier
assert (pos <= lim);
^
.\java\nio\DirectShortBufferS.java:332: warning: as of release 1.4, assert is a
keyword, and may not be used as an identifier
assert (pos <= lim);
^
.\java\nio\DirectByteBuffer.java:661: cannot resolve symbol
symbol : method assert (boolean)
location: class java.nio.DirectByteBuffer
assert (off <= lim);
^
.\java\nio\ByteBufferAsIntBufferB.java:34: warning: as of release 1.4, assert is
a keyword, and may not be used as an identifier
assert (pos <= cap);
^
.\java\nio\DirectByteBuffer.java:752: cannot resolve symbol
symbol : method assert (boolean)
location: class java.nio.DirectByteBuffer
assert (off <= lim);
^
.\java\nio\DirectByteBuffer.java:843: cannot resolve symbol
symbol : method assert (boolean)
location: class java.nio.DirectByteBuffer
assert (off <= lim);
^
.\java\nio\DirectByteBuffer.java:934: cannot resolve symbol
symbol : method assert (boolean)
location: class java.nio.DirectByteBuffer
assert (off <= lim);
^
.\java\nio\Bits.java:642: cannot resolve symbol
symbol : method assert (boolean)
location: class java.nio.Bits
assert (reservedMemory > -1);
^
.\java\nio\channels\spi\AbstractSelectableChannel.java:118: cannot resolve symbo
l
symbol : method assert (boolean)
location: class java.nio.channels.spi.AbstractSelectableChannel
assert (i <= keyCount);
^
.\java\lang\CharacterDataLatin1.java:284: cannot resolve symbol
symbol : method assert (boolean)
location: class java.lang.CharacterDataLatin1
assert (data.length == (256 * 2));
^
Note: Some input files use or override a deprecated API.
Note: Recompile with -deprecation for details.
100 errors
207 warnings
=========================================================================
Ankush
|
|
|
|
|
Anyone know where i can find some good examples on how to create an app that would grab data from a server side xml file? thanks.
|
|
|
|
|
Please elaborate. Explain the scenario.
|
|
|
|
|
I have dataset which is binded to datagrid and dateformating is done based on culture. This happens fine with out any problem.
If my dataset is retrieved as a xml string using dataset.GetXML then converted to dataset and binded to datagrid. The date formatting wont take place instead it displays in the following format
2005-02-09T14:13:24.8280000-00:00.
But I want the dateformatting to take place on datagrid in either of the case.
Padvit
|
|
|
|
|
i also have the same problem
|
|
|
|
|
I have dataset which is binded to datagrid and dateformating is done based on culture. This happens fine with out any problem.
If my dataset is retrieved as a xml string using dataset.GetXML then converted to dataset and binded to datagrid. The date formatting wont take place instead it displays in the following format
2005-02-09T14:13:24.8280000-00:00.
But I want the dateformatting to take place on datagrid in either of the case.
|
|
|
|
|
I believe you have to load the schema. So you would getXML then instantiate a new dataset, load the schema (which will tell it that field is of type date) and then load the xml to the dataset.
|
|
|
|
|
I like an free, easy to use XSLT editor. I've googled a lot and only got advanced comersial versions. Any tip?
_____________________________
...and justice for all
APe
|
|
|
|
|
The next version of visual studio has an XSLT editor/debugger. I'd use XMLSpy Home Edition for a few months if you can't get the beta, then go with that.
Christian Graus - Microsoft MVP - C++
|
|
|
|
|
I Want to create XML element without name spaces definition.
Help me
Thanks
|
|
|
|
|
Do you mean prefixes namespaces on elements? If so use "exclude-result-prefixes"
Eg:
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns="http://www.w3.org/1999/xhtml" version="1.0" xmlns:msxsl="urn:schemas-microsoft-com:xslt"
<u>exclude-result-prefixes="msxsl"</u>>
If, not, please be more specific!!
|
|
|
|
|
I am trying to insert new nodes within an existing XML document. The insert that I am having problems with is a few nodes deep.
I can insert a new node just below the root node with the following with no problems:
<br />
XmlDocument doc = new XmlDocument();<br />
doc.Load(strXMLPath);<br />
<br />
XmlNode tasks = doc.SelectSingleNode("/tasks");<br />
doc.AppendChild(tasks);<br />
<br />
Now, here is the code which tries to write a little deeper down and is breaking:
<br />
XmlDocument doc = new XmlDocument();<br />
doc.Load(strXMLPath);<br />
<br />
XmlNode checks = doc.SelectSingleNode("/tasks/task[@id='1001']/checks");<br />
doc.AppendChild(checks);<br />
<br />
The error the second code snippet gives is: This document already has a DocumentElement node. It gives this error on the doc.AppendChild(checks); line
I just can't figure it out. I did a quick watch on XmlNode checks = doc.SelectSingleNode("/tasks/task[@id='1001']/checks"); and it did put me in the correct node.
I have no idea why I can not append into this node. Anyone have any ideas?
Here is my XML doc if you want to see it for reference:
<br />
<?xml version="1.0" encoding="utf-8"?><br />
<tasks><br />
<task id="1000"><br />
<name>Task Name</name><br />
<checks><br />
<check id="1000_1"><br />
<time>14:00</time><br />
</check><br />
<check id="1000_2"><br />
<time>23:00</time><br />
</check><br />
</checks><br />
</task><br />
</tasks>
|
|
|
|
|
Why would you want to append the same node that you queried?
I would suggest the following:
XmlNode checks = doc.SelectSingleNode("/tasks/task[@id='1001']/checks");
XmlNode newCheck,newNode;
newCheck = doc.CreateElement("check");
XmlAttribute attr = doc.CreateAttribute("id");
attr.Value = "1000_3";
newCheck.Attributes.Append(attr);
//add child node of new check
newNode = doc.CreateElement("time");
newNode.Value = "15:00";
newCheck.AppendChild(newNode);
checks.AppendChild(newCheck);
|
|
|
|
|
Hello,
I am trying to modify an XML file by adding a new element in the middle.
I've managed to add something using:
Set objNewNode = MyXMLDOM.createElement("Element")
Set objNewText = MyXMLDOM.createTextNode("<item>1</item1>")
objNewNode.appendChild(objNewText)
Set objCurrNode = MyXMLDOM.documentElement
objCurrNode.appendChild(objNewNode)
MyXMLDOM.save filenamePath
This adds it to the document root at the end, how do I add it in the middle using a path? I'm sure I need to set objCurrNode differently but I can't find out how.
Many thanks
|
|
|
|
|
hello here is my problem
i using an xml file to store some strings
i wanted to use certain characters in the strings to denote colors
however the characters i used where invalid characters
for example
<name>&+RSteve&n
i assume the invalid char is either the & or the +
is there anyway i can still use these chars in my strings?
|
|
|
|
|
hi, in general you should use article's very own forum at the bottom of the page. OK, here it looks like author doesn't response for a while so be it. As I understand from article there is .aspx page... so it's like with every ASP.NET application. Fist you have to set virtual directory in IIS and then (assuming you have installed .NET framework and ASP.NET) you simply type URL to virtual directory into browser (e.g. http://localhost/quiz or something) and it should work. If it doesnt, try include .aspx file into url - somethimes there is not set default page or your page is not named as default page should be (usualy default.aspx or index.aspx).
hope it helps
David
Never forget: "Stay kul and happy" (I.A.)
David's thoughts / dnhsoftware.org / MyHTMLTidy
|
|
|
|
|
I am writing a compact framework application that stores data in an XML file. Consiquently I have to read and write and edit the data that is stored in this file. Reading and searching the data is easy enough however I am looking for the most efficient way to edit the data once stored.
The solution that I have seen suggested most often is to use XmlDocument to open the file and edit it. However I have seen it written that the fact that XmlDocument requires the entire document to be read into memory is in efficient and a bad idea with memory restricted devices such as a PDA.
This leads me to have the following questions:
Is the performance issues of XmlDocument a large concern if I am going to be opening the file, finding what I am looking for editing and closing all at once?
Secondly, if the answer to that question is true, what is the best way to edit a file? My next thought would be to use a conjunction of XmlTextReader and XmlTextWriter to search the file and push into a buffer as I go, but that seems tedious.
Many thanks for your time and advice,
Andy
|
|
|
|
|
Hi
1) Is it possible to take the "PrintScreen" of the windows currently running on the system, at some regular invervals, and save them into image files(*.bmp/*.gif/*.jpeg)?
2) From keyboard, when i press any key i can get the KeyCode, but when i press "Print Screen" button, i am unable to get the KeyCode in the Form_KeyDown(). What is the reason?
Vamshidhar K
Vamshidhar K
|
|
|
|
|
I don't think your question belongs to this forum. You should try the MC++ or C# forums since this should be mainly XML/XSLT related questions.
~Javier Lozano
(blog)
|
|
|
|