Hello, I've been playing with XDoclet builds from CVS for the past few weeks and tried the 1.2.0-beta1 build last night and have run across several issues. I tried to check these against the bug database and the mailing lists so that I don't bring up topics already discussed and apologize in advance if I missed something. I am seeing these problems using a CVS build of XDoclet from 3 days ago on Sun JVM 1.4.1 on Red Hat Linux 8.0 XDoclet from 1 day ago on Apple's JVM 1.3.1 on Mac OS 10.2.1 both with JBoss 3.2.0 beta and a Struts nightly from 2002-09-28.
1) @ejb.facade. I tried using this tag and the associated <entityfacade/> subtask on a simple EntityBean. The resulting Session bean would not compile because it did not qualify the packages for the SessionContext or any of the exceptions thrown and included a data object for my EntityBean when I am not generating those (I am using the Value Objects in their place). 2) <strutsvalidationxml/>. I am not sure if I am using this feature correctly. I have an entity bean with two struts-forms associated with them: @struts.form name="Add" @struts.form name="Edit" I associated methods with them using @struts.form-field form-name="Add" or @struts.form-field form-name="Edit". The associated Form beans are generated correctly. I added a @struts.validator tag a field of the EntityBean and reran EjbDoclet and WebDoclet. A validation.xml file was created, but no forms or fields are listed in that file. Specifically, from MemberBean.java I have: /** * @ejb.interface-method * @ejb.persistent-field * * @struts.form-field * form-name="Add" * * @struts.form-field * form-name="Edit" * * @struts.validator * type="required" * * @jboss.column-name * name="username" */ public abstract String getUsername(); /** * @ejb.interface-method */ public abstract void setUsername(String username); I run webdoclet against both the generated Form bean and the Entity Bean but no forms appear in the generate validation.xml. I have tried running webdoclet only on the Form bean and I have moved the @struts.validator tag to the setter method and those didn't work either. What I would like to have happen is to create a Form bean from my Entity bean and have that form bean be correctly validated by Struts, not by my application logic using XDoclet. I think that is what the strutsvalidationxml subtask and tags are meant to provide and am not sure if there is a bug or if I'm not using them correctly. 3) Util classes. This is probably more of a feature request then anything but, I have a session bean acting as a facade for an entity bean (I hand wrote the facade due to the problems above). The Util class created for this session bean defaulted to using COMP_NAME for both the local and remote interfaces. A remote client, however, can't get to the COMP_NAME so all the lookups fail. Changing the @ejb.util tag to generate physical JNDI names works, but it changes both the local and remote home getters. Would it make sense for the default to use the physical JDNI name for remote and the logical name for local? Sorry for the length of this mail. Please let me know additional information is needed. --Chris ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
