[JBoss JIRA] Resolved: (JBRULES-269) Parser to be stricter with newlines
by Edson Tirelli (JIRA)
[ http://jira.jboss.com/jira/browse/JBRULES-269?page=all ]
Edson Tirelli resolved JBRULES-269.
-----------------------------------
Fix Version/s: 3.1-m1
(was: 3.1-m3)
Resolution: Done
New parser was rewrote. Closing the issue for new line enforcement.
Colisions will be handle in the other issue.
> Parser to be stricter with newlines
> -----------------------------------
>
> Key: JBRULES-269
> URL: http://jira.jboss.com/jira/browse/JBRULES-269
> Project: JBoss Rules
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Drl Parser/Builder
> Affects Versions: 3.0-rc2
> Reporter: Michael Neale
> Assigned To: Edson Tirelli
> Fix For: 3.1-m1
>
>
> Given that we are not going down the route of
> when {
> }
> style brackets, we will need to be stricter about newlines.
> In otherwords, newlines are required I believe in the following scenarious:
> before a when,
> after a when before the LHS
> before a then
> after a then before then RHS
> before an end (at the end of the rule).
> when,then, end - should all appear on a line by themselves.
> Optionally (perhaps?) rule should always be at the start of a newline.
> on a similar note, should rule and end be at the start of a newline? (don't really want to have to enforce column positions - but it is kind of needed).
--
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
19 years, 3 months
[JBoss JIRA] Updated: (JBAS-1313) RepositorySelector should be integrated into JBoss Server
by Tamas Cserveny (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-1313?page=all ]
Tamas Cserveny updated JBAS-1313:
---------------------------------
Attachment: log4-rs.zip
This is the implementation. I think this should be in initialized the same way as log4jservice, since you cannot really undeploy a log4j repository selector.
> RepositorySelector should be integrated into JBoss Server
> ---------------------------------------------------------
>
> Key: JBAS-1313
> URL: http://jira.jboss.com/jira/browse/JBAS-1313
> Project: JBoss Application Server
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JMX
> Reporter: Stan Silvert
> Assigned To: Stan Silvert
> Priority: Minor
> Fix For: JBossAS-4.2.0.CR1
>
> Attachments: log4-rs.zip
>
>
> Often, an application will want to have its own log4j configuration and have all log messages generated go to an application-specific log file. Solutions to this problem are documented on this wiki page: http://www.jboss.org/wiki/Wiki.jsp?page=Logging
> The log4j RepositorySelector provides a clean solution to this problem without any special classloader settings. However, at the present time, a developer must create his own version of a RepositorySelector and make sure his application initializes it properly.
> This can be difficult to accomplish because the RepositorySelector feature is not well known and takes time to understand. It can also be difficult to make sure that the RepositorySelector is initialized before the application makes ANY call to Logger.getLogger().
> We can instead, provide a RepositorySelector implementation as part of the JBoss Application server. If a deployer finds a log4j.xml file in the /META-INF direcotry (or /WEB-INF for WARs) it would add an entry into the RepositorySelector for that application. Then, logging from that application would use the custom log4j configuration.
--
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
19 years, 3 months