[JBoss JIRA] Created: (JBRULES-1230) Not able to run drools if core-3.2.3.v_686_R32x.jar is not specified in the classpath
by Krishnan Sivaramakrishna Iyer (JIRA)
Not able to run drools if core-3.2.3.v_686_R32x.jar is not specified in the classpath
-------------------------------------------------------------------------------------
Key: JBRULES-1230
URL: http://jira.jboss.com/jira/browse/JBRULES-1230
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: All
Affects Versions: 4.0.0.GA
Environment: Windows XP, Dell Optiplex GX 270
Reporter: Krishnan Sivaramakrishna Iyer
Assigned To: Mark Proctor
Priority: Blocker
hi all,
In my application, I use simple drl file based rules and it is not a J2EE application. Based on the dependencies
documentation http://anonsvn.labs.jboss.com/labs/jbossrules/tags/4.0.1.14754GA/README_D...
, it seems I am in the compiler option
The only jars I am including are as follows :-
drools-compiler-4.0.0.jar
drools-core-4.0.0.jar
drools-decisiontables-4.0.0.jar
drools-jsr94-4.0.0.jar
antlr-runtime-3.0.jar
mvel14-1.2rc1.jar
core-3.2.3.v_686_R32x.jar [Can anyone explain why I need this, the documentation seems like this is optional, but when I
don't specify this, it does not work ?.]
I also tried not including the core but including the janino library and specifying the janino compiler at run time and that also
expects the core to be included. Any help is appreciated.
TIA,
Krishnan.
Comments from Edson Tirelli
Krishnan,
You should not need decision tables and jsr94 jars if you are not using such feature. Regarding the compiler, you must use either core (jdt) jar or Janino jar... I'm not aware of any hard dependency on core itself... if it exists, please open a jira for us to fix.
[]s
Edson
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 11 months
[JBoss JIRA] Created: (EJBTHREE-1153) Client container needs an java:comp/ORB binding
by Scott M Stark (JIRA)
Client container needs an java:comp/ORB binding
-----------------------------------------------
Key: EJBTHREE-1153
URL: http://jira.jboss.com/jira/browse/EJBTHREE-1153
Project: EJB 3.0
Issue Type: Feature Request
Reporter: Scott M Stark
Fix For: AS 5.0.0.CR1
EE.5.11ORB References
Some Java EE applications will need to make use of the CORBA ORB to perform certain operations. Such applications can find an appropriate object implementing the ORB interface by looking up the JNDI name java:comp/ORB or by requesting injection of an ORB object. The container is required to provide the java:comp/ORB name for all components except applets. Any such reference to a ORB object is only valid within the component instance that performed the lookup.
The following example illustrates how an application component acquires and uses an ORB object via injection.
@Resource ORB orb;
public void method(...) {
...
// Get the POA to use when creating object references.
POA rootPOA = (POA)orb.resolve_initial_references("RootPOA");
...
}
The following example illustrates how an application component acquires and uses an ORB object using a JNDI lookup.
public void method(...) {
...
// Obtain the default initial JNDI context.
Context initCtx = new InitialContext();
// Look up the ORB object.
ORB orb = (ORB)initCtx.lookup("java:comp/ORB");
// Get the POA to use when creating object references.
POA rootPOA = (POA)orb.resolve_initial_references("RootPOA");
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 11 months
[JBoss JIRA] Created: (JBMESSAGING-1172) Implement JDBCPersistenceManager
by Tim Fox (JIRA)
Implement JDBCPersistenceManager
--------------------------------
Key: JBMESSAGING-1172
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1172
Project: JBoss Messaging
Issue Type: Task
Reporter: Tim Fox
Assigned To: Tyronne Wickramarathne
Fix For: 2.0.0 Beta
Although JDBC is not the main form of message persistence in JBM 2.0, we still need a JDBC PersistenceManager implementation, mainly we so we can work out of the box in the distro, without switching to the BDB persistence manager which we can't distribute due to licensing restrictions.
The JDBCPersistenceManager should use Hibernate dialects so we don't have to maintain separate configuration for each database.
The implementation should use two tables to store the message data, one for messages and one for message references. This would probably have a very similar structure to the JBM_MSG and JBM_MSG_REF tables currently used in JBM 1.4.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 11 months
[JBoss JIRA] Created: (JBMESSAGING-1141) QueueBrowser sees expired messages
by Carlo de Wolf (JIRA)
QueueBrowser sees expired messages
----------------------------------
Key: JBMESSAGING-1141
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1141
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Client Manager
Affects Versions: 1.4.0.SP1
Reporter: Carlo de Wolf
Assigned To: Tim Fox
When I send a message which almost immediately expires, a queue browser will still show the message.
sender.send(message, DeliveryMode.NON_PERSISTENT, 4, 1);
Thread.sleep(2000);
QueueBrowser browser = session.createBrowser(queue);
Enumeration e = browser.getEnumeration();
List messages = CollectionsUtil.list(e);
browser.close();
if(messages.size() == 1)
{
QueueReceiver receiver = session.createReceiver(dlq);
message = (TextMessage) receiver.receive(2000);
assertNull(message);
}
else
{
assertEquals(0, messages.size());
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 11 months
[JBoss JIRA] Created: (JBMESSAGING-1148) Remove node id address mapping
by Tim Fox (JIRA)
Remove node id address mapping
------------------------------
Key: JBMESSAGING-1148
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1148
Project: JBoss Messaging
Issue Type: Task
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 2.0.0 Beta
We can dramatically simplify the way we currently deal with node id- address mappings.
We can pass in node id as additional data before call to connect so each address in the view has the extra data - this makes node id - address mapping redundant, and we can remove the join and leave messages. :)
We can also remove the failovermap altogether - and generate it on the fly from the view (now it becomes trivial!!)
This should vastly simplify things and remove the scope for race conditions.
You can associate arbitrary data with an IpAddress, see below:
| JChannel c=new JChannel(properties);
Map<String,Object> m=new HashMap<String,Object>();
m.put("additional_data", new byte[]{'b', 'e', 'l', 'a'});
c.down(new Event(Event.CONFIG, m));
c.connect("bla");
IpAddress addr=(IpAddress)c.getLocalAddress();
System.out.println("address is " + addr);
assertNotNull(addr.getAdditionalData());
assertEquals('b', addr.getAdditionalData()[0]);
c.close();|
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 11 months