[JBoss JIRA] Created: (JBESB-2604) Document registry interceptors
by Aaron Pestel (JIRA)
Document registry interceptors
------------------------------
Key: JBESB-2604
URL: https://jira.jboss.org/jira/browse/JBESB-2604
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Documentation
Environment: SOA-P 4.3 SP1
Reporter: Aaron Pestel
Priority: Minor
This is a request to document the two known registry interceptors: org.jboss.internal.soa.esb.services.registry.InVMRegistryInterceptor and org.jboss.internal.soa.esb.services.registry.CachingRegistryInterceptor
The InVMRegistryInterceptor is listed in the services guide, section 2.1 and 3.2: http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.CP01/html-single/...
In section 2.1, it shows an extract of the registry portion of the jbossesb-properties.xml - which includes InVMRegistryInterceptor, and then goes on to describe each property, but neglects to describe the org.jboss.soa.esb.registry.interceptors property where InVMRegistryInterceptor is set.
I am requesting a description in section 2.1 of the org.jboss.soa.esb.registry.interceptors property to include:
1.) format for adding 1 or many interceptors (using ", ")
2.) description of two currently available interceptors (InVMRegistryInterceptor and CachingRegistryInterceptor)
3.) description of when it would make sense or not make sense to use these two interceptors
Thanks!
--
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
13 years, 9 months
[JBoss JIRA] Created: (JBESB-2783) systinet specific loopback transport
by Kevin Conner (JIRA)
systinet specific loopback transport
------------------------------------
Key: JBESB-2783
URL: https://jira.jboss.org/jira/browse/JBESB-2783
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Registry and Repository
Affects Versions: 4.6
Reporter: Kevin Conner
Fix For: 4.7
We are currently proxying systinet UDDI requests via a mock servlet implementation but we need to investigate implementing a loopback transport as a replacement.
It looks like we need to create an implementation of org.idoox.transport.Transport and register this with the TransportRepository.
I looked into the JdkClient but this is not what we are after, all it does is use the JDK URLConnection class as the transport.
--
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
13 years, 9 months
[JBoss JIRA] Created: (JBESB-2556) Character corruption using SOAPClient (SOAPUI)
by Theodore S (JIRA)
Character corruption using SOAPClient (SOAPUI)
----------------------------------------------
Key: JBESB-2556
URL: https://jira.jboss.org/jira/browse/JBESB-2556
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Services
Affects Versions: 4.5
Environment: any
Reporter: Theodore S
When using SOAPUI using International characters can lead to character corruption.
How to reproduce:
Send chinese characters in the WS request to a webservice endpoint using the SOAPUI integration in JBossESB.
Fix:
In class org.jboss.soa.esb.actions.soap.SOAPClient change line 462:
post.setRequestEntity(new StringRequestEntity(request));
to
StringRequestEntity requestEntity = new StringRequestEntity(request,"text/xml","UTF-8");
post.setRequestEntity(requestEntity);
--
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
13 years, 11 months
[JBoss JIRA] Created: (JBESB-1553) SOAPClient action remappes objects with null strings to empty strings
by Jiri Pechanec (JIRA)
SOAPClient action remappes objects with null strings to empty strings
---------------------------------------------------------------------
Key: JBESB-1553
URL: http://jira.jboss.com/jira/browse/JBESB-1553
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Services
Affects Versions: 4.2.1 CP1
Reporter: Jiri Pechanec
Assigned To: Kevin Conner
Fix For: 4.2.1 CP2
Use webservice_consumer2 quickstart and use the attached files - contains enhanced equals and toString defintions. Make sure that option1 is used.
The object with following contents is sent to processing to ivoke web service
id = 101 lineItems = [Line Item ID= 1 Price=10.0 Ship To=aname, Line Item ID= 2 Price=20.0 Ship To=aname2] shipTo = null
But in the web service processing method the contents is
id = 101 lineItems = [Line Item ID= 1 Price=10.0 Ship To=aname, Line Item ID= 2 Price=20.0 Ship To=aname2] shipTo =
The difference is in shipTo property which was set tu null on the input but comes to web service as empty string.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months