[JBoss JIRA] (DROOLS-235) Issues with Drools Eclipse plugin
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-235?page=com.atlassian.jira.plugin... ]
Kris Verlaenen reopened DROOLS-235:
-----------------------------------
Still have the issue with the imports. So with a kmodule.xml it seems to be working now. But if you don't have a kmodule.xml, it seems it still can't find any custom classes when parsing rules. So for example, if you genereate a new Drools project but with Drools 5.1.x code compatibility, the Sample.drl generated import errors. Note that all projects using Drools5 wouldn't have such a kmodule.xml, and the plugin used to be able to just pick up those classes from the project classpath.
> 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
12 years, 10 months
[JBoss JIRA] (WFLY-1721) Access log support
by Yoshimasa Tanabe (JIRA)
[ https://issues.jboss.org/browse/WFLY-1721?page=com.atlassian.jira.plugin.... ]
Yoshimasa Tanabe edited comment on WFLY-1721 at 8/29/13 10:39 AM:
------------------------------------------------------------------
{quote}
even if you request some page, does access log file gets created then?
{quote}
No.
{code}
$ wget localhost:8080
$ ls $WILDFLY_HOME/standalone/log/
server.log server.log.2013-08-28
{code}
I build WildFly at d7ecdd6.
was (Author: emag):
{quote}
even if you request some page, does access log file gets created then?
{quote}
Yes.
{code}
$ wget localhost:8080
$ ls $WILDFLY_HOME/standalone/log/
server.log server.log.2013-08-28
{code}
I build WildFly at d7ecdd6.
> Access log support
> ------------------
>
> Key: WFLY-1721
> URL: https://issues.jboss.org/browse/WFLY-1721
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Alpha3
> Reporter: Tomaz Cerar
> Assignee: Tomaz Cerar
> Fix For: 8.0.0.Beta1
>
>
> We need to expose access log configuration trough management.
--
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
12 years, 10 months
[JBoss JIRA] (WFLY-1969) PicketLink: java.lang.LinkageError during loading javax.xml.crypto.dsig.XMLSignContext
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/WFLY-1969?page=com.atlassian.jira.plugin.... ]
Alessio Soldano commented on WFLY-1969:
---------------------------------------
I've successfully verified the above proposed solution using the JBossWS-CXF testsuite.
> PicketLink: java.lang.LinkageError during loading javax.xml.crypto.dsig.XMLSignContext
> --------------------------------------------------------------------------------------
>
> Key: WFLY-1969
> URL: https://issues.jboss.org/browse/WFLY-1969
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 8.0.0.Alpha4
> Reporter: Alessio Soldano
> Assignee: Derek Horton
> Fix For: 8.0.0.Beta1
>
>
> A linkage error javax.xml.crypto.dsig.XMLSignContext is thrown when a XMLSignatureFactory is first resolved by PicketLink (instead of the WS subsystem) on WFLY.
> This should be fixed by tuning the module dependencies in org.picketlink module, either by modifying the relative order of org.apache.santuario.xmlsec and javax.api modules, or -better by setting an exclude block as follows:
> {noformat}
> ...
> <module name="org.apache.santuario.xmlsec">
> <imports>
> <exclude path="javax/*"/>
> </imports>
> </module>
> ...
> {noformat}
--
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
12 years, 10 months
[JBoss JIRA] (WFLY-1969) PicketLink: java.lang.LinkageError during loading javax.xml.crypto.dsig.XMLSignContext
by Alessio Soldano (JIRA)
Alessio Soldano created WFLY-1969:
-------------------------------------
Summary: PicketLink: java.lang.LinkageError during loading javax.xml.crypto.dsig.XMLSignContext
Key: WFLY-1969
URL: https://issues.jboss.org/browse/WFLY-1969
Project: WildFly
Issue Type: Bug
Components: Web Services
Affects Versions: 8.0.0.Alpha4
Reporter: Alessio Soldano
Assignee: Derek Horton
Fix For: 8.0.0.Beta1
A linkage error javax.xml.crypto.dsig.XMLSignContext is thrown when a XMLSignatureFactory is first resolved by PicketLink (instead of the WS subsystem) on WFLY.
This should be fixed by tuning the module dependencies in org.picketlink module, either by modifying the relative order of org.apache.santuario.xmlsec and javax.api modules, or -better by setting an exclude block as follows:
{noformat}
...
<module name="org.apache.santuario.xmlsec">
<imports>
<exclude path="javax/*"/>
</imports>
</module>
...
{noformat}
--
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
12 years, 10 months
[JBoss JIRA] (WFLY-1721) Access log support
by Yoshimasa Tanabe (JIRA)
[ https://issues.jboss.org/browse/WFLY-1721?page=com.atlassian.jira.plugin.... ]
Yoshimasa Tanabe edited comment on WFLY-1721 at 8/29/13 10:34 AM:
------------------------------------------------------------------
{quote}
even if you request some page, does access log file gets created then?
{quote}
Yes.
{code}
$ wget localhost:8080
$ ls $WILDFLY_HOME/standalone/log/
server.log server.log.2013-08-28
{code}
I build WildFly at d7ecdd6
was (Author: emag):
> even if you request some page, does access log file gets created then?
Yes.
{code}
$ wget localhost:8080
$ ls $WILDFLY_HOME/standalone/log/
server.log server.log.2013-08-28
{code}
> Access log support
> ------------------
>
> Key: WFLY-1721
> URL: https://issues.jboss.org/browse/WFLY-1721
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Alpha3
> Reporter: Tomaz Cerar
> Assignee: Tomaz Cerar
> Fix For: 8.0.0.Beta1
>
>
> We need to expose access log configuration trough management.
--
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
12 years, 10 months
[JBoss JIRA] (WFLY-1721) Access log support
by Yoshimasa Tanabe (JIRA)
[ https://issues.jboss.org/browse/WFLY-1721?page=com.atlassian.jira.plugin.... ]
Yoshimasa Tanabe edited comment on WFLY-1721 at 8/29/13 10:34 AM:
------------------------------------------------------------------
{quote}
even if you request some page, does access log file gets created then?
{quote}
Yes.
{code}
$ wget localhost:8080
$ ls $WILDFLY_HOME/standalone/log/
server.log server.log.2013-08-28
{code}
I build WildFly at d7ecdd6.
was (Author: emag):
{quote}
even if you request some page, does access log file gets created then?
{quote}
Yes.
{code}
$ wget localhost:8080
$ ls $WILDFLY_HOME/standalone/log/
server.log server.log.2013-08-28
{code}
I build WildFly at d7ecdd6
> Access log support
> ------------------
>
> Key: WFLY-1721
> URL: https://issues.jboss.org/browse/WFLY-1721
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Alpha3
> Reporter: Tomaz Cerar
> Assignee: Tomaz Cerar
> Fix For: 8.0.0.Beta1
>
>
> We need to expose access log configuration trough management.
--
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
12 years, 10 months
[JBoss JIRA] (HIBERNATE-141) JBAS011910 Cannot resolve requirements: [XPackageRequirement[atts={osgi.wiring.package=org.hibernate.criterion}
by Steve Ebersole (JIRA)
[ https://issues.jboss.org/browse/HIBERNATE-141?page=com.atlassian.jira.plu... ]
Steve Ebersole updated HIBERNATE-141:
-------------------------------------
Assignee: (was: Steve Ebersole)
> JBAS011910 Cannot resolve requirements: [XPackageRequirement[atts={osgi.wiring.package=org.hibernate.criterion}
> ---------------------------------------------------------------------------------------------------------------
>
> Key: HIBERNATE-141
> URL: https://issues.jboss.org/browse/HIBERNATE-141
> Project: Hibernate Integration
> Issue Type: Enhancement
> Reporter: Darryl Miles
>
> EAP 6.1 with upgraded org.hibernate:main jars to 4.2.0.Final (to fix classloading issue HHH-8015 which I did observe).
> JPA has META-INF/jboss-deployment-structure.xml which has entry (amongst other things):
> <module name="org.hibernate" />
> <module name="org.hibernate.validator" />
> JPA has OSGi meta-data including OSGi-JPA:
> Meta-Persistence: META-INF/persistence.xml
> 23:00:16,860 INFO [org.jboss.osgi.framework] (MSC service thread 1-15) JBOSGI011005: Bundle uninstalled: com.domain.jpa:0.0.1.SNAPSHOT
> 23:00:16,862 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment com.domain.jpa-0.0.1-SNAPSHOT.jar (runtime-name: com.domain.jpa-0.0.1-SNAPSHOT.jar) in 4ms
> 23:00:16,863 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "com.domain.jpa-0.0.1-SNAPSHOT.jar" (runtime-name: "com.domain.jpa-0.0.1-SNAPSHOT.jar")
> 23:00:16,876 INFO [org.jboss.as.jpa] (MSC service thread 1-15) JBAS011401: Read persistence.xml for com.domain.jpa
> 23:00:16,880 INFO [org.jboss.osgi.framework] (MSC service thread 1-9) JBOSGI011001: Bundle installed: com.domain.jpa:0.0.1.SNAPSHOT
> 23:00:16,884 WARN [org.jboss.as.osgi] (MSC service thread 1-14) JBAS011910: Cannot resolve requirements: [XPackageRequirement[atts={osgi.wiring.package=org.hibernate.criterion},[com.domain.jpa:0.0.1.SNAPSHOT]]]
> 23:00:16,884 INFO [org.jboss.as.server.deployment] (MSC service thread 1-14) JBAS015970: Defer FIRST_MODULE_USE for com.domain.jpa-0.0.1-SNAPSHOT.jar making it NEVER
> 23:00:16,908 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018565: Replaced deployment "com.domain.jpa-0.0.1-SNAPSHOT.jar" with deployment "com.domain.jpa-0.0.1-SNAPSHOT.jar"
> I would expect the OSGi subsystem to have been able to find the import package org.hibernate.criterion
--
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
12 years, 10 months
[JBoss JIRA] (HIBERNATE-141) JBAS011910 Cannot resolve requirements: [XPackageRequirement[atts={osgi.wiring.package=org.hibernate.criterion}
by Steve Ebersole (JIRA)
[ https://issues.jboss.org/browse/HIBERNATE-141?page=com.atlassian.jira.plu... ]
Steve Ebersole commented on HIBERNATE-141:
------------------------------------------
Darryl, I am going to move this over to the OSGi project since the problem really seems to be there, not in the Hibernate/WildFly integration (which is what this HIBERNATE Jira project is for).
> JBAS011910 Cannot resolve requirements: [XPackageRequirement[atts={osgi.wiring.package=org.hibernate.criterion}
> ---------------------------------------------------------------------------------------------------------------
>
> Key: HIBERNATE-141
> URL: https://issues.jboss.org/browse/HIBERNATE-141
> Project: Hibernate Integration
> Issue Type: Enhancement
> Reporter: Darryl Miles
>
> EAP 6.1 with upgraded org.hibernate:main jars to 4.2.0.Final (to fix classloading issue HHH-8015 which I did observe).
> JPA has META-INF/jboss-deployment-structure.xml which has entry (amongst other things):
> <module name="org.hibernate" />
> <module name="org.hibernate.validator" />
> JPA has OSGi meta-data including OSGi-JPA:
> Meta-Persistence: META-INF/persistence.xml
> 23:00:16,860 INFO [org.jboss.osgi.framework] (MSC service thread 1-15) JBOSGI011005: Bundle uninstalled: com.domain.jpa:0.0.1.SNAPSHOT
> 23:00:16,862 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment com.domain.jpa-0.0.1-SNAPSHOT.jar (runtime-name: com.domain.jpa-0.0.1-SNAPSHOT.jar) in 4ms
> 23:00:16,863 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "com.domain.jpa-0.0.1-SNAPSHOT.jar" (runtime-name: "com.domain.jpa-0.0.1-SNAPSHOT.jar")
> 23:00:16,876 INFO [org.jboss.as.jpa] (MSC service thread 1-15) JBAS011401: Read persistence.xml for com.domain.jpa
> 23:00:16,880 INFO [org.jboss.osgi.framework] (MSC service thread 1-9) JBOSGI011001: Bundle installed: com.domain.jpa:0.0.1.SNAPSHOT
> 23:00:16,884 WARN [org.jboss.as.osgi] (MSC service thread 1-14) JBAS011910: Cannot resolve requirements: [XPackageRequirement[atts={osgi.wiring.package=org.hibernate.criterion},[com.domain.jpa:0.0.1.SNAPSHOT]]]
> 23:00:16,884 INFO [org.jboss.as.server.deployment] (MSC service thread 1-14) JBAS015970: Defer FIRST_MODULE_USE for com.domain.jpa-0.0.1-SNAPSHOT.jar making it NEVER
> 23:00:16,908 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018565: Replaced deployment "com.domain.jpa-0.0.1-SNAPSHOT.jar" with deployment "com.domain.jpa-0.0.1-SNAPSHOT.jar"
> I would expect the OSGi subsystem to have been able to find the import package org.hibernate.criterion
--
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
12 years, 10 months