I expect org.netbeans.modules.websvc.wsdl.WsdlDataObject isn't use any more.
Is that right Rico ?

Rico, please can you suggest a solution for Mobility Pack.

The WsdlDataObject still exists in Netbeans. The ServiceInformation part of it
was separated into a separate class. Added
WsdlDataObject.getCookie(ServiceInformation.class) to return ServiceInformationImpl.

Note that in the Enterprise Pack, this WsdlDataObject has been superseded by the
WsdlDataObject of SeeBeyond for the WSDL editor. If this is a concern, contact
Ritesh.Adval@Sun.COM

Maybe I don't fully understand what do you mean by your response. I know that
the ServiceInformation impementation could be obtained by calling getCookie(
ServiceInformation.class ) on the WsdlDataObject. The problem probably is in
registration of the ServiceInformation implementation because when I call
getCookie the code traverses down to the XmlDataObject where is returned null (
the ServiceInformation cookie is probably not registered as cookie ).

If the WsdlDataObject has been replaced by new implementation from SeeBeyond
then the problem with cookie registration has been probably created because in
old implementation (5.0) the getCookie method returned data properly. If there
is different approach in getting ServiceInformation.class implementation in new
version of Enteprise pack could you please draft me solution howto obtain data
similar to the ServiceInformation? Thanks.

Sorry if I was not clear.
In a pure Netbeans environment (i.e., no Enterprise Pack patches) the fix that I
put in will work---the ServiceInformation cookie has been registered appropriately.
If that IDE has the Enterprise Pack patches, this WsdlDataObject has been
superseded to use a different WsdlDataObject from the Enterprise Pack. I can see
two possible solutions to this:
1. Have the WsdlDataObject of SeeBeyond register the ServiceInformation cookie
like the one above.
2. Have you register it if you have the proper context. 
The WsdlDataObject in websvc/core used to have two "personalities"-- a
DataObject and as a ServiceInformation. The ServiceInformation part has been
factored out of WsdlDataObject as a stand-alone class and if that is what you
need, and you already have the dataobject of the WSDL, then it may be possible
for you to obtain it.
Let me know if this is still not clear. 

To cover all cases, org.netbeans.modules.websvc.core.ServiceInformationSupport
is now provided. Use this to get a ServiceInformation, passing in the dataobject.

Class ServiceInformationSupport is not in trunk but only in release55 branch. Is
it possible to commit it also to trunk?

So far I have only been working on release55. Excuse my ignorance, but when you
say trunk what does that mean?

release55 is only one branch of the development tree. The main branch is trunk
(It's branch with no name = it's main branch). I suggest you to ask some of you
coleagues howto merge your changes to the trunk. Could you please make it as
soon as possible because we can't compile out project without your changes. Thanks.

Just FYI, it is not a priority for the J2EE team to make this change available
in the trunk. There is no committment to keep trunk up to date, trunk will be
updated after the 5.5 release. We may do this change if it is really easy, but
not if this represents any non-trivial amount of work.

Michal, I sent you a note on this but have not gotten any reply, so I am putting
it here:
The changes made that caused this bug to happen were made in the release55
branch. The main change was the separation of ServiceInfo from the
WsdlDataObject into another class. The trunk does not have this change so (1)
WsdlDataObject.getCookie(ServiceInformation.class) should not return null and
(2) you should be able to compile. 

Marking as fixed in Netbeans 5.5. The changes made were not trivial, touching
many files.

misk, could you please verify the fix?

Is it commited to the trunk?

This was not committed to the trunk. Please see comment from Petr Jiricka.

v.