I think the only problem you had originally was that login-conf.xml was in
the wrong place (deploy rather than conf)
>
> [ServiceController] jboss.jca:service=XATxDS,name=XAOracleDS does not
> implement any Service methods
is an annoying and meaningless message I hope to remember to remove one of
these days.
> [XAOracleDS] Bound connection factory for resource adapter 'Minerva
> JDBC
> XATransaction ResourceAdapter' to JNDI name 'java:/XAOracleDS'
>
indicates everything went well with your datasource and it is deployed.
(It's not tested, so if you provided the wrong url or something, you will
get errors when you try to get a connection).
The errors about login-conf.xml can only be fixed by removing it from
deploy. It is not deployable by anything: it's read on startup by the jaas
framework.
There is supposed to be a way to deploy additional login modules
dynamically, but I haven't looked into exactly how it works. I think that
it involves an additional mbean rather than a login-conf.xml file.
Hope this helps
david jencks
On 2002.09.03 14:50:39 -0400 Bruce Snyder wrote:
> This one time, at band camp, David Jencks said:
>
> DJ>login-conf.xml is not a deployable package. There needs to be exactly
> one
> DJ>of them in server/[config]/conf.
>
> I've only got one of them lying there.
>
> DJ>I think someone changed the incomplete deployment warnings to only
> occur
> DJ>once, so even though the login-conf.xml is still not deployed after
> you
> DJ>redeploy the oracle-xa-service.xml you don't get notified of the
> actual
> DJ>state of the server. I think your experience is a good illustration
> of why
> DJ>always reporting ALL the deployment problems is the clearest and most
> DJ>satisfactory solution.
>
> I agree. Suppression of continually occurring errors only confuses
> end users (like in my case ;-)).
>
> DJ>INIT_WAITING_DEPLOYER means there has been an attempt to deploy the
> DJ>package, but currently there are no deployers that know what to do
> with it.
> DJ> If a deployer that recognizes that package type gets deployed, your
> DJ>package will be deployed.
>
> OK, that makes complete sense to me. Now shouldn't the jboss-xa.rar
> be handling the deployment of the oracle-xa-service.xml? If so, I've
> tracked the jboss-xa.rar to be sure that it deploys successfully. I've
> found no errors in the startup logs.
>
> Upon deploying the oracle-xa-service.xml, I'm seeing:
>
> [ServiceController] jboss.jca:service=XATxDS,name=XAOracleDS does not
> implement any Service methods
>
> This message occurs twice, but no errors are thrown. Can you please
> describe the meaning of this message?
>
> Then I see the following message:
>
> [XAOracleDS] Bound connection factory for resource adapter 'Minerva
> JDBC
> XATransaction ResourceAdapter' to JNDI name 'java:/XAOracleDS'
>
> This signals to me that the oracle-xa-service is being bound to the
> JNDI ENC listed. But then later I receive the errors I submitted
> previously. This leads me back to my original question. Shouldn't the
> (already deployed) jboss-xa.rar handle this deployment?
>
> Thanks,
>
> Bruce
> --
> perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone? Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
>
>
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
