Re: new Jetspeed version / 'Customize your page layout'
Johann Bertscheit wrote: Hi Jetspeed-fans, Hi burtonator, I have installed jetspeed (v 1.2b1) on winnt and have now the following questions: - when will the 'Customize your page layout' screen work again? snip As far as I understand the situation, Kevin could not really work on Jetspeed for the last two months so the customizer project is more or less stalled. I expect many things to be resolved during ApacheCon next week. - how to implement the 'Customize your page layout' functionality without GUI - directly in jetspeed/turbine? - in such a way, that two different users get shown two different sets of portlets, if they login into jetspeed Just define different PSML files for each user, use the org.apache.jetspeed.profiler.UserProfiler as your profiler and you'll be able to access your different files either: - by logging in as a specific user - by using the following URLs: http://myhost/servlet/jetspeed/user/myusername - how is it possible to activate/deactivate a portlet for some specific user(s)? you have 2 different PSML files so you can do whatever you want since your user is not currently able to add a portlet back. - how is it possible to access the logged user from a XSP page? (get the user-name and user-properties, as stored in the database/turbine) I'm not sure but I think so - when will be a new version of jetspeed released? Soon ;) -- Raphaël Luta - [EMAIL PROTECTED] -- -- Please read the FAQ! http://java.apache.org/faq/ To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: http://java.apache.org/main/mail.html Problems?: [EMAIL PROTECTED]
Jetspeed in the press
Hi there, I recently published an article about Jetspeed. Here is the link: http://www.pinnaclepublishing.com/JE/JEmag.nsf/0/CB3E5FA08B0947E785256961005802AC Send me your comments, suggestions. Best Regards, frederic lavigne, [EMAIL PROTECTED] -- -- Please read the FAQ! http://java.apache.org/faq/ To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: http://java.apache.org/main/mail.html Problems?: [EMAIL PROTECTED]
ACL's
ACL's in Jetspeed : I just tried to control the portlet through Jetspeed (like show / hide particular portlet in the portal) based on the ACL stuff. But I got failed because of the following strategies. If I am wrong in doings, please correct me and help me to resolve this issue.(atleast controlling one portlet) using ACL. As Mr. Kevin Burton is pointing out that Jetspeed can access and use ACL's which is in Turbine to control Jetspeed portal. But, as of my knowledge, the ACL's which we are using in Turbine is not sufficient for controlling our portlet. Turbine ACL's just control entire screen/portal not our individual portlet. It is not possibe to control access to a portlet or part of it through Turbine. If we have ACL's in jetspeed we can control our each and every portlet with in the screen/portal. For example, if we want to use Jetspeed in an intranet stuff like, think about a portlet which can show the salary of each employee. In this case we must have the ability to restrict the usage to people of the HR department. On the other hand it is not necessary to enable this restriction mechanism on the user level. In general we would restrict the access to a group of users (for example the members of the HR department). These users will be members of a specific role. As a result we should enable access to portlet functionality depending on their roles. Username may still need to be used in the access/denial specfication. Otherwise, how do you deny access to one user of the HR group, but allow access to all others? We cannot control this through Turbine ACL's. So we need seperate ACL's which should be in a position to control our individual portlet within portal/screen. With Regards, Anbunidhi Mahalingam. -- -- Please read the FAQ! http://java.apache.org/faq/ To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: http://java.apache.org/main/mail.html Problems?: [EMAIL PROTECTED]
RE: ACL's
There is a proposal for this in the cvs tree. -Original Message- From: Anbunidhi Mahalingam [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 19, 2000 4:46 AM To: [EMAIL PROTECTED] Subject: ACL's ACL's in Jetspeed : I just tried to control the portlet through Jetspeed (like show / hide particular portlet in the portal) based on the ACL stuff. But I got failed because of the following strategies. If I am wrong in doings, please correct me and help me to resolve this issue.(atleast controlling one portlet) using ACL. As Mr. Kevin Burton is pointing out that Jetspeed can access and use ACL's which is in Turbine to control Jetspeed portal. But, as of my knowledge, the ACL's which we are using in Turbine is not sufficient for controlling our portlet. Turbine ACL's just control entire screen/portal not our individual portlet. It is not possibe to control access to a portlet or part of it through Turbine. If we have ACL's in jetspeed we can control our each and every portlet with in the screen/portal. For example, if we want to use Jetspeed in an intranet stuff like, think about a portlet which can show the salary of each employee. In this case we must have the ability to restrict the usage to people of the HR department. On the other hand it is not necessary to enable this restriction mechanism on the user level. In general we would restrict the access to a group of users (for example the members of the HR department). These users will be members of a specific role. As a result we should enable access to portlet functionality depending on their roles. Username may still need to be used in the access/denial specfication. Otherwise, how do you deny access to one user of the HR group, but allow access to all others? We cannot control this through Turbine ACL's. So we need seperate ACL's which should be in a position to control our individual portlet within portal/screen. With Regards, Anbunidhi Mahalingam. -- -- Please read the FAQ! http://java.apache.org/faq/ To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: http://java.apache.org/main/mail.html Problems?: [EMAIL PROTECTED] --- This message has been scanned for viruses with Trend Micro's Interscan VirusWall. -- -- Please read the FAQ! http://java.apache.org/faq/ To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: http://java.apache.org/main/mail.html Problems?: [EMAIL PROTECTED]
Re: ACL's
Is there anyway around to do that with Turbine ACL's ??? - Original Message - From: "Brekke, Jeff" [EMAIL PROTECTED] To: "'JetSpeed'" [EMAIL PROTECTED] Sent: Thursday, October 19, 2000 1:21 PM Subject: RE: ACL's There is a proposal for this in the cvs tree. -Original Message- From: Anbunidhi Mahalingam [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 19, 2000 4:46 AM To: [EMAIL PROTECTED] Subject: ACL's ACL's in Jetspeed : I just tried to control the portlet through Jetspeed (like show / hide particular portlet in the portal) based on the ACL stuff. But I got failed because of the following strategies. If I am wrong in doings, please correct me and help me to resolve this issue.(atleast controlling one portlet) using ACL. As Mr. Kevin Burton is pointing out that Jetspeed can access and use ACL's which is in Turbine to control Jetspeed portal. But, as of my knowledge, the ACL's which we are using in Turbine is not sufficient for controlling our portlet. Turbine ACL's just control entire screen/portal not our individual portlet. It is not possibe to control access to a portlet or part of it through Turbine. If we have ACL's in jetspeed we can control our each and every portlet with in the screen/portal. For example, if we want to use Jetspeed in an intranet stuff like, think about a portlet which can show the salary of each employee. In this case we must have the ability to restrict the usage to people of the HR department. On the other hand it is not necessary to enable this restriction mechanism on the user level. In general we would restrict the access to a group of users (for example the members of the HR department). These users will be members of a specific role. As a result we should enable access to portlet functionality depending on their roles. Username may still need to be used in the access/denial specfication. Otherwise, how do you deny access to one user of the HR group, but allow access to all others? We cannot control this through Turbine ACL's. So we need seperate ACL's which should be in a position to control our individual portlet within portal/screen. With Regards, Anbunidhi Mahalingam. -- -- Please read the FAQ! http://java.apache.org/faq/ To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: http://java.apache.org/main/mail.html Problems?: [EMAIL PROTECTED] --- This message has been scanned for viruses with Trend Micro's Interscan VirusWall. -- -- Please read the FAQ! http://java.apache.org/faq/ To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: http://java.apache.org/main/mail.html Problems?: [EMAIL PROTECTED] -- -- Please read the FAQ! http://java.apache.org/faq/ To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: http://java.apache.org/main/mail.html Problems?: [EMAIL PROTECTED]
Yet another install manual...
Hi all, I wrote an install guide as well. However, mine is for installing Jetspeed with VisualAge (in the Websphere Test Environment) and DB2. I verified it with a CVS codedrop of beginning of September. I also fixed a bug in the DB2 SQL script, namely, changed the type of the VisitorID filed to auto-increment. Furthermore, I added a line to the default_roles_permissions.sql to have an additional role "authenticated_user" added (This role seems to be needed for "normal" users). Unfortunately, the list server doesn't allow to enclose files - even if they are plain text only. I'll therefore paste all files at the bottom of this mail. If there are any questions - ask them! Hope I didn't do a mistake at the pasting down there... ingo. Install Guide: Jetspeed_VisualAge_Setup.html --snip-snap- !doctype html public "-//w3c//dtd html 4.0 transitional//en" html head meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" meta name="Author" content="ingo" meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]" titleInstalling Jetspeed with VisualAge and DB2/title /head body h3 uInstalling Jetspeed with Visual Age (3.5) and DB2 (7.1)/u/h3 Ingo Schuster ([EMAIL PROTECTED]) brnbsp; pThis guide applies to the CVS versoins of Jetspeed and Turbine as of 2000-09-04. pIn the following, tt[WTE]/tt stands for the "IBM Websphere Test Environment" directory in your VisualAge directory tree, bre.g: ttd:\visual age\ide\project_resources\websphere test environment\, [jetspeed]/tt stands for the "jetspeed" directory, tt[turbine]/tt for the "turbine" directory that has been checked out from the CVS. brTogether with this guide come a zip file which contains all the config files that need to be adapted. The settings in these example files assume that VisualAge has been installed to ttd:\apps\VisualAge for Java/tt brnbsp; h4 Installation steps:/h4 0.a) Install DB2, Visual Age ;-) brnbsp;nbsp;nbsp;nbsp;nbsp;nbsp; (Make sure your DB2 is configured to use jdbc 2.0 - this is done by executing the ttusejdbc2.bat/tt) brnbsp;nbsp;nbsp;nbsp;nbsp;nbsp; (iuDont't/u/i install the VAJ Tomcat Extension - brnbsp;nbsp;nbsp;nbsp;nbsp;nbsp; the Websphere Test Environment won't run together with it and it's hard to uninstall it later.) br0.b) Install the VisualAge Websphere Test Environment: blockquotepress ttF2/tt brselecttt Features|Add Feature/tt, press ttOK/tt brselecttt IBM Webshere Test Environment/tt, press ttOK/tt/blockquote 0.c) Make sure, that outgoing internet connections don't need to use a proxy (e.g. with a SOCKS Client) br0.d) Create an extra "portal" user account for your system (restricted user) for installing and running jetspeed. The reason for this is that for the database authentication, the users password needs be written into a property file as plain text. Jetspeed can be installed and ran under a different user id and still access the database tables as the (restricted) "portal" user, however in this case aliases to all tables need to be added to the database. p1. Create following Directories: blockquotett[WTE]\hosts\Jetspeed_host/tt brtt[WTE]\hosts\Jetspeed_host\logs/tt brtt[WTE]\hosts\Jetspeed_host\Jetspeeed_Application\lib/tt brtt[WTE]\hosts\Jetspeed_host\Jetspeeed_Application\cache/tt brtt[WTE]\hosts\Jetspeed_host\Jetspeeed_Application\tmp/tt brtt[WTE]\hosts\Jetspeed_host\Jetspeeed_Application\xsp.repository/tt brtt[WTE]\hosts\Jetspeed_host\Jetspeeed_Application\doc_root/tt brtt[WTE]\hosts\Jetspeed_host\Jetspeeed_Application\doc_root\config/tt brtt[WTE]\hosts\Jetspeed_host\Jetspeeed_Application\doc_root\content/tt brtt[WTE]\hosts\Jetspeed_host\Jetspeeed_Application\doc_root\WEB_INF\templates/tt/blockquote pbr2. Create following projects within the VisualAge workspace: blockquotettPortal_Turbine/tt brttPortal_Jetspeed/tt brttPortal_Jars/tt/blockquote pbr3. Import the source files (tt.java/tt and resources): blockquotett[turbine\src\java]/tt into ttPortal_Turbine/tt brtt[jetspeed\src\java]/tt into ttPortal_Jetspeed/tt/blockquote pbr4. Import following jar files into ttPortal_Jars /tt(in the given order!!). Some jars will contain classes that are already present in the Workspace, always overwrite the "old" classes with the new ones. It is ok, that these callses are imported into existing packages. blockquote1. From tt[jetspeed\lib]/tt directory: brttnbsp;nbsp; cocoon.jar, cocoon-ext-servlet2.2jar, hsql.jar, jyve-2.0.jar, mail.jar/tt br2.nbsp; From tt[turbine\lib] /ttdirectory: brttnbsp;nbsp; activation-1.0.1.jar, ecs-1.3.3.jar, freemarker-jdk1.2.jar, village-1.3.jar,/tt brttnbsp;nbsp; webmacro-jdk1.2-27-08-2000.jar, xmlrpc.jar/tt br3. From tt[jetspeed\lib]/ttdirectory: brttnbsp;nbsp; /tt3a) ttjaxp.jar,/tt brttnbsp;nbsp; /tt3b) ttcastor.jar,/tt br4.nbsp; From tt[turbine\lib]/tt directory: brttnbsp;nbsp; 4/tta) ttxalan_1_1_D01.jar,/tt brttnbsp;nbsp; 4b/tt) ttxerces-1.1.3.jar,/tt br5.
Re: Changes in pre-proposal-0003-no-psml branch
"Thomas F. Boehme" wrote: Santiago, Thank you for the mods. They were eagerly awaited! Is it still the plan to have a proposal 0003 release ready for ApacheCON? Would that be before, during, or after the conference? Given timing, I don't know. I have not looked at the HEAD branch. I wanted to know from Kevin first. I will be in ApacheCON. That means that, if we have machines, connections, beers, pizzas, time, etc... we could be able to merge there. I think Raphael, Neeme, Kevin, ... will also be there. In any case, it should be available shortly after, when we discuss and sort out problems there. Cheers, Thomas - Original Message - From: "Santiago Gala" [EMAIL PROTECTED] To: "JetSpeed" [EMAIL PROTECTED] Sent: Monday, October 16, 2000 17:06 Subject: Changes in "pre-proposal-0003-no-psml" branch I had to rewind changes done earlier this morning by Raphael Luta. The reason is that I had already tested under my local copy CVS turbine, and there is a problem in authentication. The situation is: removed Jyve from CVS. Screens taken from Jyve now come from packages org.apache.jetspeed.turbine.localization, org.apache.jetspeed.turbine.screens and org.apache.jetspeed.turbine.actions I have just modified minimum stuff to make them run. A lot of things there belong really to Jyve. Somebody who knows turbine better than I should edit them and trim them for Jetspeed. Changed the drawing algorithm to propagate rundata. This implied changes in a lot of places. Main things that I remember: -- Daemons no longer have a rundata in init. They should not cache rundata information. This gets propagated. -- Portlets no longer get a rundata in init. The same reason. They, nevertheless, get a RunData in every getContent call. I changed the things that are cached in init. If you want to look at changes, there are examples in the whole set of Admin portlets. I added a TurbineScreenPortlet, donated by Jeff Brekke to the project. In jetspeed-config.jcfg there is an example of use, where admin portlets are shown in a portlet. A useful example would be to do the same for login screen in default.psml. Things missing: Update turbine: There are about ten files with comments like file://For new Turbine This files are what is needed to have jetspeed running under turbine cvs as of today. Nevertheless authentication does not work. I think turbine people will be changing this area next week. I would wait, or solve problems in private copies before commit. JetspeedContent: The new version assumes HTTP PUT to update jetspeed-content. There is an inner class in JetspeedDiskCacheEntry.java that will return a Writer to save the file to it. I will try to have a version that will do that using filesystem mapping and put configurable election of method in JetspeedResources.properties. I'll try to have it later or tomorrow, but don't trust much on me on that, as I travel tomorrow. You can try to write it yourselves, it should be simple. The problem is that file system mapping is very tricky, as it is not consistent accross VMs, Operating Systems, Servlet Containers, etc.. If some of you try things, check changes needed in configuration files before complaining. There are updates in quite a few of those. :-) Regards, Santiago P.S.) I hope we can have it in good shape for next week ApacheCON. -- -- Please read the FAQ! http://java.apache.org/faq/ To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: http://java.apache.org/main/mail.html Problems?: [EMAIL PROTECTED] -- -- Please read the FAQ! http://java.apache.org/faq/ To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: http://java.apache.org/main/mail.html Problems?: [EMAIL PROTECTED] -- -- Please read the FAQ! http://java.apache.org/faq/ To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: http://java.apache.org/main/mail.html Problems?: [EMAIL PROTECTED]
RE: ACL's
The proposal hasn't been implemented yet. Changes to PSML must take place. Currently there is no way to control portlet display at the layout level. If you are writing your own portlets, you could check the users name or group in the portlet itself and choose to display the content or a message or something. -Original Message- From: Anbunidhi Mahalingam [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 19, 2000 6:34 AM To: JetSpeed Subject: Re: ACL's Is there anyway around to do that with Turbine ACL's ??? - Original Message - From: "Brekke, Jeff" [EMAIL PROTECTED] To: "'JetSpeed'" [EMAIL PROTECTED] Sent: Thursday, October 19, 2000 1:21 PM Subject: RE: ACL's There is a proposal for this in the cvs tree. -Original Message- From: Anbunidhi Mahalingam [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 19, 2000 4:46 AM To: [EMAIL PROTECTED] Subject: ACL's ACL's in Jetspeed : I just tried to control the portlet through Jetspeed (like show / hide particular portlet in the portal) based on the ACL stuff. But I got failed because of the following strategies. If I am wrong in doings, please correct me and help me to resolve this issue.(atleast controlling one portlet) using ACL. As Mr. Kevin Burton is pointing out that Jetspeed can access and use ACL's which is in Turbine to control Jetspeed portal. But, as of my knowledge, the ACL's which we are using in Turbine is not sufficient for controlling our portlet. Turbine ACL's just control entire screen/portal not our individual portlet. It is not possibe to control access to a portlet or part of it through Turbine. If we have ACL's in jetspeed we can control our each and every portlet with in the screen/portal. For example, if we want to use Jetspeed in an intranet stuff like, think about a portlet which can show the salary of each employee. In this case we must have the ability to restrict the usage to people of the HR department. On the other hand it is not necessary to enable this restriction mechanism on the user level. In general we would restrict the access to a group of users (for example the members of the HR department). These users will be members of a specific role. As a result we should enable access to portlet functionality depending on their roles. Username may still need to be used in the access/denial specfication. Otherwise, how do you deny access to one user of the HR group, but allow access to all others? We cannot control this through Turbine ACL's. So we need seperate ACL's which should be in a position to control our individual portlet within portal/screen. With Regards, Anbunidhi Mahalingam. -- -- Please read the FAQ! http://java.apache.org/faq/ To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: http://java.apache.org/main/mail.html Problems?: [EMAIL PROTECTED] -- - This message has been scanned for viruses with Trend Micro's Interscan VirusWall. -- -- Please read the FAQ! http://java.apache.org/faq/ To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: http://java.apache.org/main/mail.html Problems?: [EMAIL PROTECTED] -- -- Please read the FAQ! http://java.apache.org/faq/ To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: http://java.apache.org/main/mail.html Problems?: [EMAIL PROTECTED] --- This message has been scanned for viruses with Trend Micro's Interscan VirusWall. -- -- Please read the FAQ! http://java.apache.org/faq/ To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: http://java.apache.org/main/mail.html Problems?: [EMAIL PROTECTED]
RE: ACL's
Yes, you are correct. I was lumping the portletregistry ( or .jcfg ) under 'PSML' umbrella. During customization the user would only see content they have access to. Individual and default user's psml would not hold information about security, the portlet registry does. It's all in the proposal-004, sorry for the confusion. This proposal will need to be updated when the security refactoring is completed in Turbine ( supposedly very soon ). FYI: I noticed that this proposal (004) is checked into the head, not the branch that compiles. You can view it with cvsweb. http://www.working-dogs.com/jetspeed/cvsweb/index.cgi/jetspeed/docs/proposal s/0004.txt?rev=1.2content-type=text/x-cvsweb-markup -Original Message- From: Thomas F. Boehme [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 19, 2000 8:15 AM To: JetSpeed Subject: Re: ACL's Jeff, I can't see the need to change the PSML structure. A user should see whatever is defined in his/her PSML file. Really, the control mechanism should be in place at the customization level. That is, a user who is not authorized to see certain content should not have the option of choosing that portlet for viewing in his/her page. Therefore, I would place the the authorization at content (-- jetspeed-config.jcfg or similar) rather than the layout. What do you think?` Thomas - Original Message - From: "Brekke, Jeff" [EMAIL PROTECTED] To: "'JetSpeed'" [EMAIL PROTECTED] Sent: Thursday, October 19, 2000 14:20 Subject: RE: ACL's The proposal hasn't been implemented yet. Changes to PSML must take place. Currently there is no way to control portlet display at the layout level. If you are writing your own portlets, you could check the users name or group in the portlet itself and choose to display the content or a message or something. -Original Message- From: Anbunidhi Mahalingam [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 19, 2000 6:34 AM To: JetSpeed Subject: Re: ACL's Is there anyway around to do that with Turbine ACL's ??? - Original Message - From: "Brekke, Jeff" [EMAIL PROTECTED] To: "'JetSpeed'" [EMAIL PROTECTED] Sent: Thursday, October 19, 2000 1:21 PM Subject: RE: ACL's There is a proposal for this in the cvs tree. -Original Message- From: Anbunidhi Mahalingam [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 19, 2000 4:46 AM To: [EMAIL PROTECTED] Subject: ACL's ACL's in Jetspeed : I just tried to control the portlet through Jetspeed (like show / hide particular portlet in the portal) based on the ACL stuff. But I got failed because of the following strategies. If I am wrong in doings, please correct me and help me to resolve this issue.(atleast controlling one portlet) using ACL. As Mr. Kevin Burton is pointing out that Jetspeed can access and use ACL's which is in Turbine to control Jetspeed portal. But, as of my knowledge, the ACL's which we are using in Turbine is not sufficient for controlling our portlet. Turbine ACL's just control entire screen/portal not our individual portlet. It is not possibe to control access to a portlet or part of it through Turbine. If we have ACL's in jetspeed we can control our each and every portlet with in the screen/portal. For example, if we want to use Jetspeed in an intranet stuff like, think about a portlet which can show the salary of each employee. In this case we must have the ability to restrict the usage to people of the HR department. On the other hand it is not necessary to enable this restriction mechanism on the user level. In general we would restrict the access to a group of users (for example the members of the HR department). These users will be members of a specific role. As a result we should enable access to portlet functionality depending on their roles. Username may still need to be used in the access/denial specfication. Otherwise, how do you deny access to one user of the HR group, but allow access to all others? We cannot control this through Turbine ACL's. So we need seperate ACL's which should be in a position to control our individual portlet within portal/screen. With Regards, Anbunidhi Mahalingam. -- -- Please read the FAQ! http://java.apache.org/faq/ To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: http://java.apache.org/main/mail.html Problems?: [EMAIL PROTECTED]
RE: ACL's
Thanks for the info. What branch currently compiles? Does it compile against the newer Turbine with User package and class name changes? -Original Message- From: Brekke, Jeff [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 19, 2000 10:08 AM To: 'JetSpeed' Subject: RE: ACL's [snip] FYI: I noticed that this proposal (004) is checked into the head, not the branch that compiles. You can view it with cvsweb. http://www.working-dogs.com/jetspeed/cvsweb/index.cgi/jetspeed/docs/proposal s/0004.txt?rev=1.2content-type=text/x-cvsweb-markup -- -- Please read the FAQ! http://java.apache.org/faq/ To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: http://java.apache.org/main/mail.html Problems?: [EMAIL PROTECTED]
Re: ACL's
It's "pre-proposal-0003-no-psml". As Santiago reported correctly, it compiles but does not run with the latest version of Turbine. Use the one in the lib directory of Jetspeed. Also, if things don't seem to work, try using Village 1.4 instead of Village 1.3. Thomas - Original Message - From: "Santiago Gala" [EMAIL PROTECTED] To: "JetSpeed" [EMAIL PROTECTED] Sent: Thursday, October 19, 2000 19:30 Subject: Re: ACL's Craig Berry wrote: Thanks for the info. What branch currently compiles? Does it compile against the newer Turbine pre-proposal-003-nopsml (or something similar) with User package and class name changes? No. I have in my HD a version with compiles against cvs turbine as of yesterday, but authentication did not work. I could not find why in the time I had, so I preferred to leave turbine changes out, as changes are rather small, until they finish the new authentication code. In some mail in the turbine list, Rafal told this will happen next week. After that, we will merge this branch with new turbine code, and hopefully HEAD branch. I think imported package changes, and code changes, are commited as comments with a file://For new Turbine tag (sometimes upper, sometimes lower case, to make it more interesting... ;-) ). I'm not completely sure that these will work, though, when they change the turbine next week. I don't know turbine that much. -Original Message- From: Brekke, Jeff [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 19, 2000 10:08 AM To: 'JetSpeed' Subject: RE: ACL's [snip] FYI: I noticed that this proposal (004) is checked into the head, not the branch that compiles. You can view it with cvsweb. http://www.working-dogs.com/jetspeed/cvsweb/index.cgi/jetspeed/docs/proposal s/0004.txt?rev=1.2content-type=text/x-cvsweb-markup -- -- Please read the FAQ! http://java.apache.org/faq/ To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: http://java.apache.org/main/mail.html Problems?: [EMAIL PROTECTED] -- -- Please read the FAQ! http://java.apache.org/faq/ To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: http://java.apache.org/main/mail.html Problems?: [EMAIL PROTECTED] -- -- Please read the FAQ! http://java.apache.org/faq/ To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: http://java.apache.org/main/mail.html Problems?: [EMAIL PROTECTED]
