[JBoss JIRA] (AS7-2654) Add ability to present outbound-socket-binding configurations in the admin console
by jaikiran pai (Created) (JIRA)
Add ability to present outbound-socket-binding configurations in the admin console
----------------------------------------------------------------------------------
Key: AS7-2654
URL: https://issues.jboss.org/browse/AS7-2654
Project: Application Server 7
Issue Type: Task
Components: Console
Environment: AS7 upstream
Reporter: jaikiran pai
Assignee: Heiko Braun
AS7 upstream now has support for outbound-socket-binding configurations, which was introduced in AS7-2134. An outbound-socket-binding represents a socket configuration which _connects_ to a remote destination and port. This is unlike the socket-binding which _binds_ a local server socket.
We'll have to present the outbound-socket-binding and their references separately/differently on the admin console.
P.S: AS7-2630 and AS7-2644 are examples of how the outbound-socket-binding is used.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (AS7-3203) jboss-deployment-structure.xml: dependencies for all modules
by erik van altena (Created) (JIRA)
jboss-deployment-structure.xml: dependencies for all modules
------------------------------------------------------------
Key: AS7-3203
URL: https://issues.jboss.org/browse/AS7-3203
Project: Application Server 7
Issue Type: Enhancement
Components: Class Loading
Affects Versions: 7.0.2.Final
Reporter: erik van altena
Assignee: David Lloyd
Priority: Minor
I deploy an ear with an EJB and a WAR module. In both modules I want to use logging, so I want to add the org.slf4j module to their classpath.
My first attempt to get this done was this simple jboss-deployment-structure.xml file which I placed in the META-INF folder of the EAR.
<?xml version="1.0" encoding="UTF-8"?>
<jboss-deployment-structure>
<deployment>
<dependencies>
<module name="org.slf4j" />
</dependencies>
</deployment>
</jboss-deployment-structure>
This however, does not get the job done in the case of an EAR though; SLF4J is not on the classpath of either ear module. When I deploy this exact file in a web application that deploys as a war (in the WEB-INF folder), this does work. Of course that makes some sense as the war doesn't have sub-deployments.
In stead, I have to do this:
<?xml version="1.0" encoding="UTF-8"?>
<jboss-deployment-structure>
<deployment>
<dependencies>
<module name="org.slf4j" />
</dependencies>
</deployment>
<sub-deployment name="chipstkpov-ejb.jar">
<dependencies>
<module name="org.slf4j" />
</dependencies>
</sub-deployment>
<sub-deployment name="chipstkpov-web.war">
<dependencies>
<module name="org.slf4j" />
</dependencies>
</sub-deployment>
</jboss-deployment-structure>
Note that the <deployment> section is still needed, if I leave it out the dependency still does not end up on the classpath of the sub-deployments. With this exact setup the EAR deploys just fine.
As I understand from my test results, you need to;
- define the dependencies you want to expose to the classpath in the <modules> section
- per sub-deployment you have to then explicitly add that dependency as well
What I would expect and prefer is that the first example I gave would do exactly the same WITHOUT me having to explicitly name the sub-deployments of the ear in this file. That is duplicate maintenance as any change I make to the build structure (maven poms in my case) I will now have to duplicate in this file.
Note that if I am correct in my findings, it would be very useful if this is documented in the jboss classloading documentation.
https://docs.jboss.org/author/display/AS7/Class+Loading+in+AS7
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] Created: (JBRULES-2856) Encrypted passwords in the change-set.xml
by Alessandro Lazarotti (JIRA)
Encrypted passwords in the change-set.xml
-----------------------------------------
Key: JBRULES-2856
URL: https://issues.jboss.org/browse/JBRULES-2856
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 5.1.1.FINAL
Environment: fedora 12, jdk 1.6, drools 5.1.0 expert
Reporter: Alessandro Lazarotti
Assignee: Mark Proctor
Currently the drools client API access Guvnor by creditials declared as plain-text in change-set.xml or property files. This is a security problem for many companies. Is very important develop a mechanism to obfuscate the password
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (JBRULES-3378) ClassCastException when retrieving AgendaEventListener collection
by Mario Fusco (JIRA)
Mario Fusco created JBRULES-3378:
------------------------------------
Summary: ClassCastException when retrieving AgendaEventListener collection
Key: JBRULES-3378
URL: https://issues.jboss.org/browse/JBRULES-3378
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Mario Fusco
Assignee: Mario Fusco
Following part of Spring configuration:
<bean id="debug-agenda-listener"
class="org.drools.event.DebugAgendaEventListener" />
<drools:ksession id="statefulSession" type="stateful" kbase="kbase1">
<drools:agendaEventListener ref="debug-agenda-listener"/>
</drools:ksession>
when trying to find out AgendaEventListener count registered in knowledge
stateful session, got this exception:
org.springframework.web.util.NestedServletException: Request processing failed;
nested exception is java.lang.ClassCastException:
org.jbpm.process.instance.ProcessRuntimeImpl$3 cannot be cast to
org.drools.event.rule.AgendaEventListener
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:656)
org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:549)
javax.servlet.http.HttpServlet.service(HttpServlet.java:621)
javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:393)
root cause
java.lang.ClassCastException: org.jbpm.process.instance.ProcessRuntimeImpl$3
cannot be cast to org.drools.event.rule.AgendaEventListener
org.drools.impl.StatefulKnowledgeSessionImpl.getAgendaEventListeners(StatefulKnowledgeSessionImpl.java:182)
com.redhat.droolsspring.controllers.DroolsIntegrationStatefulTest.testAgendaListener(DroolsIntegrationStatefulTest.java:28)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:616)
org.springframework.web.bind.annotation.support.HandlerMethodInvoker.invokeHandlerMethod(HandlerMethodInvoker.java:174)
org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter.invokeHandlerMethod(AnnotationMethodHandlerAdapter.java:421)
org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter.handle(AnnotationMethodHandlerAdapter.java:409)
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:771)
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:716)
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:644)
org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:549)
javax.servlet.http.HttpServlet.service(HttpServlet.java:621)
javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:393)
See attachment 542456 [details]:
build as maven project, then deploy to tomcat, open webapp in browser and click
on the first link.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months