> > 2. There is somthing that frustrate me in home-local.j : we > define the > > comp and jndi attributes with "Local" added but nowhere else do we > refer > > these. Then some work are needed when migrating from > remote to local > > IF. I personally use a hacked version of home-local.j that > looks like > > home.j for these 2, but I am wondering if I am the only one to find > this > > cumbersome. At least there is a bug report linked to that > issue. To > > support something stronger we need to patch the ejb-jar.j and the > > ejb-vendorsss.j files I guess. > > We should move it to getCompNameFor(), and I think we can > make it like home.j (without the Local postfix) if > view-type!="both", if "both" then append Local.
OK I have done that. "Local" is only added for beans of type "both". I also default localjndiname from jndiname if local-jndi-name is not defined. I add "Local" to localjndiname and compname for beans of type "both". I also change the name of ejb-ref-name in this case. When a bean is local, I don't need to specify local-jndi-name, it will default from jndi-name if any and from getCompNameFor in last chance. But still I don't understand the need for a local jndi-name. It is not used anywhere except in weblogic.xml. So I wonder why the need of local-jndi-name in ejb:bean. That's the reason I did this defaulting stuff. The swicth from remote to/from local is now simplified, that was my main goal : you change a ejb:bean from "remote" to "local" simply, then you change all ejb:ejb-ref view-type in the same manner. I commit as it is, let me know if you got problem on websphere and weblogic. > Ara. Vincent _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
