[JBoss JIRA] (JBAS-9574) Spring + Maven + Apache CXF + Jboss 6 Soap Service error
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/JBAS-9574?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated JBAS-9574:
------------------------------
Priority: Optional (was: Blocker)
> Spring + Maven + Apache CXF + Jboss 6 Soap Service error
> --------------------------------------------------------
>
> Key: JBAS-9574
> URL: https://issues.jboss.org/browse/JBAS-9574
> Project: Application Server 3 4 5 and 6
> Issue Type: Feature Request
> Reporter: Shailesh Karwa
> Priority: Optional
> Fix For: Open To Community
>
>
> DEPLOYMENTS IN ERROR: Deployment "vfs:///D:/jboss-6.0.0.Final/server/default/deploy/SpringWebServiceTest.war" is in error due to the following reason(s): java.lang.RuntimeException: Neither any mapped-name/lookup/jndi-name specified nor any ResourceProvider could process resource-env-ref named env/org.apache.cxf.ws.policy.AssertionBuilderRegistryImpl/bus of type org.apache.cxf.Bus
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (JBAS-9574) Spring + Maven + Apache CXF + Jboss 6 Soap Service error
by Shailesh Karwa (JIRA)
Shailesh Karwa created JBAS-9574:
------------------------------------
Summary: Spring + Maven + Apache CXF + Jboss 6 Soap Service error
Key: JBAS-9574
URL: https://issues.jboss.org/browse/JBAS-9574
Project: Application Server 3 4 5 and 6
Issue Type: Feature Request
Reporter: Shailesh Karwa
Priority: Blocker
DEPLOYMENTS IN ERROR: Deployment "vfs:///D:/jboss-6.0.0.Final/server/default/deploy/SpringWebServiceTest.war" is in error due to the following reason(s): java.lang.RuntimeException: Neither any mapped-name/lookup/jndi-name specified nor any ResourceProvider could process resource-env-ref named env/org.apache.cxf.ws.policy.AssertionBuilderRegistryImpl/bus of type org.apache.cxf.Bus
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (WFCORE-1120) Launcher sets "-Djava.net.preferIPv4Stack=true" also with IPv6 profile
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1120?page=com.atlassian.jira.plugi... ]
Tomaz Cerar commented on WFCORE-1120:
-------------------------------------
Yes, James'es patch addresses also that.
That is its main improvement over my original patch.
> Launcher sets "-Djava.net.preferIPv4Stack=true" also with IPv6 profile
> ----------------------------------------------------------------------
>
> Key: WFCORE-1120
> URL: https://issues.jboss.org/browse/WFCORE-1120
> Project: WildFly Core
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 2.0.1.Final
> Reporter: Marek Kopecký
> Assignee: James Perkins
>
> *Description of problem:*
> Domain tests "-Djava.net.preferIPv4Stack=true" also with IPv6 profile. This property is set in AbstractCommandBuilder of WildFly-Core:
> https://github.com/wildfly/wildfly-core/blob/master/launcher/src/main/jav...
> There should be option for disable of this option in arquillian.xml file. And testsuite should use this option with IPv6 profile.
> *How reproducible:*
> Always
> *Steps to Reproduce:*
> # ./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -Dnode0=$MYTESTIPV6_1 -Dnode1=$MYTESTIPV6_2 -Dipv6 -Dts.manualmode -Dtest=OutboundLdapConnectionTestCase -DtestLogToFile=false -Djboss.dist=$JBOSS_DIST -Dts.noSmoke
> *Actual results:*
> {noformat}
> 07:04:26,054 INFO [org.jboss.as.arquillian.container.managed.ManagedDeployableContainer] (main) Starting container with: [/qa/tools/opt/jdk1.8.0_last/bin/java,
> ...
> -Djava.net.preferIPv4Stack=true, -Djava.net.preferIPv4Stack=false
> ...
> {noformat}
> *Expected results:*
> EAP is not started with "-Djava.net.preferIPv4Stack=true" property with IPv6 profile
> *Additional info:*
> Jenkins reproducer job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP7/view/EAP7-AS-T...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (JBJCA-1304) Subject.doAs should be invoked inside of doPrivileged block
by Ivo Studensky (JIRA)
Ivo Studensky created JBJCA-1304:
------------------------------------
Summary: Subject.doAs should be invoked inside of doPrivileged block
Key: JBJCA-1304
URL: https://issues.jboss.org/browse/JBJCA-1304
Project: IronJacamar
Issue Type: Bug
Components: JDBC
Affects Versions: WildFly/IronJacamar 1.3.1.Final
Reporter: Ivo Studensky
Assignee: Ivo Studensky
If the server is running with Security Manager enabled and a deployment invokes {{getConnection()}} method a DataSource, it fails with the following exception:
{noformat}
&#27;[0m&#27;[33m15:08:52,138 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.PoolBySubject] (pool-2-thread-1) IJ000604: Throwable while attempting to get a new connection: null: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("javax.security.auth.AuthPermission" "doAs")" in code source "(vfs:/content/test.ear/lib/single.jar <no signer certificates>)" of "null")
at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:273)
at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:175)
at javax.security.auth.Subject.doAs(Subject.java:410)
at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:243)
at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.createConnectionEventListener(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:1336)
at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.getConnection(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:501)
at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(AbstractPool.java:633)
at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:605)
at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:603)
at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:430)
at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:761)
at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:138)
at org.jboss.as.connector.subsystems.datasources.WildFlyDataSource.getConnection(WildFlyDataSource.java:66)
at org.jboss.as.test.integration.jca.security.DsWithSecurityDomainTestCase.deploymentTest(DsWithSecurityDomainTestCase.java:101)
{noformat}
{{LocalManagedConnectionFactory#createManagedConnection(Subject, ConnectionRequestInfo)}} invokes {{Subject.doAs()}} without {{doPrivileged}} block. Hence, the deployment needs to have doAs permissions.
{{Subject.doAs}} should be invoked within {{doPrivileged}}.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (ELY-368) Add optional Supplier<Provider[]> to realm implementations
by David Lloyd (JIRA)
David Lloyd created ELY-368:
-------------------------------
Summary: Add optional Supplier<Provider[]> to realm implementations
Key: ELY-368
URL: https://issues.jboss.org/browse/ELY-368
Project: WildFly Elytron
Issue Type: Enhancement
Reporter: David Lloyd
Realms use key factories, certificate factories, password factories, etc. Most of the time they just use the default installed providers. Enhance the realms to accept an optional {{Supplier<Provider[]>}} which will be used to load these kinds of things. The default supplier should be {{Security::getProviders()}}.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (DROOLS-980) KieBase.getFactType should only be used to retrieve declared beans.
by Alejo Jara (JIRA)
[ https://issues.jboss.org/browse/DROOLS-980?page=com.atlassian.jira.plugin... ]
Alejo Jara edited comment on DROOLS-980 at 11/12/15 8:38 AM:
-------------------------------------------------------------
In my first version this is my class definition
ClassDefinition{className='com.example.types.Person', superClass='java.lang.Object', interfaces=[java.io.Serializable], definedClass=class com.example.types.Person, traitable=NONE, abstract=false, fields={name=FieldDefinition{name='name', type='java.lang.String', key=false, inherited=false, index=0, initExpr='null', annotations=null, accessor=[ClassFieldExtractor class=com.example.types.Person field=name]}}, annotations=null}
When kiescanner runs changing a rule to version two the Class Definition is
ClassDefinition{className='com.example.types.Person', superClass='java.lang.Object', interfaces=[java.io.Serializable, org.drools.core.factmodel.GeneratedFact], definedClass=class com.example.types.Person, traitable=null, abstract=false, fields={}, annotations=null}
The field "name" it has disappeared
was (Author: jhara):
In my first version this is my class definition
ClassDefinition{className='com.example.types.Person', superClass='java.lang.Object', interfaces=[java.io.Serializable], definedClass=class com.example.types.Person, traitable=NONE, abstract=false, fields={name=FieldDefinition{name='name', type='java.lang.String', key=false, inherited=false, index=0, initExpr='null', annotations=null, accessor=[ClassFieldExtractor class=com.example.types.Person field=name]}}, annotations=null}
When kiescanner runs without changes into kjar only change to version two the Class Definition is
ClassDefinition{className='com.example.types.Person', superClass='java.lang.Object', interfaces=[java.io.Serializable, org.drools.core.factmodel.GeneratedFact], definedClass=class com.example.types.Person, traitable=null, abstract=false, fields={}, annotations=null}
The field "name" it has disappeared
> KieBase.getFactType should only be used to retrieve declared beans.
> -------------------------------------------------------------------
>
> Key: DROOLS-980
> URL: https://issues.jboss.org/browse/DROOLS-980
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.3.0.Final
> Reporter: Alejo Jara
> Assignee: Mario Fusco
> Attachments: my_rules-1.jar
>
>
> Error inesperado en la ejecucion del artefacto
> java.lang.UnsupportedOperationException: KieBase.getFactType should only be used to retrieve declared beans. Class com.example.types.Person exists outside DRL
> at org.drools.core.definitions.impl.KnowledgePackageImpl.getFactType(KnowledgePackageImpl.java:635)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (DROOLS-980) KieBase.getFactType should only be used to retrieve declared beans.
by Alejo Jara (JIRA)
[ https://issues.jboss.org/browse/DROOLS-980?page=com.atlassian.jira.plugin... ]
Alejo Jara edited comment on DROOLS-980 at 11/12/15 7:09 AM:
-------------------------------------------------------------
In my first version this is my class definition
ClassDefinition{className='com.example.types.Person', superClass='java.lang.Object', interfaces=[java.io.Serializable], definedClass=class com.example.types.Person, traitable=NONE, abstract=false, fields={name=FieldDefinition{name='name', type='java.lang.String', key=false, inherited=false, index=0, initExpr='null', annotations=null, accessor=[ClassFieldExtractor class=com.example.types.Person field=name]}}, annotations=null}
When kiescanner runs without changes into kjar only change to version two the Class Definition is
ClassDefinition{className='com.example.types.Person', superClass='java.lang.Object', interfaces=[java.io.Serializable, org.drools.core.factmodel.GeneratedFact], definedClass=class com.example.types.Person, traitable=null, abstract=false, fields={}, annotations=null}
The field "name" it has disappeared
was (Author: jhara):
In my first version this is my class definition
ClassDefinition{className='com.example.types.Person', superClass='java.lang.Object', interfaces=[java.io.Serializable], definedClass=class com.example.types.Person, traitable=NONE, abstract=false, fields={id_negocio=FieldDefinition{name='name', type='java.lang.String', key=false, inherited=false, index=0, initExpr='null', annotations=null, accessor=[ClassFieldExtractor class=com.example.types.Person field=name]}}, annotations=null}
When kiescanner runs without changes into kjar only change to version two the Class Definition is
ClassDefinition{className='com.example.types.Person', superClass='java.lang.Object', interfaces=[java.io.Serializable, org.drools.core.factmodel.GeneratedFact], definedClass=class com.example.types.Person, traitable=null, abstract=false, fields={}, annotations=null}
The field "name" it has disappeared
> KieBase.getFactType should only be used to retrieve declared beans.
> -------------------------------------------------------------------
>
> Key: DROOLS-980
> URL: https://issues.jboss.org/browse/DROOLS-980
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.3.0.Final
> Reporter: Alejo Jara
> Assignee: Mario Fusco
> Attachments: my_rules-1.jar
>
>
> Error inesperado en la ejecucion del artefacto
> java.lang.UnsupportedOperationException: KieBase.getFactType should only be used to retrieve declared beans. Class com.example.types.Person exists outside DRL
> at org.drools.core.definitions.impl.KnowledgePackageImpl.getFactType(KnowledgePackageImpl.java:635)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (DROOLS-980) KieBase.getFactType should only be used to retrieve declared beans.
by Alejo Jara (JIRA)
[ https://issues.jboss.org/browse/DROOLS-980?page=com.atlassian.jira.plugin... ]
Alejo Jara commented on DROOLS-980:
-----------------------------------
In my first version this is my class definition
ClassDefinition{className='com.example.types.Person', superClass='java.lang.Object', interfaces=[java.io.Serializable], definedClass=class com.example.types.Person, traitable=NONE, abstract=false, fields={id_negocio=FieldDefinition{name='name', type='java.lang.String', key=false, inherited=false, index=0, initExpr='null', annotations=null, accessor=[ClassFieldExtractor class=com.example.types.Person field=name]}}, annotations=null}
When kiescanner runs without changes into kjar only change to version two the Class Definition is
ClassDefinition{className='com.example.types.Person', superClass='java.lang.Object', interfaces=[java.io.Serializable, org.drools.core.factmodel.GeneratedFact], definedClass=class com.example.types.Person, traitable=null, abstract=false, fields={}, annotations=null}
The field "name" it has disappeared
> KieBase.getFactType should only be used to retrieve declared beans.
> -------------------------------------------------------------------
>
> Key: DROOLS-980
> URL: https://issues.jboss.org/browse/DROOLS-980
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.3.0.Final
> Reporter: Alejo Jara
> Assignee: Mario Fusco
> Attachments: my_rules-1.jar
>
>
> Error inesperado en la ejecucion del artefacto
> java.lang.UnsupportedOperationException: KieBase.getFactType should only be used to retrieve declared beans. Class com.example.types.Person exists outside DRL
> at org.drools.core.definitions.impl.KnowledgePackageImpl.getFactType(KnowledgePackageImpl.java:635)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (SECURITY-928) Redundant security-related XML schema files
by Peter Skopek (JIRA)
[ https://issues.jboss.org/browse/SECURITY-928?page=com.atlassian.jira.plug... ]
Peter Skopek resolved SECURITY-928.
-----------------------------------
Resolution: Done
see comment below.
> Redundant security-related XML schema files
> -------------------------------------------
>
> Key: SECURITY-928
> URL: https://issues.jboss.org/browse/SECURITY-928
> Project: PicketBox
> Issue Type: Bug
> Components: JBossSX
> Reporter: Peter Skopek
> Assignee: Peter Skopek
>
> There are several XML schemas in server's docs/schemas that are in my opinion redundant and should be removed:
> picketbox-security-domain-configuration_4_0.xsd - duplicates subsystem configuration in jboss-as-security_1_2.xsd
> security-config_*.xsd - 3 schemas for old deployable security configuration descriptor. These kinds of deployments are afaik not supported in EAP 7.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (SECURITY-928) Redundant security-related XML schema files
by Peter Skopek (JIRA)
[ https://issues.jboss.org/browse/SECURITY-928?page=com.atlassian.jira.plug... ]
Peter Skopek commented on SECURITY-928:
---------------------------------------
Removing just picketbox-security-domain-configuration_4_0.xsd from build.
security-config_*.xsd's should stay in the build as they can be used by others.
If we ship them in EAP7 it doesn't necessary mean we support it.
> Redundant security-related XML schema files
> -------------------------------------------
>
> Key: SECURITY-928
> URL: https://issues.jboss.org/browse/SECURITY-928
> Project: PicketBox
> Issue Type: Bug
> Components: JBossSX
> Reporter: Peter Skopek
> Assignee: Peter Skopek
>
> There are several XML schemas in server's docs/schemas that are in my opinion redundant and should be removed:
> picketbox-security-domain-configuration_4_0.xsd - duplicates subsystem configuration in jboss-as-security_1_2.xsd
> security-config_*.xsd - 3 schemas for old deployable security configuration descriptor. These kinds of deployments are afaik not supported in EAP 7.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months