[JBoss ESB Development] - Webservice call SOAP Client Action doesnt work
by mgrande
mgrande [https://community.jboss.org/people/mgrande] created the discussion
"Webservice call SOAP Client Action doesnt work"
To view the discussion, visit: https://community.jboss.org/message/766593#766593
--------------------------------------------------------------
Hi,
First of all,let you know that we are beginners in the development with JBOSS,so sorry if we say any stupid thing.
We have created a SOAPClient Acton in a ESB with this properties first calling a Request and later a Respond:
<action class="es.vass.util.MyRequestActionMyRequestAction" name="PreparaRequest"/>
<action class="org.jboss.soa.esb.actions.soap.SOAPClient" name="weatherMola">
<property name="wsdl" value="http://www.webservicex.com/globalweather.asmx?WSDL"/>
<property name="SOAPAction" value="http://www.webserviceX.NET/GetCitiesByCountry"/>
<property name="responseAsOgnlMap" value="true"/>
</action>
<action class="es.vass.util.MyRequestActionMyRequestAction" name="PreparaRequest"/>
We call the action with a ESB message and it returns:
09:37:18,244 INFO [InquiryHelper] uddi:juddi.apache.org:c79564de-eb3d-470d-aba7-c85217fc70c8 is modified Wed Oct 17 16:03:03 CEST 2012 1350482583192
09:37:23,360 INFO [STDOUT] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
09:37:23,362 INFO [STDOUT] Request map is: {GetCitiesByCountry.CountryName=Spain}
09:37:23,362 INFO [STDOUT] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
09:37:23,396 INFO [STDOUT] Progress: 1 - Caching definition from url [http://www.webservicex.com/globalweather.asmx?WSDL]
09:37:24,576 INFO [STDOUT] Progress: 1 - Loading definition from cache
09:37:24,582 INFO [STDOUT] Retrieving document at 'http://www.webservicex.com/globalweather.asmx?WSDL'.
09:37:24,660 INFO [SchemaUtils] Loading schema types from [http://www.webservicex.com/globalweather.asmx?WSDL]
09:37:24,677 INFO [SchemaUtils] Getting schema http://www.webservicex.com/globalweather.asmx?WSDL
09:37:25,635 INFO [SchemaUtils] schema for [http://www.webserviceX.NET] contained [{}] namespaces
09:37:26,246 INFO [WsdlImporter] Finding importer for {http://www.webserviceX.NET}GlobalWeatherHttpPost
09:37:26,248 INFO [WsdlImporter] Missing importer for {http://www.webserviceX.NET}GlobalWeatherHttpPost
09:37:26,248 INFO [WsdlImporter] Finding importer for {http://www.webserviceX.NET}GlobalWeatherSoap12
09:37:26,317 INFO [WsdlImporter] Importing binding {http://www.webserviceX.NET}GlobalWeatherSoap12
09:37:26,322 INFO [Soap12HttpBindingImporter] importing endpoint http://www.webservicex.com/globalweather.asmx
09:37:26,393 INFO [Soap12HttpBindingImporter] importing operation GetCitiesByCountry
09:37:26,394 INFO [Soap12HttpBindingImporter] importing operation GetWeather
09:37:26,395 INFO [WsdlImporter] Finding importer for {http://www.webserviceX.NET}GlobalWeatherSoap
09:37:26,395 INFO [WsdlImporter] Importing binding {http://www.webserviceX.NET}GlobalWeatherSoap
09:37:26,396 INFO [Soap11HttpBindingImporter] importing endpoint http://www.webservicex.com/globalweather.asmx
09:37:26,413 INFO [Soap11HttpBindingImporter] importing operation GetCitiesByCountry
09:37:26,422 INFO [Soap11HttpBindingImporter] importing operation GetWeather
09:37:26,423 INFO [WsdlImporter] Finding importer for {http://www.webserviceX.NET}GlobalWeatherHttpGet
09:37:26,423 INFO [WsdlImporter] Missing importer for {http://www.webserviceX.NET}GlobalWeatherHttpGet
09:37:26,423 INFO [WsdlImporter] Finding importer for {http://www.webserviceX.NET}GlobalWeatherHttpGet
09:37:26,457 INFO [WsdlImporter] Missing importer for {http://www.webserviceX.NET}GlobalWeatherHttpGet
09:37:26,457 INFO [WsdlImporter] Finding importer for {http://www.webserviceX.NET}GlobalWeatherHttpPost
09:37:26,458 INFO [WsdlImporter] Missing importer for {http://www.webserviceX.NET}GlobalWeatherHttpPost
09:37:26,479 INFO [STDOUT] Progress: 1 - Caching definition from url [http://www.webservicex.com/globalweather.asmx?WSDL]
09:37:26,932 INFO [STDOUT] Progress: 1 - Loading definition from cache
09:37:26,948 INFO [STDOUT] Retrieving document at 'http://www.webservicex.com/globalweather.asmx?WSDL'.
09:37:26,974 INFO [SchemaUtils] Loading schema types from [http://www.webservicex.com/globalweather.asmx?WSDL]
09:37:26,974 INFO [SchemaUtils] Getting schema http://www.webservicex.com/globalweather.asmx?WSDL
09:37:27,104 INFO [SchemaUtils] schema for [http://www.webserviceX.NET] contained [{}] namespaces
09:37:27,231 INFO [SchemaUtils] Getting schema http://www.webservicex.com/globalweather.asmx?WSDL
09:37:27,729 WARN [ActionProcessingPipeline] No fault address defined for fault message! To: JMSEpr [ PortReference < <wsa:Address jms:127.0.0.1:1099#queue/esb_channel/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:destination-name : queue/esb_channel/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: 76891731-9980-4511-a82e-8fc03d6cd53b RelatesTo: jms:correlationID#76891731-9980-4511-a82e-8fc03d6cd53b
09:37:27,813 INFO [InquiryHelper] uddi:juddi.apache.org:e60d75e7-29e1-4455-82df-3cfff3236390 is modified Tue Oct 16 17:45:39 CEST 2012 1350402339761
It doesnt do anything else and we dont see any respond. We have truied the webservice with SoapUI and we know that its working. What can check to know what can be wrong?
We are working with JBOSS AS 5.1 and JBOSS ESB 4.10 in a local server. We use for the development JBOSS developer.
Thanks you in ad
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/766593#766593]
Start a new discussion in JBoss ESB Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
11 years, 2 months
[JBoss Transactions Development] - EnityManager.close() before or after JTA afterCompletion()?
by seyvet
seyvet [https://community.jboss.org/people/seyvet] created the discussion
"EnityManager.close() before or after JTA afterCompletion()?"
To view the discussion, visit: https://community.jboss.org/message/794692#794692
--------------------------------------------------------------
Hi,
See as a reference the https://community.jboss.org/message/794633#794633 thread.
In an application server, that is JavaEE 6 compliant, which of EntityManager.close() and JTA Synchronization.afterCompletion() should be closed first?
Based on the persistence specification:
7.9.1 Container Responsibilities:
After the JTA transaction has completed (either by transaction commit or rollback), The container closes the entity manager by calling EntityManager.close.
I am using DataNucleus (DN) 3.2 as a Persistence provider, and DN expects the Transaction afterCompletion() to be triggered BEFORE the EntityManager.close(). It seems that the opposite is triggered by JBoss. So I wonder if both are correct or if one should be called before another based on either JTA or Persistence JSRs?
Based on the thread dump, arjuna calls first:
at org.datanucleus.api.jpa.JPAEntityManager.close(JPAEntityManager.java:194)
at org.jboss.as.jpa.transaction.TransactionUtil$SessionSynchronization.afterCompletion(TransactionUtil.java:193)
(EntityManager.close() is called first)
Then JTA after completion:
at org.datanucleus.TransactionImpl.internalPostCommit(TransactionImpl.java:563)
at org.datanucleus.JTATransactionImpl.afterCompletion(JTATransactionImpl.java:429)
at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.afterCompletion(SynchronizationImple.java:96)
Thanks
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/794692#794692]
Start a new discussion in JBoss Transactions Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
11 years, 2 months
Re: [jboss-dev-forums] [PicketBox Development] - JBoss AS7: Enabling JASPI Authentication for Web Applications
by arjan tijms
arjan tijms [https://community.jboss.org/people/atijms] commented on the document
"JBoss AS7: Enabling JASPI Authentication for Web Applications"
To view all comments on this document, visit: https://community.jboss.org/docs/DOC-17782#comment-11498
--------------------------------------------------
Ron, thank you so much for the response!
Indeed, HttpServletRequest.authenticate works. I tested this using JBoss EAP 6.0.1, WebLogic 12.1.1, and GlassFish 3.1.2.2.
It would help a lot of the next MR to the spec would state this explicitly. Are there already any plans for this MR? And being a MR, will there be some sort of open tracker where one can submit issues?
> ValidateRequest should not be called under HttpServletRequest.login mostly because login presumes a user name/password authentication mechanism (which may not be compatible with the configured auth context).
>
Indeed, but that holds for proprietary login modules as well, doesn't it? The contract on HttpServletRequest.login already mentions something along those lines:
+"This method returns without throwing a ServletException when the login mechanism configured for the ServletContext supports username password validation"+
> I will think about how that might be possible
>
+
+
Thanks again, it will be interesting to see what the options here are.
If for some reason it really is not possible to handle HttpServletRequest.login with JSR 196, then maybe an exception should be thrown instead if jsr 196 is configured for the app?
What happens now is that the call silently goes to a completely different login module. If this login module happened to store the username/password that the user is trying to authenticate with, he/she will be totally unexpected and silently authenticated with the wrong login module.
--------------------------------------------------
11 years, 2 months
Re: [jboss-dev-forums] [JBoss AS 7 Development] - Design of AS7 multi-JSF feature
by Alexis Hassler
Alexis Hassler [https://community.jboss.org/people/sewatech] commented on the document
"Design of AS7 multi-JSF feature"
To view all comments on this document, visit: https://community.jboss.org/docs/DOC-47689#comment-11495
--------------------------------------------------
That's a great feature, really helpful when migrating JSF applications from an older AS. It's fully working with JBoss AS 7.2 (jboss-as-7.2.0.Alpha1-SNAPSHOT). On JBoss AS 7.1.3 (or EAP 6.0.1), the feature is only partial.
For example, @EJB injection doesn't work with my JSF 1.2 managed beans :( . And the jsf subsystem doesn't exist yet. On my application, I had to make a custom InjectionProvider to have my EJBs injected.
I'm really looking forward to have that new release.
--------------------------------------------------
11 years, 2 months