XDoclet: Attribute-Oriented Programming - Tag Reference

##### XDoclet

- Overview
- News and Status
- Download/Installation
- Using XDoclet
- Best Practices
- FAQ
- License

##### Ant Task Reference

- <doclet .. />
- <ejbdoclet .. />
- <hibernatedoclet .. />
- <jdodoclet .. />
- <jmxdoclet .. />
- <mockdoclet .. />
- <portletdoclet .. />
- <springdoclet .. />
- <tapestrydoclet .. />
- <webdoclet .. />
- <wseedoclet .. />

##### Tag Reference

- apache (@soap @struts @axis @tapestry)
- bea (@weblogic)
- borland (@bes)
- caucho (@resin)
- ejb (@ejb @dao)
- exolab (@castor)
- hp (@hpas)
- hibernate (@hibernate)
- ibm (@websphere)
- java (@javabean)
- jboss (@jboss)
- jdo (@jdo)
- jmx (@jmx)
- jsf (@jsf)
- macromedia (@jrun)
- mockobjects (@mock)
- mvcsoft (@mvcsoft)
- mx4j (@mx4j)
- objectweb (@jonas)
- oracle (@oc4j)
- orion (@orion)
- portlet (@portlet)
- pramati (@pramati)
- spring (@spring)
- sun (@sunone)
- sybase (@easerver)
- tjdo (@tjdo)
- web (@web @jsp)
- webwork (@webwork)
- wsee (@wsee)
- xdoclet (@xdoclet @doc @msg)

##### Feature Documentation

- Using Value Objects
- EJB Environment Handling

##### Advanced

- Maven Plug-in
- Merge Points
- IDE Integration
- Migration from EJBDoclet
- Ant 1.5 Troubleshooting

##### Community

- Feedback
- Resources
- Tools

##### Development

- Developer Guide
- Javadoc (API)
- Template Language (*.xdt)
- XJavaDoc Site

##### Search XDoclet

##### Project Documentation

- About XDoclet
- Project Info
- Project Reports
- Development Process

## @Sybase Tag Reference

Tags for creation of EAServer specific resources

Applies to: all EJB types on class level

### @Sybase Class Level Tags

@easerver.ejb-ref
@easerver.resource-ref

### @Sybase Method Level Tags

### @Sybase Field Level Tags

## @Sybase Class Level Tag Usage

### @easerver.ejb-ref (0..*)

The ejb-ref element gives a mapping between the name of an ejb reference (ejb-ref-name, provided by the Bean Developer) and the JNDI name of the referenced bean (jaguar-link, provided by the Application Assembler). There should be a corresponding @ejb.ejb-ref tag present. NB If the beans are being deployed as part of the same EJB jar or application EAR, this tag may not be needed as EAServer can usually "guess" the relevant ejb link names.

Parameter | Type | Applicability | Description | Mandatory
--- | --- | --- | --- | ---
ejb-ref-name | text |  | The ejb-ref-name element gives the name of an ejb reference. It is provided by the Bean Developer, and should match the ref-name parameter of an @ejb.ejb-ref tag. | true
jaguar-link | text |  | The jaguar-link element gives the JNDI name of the referenced ejb. It is provided by the Application Assembler. | true

### @easerver.resource-ref (0..*)

The resource-ref element gives a mapping between the name of a resource reference (res-ref-name, provided by the Bean Developer) and its resource (res-link, provided by the Application Assembler). There should be a corresponding @ejb.resource-ref tag present.

Applies to: Used in Entity, MessageDriven, and Session beans.

Parameter | Type | Applicability | Description | Mandatory
--- | --- | --- | --- | ---
res-ref-name | text |  | The res-ref-name element gives the name of a resource. It is provided by the Bean Developer, and should match the res-ref-name parameter of an @ejb.resource-ref tag. | true
res-link | text |  | The res-link element gives the value of the resource. It is provided by the Application Assembler. This will depend on the type (res-type) of the resource e.g. for datasources it will be the connection cache name, for mail sessions it will be the SMTP server name. | true

## @Sybase Method Level Tag Usage

## @Sybase Field Level Tag Usage