incomprehensible Fatal error with Jetspeed 1.5 on JONAS 4.1
Hi,
I try to deploy Jetspeed 1.5 on Jonas 4.1.2. When I don't touch the
database properties of torque.properties, there is no ploblem. Jonas 4.1.2
starts a database server(HSQL) and I try to use the Jonas database for
Jetspeed.
Here is my torque.properties
# Copyright 2004 The Apache Software Foundation
# Licensed under the Apache License, Version 2.0 (the License);
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an AS IS BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# ---
# $Id: Torque.properties,v 1.9 2004/03/17 19:10:26 jford Exp $
#
# This is the configuration file for Torque.
#
# Note that strings containing , (comma) characters must backslash
# escape the comma (i.e. '\,')
#
# ---
# NOTE NO torque. prefix on properties - this is a kluge to make it also
include the TR.properties
torque.applicationRoot = .
# ---
#
# L O G G I N G
#
# ---
# We use Log4J for all Torque logging and we embed the log4j
# properties within our application configuration.
# ---
# THIS SEEMS TO BE IGNORED - HENCE IT IS DUPLICATED IN log4j.properties
#log4j.category.org.apache.torque = ALL, org.apache.torque
#log4j.appender.org.apache.torque = org.apache.log4j.FileAppender
#log4j.appender.org.apache.file = ${applicationRoot}/logs/log
#log4j.appender.org.apache.layout = org.apache.log4j.PatternLayout
#log4j.appender.org.apache.layout.conversionPattern = %d [%t] %-5p %c -
%m%n
#log4j.appender.org.apache.append = false
# ---
#
# T O R Q U E P R O P E R T I E S
#
# ---
# These are your database settings. Look in the
# org.apache.pool.* packages for more information.
#
# The parameters to connect to the default database. You MUST
# configure these properly.
# ---
torque.database.default=db_jonas
torque.database.default.adapter=hypersonic
### torque.database.default.adapter=mysql
### torque.database.default.adapter=oracle
### torque.database.default.adapter=mssql
##
## Using torque's old pool
##
torque.dsfactory.db_jonas.connection.driver = org.hsqldb.jdbcDriver
torque.dsfactory.db_jonas.connection.url =
jdbc:hsqldb:hsql://localhost/db_jonas
torque.dsfactory.db_jonas.connection.user = jonas
torque.dsfactory.db_jonas.connection.password = jonas
torque.dsfactory.db_jonas.factory=org.apache.torque.dsfactory.TorqueDataSourceFactory
# The number of database connections to cache per ConnectionPool instance
(specified per database)
torque.dsfactory.db_jonas.pool.defaultMaxConnections=10
torque.dsfactory.db_jonas.pool.maxExpiryTime=3600
torque.dsfactory.db_jonas.pool.connectionWaitTimeout=10
### MySQL
### torque.dsfactory.default.connection.driver = org.gjt.mm.mysql.Driver
### torque.dsfactory.default.connection.url =
jdbc:mysql://localhost:3306/jetspeed
### torque.dsfactory.default.connection.user = root
### torque.dsfactory.default.connection.password =
### Oracle
### torque.dsfactory.default.connection.driver =
oracle.jdbc.driver.OracleDriver
### torque.dsfactory.default.connection.url =
jdbc:oracle:thin:@nirvana:1521:bluesun3
### torque.dsfactory.default.connection.user = jetspeed
### torque.dsfactory.default.connection.password = jetspeed
### Microsoft SQL
### torque.dsfactory.default.connection.driver = net.avenir.jdbc3.Driver
### torque.dsfactory.default.connection.url = jdbc:
AvenirDriver://localhost:1433/jetspeed
### torque.dsfactory.default.connection.user = jetspeed
### torque.dsfactory.default.connection.password = jetspeed
### SAP DB
### torque.database=sapdb
### torque.database.url = jdbc:sapdb:///tst
### torque.database.driver=com.sap.dbtech.jdbc.DriverSapDB
# The interval (in milliseconds) between which the PoolBrokerService logs
# the status of it's ConnectionPools.
#
# Default: No logging = 0 = 0 * 1000
torque.database.logInterval=0
# Determines if the quantity column of the IDBroker's id_table should
# be increased automatically if requests for ids reaches a high
# volume.
torque.idbroker.cleverquantity=true
# Determines whether the managers cache instances of the business objects.
# And also whether the MethodResultCache will really cache results.
torque.manager.useCache = true
## Using Jdbc2Pool
Access status bar URL from JSP in IFramePortlet
Dear all, I would like to access the url I see in status bar (browser page, bottom part) http://mymachine:9090/jetspeed/portal/user/visitor/page/my.psml from a jsp hosted in a IFramePortlet. %=request.getRequestURI()% does not return the whole path, i.e. it returns the path specified in the definition of the portlet in xreg file only (myApp/myStartingJsp.jsp). I know it is not a Jetspeed compliant way of working but I would appreciate any hint. Thank you Stefano Ing. Stefano Bianchi Softeco Sismat S.p.A. Via De Marini, 1 - WTC Tower 16149 Genoa (ITALY) e-mail: [EMAIL PROTECTED] tel: +39 010 60.26.368 fax: +39 010 60.26.350 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Portlets execution flow
Hi Oscar, Note: This answer does not solve your problem, it only confirms it. Read on if you are interested. We are using Jetspeed 1.6-dev and we struggle with the same problem (Velocity portlets in our case). The idea was to have multiple portlets on the page share information stored in rundata. The BuildNormalContext() method builds the context based entirely on data stored in rundata. We use a system to store data in the rundata based on portlet id / portlet group (parameter) and global for all. We then write action handlers that performs all the logic and updates the rundata. Of course this relies on the fact that the action event is executed BEFORE the buildNormaContext() methods are executed. Specifying the action for a specific portlet like this: form action=$jslink.getPortletById($portlet.ID) name=RundataTest method=GET or this: form action=$jslink.getAction(portlets.test.general.Rundata_TestAction, $portlet) name=RundataTest method=GET executes the action specifically for that particular portlet. Exactly what we wanted. But, then we noticed that the some of the portlets displayed old data! The pattern for the problem was top-bottom-left-right as you describe. Lets say we have two portlets A B (AE=Action Event, BNC=BuildNormalContext). 1. Clicking on portlet A executes: AE for A - BNC for A - BNC for B (Perfect!). 2. Clicking on portlet B executes: BNC for A - AE for B - BNC for B (Disaster!) In case 2 portlet A is diplayed using old values from the rundata object. Oh dear... The only answer I have received on this problem is that in JSR168 (Jetspeed-2 implements this) the action event should always be executed before the portlets are rendered in an undefined order. Very cute, but migrating to Jetspeed-2 is not an option for the moment. It would be nice to get an opinion from an experienced Jetspeed developer on how much work it would be to modifiy Jetspeed-1 to behave in this way to. Right now we have to be really careful when planning the actions/flow in the portal and this is quite a limitation for the moment. Kind regards, Bjorn Vidar Remme Oscar Ruiz [EMAIL PROTECTED] 05.08.2004 13:33 Please respond to Jetspeed Users List To: 'Jetspeed Users List' [EMAIL PROTECTED] cc: Subject:Portlets execution flow Hi all, can anyone clarify me how multiple MVC portlets (JSP for instance) are executed and output displayed? There is obviously an order in which portlet controllers are called, apparently from top to bottom and left to right. *apparently* the View component (JSP) is executed right after the Controller, hence if portlets are sharing a Model the whole thing results in a disaster. Is there a way of rendering the page (i.e. execute the View components) after all controllers have completed? Many thanks. Oscar. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: zip stream and content-type in portlet
Frédéric FACHINETTI wrote: Hello, I have a portlet that query a database and then display the resultset using some JSP's. Now, I want to retrieve the query results not in html format but in a zip file format ie when I submit the query in my portlet I then have the save as ... window and I'm able to retrieve the query results thru a zipped text file. I managed to do it in an old perl application by changing the content-type and by printing the result in a zip stream. But with java and Jetspeed, I have no idea if it's possible and how to proceed. Is there a content-type specific to each portlet ? Nope, HTTP only defines a content-type for a whole response. To do this within Jetspeed, you ned to define a new screen template for example: WEB-InF/conf/templates/vm|jsp/SendFile.vm: $data.Response.setContentType(application/octet-stream)$file create an action to set the file object in the context to the ZIP file you want to send in your portlet create a link to this screen like this: jetspeed-root/template/SendFile/action/MySendAction. This is standard Turbine stuff so you should probably check out the Turbine documentation and mailing-list for further examples of how to use the Turbine screen to send non-HTML output. -- Raphaël Luta - [EMAIL PROTECTED] Apache Jetspeed - Enterpise Portal in Java http://portals.apache.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Portlets execution flow
What if you use the following form? form action=$jslink.setAction(myaction) name=RundataTest input type=submit name=eventSubmit_doSomething/ /form This should fire the action before anything else. As long as your portlets do not store data in the portletsessionstate, then this should be fine. Jeremy Ford [EMAIL PROTECTED] From: Bjorn Vidar Remme [EMAIL PROTECTED] Reply-To: Jetspeed Users List [EMAIL PROTECTED] To: Jetspeed Users List [EMAIL PROTECTED] Subject: Re: Portlets execution flow Date: Fri, 6 Aug 2004 11:10:55 +0200 Hi Oscar, Note: This answer does not solve your problem, it only confirms it. Read on if you are interested. We are using Jetspeed 1.6-dev and we struggle with the same problem (Velocity portlets in our case). The idea was to have multiple portlets on the page share information stored in rundata. The BuildNormalContext() method builds the context based entirely on data stored in rundata. We use a system to store data in the rundata based on portlet id / portlet group (parameter) and global for all. We then write action handlers that performs all the logic and updates the rundata. Of course this relies on the fact that the action event is executed BEFORE the buildNormaContext() methods are executed. Specifying the action for a specific portlet like this: form action=$jslink.getPortletById($portlet.ID) name=RundataTest method=GET or this: form action=$jslink.getAction(portlets.test.general.Rundata_TestAction, $portlet) name=RundataTest method=GET executes the action specifically for that particular portlet. Exactly what we wanted. But, then we noticed that the some of the portlets displayed old data! The pattern for the problem was top-bottom-left-right as you describe. Lets say we have two portlets A B (AE=Action Event, BNC=BuildNormalContext). 1. Clicking on portlet A executes: AE for A - BNC for A - BNC for B (Perfect!). 2. Clicking on portlet B executes: BNC for A - AE for B - BNC for B (Disaster!) In case 2 portlet A is diplayed using old values from the rundata object. Oh dear... The only answer I have received on this problem is that in JSR168 (Jetspeed-2 implements this) the action event should always be executed before the portlets are rendered in an undefined order. Very cute, but migrating to Jetspeed-2 is not an option for the moment. It would be nice to get an opinion from an experienced Jetspeed developer on how much work it would be to modifiy Jetspeed-1 to behave in this way to. Right now we have to be really careful when planning the actions/flow in the portal and this is quite a limitation for the moment. Kind regards, Bjorn Vidar Remme Oscar Ruiz [EMAIL PROTECTED] 05.08.2004 13:33 Please respond to Jetspeed Users List To: 'Jetspeed Users List' [EMAIL PROTECTED] cc: Subject:Portlets execution flow Hi all, can anyone clarify me how multiple MVC portlets (JSP for instance) are executed and output displayed? There is obviously an order in which portlet controllers are called, apparently from top to bottom and left to right. *apparently* the View component (JSP) is executed right after the Controller, hence if portlets are sharing a Model the whole thing results in a disaster. Is there a way of rendering the page (i.e. execute the View components) after all controllers have completed? Many thanks. Oscar. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ On the road to retirement? Check out MSN Life Events for advice on how to get there! http://lifeevents.msn.com/category.aspx?cid=Retirement - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Portlets execution flow
Bjorn, Oscar - I have never seen the problems you are mentioning below - my action handler methods ALWAYS execute before the build*() methods on the active portlets. We are currently using Velocity-based portlets. When we specify the action parameter in a form, we use the following code template: form method=post action=$jslink or form method=post action=$jslink.setAction(portlets.FooAction) The first version uses the default action as specified in the xreg for the portlet - this is what we use in most cases. The second version uses any action you specify - as long as the action package you are using is declared to Turbine using the module.packages key (see TurbineResources.properties, and look for that key.) For an example of the first version, look at the source in /tutorial/tutorials/9/templates/vm/portlets/html/coffees-browser.vm (directly from cvs) as well as the related xreg files. An example of the second version is at: http://portals.apache.org/jetspeed-1/tutorial/7/events.html. Good luck, Eric Bjorn Vidar Remme [EMAIL PROTECTED] 08/06/2004 04:10 AM Please respond to Jetspeed Users List [EMAIL PROTECTED] To Jetspeed Users List [EMAIL PROTECTED] cc Subject Re: Portlets execution flow Hi Oscar, Note: This answer does not solve your problem, it only confirms it. Read on if you are interested. We are using Jetspeed 1.6-dev and we struggle with the same problem (Velocity portlets in our case). The idea was to have multiple portlets on the page share information stored in rundata. The BuildNormalContext() method builds the context based entirely on data stored in rundata. We use a system to store data in the rundata based on portlet id / portlet group (parameter) and global for all. We then write action handlers that performs all the logic and updates the rundata. Of course this relies on the fact that the action event is executed BEFORE the buildNormaContext() methods are executed. Specifying the action for a specific portlet like this: form action=$jslink.getPortletById($portlet.ID) name=RundataTest method=GET or this: form action=$jslink.getAction(portlets.test.general.Rundata_TestAction, $portlet) name=RundataTest method=GET executes the action specifically for that particular portlet. Exactly what we wanted. But, then we noticed that the some of the portlets displayed old data! The pattern for the problem was top-bottom-left-right as you describe. Lets say we have two portlets A B (AE=Action Event, BNC=BuildNormalContext). 1. Clicking on portlet A executes: AE for A - BNC for A - BNC for B (Perfect!). 2. Clicking on portlet B executes: BNC for A - AE for B - BNC for B (Disaster!) In case 2 portlet A is diplayed using old values from the rundata object. Oh dear... The only answer I have received on this problem is that in JSR168 (Jetspeed-2 implements this) the action event should always be executed before the portlets are rendered in an undefined order. Very cute, but migrating to Jetspeed-2 is not an option for the moment. It would be nice to get an opinion from an experienced Jetspeed developer on how much work it would be to modifiy Jetspeed-1 to behave in this way to. Right now we have to be really careful when planning the actions/flow in the portal and this is quite a limitation for the moment. Kind regards, Bjorn Vidar Remme Oscar Ruiz [EMAIL PROTECTED] 05.08.2004 13:33 Please respond to Jetspeed Users List To: 'Jetspeed Users List' [EMAIL PROTECTED] cc: Subject:Portlets execution flow Hi all, can anyone clarify me how multiple MVC portlets (JSP for instance) are executed and output displayed? There is obviously an order in which portlet controllers are called, apparently from top to bottom and left to right. *apparently* the View component (JSP) is executed right after the Controller, hence if portlets are sharing a Model the whole thing results in a disaster. Is there a way of rendering the page (i.e. execute the View components) after all controllers have completed? Many thanks. Oscar. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Portlets execution flow
Hi all, Well the trouble by using setAction() is that the action is executed for all the portlets (if a suitable method exists). You can easily test this by adding multiple instances of the same portlet to a page (same action class) or multiple portlets with different action classes but the same event name. You will then see that the action event is executed once for all the portlets. The pattern is thus (AE=action event, BNC=buildNormalContext): AE for portlet A, BNC for portlet A, AE for portlet B, BNC for portlet B etc.. Not what we want at all, we just want the action event to fire once. This is why I specify the portlet ID in the action like this: $jslink.getAction(myaction, $portlet) The action event is then executed only once, but as I described in my previous post the pattern is (clicking on portlet B): BNC-A, AE -B, BNC-B and not the desired AE-B, BNC-A, BNC-B. Note: I am using getAction() because setAction() is deprecated according to the documentation. It does the same thing. Kind regards, Bjorn Vidar Remme [EMAIL PROTECTED] 06.08.2004 15:54 Please respond to Jetspeed Users List To: Jetspeed Users List [EMAIL PROTECTED] cc: Subject:Re: Portlets execution flow Bjorn, Oscar - I have never seen the problems you are mentioning below - my action handler methods ALWAYS execute before the build*() methods on the active portlets. We are currently using Velocity-based portlets. When we specify the action parameter in a form, we use the following code template: form method=post action=$jslink or form method=post action=$jslink.setAction(portlets.FooAction) The first version uses the default action as specified in the xreg for the portlet - this is what we use in most cases. The second version uses any action you specify - as long as the action package you are using is declared to Turbine using the module.packages key (see TurbineResources.properties, and look for that key.) For an example of the first version, look at the source in /tutorial/tutorials/9/templates/vm/portlets/html/coffees-browser.vm (directly from cvs) as well as the related xreg files. An example of the second version is at: http://portals.apache.org/jetspeed-1/tutorial/7/events.html. Good luck, Eric Bjorn Vidar Remme [EMAIL PROTECTED] 08/06/2004 04:10 AM Please respond to Jetspeed Users List [EMAIL PROTECTED] To Jetspeed Users List [EMAIL PROTECTED] cc Subject Re: Portlets execution flow Hi Oscar, Note: This answer does not solve your problem, it only confirms it. Read on if you are interested. We are using Jetspeed 1.6-dev and we struggle with the same problem (Velocity portlets in our case). The idea was to have multiple portlets on the page share information stored in rundata. The BuildNormalContext() method builds the context based entirely on data stored in rundata. We use a system to store data in the rundata based on portlet id / portlet group (parameter) and global for all. We then write action handlers that performs all the logic and updates the rundata. Of course this relies on the fact that the action event is executed BEFORE the buildNormaContext() methods are executed. Specifying the action for a specific portlet like this: form action=$jslink.getPortletById($portlet.ID) name=RundataTest method=GET or this: form action=$jslink.getAction(portlets.test.general.Rundata_TestAction, $portlet) name=RundataTest method=GET executes the action specifically for that particular portlet. Exactly what we wanted. But, then we noticed that the some of the portlets displayed old data! The pattern for the problem was top-bottom-left-right as you describe. Lets say we have two portlets A B (AE=Action Event, BNC=BuildNormalContext). 1. Clicking on portlet A executes: AE for A - BNC for A - BNC for B (Perfect!). 2. Clicking on portlet B executes: BNC for A - AE for B - BNC for B (Disaster!) In case 2 portlet A is diplayed using old values from the rundata object. Oh dear... The only answer I have received on this problem is that in JSR168 (Jetspeed-2 implements this) the action event should always be executed before the portlets are rendered in an undefined order. Very cute, but migrating to Jetspeed-2 is not an option for the moment. It would be nice to get an opinion from an experienced Jetspeed developer on how much work it would be to modifiy Jetspeed-1 to behave in this way to. Right now we have to be really careful when planning the actions/flow in the portal and this is quite a limitation for the moment. Kind regards, Bjorn Vidar Remme Oscar Ruiz [EMAIL PROTECTED] 05.08.2004 13:33 Please respond to Jetspeed Users List To: 'Jetspeed Users List' [EMAIL PROTECTED] cc: Subject:Portlets execution flow Hi all, can anyone clarify me how multiple MVC portlets (JSP for instance) are executed and output displayed? There is obviously an order in
RE: Portlets execution flow
Bjorn: You can limit the impact of which class runs your method via the action by qualifying the action. That is: use action=Myportlet2.doUpdate rather than action=doUpdate. With the second method any portlet which has a doUpdate method will fire. As to having several Portlets share a current model. We have found that it is best to have a separate action class that modifies the model. Then using the setAction style described in this thread you can update the common model first. That action will be called before any rendering. Your portlet should then be limited to building up your context. Otherwise you are duplicating your efforts by putting model update code in 2 places. Bob -Original Message- From: Bjorn Vidar Remme [mailto:[EMAIL PROTECTED] Sent: Friday, August 06, 2004 10:41 AM To: Jetspeed Users List Subject: Re: Portlets execution flow Hi all, Well the trouble by using setAction() is that the action is executed for all the portlets (if a suitable method exists). You can easily test this by adding multiple instances of the same portlet to a page (same action class) or multiple portlets with different action classes but the same event name. You will then see that the action event is executed once for all the portlets. The pattern is thus (AE=action event, BNC=buildNormalContext): AE for portlet A, BNC for portlet A, AE for portlet B, BNC for portlet B etc.. Not what we want at all, we just want the action event to fire once. This is why I specify the portlet ID in the action like this: $jslink.getAction(myaction, $portlet) The action event is then executed only once, but as I described in my previous post the pattern is (clicking on portlet B): BNC-A, AE -B, BNC-B and not the desired AE-B, BNC-A, BNC-B. Note: I am using getAction() because setAction() is deprecated according to the documentation. It does the same thing. Kind regards, Bjorn Vidar Remme [EMAIL PROTECTED] 06.08.2004 15:54 Please respond to Jetspeed Users List To: Jetspeed Users List [EMAIL PROTECTED] cc: Subject:Re: Portlets execution flow Bjorn, Oscar - I have never seen the problems you are mentioning below - my action handler methods ALWAYS execute before the build*() methods on the active portlets. We are currently using Velocity-based portlets. When we specify the action parameter in a form, we use the following code template: form method=post action=$jslink or form method=post action=$jslink.setAction(portlets.FooAction) The first version uses the default action as specified in the xreg for the portlet - this is what we use in most cases. The second version uses any action you specify - as long as the action package you are using is declared to Turbine using the module.packages key (see TurbineResources.properties, and look for that key.) For an example of the first version, look at the source in /tutorial/tutorials/9/templates/vm/portlets/html/coffees-browser.vm (directly from cvs) as well as the related xreg files. An example of the second version is at: http://portals.apache.org/jetspeed-1/tutorial/7/events.html. Good luck, Eric Bjorn Vidar Remme [EMAIL PROTECTED] 08/06/2004 04:10 AM Please respond to Jetspeed Users List [EMAIL PROTECTED] To Jetspeed Users List [EMAIL PROTECTED] cc Subject Re: Portlets execution flow Hi Oscar, Note: This answer does not solve your problem, it only confirms it. Read on if you are interested. We are using Jetspeed 1.6-dev and we struggle with the same problem (Velocity portlets in our case). The idea was to have multiple portlets on the page share information stored in rundata. The BuildNormalContext() method builds the context based entirely on data stored in rundata. We use a system to store data in the rundata based on portlet id / portlet group (parameter) and global for all. We then write action handlers that performs all the logic and updates the rundata. Of course this relies on the fact that the action event is executed BEFORE the buildNormaContext() methods are executed. Specifying the action for a specific portlet like this: form action=$jslink.getPortletById($portlet.ID) name=RundataTest method=GET or this: form action=$jslink.getAction(portlets.test.general.Rundata_TestAction, $portlet) name=RundataTest method=GET executes the action specifically for that particular portlet. Exactly what we wanted. But, then we noticed that the some of the portlets displayed old data! The pattern for the problem was top-bottom-left-right as you describe. Lets say we have two portlets A B (AE=Action Event, BNC=BuildNormalContext). 1. Clicking on portlet A executes: AE for A - BNC for A - BNC for B (Perfect!). 2. Clicking on portlet B executes: BNC for A - AE for B - BNC for B (Disaster!) In case 2 portlet A is diplayed using old values from the rundata object. Oh dear... The only answer I have received on this problem is that in JSR168
RE: jetspeed 1 and wap
Danny: Thanks for point out the bug. At least now I know it is not my setup procedure. Since I am new in WAP device, I would really appreciate it if you can share your working wml/default.jsp,wml/default.vm files and other related scripts which allow user login Thank you very much -Original Message- From: Danny [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 04, 2004 2:59 AM To: 'Jetspeed Users List' Subject: AW: jetspeed 1 and wap I figured out, that the wml/default.jsp for jsp layout doesn't support login. I copied over the wml/default.vm and some related scripts and fixed it. -Ursprüngliche Nachricht- Von: Shen, Ching [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 3. August 2004 18:31 An: [EMAIL PROTECTED] Betreff: jetspeed 1 and wap I am trying to setup my jetspeed apps (ops) for WAP users who using blackberry devices. User can access directly to wml file OK, http://linuxdv01:8080/ops/wml/weather.wml But if they use http://linuxdv01:8080/ops/, they view user anon whole default HTML page, instead only login portion. Problem1: with WML enable only, user can't login Problem: with HTML/WML enable , user can login, but get html view for user turbine instead wml view What I did wrong or missing? Please help. Any suggestion will be greatly appreciated - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: jetspeed 1 and wap
Raphael: Thanks for the help. I checked the file and see there has no place mentioned blackburry browser blackburry browser claim Protocol WAP 1.1 , HTTP/IPPP Gateways WAP 1.1 - any WAP-compliant gateway, without proprietary extensions (must support WTP-level segmentation and reassembly) HTTP/IPPP - Blackberry Enterprise Server with Mobile Data Service extensions Description WAP - push applications are not supported - supports WAP 1.1 features, including WML 1.3, WMLScript 1.2, and WTLS HTTP - supports HTTP over SSL/TLS - supports secure access to corporate intranets, including push applications and custom plug-ins for data parsing and conversion Since I am new in WAP , I would really appreciate it if you can let me know whether their browser meet one of jetspeed 1 client category. Does upgrade to jetspeed 2 will help? -Original Message- From: Raphaël Luta [mailto:[EMAIL PROTECTED] Sent: Thursday, August 05, 2004 5:43 AM To: Jetspeed Users List Subject: Re: jetspeed 1 and wap Shen, Ching wrote: I am trying to setup my jetspeed apps (ops) for WAP users who using blackberry devices. User can access directly to wml file OK, http://linuxdv01:8080/ops/wml/weather.wml But if they use http://linuxdv01:8080/ops/, they view user anon whole default HTML page, instead only login portion. Problem1: with WML enable only, user can't login Problem: with HTML/WML enable , user can login, but get html view for user turbine instead wml view What I did wrong or missing? Please help. Any suggestion will be greatly appreciated Make sure the client you use for testing is recognized as a WML compatible device in WEB-INF/conf/clients.xreg -- Raphaël Luta - [EMAIL PROTECTED] Apache Jetspeed - Enterise Portal in Java http://portals.apache;org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Portlet state problem
Hi, We are seeing some pretty strange behavior with our JS1.5 portal. If a portlet is in a maximized state and you click on a link in the left nav bar before restoring the original portlet the only content that is shown is . This only occurs if the user tries to navigate away from a maximized portlet. Does anyone know of a fix or workaround for this. Thanks, Andrew - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: zip stream and content-type in portlet
Thank you Raphael. I will try that right away. Fred On Thu, 2004-08-05 at 23:09, Raphaël Luta wrote: Frédéric FACHINETTI wrote: Hello, I have a portlet that query a database and then display the resultset using some JSP's. Now, I want to retrieve the query results not in html format but in a zip file format ie when I submit the query in my portlet I then have the save as ... window and I'm able to retrieve the query results thru a zipped text file. I managed to do it in an old perl application by changing the content-type and by printing the result in a zip stream. But with java and Jetspeed, I have no idea if it's possible and how to proceed. Is there a content-type specific to each portlet ? Nope, HTTP only defines a content-type for a whole response. To do this within Jetspeed, you ned to define a new screen template for example: WEB-InF/conf/templates/vm|jsp/SendFile.vm: $data.Response.setContentType(application/octet-stream)$file create an action to set the file object in the context to the ZIP file you want to send in your portlet create a link to this screen like this: jetspeed-root/template/SendFile/action/MySendAction. This is standard Turbine stuff so you should probably check out the Turbine documentation and mailing-list for further examples of how to use the Turbine screen to send non-HTML output. -- Raphaël Luta - [EMAIL PROTECTED] Apache Jetspeed - Enterpise Portal in Java http://portals.apache.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] O.S.B Oceanienne de Services Bancaires BP 9178 Motu Uta 98715 Papeete Tahiti - Polynesie Francaise Site : http://www.osb.pf Tel : (689) 54 08 00 Fax : (689) 41 34 08 ** Ce message et toutes les pieces jointes (ci-apres le message) sont etablis a l'intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le detruire et d'en avertir immediatement l'expediteur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'Internet ne permettant pas d'assurer l'integrite de ce message, l'OSB decline toute responsabilite au titre de ce message, dans l'hypothese ou il aurait ete modifie ou infeste par un virus. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: After Maximize Protlet, buildNormalContext not Called
We are seeing this problem in JS 1.5, does anyone have a bug to reference? I did not see any open or closed issues resembling this post. Does anyone have a workaround. This is the issue ASturtz posted subject 'Portlet state problem' this afternoon. -Art - From: Dmitry Sklyut Subject: RE: After Maximize Protlet, buildNormalContext not Called Date: Thu, 12 Feb 2004 06:39:41 -0800 That is what I saw also. Handling of the js_peid is not consistent as well as handling of template. They just don't get reset correctly. This is still a problem in b4 and 1.4 final. Dmitry -Original Message- From: Boyd, David [mailto:[EMAIL PROTECTED] Sent: Thursday, February 12, 2004 9:36 AM To: 'Jetspeed Users List' Cc: Dmitry Sklyut Subject: RE: After Maximize Protlet, buildNormalContext not Called After further investigation, your comments make sense. There seems to be a bug in the way Jetspeed 1.4b3 handles a portlet when it is maximized, restored or minimized. After digging around and outputting rundata, saw that when you maximized a portlet, the js_peid is set to the portlet that is maximized. When you then select a link off of that page to go to a completely different psml, the Jetspeed:pane tag lib is called, it checks to see if the js_peid is set, if so, then it uses that value to look for a portlet in the psml file, if it is not set then it uses the name to locate the portlet. Since the psml does not have any portlets with that js_peid, we get the blank screen. The solution was to modify the MAXIMAZE, RESTORE and MINIMIZE classes along with the pane taglib class. Added a new key,value pair to the temp storage to control the behavior. This mailbox protected from junk email by Matador from MailFrontier, Inc. http://info.mailfrontier.com http://info.mailfrontier.com/ -Original Message- From: Dmitry Sklyut [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 10, 2004 5:42 PM To: 'Jetspeed Users List' Subject: RE: After Maximize Protlet, buildNormalContext not Called I saw that happen with forwards that forwarded to a pane. All works fine if forwarded to a portlet. I think it happens because rundata keeps the old js_peid and tries to render the portlet with that old js_peid. Dmitry -Original Message- From: Boyd, David [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 10, 2004 5:39 PM To: Jetspeed Users List Subject: After Maximize Protlet, buildNormalContext not Called I have a page where there are 2 columns of 5 rows of portals. If a user maximizes a given portlet, and then selects a link from that portlet, the user is taken to the correct page, as indicated by the URL, but no content is displayed except for the following /. If the user navigates back to the original page, selects the restore icon, then selects same link on the same portlet, the user is taken to the same page, but, now there is content. Any ideal as to why this occurs. _ This mailbox protected from junk email by Matador from MailFrontier, Inc. http://info.mailfrontier.com http://info.mailfrontier.com/ http://info.mailfrontier.com http://info.mailfrontier.com/
Build
I am new to jetspeed: I had jetspeed 2 installed. Installed jestspeed 1.5 and took the tutorial. Now when I try to build jetspeed 2 I get: BUILD FAILED File.. C:\IMICS\DevTools\jakarta-jetspeed-2\maven.xml Element... maven:reactor Line.. 318 Column 40 Unable to obtain goal [deploy-plugin] -- C:\IMICS\DevTools\jakarta-jetspeed-2\ma ven-plugin\maven.xml:54:43: attainGoal No goal [plugin:deploy] Total time: 3 minutes 49 seconds Finished at: Fri Aug 06 13:35:07 CDT 2004 Any ideas? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Why no frame-portlets?
Hello, why isn't it possible to put portlets into frames? I wouldn't have to reload the whole content over and over again. maybe you have a hint. thanks
RE: Build
Hi, I receive the exact same error. I referred to the issues in the Jetspeed 2 Tiki, and still no luck :( Thanks, Philip From: Call, Terry M [EMAIL PROTECTED] Reply-To: Jetspeed Users List [EMAIL PROTECTED] To: Jetspeed Users List [EMAIL PROTECTED] Subject: Build Date: Fri, 6 Aug 2004 14:22:05 -0500 I am new to jetspeed: I had jetspeed 2 installed. Installed jestspeed 1.5 and took the tutorial. Now when I try to build jetspeed 2 I get: BUILD FAILED File.. C:\IMICS\DevTools\jakarta-jetspeed-2\maven.xml Element... maven:reactor Line.. 318 Column 40 Unable to obtain goal [deploy-plugin] -- C:\IMICS\DevTools\jakarta-jetspeed-2\ma ven-plugin\maven.xml:54:43: attainGoal No goal [plugin:deploy] Total time: 3 minutes 49 seconds Finished at: Fri Aug 06 13:35:07 CDT 2004 Any ideas? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Build
Sorry, I was 6 out on the line number... I am having difficulties with the maven plug-in. Starting the reactor... Our processing order: Jetspeed 2 Maven Plugin + | Build and deploy the Jetspeed 2 Maven plugin Jetspeed 2 Maven Plugin | Memory: 36M/53M + BUILD FAILED File.. E:\jetspeed-2.0\jakarta-jetspeed-2\maven.xml Element... maven:reactor Line.. 324 Column 40 Unable to obtain goal [deploy-plugin] -- E:\jetspeed-2.0\jakarta-jetspeed-2\maven-plugin\maven.xml:5 4:43: attainGoal No goal [plugin:deploy] Total time: 4 minutes 28 seconds Finished at: Fri Aug 06 21:54:37 PDT 2004 Please, any help would be greatly appreciated. Thanks, Philip -Original Message- From: Philip Saville [mailto:[EMAIL PROTECTED] Sent: Friday, August 06, 2004 6:06 PM To: [EMAIL PROTECTED] Subject: RE: Build Hi, I receive the exact same error. I referred to the issues in the Jetspeed 2 Tiki, and still no luck :( Thanks, Philip From: Call, Terry M [EMAIL PROTECTED] Reply-To: Jetspeed Users List [EMAIL PROTECTED] To: Jetspeed Users List [EMAIL PROTECTED] Subject: Build Date: Fri, 6 Aug 2004 14:22:05 -0500 I am new to jetspeed: I had jetspeed 2 installed. Installed jestspeed 1.5 and took the tutorial. Now when I try to build jetspeed 2 I get: BUILD FAILED File.. C:\IMICS\DevTools\jakarta-jetspeed-2\maven.xml Element... maven:reactor Line.. 318 Column 40 Unable to obtain goal [deploy-plugin] -- C:\IMICS\DevTools\jakarta-jetspeed-2\ma ven-plugin\maven.xml:54:43: attainGoal No goal [plugin:deploy] Total time: 3 minutes 49 seconds Finished at: Fri Aug 06 13:35:07 CDT 2004 Any ideas? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
