Java Nullpointer exception while importing docs using Webtop 6.5

Hello DM Experts,

We are in the process of setting up Documentum 6.5. Users are getting Java null pointer exception while importing the documents in cabinets.The functionality is working for few users and failing for others for the same cabinets.

The exception popes up at the final screen when after putting all the required attributes users press "OK"....

Attached screen shot has more details of the error..

I am wondering if there is somthing to do with the permission sets.....Any help will be greatly appreciated..

Thanks.

Find more posts tagged with

Comments

AshishSrivastava

The issue seems to be in your custom TBO code.

Are you trying to set some attribute where it is throwing error?

Kind Regards,

Ashish Srivastava

rajanvyadav

Thanks for your reply.

Yes...Ther are about 20 attbutes ( 5 Mandatory and rest optional) to be filled while importing the document...After putting in the mandatory attributes like Names, Author, Doc Clasification etc...while excuting the import process this error pops up...

Could you please bit elaborate the possible issue with custome code...I have not been involved in the webtop fron end customizations...

Thanks

AshishSrivastava

can you post your TBO code - Type based Business Object - tboRddmcDoc

It is not in webtop customization

Kind Regards,

Ashish Srivastava

rajanvyadav

Thansk for the help Ashish....I could not take out the TBO code due system unavalibity today.

As soon as I get the code...we will take our discussion forward..

Thanks once again....

rajanvyadav

Hello Abhishek,

I could get to the cstome TBO code and also got the custome attribute piece of code causing the null exception. I got this code from the tbo.jar on the tomcat where webtop is dployed.Here, we are trying to set the folder path as an attribute and null value of this attribute is causing the exception.

I wanted to be able to debug this code so I set up the code in Docuemntum Composer.Though, I do not have any prior experience on Documentum Composer, I could manage to set up the code as I had worked on othe eclipse based IDE.

If you have an idea and can help me to set up the debugging enviroment, would help me to nail down the reason of null exception. Or if you can guide me with the process of deployment for webtop, would help me to put more debug statements in code.....

Thanks for all the assitance so far..

AshishSrivastava

First of all my name is Ashish (not Abhishek)

Anyways No worries

If you can get your source code of tbo.jar, you can set it up in your eclipse or any java ide, put necessary dfc jars in classpath and try to compile it.

then you can put the debug statements to get to the root of the issue.

again, build, export the jar and place the jar file in the same location where you found it on tomcat

Now whenever you will import/create new object, you can see your debug statements.

can you post what statement was causing the issue?

As you mentioned, you are trying to set the folder path to some attribute value, you can put some statement taht only assign in case the attribute is not null or you can make the attribute a mandatory field.

Kind Regards,

Ashish Srivastava

rajanvyadav

Hello Ashish (this time I double checked if I am putting the correct name ...sorry about mistake last time )

I could nail down the piece of code which is causing the null pointer exception..

protected void doLink (String folderSpec, Object[] extendedArgs) throws DfException{

try{

IDfSession session = getSession();

IDfId oFolderId =

new DfId(folderSpec);IDfFolder oParentFolder=

null;

if ( oFolderId.isObjectId() )oParentFolder = (IDfFolder)session.getObject(oFolderId);

elseoParentFolder = (IDfFolder)session.getObjectByPath(folderSpec);

String strParentName = oParentFolder.getObjectName();

m_strFolderPath = oParentFolder.getFolderPath(0);}

catch

(Exception e){}

super.doLink(folderSpec, extendedArgs);

Somehow the value of m_strFolderPath variable is not being set...which is causing the code to fail.....

AshishSrivastava

Good to hear that you got the root cause.

Kind Regards,

Ashish Srivastava

Francois Dauberlieu

Could it be that you get the error when oParentFolder is a Cabinet ?

RaviJha

Hmmm... not exactly, even if the oParentFolder is a cabinet, you should normally get the value for r_folder_path[0].

Could it be that the folderSpec that you have doesnt correspond to a folder id or folder's path i.e the IDfPersistentObject that you got is actually not an IDfFolder? But then I would have expected a different error.

Maybe debugging at this point will help.

Ravi

mszurap

Just to make your code simpler:

protected void doLink (String folderSpec, Object[] extendedArgs) throws DfException {

IDfFolder oParentFolder = getSession().getFolderBySpecification(folderSpec);

m_strFolderPath = oParentFolder.getFolderPath(0);

//do the rest...

super.doLink(folderSpec, extendedArgs);

}

Still got errors on this?