The changes I made are to the jboss version of xdoclet (actually to the stuff in the xdoclet.modules.jboss.ws package only) as what is distributed with jboss doesn't currently work with the head version of xdoclet.
the changes I have made are mostly to the template, but here is a list
of what I have done:
I moved the resources directory into the ws directory
I edited JBossNetSubTask.java so it wouldn't fail to compile
Then I made quite a number of changes to the template
I have removed the <ejb-ref> tags
@jboss-net.web-service:
added the scope attribute
I have also added to the template the ability to include the
JBossAuthenticationHandler and/or JBossAuthorizationHandler in the
requestFlow
@jboss-net.authentication
domain="myDomain"
@jboss-net.authorization
domain="myDomain"
allowed-roles="foo,bar,baz" <- optional defaults to "*" in the
JBossAuthorizationHandler
denied-roles="admin" <- optional
Since I sometimes want to pass entity bean data back to the client from
a session bean, and I prefer to use dataobjects I added to the
xml-schema tag a data-object attribute that causes the dataobject to be
used for the typeMapping rather than the ejb.
@jboss-net.xml-schema
urn="ReportList"
data-object="true"
There are probably better ways to implement the changes I made in the
template, but I am no xdoclet guru so I stuck with what I was first
able to get working.
Also I haven't added any of the tag changes to the xml documentation
(mostly because I am not sure I understand how that works, and haven't
taken the time to figure it out yet)
Jason Essington
Green River Computing Services
307-367-2276
[EMAIL PROTECTED]
jboss.net_module.tgz
Description: GNU Zip compressed data
On Wednesday, September 25, 2002, at 01:38 AM, Jung , Dr. Christoph wrote: > Jason, > > We decided to get rid of the redundante <ejb-ref/> tags inside the > web-service.xml - I am not sure > whether this is already reflected in the xdoclet template, that is why > I > marked this feature as "deprecated". > > It has nothing to do with the authentication and authorization handlers > which allow you to > authenticate (sic!) and authorize (sicut!) an incoming web service > call per > web-service transport > chain (and not globally through the servlet configuration) against the > specified security domain. > > I would be very interested in your adaptions, BTW. Is this against the > jboss-version of xdoclet? > > CGJ > > -----Ursprüngliche Nachricht----- > Von: Jason Essington [mailto:[EMAIL PROTECTED]] > Gesendet: Dienstag, 24. September 2002 21:42 > An: [EMAIL PROTECTED] > Betreff: [JBoss-user] jboss.net changes and xdoclet > > > I have hacked the jboss.net module (supplied in the cvs version of > jboss) to work with the latest version of xdoclet. > > It has been working fine, but since the recent changes to jboss.net I > am getting this warning upon deployment: > > 13:28:31,238 WARN [AxisService] Web Service Deployment > org.jboss.deployment.DeploymentInfo@90610f9c { > url=file:/Users/jason/jboss-3.2.0beta/server/default/tmp/deploy/server/ > default/deploy/hedgehog-app.ear/72.hedgehog-app.ear-contents/hedgehog- > soap.wsr } > deployer: org.jboss.net.axis.server.AxisService@1001ca > status: Starting > state: START_DEPLOYER > watch: > jar:file:/Users/jason/jboss-3.2.0beta/server/default/tmp/deploy/server/ > default/deploy/hedgehog-app.ear/72.hedgehog-app.ear-contents/hedgehog- > soap.wsr!/META-INF/web-service.xml > lastDeployed: 1032895699652 > lastModified: 1032895699000 > mbeans: > makes use of the deprecated ejb-ref feature. Please adjust any > ejb-providing service tag inside your web-service.xml pointing to > ejb/Login to use the absolute Login instead. > > It doesn't seem to effect how jboss.net works, but I would like to > adjust the xdoclet module's xdt file to work properly without raising > this warning. > > What is this warning trying to tell me (I'm kinda dense sometimes)? > Should I > remove the <ejb-ref> tags and just use the ejb/[beanName] jndi > name? > > does anyone have a sample web-service.xml file that conforms to the > newer requirements? > > also I have not quite nailed down when, why and how to use > JBossAuthenticationHandler and JBossAuthorizationHandler. > > is it as simple as adding: > <handler type="java:org.jboss.net.axis.server. > JBossAuthenticationHandler"/> > and / or > <handler type="java:org.jboss.net.axis.server. > JBossAuthorizationHandler"/> > in your <requestFlow>? or is there more to it than that? > > Under what circumstances would I want to use these handlers? > > Thanks > > -jason > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > ########################################### > > This message has been scanned by F-Secure Anti-Virus for Microsoft > Exchange. > For more information, connect to http://www.F-Secure.com/ > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > >
