Menu
▾
▴
aplaws-devel — Developer Mailing List. Forum postings are forwarded to this list.
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(10) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
|
Feb
(13) |
Mar
(15) |
Apr
(29) |
May
(28) |
Jun
(111) |
Jul
(185) |
Aug
(366) |
Sep
(121) |
Oct
(73) |
Nov
(57) |
Dec
(23) |
| 2005 |
Jan
(30) |
Feb
(49) |
Mar
(51) |
Apr
(47) |
May
(95) |
Jun
(74) |
Jul
(62) |
Aug
(61) |
Sep
(46) |
Oct
(73) |
Nov
(111) |
Dec
(59) |
| 2006 |
Jan
(114) |
Feb
(34) |
Mar
(47) |
Apr
(49) |
May
(106) |
Jun
(47) |
Jul
(78) |
Aug
(31) |
Sep
(35) |
Oct
(39) |
Nov
(63) |
Dec
(17) |
| 2007 |
Jan
(40) |
Feb
(32) |
Mar
(17) |
Apr
(15) |
May
(28) |
Jun
(20) |
Jul
(80) |
Aug
(83) |
Sep
(52) |
Oct
(26) |
Nov
(6) |
Dec
(9) |
| 2008 |
Jan
(22) |
Feb
(11) |
Mar
(45) |
Apr
(5) |
May
(8) |
Jun
|
Jul
(16) |
Aug
(5) |
Sep
(3) |
Oct
(4) |
Nov
(14) |
Dec
(3) |
| 2009 |
Jan
(25) |
Feb
(46) |
Mar
(17) |
Apr
(8) |
May
(74) |
Jun
(48) |
Jul
(11) |
Aug
(9) |
Sep
|
Oct
|
Nov
(2) |
Dec
(2) |
|
From: Aplaws D. L. <apl...@li...> - 2009-05-24 10:26:00
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7407146 By: terry_permeance Great. I might have asked this before but can someone please explain the versioning system: project.xml: @ccmVersion = 6.1 @version = 1-0-5 @release = alpha-1 */application.xml @version = 6.6.0 @release = 1 Thanks, Terry ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=368401 |
|
From: Aplaws D. L. <apl...@li...> - 2009-05-24 09:49:03
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7407125 By: pboy >From the commit log: Bump trunk version to 6.6 This development cycle aims at: - standard compliant runtime environment (milestone 1) - a new standard development environment (milestone 2) - a new user installation & maintenance tool (milestone 3) - eventually a new standard theme (Mandalay) It is planned to create a stable release July / August (Years details not determined yet :-) ) With this version jump we enter a period of instability and changes. Developers are advised to keep 2 versions of trunk: HEAD and HEAD-5 to ensure they (hopefully) have always a working sample at hand! For the present the following changes are fixed: - the previous runtime system will not work anymore - all the CCM environment variables but CCM_HOME are not used anymore - CCM_HOME is used during installation only and points to the application directory (application context), NOT to the servlet container as previously! - the ccm scripts are no longer supported and don't work anymore - this includes the ccm based development environment! - ECDC is the new development environment so far (will be complemented by Maven) - modules in the contrib tree will not work out of the box but have to be adopted - there is no user installation tool available at the moment. If a user installation is needed manual adoptions are requirred. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=368401 |
|
From: Aplaws D. L. <apl...@li...> - 2009-05-22 10:30:26
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7404347 By: bprucha > I will start to make APLAWS installable in any arbitrary directory, specified in project.xml webapp tag or during installation time. This involves a massive rewriting of xsl files and a lot of work in web.xml and the dispatcher magic and may take some time. Peter, I have already done work to get APLAWS to run under a context other than root. It does not require a massive rewrite of xsl files. The xsl files get loaded through the templating system which will look for the xsl files under the context defined with the web.context (from memory) registry configuration setting. I can help you with the changes that do need to be made. Their aren't that many as far as getting it to run is concerned. I'm going to be away for several days but can provide a path when I get back. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=368401 |
|
From: Aplaws D. L. <apl...@li...> - 2009-05-22 09:56:15
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7404301 By: pboy OK, but it is the better name so we should keep it. Peter ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=368401 |
|
From: Aplaws D. L. <apl...@li...> - 2009-05-22 09:45:26
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7404291 By: terry_permeance Oh yes, load-bundle-config is redundant. Sorry! Terry ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=368401 |
|
From: Aplaws D. L. <apl...@li...> - 2009-05-22 08:56:35
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7404227 By: pboy Yes, but isn't load-init just doing that? Currently I don't see a difference between load-bundle-config and load-init ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=368401 |
|
From: Aplaws D. L. <apl...@li...> - 2009-05-22 08:51:53
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7404219 By: pboy 'Hm, seems to be another example where my svn didn't work. I will have a look into it. But can we agree about the underlying rationale? Peter ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=368401 |
|
From: Aplaws D. L. <apl...@li...> - 2009-05-22 08:50:20
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7404215 By: pboy What a pitty, I was glad having found someone who may be able to provide some information :-) Is that module for apach 1 only? Or do you have some knowledge about the module anyway you could share? Peter ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=368401 |
|
From: Aplaws D. L. <apl...@li...> - 2009-05-22 08:46:33
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7404208 By: terry_permeance load-bundle-config is equivalent to load-bundle --config ... Because "ant clean" deletes the configuration, it is necessary to reload just the configuration. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=368401 |
|
From: Aplaws D. L. <apl...@li...> - 2009-05-22 08:41:44
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7404197 By: pboy Hi Terry, yes, ecdc will become the new standard. In the future maven should become an alternative. I already started to work on it. The current trunk policy rules that trunk is just a container for packages / directories, no logik in root. Having at least a build.xml in trunk which provides a "prepare" task would make starting development a lot easier. So we should reconsider the policy. About the current planing for the future as of discussion of TSC group: We are planing an APLAWS 1.x.y release (perhaps 1.5.0) at July / August with the milestones (1) (2) (3) finished. So it will be the first release of a "new" APLAWS, running in a standard servlet container At the end of the year we are planing another 1.x.z release which aims at a massive clean-up of the code base as a ground for future development. I suppose Francois will publish the minutes of the meeting soon. Peter ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=368401 |
|
From: Aplaws D. L. <apl...@li...> - 2009-05-22 08:17:21
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7404152 By: pboy Hi Terry, isn't the load-bundle-config the same as the previous load-init? (but a better name in a systematic perspectivce). Or what is the difference between both? Peter ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=368401 |
|
From: Aplaws D. L. <apl...@li...> - 2009-05-22 08:16:10
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7404150 By: terry_permeance ant start worked ant load-bundle put the configuration under webapps/ROOT/webapps/ROOT/WEB-INF/conf ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=368401 |
|
From: Aplaws D. L. <apl...@li...> - 2009-05-22 08:12:05
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7404141 By: pboy Hi Terry, I suppose your patch will break a lot of modifications I made to the java code. The rationale of milestone (1) is that all references to files, resources and anything else in APLAWS is strictly made relative to document root rsp. the web application context All modifications / configurations regarding the servlet container and where to install APLAWS (in which context) are the responsibility of the container / the container administrator / the container's webapp installation tool. Nothing at all that APLAWS should care about. In some situations we need the full file system path to a file or resource (esp. during installation / initial configuration and while using the test machinery I suppose), and we need the path to the APLAWS web context. That is ccm.home in the logik of milestone (1). Currently ccm.home is fixed ${app.server.webapp.dir}/ROOT. As soon as I've finished the work on the URL resource: protocol (I suppose I will provide a patch today in the evening) I will start to make APLAWS installable in any arbitrary directory, specified in project.xml webapp tag or during installation time. This involves a massive rewriting of xsl files and a lot of work in web.xml and the dispatcher magic and may take some time. So ccm.home will become: ${app.server.webapp.dir}/${ccm:project.webapp} See milestone (1) and related tickets for details. Well, I suppose I should start to write a new developer guide as soon as possible. In which situations do we need ccm.home pointing to the servlet containers home dir? Peter ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=368401 |
|
From: Aplaws D. L. <apl...@li...> - 2009-05-22 07:53:57
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7404107 By: terry_permeance Hi Peter, No we use apache2. But I was concerned that two jdk13-based jars are being deployed to the system and may have unexpected side effects. Terry ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=368401 |
|
From: Aplaws D. L. <apl...@li...> - 2009-05-22 07:47:53
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7404093 By: pboy Terry, I just saw your patch and conclude that you use that module or at least how to use it. I'm struggeling with that module for years now. Please, please could you add some documentation at https://fedorahosted.org/aplaws/wiki/AdminPackagesAuthHttp I created a template proposal how to describe the APLAWS modules and started a list pf APLAWS packages ( https://fedorahosted.org/aplaws/wiki/AdminPackageList ) ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=368401 |
|
From: Aplaws D. L. <apl...@li...> - 2009-05-22 06:47:03
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7404008 By: terry_permeance Hi Peter, I think it's now pretty smooth. Not too many manual steps remaining! Now that 1.0.5 is "out of the way", do you plan to make ecdc the standard and move tools-ng\ecdc\build.xml and *.properties into the root folder? Regards, Terry ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=368401 |
|
From: Aplaws D. L. <apl...@li...> - 2009-05-22 06:14:57
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7403971 By: pboy Fine, I wondered about your problem because it works fine here for a long time (svnkit-1.2.3 on fedora workstation). Peter ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=368401 |
|
From: Aplaws D. L. <apl...@li...> - 2009-05-22 06:09:03
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7403965 By: pboy It is an implementation of the Linux rpm machinery for Sun Solaris. Years back is was needed by Camden (and may be others), which used to run APLAWS on Sun machines, to enable the rpm based APLAWS distribution and configuration during the rpm installation step. I don't know it someone still uses Solaris and I'm not shure, if Sun now delivers a rpm compatibility kit natively (as does IBM for AIX). Nevertheless, as soon as we abandon the ccm script system an the rpm based installation, it is nolonger needed anyway. Over the next days I will bump the CCM version number.Then we should make the tools directory outdated. We should use it as a kind of "stone quarry" for the development of the user installation & maintenance tools, but delete those parts we definitely no longer use. Peter ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=368401 |
|
From: Aplaws D. L. <apl...@li...> - 2009-05-22 02:07:41
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7403793 By: terry_permeance tools\rpms\solaris-linux-compat\package\rpm-4.0.4-dc2-sol8-sparc-local.gz What is this file for? It is 14MB in size. Terry ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=368401 |
|
From: Aplaws D. L. <apl...@li...> - 2009-05-22 01:54:06
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7403778 By: terry_permeance I upgraded my SVNKit from 1.2.2 to 1.3.0 and the speed of fedora increased massively! Regards, Terry ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=368401 |
|
From: Aplaws D. L. <apl...@li...> - 2009-05-21 09:55:02
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7402532 By: pboy Some remarks about the current state and the problems which came up yesterday. a) The URL resource: protocol extension is still in use. I had the same idea as Brett how to eliminate it (using ResourceProtocol), but overlooked the unsuficient implementation of AbstractParameter providing the default value which resulted in a casting error. Thanks to Brett's patch the problem is resolved now. I'll provide a patch over the weekend which replaces the URL resource extension in all trunk modules. In the meantime the solution suggested in ~/tools-ng/ecdc/README.txt should be used (copying the ccm-core-system-x.y.z.jar into $JAVA_HOME/jre/lib/ext). Many thanks to Brett for providing the patch! b) Validation error regarding project.xml There was an entry in the example file project.xml.complete which ponited to a wrong location. (~/tools/devel/... instead of ~/tools-ng/common/xsd/...). It is corrected thanks to Terry. Developers who have their own project.xml in place have to adjust it: In ccm:project - modify the scheme file location: tag xsi:schemaLocation= ... - add webapp=ROOT - optional: add prettyName - optional: provide version and release (osed in war file generation) c) Load-bundle information ECDC is meant to require minimal steps in the development cycle to be entered over and over again. Therefore all information required in the load-bundle step is taken from a bundle file. In contrast to the well known "ccm load-bundle" command there is no interactive mechanism to enter required information for database connection and administrator name and password. The example local.ccm.properties points to ~/ccm-ldn-aplaws/bundles/devel where all those informations are included in .../cfg/integration.properties (at the end of the file). It is best practice to create one's one bundle file, e.g. myAuth, and maintain a devel version, which includes those information, e.g. myAuth-devel, and a production version, which duplicates all the files of the devel version leaving off the database connection and administration information for security reasons, e.g. myAuth-prod. The latter is useless at the moment because we don't have a user installation procedure yet, but will be used when we have one (see milestone (3) on fedorahosted trac). Hope this helps. Peter ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=368401 |
|
From: Aplaws D. L. <apl...@li...> - 2009-05-20 12:28:51
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7400992 By: bprucha I ran into this problem when using JBoss. Because JBoss uses it's own resource handler I couldn't just add the ccm-core-system jar. I will submit the patches to SourceForge Patch Tracker. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=368401 |
|
From: Aplaws D. L. <apl...@li...> - 2009-05-20 11:42:13
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7400924 By: pboy Chandra, | xsi:schemaLocation="http://ccm.redhat.com/ccm-project file:tools/devel/xsd/project.xsd">.. It is the wrong scheme file, use: file:tools-ng/devel/xsd/project.xsd ^^^^ | Regarding issue resources protocol i am also getting error as terry | mentioned in this thread, when i start my server " ant start". see previous post or ~/tools-ng/ecdc/README.txt | Another thing.. using E C D C development process when i start | "ant load-bundle " it is unable to find the WAF jdbc URL.. i manually created | ccm/core/runtime.properties file under /runtime/apache-tomcat.x.x/ \ | webapps/ROOT/WEB-INF/conf/registry... | then load-bundle populdated the metedata but still it has not asked adminitrator | user name and password. so i daubt how i will login in content-center.. You should add this information to ~/ccm-ldn-aplaws/<yourbundle>/cfg/integration.properties and load-bundle will automatically pick it up and create all necessary entries in the registry. See ~/ccm-ldn-aplaws/bundles/devel/cfg/integration.properties, line 38 - 43 as an example. | I know it would be too much i am asking here but things looks bit not easy | for me..Is it same experince with other cummunity user well or it is just me | It's perfectly OK. I hope, we will get the beast up and running and have a pleasant development future :-) Cheers Peter ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=368401 |
|
From: Aplaws D. L. <apl...@li...> - 2009-05-20 11:31:33
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7400908 By: pboy | With ecdc, I get validation errors with project.xml: | ... | These are easily fixed but I assume we want to commit a permanent change? Seems to be just another example where my svn does not transfer all modifications for some reason. I see, you provided a fix. I'll check later today, what happened with my system. Unfortunately, I've a meeting now. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=368401 |
|
From: Aplaws D. L. <apl...@li...> - 2009-05-20 11:27:06
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7400899 By: pboy Terry: | Do you plan to commit these changes? Do you need help to make the changes? Help greatly appreciated. I'll send you a description of the problems I'm working on bia mail later today. Peter ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=368401 |
7 messages has been excluded from this view by a project administrator.
