Hi Portal Developers,
A new reference is available that lists ALL public portal APIs, and provides the following information:
JAR file for compilation
Location of JAR file
Required sharing reference for portalapp.xml (runtime reference)
The list is provided as a spreadsheet in XML, enabling you to sort and filter as needed, and to get a quick overview of the available classes, packages and JARs.
Click <a href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f08f37c1-992c-2a10-35a6-fbb1600aff51">here</a> for the spreadsheet.
The spreadsheet also provides similar information for using the built-in tag libraries.
Feel free to respond to this post, or email the author, if you have any suggestions.
That is really very nice that we have such a reference now,This will really save lots of time of portal developers,i too have spent lot of time searching for various JARs.But why we are not putting this file available right away on SDN itself??We can provide a link or put it in Downloads so that this reference will be easily availabe.
Except for defining the "official public" APIs in one sheet, this definitely shoud not save any time, as evereyone has the possibility to use ClassLocator -- http://sourceforge.net/projects/classlocator -- which does the job definitively faster than manually looking up some table!
Daniel, of course you know that this is not against you; I'm just estonished that people think this should save time (in such a case, please install ClassLocator to <i>really</i> save time...). Also look out for other threads about it to get some extra ideas how to use it... Also see Pimp Up My NWDS Part 1
Hope it helps to clarify this
I agree that the classlocator tool is the way to go. However...
Despite its existence, people still ask for JARs and sharingreferences, perhaps they do not want to use the class locator tool or just want the information before starting to develop.
Class locator is not an official SAP tool so, technically, I am not supposed to point people to it. So I have to provide something that describes the extent of our APIs, and how to make use of them.
I use the classlocator, and it certainly is faster than manually figuring out where the JAR is and then adding an external reference. The spreadsheet does help with the sharing reference, as well as listing the built-in tag libraries.
P.S.: Hope to see you at Tech Ed, Munich. We can have a debate on this there.
> Despite its existence, people still ask for JARs and sharingreferences
I think the reason is more that these people do not know ClassLocator instead of not wanting to use it... These who have used it once within the SAP/Java/Portal world will <i>never</i> give it away again...
> The spreadsheet does help with the sharing reference,
> as well as listing the built-in tag libraries.
As said before, I didn't want to say <i>anything</i> against your sheet, I would never say anything against anything produced by yours
> Hope to see you at Tech Ed, Munich. We can have a debate on this there.
That seems to be a promise that you will be there Very nice to hear, and I'll be there, too!
There is a new project online to search for SAP Jars in a database:
Current state is NW 2004s SPS 09, SAP API Doc is SPS 10, mainly portal JARs, more added on the fly.
It's planned to include a "report missing classes" function to include the community to improve the quality of this database.
concerning the hint to use "sapjarfinder.com" - this is really the wrong way to go (again; see my statement above). If you need the class for build-time issues, you'll need a copy of the JAR locally (through a locally deployed server or just as a copy of the JARs from some server in your company). And having these at hand, one definitely should use ClassLocator, as this directly extends the .classpath file.
Using "sapjarfinder.com" just means you don't know the way to got... A short introduction for ClassLocator can be found here: Pimp Up My NWDS Part 1
This is really strange how people run in masses into the wrong direction...
Hope it helps (to turn around)