Connecting to WebDAV servers via the Java™ connector architecture

• US 20040168128A1
• Filed: 02/21/2003
• Published: 08/26/2004
• Est. Priority Date: 02/21/2003
• Status: Abandoned Application

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Kinner, Jason, Snyder, Joseph J., Friedman, Richard
• Application Number:
  US10/371,284
• Publication Number:
  US 20040168128A1
• Time in Patent Office: Days
• US Class Current: 715/530
• CPC Class Codes: G06F 40/117 Tagging; Marking up details of markup languages G06F40/143; Designating a block; Setting of attributes style sheets, e.g. eXtensible Stylesheet Language Transformation [XSLT], G06F40/154

Abstract

A method that conforms to a Java™ Connector Architecture (JCA) specification for accessing WebDAV-compliant servers as enterprise resources is provided. The method comprises providing a WebDAV-compliant connector communicating with a multilayer resource adapter API, and creating a SAX-based processing pipeline. The method further comprises processing property values using the processing pipeline, using a MultiStatus Response Record to map a resource URL to a set of properties, and implementing accessor methods for marshaling property values to and from an XML format. The method further comprises using the processed property values to enable transmitting WebDAV messages between a client and a server.

Claims

1. A system operable to support Web-based Distributed Authoring and Versioning (WebDAV) protocol, said system comprising:

a plurality of applications and server implementations;

a WebDAV-compliant connector that conforms to a Java™

Connector Architecture (JCA) specification, said WebDAV-compliant connector operable to access WebDAV-compliant servers as enterprise resources; and

a resource adapter application programming interface (API) operable to communicate with said WebDAV-compliant connector.

2. The system of claim 1 wherein said WebDAV-compliant connector is operable to access said WebDAV-compliant servers from any Java™

or Java™

version 2 Enterprise Edition (J2EE) application.

3. The system of claim 1 wherein said WebDAV-compliant connector is operable to be invoked from any application that can invoke Java™

code.

4. The system of claim 1 wherein the architecture of said resource adapter API further comprises an EnterpriseJavaBeans™

(EJB) layer.

5. The system of claim 1 wherein the architecture of said resource adapter API further comprises a servlet layer.

6. The system of claim 1 wherein the architecture of said resource adapter API further comprises a JCA layer.

7. The system of claim 1 wherein said resource adapter API is operable to encode property values using well-formed extensible Markup Language (XML) via a Simple API for XML (SAX)-based processing pipeline API.

8. The system of claim 7 wherein the architecture of said processing pipeline API is operable to implement accessor methods for marshaling property values to and from an XML format.

9. The system of claim 1 wherein said WebDAV-compliant connector conforms to the Java™

Connector Architecture (JCA), version 1.0 specification.

10. A method that conforms to a Java™

Connector Architecture (JCA) specification for accessing WebDAV-compliant servers as enterprise resources, said method comprising;

providing a WebDAV-compliant connector, said WebDAV-compliant connector communicating with a multilayer resource adapter API;

creating a SAX-based processing pipeline;

processing property values using said processing pipeline;

using a MultiStatus Response Record to map a resource URL to a set of properties;

implementing accessor methods for marshaling property values to and from an XML format; and

using said processed property values to enable transmitting WebDAV messages between client and server.

11. The method of claim 10 wherein creating said SAX-based processing pipeline comprises implementing an AbstractValueFormatter WebDAVclass, thereby extending a SAX DefaultHandler class.

12. The method of claim 11 wherein creating said SAX-based processing pipeline comprises overriding XML parsing methods in which property values are encoded in said WebDAV-compliant server.

13. The method of claim 10 further comprising reporting and storing errors as WebDAVException(s).

14. The method of claim 10 wherein said resource adapter API provides a capability selected from the group consisting of lock management, connection management, pooling, and support of a Distributed Authoring Searching and Locating (DASL) protocol.

15. The method of claim 10 wherein said WebDAV-compliant connector conforms to the Java™

Connector Architecture (JCA), version 1.0 specification.

16. A system operable to support Web-based Distributed Authoring and Versioning (WebDAV) protocol, said system comprising:

means for providing a WebDAV-compliant connector, said WebDAV-compliant connector communicating with a multilayer resource adapter API;

means for creating a SAX-based processing pipeline;

means for processing property values using said processing pipeline;

means for using a MultiStatus Response Record to map a resource URL to a set of properties;

means for implementing accessor methods for marshaling property values to and from an XML format; and

means for using said processed property values to enable transmitting WebDAV messages between client and server.

17. The system of claim 16 wherein said means for creating said SAX-based processing pipeline comprises means for implementing an AbstractValueFormatter WebDAVclass, thereby extending a SAX DefaultHandler class.

18. The system of claim 17 wherein said means for creating said SAX-based processing pipeline comprises means for overriding XML parsing methods in which property values are encoded in said WebDAV-compliant server.

19. The system of claim 16 further comprising means for reporting and storing errors as WebDAVException(s).

20. The system of claim 16 wherein said resource adapter API provides means for a capability selected from the group consisting of lock management, connection management, pooling, and support of a Distributed Authoring Searching and Locating (DASL) protocol.

21. Computer-executable software code stored to a computer-readable medium, said computer-executable software code comprising:

code for processing property values using a processing pipeline;

code for using a MultiStatus Response Record to map a resource URL to a set of properties;

code for implementing accessor methods for marshaling property values to and from an XML format; and

code for using said processed property values to enable transmitting WebDAV compliant messages between a client and a server.

22. The computer-executable software code of claim 21 further comprising code for creating a SAX-based processing pipeline comprising code for implementing an AbstractValueFormatter WebDAVclass, thereby extending a SAX DefaultHandler class.

23. The computer-executable software code of claim 21 comprising code for overriding XML parsing methods in which property values are encoded in said WebDAV-compliant server.

24. The computer-executable software code of claim 21 further comprising code for reporting and storing errors as WebDAVException(s).

25. The computer-executable software code of claim 21 comprising code for a capability selected from the group consisting of lock management, connection management, pooling, and support of a Distributed Authoring Searching and Locating (DASL) protocol.