Index: openacs-4/packages/b-responsive-theme/www/blank-master.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/b-responsive-theme/www/blank-master.tcl,v diff -u -N -r1.1 -r1.2 --- openacs-4/packages/b-responsive-theme/www/blank-master.tcl 8 Apr 2015 08:46:49 -0000 1.1 +++ openacs-4/packages/b-responsive-theme/www/blank-master.tcl 12 Apr 2018 07:47:22 -0000 1.2 @@ -175,8 +175,8 @@ set tinymce_elements [list] foreach htmlarea_id [lsort -unique $::acs_blank_master__htmlareas] { lappend tinymce_elements $htmlarea_id - } - set tinymce_config $::acs_blank_master(tinymce.config) + } + set tinymce_config $::acs_blank_master(tinymce.config) # Figure out the language to use # 1st is the user language, if not available then the system one, @@ -192,7 +192,7 @@ } } - # TODO : each element should have it's own init + # TODO : each element should have its own init template::head::add_javascript -script " tinyMCE.init(\{language: \"$tinymce_lang\", $tinymce_config\}); " -order tinymceZ Index: openacs-4/packages/bookmarks/www/index.vuh =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/bookmarks/www/index.vuh,v diff -u -N -r1.4 -r1.5 --- openacs-4/packages/bookmarks/www/index.vuh 18 Apr 2014 06:41:09 -0000 1.4 +++ openacs-4/packages/bookmarks/www/index.vuh 12 Apr 2018 07:47:22 -0000 1.5 @@ -1,6 +1,6 @@ # # Outputs an html file in the format used by netscape/mozilla -# for it's bookmarks menu +# for its bookmarks menu # # index.vuh created from the original registered proc @@ -33,7 +33,7 @@ if {$folder_list eq "0"} { lappend folder_list $parent_id } else { - set previous_parent_id [lindex $folder_list end] + set previous_parent_id [lindex $folder_list end] if {$parent_id != $previous_parent_id} { set parent_location [lsearch -exact $folder_list $parent_id] @@ -82,5 +82,5 @@

" - + doc_return 200 text/html $html Index: openacs-4/packages/bulk-mail/tcl/bulk-mail-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/bulk-mail/tcl/bulk-mail-procs.tcl,v diff -u -N -r1.15 -r1.16 --- openacs-4/packages/bulk-mail/tcl/bulk-mail-procs.tcl 29 Mar 2018 17:28:50 -0000 1.15 +++ openacs-4/packages/bulk-mail/tcl/bulk-mail-procs.tcl 12 Apr 2018 07:47:22 -0000 1.16 @@ -108,11 +108,11 @@ @param message the body of the email, can be overridden by a value selected in the query. will be interpolated with values from the query. - @param message_type - "text" or "html" (added by mohan) + @param message_type - "text" or "html" (added by mohan) @param query a query that must select the email address to send to as 'email' and can select any other values that will be interpolated into the subject and message of the bulk_mail for - each recipient. if column 'foo' is selected it's value + each recipient. if column 'foo' is selected its value will be interpolated anywhere that '{foo}' appears in the subject or message of the bulk_mail. if columns 'from_addr', 'reply_to', 'subject', or 'message' are selected, their Index: openacs-4/packages/email-handler/doc/index.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/email-handler/doc/index.html,v diff -u -N -r1.2 -r1.3 --- openacs-4/packages/email-handler/doc/index.html 5 Apr 2018 14:44:09 -0000 1.2 +++ openacs-4/packages/email-handler/doc/index.html 12 Apr 2018 07:47:22 -0000 1.3 @@ -117,7 +117,7 @@ When installing the email handler, you must go to the Site Map on your ACS web server and instantiate a copy of the package with the name 'email-handler'. It should be mounted at /email-handler in order to -edit it's parameters, although you can probably mount it at another +edit its parameters, although you can probably mount it at another URL and it will still work.

Index: openacs-4/packages/ezic-gateway/tcl/ezic-gateway-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/ezic-gateway/tcl/ezic-gateway-procs.tcl,v diff -u -N -r1.3 -r1.4 --- openacs-4/packages/ezic-gateway/tcl/ezic-gateway-procs.tcl 4 Sep 2008 12:44:38 -0000 1.3 +++ openacs-4/packages/ezic-gateway/tcl/ezic-gateway-procs.tcl 12 Apr 2018 07:47:22 -0000 1.4 @@ -224,12 +224,12 @@ billing_country } { ChargeCard is a wrapper so we can present a consistent interface to - the caller. It will just pass on it's parameters to - ezic_gateway.postauth or ezic_gateway.authcapture, - whichever is appropriate for the implementation at hand. + the caller. It will just pass on its parameters to + ezic_gateway.postauth or ezic_gateway.authcapture, + whichever is appropriate for the implementation at hand. - PostAuth is used when there is a successful authorize transaction in - the ezic_gateway_result_log for transaction_id. AuthCapture will + PostAuth is used when there is a successful authorize transaction in + the ezic_gateway_result_log for transaction_id. AuthCapture will be used if there is no prior authorize transaction in the log. @author Bart Teeuwisse Index: openacs-4/packages/glossary/www/doc/design.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/glossary/www/doc/design.html,v diff -u -N -r1.1 -r1.2 --- openacs-4/packages/glossary/www/doc/design.html 20 Apr 2001 20:51:12 -0000 1.1 +++ openacs-4/packages/glossary/www/doc/design.html 12 Apr 2018 07:47:22 -0000 1.2 @@ -38,17 +38,17 @@

The Glossary Package is based on the ACS 3.x glossary module which was simply - a repository for a site's terms and their definitions. + a repository for a site's terms and their definitions.

- In the process of migrating the glossary to an ACS 4.0 package, we will - expand it's feature set to support multiple contexts. A site, subsite, - group, user, or even document (a this point the document must exist in the database as an ACS object) may have one or more glossaries associated - with it. Terms may have illustrations (acs-content-repository). Each glossary can have its security set (acs-permissions), a workflow, and - optionally except user comments. A glossary's content will be stored in + In the process of migrating the glossary to an ACS 4.0 package, we will + expand its feature set to support multiple contexts. A site, subsite, + group, user, or even document (a this point the document must exist in the database as an ACS object) may have one or more glossaries associated + with it. Terms may have illustrations (acs-content-repository). Each glossary can have its security set (acs-permissions), a workflow, and + optionally except user comments. A glossary's content will be stored in the content repository and its presentation will use the ArsDigita Templating System (ATS).

-The Glossary Package does not provide a mechanism to expire content (glossaries or terms). +The Glossary Package does not provide a mechanism to expire content (glossaries or terms).

Glossaries provide excellent support for collaboration. Referring to terms' definitions can keep misunderstanding in check thus making it easier to work in groups. Index: openacs-4/packages/glossary/www/doc/requirements.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/glossary/www/doc/requirements.html,v diff -u -N -r1.3 -r1.4 --- openacs-4/packages/glossary/www/doc/requirements.html 11 Apr 2018 20:52:01 -0000 1.3 +++ openacs-4/packages/glossary/www/doc/requirements.html 12 Apr 2018 07:47:22 -0000 1.4 @@ -22,13 +22,13 @@

II. Vision Statement

The Glossary Package is based on the ACS 3.x glossary module which was simply - a repository for a site's terms and their definitions. + a repository for a site's terms and their definitions.

- In the process of migrating the glossary to an ACS 4.0 package, we will - expand it's feature set to support multiple contexts. A site, subsite, - group, user, or even document (a this point the document must exist in the database as an ACS object) may have one or more glossaries associated - with it. Terms may have illustrations (acs-content-repository). Each glossary can have its security set (acs-permissions), a workflow, and - optionally except user comments. A glossary's content will be stored in + In the process of migrating the glossary to an ACS 4.0 package, we will + expand its feature set to support multiple contexts. A site, subsite, + group, user, or even document (a this point the document must exist in the database as an ACS object) may have one or more glossaries associated + with it. Terms may have illustrations (acs-content-repository). Each glossary can have its security set (acs-permissions), a workflow, and + optionally except user comments. A glossary's content will be stored in the content repository and its presentation will use the ArsDigita Templating System (ATS). @@ -58,7 +58,7 @@

  • Mechanism for users to comment on terms. This feature is controlled by the administrator of the glossary via setting permissions.
    • - + Index: openacs-4/packages/jabber/sql/oracle/jabber-notification-forum-create.sql =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/jabber/sql/oracle/jabber-notification-forum-create.sql,v diff -u -N -r1.1 -r1.2 --- openacs-4/packages/jabber/sql/oracle/jabber-notification-forum-create.sql 20 Oct 2004 19:36:47 -0000 1.1 +++ openacs-4/packages/jabber/sql/oracle/jabber-notification-forum-create.sql 12 Apr 2018 07:47:22 -0000 1.2 @@ -4,47 +4,42 @@ -- @email bkiesbye@sussdorff-roy.com -- - - - --- This code registers the forum (package) with the +-- This code registers the forum (package) with the -- new NotificationMethodImplementations from the jabber package. -- When the forum (package is re/installed after the jabber package) -- the code from this from this file should run after the forum instalation. -- This hack should be part of the forums package. --- Comment: it should not be a hack like this anyway , the service contract is responsible +-- Comment: it should not be a hack like this anyway , the service contract is responsible -- ,to let every App., that is interested in making use of the NotificationDeliveryMethod interface, -- get access to all implementations of this interface. The Notification package is able to handle --- more then one implementation of it's interface (like it schould by openacs definition) --- but the service contract package dosn't seem to be able to properly populate multiple implementations --- of the same interface (service contract). Even if it alowes multiple implementations to exist +-- more then one implementation of its interface (like it should by openacs definition) +-- but the service contract package doesn't seem to be able to properly populate multiple implementations +-- of the same interface (service contract). Even if it allows multiple implementations to exist declare v_type_id_message int; v_delivery_method_id_and notification_types_del_methods.delivery_method_id%TYPE; v_type_id_thread notification_types_del_methods.type_id%TYPE; v_delivery_method_id_or notification_types_del_methods.delivery_method_id%TYPE; -begin - SELECT delivery_method_id INTO v_delivery_method_id_and FROM notification_delivery_methods WHERE short_name like('imessage_and_email'); - +begin + SELECT delivery_method_id INTO v_delivery_method_id_and FROM notification_delivery_methods WHERE short_name like('imessage_and_email'); - SELECT delivery_method_id INTO v_delivery_method_id_or FROM notification_delivery_methods WHERE short_name like('imessage_or_email'); + SELECT delivery_method_id INTO v_delivery_method_id_or FROM notification_delivery_methods WHERE short_name like('imessage_or_email'); - SELECT type_id INTO v_type_id_message FROM notification_types WHERE short_name like('forums_message_notif'); + SELECT type_id INTO v_type_id_message FROM notification_types WHERE short_name like('forums_message_notif'); + SELECT type_id INTO v_type_id_thread FROM notification_types WHERE short_name like('forums_forum_notif'); - SELECT type_id INTO v_type_id_thread FROM notification_types WHERE short_name like('forums_forum_notif'); - - insert into notification_types_del_methods (type_id, delivery_method_id) + insert into notification_types_del_methods (type_id, delivery_method_id) values ( v_type_id_thread ,v_delivery_method_id_and); - insert into notification_types_del_methods (type_id, delivery_method_id) + insert into notification_types_del_methods (type_id, delivery_method_id) values ( v_type_id_thread , v_delivery_method_id_or ); - insert into notification_types_del_methods (type_id, delivery_method_id) + insert into notification_types_del_methods (type_id, delivery_method_id) values ( v_type_id_message , v_delivery_method_id_and); - insert into notification_types_del_methods (type_id, delivery_method_id) + insert into notification_types_del_methods (type_id, delivery_method_id) values ( v_type_id_message , v_delivery_method_id_or); end; / Index: openacs-4/packages/jabber/www/doc/ns-jabber-documentation.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/jabber/www/doc/ns-jabber-documentation.adp,v diff -u -N -r1.5 -r1.6 --- openacs-4/packages/jabber/www/doc/ns-jabber-documentation.adp 5 Apr 2018 14:44:09 -0000 1.5 +++ openacs-4/packages/jabber/www/doc/ns-jabber-documentation.adp 12 Apr 2018 07:47:22 -0000 1.6 @@ -420,7 +420,7 @@

    append html "</table>"

    -This example calls jb_activeconferencerooms and stores the ns_set ID in the variable active_rooms, it checks if the function hasent returned -1 (no error). Then it reads the size of the ns_set into the variable row_count . Then in a for loop , it loops through the returned ns_set putting it's keys in the first column of the table , and in the second column it first reads the ns_set ID from the keys (roomNames) value pair , and then from this ns_set it reads the value from position 1 (wich holds the topic of this room). +This example calls jb_activeconferencerooms and stores the ns_set ID in the variable active_rooms, it checks if the function hasent returned -1 (no error). Then it reads the size of the ns_set into the variable row_count . Then in a for loop , it loops through the returned ns_set putting its keys in the first column of the table , and in the second column it first reads the ns_set ID from the keys (roomNames) value pair , and then from this ns_set it reads the value from position 1 (wich holds the topic of this room).

    Structur of the ns_set returned by jb_activeconferencerooms Index: openacs-4/packages/layout-managed-subsite/www/doc/install.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/layout-managed-subsite/www/doc/install.adp,v diff -u -N -r1.1 -r1.2 --- openacs-4/packages/layout-managed-subsite/www/doc/install.adp 26 Nov 2008 11:10:23 -0000 1.1 +++ openacs-4/packages/layout-managed-subsite/www/doc/install.adp 12 Apr 2018 07:47:22 -0000 1.2 @@ -7,7 +7,7 @@ admin UI pages to add the includelets and their associated applications to the subsite, but it's easiest to do so before running the wizard.

    Each includelet package depends on an application package, typically a standalone package -such as forums. In some cases, an includelet package will provide it's own application, +such as forums. In some cases, an includelet package will provide its own application, for example the content-includelet package, which provides simple content management for an individual includelet but which is not meant to be used standalone outside of the Layout Manager environment. Index: openacs-4/packages/new-portal/sql/oracle/api-create.sql =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/new-portal/sql/oracle/api-create.sql,v diff -u -N -r1.44 -r1.45 --- openacs-4/packages/new-portal/sql/oracle/api-create.sql 7 Oct 2007 22:37:02 -0000 1.44 +++ openacs-4/packages/new-portal/sql/oracle/api-create.sql 12 Apr 2018 07:47:22 -0000 1.45 @@ -251,7 +251,7 @@ else - -- we have a portal as our template. copy it's theme, pages, layouts, + -- we have a portal as our template. copy its theme, pages, layouts, -- elements, and element params. select theme_id into v_theme_id Index: openacs-4/packages/new-portal/sql/oracle/upgrade/upgrade-0.1a-0.2d1.sql =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/new-portal/sql/oracle/upgrade/upgrade-0.1a-0.2d1.sql,v diff -u -N -r1.1 -r1.2 --- openacs-4/packages/new-portal/sql/oracle/upgrade/upgrade-0.1a-0.2d1.sql 8 Oct 2003 16:03:58 -0000 1.1 +++ openacs-4/packages/new-portal/sql/oracle/upgrade/upgrade-0.1a-0.2d1.sql 12 Apr 2018 07:47:22 -0000 1.2 @@ -242,7 +242,7 @@ else - -- we have a portal as our template. copy it's theme, pages, layouts, + -- we have a portal as our template. copy its theme, pages, layouts, -- elements, and element params. select theme_id into v_theme_id Index: openacs-4/packages/new-portal/sql/oracle/upgrade/upgrade-2.1.0a-2.1.0a2.sql =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/new-portal/sql/oracle/upgrade/upgrade-2.1.0a-2.1.0a2.sql,v diff -u -N -r1.2 -r1.3 --- openacs-4/packages/new-portal/sql/oracle/upgrade/upgrade-2.1.0a-2.1.0a2.sql 13 Jan 2005 13:58:24 -0000 1.2 +++ openacs-4/packages/new-portal/sql/oracle/upgrade/upgrade-2.1.0a-2.1.0a2.sql 12 Apr 2018 07:47:22 -0000 1.3 @@ -219,7 +219,7 @@ else - -- we have a portal as our template. copy it's theme, pages, layouts, + -- we have a portal as our template. copy its theme, pages, layouts, -- elements, and element params. select theme_id into v_theme_id Index: openacs-4/packages/new-portal/sql/oracle/upgrade/upgrade-2.3.0d3-2.3.0d4.sql =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/new-portal/sql/oracle/upgrade/upgrade-2.3.0d3-2.3.0d4.sql,v diff -u -N -r1.2 -r1.3 --- openacs-4/packages/new-portal/sql/oracle/upgrade/upgrade-2.3.0d3-2.3.0d4.sql 15 May 2007 20:14:47 -0000 1.2 +++ openacs-4/packages/new-portal/sql/oracle/upgrade/upgrade-2.3.0d3-2.3.0d4.sql 12 Apr 2018 07:47:22 -0000 1.3 @@ -228,7 +228,7 @@ else - -- we have a portal as our template. copy it's theme, pages, layouts, + -- we have a portal as our template. copy its theme, pages, layouts, -- elements, and element params. select theme_id into v_theme_id Index: openacs-4/packages/new-portal/sql/oracle/upgrade/upgrade-2.3.1d1-2.3.1d2.sql =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/new-portal/sql/oracle/upgrade/upgrade-2.3.1d1-2.3.1d2.sql,v diff -u -N -r1.2 -r1.3 --- openacs-4/packages/new-portal/sql/oracle/upgrade/upgrade-2.3.1d1-2.3.1d2.sql 7 Oct 2007 22:37:02 -0000 1.2 +++ openacs-4/packages/new-portal/sql/oracle/upgrade/upgrade-2.3.1d1-2.3.1d2.sql 12 Apr 2018 07:47:22 -0000 1.3 @@ -255,7 +255,7 @@ else - -- we have a portal as our template. copy it's theme, pages, layouts, + -- we have a portal as our template. copy its theme, pages, layouts, -- elements, and element params. select theme_id into v_theme_id Index: openacs-4/packages/new-portal/www/themes/kelp-theme/dotlrn/dotlrn-master-kelp.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/new-portal/www/themes/kelp-theme/dotlrn/dotlrn-master-kelp.tcl,v diff -u -N -r1.7 -r1.8 --- openacs-4/packages/new-portal/www/themes/kelp-theme/dotlrn/dotlrn-master-kelp.tcl 7 Aug 2017 23:48:12 -0000 1.7 +++ openacs-4/packages/new-portal/www/themes/kelp-theme/dotlrn/dotlrn-master-kelp.tcl 12 Apr 2018 07:47:22 -0000 1.8 @@ -15,16 +15,16 @@ # # /www/dotlrn-master.tcl # -# This is the "default-master" template for dotlrn sites. +# This is the "default-master" template for dotlrn sites. # # Instructions: # -# 1. Put this file and it's .adp file into the server's /www directory. +# 1. Put this file and its .adp file into the server's /www directory. # That's the one with the "default-master" Tcl and adp files. You don't # have to edit or remove the "default-master" files, since they will be # ignored by the next step. # -# 2. Change the "Main Site"'s "DefaultMaster" parameter +# 2. Change the "Main Site"'s "DefaultMaster" parameter # from "/www/default-master" to "/www/dotlrn-master" # at http://yoursite.com/admin/site-map # @@ -34,7 +34,7 @@ # at the top of the page, the title of the pages, the fonts of the portlets, etc. # # WARNING: All current portlet themes (table, deco, nada, etc) depend on some -# of the CSS defined below. Be careful when you edit the CSS below, +# of the CSS defined below. Be careful when you edit the CSS below, # and check how themes use it. # # Index: openacs-4/packages/organizations/sql/postgresql/organizations-create.sql =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/organizations/sql/postgresql/organizations-create.sql,v diff -u -N -r1.7 -r1.8 --- openacs-4/packages/organizations/sql/postgresql/organizations-create.sql 18 Dec 2006 14:10:47 -0000 1.7 +++ openacs-4/packages/organizations/sql/postgresql/organizations-create.sql 12 Apr 2018 07:47:22 -0000 1.8 @@ -31,7 +31,7 @@ -- organization -- this will be a party --- probably should be it's own package +-- probably should be its own package create table organizations ( organization_id integer @@ -45,9 +45,9 @@ -- this can be ein/ssn/vat reg_number varchar(100), -- The internal client_id. You should have your own sequence for that. - client_id varchar(100) constraint orga_client_id_un unique, + client_id varchar(100) constraint orga_client_id_un unique, notes text -); +); create index organization_name_ix on organizations(name); create index organization_cliend_idx on organizations(client_id); Index: openacs-4/packages/payment-gateway/www/creditcard-widget.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/payment-gateway/www/creditcard-widget.tcl,v diff -u -N -r1.1 -r1.2 --- openacs-4/packages/payment-gateway/www/creditcard-widget.tcl 5 Jun 2002 02:32:58 -0000 1.1 +++ openacs-4/packages/payment-gateway/www/creditcard-widget.tcl 12 Apr 2018 07:47:22 -0000 1.2 @@ -1,9 +1,9 @@ ad_page_contract { This is part of the credit card gateway, for obvious reasons, but it - takes it's list of of what cards it can accept from the caller's - package params. + takes its list of what cards it can accept from the caller's + package params. - That means that it's intended to be used only by the caller, and that + That means that it's intended to be used only by the caller, and that the caller must define a package param called CreditCardsAccepted. That param is *not* part of this package and it's not supposed to be. Don't try to add one! :) Index: openacs-4/packages/sample-gateway/tcl/sample-gateway-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/sample-gateway/tcl/sample-gateway-procs.tcl,v diff -u -N -r1.2 -r1.3 --- openacs-4/packages/sample-gateway/tcl/sample-gateway-procs.tcl 24 Feb 2005 13:33:25 -0000 1.2 +++ openacs-4/packages/sample-gateway/tcl/sample-gateway-procs.tcl 12 Apr 2018 07:47:22 -0000 1.3 @@ -91,12 +91,12 @@ @author Janine Sisk; furfly.net, LLC (janine@furfly.net) } { # ChargeCard is a wrapper so we can present a consistent interface to - # the end caller. It will just pass on it's parameters to PostAuth, + # the end caller. It will just pass on its parameters to PostAuth, # AuthCapture or Charge, whichever is appropriate for the implementation # at hand. Here, we are doing nothing. # We are returning the transaction_id we were given, but if this - # wasn't just a stub we'd be returning the value that came back from + # wasn't just a stub we'd be returning the value that came back from # the gateway. We'd also be returning the value that was returned. set return_values(response_code) [nsv_get payment_gateway_return_codes success] set return_values(reason) "" Index: openacs-4/packages/soap-gateway/www/doc/index.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/soap-gateway/www/doc/index.adp,v diff -u -N -r1.2 -r1.3 --- openacs-4/packages/soap-gateway/www/doc/index.adp 4 Apr 2018 08:11:26 -0000 1.2 +++ openacs-4/packages/soap-gateway/www/doc/index.adp 12 Apr 2018 07:47:22 -0000 1.3 @@ -30,25 +30,25 @@

  • License

    • Overview (toc)

    -

    The Simple Object Access Protocol (SOAP) v1.1 - was submitted to W3C on April 18, 2000. Its compatriot +

    The Simple Object Access Protocol (SOAP) v1.1 + was submitted to W3C on April 18, 2000. Its compatriot Web Services Description Language (WSDL) was submitted - on March 14, 2001. Together they attempt to unify diverse systems using a form - of XML RPC. Most major software vendors are involved to some extent. Its future + on March 14, 2001. Together they attempt to unify diverse systems using a form + of XML RPC. Most major software vendors are involved to some extent. Its future looks bright.

    -

    SOAP fits nicely into the Client/Server topology. Given a client that needs - some functionality available on a server, SOAP can be used to specify an operation - and its arguments to be submitted by the client to the server. At it's root, - the data representing the operation is fairly basic. If the connection between - the client and server were a TCP wire, a data trace would show about a page - of XML. The XML is not complex and is often decipherable at a glance. The XML - data is specified as a SOAP Envelope. An evolving SOAP - specification defines the Envelope and its progeny. The XML data transmitted - between the client and server is not arbitrary and should conform to a referenced - WSDL instance published by the server. It's the WSDL that defines the published - services and the invocation formats required for execution. The vast majority - of SOAP documentation demonstrates SOAP over HTTP. Another mentioned transport - is SMTP. In each case, the SOAP Envelope follows the respective header as an +

    SOAP fits nicely into the Client/Server topology. Given a client that needs + some functionality available on a server, SOAP can be used to specify an operation + and its arguments to be submitted by the client to the server. At its root, + the data representing the operation is fairly basic. If the connection between + the client and server were a TCP wire, a data trace would show about a page + of XML. The XML is not complex and is often decipherable at a glance. The XML + data is specified as a SOAP Envelope. An evolving SOAP + specification defines the Envelope and its progeny. The XML data transmitted + between the client and server is not arbitrary and should conform to a referenced + WSDL instance published by the server. It's the WSDL that defines the published + services and the invocation formats required for execution. The vast majority + of SOAP documentation demonstrates SOAP over HTTP. Another mentioned transport + is SMTP. In each case, the SOAP Envelope follows the respective header as an XML Payload.

    Many web servers have been retrofitted to support a SOAP subsystem; e.g., Websphere, Apache, iPlanet, IIS, etc. There are a handful of SOAP toolkits. To name a few, Index: openacs-4/packages/static-portlet/tcl/static-portal-content-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/static-portlet/tcl/static-portal-content-procs.tcl,v diff -u -N -r1.21 -r1.22 --- openacs-4/packages/static-portlet/tcl/static-portal-content-procs.tcl 7 Aug 2017 23:48:29 -0000 1.21 +++ openacs-4/packages/static-portlet/tcl/static-portal-content-procs.tcl 12 Apr 2018 07:47:22 -0000 1.22 @@ -17,7 +17,7 @@ ad_library { The procs for manipulating static portal content. This is like having - the "bboard" included in it's own "bboard-portlet" package. + the "bboard" included in its own "bboard-portlet" package. @author arjun@openforce.net @cvs-id $Id$ @@ -30,11 +30,11 @@ {-package_id:required} {-content:required} {-pretty_name:required} - {-format "text/html"} + {-format "text/html"} } { Calls the pl/sql to create the new content item } { - # Create the content item + # Create the content item set content_id [db_exec_plsql new_content_item {}] # Ben's style only cause he was editing here and then changed things back @@ -49,7 +49,6 @@ } { This is a bit different from other add_self_to_page procs. } { - if {$template_id ne ""} { # we got a template_id, so we know that (1) that we are # being called from add_applet_to_community. That means that @@ -64,36 +63,35 @@ [static_portlet::get_my_name] ] - set new_content_ids [list] - foreach oei $old_element_id { - set old_content_id [portal::get_element_param $oei content_id] - + set new_content_ids [list] + foreach oei $old_element_id { + set old_content_id [portal::get_element_param $oei content_id] - # clone the template's content - lappend new_content_ids [static_portal_content::new \ - -package_id $package_id \ - -content [get_content -content_id $old_content_id] \ - -format [get_content_format -content_id $old_content_id] \ - -pretty_name [get_pretty_name -content_id $old_content_id]] + # clone the template's content + lappend new_content_ids [static_portal_content::new \ + -package_id $package_id \ + -content [get_content -content_id $old_content_id] \ + -format [get_content_format -content_id $old_content_id] \ + -pretty_name [get_pretty_name -content_id $old_content_id]] - } + } - # update the new static portlet's params, and return - set new_element_ids [portal::get_element_ids_by_ds \ - $portal_id \ - [static_portlet::get_my_name] - ] + # update the new static portlet's params, and return + set new_element_ids [portal::get_element_ids_by_ds \ + $portal_id \ + [static_portlet::get_my_name] + ] - foreach nei $new_element_ids nci $new_content_ids { - portal::set_element_param $nei "package_id" $package_id - portal::set_element_param $nei "content_id" $nci - } + foreach nei $new_element_ids nci $new_content_ids { + portal::set_element_param $nei "package_id" $package_id + portal::set_element_param $nei "content_id" $nci + } - # we use the return value to create the portlet on the non-member - # page, which is linked to the same content as on the - # main comm page + # we use the return value to create the portlet on the non-member + # page, which is linked to the same content as on the + # main comm page - return [lindex $new_content_ids 0] + return [lindex $new_content_ids 0] } db_transaction { @@ -113,7 +111,7 @@ portal::set_element_param $element_id package_id $package_id portal::set_element_param $element_id content_id $content_id } - return $element_id + return $element_id } ad_proc -public clone { @@ -168,15 +166,14 @@ {-content_id:required} {-content:required} {-pretty_name:required} - {-format "text/html"} + {-format "text/html"} } { updates the content item } { - - db_transaction { + db_transaction { # update the content item db_dml update_content_item {} - + # update the title of the portal element set element_id [portal::get_element_id_from_unique_param \ -portal_id $portal_id \ @@ -195,7 +192,6 @@ } { deletes the item } { - db_dml delete_content_item { delete from static_portal_content where content_id = :content_id } @@ -228,13 +224,13 @@ } { return [db_string get_package_id.select {}] } - + ad_proc -public get_content_format { - {-content_id:required} + {-content_id:required} } { - Get the format of the content's item + Get the format of the content's item } { - return [db_string get_content_format.select {} ] + return [db_string get_content_format.select {} ] } } Index: openacs-4/packages/tsoap/tcl/SOAP-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/tsoap/tcl/SOAP-procs.tcl,v diff -u -N -r1.5 -r1.6 --- openacs-4/packages/tsoap/tcl/SOAP-procs.tcl 4 Apr 2018 22:00:34 -0000 1.5 +++ openacs-4/packages/tsoap/tcl/SOAP-procs.tcl 12 Apr 2018 07:47:23 -0000 1.6 @@ -16,7 +16,7 @@ package require uri; # tcllib 1.0 catch {package require uri::urn}; # tcllib 1.2 # package require SOAP::Utils; # TclSOAP -package require rpcvar; # TclSOAP +package require rpcvar; # TclSOAP package require tdom # ------------------------------------------------------------------------- @@ -38,8 +38,8 @@ # ------------------------------------------------------------------------- # Description: -# Register the namespace for handling SOAP methods using 'scheme' as a -# transport. See the http.tcl and smtp.tcl files for examples of how +# Register the namespace for handling SOAP methods using 'scheme' as a +# transport. See the http.tcl and smtp.tcl files for examples of how # to plug in a new scheme. # A SOAP transport package requires an 'xfer' method for performing the # SOAP method call and a 'configure' method for setting any transport @@ -77,7 +77,7 @@ # proc ::SOAP::transportHook {procVarName cmdname} { upvar $procVarName procvar - + array set URL [uri::split $procvar(proxy)] if {$URL(scheme) == "urn"} { set URL(scheme) "$a(scheme):$a(nid)" @@ -96,7 +96,7 @@ # Parameters: # name - the name of a Tcl entity, or list of command and arguments # Result: -# Fully qualified namespace path for the named entity. If the name +# Fully qualified namespace path for the named entity. If the name # parameter is a list the the first element is namespace qualified # and the remainder of the list is unchanged. # @@ -111,8 +111,8 @@ # ------------------------------------------------------------------------- # Description: -# An interal procedure to mangle and SOAP method name and it's namespace -# and generate a name for use as a specific SOAP variable. This ensures +# An internal procedure to mangle a SOAP method name and its namespace +# and generate a name for use as a specific SOAP variable. This ensures # that similarly named methods in different namespaces do not conflict # within the SOAP package. # Parameters: @@ -296,14 +296,14 @@ -parse* { set procvar(parseProc) [qualifyNamespace $value] } -post* { set procvar(postProc) [qualifyNamespace $value] } -com* { set procvar(command) [qualifyNamespace $value] } - -err* { - set procvar(errorCommand) [qualifyNamespace $value] + -err* { + set procvar(errorCommand) [qualifyNamespace $value] } default { # might be better to delete the args as we process them # and then call this once with all the remaining args. # Still - this will work fine. - if {[info exists transportHook] + if {[info exists transportHook] && [info commands $transportHook] != {}} { if {[catch {eval $transportHook $procVarName \ [list $opt] [list $value]}]} { @@ -318,7 +318,7 @@ } } - if { $procvar(name) == {} } { + if { $procvar(name) == {} } { set procvar(name) $procName } @@ -332,19 +332,19 @@ return -code error "invalid transport:\ \"$scheme\" is improperly registered" } - } - + } + # The default version is SOAP 1.1 if { $procvar(version) == {} } { set procvar(version) SOAP1.1 } # Canonicalize the SOAP version URI switch -glob -- $procvar(version) { SOAP1.1 - 1.1 { - set procvar(version) "http://schemas.xmlsoap.org/soap/envelope/" + set procvar(version) "http://schemas.xmlsoap.org/soap/envelope/" } SOAP1.2 - 1.2 { - set procvar(version) "http://www.w3.org/2001/06/soap-envelope" + set procvar(version) "http://www.w3.org/2001/06/soap-envelope" } } @@ -357,14 +357,14 @@ set procvar(encoding) "http://schemas.xmlsoap.org/soap/encoding/" } SOAP1.2 - 1.2 { - set procvar(encoding) "http://www.w3.org/2001/06/soap-encoding" + set procvar(encoding) "http://www.w3.org/2001/06/soap-encoding" } } # Select the default parser unless one is specified if { $procvar(parseProc) == {} } { set procvar(parseProc) [namespace current]::parse_soap_response - } + } # If no request wrapper is set, use the default SOAP wrap proc. if { $procvar(wrapProc) == {} } { @@ -423,7 +423,7 @@ foreach opt [set $transportOptions] { array set $varName [list $opt {}] } - + # Call any transport defined construction proc set createHook "[schemeloc $scheme]::method:create" if {[info commands $createHook] != {}} { @@ -662,7 +662,7 @@ pack $f2 -side bottom -fill x pack $m -side top -fill x -expand 1 pack $f1 -side top -anchor n -fill both -expand 1 - + #bind .tx "$f2.b invoke" tkwait window .tx @@ -685,7 +685,7 @@ # detail - list of {detailName detailInfo} # Result: # returns the XML text of the SOAP Fault packet. -# +# proc ::SOAP::fault {faultcode faultstring {detail {}}} { set doc [dom createDocument "SOAP-ENV:Envelope"] set bod [reply_envelope $doc] @@ -704,14 +704,14 @@ set dtl [$doc createElement "e:errorInfo"] $dtl0 appendChild $dtl $dtl setAttribute "xmlns:e" "urn:TclSOAP-ErrorInfo" - + foreach {detailName detailInfo} $detail { set err [$doc createElement $detailName] $dtl appendChild $err $err appendChild [$doc createTextNode $detailInfo] } } - + # serialize the DOM document and return the XML text regsub "\]*>\n" [$doc asXML] {} r $doc delete @@ -933,7 +933,7 @@ set procName [lindex [split $procVarName {_}] end] set params $procvar(params) set name $procvar(name) - + if { [llength $args] != [expr { [llength $params] / 2 } ]} { set msg "wrong # args: should be \"$procName" foreach { id type } $params { @@ -942,18 +942,18 @@ append msg "\"" return -code error $msg } - + set doc [dom createDocument "methodCall"] set d_root [$doc documentElement] set d_meth [$doc createElement "methodName"] $d_root appendChild $d_meth $d_meth appendChild [$doc createTextNode $name] - + if { [llength $params] != 0 } { set d_params [$doc createElement "params"] $d_root appendChild $d_params } - + set param_no 0 foreach {key type} $params { set val [lindex $args $param_no] @@ -976,7 +976,7 @@ # ------------------------------------------------------------------------- # Description: -# Parse a SOAP response payload. Check for Fault response otherwise +# Parse a SOAP response payload. Check for Fault response otherwise # extract the value data. # Parameters: # procVarName - the name of the SOAP method configuration variable @@ -1024,7 +1024,7 @@ } else { set procvar(headers) {} } - + set result {} if {[info exists procvar(name)]} { @@ -1087,7 +1087,7 @@ -errorinfo $err(faultString) \ "Received XML-RPC Error" } - + # Recurse over each params/param/value set n_params 0 foreach valueNode [selectNode $doc \ @@ -1137,7 +1137,7 @@ set paramsNode [selectNode $doc "/methodCall/params"] set paramValues {} if {$paramsNode != {}} { - set paramValues [decomposeXMLRPC $paramsNode] + set paramValues [decomposeXMLRPC $paramsNode] } if {[llength $paramValues] == 1} { set paramValues [lindex $paramValues 0] @@ -1232,7 +1232,7 @@ if {$headers != {}} { insert_headers $node $headers } - + # If the rpcvar namespace is a URI then assign it a tag and ensure we # have our colon only when required. if {$typexmlns != {} && [regexp : $typexmlns]} { @@ -1248,7 +1248,7 @@ } } - if {[string match {*()} $typeinfo] || [string match {*()} $type] + if {[string match {*()} $typeinfo] || [string match {*()} $type] || [string match array $type]} { # array type: arrays are indicated by one or more () suffixes or # the word 'array' (depreciated) @@ -1264,16 +1264,16 @@ set dimensions [regexp -all -- {\(\)} $typeinfo] set itemtype [string trimright $typeinfo ()] } - + # Look up the typedef info of the item type set itemxmlns [typedef -namespace $itemtype] if {$itemxmlns != {} && [regexp : $itemxmlns]} { $node setAttribute "xmlns:i" $itemxmlns set itemxmlns i } - + # Currently we do not support non-0 offsets into the array. - # This is because I don;t know how I should present this to the + # This is because I don't know how I should present this to the # user. It's got to be a dynamic attribute on the value. $node setAttribute "xmlns:SOAP-ENC" "http://schemas.xmlsoap.org/soap/encoding/" $node setAttribute "xsi:type" "SOAP-ENC:Array"