The following comment has been added to this issue:

     Author: Vassil Dichev
    Created: Sat, 11 Sep 2004 8:11 AM
       Body:
Hi there,

Issue XDT-1026 is still not fixed, I think; the following fix still does not solve the 
problem:
"[Xdoclet-devel] CVS: 
xdoclet/modules/hibernate/src/xdoclet/modules/hibernate/resources 
jboss-service.xdt,1.15,1.16, David M. Lloyd"

I think editing jboss-service.xdt won't cut it, at least on xdoclet 1.2.1 it didn't 
(Update: I just checked that in CVS the same problem appears). It only worked for me 
after I removed the entry for useOuterJoin from jboss-service.xdt altogether.

After some debugging it turns out that showSql exhibits the same behavior: even if 
it's not mentioned in the ant task at all *and* ifHasConfigParam is specified in the 
xdt. I think you have already figured it out: they are both boolean.

Upon further investigation I found that getShowSql and getUseOuterJoin from 
xdoclet.modules.hibernate.JBossServiceSubTask both return boolean. All other getters 
return String, and when they are missing, null is returned. For the boolean getters, 
there's no way to indicate that the attribute is missing! So showSql and useOuterJoin 
is either false or true.

You can easily observe this if you set the following line in log4j.properties:
log4j.category.xdoclet.tagshandler.ConfigTagsHandler=DEBUG

For instance, I got this output:

....
[hibernatedoclet] (ConfigTagsHandler.getConfigParameter 83  ) subtask=class 
xdoclet.modules.hibernate.JBossServiceSubTask
[hibernatedoclet] (ConfigTagsHandler.getConfigParameter 84  ) 
currentConfigParamIndex=-1
[hibernatedoclet] (ConfigTagsHandler.getConfigParameter 85  ) currentConfigParam=null
[hibernatedoclet] (ConfigTagsHandler.getConfigParameter 86  ) paramName=showSql
[hibernatedoclet] (ConfigTagsHandler.getConfigParameter 193 ) Config param 
found:showSql
[hibernatedoclet] (ConfigTagsHandler.getConfigParameter 202 ) configValue=false
....
[hibernatedoclet] (ConfigTagsHandler.getConfigParameter 83  ) subtask=class 
xdoclet.modules.hibernate.JBossServiceSubTask
[hibernatedoclet] (ConfigTagsHandler.getConfigParameter 84  ) 
currentConfigParamIndex=-1
[hibernatedoclet] (ConfigTagsHandler.getConfigParameter 85  ) currentConfigParam=null
[hibernatedoclet] (ConfigTagsHandler.getConfigParameter 86  ) 
paramName=userTransactionName
[hibernatedoclet] (ConfigTagsHandler.getConfigParameter 193 ) Config param 
found:userTransactionName
[hibernatedoclet] (ConfigTagsHandler.getConfigParameter 202 ) configValue=null
....

Let me point out again that I haven't mentioned showSql or useOuterJoin anywhere in 
the ant task and I've edited my jboss-service.xdt to look like this:

....
     <XDtConfig:ifHasConfigParam paramName="showSql">
       <attribute name="ShowSql"><XDtConfig:configParameterValue 
paramName="showSql"/></attribute>
     </XDtConfig:ifHasConfigParam>
     <XDtConfig:ifHasConfigParam paramName="useOuterJoin">
       <attribute name="UseOuterJoin"><XDtConfig:configParameterValue 
paramName="useOuterJoin"/></attribute>
     </XDtConfig:ifHasConfigParam>
....

What is the purpose of returning boolean in the getters when it will be converted to a 
String anyway?

Hope that helps,
Vassil Dichev

---------------------------------------------------------------------
View this comment:
  
http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1059?page=comments#action_14822

---------------------------------------------------------------------
View the issue:
  http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1059

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: XDT-1059
    Summary: jbossservice UseOuterJoin not supported anymore in hibernate 2.1.6
       Type: Bug

     Status: Open
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: XDoclet
 Components: 
             Hibernate Module
   Versions:
             1.2.1
             1.2.2

   Assignee: xdoclet-devel (Use for new issues)
   Reporter: Thomas Herbst

    Created: Tue, 7 Sep 2004 3:15 PM
    Updated: Sat, 11 Sep 2004 8:11 AM

Description:
With hibernate 2.1.6 the UseOuterJoin is removed from the 
net.sf.hibernate.jmx.HibernateService MBean so the attribute can not be set default to 
false, because jboss cannot deploy the service anymore.


21:31:02,500 INFO  [NamingService] Started jnpPort=1099, rmiPort=1098, backlog=5
0, bindAddress=/0.0.0.0, Client SocketFactory=null, Server SocketFactory=org.jbo
[EMAIL PROTECTED]
21:31:03,721 INFO  [ServiceConfigurator] Problem configuring service jboss.jca:s
ervice=HibernateServices
org.jboss.deployment.DeploymentException: No Attribute found with name: UseOuter
Join
        at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.ja
va:321)
        at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigura
tor.java:160)
        at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java
:114)
        at org.jboss.system.ServiceController.install(ServiceController.java:198
)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM. 
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
_______________________________________________
xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel

Reply via email to