on 06-20-2008 2:21 PM
Hi
I've created an EJB DC that needs to use the security API, and have set references that allow the project to be built locally. However, it fails to build on the CBS due to "packages not existing".
From doing a bit of searching, it seems I need to add SAP-JEE to the dependencies. Is this correct? I can't find the 7.10 version of this component in our SLD.
Please could someone help? Is there a place on SAP help where I can find out what is in each package? I have no idea which SCA to import, and haven't managed to find any documentation outlining what is in each of the SAP SCA files - so I'm a little bit stuck.
Any help would be very much appreciated!
Thanks
Stuart
Just for some more details, I'm getting the following errors in the build log:
package com.sap.security.api does not exist
package com.sapportals.connector.connection does not exist
package com.sapportals.portal.ivs.cg does not exist
package com.sapportals.portal.prt.runtime does not exist
Does anyone know which dependencies are required to make this work?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok... here's one more update before I throw our NWDI server off the roof.
After much pain and frustration, I have found what appear to be the correct build-time dependencies for my EJB project. Despite a lack of documentation (or very well hidden documentation), these seem to be the dependencies I need:
ENGFACADE
ENGINEAPI (for com.sap.exception, com.sap.security.api.sda, security.class)
EP-BASIS-API (for tc/epbc/connectivityfw/api, tc/epbc/prt/api)
FRAMEWORK
SAP_BUILDT
However, after adding these as built-time dependencies in the SLD, updating CMS, importing the relevant SCA's and rebuilding my projects... I still get the same errors!
Please could someone help with this?! Unfortunately there's nothing obviously wrong, so I'm running out of ideas here.
Thanks
Stuart
Ok... it turns out this was another of my silly mistakes. I hadn't defined the dependencies within each DC in NWDS (Component Properties view). Unfortunately I can't find any documentation that highlights this step, which left it to a process of trial and error to get it working.
I now have the project giving very few build errors. All I need now is to find which dependency to add for com.sapportals.portal.ivs.cg.IConnectorGatewayService (and related classes/interfaces).
If anyone knows where I can find this, please let me know. I've searched on Google, SDN, SAP Help, and can't find it anywhere.
In the dependencies tab, I also see warnings about references to deprecated components. I've fixed most, but it doesn't say which components to use in place of the following:
- security_api
- tc/conn/connectorframework
Any help on the dependencies would be great!
Thanks in advance
Stuart
Thanks Ayyapparaj
I've got the local build working fine... it's the DC build that's giving problems. I don't see a way to add jar files to the references of a DC build. It seems this must be done via DC dependencies (define dependency in SLD, import in CMS, then select which imported DC's you need as dependencies for each of your own DC's).
Am I getting this wrong? This is the first time I'm trying this, so I could possibly be missing something important.
I need to set the dependency within the Development Infrastructure perspective.
Do you know how I should do this?
Thanks
Stuart
Hi everyone
I found this doc that refers to NW 2004 & 7.0, but has no specific reference to 7.1: [https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/194bdc4f-0901-0010-82ba-bf73af5d5f75]
In the introduction it says:
Currently, there is not a software component (SC) delivered with NW2004 or 2004S (although 2004S is planned to ship portal SCs at time of this publication) that contains the commonly used portal libraries. SAP Note 906973 states that developers should use External Library DCu2019s to satisfy build time dependencies for portal development (par files). This is a different approach from the days of being able to use class finding tools such as jarclassfinder and right clicking to add a jar to the projectu2019s classpath. This no longer works with DCu2019s because at build time they recreate their classpath based on the u201CUsed DCsu201D listed in the DCu2019s definition (thus deleting any entries you added). However this initial work is more than worth it because using public dependencies based on external libraries allows any developer to check out your project from the DTR and be build ready. This avoids the tedious process of having a developer send you their par and you having to figure out which import belongs to which jaru2014which is a very common complaint of Java developers today.
Seeing as they plan on shipping portal SC's at the time of publication, I assume this should be available now? Please could someone from SAP confirm?
Thanks
Stuart
Hello-
It was my understanding that there was going to be quite a bit of portal jar files rolled into an SC within 7.0 (2004s at the time), however I dont think the jar you are looking for is yet part of the EP_BUILDT SC. My advice for now would be to simply package the jar into an External Library, create a public part and reference this as part of your build time requirements.
Hope it helps,
Marty
Hi Stuart,
How did you resolve this. I created a wd project which uses com.sap.security.api. I just extended ECLIPSE_HOME variable to include this jar file. But when I try to activate my activity it fails with build error "package com.sap.security.api does not exist". How could I add it to my project. If I develop the same project local no problem, but if I use NWDI it throws this error. I am really in need of fixing this ASAP. Can you please help me in resolving this.
Thank You,
Hari.
User | Count |
---|---|
94 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.