Example:
|
Recommendation:
|
Complete
Syntax:
|
| Length: |
Minimum
n/a |
Maximum
n/a |
Recommended
n/a |
Usage:
|
Description:
|
Comments:
|
Examples:
|
|
Google-Comments: |
|
Yahoo-Comments: |
|
MSN-Comments: |
|
AOL-Comments: |
| Ask
Jeeves-Comments: |
|
AltaVista-Comments: |
|
Excite-Comments: |
| HotBot-Comments: |
| Itomi-Comments: |
| InfoSeek-Comments: |
| Lycos-Comments: |
| NorthernLight-Comments: |
| |
| USA Usage/Comments: |
| UK
Usage/Comments: |
| CDN Usage/Comments: |
| DCMI Usage/Comments: |
| Other International/Comments: |
| |
| Commerical Usage/Comments: |
| Governmental Usage/Comments: |
| Education Usage/Comments: |
| Non-profit Usage/Comments: |
| |
| HTML 1.0 |
| HTML 2.0 |
| HTML 3.2 |
| HTML 4.0 |
| XHTML |
| DHTML |
| eGMS |
| PICS |
| DCMI |
| W3C |
| |
| |
| |
| |
Date: 09/18/05 10:17:45
Subject:
KCL:
META tags
... <META NAME="content_destination"
CONTENT=""> - no longer used: deprecated. <META
NAME="source_path" CONTENT=""> - no longer used:
deprecated. ...
www.kcl.ac.uk/www/styleGuide/meta.html
- 8k - Supplemental Result -
Cached -
Similar pages
META tags
META tags are invisible to the user. Their purpose is to provide
data about the page within which they're located. In the form of
META tags, this data can be read by software and put to use. For
example, search engines use META data to create accruate indexes of
a web-site's pages.
META tags have a simple format:
<META NAME="author" CONTENT="Stephen Emmott">
META tags are like labels for the page. NAME indicates the
purpose of the label; CONTENT contains the data. The example above
indicates that the author is Stephen Emmott. The great
thing about META tags is that labels can be generated dependent upon
needs. Alternatively, it is possible to use one of a number of
standardised labels that have been agreed by HE and other
communities (e.g., Dublin Core).
KIS uses META tags for a number of 'home-grown' labels. These are
listed below together with a description explaining what CONTENT
should be set to.
<META NAME="IP" CONTENT="">
- name of the Information Provider who maintains this page.
<META NAME="e-mail" CONTENT="">
- e-mail address of the Information Provider who maintains this
page.
<META NAME="created" CONTENT="">
- the date upon which this page was created: using the form
DD/MM/YYYY.
<META NAME="modified" CONTENT="">
- the date upon which this page was last modified: using the form
DD/MM/YYYY.
<META NAME="expires" CONTENT="">
- an expiry date for the page or its content: using the form
DD/MM/YYYY.
<META NAME="keywords" CONTENT="">
- a list of keywords (each separated by a comma) for the content
on the page.
<META NAME="description" CONTENT="">
- one or two sentences describing the page.
<META NAME="copyright" CONTENT="">
- name of the organisation or individual to whom copyright
belongs.
<META NAME="content_source" CONTENT="">
- name of the department or institution from which the content
came.
<META NAME="content_destination" CONTENT="">
- no longer used: deprecated.
<META NAME="source_path"
CONTENT="">
- no longer used: deprecated.
These META tags sit within the HEAD tag of the page. Take a look
at the code for this page to see them in use.
Within KIS, these META tags are used by the search engine to
build detailed indexes of the site. It is then possible to search by
set fields e.g., by author, expires, etc. The tags are also used by
software created for the purposes of maintaining KIS as a collection
- they help in managing the site behind the scenes.
To
set up a helper application (CA)
... The Source Path property value in Content
Analyzer come from the <META
NAME="SOURCE PATH" . . . tag. The source path
is used by ...
www.ppg.com/siteserver/docs/ssa_track_fjyz.htm
- 6k - Supplemental Result -
Cached -
Similar pages
To set up a helper application
- On the Tools menu, click Program Options, and
then click the Helpers tab.
- In the Resource type list, select the resource for
which you want to set up the helper application.
- Click Add.
- In the Path to application box, type the path and
file name of the helper application, and then click OK.
- The file name for the helper application automatically
appears in the Menu text box. If needed, Type a
descriptive name for the helper application in the Menu text
box.. Note that whatever is typed in the Menu text box
appears under Open With in the Tools menu.
- The path and file name for the helper application
automatically appears in the Application box. If needed,
you can modify the path in the Application box.
- If needed, you can specify parameters for the helper
application in the Parameters box. You can also click
Variables to add different parameters to the Parameters
box:
- URL:The value of the URL property is substituted
in place of this variable when constructing the command line
for the specified helper application.
- Local Path (default):The value of the Local Path
property (populated when creating a project from file, or
when creating a project from URL with a site copy) is
substituted in place of this variable when constructing the
command line for the specified helper application.
Command line flags can be used with these variables. For
example, suppose you want to use the $LocalPath variable
with Microsoftฎ Notepad whose file name you want to specify
from the command line. You could type the following in the
Parameters box, -f $LocalPath, so that for a
particular resource that has a Local Path value of C:\mysite\default.htm,
the command line used to open that application would be
Notepad.exe -f C:\mysite\default.htm.
- Source Path:The value of the Source Path property
(entered by the user) is substituted in place of this
variable when constructing the command line for the
specified helper application.
The Source Path property value in Content Analyzer come
from the <META NAME="SOURCE PATH" . . . tag. The source path
is used by a helper application if you set a value in the
Parameters box.
- Local Path URL / Full URL:If the Local Path
property has a value, it is converted to the equivalent URL
and this URL is substituted in place of this variable when
constructing the command line for the specified helper
application. If the Local Path property does not have a
value, the value of the URL property is substituted in place
of this variable when constructing the command line for the
specified helper application. Note that Content Analyzer
changes the name of this variable from Local Path URL/Full
URL to Local Path URL/URL.
Web
Services Tools
... ws_example.ear |---META-INF |
---application.xml ---ws_example_web.war |---index ...
context>/statelessdocws</context> <option name="source-path">converter.xsl
...
docs.jcu.edu.au/appserver_904_doc/web.904/b10447/tools.htm
- 36k - Supplemental Result -
Cached -
Similar pages
9 Web Services Tools
The Oracle Application Server Web Services assembly tool,
WebServicesAssembler, assists in assembling
Oracle Application Server Web Services. The Web Services
assembly tool takes a configuration file which describes a
Web Service, including the location of the Java classes,
PL/SQL stored procedures or functions, or J2EE EAR, WAR, or
JAR files and produces a J2EE EAR file that can be deployed
under Oracle Application Server Web Services.
This chapter contains the following topics:
Running the Web Services Assembly Tool
Run the
Web Services assembly tool as follows:
java -jar WebServicesAssembler.jar [-debug] -config [file]
or
java -jar WebServicesAssembler.jar [-debug]
Where file is a Web Services assembly tool
configuration file. Without the -config
option, a file named config.xml must be
present in the same directory where
WebServicesAssembler.jar is invoked.
With the -debug option,
WebServicesAssembler displays verbose debugging
comments.
|
Note:
When running
WebServicesAssembler.jar from the
command line, the PATH
environment variable should include the
JDK/bin directory (the
directory with the javac
compiler).
|
Web Services Assembly Tool Configuration File Sample
The
sample configuration file shown in
Example 9-1 defines two services to be wrapped in an
Enterprise ARchive file (EAR). The sample includes
configuration information for services defined with
<stateless-java-service> and <stateful-java-service>
tags.
Example
9-1 Sample Web Services Assembly Tool Configuration
File
<web-service>
<display-name>Web Services Example</display-name>
<description>Java Web Service Example</description>
<!-- Specifies the resulting web service archive will be stored in ./ws_example.ear -->
<destination-path>./ws_example.ear</destination-path>
<!-- Specifies the temporary directory that web service assembly
tool can create temporary files. -->
<temporary-directory>./tmp</temporary-directory>
<!-- Specifies the web service will be accessed in the servlet context
named "/webservices". -->
<context>/webservices</context>
<!-- Specifies the web service will be stateless -->
<stateless-java-service>
<interface-name>oracle.j2ee.ws_example.StatelessExample</interface-name>
<class-name>oracle.j2ee.ws_example.StatelessExampleImpl</class-name>
<!-- Specifies the web service will be accessed in the uri named
"statelessTest" within the servlet context. -->
<uri>/statelessTest</uri>
<!-- Specifies the location of Java class files are under ./src -->
<java-resource>./src</java-resource>
</stateless-java-service>
<stateful-java-service>
<interface-name>oracle.j2ee.ws_example.StatefulExample</interface-name>
<class-name>oracle.j2ee.ws_example.StatefulExampleImpl</class-name>
<!-- Specifies the web service will be accessed in the uri named
"statefulTest" within the servlet context. -->
<uri>/statefulTest</uri>
<!-- Specifies the location of Java class files are under ./src -->
<java-resource>./src</java-resource>
</stateful-java-service>
</web-service>
Web Services Assembly Tool Configuration File Sample
Output
After running the Web Services Assembly tool with
the sample input file shown in
Example 9-1, the generated output is an EAR file
(/tmp/ws_example.ear) The generated
J2EE .ear file, ws_example.ear, has the
structure shown in
Example 9-2.
Example 9-2 Structure of Web Services Assembly
Tool Sample Ear File
ws_example.ear
|---META-INF
| ---application.xml
---ws_example_web.war
|---index.html
---WEB-INF
|------web.xml
------classes
------oracle
-----j2ee
---ws_example
|---StatefulExample.java
|---StatefulExample.class
|---StatefulExampleImpl.java
---StatefulExampleImpl.class
|---StatelessExample.java
|---StatelessExample.class
|---StatelessExampleImpl.java
---StatelessExampleImpl.class
Generating WSDL Files and Client Side Proxies
This
section describes using the <wsdl-gen> and
<proxy-gen> tags in a
WebServicesAssembler configuration file. These
tags controls the options for generating WSDL files and
client-side proxies for Web Services. A client-side
developer can obtain and use the WSDL file or the
client-side proxies to build an application that uses a
Web Service. A server-side developer that is assembling
Web Services can use these file for testing Web
Services.
This section covers the following topics:
Generating and Assembling WSDL Files
Using Oracle Application Server Web Services, a
Web Service developer has several choices for
deciding how the WSDL file that is associated with a
Web Service is generated:
- Using the
<wsdl-gen> tag, you
can specify that WebServicesAssembler
create the WSDL file. At assembly time when the
Web Service is prepared, the
WebServicesAssembler generates and
packages the WSDL file with the Web Service.
Example 9-3 shows a configuration file that
includes the <wsdl-gen> tag.
- Allowing the Oracle Application Server Web
Services runtime to generate the WSDL file when
the WSDL is requested by a Web Service client
(after the WEB Service is deployed). In this
case, you do not specify the
<wsdl-gen>
tag in the configuration file.
- Creating a WSDL file manually. In this case,
use the
<wsdl-gen> tag during
assembly of the J2EE .ear file to specify the
path to the WSDL file. At assembly time when the
Web Service is prepared, the
WebServicesAssembler packages the WSDL
file with the Web Service.
Table 9-1 describes the <wsdl-gen>
WebServicesAssembler configuration file
sub-tags.
|
Note:
Using the <wsdl-gen>
tag, the default behavior is to
package the WSDL into the J2EE .ear
file. To exclude the generated WSDL
from the J2EE .ear file, use
<option name="packageIt"> tag
and set the value to false.
|
Example 9-3 WebServicesAssembler Configuration
File Including <wsdl-gen>
<web-service>
<display-name>Stateless Java Document Web Service</display-name>
<description>Stateless Java Document Web Service Example</description>
<destination-path>./statelessdocws.ear</destination-path>
<temporary-directory>./temp</temporary-directory>
<context>/statelessdocws</context>
<option name="source-path">converter.xsl</option>
<stateless-java-service>
<interface-name>StatelessDoc</interface-name>
<class-name>StatelessDocImpl</class-name>
<uri>/docservice</uri>
<java-resource>./classes</java-resource>
<message-style>doc</message-style>
</stateless-java-service>
<!-- generate the wsdl -->
<wsdl-gen>
<wsdl-dir>wsdl</wsdl-dir>
<!-- over-write a pregenerated wsdl , turn it 'false'
to use the pregenerated wsdl-->
<option name="force">true</option>
<option name="httpServerURL">http://localhost:8888</option>
</wsdl-gen>
</web-service>
Manually Producing a WSDL File
When you do not want to use either the
WebServicesAssembler tool generated WSDL
or the Oracle Application Server Web Services
runtime generated WSDL file, and you want to
supply your own version of the Web Service WSDL
file, perform the following steps:
- Manually create the WSDL file for your
service.
- Name the WSDL file with a name using the
.wsdl extension placed after
the service name. For example,
service1.wsdl for a service named
service1.
- Create a configuration file that
includes the
<wsdl-gen> tag,
including <option name="force">
set to false and <option
name="packageIt"> set to true.
- Place the WSDL file that you create in
the directory specified with the
<wsdl-dir> tag.
- Run the
WebServicesAssembler
with the specified configuration file.
Generating Client-Side Proxies with WSDL
When the <proxy-gen> tag is included
in a configuration file with the <wsdl-gen>,
the generated WSDL is used to generate the proxy
that is placed in the specified directory (this
occurs when WebServicesAssembler runs
during the Web Service assembly process).
Table 8-2 lists the <proxy-gen>
sub-tags.
|
Note:
Using <proxy-gen>,
the generated proxy is not assembled
in the J2EE .ear file. |
Example 9-4 shows a sample configuration file
that includes both the <wsdl-gen> and
the <proxy-gen> tags.
Example 9-4 WebServicesAssembler Configuration
File Including <wsdl-gen>
<web-service>
<display-name>Test</display-name>
<description>Test program</description>
<destination-path>test.ear</destination-path>
<temporary-directory>temp/</temporary-directory><context>/HotelService</context>
<option name="source-path">Workspace1/common/classes</option>
<stateless-java-service>
<interface-name>com.mypackage1.Itest</interface-name>
<uri>/main</uri>
<class-name>com.mypackage1.test</class-name>
</stateless-java-service>
<wsdl-gen>
<wsdl-dir>wsdl</wsdl-dir>
<option name="force">true</option>
<option name="httpServerURL">http://localhost:8888</option>
<option name="packageIt">false</option>
</wsdl-gen>
<proxy-gen>
<proxy-dir>proxy</proxy-dir>
<option name="include-source">true</option>
</proxy-gen>
</web-service>
Web Services Assembly Tool Configuration File
Specification
The
input file for WebServicesAssembler is an
XML file conforming to the Web Services Assembly Tool
configuration file DTD.
Example 9-5 shows the Web Services Assembly Tool
Configuration file DTD.
Example
9-5 Assembly Tool Input File DTD
<?xml version="1.0" encoding="UCS-2"?>
<!-- Specify the properties of the web services to be assembled. -->
<!ELEMENT web-service ((display-name)?,(description)?,destination-path,temporary-directory,context,(datasource-JNDI-name)?,(stateful-java-service)*,(stateless-java-service)*,(stateless-stored-procedure-java-service)*,(stateless-session-ejb-service)*,(jms-doc-service)*,(option)*,(wsdl-gen)?,(proxy-gen)?)>
<!ELEMENT display-name (#PCDATA)*>
<!ELEMENT description (#PCDATA)*>
<!-- Specify the full path of the resulting EAR file. For example,
"/home/demo/webservices.ear" -->
<!ELEMENT destination-path (#PCDATA)*>
<!-- Specify a directory where the assembly tool can create temporary
directories and files. -->
<!ELEMENT temporary-directory (#PCDATA)*>
<!-- Specify the context root of the web services. For example, "/webservices". -->
<!ELEMENT context (#PCDATA)*>
<!-- for specifying database resource refs -->
<!ELEMENT datasource-JNDI-name (#PCDATA)*>
<!-- Specify the properties of a stateful Java service -->
<!ELEMENT stateful-java-service ((interface-name)?,class-name,uri,(java-resource)*,(ejb-resource)*,(scope)*,(session-timeout)*,(message-style)?)>
<!-- Specify the properties of a stateless Java service -->
<!ELEMENT stateless-java-service ((interface-name)?,class-name,uri,(java-resource)*,(ejb-resource)*,(message-style)?)>
<!-- Specify the properties of a stateless stored procedure Java service -->
<!ELEMENT stateless-stored-procedure-java-service ((interface-name)?,(class-name)?,uri,database-JNDI-name,(java-resource)?,(jar-generation)?)>
<!-- Specify the properties of a stateless session ejb service -->
<!ELEMENT stateless-session-ejb-service (path,uri,ejb-name,(ejb-resource)*)>
<!-- Specify the java interface which defines the public methods to be exposed
in the web service. For example, "com.foo.myproject.helloWorld". -->
<!ELEMENT interface-name (#PCDATA)*>
<!-- Specify the java class to be exposed as a web service. If interface-name is
not specified, all the public methods in this class will be exposed. For example,
"com.foo.myproject.helloWorldImpl". -->
<!ELEMENT class-name (#PCDATA)*>
<!-- Specify the uri of this service. This uri is used in the URL to access the
WSDL and client jar, and invoke the web service. For example, "/myService". -->
<!ELEMENT uri (#PCDATA)*>
<!--
Specify the java resources used in this service.
The value can be a directory or a file that implements the web services. If it
is a directory, all the files and subdirectories under the directory are copied
and packaged in the Enterprise ARchive. If the java resource should belong to a
java package, you should either package it as a jar file and specify it as a
java resource, or create the necessary directory and specify the directory which
contains this directory structure as java resource. For example, you want to
include "com.mycompany.mypackage.foo" class as a java resource of the web
services, you can either package this class file in foo.jar and specify
<java-resource>c:/mydir/foo.jar</java-resource>, or place the class under
d:/mydir/com/mycompany/mypackage/foo.class and specify the java resource as
<java-resource>c:/mydir/</java-resource>.
-->
<!ELEMENT java-resource (#PCDATA)*>
<!-- Specify the ejb resources used in this service. ejb-resource should be a
jar file that implements a enterprise java bean. -->
<!ELEMENT ejb-resource (#PCDATA)*>
<!-- Specify the database JNDI name for stateless PL/SQL web service. -->
<!ELEMENT database-jndi-name (#PCDATA)*>
<!-- Specifies the path of the EJB jar file to exposed as web services. -->
<!ELEMENT path (#PCDATA)*>
<!-- Specify the ejb-name of the session bean to be exposed as web services.
ejb-name should match the <ejb-name> value in the META-INF/ejb-jar.xml of the bean. -->
<!ELEMENT ejb-name (#PCDATA)*>
<!-- Specify scope of Stateful Java service -->
<!ELEMENT scope (#PCDATA)*>
<!-- Specify session timeout of Stateful Java service -->
<!ELEMENT session-timeout (#PCDATA)*>
<!-- Specify the directory location of the generated wsdl-->
<!ELEMENT wsdl-dir (#PCDATA)*>
<!-- Specify that wsdl generation is to happen 'force' 'httpServerURL' 'packageIt'-->
<!ELEMENT wsdl-gen (wsdl-dir,(option)*)>
<!-- Specifyg the directory location of the generated proxy-->
<!ELEMENT proxy-dir (#PCDATA)*>
<!ELEMENT option (#PCDATA)*>
<!ATTLIST option name CDATA #REQUIRED>
<!-- Specifying that proxy generation is asked for , it can have optional tags as
'include-source' 'wsdl-location' -->
<!ELEMENT proxy-gen (proxy-dir,(option)*)>
<!ELEMENT jar-generation (db-package-name,db-schema,db-url,prefix,(method-name)*)>
<!ELEMENT database-JNDI-name (#PCDATA)*>
<!ELEMENT db-package-name (#PCDATA)*>
<!ELEMENT db-url (#PCDATA)*>
<!ELEMENT db-schema (#PCDATA)*>
<!ELEMENT prefix (#PCDATA)*>
<!ELEMENT method-name (#PCDATA)*>
<!-- specify the message style ,if this tag is not present it is considered to have 'rpc' ..it can have values of 'rpc' or 'doc' or 'document' -->
<!ELEMENT message-style (#PCDATA)*>
<!ELEMENT connection-factory-resource-ref (#PCDATA)*>
<!ELEMENT topic-resource-ref (#PCDATA)*>
<!ELEMENT queue-resource-ref (#PCDATA)*>
<!--Resource ref of the return destination factory-->
<!ELEMENT reply-to-connection-factory-resource-ref (#PCDATA)*>
<!--Resource ref of the return destination Topic. -->
<!ELEMENT reply-to-topic-resource-ref (#PCDATA)*>
<!--Resource ref of the return destination Queue. -->
<!ELEMENT reply-to-queue-resource-ref (#PCDATA)*>
<!--jms-priority ,jms-message-type,jms-delvery-mode ,jms-expiration The JMS properties are only set for enqueuing operations, i..e, for send operations only. -->
<!ELEMENT jms-priority (#PCDATA)*>
<!ELEMENT jms-message-type (#PCDATA)*>
<!ELEMENT jms-delivery-mode (#PCDATA)*>
<!ELEMENT jms-expiration (#PCDATA)*>
<!-- operation property is optional. Possible values for this parameter are: send, receive, and both. If not provided, the value defaults to both. -->
<!ELEMENT operation (#PCDATA)*>
<!ELEMENT jms-doc-service (uri,connection-factory-resource-ref,(topic-resource-ref)?,(queue-resource-ref)?,(reply-to-connection-factory-resource-ref)?,(reply-to-topic-resource-ref)?,(reply-to-queue-resource-ref)?,(jms-priority)?,(jms-message-type)?,(jms-delivery-mode)?,(jms-expiration)?,(operation)?)>
Web Services Assembly Tool Limitations
The WebServicesAssembler tool has the
following limitations:
- No Upload/download capabilities: the
Web Services Assembly tool does not upload Java
classes from a client system to a server or download
a generated EAR file back to a client system.
- Does not support advanced
configuration tasks: for example, the Web Services
Assembly tool is not able to control the security
options for a Web Services Servlet, cannot secure an
EJB, secure welcome files, or perform other
administrative tasks.
|
| |
|