April 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-999) Remove deprecated classes or methods

by Bela Ban (JIRA)

Remove deprecated classes or methods ------------------------------------ Key: JGRP-999 URL: https://jira.jboss.org/jira/browse/JGRP-999 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0 Classes/methods annotated with @Deprecated (or @deprecated in the Javadocs) need to be removed -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-1109) Port the AS JChannelFactory impl to JGroups as "JChanelFactory2"

by Brian Stansberry (JIRA)

Port the AS JChannelFactory impl to JGroups as "JChanelFactory2" ---------------------------------------------------------------- Key: JGRP-1109 URL: https://jira.jboss.org/jira/browse/JGRP-1109 Project: JGroups Issue Type: Sub-task Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Optional Fix For: 2.9 Parent task involves API changes, so can't happen before 3.0. A possibility for earlier releases is to add the AS ChannelFactory impl as a second impl, under a different name. Perhaps SharedTransportChannelFactory since the key behavior is the fact that channels it creates all use the shared transport; no MuxChannels are created. Users who wanted that behavior could instantiate SharedTransportChannelFactory instead of the legacy JChannelFactory. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JGRP-909) JChannel: change getLocalAddress() to getAddress()

by Bela Ban (JIRA)

JChannel: change getLocalAddress() to getAddress() --------------------------------------------------- Key: JGRP-909 URL: https://jira.jboss.org/jira/browse/JGRP-909 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 3.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-835) RpcDispatcher/MessageDispatcher: remove deadlock_detection parameters

by Bela Ban (JIRA)

RpcDispatcher/MessageDispatcher: remove deadlock_detection parameters --------------------------------------------------------------------- Key: JGRP-835 URL: https://jira.jboss.org/jira/browse/JGRP-835 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0 related to https://jira.jboss.org/jira/browse/JGRP-828 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-412) Replace all uses of Channel.receive() with Receiver.receive() callbacks

by Bela Ban (JIRA)

Replace all uses of Channel.receive() with Receiver.receive() callbacks ----------------------------------------------------------------------- Key: JGRP-412 URL: http://jira.jboss.com/jira/browse/JGRP-412 Project: JGroups Issue Type: Task Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 3.0 This includes removing PullPushAdapters and converting MessageDispatcher/RpcDispatcher to use Receiver instead of PullPushAdapter -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JGRP-453) Change signature of Channel.down() to return Object, rename downcall() to down()

by Bela Ban (JIRA)

Change signature of Channel.down() to return Object, rename downcall() to down() -------------------------------------------------------------------------------- Key: JGRP-453 URL: http://jira.jboss.com/jira/browse/JGRP-453 Project: JGroups Issue Type: Task Affects Versions: 2.5 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 3.0 We had to make Channel.down() return void, otherwise JGroups would not have been backwards compatible with JBoss 4.0.5 -- 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, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-612) ChannelFactory should have only channel create methods

by Vladimir Blagojevic (JIRA)

ChannelFactory should have only channel create methods ------------------------------------------------------ Key: JGRP-612 URL: http://jira.jboss.com/jira/browse/JGRP-612 Project: JGroups Issue Type: Task Affects Versions: 2.5, 2.6, 2.7, 2.x Reporter: Vladimir Blagojevic Assigned To: Bela Ban Fix For: 3.0 ChannelFactory should not have setMultiplexerConfig methods but rather only create channel methods. Multiplexer configuration can be initialized through implementors constructor. -- 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, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JGRP-1185) JChannel: remove mq

by Bela Ban (JIRA)

JChannel: remove mq ------------------- Key: JGRP-1185 URL: https://jira.jboss.org/jira/browse/JGRP-1185 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0 Remove message queue, as it is not needed anymore -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-1108) Replace JChannelFactory with one based on the JBoss AS impl

by Brian Stansberry (JIRA)

Replace JChannelFactory with one based on the JBoss AS impl ----------------------------------------------------------- Key: JGRP-1108 URL: https://jira.jboss.org/jira/browse/JGRP-1108 Project: JGroups Issue Type: Task Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 3.0 As part of JGRP-612, modify JChannelFactory to work more like the JBAS JChannelFactory -- ensuring channels have a singleton name etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JGRP-743) Remove Multiplexer, MuxChannel

by Bela Ban (JIRA)

Remove Multiplexer, MuxChannel ------------------------------ Key: JGRP-743 URL: http://jira.jboss.com/jira/browse/JGRP-743 Project: JGroups Issue Type: Task Reporter: Bela Ban Assigned To: Bela Ban Fix For: 3.0 Replaced by shared transport -- 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, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JGRP-994) JChannel: remove AUTO_RECONNECT and AUTO_GETSTATE options

by Bela Ban (JIRA)

JChannel: remove AUTO_RECONNECT and AUTO_GETSTATE options --------------------------------------------------------- Key: JGRP-994 URL: https://jira.jboss.org/jira/browse/JGRP-994 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JGRP-907) Drop org.jgroups.persistence package

by Bela Ban (JIRA)

Drop org.jgroups.persistence package ------------------------------------ Key: JGRP-907 URL: https://jira.jboss.org/jira/browse/JGRP-907 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 3.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-513) Remove deprecated system properties (non 'jboss' namespace)

by Brian Stansberry (JIRA)

Remove deprecated system properties (non 'jboss' namespace) ----------------------------------------------------------- Key: JGRP-513 URL: http://jira.jboss.com/jira/browse/JGRP-513 Project: JGroups Issue Type: Task Reporter: Brian Stansberry Assigned To: Bela Ban Priority: Minor As discussed on http://wiki.jboss.org/wiki/Wiki.jsp?page=SystemProps there are a number of deprecated, 'legacy' system properties. This is just a JIRA entry to track remembering to clean them up. This JIRA is for the non-'jboss' namespaced properties, which perhaps we would keep around longer than the 'jboss' ones. -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JGRP-512) Remove support for deprecated 'jboss' namespaced system properties

by Brian Stansberry (JIRA)

Remove support for deprecated 'jboss' namespaced system properties ------------------------------------------------------------------ Key: JGRP-512 URL: http://jira.jboss.com/jira/browse/JGRP-512 Project: JGroups Issue Type: Task Reporter: Brian Stansberry Assigned To: Bela Ban Priority: Minor As discussed on http://wiki.jboss.org/wiki/Wiki.jsp?page=SystemProps there are a number of deprecated, 'legacy' system properties. This is just a JIRA entry to track remembering to clean them up. I'm creating a separate JIRA for the non-'jboss' namespaced properties. Use of the 'jboss' namespace isn't too good, so it might be justified removing those earlier, e.g. 2.5, so users won't use them in AS 5.x and expect them to work. -- 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, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JGRP-694) Convert documentation to new DocBook format

by Richard Achmatowicz (JIRA)

Convert documentation to new DocBook format ------------------------------------------- Key: JGRP-694 URL: http://jira.jboss.com/jira/browse/JGRP-694 Project: JGroups Issue Type: Task Reporter: Richard Achmatowicz Assigned To: Bela Ban Fix For: 2.7 Convert existing JGroups documentation shipped with the release to the new DocBook format. -- 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, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JGRP-1046) FC: change semantics of min_threshold

by Bela Ban (JIRA)

FC: change semantics of min_threshold ------------------------------------- Key: JGRP-1046 URL: https://jira.jboss.org/jira/browse/JGRP-1046 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0 FC.max_credits=1000000,min_threshold=0.2: This means that when a receiver's credits for a sender drop below 800'000 bytes, the receiver will send 200'000 bytes to the sender. This can be misleading because one might think min_threshold means the number of bytes *remaining* after which to send new credits. We need to either change the semantics of min_threshold, or introduce a new property. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-563) Consolidate state transfer API to use streams

by Vladimir Blagojevic (JIRA)

Consolidate state transfer API to use streams --------------------------------------------- Key: JGRP-563 URL: http://jira.jboss.com/jira/browse/JGRP-563 Project: JGroups Issue Type: Task Reporter: Vladimir Blagojevic Assigned To: Vladimir Blagojevic Fix For: 3.0 Although streaming state transfer has its advantages over byte based state transfer, byte based state transfer is absolutely necessary since streaming based transfer relies on plain sockets that are not firewall friendly. However, that does not mean that we cannot consolidate state transfer API at application level and mask byte based transfer with streams. We have already done this in JBC 2.0 so there is no reason not to do it on JGroups level as well. Advantages: - simpler state transfer API - interchangeable state transfer mechanism without affect on application - simplification of client application Disadvantages: - we break current API by eliminating getState(byte[]) and setState(byte []) -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JGRP-567) Add one shot state transfer for multiple substates

by Vladimir Blagojevic (JIRA)

Add one shot state transfer for multiple substates -------------------------------------------------- Key: JGRP-567 URL: http://jira.jboss.com/jira/browse/JGRP-567 Project: JGroups Issue Type: Feature Request Affects Versions: 2.x Reporter: Vladimir Blagojevic Assigned To: Vladimir Blagojevic Currently (2.5) each sub state transfer requires separate state transfer invocation for each sub state. It would be very convenient if we could transfer a list of substates all in one underlying state transfer. This would require introduction of a new method in JChannel API, however we should avoid additional callbacks on application level. Proposed API for additional JChannel method is: public boolean getState(Address target, List<String> state_ids, long timeout) throws ChannelNotConnectedException, ChannelClosedException; -- 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, 4 months

2
9
0 / 0

[JBoss JIRA] Created: (JBAS-7922) MDB transaction still commits when EJB container is not started, resulting in undelivered messages being ACK'd

by Robert West (JIRA)

MDB transaction still commits when EJB container is not started, resulting in undelivered messages being ACK'd -------------------------------------------------------------------------------------------------------------- Key: JBAS-7922 URL: https://jira.jboss.org/jira/browse/JBAS-7922 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-5.1.0.GA Environment: Version info: JBoss 5.1.0 GA (we use a local build, and have updated JBoss Cache to 3.2.1.GA, JBossTS to 4.6.1.GA_CP03 and JGroups to 2.6.13.GA to pick up bug fixes for issues we have encountered in production) ActiveMQ 5.3.0 GA HornetQ 2.0.0 GA Java 1.6.0_17 Mac OS 10.6.2 Reporter: Robert West Assignee: Carlo de Wolf Priority: Critical Testing scenario: Deployed JBoss 5.1.0.GA (with tweaks to the pom during build, see Environment) with a JCA adapter for an external JMS broker, used both ActiveMQ 5.3.0 and HornetQ 2.0.0, both clustered and standalone. Also tried an embedded HornetQ broker with the same results. Deployed an ear that has a simple MDB requiring container managed transactions listening to a queue with max sessions set to 2 and a simple jsp to publish an arbitrary number of text messages to that queue. The MDB simply prints the text information provided by the message, but also has a hard-coded 1 second pause for every even numbered message. When I shut down JBoss while messages are still being consumed, the BlockContainerShutdownInterceptor starts throwing DispatcherConnectExceptions, as the EJB container has been stopped or is in the process of being stopped. However, it doesn't mark the transaction for rollback itself, and MessageInflowLocalProxy.delivery() only marks the transaction for rollback if the invocation chain throws an Error or RuntimeException. Thus, in this case, JBoss failed to deliver the message to the MDB, but committed the transaction. According to the spec, for an MDB with a container managed transaction, the message should be ACK'd to the broker if the transaction successfully commits, and both the ActiveMQ and HornetQ JCA implementations dutifully do this, resulting in all messages that were attempted to be delivered after the EJB container shutdown being lost. When the BlockContainerShutdownInterceptor detects that the EJB container has been shutdown, it needs to take an action that will ensure the transaction is marked for rollback. After parsing through the code involved in the interceptor chain, I can see a few potential solutions: * Have BlockContainerShutdownInterceptor.invoke() call TxUtil.getTransactionManager().setRollbackOnly() before it would throw a DispatcherConnectException. Probably need to consume any exception thrown from setRollbackOnly() and log it first I suppose, although it's always a bit odd when you get an exception thrown when you intend to throw an exception anyway for a different reason. * Have BlockContainerShutdownInterceptor.invoke() put some state on the Invocation to indicate that delivery is being blocked. MessagingContainer.localInvoke() could then take some action based on this state to ensure the transaction is rolled back, either rolling it back itself or notifying its caller that the transaction should be rolled back. A bit odd here if BlockContainerShutdownInterceptor.invoke() continues to throw an exception, as there would be data about the exception being passed back outside the exception though. * Have MessageInflowLocalProxy handle DispatcherConnectExceptions. It might be better to introduce an additional class, say InvocationInterruptedException that DispatcherConnectException could extend, to allow for the possibility that invocations may be interrupted for other reasons, allowing MessageInflowLocalProxy to not care as much about the particular reason invocation was halted, but still be able to roll back the transaction whenever it is. I slightly favor the third approach based on what I've seen of that portion of the code so far, so I will probably work to put together a patch file along those lines. This is the first time I've delved deeply into the JBoss source code though. If I can find some examples of test cases in this part of the code base, I'll attempt to put together a verifying test case as well. I marked the priority as Critical, based on the guidelines, as this is resulting in data loss and as far as I best understand the spec is a violation of the spec. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

4
7
0 / 0

[JBoss JIRA] Created: (JBWEB-107) Cross Domain JSESSIONID Cookie

by Mike Millson (JIRA)

Cross Domain JSESSIONID Cookie ------------------------------ Key: JBWEB-107 URL: http://jira.jboss.com/jira/browse/JBWEB-107 Project: JBoss Web Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tomcat Module Reporter: Mike Millson Assigned To: Mladen Turk Currently the JSESSIONID cookie domain is set to the domain name of the Host that emits the cookie (e.g. www.domain.com). This is an issue with customers using Aliases (e.g. secure.domain.com, zzz.domain.com, etc.), as the session is lost when switching between the main domain and any aliases. In these cases, it would be useful to be able to specify the domain to be "domain.com" so the same JSESSIONID cookie is used across the aliases and converges to the same session. -- 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, 4 months

3
9
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2083) Create "embedded" component for EJB 3.1 EJBContainer implementation

by Andrew Lee Rubinger (JIRA)

Create "embedded" component for EJB 3.1 EJBContainer implementation ------------------------------------------------------------------- Key: EJBTHREE-2083 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2083 Project: EJB 3.0 Issue Type: Feature Request Components: embedded Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Start porting in local development towards the EJB 3.1 Embedded container support. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1999) Create "embedded" component

by Andrew Lee Rubinger (JIRA)

Create "embedded" component --------------------------- Key: EJBTHREE-1999 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1999 Project: EJB 3.0 Issue Type: Task Components: embedded Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Create a component w/ SPI/API, build, and impl modules to house the E-EJB3 configuration -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (SECURITY-31) White Paper on JMX Security

by Anil Saldhana (JIRA)

White Paper on JMX Security --------------------------- Key: SECURITY-31 URL: http://jira.jboss.com/jira/browse/SECURITY-31 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: White Papers Reporter: Anil Saldhana Assigned To: Anil Saldhana There is a need for a simple technical white paper that talks about the various scenarios involved in security jmx in JBoss. This includes the jmx consoles as well as the invokers. -- 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, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWEB-95) Provide a com.sun.net.httpserver.HttpServerProvider implementation

by Scott M Stark (JIRA)

Provide a com.sun.net.httpserver.HttpServerProvider implementation ------------------------------------------------------------------ Key: JBWEB-95 URL: http://jira.jboss.com/jira/browse/JBWEB-95 Project: JBoss Web Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tomcat Module Reporter: Scott M Stark Assigned To: Mladen Turk To plug jbossweb into jdk6, we need a com.sun.net.httpserver.HttpServerProvider implementation http://java.sun.com/javase/6/docs/jre/api/net/httpserver/spec/com/sun/net... -- 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, 4 months

2
12
0 / 0

[JBoss JIRA] Created: (SECURITY-468) Annotations @RolesAllowed, @PermitAll and @DenyAll for authorization

by Anil Saldhana (JIRA)

Annotations @RolesAllowed, @PermitAll and @DenyAll for authorization -------------------------------------------------------------------- Key: SECURITY-468 URL: https://jira.jboss.org/jira/browse/SECURITY-468 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: PicketBox Affects Versions: PicketBox_v3_0_beta2 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: PicketBox_v3_0_beta3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-6519) JCA / XAResourceRecovery

by Jesper Pedersen (JIRA)

JCA / XAResourceRecovery ------------------------ Key: JBAS-6519 URL: https://jira.jboss.org/jira/browse/JBAS-6519 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JCA service Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: JBossAS-5.1.0.Beta1 Add support for org.jboss.tm.XAResourceRecovery in the JCA layer -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
8
0 / 0

[JBoss JIRA] Created: (JBAS-5474) @PostLoad -> LazyInitializationException: illegal access to loading collection ond a @OneToMany with FetchType.EAGER

by Stefan Lindner (JIRA)

@PostLoad -> LazyInitializationException: illegal access to loading collection ond a @OneToMany with FetchType.EAGER -------------------------------------------------------------------------------------------------------------------- Key: JBAS-5474 URL: http://jira.jboss.com/jira/browse/JBAS-5474 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-4.2.2.GA Environment: Win XP SP2, Java 1.5.0_15-b04 Reporter: Stefan Lindner Assigned To: Carlo de Wolf Fix For: JBossAS-4.2.3.GA I have a bean with a @OneToMany relation mapping like private List<TherapieeinheitBean> therapieeinheiten; @OneToMany( cascade = {CascadeType.REFRESH}, fetch = FetchType.EAGER, mappedBy="therapiekatalog" ) with FetchType.EAGER and a simnple @PostLoad like @PostLoad public void postLoad() { System.out.println("!!!!!!!!!! postLoad !!!!!!!!!!"); System.out.print("size: " + therapieeinheiten.size()); } When an entity of this bean is loaded JBoss trows org.hibernate.LazyInitializationException: illegal access to loading collection at org.hibernate.collection.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:341) at org.hibernate.collection.AbstractPersistentCollection.read(AbstractPersistentCollection.java:86) at org.hibernate.collection.PersistentBag.iterator(PersistentBag.java:249) at de.visiodesk.therapiekatalog.TherapiekatalogBean.postLoad(TherapiekatalogBean.java:170) . . . and prints the messages WARN [LoadContexts] fail-safe cleanup (collections) : org.hibernate.engine.loading.CollectionLoadContext@2c8ce9<rs=Ingres-ResultSet[18523]> WARN [CollectionLoadContext] On CollectionLoadContext#cleanup, localLoadingCollectionKeys contained [206] entries afterwards. The PostLoad method should be called after the data was completely loaded. Is there a workaround for this Problem? I found some other ressources on the net where peole had the same problem, but I saw no resolution, no hint, no workaround. -- 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, 4 months

9
15
0 / 0

[JBoss JIRA] Created: (JBREM-1182) Update testsuite to run under Hudson

by Richard Achmatowicz (JIRA)

Update testsuite to run under Hudson -------------------------------------- Key: JBREM-1182 URL: https://jira.jboss.org/jira/browse/JBREM-1182 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Components: general Affects Versions: 2.2.3.SP1 Reporter: Richard Achmatowicz Fix For: 2.2.3.SP2 Update the JBoss Remoting testsuite to run under Hudson. Some current problems include: (i) on Linux, JRunit based tests are failing due to members not finding each other (ii) on Linux, under JDK6, JRunit based tests are not able to create a JGroups stack (iii) JRunit system properties specified by the user on the command line are not being passed the the JUnit targets correctly, and so have no effect on the tests -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
25
0 / 0

[JBoss JIRA] Created: (JBAS-5559) Example MC configuration for JBossCache instance with JDBCCacheLoader

by Galder Zamarreno (JIRA)

Example MC configuration for JBossCache instance with JDBCCacheLoader --------------------------------------------------------------------- Key: JBAS-5559 URL: http://jira.jboss.com/jira/browse/JBAS-5559 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation, JBoss Cache Reporter: Galder Zamarreno Assigned To: Galder Zamarreno Priority: Minor Include an example on how to configure a JBossCache instance's JDBCCacheLoader via MC. -- 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, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBCL-94) Spaces in URLs returned by getResource() should in vfszip: handler

by Ondrej Medek (JIRA)

Spaces in URLs returned by getResource() should in vfszip: handler ------------------------------------------------------------------ Key: JBCL-94 URL: https://jira.jboss.org/jira/browse/JBCL-94 Project: JBoss ClassLoader Issue Type: Bug Components: ClassLoader Environment: JBoss AS 5.0.1, WinXP, JDK 1.6.0u12 Reporter: Ondrej Medek Priority: Minor Hi, I have an EAR deployed as directory (not as JAR). Inside I have one service bean and a config directory. I have tried to deploy config directory as a plain directory and packed in the JAR. I have spotted different behaviour of handling spaces in the resource URLS returned by org.jboss.classloader.spi.base.BaseClassLoader when accessing the config directory. My service bean reads config direcory by: this.getClass().getClassLoader().getResource("conf/") I get the URL: vfsfile:/C:/Program%20Files/JBoss/jboss-5.0.1.GA/server/default/deploy/prinsee-ear.ear/conf/ (Space is '%20') however, when I put the resource in the JAR and access it by: this.getClass().getClassLoader().getResource("prinsee-client.jar/conf") I get the URL: vfszip:/C:/Program Files/JBoss/jboss-5.0.1.GA/server/default/deploy/prinsee-ear.ear/prinsee-client.jar/conf/ (Space is ' '). I think, the behaviour of vfszip: handler is wrong. The space should be always '%20'. Cheers andy -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (JBVFS-60) Need better hasBeenModified implementation

by Scott M Stark (JIRA)

Need better hasBeenModified implementation ------------------------------------------ Key: JBVFS-60 URL: https://jira.jboss.org/jira/browse/JBVFS-60 Project: JBoss VFS Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR1 Reporter: Scott M Stark Fix For: 2.0.0.GA The current hasBeenModified implementation relies on the URLConnection.getLastModified() value. This has relatively low resolution (~1ms) on some systems and rapid changes to the underlying files is not be reflected. One example of this was the JBVFS-59 repeated updates to a link file not been seen. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (JBVFS-50) Don't use host names in custom vfs urls

by Adrian Brock (JIRA)

Don't use host names in custom vfs urls --------------------------------------- Key: JBVFS-50 URL: https://jira.jboss.org/jira/browse/JBVFS-50 Project: JBoss VFS Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Adrian Brock The InMemory vfs and AssembledDirectory vfs are using host names as part of their urls/uris. This is causing the JDK to do some kind of security check which involves going to the dns to try to determine the ip address of the host. This is obviously inefficent. The URL schemes should be changed not to use host names. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

4
5
0 / 0

[JBoss JIRA] Created: (JBJCA-94) Reauthentication support

by Jesper Pedersen (JIRA)

Reauthentication support ------------------------ Key: JBJCA-94 URL: https://jira.jboss.org/jira/browse/JBJCA-94 Project: JBoss JCA Issue Type: Task Components: Core Reporter: Jesper Pedersen Assignee: Jesper Pedersen Implement reauthentication support. See chapter 8 and related security discussions for details. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (JBRULES-1644) Make drools imply null checks before trying to read a value

by Alex McCarrier (JIRA)

Make drools imply null checks before trying to read a value ----------------------------------------------------------- Key: JBRULES-1644 URL: http://jira.jboss.com/jira/browse/JBRULES-1644 Project: JBoss Drools Issue Type: Feature Request Components: Drl Parser/Builder Affects Versions: 4.0.6 Environment: all Reporter: Alex McCarrier Assigned To: Mark Proctor Priority: Minor Fix For: FUTURE Not sure if this is MVEL or drools itself, but it would be nice if it would do null checks on fields for you rather than having the rule author do it. Example, when doing something like: when Object(value1.value2 == something) before attempting to read value2 it makes sure value1 is not null, and if value1 is null than rather than throwing an error like it does currently, just consider the rule as not matching. -- 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, 5 months

3
2
0 / 0

[JBoss JIRA] Created: (JBJCA-260) Create a WorkManager implementation that uses JBoss Threads

by Jesper Pedersen (JIRA)

Create a WorkManager implementation that uses JBoss Threads ----------------------------------------------------------- Key: JBJCA-260 URL: https://jira.jboss.org/jira/browse/JBJCA-260 Project: JBoss JCA Issue Type: Task Components: Core Reporter: Jesper Pedersen Assignee: Jesper Pedersen Create a WorkManager implementation that make use of the JBoss Threads project. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBJCA-237) ResourceAdapterAssociation

by Jesper Pedersen (JIRA)

ResourceAdapterAssociation -------------------------- Key: JBJCA-237 URL: https://jira.jboss.org/jira/browse/JBJCA-237 Project: JBoss JCA Issue Type: Task Components: Core, Deployer Reporter: Jesper Pedersen Assignee: Jesper Pedersen Make sure that the ResourceAdapterAssociation interface is probably handled -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBJCA-258) Bind connection factories into JNDI

by Jesper Pedersen (JIRA)

Bind connection factories into JNDI ----------------------------------- Key: JBJCA-258 URL: https://jira.jboss.org/jira/browse/JBJCA-258 Project: JBoss JCA Issue Type: Task Components: Deployer Reporter: Jesper Pedersen Assignee: Jesper Pedersen Bind each connection factory into JNDI. Also set the naming reference in each connection factory. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBJCA-106) SJC: Add support for property maps

by Jesper Pedersen (JIRA)

SJC: Add support for property maps ---------------------------------- Key: JBJCA-106 URL: https://jira.jboss.org/jira/browse/JBJCA-106 Project: JBoss JCA Issue Type: Task Components: Core Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha2 Add support for property maps, so they can be passed in the configuration. The remotable naming server is an example of an use-case. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (JBJCA-31) Testsuite

by Jesper Pedersen (JIRA)

Testsuite --------- Key: JBJCA-31 URL: https://jira.jboss.org/jira/browse/JBJCA-31 Project: JBoss JCA Issue Type: Task Components: Core Reporter: Jesper Pedersen Assignee: Jesper Pedersen Parent task for the test suite for the core implementation -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (JBJCA-25) JDBC3

by Jesper Pedersen (JIRA)

JDBC3 ----- Key: JBJCA-25 URL: https://jira.jboss.org/jira/browse/JBJCA-25 Project: JBoss JCA Issue Type: Task Components: JDBC Reporter: Jesper Pedersen Assignee: Jesper Pedersen The JDBC3 based work -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBJCA-3) Add Maven based build system

by Jesper Pedersen (JIRA)

Add Maven based build system ---------------------------- Key: JBJCA-3 URL: https://jira.jboss.org/jira/browse/JBJCA-3 Project: JBoss JCA Issue Type: Sub-task Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0 Alpha1 Add Maven style build environment -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-5426) Define JCA SPI

by Jesper Pedersen (JIRA)

Define JCA SPI -------------- Key: JBAS-5426 URL: http://jira.jboss.com/jira/browse/JBAS-5426 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JCA service Reporter: Jesper Pedersen Assigned To: Jesper Pedersen Fix For: JBossAS-5.0.0.CR1 We need to define a SPI for the JCA layer in order to better separate clients (f.ex. EJB3) of JCA from the actual implementation. The SPI will live in the jboss-integration module. -- 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, 5 months

2
7
0 / 0

[JBoss JIRA] Created: (JBJCA-268) Provide JCA 1.5 profile of the container

by Jesper Pedersen (JIRA)

Provide JCA 1.5 profile of the container ---------------------------------------- Key: JBJCA-268 URL: https://jira.jboss.org/jira/browse/JBJCA-268 Project: JBoss JCA Issue Type: Task Components: Build, Common, Core, Deployer, Documentation, Embedded Reporter: Jesper Pedersen Assignee: Jesper Pedersen Priority: Blocker Fix For: 1.1.0.CR1 Create a JCA 1.5 profile of the container -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBBUILD-430) Look into bug with maven plugin manager.

by Paul Gier (JIRA)

Look into bug with maven plugin manager. ---------------------------------------- Key: JBBUILD-430 URL: http://jira.jboss.com/jira/browse/JBBUILD-430 Project: JBoss Build System Issue Type: Task Components: Maven Reporter: Paul Gier Fix For: Maven Build - Maint 2007 There seems to be a bug in maven in the plugin resolution when there are different versions of plugins available in different repositories. A maven bug should be submitted, and the issue should be patched. -- 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, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBJCA-263) Support template replace for ds.xml

by Jeff Zhang (JIRA)

Support template replace for ds.xml ----------------------------------- Key: JBJCA-263 URL: https://jira.jboss.org/jira/browse/JBJCA-263 Project: JBoss JCA Issue Type: Feature Request Components: Core Reporter: Jeff Zhang Assignee: Jesper Pedersen template value like ${max.pool} could be replaced in the ds.xml -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

3
7
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2241) Restore user's settings and portlets to default

by Brian Dill (JIRA)

Restore user's settings and portlets to default ----------------------------------------------- Key: JBPORTAL-2241 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2241 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.6.6 Final Reporter: Brian Dill Allow portal users to restore their portal to the original settings/portlets. Excerpt from discussion with Thomas Heute. "They could store the location of the reference as a portal object property of the copied page. And copy what exists for 'Copy this page to my dashboard' link. If the referenced page didn't change, they could then delete the current page, and copy the one referenced as portal object property." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-6012) Seam integration with AnnotationEnvironment / ResourceVisitor

by Ales Justin (JIRA)

Seam integration with AnnotationEnvironment / ResourceVisitor ------------------------------------------------------------- Key: JBAS-6012 URL: https://jira.jboss.org/jira/browse/JBAS-6012 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: MicroContainer bus Affects Versions: JBossAS-5.0.0.CR2 Reporter: Ales Justin Assignee: Ales Justin Priority: Minor Fix For: JBossAS-5.0.0.GA Integrate Seam's annotation / resource lookup with existing JBossAS / MC annotation / resource handling. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
5
0 / 0

[JBoss JIRA] Created: (JBAS-6843) Metadata not created for deployments listed through Classpath attribute of Manifest.MF files

by jaikiran pai (JIRA)

Metadata not created for deployments listed through Classpath attribute of Manifest.MF files -------------------------------------------------------------------------------------------- Key: JBAS-6843 URL: https://jira.jboss.org/jira/browse/JBAS-6843 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployers Affects Versions: JBossAS-5.1.0.CR1, JBossAS-5.1.0.Beta1 Reporter: jaikiran pai Assignee: Ales Justin If a (EJB) *deployment* jar contains a MANIFEST.MF which points to another *deployment* (not a plain jar) through the ClassPath attribute, then the deployment framework does not generate metadata for the deployment listed in MANIFEST.MF Ex: A.jar is an EJB3 deployment which contains a MANIFEST.MF pointing to B.jar (another EJB3 deployment). While processing A.jar (and its entries in MANIFEST.MF), the deployment framework does not generate metadata for B.jar As per EJB3.0 core spec, section 20.3: The ejb-jar ﬁle must contain, either by inclusion or by reference, the class ﬁles of each enterprise bean as follows: - The enterprise bean class. - The enterprise bean business interfaces, web service endpoint interfaces, and home and component interfaces. - Interceptor classes. - The primary key class if the bean is an entity bean. We say that a jar ﬁle contains a second ﬁle "by reference" if the second ﬁle is named in the Class-Path attribute in the Manifest ﬁle of the referencing jar ﬁle or is contained (either by inclusion or by reference) in another jar ﬁle that is named in the Class-Path attribute in the Manifest ﬁle of the referencing jar ﬁle. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

4
8
0 / 0

[JBoss JIRA] Created: (JBRULES-2350) The order of resources are not preserved when loaded by the KnowledgeAgentImpl

by Pieter Martin (JIRA)

The order of resources are not preserved when loaded by the KnowledgeAgentImpl ------------------------------------------------------------------------------ Key: JBRULES-2350 URL: https://jira.jboss.org/jira/browse/JBRULES-2350 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: All Affects Versions: 5.1.0.M1 Reporter: Pieter Martin Assignee: Mark Proctor The order of resources are not preserved when loaded by the KnowledgeAgentImpl. This can cause a dslr file to be loaded before its dsl causing compilation errors. Some investigation shows that the resources are loaded into a HashMap, in the org.drools.agent.impl.KnowledgeAgentImpl class. The map does not preserve the order. Most likely changing the map to a class that where the iteration order is the insertion order will solve the problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2377) Problems with DSL / DSLR files when used with a KnowledgeAgent / Change Sets

by Macon Pegram (JIRA)

Problems with DSL / DSLR files when used with a KnowledgeAgent / Change Sets ---------------------------------------------------------------------------- Key: JBRULES-2377 URL: https://jira.jboss.org/jira/browse/JBRULES-2377 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler, drools-compiler (expert), drools-compiler-DSL Affects Versions: 5.0.1.FINAL Environment: Windows XP, Mac OS X, JDK 1.5.0_12 Reporter: Macon Pegram Assignee: Mark Proctor I tried to address this on the Drools Mailing list but did not receive an answer. See: Mailing list message threads: "[rules-users] DSL, DSLR and Changesets...", "[rules-users] Can DSL / DSLR be loaded in a changeset?" ---- Are DSL and DSLR files supported by the KnowledgeAgent / Changeset code. Here's the details of my test case: I have a Changeset file I'm trying to load which looks like the following: <?xml version="1.0" encoding="UTF-8"?> <change-set xmlns='http://drools.org/drools-5.0/change-set' xmlns:xs='http://www.w3.org/2001/XMLSchema-instance' > <add> <resource source="classpath:com/test/general/" type="DSL" /> <resource source="classpath:com/test/general/" type="DSLR" /> </add> </change-set> There's a single DSL and a single DSLR file in this folder. I'm loading the change set as follows: KnowledgeAgent ka = KnowledgeAgentFactory.newKnowledgeAgent(agentName); ka.applyChangeSet(ResourceFactory.newClassPathResource(agentName + "-changeset.xml", getClass())); When I run this code, the logger suggests the DSL and DSLR are being loaded and compiled: [2009:10:299 16:10:52:info] KnowledgAgent created, with configuration: monitorChangeSetEvents=true scanResources=true scanDirectories=true ++ Constructing and applying changeSet: dsl-test [2009:10:299 16:10:52:info] KnowledegAgent has started listening for ChangeSet notifications (null: 3, 68): cvc-elt.1: Cannot find the declaration of element 'change-set'. [2009:10:299 16:10:317:info] KnowledgAgent applying ChangeSet [2009:10:299 16:10:317:debug] KnowledgeAgent subscribing to directory=[ClassPathResource path='com/test/general/'] [2009:10:299 16:10:317:debug] ResourceChangeNotification subscribing listener=org.drools.agent.impl.KnowledgeAgentImpl@b9b618 to resource=[ClassPathResource path='com/test/general/'] [2009:10:299 16:10:317:debug] ResourceChangeScanner subcribing notifier=org.drools.io.impl.ResourceChangeNotifierImpl@61ec49 to resource=[ClassPathResource path='com/test/general/'] [2009:10:299 16:10:317:debug] KnowledgeAgent subscribing to directory content resource=[FileResource file='C:\bea\user_projects\workspaces\alerts\rules-kb\test-kb\target\test-classes\com\test\general\test.dsl'] [2009:10:299 16:10:317:debug] ResourceChangeNotification subscribing listener=org.drools.agent.impl.KnowledgeAgentImpl@b9b618 to resource=[FileResource file='C:\bea\user_projects\workspaces\alerts\rules-kb\test-kb\target\test-classes\com\test\general\test.dsl'] [2009:10:299 16:10:317:debug] ResourceChangeScanner subcribing notifier=org.drools.io.impl.ResourceChangeNotifierImpl@61ec49 to resource=[FileResource file='C:\bea\user_projects\workspaces\alerts\rules-kb\test-kb\target\test-classes\com\test\general\test.dsl'] [2009:10:299 16:10:317:debug] KnowledgeAgent subscribing to directory content resource=[FileResource file='C:\bea\user_projects\workspaces\alerts\rules-kb\test-kb\target\test-classes\com\test\general\test-dsl.dslr'] [2009:10:299 16:10:317:debug] ResourceChangeNotification subscribing listener=org.drools.agent.impl.KnowledgeAgentImpl@b9b618 to resource=[FileResource file='C:\bea\user_projects\workspaces\alerts\rules-kb\test-kb\target\test-classes\com\test\general\test-dsl.dslr'] [2009:10:299 16:10:317:debug] ResourceChangeScanner subcribing notifier=org.drools.io.impl.ResourceChangeNotifierImpl@61ec49 to resource=[FileResource file='C:\bea\user_projects\workspaces\alerts\rules-kb\test-kb\target\test-classes\com\test\general\test-dsl.dslr'] [2009:10:299 16:10:317:debug] KnowledgeAgent subscribing to directory=[ClassPathResource path='com/hmc/test/general/'] [2009:10:299 16:10:317:debug] ResourceChangeNotification subscribing listener=org.drools.agent.impl.KnowledgeAgentImpl@b9b618 to resource=[ClassPathResource path='com/hmc/test/general/'] [2009:10:299 16:10:317:debug] KnowledgeAgent ChangeSet requires KnowledgeBuilder [2009:10:299 16:10:317:debug] KnowledgeAgent rebuilding KnowledgeBase using ChangeSet [2009:10:299 16:10:317:debug] KnowledgeAgent building resource=[FileResource file='C:\bea\user_projects\workspaces\alerts\rules-kb\test-kb\target\test-classes\com\test\general\test.dsl'] [2009:10:299 16:10:333:debug] KnowledgeAgent building resource=[FileResource file='C:\bea\user_projects\workspaces\alerts\rules-kb\test-kb\target\test-classes\com\test\general\test-dsl.dslr'] [2009:10:299 16:10:333:info] KnowledgeAgent new KnowledgeBase now built and in use However after load is completed I try to run the following code: System.out.println("KB Info"); Collection<KnowledgePackage> pkgs = ka.getKnowledgeBase().getKnowledgePackages(); for (KnowledgePackage kp : pkgs) { for (Rule rule : kp.getRules()) { System.out.println("Rule: " + rule.getName() + ", " + ule.getPackageName()); for (String attribs : rule.listMetaAttributes()) System.out.println("---- " + attribs); } } } I get NO output (except of course "KB Info"). If I initialize the knowledgebase like this: KnowledgeBuilder kbuilder = KnowledgeBuilderFactory .newKnowledgeBuilder(); kbuilder.add(ResourceFactory .newClassPathResource("com/test/general/test.dsl"), ResourceType.DSL); kbuilder.add(ResourceFactory .newClassPathResource("com/test/general/test-dsl.dslr"), ResourceType.DSLR); if (kbuilder.hasErrors()) { throw new Exception(kbuilder.getErrors().toString()); } KnowledgeBase kbase = KnowledgeBaseFactory.newKnowledgeBase(); kbase.addKnowledgePackages(kbuilder.getKnowledgePackages()); } ... and run the same output code I get a list of the rules that were loaded. Any clues why the different behavior? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

2
10
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2010