[JBoss JIRA] (AS7-3043) RESTEasy: Setting cfg. param resteasy.scan.resources=false causes that servlet-name javax.ws.rs.core.Application is not defined
by Pavel Janousek (JIRA)
[ https://issues.jboss.org/browse/AS7-3043?page=com.atlassian.jira.plugin.s... ]
Pavel Janousek commented on AS7-3043:
-------------------------------------
PR-1830 can demonstrate this issue.
Also as you might see - resteasy.scan.resources=blah produces the same problem (-> behavior is the same as resteasy.scan.resources=false) although I'd like to see exception due to invalid deployment descriptor)...
> RESTEasy: Setting cfg. param resteasy.scan.resources=false causes that servlet-name javax.ws.rs.core.Application is not defined
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-3043
> URL: https://issues.jboss.org/browse/AS7-3043
> Project: Application Server 7
> Issue Type: Bug
> Components: REST
> Affects Versions: 7.1.0.Beta1b, 7.1.1.Final, 7.1.2.Final
> Reporter: Pavel Janousek
> Assignee: Weinan Li
> Priority: Blocker
>
> When I set {code:xml}
> <context-param>
> <param-name>resteasy.scan.resources</param-name>
> <param-value>false</param-value>
> </context-param>
> {code} in web.xml, I can't use{code:xml}
> <servlet-mapping>
> <servlet-name>javax.ws.rs.core.Application</servlet-name>
> <url-pattern>/myjaxrs/*</url-pattern>
> </servlet-mapping>
> {code} because _javax.ws.rs.core.Application_ is not defined yet.
> I got exception like this:{code}java.lang.IllegalArgumentException: Servlet mapping specifies an unknown servlet name javax.ws.rs.core.Application{code}
> I'm not sure, but I think that declaration of servlet-name _javax.ws.rs.core.Application_ should be independent to setting this parameter to *any* value. It should only impact scanning user-defined (= included in WAR) resources.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] (AS7-3043) RESTEasy: Setting cfg. param resteasy.scan.resources=false causes that servlet-name javax.ws.rs.core.Application is not defined
by Pavel Janousek (JIRA)
[ https://issues.jboss.org/browse/AS7-3043?page=com.atlassian.jira.plugin.s... ]
Pavel Janousek updated AS7-3043:
--------------------------------
Fix Version/s: (was: 7.1.0.CR1)
Affects Version/s: 7.1.1.Final
7.1.2.Final
Description:
When I set {code:xml}
<context-param>
<param-name>resteasy.scan.resources</param-name>
<param-value>false</param-value>
</context-param>
{code} in web.xml, I can't use{code:xml}
<servlet-mapping>
<servlet-name>javax.ws.rs.core.Application</servlet-name>
<url-pattern>/myjaxrs/*</url-pattern>
</servlet-mapping>
{code} because _javax.ws.rs.core.Application_ is not defined yet.
I got exception like this:{code}java.lang.IllegalArgumentException: Servlet mapping specifies an unknown servlet name javax.ws.rs.core.Application{code}
I'm not sure, but I think that declaration of servlet-name _javax.ws.rs.core.Application_ should be independent to setting this parameter to *any* value. It should only impact scanning user-defined (= included in WAR) resources.
was:
When I set {code:xml}
<context-param>
<param-name>resteasy.scan.resources</param-name>
<param-value>false</param-value>
</context-param>
{code} in web.xml, I can't use{code:xml}
<servlet-mapping>
<servlet-name>javax.ws.rs.core.Application</servlet-name>
<url-pattern>/myjaxrs/*</url-pattern>
</servlet-mapping>
{code} because _javax.ws.rs.core.Application_ is not defined yet.
I got exception like this:{code}ava.lang.IllegalArgumentException: Servlet mapping specifies an unknown servlet name javax.ws.rs.core.Application{code}
I'm not sure, but I think that declaration of servlet-name _javax.ws.rs.core.Application_ should be independent to setting this parameter to *any* value. It should only impact scanning user-defined (= included in WAR) resources.
> RESTEasy: Setting cfg. param resteasy.scan.resources=false causes that servlet-name javax.ws.rs.core.Application is not defined
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-3043
> URL: https://issues.jboss.org/browse/AS7-3043
> Project: Application Server 7
> Issue Type: Bug
> Components: REST
> Affects Versions: 7.1.0.Beta1b, 7.1.1.Final, 7.1.2.Final
> Reporter: Pavel Janousek
> Assignee: Weinan Li
> Priority: Blocker
>
> When I set {code:xml}
> <context-param>
> <param-name>resteasy.scan.resources</param-name>
> <param-value>false</param-value>
> </context-param>
> {code} in web.xml, I can't use{code:xml}
> <servlet-mapping>
> <servlet-name>javax.ws.rs.core.Application</servlet-name>
> <url-pattern>/myjaxrs/*</url-pattern>
> </servlet-mapping>
> {code} because _javax.ws.rs.core.Application_ is not defined yet.
> I got exception like this:{code}java.lang.IllegalArgumentException: Servlet mapping specifies an unknown servlet name javax.ws.rs.core.Application{code}
> I'm not sure, but I think that declaration of servlet-name _javax.ws.rs.core.Application_ should be independent to setting this parameter to *any* value. It should only impact scanning user-defined (= included in WAR) resources.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] (AS7-3043) RESTEasy: Setting cfg. param resteasy.scan.resources=false causes that servlet-name javax.ws.rs.core.Application is not defined
by Pavel Janousek (JIRA)
[ https://issues.jboss.org/browse/AS7-3043?page=com.atlassian.jira.plugin.s... ]
Pavel Janousek edited comment on AS7-3043 at 3/16/12 3:26 PM:
--------------------------------------------------------------
I've just verified this JIRA and unfortunately it isn't resolved yet. The issue still remains.
The problem is still the same - when I set resteasy.scan.resource to false, servlet with name javax.ws.ts.core.Application isn't defined - exception is the same as in description due to mapping specified.
I think it is also against JAX-RS specs section 2.3.2. item one (when no subclass of Application is present....) because in my case I don't use my own Application subclass at all.
was (Author: pjanouse):
I've just verified this JIRA and unfortunately it isn't resolved yet. The issue still remains.
The problem is still the same - when I set resteasy.scan.resource to false, servlet with name javax.ws.ts.core.Application isn't defined - exception is the same as in description due to mapping specification.
I think it is also against JAX-RS specs section 2.3.2. item one (when no subclass of Application is present....) because in my case I don't use my own Application subclass at all.
> RESTEasy: Setting cfg. param resteasy.scan.resources=false causes that servlet-name javax.ws.rs.core.Application is not defined
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-3043
> URL: https://issues.jboss.org/browse/AS7-3043
> Project: Application Server 7
> Issue Type: Bug
> Components: REST
> Affects Versions: 7.1.0.Beta1b
> Reporter: Pavel Janousek
> Assignee: Weinan Li
> Priority: Blocker
> Fix For: 7.1.0.CR1
>
>
> When I set {code:xml}
> <context-param>
> <param-name>resteasy.scan.resources</param-name>
> <param-value>false</param-value>
> </context-param>
> {code} in web.xml, I can't use{code:xml}
> <servlet-mapping>
> <servlet-name>javax.ws.rs.core.Application</servlet-name>
> <url-pattern>/myjaxrs/*</url-pattern>
> </servlet-mapping>
> {code} because _javax.ws.rs.core.Application_ is not defined yet.
> I got exception like this:{code}ava.lang.IllegalArgumentException: Servlet mapping specifies an unknown servlet name javax.ws.rs.core.Application{code}
> I'm not sure, but I think that declaration of servlet-name _javax.ws.rs.core.Application_ should be independent to setting this parameter to *any* value. It should only impact scanning user-defined (= included in WAR) resources.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] (AS7-3043) RESTEasy: Setting cfg. param resteasy.scan.resources=false causes that servlet-name javax.ws.rs.core.Application is not defined
by Pavel Janousek (JIRA)
[ https://issues.jboss.org/browse/AS7-3043?page=com.atlassian.jira.plugin.s... ]
Pavel Janousek reopened AS7-3043:
---------------------------------
Assignee: Weinan Li (was: Pavel Janousek)
I've just verified this JIRA and unfortunately it isn't resolved yet. The issue still remains.
The problem is still the same - when I set resteasy.scan.resource to false, servlet with name javax.ws.ts.core.Application isn't defined - exception is the same as in description due to mapping specification.
I think it is also against JAX-RS specs section 2.3.2. item one (when no subclass of Application is present....) because in my case I don't use my own Application subclass at all.
> RESTEasy: Setting cfg. param resteasy.scan.resources=false causes that servlet-name javax.ws.rs.core.Application is not defined
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-3043
> URL: https://issues.jboss.org/browse/AS7-3043
> Project: Application Server 7
> Issue Type: Bug
> Components: REST
> Affects Versions: 7.1.0.Beta1b
> Reporter: Pavel Janousek
> Assignee: Weinan Li
> Priority: Blocker
> Fix For: 7.1.0.CR1
>
>
> When I set {code:xml}
> <context-param>
> <param-name>resteasy.scan.resources</param-name>
> <param-value>false</param-value>
> </context-param>
> {code} in web.xml, I can't use{code:xml}
> <servlet-mapping>
> <servlet-name>javax.ws.rs.core.Application</servlet-name>
> <url-pattern>/myjaxrs/*</url-pattern>
> </servlet-mapping>
> {code} because _javax.ws.rs.core.Application_ is not defined yet.
> I got exception like this:{code}ava.lang.IllegalArgumentException: Servlet mapping specifies an unknown servlet name javax.ws.rs.core.Application{code}
> I'm not sure, but I think that declaration of servlet-name _javax.ws.rs.core.Application_ should be independent to setting this parameter to *any* value. It should only impact scanning user-defined (= included in WAR) resources.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] (JBRULES-3428) accumulate/collect CEs should trigger against largest fact set possible
by Adar Dembo (JIRA)
Adar Dembo created JBRULES-3428:
-----------------------------------
Summary: accumulate/collect CEs should trigger against largest fact set possible
Key: JBRULES-3428
URL: https://issues.jboss.org/browse/JBRULES-3428
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: drools-compiler
Affects Versions: 5.4.0.Beta2
Reporter: Adar Dembo
Assignee: Mark Proctor
I'm interested in a way to ensure that a rule containing a collect or accumulate CE doesn't fire until no other rule inserting an accumulated/collected fact can fire. I've had a few conversations on IRC about this, where I was told that the only ways to accomplish this were through explicit ordering (i.e. salience, agenda groups, or ruleflow-groups), or through meta-objects. Obviously explicit ordering works, but it makes ongoing rule maintenance and reasoning more difficult. And meta-objects don't always work: you don't always know ahead of time how many of these accumulated/collected facts to expect, and you can't always use retraction + not exists() as a condition (suppose the retracted facts need to be used by multiple rules).
My rules makes extensive use of collect and accumulate to aggregate sets of facts, and to work around this I've partitioned my rules into agenda-groups, and, within a rule file, used salience to guarantee ordering. Frankly, this explicit ordering is pretty tiresome.
Here's a concrete example:
{noformat}
rule "insert accumulated fact"
when
Foo()
then
insert(new Bar())
end
rule "do the accumulation"
when
accumulate(Bar(), $count : count())
then
insert(new Cow($count));
end
{noformat}
I shouldn't have to insert "salience -1" into the second rule to guarantee that I get a Cow() with the largest count possible. Now, you might say "well, retract the Foo() when you insert the Bar(), and then add not exists(Bar()) to the second rule". Suppose there's a third rule that also depends on Foo(); retracting Foo() would mean the second rule doesn't get to use it. Or you might say "if you insert all your Foo() objects a priori, insert a FooCount() along with them that the second rule can use to know how many Bar() objects should exist before firing". That does work when Foo() is inserted a priori, but it gets messy if it's inserted by another rule; how do you know how many to expect then?
Ideally the second rule would know that it depends on facts from the first rule, and wouldn't fire until the first rule (and other rules that may trigger the first rule) can no longer fire. Less ideal would be an explicit dependency mechanism that I can insert into the second rule to control this myself.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] (AS7-4112) xsd validation errors
by Juergen Hoffmann (JIRA)
Juergen Hoffmann created AS7-4112:
-------------------------------------
Summary: xsd validation errors
Key: AS7-4112
URL: https://issues.jboss.org/browse/AS7-4112
Project: Application Server 7
Issue Type: Bug
Reporter: Juergen Hoffmann
elements added at runtime cannot be correctly validated with the current xsd schemas.
<server-group name="server-group" profile="default">
<jvm name="default">
<heap size="1g" max-size="1g"/>
<jvm-options>
<option value="-Dgrails.env=qual"/>
</jvm-options>
</jvm>
<socket-binding-group ref="standard-sockets"/>
<deployments>
<deployment name="my.war" runtime-name="my.war"/>
</deployments>
</server-group>
produces
cvc-complex-type.2.4.b: The content of element 'deployment' is not complete. One of '{"urn:jboss:domain:1.1":content, "urn:jboss:domain:1.1":fs-archive, "urn:jboss:domain:1.1":fs-exploded}' is expected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month