There I have given 9 simple steps to build an axis2 webservice and a client to use that web service.

http://ongkoor.blogspot.com/2010/09/axis2-webservice-with-eclipse-europa-in.html

copied and pasted from the link

I’ve had this problem in FF3 but this time not related to iframe or overflow
setting but because of disabling input for a moment.

If someone stumbles upon same issue, this may help:

Testcase to reproduce problem:
textarea.disabled = true;
setTimeout(function() {
textarea.disabled = false;
textarea.focus();
}, 0);

How to fix it:

textarea.blur(); // blur first
textarea.disabled = true;
setTimeout(function() {
textarea.disabled = false;
textarea.focus();
}, 0);

<input type=”text” size=”20″ class=”email”/>

<input type=”text” size=”20″ class=”username”/>

with jQuery we can do it simply


jQuery('.email').keyup(function (e) {
var index = text.indexOf('@');
if (index == -1) {
jQuery('.username').val(text);
}else if (index) {
jQuery('.username').val(text.substring(0, index));
}
});


http://www.mail-archive.com/xalan-j-users@xml.apache.org/msg04890.html

copy and paste from the above link

[

Hello, Erik.   

I was struggling with this problem back in November 2005, but after some
poking around I found a one-line change that has eliminated all "No more
DTM IDs" errors on my project.

I unpacked xalan_2_7_0.jar and in
src/org/apache/xml/dtm/DTMManager.java, line 362, I found, read, and (I
hope) understood this comment:

  /** This value, set at compile time, controls how many bits of the
   * DTM node identifier numbers are used to identify a node within a
   * document, and thus sets the maximum number of nodes per
   * document. The remaining bits are used to identify the DTM
   * document which contains this node.
   *
   * If you change IDENT_DTM_NODE_BITS, be sure to rebuild _ALL_ the
   * files which use it... including the IDKey testcases.
   *
   * (FuncGenerateKey currently uses the node identifier directly and
   * thus is affected when this changes. The IDKEY results will still be
   * _correct_ (presuming no other breakage), but simple equality
   * comparison against the previous "golden" files will probably
   * complain.)
   * */

I then changed the following constant's value from 16 to 12.

  public static final int IDENT_DTM_NODE_BITS = 12;

Then I added a little static initializer purely to convince myself that
my webserver actually found my copy of xalan.jar

  static {
     System.out.println(" IDENT_DTM_NODE_BITS: "+ IDENT_DTM_NODE_BITS );
  }

My understanding of this change is that I gave up four (16-12) bits
worth of IDs for identifying documents, in exchange for four more bits
of node IDs within each document.  I cannot imagine in my app needing
more than 2^12 (4096) document IDs, but I certainly need more than 2^16
(65536) worth of nodes within a document.  Now I can have up to 2^20
(1,048,576) nodes per document.

Now, maybe some more knowledgable xalan developers can answer this:  In
the above comment, it says: " If you change IDENT_DTM_NODE_BITS, be sure
to rebuild _ALL_ the files which use it... including the IDKey
testcases.".  Now, I did rebuild the entire package, which I am sure
satisfies that requirement, but why does it have to be a compile-time
setting?   Since other classes would have to refer to
DTMManager.IDENT_DTM_NODE_BITS (AFAIK, referring to a final variable
like this doesn't actually COPY the value into the other classes, or
does it?)   Would it not also work to provide 16 as a default, but allow
it to be overridden, like this?

    public static final int IDENT_DTM_NODE_BITS = 

Integer.parseInt(System.getProperty("org.apache.xml.dtm.DTMManager.IDENT
_DTM_NODE_BITS"), "16");

Then people who need another value can simply start their app with
  -Dorg.apache.xml.Dorg.apache.xml.dtm.DTMManager.IDENT_DTM_NODE_BITS=12
on the command line and be done with it.

If there is a downside to what I have done, PLEASE discuss!  So far, I
do not see one!

tlj

Timothy Jones - Sr. Systems Engineer, Development
(813) 637-5366 - Syniverse Technologies
Learn a new language, grow a new soul, live a new life.

]

“accidental mix and match JSTL versions”

See the link [☼ http://3.ly/lmk]

So what you will have to do is

Just change

<%@ taglib uri=”http://java.sun.com/jstl/core” prefix=”c”%>           to

<%@ taglib uri=”http://java.sun.com/jsp/jstl/core” prefix=”c”%>

http://www.vaannila.com/hibernate/hibernate-tutorial/hibernate-tutorial.html

This is a very nice tutorial for anyone who wants to test hibernate in eclipse.

Just follow all the examples. Last page of every section includes a very simple source code.

http://www.slideshare.net/asfak/cellular-automata-1971307

For .ppt file

Cellular Automata Presentation file .ppt

http://www.slideshare.net/asfak/erlang-1971533

For .ppt file please visit

Erlang presentation .ppt file

I should give a cordial thanks to Mahbub Shahriar (Project Manager, KAZ Software Ltd. Bangladesh) for finding out the solution for this problem.

Problem:

Sometimes it is required to keep the special characters same in the output XML file as in the input XML file.

Solution:

For example:

input.xml


<?xml version="1.0" encoding="UTF-8"?>
<abc>
<def>'single quotation' "double quotation" Apostrophe' Apostrophe&apos; &quot;Quotation&quot; A&amp;B</def>
</abc>

We want output should be as it is in the output. That is special characters should not be changed and also the characters single quotation (‘), double quotation (“) should also not be changed.

If we read the input xml file (input.xml) file by the following way


SAXReader reader = new SAXReader();//DEFAULT SAXReader is used.
reader.setValidation(false);
reader.setFeature(feature, false);
Document inputDoc = reader.read("input/input.xml");


Reader will read &quote; as ” and ‘ as ‘ and when it will be written to the output file special characters will not be seen.

A little trick is used in the following Java program so that this problem is resolved. There you will see MySAXParser() is used as argument which extends SAXParser().

//LOOK !! Here default is not taken.
SAXReader reader = new SAXReader(new MySAXParser());
reader.setValidation(false);
reader.setFeature(feature, false);
Document inputDoc = reader.read("input/input.xml");



//MySAXParser.java
public class MySAXParser extends SAXParser {

private String entityNane;

@Override
public void characters(XMLString text, Augmentations augs) throws XNIException {
if (this.entityNane != null) {
char[] charArray = this.entityNane.toCharArray();

text.setValues(charArray, 0, charArray.length);

this.entityNane = null;
}
super.characters(text, augs);
}

@Override
public void startGeneralEntity(String name, XMLResourceIdentifier identifier, String encoding, Augmentations augs) throws XNIException {
super.startGeneralEntity(name, identifier, encoding, augs);

this.entityNane = “&” + name + “;”;
}
}

So now what’s the trick here in MySAXParser.java?

Normally all texts in the XML file is run through the method

public void characters(

but if special characters are encountered then the method

public void startGeneralEntity(

is called first and then public void characters( is called.

Here the trick is done. The trick is very easy.

Jar-files:

dom4j-1.5.1.jar
jaxen-1.1-beta-8.jar
xercesImpl.jar

Source Codes:

//ADom4jDemoMain.java

import java.io.File;
import java.io.FileOutputStream;
import java.io.OutputStreamWriter;

import org.dom4j.Document;
import org.dom4j.io.OutputFormat;
import org.dom4j.io.SAXReader;
import org.dom4j.io.XMLWriter;
import org.dom4j.tree.FlyweightProcessingInstruction;

public class ADom4jDemoMain {

public static String feature = “http://apache.org/xml/features/nonvalidating/load-external-dtd”;

public static void main(String[] args) {

//This will change in the output
try {
SAXReader reader = new SAXReader();//LOOK HERE DEFAULT SAXReader is read.
reader.setValidation(false);
reader.setFeature(feature, false);
Document inputDoc = reader.read(“input/input.xml”);
writeDocument(inputDoc, new File(“output/changed_output.xml”));
}catch(Exception e) {
e.printStackTrace();
}

//This WILL NOT change in the output.
try {
SAXReader reader = new SAXReader(new MySAXParser());//LOOK !! Here default is not taken.
reader.setValidation(false);
reader.setFeature(feature, false);
Document inputDoc = reader.read(“input/input.xml”);
writeDocument(inputDoc, new File(“output/same_output.xml”));
}catch(Exception e) {
e.printStackTrace();
}

}

public synchronized static void writeDocument(Document doc, File df) {
System.out.println((df.exists() ? “Overwriting” : “Creating”) + ” file – ” + df);
df.getParentFile().mkdirs();
try {
OutputFormat format = OutputFormat.createPrettyPrint();
format.setIndentSize(4);
XMLWriter writer = new XMLWriter(new OutputStreamWriter(new FileOutputStream(df), “UTF-8″),format);
FlyweightProcessingInstruction xmlDeclaration = new FlyweightProcessingInstruction(“xml”,
“version=\”1.0\” encoding=\”UTF-8\”");
writer.setEscapeText(false);//Look escaping is turned off from writer.
writer.write(xmlDeclaration);
writer.write(doc.processingInstructions());
writer.write(doc.getDocType());
writer.write(doc.getRootElement());
writer.close();

} catch (Exception e) {
e.printStackTrace();
}
}
}


//MySAXParser.java

import org.apache.xerces.parsers.SAXParser;
import org.apache.xerces.xni.Augmentations;
import org.apache.xerces.xni.XMLResourceIdentifier;
import org.apache.xerces.xni.XMLString;
import org.apache.xerces.xni.XNIException;

public class MySAXParser extends SAXParser {

private String entityNane;

@Override
public void characters(XMLString text, Augmentations augs) throws XNIException {
if (this.entityNane != null) {
char[] charArray = this.entityNane.toCharArray();
text.setValues(charArray, 0, charArray.length);

this.entityNane = null;
}
super.characters(text, augs);
}

@Override
public void startGeneralEntity(String name, XMLResourceIdentifier identifier, String encoding, Augmentations augs) throws XNIException {
super.startGeneralEntity(name, identifier, encoding, augs);

this.entityNane = “&” + name + “;”;
}
}