[XDoclet-JIRA] Commented: (XDT-1690) Tag jboss.read-ahead must be on method level

"Christian Nolte (JIRA)" <[email protected]> Mon, 6 Aug 2007 10:28:58 -0500 (CDT)
Newsgroups gmane.comp.java.xdoclet.devel
Message-ID <125445706.1186414138627.JavaMail.j2ee@atlassian01.managed.contegix.com>
    [ http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_17802 ] 

Christian Nolte commented on XDT-1690:
--------------------------------------

Sorry. This is no bug but a failure on my side... I just saw the documentation on jboss.query. This BUG can be closed.

> Tag jboss.read-ahead must be on method level
> --------------------------------------------
>
>                 Key: XDT-1690
>                 URL: http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1690
>             Project: XDoclet
>          Issue Type: Bug
>    Affects Versions: 1.2.3
>            Reporter: Christian Nolte
>            Assignee: xdoclet-devel (Use for new issues)
>
> The tag jboss.read-ahead has to be specified on class-level. This leads to an invalid jbosscmp-jdbc entity-entry like:
> <!-- ... -->
> <entity>
>   <read-ahead>
>     <!-- ... -->
>   </read-ahead>
>   <!-- ... -->
>   <query>
>     <!-- ... -->
>   </query>
> </entity>
> It must be:
> <entity>
>   <!-- ... -->
>   <query>
>     <!-- ... -->
>     <read-ahead>
>       <!-- ... -->
>     </read-ahead>
>   </query>
> </entity>
> This tag has therefor to be specified on method-level on methods which specifiy jboss.query, jboss.dynamic-query and so on.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/xdoclet/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/