Jdk1.1.8- jdk1.3

Hi,
when I compare my software, compiled with jdk1.1.8 with it when I compile it with jdk1.3 it needs 2-3times more memory.
This is the result of an analyse with JProbe. Has anybody made the same experience?
regards,
ulli

Hi schapel,
yes, there occur problems. I tested it out. There are not only depreceated methodes and fields. The JFrame works on other ways. Former workarounds(used to clear references on the frame) are now no longer required or did't work under jdk1.3...and so on. but never mind. sun knows this problems and there is a page with incompabilities between different versions of jdk.
http://java.sun.com/j2se/1.3/compatibility.html
with the memoryuse, I've made the same experiences. let's see what the next releases will give us:-)
Thanks for your reply,
regards
Ulli

Similar Messages

Error in @Override while chaning from JDK1.6 to JDk1.5

Hi,
I am getting following error while migrating from JDK1.6 to JDK1.5.
Multiple markers at this line
     - implements org.quartz.Job.execute
     - The method execute(JobExecutionContext) of type TransferFiles must override a superclass
     method
I have a class which implements Job interface having one method execute(JobExecutionContext context) . I am overriding this method inside one of my class by using @Override annotataion.
It is working absolutely fine in JDK1.6 but while migrating to JDK1.5 it is showing the above error.
Kindly help me in this regard.
Thanks,
AK

Thank you very much for your kind help. I would like to tell you that by changing my enviroment to JDK1.5 from JDK1.6 it is asking for change the project facet. After changing the Project Facet from 6.0 to 5.0 I am getting error at @Override annotation line.
I am sharing my code here.
@Override
     public void execute(JobExecutionContext arg0) throws JobExecutionException {
          System.out.println("Quartz Scheduler: " + new Date());
          errFileList.clear();
          ArrayList<String> inputFileList = new ArrayList<String>();
          try {
               Authenticate.setUser();
               inputFileList = getInputFileList(yesterdayDate());
               int x = 0;
               Iterator<String> inputIterator = inputFileList.iterator();
               while (inputIterator.hasNext()) {
                    String inputFile = inputIterator.next();
                    StringTokenizer st = new StringTokenizer(inputFile, "&");
                    String output = null;
                    while (st.hasMoreTokens()) {
                         String view = (String) st.nextElement();
                         if (view.startsWith("view")) {
                              StringTokenizer st1 = new StringTokenizer(view, "=");
                              while (st1.hasMoreTokens()) {
                                   output = (String) st1.nextElement();
                    x++;
                    String outputFile = OUTPUT_FILES + output + XML;
                    getAuthentication(Authenticate.getUserId(), Authenticate
                              .getPassword());
                    status = copyfile(inputFile, outputFile, x);
                    runTime();
               runDate();
               LOG.info("Error Files Are : " + getErrorFileList());
               LOG.info("No of Error Files : " + errFileList.size());
               if ((null != status) && (errFileList.size() > 0)) {
                    setSendMail(true);
                    EmailHandler
                              .dispatchEmail(toMailList(), Email.ERROR_FILES,
                                        TransferFiles.getErrorFileList().toString(),
                                        Email.FROM);
               // readLogfile(
               // "C:/Program Files/Apache Software Foundation/Tomcat 5.5/webapps/XmlFileTransformation/FileTransform.log"
          } catch (Exception e) {
               System.out.println("Exception" + e);
               LOG.error("Exception" + e);
Here I have two suggestions coming by eclipse.
1.create execute method in super type ToolConstants
2.Remove @Override annotation.
but I have the same method inside an interface named as Job. So after removing the @Override annotation
I am getting the following runtime exception.
javax.servlet.ServletException: Servlet execution threw an exception
root cause
java.lang.NoClassDefFoundError: javax/activation/DataSource
     fileTransform.FileTransServlet.doPost(FileTransServlet.java:52)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:647)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
Please help me.
Thanks,
Ak

Hashtable - jdk1.2 vs jdk1.3

hash is Hashtable
for (Enumeration e = hash.keys() ; e.hasMoreElements() ;) {
System.out.println(e.nextElement());
This program prints the elements in a different order
under jdk1.2 and jdk1.3. This means the hashtable
implementation is different under these two versions.
Am I correct?
I know I am not supposed to rely on this order, but
unfortunately significantly large part of a code
uses this order. and my transition to jdk1.3 fails.
and jdk1.2 doesnt work on RH7.1 ;-(
Is there something I can do or am I totally out of luck?
thanks
Santosh

I believe I had a mental lapse when I wrote my last post. The problem has to do with the initial table capacity. In JDK 1.2 the default capacity is 101. In JDK 1.3 the default capacity is 11.
The hashcodes for the strings "a", "b", and "c" are 97, 98, and 99 respectively. In JDK 1.2 these were simple placed in the table array at the index with the same value as the hashcode. Enumeration of the keys results in iterating over all non-null elements in the table array starting with the last array element. This results in an ordering of the elements by index which produces c b a.
In JDK 1.3 the hashcodes for the strings "a", "b", and "c" are the same as in JDK 1.2 but they are placed at different indices in the table array. In this case "a" is at index 9, "b" is at index 10, and "c" is at index 0. Enumeration of the keys still results in iteration over all non-null elements in the table array starting with the last element. However due to the different element positions the output is b a c.
This trivial case can be solved by simply creating a Hashtable in JDK 1.3 with an initial capacity of 101. Try running the code below using JDK 1.2 and JDK 1.3. You will find that the Hashtable with an initial capacity of 101 produces the same results in the two different JVMs.Hashtable htab1 = new Hashtable();
htab1.put(new String("a"), new String("element1"));
htab1.put(new String("b"), new String("element2"));
htab1.put(new String("c"), new String("element3"));
System.out.println("Hashtable 1 with default capacity");
for (java.util.Enumeration e = htab1.keys(); e.hasMoreElements();) {
   String key = (String) e.nextElement();
   System.out.println("hash:" + key.hashCode() + " key:" + key);
Hashtable htab2 = new Hashtable(101);
htab2.put(new String("a"), new String("element1"));
htab2.put(new String("b"), new String("element2"));
htab2.put(new String("c"), new String("element3"));
System.out.println("Hashtable 2 with capacity of 100");
for (java.util.Enumeration e = htab2.keys(); e.hasMoreElements();) {
   String key = (String) e.nextElement();
   System.out.println("hash:" + key.hashCode() + " key:" + key);
}To start solving your problem you will need to determine if there are differences in the way elements are placed in the table array and in the way the table is rehashed.

JBuilder4Foundation upgrade fom JDK1.3 to JDK1.4

Hi!
I have a problem with using j2sdk1.4.0 in JBuilder4 Foundation. I replaced JDK1.3 by JDK1.4. Creating an new project using JDK1.4. I try to compile a new class file, but failed with compiler error "wrong version of class file 48.0"
I suppose I have to do some addtional settings, but where?
Best regards,
Jochen

Hi,
JBuilder checks the version of the class files and will not work with jdk1.4 directly.
You can patch your jdk, see the link below
http://community.borland.com/article/0,1410,27969,00.html
or you can develop in jdk1.3 and run with jdk1.4
or you can upgrade your JBuilder.
good luck.

Different behavoiur of word boundary pattern \b in JDK1.4 and JDK1.5

I noticed that word boundary pattern '\b' behaviour in jdk1.5.0 beta 1 differs from standard expected regular expression behaviour, that presents for example in jdk1.4
There is simple test code BoundaryTest.java below:
import java.util.regex.*;
public class BoundaryTest {
     public static void main(String[] args) {
          String testString = new String("word1 word2 word3");
          System.out.println("Test string: " + testString);
          Pattern p = Pattern.compile("\\b");
          Matcher m = p.matcher(testString.subSequence(0,testString.length()));
          int position = 0;
          int start = 0;
          while (m.find(position)){
               start = m.start();
               if (start == testString.length() ) break;
               if (m.find(start+1)){
                    position = m.start();
               } else {
                    position = testString.length();
               System.out.println(testString.substring(start, position));
}After compiling (in jdk1.5 or jdk1.4) one could get the next results:
>...\jdk1.4\bin\java BoundaryTest
Test string: word1 word2 word3
word1
word2
word3
And it is usual beahaviour, but in jdk1.5 we have:
>..\jdk1.5\bin\java BoundaryTest
Test string: word1 word2 word3
w
o
r
d
1
w
o
r
d
2
w
o
r
d
3
Seems that '\b' works just like '\w' in JDK1.5.
Is it a bug of new JDK or just some new feature?

To be honest, I have no idea if that the case, I am new to Java so I only had 1.4.2 for about a week before removing it and installing 1.5.0 beta... Buy the code bellow now shows the out put you desired...
import java.util.regex.*;
public class BoundaryTest {
     public static void main(String[] args) {
     String testString = new String("word1 word2 word3");
          System.out.println("Test string: " + testString);
          Pattern p = Pattern.compile("\\b");
          Matcher m = p.matcher(testString.subSequence(0,testString.length()));
          int position = 0;
          int start = 0;
          String datastring = ""; // initializes with nothing
          while (m.find(position)){
               start = m.start();
               if (start == testString.length() ) break;
               if (m.find(start+1)){
                    position = m.start();
               } else {
                    position = testString.length();
               datastring += testString.substring(start,position); // adds to string
          System.out.println(datastring); // out puts legible string
}Feel free to ignore anything I say as to this matter since as mention above, I can not test it with an earlier version since that one is now gone...
-MaxxDmg...
- ' Aye, Its Bright out... Where me put me Ale...'

Difference between jdk1.3 and jdk1.4 and jdk1.5

Hi All
1: I wud like to know the difference between jdk1.3 and jdk1.4 and jdk1.5. I could not recoginze the correct answer for this.. mostly i need the added advantages for version of JDK..
2: I wud also like to know difference in J2SE and J2EE.
Thanks in advance

while I can't tell you exclusively the differences, other than more methods have been added and some have been deprecated, from version to version, that is at least one difference.
I know several like me are reluctant at the moment to jump on up to 1.5, for fear of (and reasonably so) making their current apps go haywire!
Mine did just the other day when I tried to upgrade the JDK from 1.4.0 to 1.4.2.12!! It hosed everything.
J2SE is the Standard Environment, and J2EE is the Enterprise environment, which at the very least allows for things like the java Mail interface, using servlets and classes with the HTTP environment!
I'm sure many other posters could more accurately and specifically give you some other criterion of differences and advantages.

Differences between JDK1.5 and JDK1.6

Hi,
Can any one tell me what are the futures in JDK1.6 then JDK1.5?
Thanks in Advance.......

[The Documentation|http://java.sun.com/javase/6/webnotes/features.html] can.

Moving from jdk1.3 to jdk1.4

Hi everybody,
I need one info.
There is a bug in JDK1.3 related with HTTPClasses and Sun Says it has been fixed in JDK1.4.
So i want to move to JDK1.4 .
NOW what are the possible problems . My application uses Swing , XML ( xalan parser) .
Can someone please give me some info on this?
regds,
Rajesh

Hi ,
my concern is for parsers what we are using Xalan and Xerces .
If they would be using deprecated API then it could be a problem,
as I remember reading similar problem somewhere. So wanted to
ask the Forum.
thanx,
Rajesh

XSLT recursion changed direction from JDK1.4 to JDK1.5?

We make use of XSLT template recursion, and when we tried to test our code with JDK 1.5, the recursion "changed direction". I believe some sort of optimization is taking place that's inappropriately switching around the order or something.
Here's a test case:
test-data.xml:
<?xml version="1.0" encoding="utf-8"?>
<rating>3</rating>test-temp.xml:
<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet
    version="1.0"
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="html"/>
<xsl:template match="/">
<html>
<body>
<xsl:call-template name="showRating">
<xsl:with-param name="num" select="'1'"/>
</xsl:call-template>
</body>
</html>
</xsl:template>

<xsl:template name="showRating">
   <xsl:param name="num"/>
    <xsl:if test="$num <= rating">
    <img border="0" src="yellow_star.gif" valign="absmiddle"/>
    </xsl:if>
    <xsl:if test="$num > rating">
    <img border="0" src="white_star.gif" valign="absmiddle"/>
    </xsl:if>
<xsl:if test="$num <= '4'">
<xsl:text>
</xsl:text> 
<xsl:call-template name="showRating">
<xsl:with-param name="num" select="$num + 1" />
</xsl:call-template>
</xsl:if>
</xsl:template>
</xsl:stylesheet>testxslt.java:
import java.io.*;
import javax.xml.transform.*;
import javax.xml.transform.stream.*;
public class testxslt {
public static void main(String[] args) {
    try {
      new testxslt();
    catch(Throwable t) {
      System.err.println(t + ": " + t.getMessage());
      t.printStackTrace();
private testxslt() throws Exception {
    String stylesheet = readFile("test-temp.xml");
    String data = readFile("test-data.xml");
    String out = transform(stylesheet, data);
    System.out.println(out);
private String readFile(String filename) throws IOException {
    StringBuffer out = new StringBuffer();
    Reader r = new FileReader(filename);
    int count;
    char buf[] = new char[1024];
    while((count = r.read(buf)) > 0)
      out.append(buf, 0, count);
    r.close();
    return out.toString();
private String transform(String stylesheet, String data) throws Exception {
    ByteArrayOutputStream resultStream = new ByteArrayOutputStream();
    StreamResult transStreamResult = new StreamResult(resultStream);
    Source xmlData = new StreamSource(new StringReader(data));
    StreamSource styleSource = new StreamSource(new StringReader(stylesheet));
    TransformerFactory tf = TransformerFactory.newInstance();
    Templates t = tf.newTemplates(styleSource);
    Transformer trans = t.newTransformer();
    trans.transform(xmlData, transStreamResult);
    return resultStream.toString();
}If you run it with jdk1.4, the yellow stars will (correctly) print first. If you run it with JDK 1.5, the white stars will print first.
WTF?

More info: I downloaded xalan from xml.apache.org, and by adding xalan.jar to the classpath, I can get JDK1.5 to output the stars in the right order. So this appears to be some issue having directly to do with the XSLTC transformer.

JDialog jdk1.5 vs jdk1.6

Hi,
I'm having a different behaviour when I'm executing the following code on jdk1.5 and 1.6 :
import java.awt.BorderLayout;
import java.awt.Color;
import javax.swing.JButton;
import javax.swing.JDialog;
import javax.swing.JFrame;
import javax.swing.JLabel;
import javax.swing.JPanel;
import javax.swing.JPasswordField;
import javax.swing.JTabbedPane;
import javax.swing.JTextField;
import javax.swing.event.ChangeEvent;
import javax.swing.event.ChangeListener;
class test extends JFrame {
     private JTabbedPane tabbedPane;
     private JPanel panel1;
     private JPanel panel2;
     private JPanel panel3;
     // Main method to get things started
     public static void main(String args[]) {
          // Create an instance of the test application
          test mainFrame = new test();
          mainFrame.setVisible(true);
     public test() {
          // NOTE: to reduce the amount of code in this example, it uses
          // panels with a NULL layout. This is NOT suitable for
          // production code since it may not display correctly for
          // a look-and-feel.
          setTitle("Tabbed Pane Application");
          setSize(300, 200);
          setBackground(Color.gray);
          JPanel topPanel = new JPanel();
          topPanel.setLayout(new BorderLayout());
          getContentPane().add(topPanel);
          // Create the tab pages
          createPage1();
          createPage2();
          // Create a tabbed pane
          tabbedPane = new JTabbedPane();
          tabbedPane.addTab("Page 1", panel1);
          tabbedPane.addTab("Page 2", panel2);
          topPanel.add(tabbedPane, BorderLayout.CENTER);
          tabbedPane.addChangeListener(new ChangeListener() {
               // This method is called whenever the selected tab changes
               public void stateChanged(ChangeEvent evt) {
                    JTabbedPane pane = (JTabbedPane) evt.getSource();
                    // Get current tab
                    int sel = pane.getSelectedIndex();
                    if (sel == 1) {
                         JDialog dial = new JDialog();
                         dial.setModal(true);
                         dial.setVisible(true);
     public void createPage1() {
          panel1 = new JPanel();
          panel1.setLayout(null);
          JLabel label1 = new JLabel("Username:");
          label1.setBounds(10, 15, 150, 20);
          panel1.add(label1);
          JTextField field = new JTextField();
          field.setBounds(10, 35, 150, 20);
          panel1.add(field);
          JLabel label2 = new JLabel("Password:");
          label2.setBounds(10, 60, 150, 20);
          panel1.add(label2);
          JPasswordField fieldPass = new JPasswordField();
          fieldPass.setBounds(10, 80, 150, 20);
          panel1.add(fieldPass);
     public void createPage2() {
          panel2 = new JPanel();
          panel2.setLayout(new BorderLayout());
          panel2.add(new JButton("North"), BorderLayout.NORTH);
          panel2.add(new JButton("South"), BorderLayout.SOUTH);
          panel2.add(new JButton("East"), BorderLayout.EAST);
          panel2.add(new JButton("West"), BorderLayout.WEST);
          panel2.add(new JButton("Center"), BorderLayout.CENTER);
}On jdk1.5 when I press the 2nd tab, the popup is displayed but the tab 2 is only displayed when I close the popup.
On jdk1.6 when I press the 2nd tab, the popup is displayed and tab 2 is also displayed even when I don't close the popup.
Does anyone had this kind of problem ?
I would expect to have the same behaviour on 1.5 and 1.6..
Is there any workaround to display the 2nd tab only when popup is close on jdk 1.6 ?
Regards
Tiago

It can easily be solved by inelegant kludge.
class test extends JFrame
private JTabbedPane tabbedPane;
private JPanel panel1;
private JPanel panel2;
private JPanel panel3;
private boolean dlgShown = false; // *** class variable
    tabbedPane.addChangeListener(new ChangeListener()
      public void stateChanged(ChangeEvent evt)
        JTabbedPane pane = (JTabbedPane) evt.getSource();
        int sel = pane.getSelectedIndex();
        if (sel == 1)
          if (!dlgShown) // ***
            pane.setSelectedIndex(0); // ***
            JDialog dial = new JDialog();
            dial.setModal(true);
            dial.setPreferredSize(new Dimension(200, 100));
            dial.pack();
            dial.setLocationRelativeTo(null);
            dial.setVisible(true);
            dlgShown = !dlgShown; // ***
            pane.setSelectedIndex(1); // ***
          else
            dlgShown = !dlgShown;
}note: more elegant solutions most welcome!

Help me :chinese character display between JDK1.3 and JDK1.4

My Application was builded in jdk1.3 under jb6,but when I switch my project's properties/paths/JDK to jdk1.4( the newest one),then rebuilder it,It can't display "chinese String" normally, why?
Thanks!

You should check that the right font.properties file is being used in the path:
<jdk1.3.1_path>/jre/bin/lib/font.properties...
If you need to display Traditional Chinese you should replace font.properties with font.properties.zh_TW.
Make sure to keep an original copy of font.properties.
Also, check that jbuilder is looking at the right jdk.
JBuilder > Tools > Configure JDK > set up the new JDK
JBuilder > Project > Project Properties > select the new JDK
good luck!
katherine

JDk1.5 Vs JDK1.4

Whether below given statement would compile in JDK 1.5.
Right now it is fine in Jdk 1.4 pls tell us such we can shift from JDK1.4 to JDK 1.5
Enumeration enum = aRequest.getParameterNames();

Whether below given statement would compile in JDK
1.5.
Right now it is fine in Jdk 1.4 pls tell us such we
can shift from JDK1.4 to JDK 1.5
Enumeration enum = aRequest.getParameterNames();Rename enum.
Kaj

EJB compatible on JDK1.3 and JDK1.4

One EJB running on WLS8.1(JDK1.4), is it OK to be invoked from WLS6.1(JDK1.3) ?

The deployment descriptors are required to be modified for WebLogic 6.1
http://e-docs.bea.com/wls/docs81/upgrade/upgrade6xto81.html#1068412
Kevin <[email protected]> wrote:
One EJB running on WLS8.1(JDK1.4), is it OK to be invoked from WLS6.1(JDK1.3)

JDK1.4 Vs JDK1.3

Hello Gurus,
Is there any doc saying what are all the differences between JDK1.4 &
JDK1.3 ?
Thanks In Advance,
Olabora.

If you are talking about new feature of JDK 1.4, check out:
http://java.sun.com/j2se/1.4/docs/relnotes/features.html
These are different from JDK 1.3.x

Jdk1.3 vs jdk1.4 and SASL authentication

I'm trying to get SASL authentication work with jdk1.3 and iPlanet Directory Server. Everytime I get same exception:
SASL authentication failed. Root exception is java.lang.NoSuchMethodError
When I try with jdk1.4 everything works fine. Now I'm just wondering that is there other things that I should take care when I try get authentication work with jdk1.3. I know that all the extension packages are integrated to the jdk1.4 and I have set same packages to the CLASSPATH when I'm trying to do same with jdk1.3, but same exception occurs than above.
Does anyone know what's the problem?
Thanks,
Janne

Hi ,
Jsse 1.0.3 (strictly this version only) is needed along with jdk1.3 for the SASL or SSL authentication to be done fine.
Hope this helps,
Regards,
Sathya

Jdk1.1.8- jdk1.3

Similar Messages

Maybe you are looking for