using System;

using System.Text;

using System.Collections;

using System.Collections.Generic;

using System.Runtime.Serialization;


namespace MyNamespace.DataTypes {

  [Serializable]

  public class MyDictionary: Dictionary {

    public MyDictionary()

      : base() {

    }

    public MyDictionary(SerializationInfo info, StreamingContext context)

      : base(info, context) {

    }

  }

}

The error I was getting was, "System.Runtime.Serialization.SerializationException: The constructor to deserialize an object of type 'MyNamespace.DataTypes.MyDictionary' was not found."

I got the idea here: http://www.vbforums.com/showthread.php?t=314430, which has the code example in VB.NET.

To serialize Dictionary objects using an XML serializer, you have to implement a custom dictionary as described here: http://weblogs.asp.net/pwelter34/archive/2006/05/03/444961.aspx.

The errors were of the type:

Warning: session_start() [function.session-start]: Cannot send session
cookie - headers already sent by...

Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent...

One of those who reported the errors also provided a solution, which was to place the PHP session code before any of the html code. Perhaps the newer versions of PHP (I only have 5.1.1 installed) are getting more syntactically tighter. I know the newer versions of PHP are requiring full PHP tags now.

Anyway, there is a new version of the test.php code in my PHP install guide

Every Oracle Form is composed of Java objects. Text fields, buttons, frames, you name it, they are all some derivitive of Java awt or swing objects. As such, they can be extended.
Sounds simple, even too simple, doesn't it? Well, it really is!
If you're a Forms developer, there's a good chance that you know about embedding Java Beans (also called PJCs - Pluggable Java Components) into your Forms. They're really cool and can be used to accomplish all kinds of things. This takes PJCs one level further.

flippant

flippant