poorna chandran

Greenhorn
+ Follow
since Apr 02, 2006
Merit badge: grant badges
Cows and Likes
Cows
Total received
In last 30 days
0
Forums and Threads

Recent posts by poorna chandran

HI,

I AM WORKING IN WEB SERVICES WITH AXIS.PLEASE GUIDE ME IN THIS QUESTION

WE CAN CHECK OUR LOCAL WEBSERVICES ARE WORKING IN BASIC PROFILE CONFORMANCE OR NOT
BUT
HOW CAN WE CHECK REMOTE WEB SERVICES WORKING IN BASIC PROFILE 1.0 OR 1.1

OR NOT?
TELL ME BRIEF IDEAS ALSO FRIENDS SHARE YOUR IDEAS WITH WEB SERVICES
18 years ago
Hello friends,

i am portal developments with portlets.

Please clarify the my following doubts

1.How portlets assembled in to portals.
2.how we cache portals contents
3.how we embed a pluto container to our tomcat web applications(web applications +portlets)(both want to be in same web context)
18 years ago
hello friends,

i want details about portlets (JSR 168)

1.portlet is a advance concept?
2.learning portlets is usefull
3.Tell me some usefull links for portlets
4. I WANT TO DEVELOP A PORTAL WITH PORTLETS?
18 years ago
Portlets are pluggable user interface components that are managed and displayed in a web portal. Portlets produce fragments of markup code that are aggregated into a portal page. Typically, following the desktop metaphor, a portal page is displayed as a collection of non-overlapping portlet windows, where each portlet window displays a portlet. Hence a portlet (or collection of portlets) resembles a web-based application that is hosted in a portal. Portlet applications include email, weather reports, discussion forums, and news.

Portlet standards are intended to enable software developers to create portlets that can be plugged in any portal supporting the standards.

[edit]
Portlet Standards
The purpose of the Web Services for Remote Portlets protocol is to provide a web services standard that allows for the "plug-n-play" of remote running portlets from disparate sources.

The Java Portlet Specification (JSR168) enables interoperability for portlets between different web portals. This specification defines a set of APIs for between the portlet container and the portlet addressing the areas of personalization, presentation and security.

Apache Pluto is a reference implementation of JSR168. Other than the reference implementation, a number of vendors provide commercial implementations of the portlet container. Some of the leading vendors are IBM, Oracle and BEA Systems. These vendors provide standards based implementations and also provide extensions not yet approved by the standards body. Furthermore a number of open-source portal solutions support JSR168 such as Apache's Jetspeed-2 Enterprise Portal, JBoss Portal, and Liferay Portal.
18 years ago

Originally posted by Satou kurinosuke:
could you please post your jsp file (the part using JSTL) ?



<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
<html>
<head>
<title>Simple Example</title>
</head>
<body>

<c:set var="browser" value="${header['User-Agent']}"/>
<c ut value="${browser}"/>

</body>
</html>
19 years ago
JSP

Originally posted by Satou kurinosuke:
could you please post your jsp file (the part using JSTL) ?



Pls Freind Find files here

http://www.ispacedesign.com/Jstl.zip
http://www.ispacedesign.com/Jstl.zip
19 years ago
JSP
JSTL
Pls friends reply me to this exception JSTL. im using jstl in tomcat 5.0.x and jdk1.5 following exception is arises.

HTTP Status 500 -

--------------------------------------------------------------------------------

type Exception report

message

description The server encountered an internal error () that prevented it from fulfilling this request.

exception

javax.servlet.ServletException: javax.servlet.jsp.tagext.TagAttributeInfo.(Ljava/lang/String;ZLjava/lang/String;ZZ)V
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:256)
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)


root cause

java.lang.NoSuchMethodError: javax.servlet.jsp.tagext.TagAttributeInfo.(Ljava/lang/String;ZLjava/lang/String;ZZ)V
org.apache.jasper.compiler.TagLibraryInfoImpl.createAttribute(TagLibraryInfoImpl.java:573)
org.apache.jasper.compiler.TagLibraryInfoImpl.createTagInfo(TagLibraryInfoImpl.java:433)
org.apache.jasper.compiler.TagLibraryInfoImpl.parseTLD(TagLibraryInfoImpl.java:291)
org.apache.jasper.compiler.TagLibraryInfoImpl.(TagLibraryInfoImpl.java:222)
org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:458)
org.apache.jasper.compiler.Parser.parseDirective(Parser.java:523)
org.apache.jasper.compiler.Parser.parseElements(Parser.java:1577)
org.apache.jasper.compiler.Parser.parse(Parser.java:171)
org.apache.jasper.compiler.ParserController.parse(ParserController.java:253)
org.apache.jasper.compiler.ParserController.parse(ParserController.java:137)
org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:237)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:456)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:439)
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:552)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:291)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:301)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:248)
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)


note The full stack trace of the root cause is available in the Tomcat logs.


--------------------------------------------------------------------------------

Apache Tomcat/5.0.18
19 years ago
JSP