on 02-10-2005 1:48 PM
Hi,
I am trying a sample case study Web Dynpro application which uses Adaptive RFC Model. The application development in NetWeaver 7.0.0 went fine.
I am also able to configure SLD Data Supplier settings in the Visual Administrator and a corresponding JCo Destination in the Content Administrator.
Though the deployment is successful, I get an exception when the application is run.
I'm producing the top part of the stack trace below
-
com.sap.tc.webdynpro.progmodel.context.DictionaryException: type 'com.sap.demo.flightlist.model.types.Bapimaxrow' not found: com.sap.dictionary.runtime.DdException:
at com.sap.tc.webdynpro.progmodel.context.DictionaryHandler.getSimpleType(DictionaryHandler.java:322)
at com.sap.tc.webdynpro.progmodel.context.DictionaryHandler.getDataType(DictionaryHandler.java:118)
at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.init(AttributeInfo.java:515)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes(NodeInfo.java:899)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:879)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:887)
at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:279)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:382)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.createApplication(ClientApplication.java:301)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:546)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:198)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:153)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
-
The type in question is available in the IDE (i.e in the source development project in NetWeaver).
I'm new to NetWeaver as well as the J2EE Engine. So, I have no clue as to what may be wrong. I was able to deploy and run sample applications which didn't use Models or Context-Model data binding, though.
All help is welcome. Please let me know if the full details of the error is needed.
Regards,
Amshuman
Hi,
Thanks for the solutions.
I can't say I understand Ulli Hoffmann's solution. This is definitely because I don't know the workings of J2EE Engine.
But I have created only one JCo-connection as Achim Hauck predicted. I'll try creating the two connections and post the results. With hindsight, I remember mentioning two names in the Create Model Wizard for model data and meta-data.
Thanks and regards,
Amshuman
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
you'll need 2 jco-connections. one for data & one for meta-data.
did you test both successfull in content administrator?
kr, achim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
there are two problems involved here:
1) in one recent 700 installation the java dictionary runtime has bug, which causes the stack trace being incomplete
For that you need to get a new SapDictionaryTypesRuntime.jar.
2) when this one runs fine your stack trace should include a message saying '... failed to create provider: Field LTRFLDDIS not a member of DFIES'.
This is now the actual problem in your installation. The JCO doesn't work with a recent 700 dictionary modification.
To fix it you will need a new jrfc.jar. Check out note 802727.
regards, Ulli
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.