Phew! So there *is* a reason it wasn't working for me,
...I thought that I was going crazy. ;-)
This is a behaqviour that would be very valuable to us.
Were trying to present our system's API to the external world via
UDDI-lookups followed by SOAP-invocations, meanwhile, our internal
processes use the same API functions via JNDI-lookups followed by
direct invocations.
It sound like I'm being lazy, but the truth is we all have tons of
development to do, and I can't justify the time spent writing
'wrapper'/'proxy' beans for all our API beans.
I guess that I really want to believe in the "zero effort" part of
ZOAP, even though I firmly believe Robert Heinlein: TANSTAAFL ("There
ain't no such thing as a free lunch" - The Moon is a Harsh Mistress)
:-)
I'll be eagerly awaiting this feature!
Many thanks in advance,
DouglasDD
--
Douglas D. Dickinson =^..^= [EMAIL PROTECTED]
Jung , Dr. Christoph wrote:
> Well, hmm,
>
> the example you described should work ... SOAP-Bean calls JRMP bean, where
> JRMP-bean
> is looked up through JNDI ...
>
> your trace however indicates that you seem to lookup the
> SOAP-Bean through JNDI ?
>
> unfortunately, I have not yet been able to test/commit those
> parts my local source repository which contain the
> serializable SoapInvocationHandler (including in-VM optimisation) that can
> be
> put into /looked up from JNDI (hence, the registration is disabled for
> SOAP-beans at the moment).
>
> Until then, there is only the possiblity to construct the client proxies
> "manually" (as done in the test example).
>
> I�m sorry ... the more I�m sorry, the earlier I will take some spare time to
> do that pending commit (next week?) ... So please keep on asking!
>
> CGJ
> Douglas D. Dickinson wrote:
>>
>> Fellow zoapers,
>>
>> When I deploy EJBs with zoap-enabled SOAP interfaces,
>> it seems that I can no longer find them via JNDI look-ups.
>>
>> If I disable ZOAP (by setting <configuration-name> to empty
>> in the .jar file's jboss.xml and changing nothing else), it works.
>> ie the JNDI calls work, and the method invocation
>> (getSubscriberID()) on the remote (EJB) Object returns
>> sucessfully.
>>
>> I was expecting that the zoap-enabled EJBs would be
>> accessible by both the old (JNDI) and new (SOAP) methods.
>>
>> I suppose it could be possible to:
>> - deploy bean B(configuration-name: none)
>> - deploy bean BZ(configuration-name: SOAP-enabled Stateless SessionBean)
>> where BZ simply looks up B via JNDI & calls it
>> ....but this seems to go against the "zero effort" ideal of ZOAP :-)
>>
>> Am I missing something here?
>>
>> (Config/Log/Code details are included below)
>>
>> Many thanks in advance,
>> DouglasDD
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
