Error when Creating Web Dynpro Model in CAF-Service

[Former Member]

Hi All,

I reaaly need help. AFter updating to SPS 9, it was necessary to redeploy my Entity Service. That contains to "Create a Web Dynpro Model" in the Service Explorer,

to get an interface of the Service in my Web Dynpro Application.

Before I update to SPS 9, the Application works fine.

But now, when I want to "Create a Web Dynpro Model" in the NWDS I get the following Error-Message (its not a useful Error-Message):

<i>Error cannot create Web Dynpro Model:

Creation of Web Dynpro model failed. Reason: null </i>

Thanks for helping me

Steve

[Former Member · Accepted solution]

Steve,

I'v checked the FileSystemService implementation and in SP8 I found the following statement:

        if(lAbsolutePath.length() > 249)
        {
            if(logging)
                sCategoryMDOLocating.errorT(sLocation, "computeAbsolutePath()", "absolute path too long (" + lAbsolutePath.length() + ") for MDO: ");
            return null;
        }

You see that restrictive lenght is 249 but your lenght is 253. So, it seems SP9 implementation is changed.

So, there are following solutions:

1. Change the package and class name lenght.

2. move local development configurations' root folder to another location with shorter path prefix

Before this check the implementation of this class for SP9 because I don't have IDE of this service pack level.

\eclipse\plugins\com.sap.ide.metamodel.core.libs_2.0.0\SapMetamodelCore.jar

Class: com.sap.ide.metamodel.core.service.FileSystemService

Method: computeAbsolutePathInternal

Best regards,

Aliaksei

[Former Member]

Sorry,

it is obvious that 249 < 253, so I actually don't know why it does work under SP8, possible you changed something in your file system after migration. But it's a source of your problem, you need to shorten paths.

Best regards,

Aliaksei

[Former Member]

Your right, after updating to SPS I create a new DC for my Services. The path now is longer, than the old DC, that caused the error.

Thanks for your help, now I reduce the path

Bye Steve

[Former Member]

Hi Guys,

The developers (some of them) seem to encounter the same problem (NWDS SP9). The Web Dynpro Model is not getting created for CAF for a few user ids. I have tried to replicate the problem for these users by:

- shortening their user ids

- changing the Local Development folder to a shorter path

- using an user id of the same character length as those users ids for whom the same CAF web dynpro model creation seems to work without any problems

Because it is working for some user ids we are not able to understand the root cause of the problem. I would be glad if you could shed some light on this.

Regards,

Krishna

Message was edited by:

Krishna G.S

[Former Member]

Hi Krishna,

i didnt understand your question exactly.

Can you give me a more detailed question, pelase?

In our project it was teh problem that the path of our DC Project was too long.

The shouldnt be shorter than 250 signs.

Error: could not get a valid path for ModelClass "<b>cas.conti.com.sap.cd.databaseservices.cd_database.<u>changedescriptiontableservice</u>.QChangeDescriptionTableServiceFindByTitle</b>"

When you name your Services too long than you could have problem.

In my case there are more than 249 sign (no need to count for you ).

ChangeDescriptionTabelService is too long you know.

Hope I can help you little bit

Bye STeve

[Former Member]

Hi Steve,

Thanks for your efforts. The problem is that for some developers the CAF Web Dynpro model creation doesn't seem to work ("Creation of Web Dynpro Model failed. Reason: null"). The same activity of creating a CAF Web Dynpro model works with some ids where their path to the workspace is actually lengthier than the ones for which it doesn't work..

For instance the user “uma.th” has the workspace "C:\Documents and Settings\uma.th\Documents\SAP\workspace" and the CAF application is in "C:\Documents and Settings\uma.th\.dtc\LocalDevelopment\DCs\sap.com\cafone"

This user is able to create the model (e.g “cafone”) successfully without any problems.

Now for another user by the id “mut.ar” & “m” the same model creation (i.e. “cafone”) does not work and their respective Local Development folders are “C:\Documents and Settings\mut.ar\.dtc\LocalDevelopment” & “C:\Documents and Settings\m\.dtc\LocalDevelopment”. So for both these cases their path to the Local Development is shorter (for “m”) / same (for “mut.ar”) in co-relation to the user “uma.th”. These two users have tried to create CAF application with name “t” as well. This didn’t work either so I am wondering if this could be the problem with the max no of characters. Please note that the OS level authorizations are the same for all these users.

The workspace log file shows the following (for user “m”):

!ENTRY com.tssap.util 4 0 Feb 27, 2007 13:16:00.17

!MESSAGE Feb 27, 2007 1:16:00 PM com.sap.ip.mmr.foundation.AssociationsOfObject [Thread[main,5,main]] Error: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 35, 3c, 3f(:main:, row:1, col:3)(:main:, row=1, col=3) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 35, 3c, 3f(:main:, row:1, col:3)

Hence I am not able to understand the reason why this problem is being encountered only by some users. It doesn't make sense.

Regards,

Krishna

[Former Member]

Hi Steve,

I just wish to add that I have seen that the same setup works fine on another system for the user id "mut.ar". I don't think this problem is due to the character length. I had even tried to fix this problem by uninstalling & reinstalling the NWDS SP9 & removing the workspaces & recreating the user id etc on the system where this problem is being encountered. The problem still remains the same.

Regards,

Krishna

[Former Member]

Hi Steve,

please check the workspace log for original exception.

Also please check the thread: /thread/112510 [original link is broken]

But I think that's not the case.

Best regards,

Aliaksei

[Former Member]

Hi Aliaksei,

the problem in the thread is the same I got.

When I use only 7 letters for the operation name, the creation work. When I use more then 7 letters the creation doesnt work.

But its hard to find a methodname with only 7 letters.

In SPS 8 I didnt have problems with the length of method names. Why is it so?

The workspace log:

!ENTRY com.tssap.util 4 0 Okt 10, 2006 15:12:45.577
!MESSAGE Oct 10, 2006 3:12:45 PM         com.sap.ip.mmr.foundation.AssociationsOfObject        [Thread[main,5,main]] Error: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 35, 3c, 3f(:main:, row:1, col:3)(:main:, row=1, col=3) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 35, 3c, 3f(:main:, row:1, col:3)

!ENTRY com.tssap.util 4 0 Okt 10, 2006 15:12:45.592
!MESSAGE Oct 10, 2006 3:12:45 PM         com.sap.ip.mmr.foundation.AssociationsOfObject        [Thread[main,5,main]] Error: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 35, 3c, 3f(:main:, row:1, col:3)(:main:, row=1, col=3) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 35, 3c, 3f(:main:, row:1, col:3)

!ENTRY com.tssap.util 4 0 Okt 10, 2006 15:12:48.705
!MESSAGE Oct 10, 2006 3:12:48 PM  com.sap.ide.metamodel.core.service.FileSystemService.comp... [Thread[main,5,main]] Error: absolute path too long (253) for MDO: 

!ENTRY com.tssap.util 4 0 Okt 10, 2006 15:12:48.705
!MESSAGE Oct 10, 2006 3:12:48 PM  com.sap.ide.metamodel.core.service.FileSystemService.comp... [Thread[main,5,main]] Error: absolute path too long (253) for MDO: 

!ENTRY com.tssap.util 4 0 Okt 10, 2006 15:12:48.705
!MESSAGE Oct 10, 2006 3:12:48 PM  com.sap.ide.metamodel.webdynpro.implementation.ModelProxy... [Thread[main,5,main]] Error: could not get a valid path for ModelClass "cas.conti.com.sap.cd.database.services.cd_database.changedescriptiontableservice.QChangeDescriptionTableServiceFindByTitle" (path too long?)

!ENTRY com.tssap.util 4 0 Okt 10, 2006 15:12:48.705
!MESSAGE Oct 10, 2006 3:12:48 PM  com.sap.ide.metamodel.webdynpro.implementation.ModelProxy... [Thread[main,5,main]] Error: could not get a valid path for ModelClass "cas.conti.com.sap.cd.database.services.cd_database.changedescriptiontableservice.QChangeDescriptionTableServiceFindByTitle" (path too long?)

Thanks

Steve

[Former Member]

Now I can isolate the error for a more detailed error description.

The error raises when I add a findBy-method with an parameter, the error doesnt exist when I create a method without any parameter.

Hope that helps