[
https://jira.jboss.org/jira/browse/JBESB-3013?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-3013:
-------------------------------------
This occurs because the inquire method is overloaded and the aspect is being applied to
them both.
Will modify the AOP config and double check the others.
Juddi client aspect error
-------------------------
Key: JBESB-3013
URL:
https://jira.jboss.org/jira/browse/JBESB-3013
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Registry and Repository
Affects Versions: 4.7
Reporter: Kevin Conner
Assignee: Kevin Conner
Fix For: 4.7 CP1
The juddi client aspect currently assumes that the first argument is an element, but
searching results in the following CCE.
16:42:44,150 ERROR [InquiryServiceImpl] Could not obtain token. $Proxy341 cannot be cast
to org.w3c.dom.Element
java.lang.ClassCastException: $Proxy341 cannot be cast to org.w3c.dom.Element
at
org.jboss.internal.soa.esb.services.registry.aspect.JUDDIClientInquiryAspect.inquire(JUDDIClientInquiryAspect.java:71)
at
org.jboss.aop.advice.org.jboss.internal.soa.esb.services.registry.aspect.JUDDIClientInquiryAspect_z_inquire_18405154.invoke(JUDDIClientInquiryAspect_z_inquire_18405154.java)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira