[JBoss AS 7 Development] - Re: Calls against multiple servers from a single client
by Tarek Hammoud
Tarek Hammoud [https://community.jboss.org/people/thammoud] created the discussion
"Re: Calls against multiple servers from a single client"
To view the discussion, visit: https://community.jboss.org/message/759498#759498
--------------------------------------------------------------
If you look at the bolded code in EJBInvocationHandler:
Object doInvoke(final T proxy, final Method method, final Object[] args) throws Throwable {
final MethodHandler handler = clientSideMethods.get(new MethodKey(method));
if (handler != null && handler.canHandleInvocation(this, proxy, method, args)) {
return handler.invoke(this, proxy, method, args);
}
* final EJBClientContext context = EJBClientContext.requireCurrent();*
return doInvoke(this, async, proxy, method, args, context);
}
EJBClientContext is using a non-thread local static. I don't know how to make that thread safe with the above suggestions. Looking forward to hearing from you.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/759498#759498]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
11 years, 6 months
[JBoss AS 7 Development] - Re: CLI non-interactive mode improvements
by Alexey Loubyansky
Alexey Loubyansky [https://community.jboss.org/people/aloubyansky] created the discussion
"Re: CLI non-interactive mode improvements"
To view the discussion, visit: https://community.jboss.org/message/714239#714239
--------------------------------------------------------------
About the environment properties, makes sense. Although, I think it's a different issue from interactive value prompting.
While conditions and force are interesting features, you can achieve repeatable script executions by using batches which make a script an atomic action, i.e. everything in the script will be applied or rolled back.
The force in the suggested form (for operations especially) won't be implemented. For some commands, perhaps. In general, though, I, personally, don't like the idea... but I see your point. Conditions are interesting.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/714239#714239]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
11 years, 6 months
[JBoss AS 7 Development] - org.hibernate.internal.SessionImpl cannot be cast to org.hibernate.classic.Session
by Machara Rao P
Machara Rao P [https://community.jboss.org/people/machararao] created the discussion
"org.hibernate.internal.SessionImpl cannot be cast to org.hibernate.classic.Session"
To view the discussion, visit: https://community.jboss.org/message/751185#751185
--------------------------------------------------------------
HI
I am newly joined in this community! i am facing some issue when i try to use Hibernate Search in JBoss 7 i am getting following exception
14:46:01,104 WARN [org.hibernate.internal.SessionFactoryImpl] (http-localhost-127.0.0.1-8079-1) HHH000008: JTASessionContext being used with JDBCTransactionFactory; auto-flush will not operate correctly with getCurrentSession()
14:47:32,172 ERROR [stderr] (http-localhost-127.0.0.1-8079-2) java.lang.ClassCastException: org.hibernate.internal.SessionImpl cannot be cast to org.hibernate.classic.Session
14:47:32,174 ERROR [stderr] (http-localhost-127.0.0.1-8079-2) at org.hibernate.search.impl.FullTextSessionImpl.<init>(FullTextSessionImpl.java:105)
14:47:32,174 ERROR [stderr] (http-localhost-127.0.0.1-8079-2) at org.hibernate.search.Search.getFullTextSession(Search.java:45)
14:47:32,175 ERROR [stderr] (http-localhost-127.0.0.1-8079-2) at org.hibernate.search.jpa.impl.FullTextEntityManagerImpl.getFullTextSession(FullTextEntityManagerImpl.java:71)
14:47:32,176 ERROR [stderr] (http-localhost-127.0.0.1-8079-2) at org.hibernate.search.jpa.impl.FullTextEntityManagerImpl.createFullTextQuery(FullTextEntityManagerImpl.java:100)
please help me solving this issue
Thanks in advance
Machara
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/751185#751185]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
11 years, 6 months
[JBoss AS 7 Development] - Error trying to Validate jboss-ejb3.xml
by vam kris
vam kris [https://community.jboss.org/people/vamsi2012] created the discussion
"Error trying to Validate jboss-ejb3.xml"
To view the discussion, visit: https://community.jboss.org/message/762035#762035
--------------------------------------------------------------
In the Jboss-ejb3.xml,its trying to reference http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd something like this.
In the above,We are referencing both Schemas http://www.jboss.com/xml/ns/javaee http://www.jboss.com/xml/ns/javaee jboss-ejb3-2_0.xsd (namespace is http://www.jboss.com/xml/ns/javaee http://www.jboss.com/xml/ns/javaee ) and http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd (namespace is http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee) under xsi:schemaLocation. jboss-ejb3-2_0.xsd inturn references jboss-ejb3-spec-2_0.xsd something like this
There is an ambiguity error or the Conflict that is Caused for the Element in both jboss-ejb3-spec-2_0.xsd and ejb-jar_3_1.xsd 1. jboss-ejb3-spec-2_0.xsd Defines the Defines the Element as below:
It references assembly-descriptor like this: 2. http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd Defines the Element something like this The assembly-descriptorType defines application-assembly information. The application-assembly information consists of the following parts: the definition of security roles, the definition of method permissions, the definition of transaction attributes for enterprise beans with container-managed transaction demarcation, the definition of interceptor bindings, a list of methods to be excluded from being invoked, and a list of exception types that should be treated as application exceptions. All the parts are optional in the sense that they are omitted if the lists represented by them are empty. Providing an assembly-descriptor in the deployment descriptor is optional for the ejb-jar or .war file producer. Because of the above Scenario when I am trying to Validate the XML ,I am getting the following error: cos-nonambig: " http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee":assembly-descriptor and " http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee":assembly-descriptor (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles. Attached are the 3 XSD Files. Could anyone help me resolve this.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/762035#762035]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
11 years, 6 months
[JBoss Web Services Development] - SOAP Message validation now enabled by default?
by Paul Robinson
Paul Robinson [https://community.jboss.org/people/paul.robinson] created the discussion
"SOAP Message validation now enabled by default?"
To view the discussion, visit: https://community.jboss.org/message/762174#762174
--------------------------------------------------------------
Hello,
Since AS7 upgraded from CXF '2.4.8-patch-01' to '2.4.9' ( https://github.com/jbossas/jboss-as/commit/0a1e626a5c4bf52a8c75e0cd27f15c... https://github.com/jbossas/jboss-as/commit/0a1e626a5c4bf52a8c75e0cd27f15c...) we have been getting the following 'unexpected element' error:
18:34:17,669 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (http-/127.0.0.1:8080-3) Interceptor for {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationParticipantSer
vice#{http://schemas.arjuna.com/ws/2005/10/wsarjtx}FaultOperation has thrown exception, unwinding now: org.apache.cxf.interceptor.Fault: Unexpected element {http://schemas.xmlsoa
p.org/soap/envelope/}Fault found. Expected {http://schemas.arjuna.com/ws/2005/10/wsarjtx}Fault.
at org.apache.cxf.interceptor.DocLiteralInInterceptor.validatePart(DocLiteralInInterceptor.java:259) [cxf-rt-core-2.4.9.jar:2.4.9]
at org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(DocLiteralInInterceptor.java:201) [cxf-rt-core-2.4.9.jar:2.4.9]
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263) [cxf-api-2.4.9.jar:2.4.9]
at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) [cxf-rt-core-2.4.9.jar:2.4.9]
at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:207) [cxf-rt-transports-http-2.4.9.jar:2.4.9]
at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:91)
at org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:169)
at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:87)
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:185) [cxf-rt-transports-http-2.4.9.jar:2.4.9]
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:108) [cxf-rt-transports-http-2.4.9.jar:2.4.9]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) [jboss-servlet-api_3.0_spec-1.0.1.Final.jar:1.0.1.Final]
at org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:135)
at org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:140)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.1.Final.jar:1.0.1.Final]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:372)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:679)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931)
at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_35]
This error occurs because our message type doesn't match that required by the WSDL:
<soap:Body>
<ns2:Fault xmlns:ns2="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns3="http://schemas.arjuna.com/ws/2005/10/wsarjtx">
<faultcode>ns3:TransactionRolledBack</faultcode>
<faultstring>ARJUNA043178: Transaction rolled back</faultstring>
</ns2:Fault>
</soap:Body>
Notice that the message is of type "ns2:Fault", rather than "ns3:Fault". The wsdl wants a '{http://schemas.arjuna.com/ws/2005/10/wsarjtx}Fault'.
So we have two problems here. The first is the problem that we have been sending malformed messages for some time. The second is that since the upgrade to CXF 2.4.9, this issue was not tolerated. In the long term we need to fix the message, but that may not be possible in the short term as we may not be able to get this fix into the release that needs it.
Do you know what has changed in CXF to cause this issue and do you know of a work-around?
For the original issue see here: https://issues.jboss.org/browse/JBTM-1275 https://issues.jboss.org/browse/JBTM-1275
Thanks,
Paul.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/762174#762174]
Start a new discussion in JBoss Web Services Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
11 years, 6 months