[JBoss JIRA] (AS7-1762) rewrite rule doesnt function
by Carl L (JIRA)
[ https://issues.jboss.org/browse/AS7-1762?page=com.atlassian.jira.plugin.s... ]
Carl L commented on AS7-1762:
-----------------------------
Hi, Carlos. I've haven't test in EAP but rewrite has been working fine for us with JBoss 7.1.1. We added {{flags="L"}} to our tag, but I'm not sure if that's significant in this case. Current rule:
{code}
<rewrite pattern="^/(.*)/([\w\-]+)$" substitution="/$1/$2.jsp" flags="L"/>
{code}
> rewrite rule doesnt function
> ----------------------------
>
> Key: AS7-1762
> URL: https://issues.jboss.org/browse/AS7-1762
> Project: Application Server 7
> Issue Type: Bug
> Components: Web
> Affects Versions: 7.0.1.Final
> Reporter: jefimm
> Assignee: Remy Maucherat
> Fix For: 7.1.0.Beta1
>
> Attachments: helloworld.war
>
>
> I have tried to add the following configuration to the standalone.xml <virtual-server> node:
> <virtual-server name="default-host">
> <alias name="localhost"/>
> <alias name="example.com"/>
> <rewrite pattern="^/helloworld(.*)" substitution="/helloworld/test.jsp"/>
> </virtual-server>
> and I have deployed the helloworld.war, however the rewrite does not work (I know I can deploy war at the root context I just want to test the rewrite).
--
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
10 years, 8 months
[JBoss JIRA] (AS7-1762) rewrite rule doesnt function
by Carl L (JIRA)
[ https://issues.jboss.org/browse/AS7-1762?page=com.atlassian.jira.plugin.s... ]
Carl L edited comment on AS7-1762 at 8/29/13 12:42 PM:
-------------------------------------------------------
Hi, Carlos. I've haven't tested in EAP but rewrite has been working fine for us with JBoss 7.1.1. We added {{flags="L"}} to our tag, but I'm not sure if that's significant in this case. Current rule:
{code}
<rewrite pattern="^/(.*)/([\w\-]+)$" substitution="/$1/$2.jsp" flags="L"/>
{code}
was (Author: scorcher14x):
Hi, Carlos. I've haven't test in EAP but rewrite has been working fine for us with JBoss 7.1.1. We added {{flags="L"}} to our tag, but I'm not sure if that's significant in this case. Current rule:
{code}
<rewrite pattern="^/(.*)/([\w\-]+)$" substitution="/$1/$2.jsp" flags="L"/>
{code}
> rewrite rule doesnt function
> ----------------------------
>
> Key: AS7-1762
> URL: https://issues.jboss.org/browse/AS7-1762
> Project: Application Server 7
> Issue Type: Bug
> Components: Web
> Affects Versions: 7.0.1.Final
> Reporter: jefimm
> Assignee: Remy Maucherat
> Fix For: 7.1.0.Beta1
>
> Attachments: helloworld.war
>
>
> I have tried to add the following configuration to the standalone.xml <virtual-server> node:
> <virtual-server name="default-host">
> <alias name="localhost"/>
> <alias name="example.com"/>
> <rewrite pattern="^/helloworld(.*)" substitution="/helloworld/test.jsp"/>
> </virtual-server>
> and I have deployed the helloworld.war, however the rewrite does not work (I know I can deploy war at the root context I just want to test the rewrite).
--
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
10 years, 8 months
[JBoss JIRA] (DROOLS-235) Issues with Drools Eclipse plugin
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-235?page=com.atlassian.jira.plugin... ]
Mario Fusco resolved DROOLS-235.
--------------------------------
Resolution: Done
That further issue was caused by the new ClassLoader. I fixed it.
> Issues with Drools Eclipse plugin
> ---------------------------------
>
> Key: DROOLS-235
> URL: https://issues.jboss.org/browse/DROOLS-235
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 6.0.0.CR2
> Reporter: Kris Verlaenen
> Assignee: Mario Fusco
> Fix For: 6.0.0.CR3
>
> Attachments: Screenshot1.png
>
>
> When generating a sample Drools project with the Eclipse plugin (6.0.x), there are several issues:
> * When DroolsBuilder is trying to parse the Sample.drl, it seems to be failing to import the Message class (resulting in 11 errors in the problems view), see screenshot1. Executing the test does seem to work though
> * When both Sample.drl and Sample.xls are created in the same project, the imports seems to clash, executing the test fails when compiling:
> java.lang.RuntimeException: Error while creating KieBase[Message [id=1, level=ERROR, path=rules/Sample.drl, line=15, column=0
> text=Rule Compilation error The import com.sample.DroolsTest.Message collides with another import statement], Message [id=2, level=ERROR, path=dtables/Sample.xls, line=15, column=0
> text=Rule Compilation error The import com.sample.DroolsTest.Message collides with another import statement], Message [id=3, level=ERROR, path=dtables/Sample.xls, line=5, column=0
> text=Rule Compilation error The import com.sample.DroolsTest.Message collides with another import statement], Message [id=4, level=ERROR, path=rules/Sample.drl, line=5, column=0
> text=Rule Compilation error The import com.sample.DroolsTest.Message collides with another import statement]]
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:170)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:298)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:273)
> at com.sample.DroolsTest.main(DroolsTest.java:17)
> Isn't this allowed?
> * When executing DroolsTest, there seems to be a Sysout somewhere in the code base:
> kmodules: file:/NotBackedUp/jBPM-6.0.0.CR2/jbpm-installer/workspace/drools/target/META-INF/kmodule.xml
--
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
10 years, 8 months
[JBoss JIRA] (WFLY-1967) Connection properties should be extracted automatically when creating a new Datasource
by Jesper Pedersen (JIRA)
[ https://issues.jboss.org/browse/WFLY-1967?page=com.atlassian.jira.plugin.... ]
Jesper Pedersen updated WFLY-1967:
----------------------------------
Labels: JDBC JDBC_connection open_to_community (was: JDBC JDBC_connection)
Assignee: (was: Jesper Pedersen)
Affects Version/s: (was: 8.0.0.Alpha4)
> Connection properties should be extracted automatically when creating a new Datasource
> --------------------------------------------------------------------------------------
>
> Key: WFLY-1967
> URL: https://issues.jboss.org/browse/WFLY-1967
> Project: WildFly
> Issue Type: Enhancement
> Components: JCA
> Reporter: Jay Wu
> Priority: Optional
> Labels: JDBC, JDBC_connection, open_to_community
>
> When create a new Datasource, it needs to input the connection properties such as databaseName, serverName, user, password etc even also the datasouce class manually.
> It should be enhanced for the ease for operation to extract the connection properties automatically when creating a new Datasource
--
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
10 years, 8 months
[JBoss JIRA] (WFLY-1972) CLI command should not allow same runtime-name to be used at another deploy
by Emmanuel Hugonnet (JIRA)
[ https://issues.jboss.org/browse/WFLY-1972?page=com.atlassian.jira.plugin.... ]
Emmanuel Hugonnet updated WFLY-1972:
------------------------------------
Description:
Having two deployments with the same runtime-name in the domain content repository, so they can be deployed to different instances, is ok.
Having two deployments with the same runtime name actually deployed to an instance is not (that's the issue here).
Same for standalone.
> CLI command should not allow same runtime-name to be used at another deploy
> ---------------------------------------------------------------------------
>
> Key: WFLY-1972
> URL: https://issues.jboss.org/browse/WFLY-1972
> Project: WildFly
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Emmanuel Hugonnet
> Assignee: Brian Stansberry
>
> Having two deployments with the same runtime-name in the domain content repository, so they can be deployed to different instances, is ok.
> Having two deployments with the same runtime name actually deployed to an instance is not (that's the issue here).
> Same for standalone.
--
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
10 years, 8 months
[JBoss JIRA] (DROOLS-244) Sliding windows working incorrectly
by Vytautas Gimbutas (JIRA)
[ https://issues.jboss.org/browse/DROOLS-244?page=com.atlassian.jira.plugin... ]
Vytautas Gimbutas updated DROOLS-244:
-------------------------------------
Attachment: Event.java
file.drl
Transaction.java
TransactionCompletedEvent.java
TransactionCreatedEvent.java
TransactionEvent.java
> Sliding windows working incorrectly
> -----------------------------------
>
> Key: DROOLS-244
> URL: https://issues.jboss.org/browse/DROOLS-244
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Vytautas Gimbutas
> Assignee: Mark Proctor
> Attachments: Event.java, file.drl, Transaction.java, TransactionCompletedEvent.java, TransactionCreatedEvent.java, TransactionEvent.java
>
>
> I'm having an issue with sliding windows. For some reason even though event is in the past it still gets into the window.
> I'm attaching drl file, the event/fact classes.
> I expect it to print 1 0, but instead it prints: 1 1
> The code that reproduces the issue:
> KnowledgeBuilder kbuilder = KnowledgeBuilderFactory.newKnowledgeBuilder();
> kbuilder.add(ResourceFactory.newClassPathResource("file.drl") , ResourceType.DRL);
> if (kbuilder.hasErrors() ) {
> System.out.println( kbuilder.getErrors() );
> }
> KnowledgeBase kbase = KnowledgeBaseFactory.newKnowledgeBase();
> kbase.addKnowledgePackages(kbuilder.getKnowledgePackages());
> StatefulKnowledgeSession ksession = kbase.newStatefulKnowledgeSession();
> Transaction transaction = new Transaction();
> TransactionCompletedEvent event = new TransactionCompletedEvent();
> event.setTransaction(transaction);
> ksession.insert(transaction);
> Date today = new Date();
> Calendar cal = new GregorianCalendar();
> cal.setTime(today);
> cal.add(Calendar.DAY_OF_MONTH, -30);
> event.setCreated(cal.getTime());
> WorkingMemoryEntryPoint wmep = ksession.getWorkingMemoryEntryPoint("TransactionCompletedEventStream");
> wmep.insert(event);
> ksession.fireAllRules();
> TransactionCreatedEvent event2 = new TransactionCreatedEvent();
> event2.setTransaction(transaction);
> ksession.insert(transaction);
> ksession.getWorkingMemoryEntryPoint("TransactionCreatedEventStream").insert(event2);
> ksession.fireAllRules();
--
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
10 years, 8 months
[JBoss JIRA] (WFLY-1907) The whoami operation is not usable with the JMX integration.
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-1907?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse updated WFLY-1907:
-----------------------------------
Description:
The whoami operation is not usable with the JMX integration as the return type is Void.
Need to review the operation description for the correct return type.
{code}
[standalone@localhost:9990 /] :whoami(verbose=true)
{
"outcome" => "success",
"result" => {
"identity" => {
"username" => "darranl",
"realm" => "ManagementRealm"
},
"groups" => [
"One",
"Two",
"Three"
],
"roles" => [
"One",
"Two",
"Three"
]
}
}
{code}
was:
The whoami operation is not usable with the JMX integration as the return type is Void.
Need to review the operation description for the correct return type.
> The whoami operation is not usable with the JMX integration.
> ------------------------------------------------------------
>
> Key: WFLY-1907
> URL: https://issues.jboss.org/browse/WFLY-1907
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, JMX
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 8.0.0.Beta1
>
>
> The whoami operation is not usable with the JMX integration as the return type is Void.
> Need to review the operation description for the correct return type.
> {code}
> [standalone@localhost:9990 /] :whoami(verbose=true)
> {
> "outcome" => "success",
> "result" => {
> "identity" => {
> "username" => "darranl",
> "realm" => "ManagementRealm"
> },
> "groups" => [
> "One",
> "Two",
> "Three"
> ],
> "roles" => [
> "One",
> "Two",
> "Three"
> ]
> }
> }
> {code}
--
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
10 years, 8 months
[JBoss JIRA] (DROOLS-244) Sliding windows working incorrectly
by Vytautas Gimbutas (JIRA)
Vytautas Gimbutas created DROOLS-244:
----------------------------------------
Summary: Sliding windows working incorrectly
Key: DROOLS-244
URL: https://issues.jboss.org/browse/DROOLS-244
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Vytautas Gimbutas
Assignee: Mark Proctor
I'm having an issue with sliding windows. For some reason even though event is in the past it still gets into the window.
I'm attaching drl file, the event/fact classes.
I expect it to print 1 0, but instead it prints: 1 1
The code that reproduces the issue:
KnowledgeBuilder kbuilder = KnowledgeBuilderFactory.newKnowledgeBuilder();
kbuilder.add(ResourceFactory.newClassPathResource("file.drl") , ResourceType.DRL);
if (kbuilder.hasErrors() ) {
System.out.println( kbuilder.getErrors() );
}
KnowledgeBase kbase = KnowledgeBaseFactory.newKnowledgeBase();
kbase.addKnowledgePackages(kbuilder.getKnowledgePackages());
StatefulKnowledgeSession ksession = kbase.newStatefulKnowledgeSession();
Transaction transaction = new Transaction();
TransactionCompletedEvent event = new TransactionCompletedEvent();
event.setTransaction(transaction);
ksession.insert(transaction);
Date today = new Date();
Calendar cal = new GregorianCalendar();
cal.setTime(today);
cal.add(Calendar.DAY_OF_MONTH, -30);
event.setCreated(cal.getTime());
WorkingMemoryEntryPoint wmep = ksession.getWorkingMemoryEntryPoint("TransactionCompletedEventStream");
wmep.insert(event);
ksession.fireAllRules();
TransactionCreatedEvent event2 = new TransactionCreatedEvent();
event2.setTransaction(transaction);
ksession.insert(transaction);
ksession.getWorkingMemoryEntryPoint("TransactionCreatedEventStream").insert(event2);
ksession.fireAllRules();
--
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
10 years, 8 months