[JBoss JIRA] (AS7-5281) JBoss loading wrong Hibernate version when using Persistence unit in WAR file
by Kuthair Habboush (JIRA)
Kuthair Habboush created AS7-5281:
-------------------------------------
Summary: JBoss loading wrong Hibernate version when using Persistence unit in WAR file
Key: AS7-5281
URL: https://issues.jboss.org/browse/AS7-5281
Project: Application Server 7
Issue Type: Feature Request
Components: Class Loading, JPA / Hibernate
Affects Versions: 7.1.1.Final
Environment: JBoss 7.1.1.Final & Hibernate 4.1.5.SP1 on Mac OSX 10.7/10.8
SQL Server 2008 on Windows 7 virtual
Reporter: Kuthair Habboush
Assignee: David Lloyd
Attachments: hibernate-test.zip
JBoss is loading Hibernate 4.0.1.Final (ships with) instead of the version specified in my Maven POM file and embedded in WAR archive, version: 4.1.5.SP1.
This ONLY occurs when I have a Persistence Unit setup in my WAR file in directory: resources/META-INF.
If I rename persistence.xml to persistence.xml.old, JBoss loads the correct version: Hibernate 4.1.5.SP1.
I have a sample project.
--
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, 7 months
[JBoss JIRA] (JBRULES-3684) MVEL is having issues resolving a generic member in a concrete type
by Justin Holmes (JIRA)
Justin Holmes created JBRULES-3684:
--------------------------------------
Summary: MVEL is having issues resolving a generic member in a concrete type
Key: JBRULES-3684
URL: https://issues.jboss.org/browse/JBRULES-3684
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler
Affects Versions: 5.5.0.CR1
Reporter: Justin Holmes
Assignee: Mark Proctor
Priority: Minor
Pull request with test case to follow...
I have 2 classes:
public abstract class AbstractBase<T> {
protected T foo;
public T getFoo() {
return foo;
}
}
public class StringConcrete extends AbstractBase<String> {
public StringConcrete() {
this.foo = new String();
}
}
The following rule fails in MVEL dialect, but passes in Java dialect.
rule "test"
dialect "mvel"
when
$S : StringConcrete()
then
System.out.println( $S.getFoo().concat("this works with java dialect") );
end
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-5969) WebDeploymentService does blocking tasks in a MSC thread
by jaikiran pai (JIRA)
jaikiran pai created AS7-5969:
---------------------------------
Summary: WebDeploymentService does blocking tasks in a MSC thread
Key: AS7-5969
URL: https://issues.jboss.org/browse/AS7-5969
Project: Application Server 7
Issue Type: Bug
Components: Web
Reporter: jaikiran pai
Assignee: jaikiran pai
The WebDeploymentService in its start/stop lifecycle methods triggers the web application context initialization which can internally trigger various component initialization tasks like startup servlet initializations and servlet context initializations. This currently happens in a MSC thread but instead should be happening via a server executor which is already available for such blocking tasks.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-5963) Provide ability to detect server shutdown
by Thomas Diesler (JIRA)
Thomas Diesler created AS7-5963:
-----------------------------------
Summary: Provide ability to detect server shutdown
Key: AS7-5963
URL: https://issues.jboss.org/browse/AS7-5963
Project: Application Server 7
Issue Type: Feature Request
Components: Server
Reporter: Thomas Diesler
Assignee: Jason Greene
Fix For: 7.2.0.Alpha1
The general use case is that a subsystem maintains state (on behalf of a deployment) that should be removed on explicit user interaction (i.e. mgmt op) but not on subsystem/server shutdown. This should also work in the domain case. Perhaps the ApplicationServerService (or similar) could be queried about whether it is currently shutting down.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-2792) CLI doesn't show resolved multicast address for socket-binding definition like jgroups-udp or jgroups-mping
by Rostislav Svoboda (Created) (JIRA)
CLI doesn't show resolved multicast address for socket-binding definition like jgroups-udp or jgroups-mping
-----------------------------------------------------------------------------------------------------------
Key: AS7-2792
URL: https://issues.jboss.org/browse/AS7-2792
Project: Application Server 7
Issue Type: Bug
Components: CLI, Domain Management
Affects Versions: 7.1.0.Beta1
Reporter: Rostislav Svoboda
Assignee: Alexey Loubyansky
Fix For: 7.1.0.CR1
Hi Alexey.
CLI doesn't show resolved multicast address for socket-binding definition like jgroups-udp or jgroups-mping. I would expect to see 'resolved-multicast-address' or something similar to 'resolved-address' for interface definition.
I hope management model can provide such information. If not please reassign to Brian.
{code}
$ bin/standalone.sh -c standalone-ha.xml -u 224.34.3.154
$ bin/jboss-admin.sh -c
[standalone@localhost:9999 /] cd /socket-binding-group=standard-sockets/socket-binding=jgroups-udp
[standalone@localhost:9999 socket-binding=jgroups-udp] :read-resource(include-runtime=true)
{
"outcome" => "success",
"result" => {
"bound" => false,
"bound-address" => undefined,
"bound-port" => undefined,
"fixed-port" => false,
"interface" => undefined,
"multicast-address" => expression "${jboss.default.multicast.address:230.0.0.4}",
"multicast-port" => 45688,
"name" => "jgroups-udp",
"port" => 55200
}
}
{code}
--
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, 7 months
[JBoss JIRA] (AS7-5966) Installed library not recognized as CDI bean archive
by Martin Kouba (JIRA)
Martin Kouba created AS7-5966:
---------------------------------
Summary: Installed library not recognized as CDI bean archive
Key: AS7-5966
URL: https://issues.jboss.org/browse/AS7-5966
Project: Application Server 7
Issue Type: Bug
Components: CDI / Weld
Affects Versions: 7.1.2.Final (EAP)
Reporter: Martin Kouba
Assignee: Stuart Douglas
The CDI 1.0 spec states in 12.1. "Bean archives":
{quote}
* In an application deployed as an ear, the container searches every bean archive bundled with or *referenced by* the ear, including bean archives bundled with or referenced by wars and EJB jars contained in the ear. The bean archives might be library jars, EJB jars, rars or war WEB-INF/classes directories.
* In an application deployed as a war, the container searches every bean archive bundled with or *referenced by* the war. The bean archives might be library jars or the WEB-INF/classes directory.
* In an application deployed as an EJB jar, the container searches the EJB jar, if it is a bean archive, and every bean archive referenced by the EJB jar.
* ...
{quote}
Java EE 6 allows to reference installed libraries - see EE.8.2.2 "Installed Libraries".
However it seems installed libraries are not recognized as bean archives.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months