[
https://issues.apache.org/jira/browse/JUDDI-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12836871#action_12836871
]
Tom Cunningham commented on JUDDI-364:
--------------------------------------
I got this one, I have a fix for it, I'll try to have it in tonight.
The reason why we won't add it to the build isn't because we don't want to
support jboss API changes, it's because we'd like to avoid any extraneous
dependencies. I will set up a build file for this though.
> JBossAuthenticator will not compile against release. Documentation of this
> class is out of date
> ------------------------------------------------------------------------------------------------
>
> Key: JUDDI-364
> URL: https://issues.apache.org/jira/browse/JUDDI-364
> Project: jUDDI
> Issue Type: Bug
> Affects Versions: 3.0.1
> Reporter: Ryan Hochstetler
> Assignee: Tom Cunningham
> Fix For: 3.0.2
>
>
> JBossAuthenticator in docs does not compile against the present release as
> distributed. The documentation which refers to this example class is out of
> date, also.
> 1.) JBossAuthenticator does not fully implement
> org.apache.juddi.v3.auth.Authenticator. It is missing UddiEntityPublisher
> identify(String authInfo, String authorizedName)
> 2.) The documentation at:
> http://ws.apache.org/juddi/docs/3.0/userguide/html_single/index.html refers
> to the old package this class used to occupy. Section 3.5
> Same section also refers to the same config property by two different names.
> Replace juddi.sercuity.domain with juddi.securityDomain, as this is the value
> of Property.JUDDI_SECURITY_DOMAIN
> 3.) The inline documentation in JBossAuthenticator refers to the old package
> as well.
> 4.) Numerous references juddi.auth throughout the document. One reference
> to juddi.authenticator, which I believe is correct as it corresponds to
> Property.JUDDI_AUTHENTICATOR
> Might I suggest moving this class out of docs and into the compiled and
> tested baseline so that it is regularly compiled, in order to avoid such
> problems in the future. I understand your motivation for keeping it
> separate. You wish to avoid the burden of answering users' questions about
> it or maintaining it when JBoss API changes. It's reasonable to predict that
> you're going to have to do these things anyway (since people will still post
> on the forums and write bug reports about it when it's out of date). Why not
> move all such code and examples into a separate distribution package, e.g.
> juddi-integration.jar? Providing simple integration into popular app
> containers out of the box can only be good for the jUDDI project.
> And before you accuse me of demanding something for nothing, note that I'm
> tasked with deploying jUDDI backed by Oracle 11g, for which there is no
> current documentation, only a plea for contributions. ;)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
