Support for Portlet API

Does the BEA Portal Server support portlets written
to the proposed Portlet API?
Specifically, I've played with Jetspeed before
and have some portlets for Jetspeed. How easy
is it to port those portlets to the Portal Server?
From what I've gone through so far with the Portal
Server 7 sampleportal site and looking through the
sample code, it seems to be very different from
what I'm used to in Jetspeed.
I would appreciate any pointers on documentations
geared more for developers. While the tutorials
are useful, they are a bit light on customization.
Lew

I doubt it since the Portlet API isn't finalized yet, so BEA's API (along
with others) is still very proprietary.
My best guess is that it won't be compliant untill one release version after
the spec has been completly finished and accepted. 1-2 years? And that is
if BEA decides to conform to the spec at all.
"Lew Davis" <[email protected]> wrote in message
news:[email protected]..
>
Does the BEA Portal Server support portlets written
to the proposed Portlet API?
Specifically, I've played with Jetspeed before
and have some portlets for Jetspeed. How easy
is it to port those portlets to the Portal Server?
From what I've gone through so far with the Portal
Server 7 sampleportal site and looking through the
sample code, it seems to be very different from
what I'm used to in Jetspeed.
I would appreciate any pointers on documentations
geared more for developers. While the tutorials
are useful, they are a bit light on customization.
Lew

Similar Messages

Why is there no WSDL type support for Web Api?

So I am just getting started with .Net WebApi and one thing that I am noticing straight away is that there is no Contract defining how the Api looks and should be consumed (Request/Responses from each Action), this is usually in the form of a WSDL for WCF/Soap.
It seems to me like this is something that would be very valuable and make life a lot easier for consumers of your Api.
Is there a reason there isn't one? Is there a programming paradime or principle that I am unaware of? Is there a way I could create one?

SOAP, REST AND PEOPLE'S CREATIVITY
SOAP needs a description document like WSDL because each resource can be consumed with different messages, there are no definition on the protocol about constraints to the possible names/messages that you can manipulate a resource.
For example, in SOAP your web service that allow clients manipulate an user can expose the operation that create an user in many different messages, like:
addUser
createUser
insertUser
Of course, these are just few sample messages, because I've see a lot of funny web services method names. There are really creative people out there.
In other hand, if you are exposing your underlying system using web api that really respect the REST principles, the client just need to know that you have a resource named Users, because there is 99% of chance that you can create an user in this way
POST /Users
And this occurs for each operation you want to expose using SOAP or a web api REST.
Despite being SOAP a protocol, which restricts what you can or can not do, and be REST a style architecture, which leaves many open points of how to do things. There are efforts to define conventions of how to expose and consume REST web apis.
DESCRIBING A WEB API REST
In the field of how to describe a web api REST I can cite
Swagger. It is not a attempt to create a WSDL like to web api REST, but it is a good attempt to create an open standard for describing web apis REST.
Swagger is a specification and complete framework implementation for describing, producing, consuming, and visualizing RESTful web services.
I use Swagger a lot and really love it, mainly because
Swagger UI that allow you generate a nice live console and documentation for your web api.
There are many implementations of Swagger for most of languages: C#, Java, Python, Ruby, etc.
If you are using ASP .NET Web API, there a some projects to auto generate the Swagger specification, like
Swagger.NET
GENERATING CLIENTS TO A WEB API REST
Because the constraints of REST, like the limited set of verbs (GET, POST, PUT, DELETE, etc) is not so difficuty to generate a client library to a web api REST.
Projects like
WebApiProxy can easily generate clients do C# and Javascript.
CONVENTIONS FOR WEB API REST
To keep our lifes as developers easier is good define some conventions of how our web api REST will behave, the best effort I know in this field is the very good
Apigee - Web Api Design ebook. The e-book is not an attempt to create a bible or a mantra about how to design your api, but rather a collection of conventions observed in large web REST apis, like Twitter, Facebook, Linkedin, Google, etc.

Support for additional apis

hello i to all
my question is that
Mobiles only support MIDP 1.0,2.0
but how these mobiles can support additional apis
like bluetooth and mmapi etc
please reply it

I do think that the j2me has some specific apis for bluetooth and mime... but the implementation of these technologies varies from cel to cel. So, you must make program including these kind of technologies but if the cell phone doesn't have this technology support in it, I'm not sure, but I do think that it'll not work. If I'm wrong in it... plz... correct me. =)

GetRealPath("/") supported for Servlet API 2.0?

Can anyone tell me if the getRealPath("/") method is suppored in the Servlet API 2.0? Or where I can find documentation from 2.0? Thanks!

I guess a better question would be: I've written code in Servlet API 2.3 and I've been testing w/ Tomcat 4.0.3 on my local machine. Everything is fine. The people I'm developing for just got a new server (b/c their old one didn't support servlets at all) which uses JServ which only supports servlet api 2.0. Now my servlet is throwing errors. getRealPath() was returning a path in Tomcat, but now it just returns null. And getResource() doesn't seem to be a valid method in api 2.0. Is there 2.0 code that I can use instead? And if so do I need to use an older api to compile it?

Support for Portlet...

Does Java EE 5 support portlets?
Any help / links in this regard will be useful.
Further, we are using Sun App Server 9.
If Java EE 5 does support portlet development, does Sun ApplServer 9 support deployment of portlets?
Thanks...
Message was edited by:
SD_STP

Java Portlets are being supported in the new Java Application Platform SDK Update 2 release.Porletcontainer is a part of this Application Platform SDK release.
You can download them from http://java.sun.com/javaee/downloads/index.jsp.
Netbeans Portlet Plugin is available that helps developers to develop, deploy and test portlets on the Portlet Container 1.0
Plugin can be downloaded from http://portalpack.netbeans.org/download.html

Apia, Samoa time zone support for iCloud

There does not seem to be support for the Apia, Samoa time zone in iCloud. This is an idiosyncratic time zone being UTC +13hrs with daylight savings (UTC +14hr) during the "summer" commencing at 3am on the last Sunday in September and ceasing at 4am on the first Sunday in April.
http://www.timeanddate.com/time/zone/samoa/apia
Tonga, Tokelau and Rawaki (Kiribati) have the same time zone but no DST.
American Samoa has the same time but a day earlier and no DST.
I tried to make an Apple support request but it wants an Apple hardware ID and I'm using iCloud on a Sony Vaio.

It looks like the reminders don't "float" - so all the dates and times I set for reminders while in St. Lous are reporting at weird times because of the time change from Tokyo time. Is there any way of fixing this short of resetting all the times?
Thanks,
doug

Support for DbXml specific functionality in XQuery vs. Shell or API

Is / will there be any support for doing common commands in pure XQuery rather than just programmatically or through the shell? For example, in the shell I can create / list / delete indexes on a container, output query plans, etc. Are the same functions that are called through the shell available as XQuery functions? possibly in a dbxml function namespace?
In a related question, but possibly deserving of a new thread if it doesn't already have one - I know XQuilla has the ability to call registered external functions from parsed XQuery, is there a way to tell DbXml to register a function with XQuilla's static context before using it? that would make it possible for me to add the functionality described above myself without disturbing your distributed code.

Not so handy with C++ (my everday languages are PHP and Java), but if you say it can be done then I'll take a hack at it. If you happen to have examples of how other people have done it and you could point me at them it would be marvelous.
To answer your second question: "bingo." It mostly means less interface work and brings it closer to what SQL can do in relational databases.
The project allows the end user to define their own document structures (schema definitions more or less) and then create instances of these documents in a XML editing interface. For each document type, the end user is also able to define a set of named queries (abstracted function declarations) which lets us captures business rules without customizing our PHP code. Because the structure and queries that will be used against the documents are user defined its fairly impossible for me to automatically setup adequate indexes for the container of each set of documents. So I need an interface to allow the user to create / review / delete the indexes themselves.
We've already created an interface that allows the user to execute arbitrary queries against a selected document. In the future we'd also like this same interface to do result set based content updates (through the XmlModify class) and whole document addition / replacement. So inclusion of index control makes sense as well. We can find ways to use the APIs, it just seems like this could benefit more than just our project.
Placing the functionality from the shell into xquery extension functions seems analogous to having the UPDATE, DELETE and CREATE syntaxes of SQL.

GroupWise 7.0 API Gateway is supported for Exchange 2007?

Can someone confirm that GroupWise 7.0 API Gateway is supported for Exchange 2007?
I found a note in a guide that stated it was not YET supported as of 1/27/2008.

bwalker2,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://support.novell.com/forums/faq_general.html
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

NLS ISO88595 support for ldap OID C API

Please Help!
How to order from Oracle Internet Directory C API to process single byte
string (ISO-8859-5) instead of
Unicode string ( in input and output parameters values ) ?
#include <ldap.h>
char* base ="cn=��_��, cn=com"; /* in ISO */
ldap_search_s(ld , base .... ); /* not detecting base with russian word */
How to switch NLS ISO support for ldap OID C API ?
If any other approach to solve it problem?
(for example in Oracle OCI C API it solved by setting client NLS_LANG
environment variable .
In my case NLS_LANG not working)

UP plz

API support for color extraction feature

Is there API support for color extraction feature? if not, is
it scheduled?

Hello, thanks for the post.
In order to provide the best user experience for color
extraction, we had to split the functionality between client-side
and server-side, so we are not able to offer an API for this
functionality at this time. We are, however, very interested in
feedback on what kinds of APIs are interesting to you and how you
are interested in using them, so folks, please let us know.
Current APIs, including the new Random theme browsing view
and to view comments to your themes, are available on the
kuler API
wiki. We've seen some really fabulous and creative use of the
kuler APIs, and we look forward to more.
Sami

JSF 1.0 and Portlet API

Does JSF and Portlet API works together?
Can we use JSF 1.0 for portlet JSP development?

JSF 1.0 does include a number of changes specifically to support writing portlets with the JSR 168 API. We didn't quite have time to get that support in "out-of-the-box", but we did make JSF sufficiently configurable that one could add JSR 168 support simply by dropping in a bonus JAR! (If memory serves, that JAR needed to apply decorators to FacesContextFactory and ViewHandler, but my memory is a bit foggy at the moment.)
-- Adam Winer (EG member)

Multilingual support for BI Publisher reports

Hi all,
We are currently using BI Publisher APIs to generate reports. Our aim is to enable multi-language support for these reports.The translatable strings based on the locale are stored in xliff files. Using jedit, UTF-8 encoding is chosen as the default encoding for these xliff files. It works fine with french and some other single byte languages but with double byte languages like chinese,japanese it is throwing the below mentioned error.
Interestingly, with the same type of encoding (UTF-8), the BI Publisher stand alone server successfully supports the multi byte feature.
java.io.UTFDataFormatException: Invalid UTF8 encoding.
at oracle.xml.parser.v2.XMLUTF8Reader.checkUTF8Byte(XMLUTF8Reader.java:160)
at oracle.xml.parser.v2.XMLUTF8Reader.readUTF8Char(XMLUTF8Reader.java:187)
at oracle.xml.parser.v2.XMLUTF8Reader.fillBuffer(XMLUTF8Reader.java:120)
at oracle.xml.parser.v2.XMLByteReader.saveBuffer(XMLByteReader.java:450)
at oracle.xml.parser.v2.XMLReader.fillBuffer(XMLReader.java:2363)
at oracle.xml.parser.v2.XMLReader.tryRead(XMLReader.java:1087)
at oracle.xml.parser.v2.XMLReader.scanXMLDecl(XMLReader.java:2922)
at oracle.xml.parser.v2.XMLReader.pushXMLReader(XMLReader.java:519)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:283)
at oracle.apps.xdo.template.FOProcessor.mergeTranslation(FOProcessor.java:1922)
at oracle.apps.xdo.template.FOProcessor.createFO(FOProcessor.java:1706)
at oracle.apps.xdo.template.FOProcessor.generate(FOProcessor.java:1027)
at glog.server.report.BIPReportRTFCoreBuilder.format(BIPReportRTFCoreBuilder.java:61)
at glog.server.report.BIPReportCoreBuilder.build(BIPReportCoreBuilder.java:152)
at glog.server.report.BIPReportCoreBuilder.buildFormatDocument(BIPReportCoreBuilder.java:77)
at glog.webserver.oracle.bi.BIPReportProcessServlet.process(BIPReportProcessServlet.java:279)
at glog.webserver.util.BaseServlet.service(BaseServlet.java:614)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:654)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:445)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:379)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:292)
at glog.webserver.report.BIPReportPreProcessServlet.getDocument(BIPReportPreProcessServlet.java:57)
at glog.webserver.util.AbstractServletProducer.process(AbstractServletProducer.java:79)
at glog.webserver.util.BaseServlet.service(BaseServlet.java:614)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at glog.webserver.session.ParameterValidation.doFilter(ParameterValidation.java:29)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at glog.webserver.screenlayout.ClientSessionTracker.doFilter(ClientSessionTracker.java:59)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at glog.webserver.util.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:44)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:263)
at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767)
at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697)
at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
at java.lang.Thread.run(Thread.java:595)
<Line 1, Column 1>: XML-20108: (Fatal Error) Start of root element expected.
oracle.apps.xdo.XDOException
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at oracle.apps.xdo.common.xml.XSLT10gR1.invokeNewXSLStylesheet(XSLT10gR1.java:641)
at oracle.apps.xdo.common.xml.XSLT10gR1.transform(XSLT10gR1.java:247)
at oracle.apps.xdo.common.xml.XSLTWrapper.transform(XSLTWrapper.java:181)
at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:1151)
at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:275)
at oracle.apps.xdo.template.FOProcessor.createFO(FOProcessor.java:1809)
at oracle.apps.xdo.template.FOProcessor.generate(FOProcessor.java:1027)
at glog.server.report.BIPReportRTFCoreBuilder.format(BIPReportRTFCoreBuilder.java:61)
at glog.server.report.BIPReportCoreBuilder.build(BIPReportCoreBuilder.java:152)
at glog.server.report.BIPReportCoreBuilder.buildFormatDocument(BIPReportCoreBuilder.java:77)
at glog.webserver.oracle.bi.BIPReportProcessServlet.process(BIPReportProcessServlet.java:279)
at glog.webserver.util.BaseServlet.service(BaseServlet.java:614)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:654)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:445)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:379)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:292)
at glog.webserver.report.BIPReportPreProcessServlet.getDocument(BIPReportPreProcessServlet.java:57)
at glog.webserver.util.AbstractServletProducer.process(AbstractServletProducer.java:79)
at glog.webserver.util.BaseServlet.service(BaseServlet.java:614)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at glog.webserver.session.ParameterValidation.doFilter(ParameterValidation.java:29)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at glog.webserver.screenlayout.ClientSessionTracker.doFilter(ClientSessionTracker.java:59)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at glog.webserver.util.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:44)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:263)
at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767)
at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697)
at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
at java.lang.Thread.run(Thread.java:595)
Caused by: oracle.xdo.parser.v2.XMLParseException: Start of root element expected.
at oracle.xdo.parser.v2.XSLProcessor.reportException(XSLProcessor.java:806)
at oracle.xdo.parser.v2.XSLProcessor.newXSLStylesheet(XSLProcessor.java:571)
Thanks,
Anuradha .

Hi Klaus,
Even notepad does not solve the issue!
Is there any other text editor with reliable encoding, by which we can save as UTF-8?
Thanks
Kosstubh

Development Environment for Server APIs in Webcenter Interaction 10.3

Hi, I installed “Oracle Web Center Interaction 10.3" on standard environment mentioned by oracle (Window 2003 server, IIS6.0, SQL Server 2005). Everything works fine concerning the portal and services.
I also have visual studio 2005 on the same machine and trying to setup a development environment where I can user server APIs (I start with creating IPTSession).
I am using follwong code to start with:
/String serverConfigDir = ConfigPathResolver.GetOpenConfigPath();
IOKContext configContext = OKConfigFactory.createInstance(serverConfigDir, "portal");
PortalObjectsFactory.Init(configContext);
IPTSession ptSession = PortalObjectsFactory.CreateSession();
Problem: code compiles if I add few dlls, but it do not run, it throws following error
com.plumtree.openkernel.exceptions.OKFactoryException: Error in AOKFactory.createAndInitializeInstance, unable to create object with name 'com.plumtree.openkernel.impl.config.Config' in assembly or JAR file 'openconfig'.
I think either server APIs are not more supported in 10.3 or I do not know how to setup the development environment for server APIs.
Can anyone help??

i have already tried putting hardcoded path but it didn't help, morover the previous line gives me correct path.
I issue i mentioned seems to be related with some setting or missing native dlls
com.plumtree.openkernel.exceptions.OKFactoryException: Error in AOKFactory.createAndInitializeInstance, unable to create object with name 'com.plumtree.openkernel.impl.config.Config' in assembly or JAR file 'openconfig'.
i got follwing extract from the wsserver-wrapper.log file
INFO | jvm 1 | 2009/02/20 12:26:17 | 2-20-2009 12:26:17.606 Info OpenKernel.Config Disabled-1235112977434 WrapperStartStopAppMain com.plumtree.openkernel.impl.config.providers.ConfigXMLFileProvider Loading config data from C:\bea\alui\ptws\10.3.0\bin\..\..\..\common/../settings
INFO | jvm 1 | 2009/02/20 12:26:18 | 2-20-2009 12:26:18.325 Info OpenKernel.Config Disabled-1235112977434 WrapperStartStopAppMain com.plumtree.openkernel.impl.config.providers.ConfigXMLFileProvider Setting subscription data.
INFO | jvm 1 | 2009/02/20 12:26:18 | container config context:EAS:wsserver
i didn't modified anything in any config file, just configured everything on one machine with oracle configuration manager

[svn:fx-trunk] 10876: Add support for drag-and-drop from Spark List to Spark List.

Revision: 10876
Author:   [email protected]
Date:     2009-10-05 15:20:07 -0700 (Mon, 05 Oct 2009)
Log Message:
Add support for drag-and-drop from Spark List to Spark List.
- List drop related handlers
- LayoutBase APIs
- VerticalLayout DND support
Notes:
- ListSkin is not final.
- Drag-scrolling not yet implemented.
QE notes: Only VerticalLayout works, HorizontalLayout still not implemented.
Doc notes: None
Bugs: None
Reviewer: Deepa
Tests run: checkintests
Is noteworthy for integration: No
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/List.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/layouts/VerticalLayout.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/layouts/supportClasses/LayoutBase.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/spark/ListSkin.mxml
    flex/sdk/trunk/frameworks/spark-manifest.xml
Added Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/layouts/supportClasses/DropLocation.as

Whoops, disregard my question - I just read the spec that indicates drag and drop is scheduled for later work.
David

Support for PL/SQL Record

We have a procedure in a package,this procedure makes use of a Record Type.
In BPEL, whiile creating the partner link, when we are trying to access this procedure we get the following error.
"WSDLException:faultCode=OTHER_ERROR:Database type is either not supported or is not implemented.
Parameter L_ECO_REC is of type SAN_REC_TYPE which is either not supported or not an implemented data type.
Check to ensure that the type of the parameter is one of the supported datatypes or that there is a collection or user defined type definition representing this type defined in the database.contact oracle support if error is not fixable."
Also please find below the package specification and body:
CREATE OR REPLACE package eco_pack is
TYPE San_Rec_Type IS RECORD
( Eco_Name VARCHAR2(10)
, Change_Notice_Prefix VARCHAR2(10)
, Change_Notice_Number NUMBER
, Organization_Code VARCHAR2(3)
PROCEDURE sandeep(l_eco_rec IN eco_pack.San_Rec_Type);
end;
CREATE OR REPLACE package body eco_pack is
PROCEDURE createeco(l_eco_rec IN eco_pack.San_Rec_Type) AS
BEGIN
INSERT
INTO ag_log
VALUES(1, 'ECO name is' || l_eco_rec.eco_name, 1);
COMMIT;
END;
end;
Does BPEl support PL/SQL Record Type, if so how ?
Thanks,
Shivram
.

PL/SQL types like RECORD, BOOLEAN and TABLE are not supported in the DB adapter with the current BPEL PM release (as the error message indicates). You can use JPublisher manually to generate an OBJECT type that corresponds with the RECORD. JPublisher will also create a wrapper and conversion APIs to convert between the two. You would then call the wrapper API which takes the OBJECT and then calls the underlying PL/SQL that takes the RECORD.
With the 10.1.2 Phase 2 release of BPEL PM, the DB adapter does all of this for you from within the design time wizard. JPublisher is invoked silently under the covers, the SQL that gets generated is automatically loaded into the database schema. That will create the OBJECT type, wrapper and conversion APIs. An XSD is generated for the wrapper API. Your partner link will invoke the wrapper, not the original API.
Note also that support for BOOLEAN and TABLE was also added. JPublisher generates wrapper APIs that substitute appropriate types for these parameters (e.g. INTEGER for BOOLEAN, Nested Table for TABLE).

Support for Portlet API

Similar Messages

Maybe you are looking for