There is a JavaScript Bug in PTControls.js (/bea/alui/ptimages/imageserver/plumtree/common/private/js/jscontrols/LATEST) if the doctype of the portal page is set to HTML 4.0 Transition. The portlet menus will not be displayed beneath the portlet header, but in the upper left corner of the browser window. To fix this bug you have to add

if (this.popup.style.left == '') {
   this.popup.style.left = '' + left + 'px';
   this.popup.style.top = '' + top + 'px';
}

to the 'PTMenu.prototype.show' method in line 13688.

There is another JavaScript bug in Oracle WebCenter Interaction 10gR3 (\bea\alui\ptimages\imageserver\plumtree\common\private\jsutil\LATEST\ptutil.js). My current version of this file 'ptutils.js' is 334989. You can find the bug in line 116:

                if (srcObj.Class && (srcObj.Class == 'Array') && (typeof srcObj[i] == 'function')) { continue; }

which should be

                if (srcObj.Class && (srcObj.Class == 'Array') && (typeof srcObj[i] == 'function')) { continue; }
                if (typeof srcObj[i] == 'function') { continue; } // <-- This line is missing

For some reasons it is very helpful to have a java decompiler. If you need one, have a look to http://java.decompiler.free.fr/, which also has a good Eclipse integration.

There is a javascript bug in PTControls.js (\bea\alui\ptimages\imageserver\plumtree\common\private\js\jscontrols\LATEST). My current version of this file is 334989. You can find the bug in line 16424

PTTabControl.prototype,constructor = PTTabControl;

which has to be

PTTabControl.prototype.constructor = PTTabControl;

On August 27th, 2008, Bill Benac published a very useful Firefox Add-on. With this add-on you can always recognize the portal server the response came from. Especially it is very useful in a clustered environment.


My colleagues and me extended this add-on with additional information, like the construction and response time. You can get this add-on from Bill Benac's website http://blog.billbenac.com/blog/2008/08/firefox-plugin-shows-host-port.html or send me a mail ;-).

Um auf Anmeldeinformationen einer Web Applikation aus einer anderen Web Applikation auf der selben Maschine zugreifen zu können und so eine Art von Single Sign-On abzubilden, ist entscheidend, dass in der web.config beider Applikationen der selbe machineKey konfiguriert wurde.

LoginWebSite:

web.config:
<system.web>
    <!-- [...] -->

    <authentication mode="Forms">
        <forms loginUrl="Login.aspx"/>
    </authentication>

    <authorization>
        <deny users="?"/>
    </authorization>

        <machineKey validationKey="D61B3C89CB33A2F1422FF158AFF7320E8DB8CB5CDA1742572A487D94018787EF42682B202B746511891C1BAF47F8D25C07F6C39A104696DB51F17C529AD3CABE" decryptionKey="FBF50941F22D6A3B229EA593F24C41203DA6837F1122EF17" />
   
    <!-- [...] -->
</system.web>

Login.aspx:
    <!-- [...] -->
    <div>
        <asp:Login ID="Login1" runat="server">
        </asp:Login>
    </div>
    <!-- [...] -->


ApplWebSite:

web.config:
<system.web>
    <!-- [...] -->

    <authentication mode="Forms">
        <forms loginUrl="/Login/Login.aspx"/>
    </authentication>

    <authorization>
        <deny users="?"/>
    </authorization>

        <machineKey validationKey="D61B3C89CB33A2F1422FF158AFF7320E8DB8CB5CDA1742572A487D94018787EF42682B202B746511891C1BAF47F8D25C07F6C39A104696DB51F17C529AD3CABE" decryptionKey="FBF50941F22D6A3B229EA593F24C41203DA6837F1122EF17" />

    <!-- [...] -->

</system.web>

Mit C# 3.0 ist es möglich, Klassen von außen mit "Extension Methods" zu erweitern, ohne von der entsprechenden Klasse ableiten zu müssen. Dies ist von Vorteil, wenn man den ursprünglichen Datentyp (die ursprüngliche Klasse) beibehalten (Instanz i ist weiterhin vom Typ t), sealed oder Fremd-Klassen erweitern, oder unabhängig bei zukünftigen Weiterentwicklungen sein möchte... Die Erweiterungen werden im Quellcode verwendet, als gehören sie zu der jeweiligen Klasse. Im Visual Studio 2008 werden Extension Methods von IntelliSence durch den Hinweis "(extension)" gekennzeichnet.

using

System;
using System.Collections.Generic;
using System.Linq;
using System.Text;

namespace

_002_MethodExtensions
{
   
    public static class MyStringExtension
    {
       public static string Reverse( this string s)
      {
          if (s == null || s.Length == 0)
             return s;

          StringBuilder sb = new StringBuilder ();
         for ( var i = s.Length; i != 0; --i) 
         {
            sb.Append(s[i - 1]);
         }

          return sb.ToString();
      }
   }

   class Program
   {
      static void Main( string [] args)
      {
          string hello = "Hello World" ;
          Console .WriteLine( "{0} --> {1}" , hello, hello.Reverse());
      }
   }

}

Ein neues Sprachfeature von C# 3.0 sind automatisch implementierte Eigenschaften. Wo bisher ausimplementierte Getter und Setter notwendig waren, reicht nun die simple Anweisung "get;" bzw. "set;" bei der Property Deklaration.

Beispiel:

using

System;
using System.Collections.Generic;
using System.Linq;
using System.Text;

namespace _001_AutoImplProperties
{
   
   /// <summary>
   /// Sample class for Automatically Implemented Properties
   /// </summary>
   class Person
   {
      public Guid Id { get ; private set ; } // only public getter
      public string Name { get ; set ; } // public getter and setter
      public string Address { get ; set ; }
      public string City { get ; set ; }
      public string Zip { get ; set ; }

      public Person( Guid id)
      {
         Id = id;
      }

      public override string ToString()
      {
         return string .Format( "{0} ({1})" , Name, Id);
      }
   }

   class Program
   {
      static void Main( string [] args)
      {
         Person a = new Person ( Guid .NewGuid()) { Name = "Andreas" , Address = "Adresse 1" , Zip = "12345" , City = "Ort 1" };
         Person b = new Person ( Guid .NewGuid()) { Name = "Melanie" , Address = "Adresse 2" , Zip = "98765" , City = "Ort 2" };

         Console .WriteLine(a);
         Console .WriteLine(b);
      }
   }
}