Re: At wits end with jboss-struts new build system!

OK, I've now given up trying to fix this problem. I have discovered that
the keel-server.jar is where the server side code used to reside with the
configuration files in the .war file. I manually set this situation up but
merely got stuck further on.

Each time I get a little further in understanding where things should go
for the jboss build I discover a multitude of new errors. I simply don't
have the skills to try to fix this build or even to just patch it to get
it working until it get's fixed for real.

I would suggest that you warn new folk of this situation in the wiki
please-start-here section and save them many days of running in the dark
with scissors. Also, is is not possible to run a nightly ant test with the
jboss and other configurations?

Mike, please let me know when you get around to fixing this situation. I
was really hoping to get this new build system working as I have a 8-10
minute round trip code-clean-build-deploy-test cycle with Keel 2.0 and I
haven't managed to get a working eclipse debug system up either. I'll
never release my app given this situation. For some reason my project is
very sensitive to changes necessitating a clean (and mostly manually
deleting certain build directories) every time.

Thanks,
Max


> Hi Mike,
>
> I've found an additional problem in the new build system for jboss-struts:
>
> The ejb-jar.xml and jboss.xml configuration files are not created in the
> build process. I copied them into my deployment manually, but the keel
> server still does not start. I've got a breakpoint in the ejbCreate()
> funtion in comm-jbossmq KeelServerBean class but it is never called.
>
> Can you direct me to where/how this ejb is instantiated.
>
> Thanks,
> Max
>
> PS: My below message may have been swallowed by the mail list server.
>
>
>
>
> Mike,
>
> So far I've found the following errors in the build process (the example
> app still does not run though - it hangs on loading the navigate page):
>
> 1) Location of server directory is wrong. The build process creates the
> server directory in example-projects\jboss-struts\server instead of
> example-projects\jboss-struts\webapps\keel\server.
>
> 2) The web.xml file fails on deploy because the following section appears
> at the end of the file instead of the beginning:
>
>   <context-param>
>        <param-name>jms-client</param-name>
>        <param-value>org.keel.comm.jbossmq.clients.KeelJmsClientJbossMQ</param-value>
>   </context-param>
>
> 3) The following section does not exist in the new buidl system web.xml.
> I'm not sure if it is no longer required. I've tried to copy it from my
> old Keel 2.0 web.xml but it generates errors on deploy.
>
>   <resource-ref>
>   	<description>JMS Queue For Keel Requests</description>
>   	<res-ref-name>jms/Requests</res-ref-name>
>   	<res-type>javax.jms.Queue</res-type>
>   	<res-auth>Container</res-auth>
>   </resource-ref>
>
>  <resource-ref>
>   	<description>JMS Queue Factory</description>
>   	<res-ref-name>jms/QueueFactory</res-ref-name>
>   	<res-type>javax.jms.QueueConnectionFactory</res-type>
>   	<res-auth>Container</res-auth>
>   </resource-ref>
>
> Hope this helps.
> Max
>
>
> _______________________________________________
> User mailing list
> [email protected]
> http://lists.keelframework.org/listinfo.cgi/user-keelframework.org
>