[JBossWS] - Re: web service and asynchronous processing
by vitor_b
Hello
Thank you for your reply, but unfortunately there are some things i don't understand. Could you clarify these for me please?
We have Message Addressing Properties:
<wsa:To>xs:anyURI</wsa:To> ?
| <wsa:From>wsa:EndpointReferenceType</wsa:From> ?
| <wsa:ReplyTo>wsa:EndpointReferenceType</wsa:ReplyTo> ?
| <wsa:FaultTo>wsa:EndpointReferenceType</wsa:FaultTo> ?
| <wsa:Action>xs:anyURI</wsa:Action>
| <wsa:MessageID>xs:anyURI</wsa:MessageID> ?
| <wsa:RelatesTo RelationshipType="xs:anyURI"?>xs:anyURI</wsa:RelatesTo> *
| <wsa:ReferenceParameters>xs:any*</wsa:ReferenceParameters> ?
where EndpointReferenceType means:
<wsa:EndpointReference>
| <wsa:Address>xs:anyURI</wsa:Address>
| <wsa:ReferenceParameters>xs:any*</wsa:ReferenceParameters> ?
| <wsa:Metadata>xs:any*</wsa:Metadata>?
| </wsa:EndpointReference>
That is ok, but there is on the page
http://jbws.dyndns.org/mediawiki/index.php/JAX-WS_User_Guide#WS-Addressing
something like this:
<handler-chains xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
| xsi:schemaLocation="http://java.sun.com/xml/ns/javaee javaee_web_services_1_2.xsd">
|
| <handler-chain>
| <protocol-bindings>##SOAP11_HTTP</protocol-bindings>
| <handler>
| <handler-name>Application Server Handler</handler-name>
| <handler-class>org.jboss.test.ws.jaxws.samples.wsaddressing.ServerHandler</handler-class>
| </handler>
| </handler-chain>
|
| </handler-chains>
At this point i have some questions:
1. in which file should i put handler-chains element?
2. What does element handler-class contain? What is this class? Does this class is able to read SOAPMessage? I think i should i think write this class myself, but what is the contract for writing this class? What interface should it implement? SOAPHandler? Do i have to implement logic which will take info from soap message header?
3. I think these properties are handled automatically, this means webservice will send reply to adderss taken from element: wsa:ReplyTo, and i don't need to do anything in order to get this done. Am i right?
4. If 3 is true, that means that message addressing properties don't support property i need. Client should have entry point which will accept soap message sent by server after message from queue is processed. But this entry point will not be any identified by message addressing properties received in request
.................request......................................RequestObject
Client -------------------------> WebService ---------------
Client <------------------------- WebService ..................|
............ConfirmationObject........................................v
............................................................................Queue
...................................................................................|
...................SOAPMessage.........................................|
Client (EP) <------------------- SessionBean <-----------
Client (EP) --------------------> SessionBean
. (dot) - only used as a spaces, to format this message
EP - this should be a client entry point, where all results after processing objects from queue will be sent. There won't be address of this EP in the request.
Any help will be appreciated.
cheers
vitor_b
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025145#4025145
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025145
19Â years, 1Â month
[EJB 3.0] - Database Connection Pooling?
by majohnst
Really simple question, how do I setup database connection pooling in JBoss? Is it installed by default?
I am currently using EJB3 to access a datasource defined through jboss. I am accessing the database through:
| <local-tx-datasource>
| <jndi-name>MyDS</jndi-name>
| <connection-url>jdbc:postgresql://localhost/mydb</connection-url>
| <driver-class>org.postgresql.Driver</driver-class>
| <user-name>username</user-name>
| <password></password>
| <min-pool-size>5</min-pool-size>
| <max-pool-size>20</max-pool-size>
| </local-tx-datasource>
|
| ...
|
| @PersistenceContext(unitName="myname")
| private EntityManager em;
| ...
| Object obj = em.find(MyClass.class, id)
|
All my code works correctly, I just want to understand how the database connections are pooled. Is there anything else I need to change in my EJB3 to take advantage of the connection pooling?
Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025136#4025136
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025136
19Â years, 1Â month