Skip to content
This repository has been archived by the owner on Jun 14, 2024. It is now read-only.

Section "Packaging Resource Adapter Archives" contains redundant and repetitive information. #254

Open
DmitriGit opened this issue Oct 7, 2021 · 1 comment

Comments

@DmitriGit
Copy link
Contributor

Hello,

in the section "https://eclipse-ee4j.github.io/jakartaee-tutorial/#packaging-resource-adapter-archives" :

1) the first paragraph :
"..... A resource adapter can be deployed on any Jakarta EE server, much like a Jakarta EE application. A RAR file can be contained in an Enterprise Archive (EAR) file, or it can exist as a separate file."

2) and the last paragraph :
"A RAR file can be deployed on the application server as a standalone component or as part of a larger application. In both cases, the adapter is available to all applications using a lookup procedure."

contain the same information.

Can I send you my version of that section that merge the content of these two similar paragraphs?

Thank you,
Dmitri.

@DmitriGit
Copy link
Contributor Author

DmitriGit commented Oct 8, 2021

My proposal is the following:

"
Packaging Resource Adapter Archives

A Resource Adapter Archive (RAR) file stores XML files, Java classes, and other objects for Jakarta EE Connector applications.

The RAR file contains

  • A JAR file with the implementation classes of the resource adapter
  • An optional META-INF/ directory that can store an ra.xml file and/or an application server–specific deployment descriptor used for configuration purposes

A RAR file can be deployed on the application server as a standalone component (much like a Java EE application) or as part of a larger application (for example, it can be contained in an Enterprise Archive (EAR) file). In both cases, the adapter is available to all applications using a lookup procedure.
"

Let me know if you like my version so I modify the corresponding "asciidoc" and commit it.

Thank you and have a nice day,
Dmitri.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant