[JBoss JIRA] Created: (JBBUILD-426) maven-jboss-deploy-plugin leaves version number in artifacts
by Carlo de Wolf (JIRA)
maven-jboss-deploy-plugin leaves version number in artifacts
------------------------------------------------------------
Key: JBBUILD-426
URL: http://jira.jboss.com/jira/browse/JBBUILD-426
Project: JBoss Build System
Issue Type: Bug
Components: maven-jboss-deploy-plugin
Affects Versions: maven-jboss-deploy-plugin-1.4
Reporter: Carlo de Wolf
Priority: Critical
The deploy creates files with version numbers for the ant build repository. The files should not contain any version reference.
carlo@alien:~/work/repository.jboss.org/jboss$ ls jboss-metadata/1.0.0-SNAPSHOT/lib/
jboss-metadata-1.0.0-SNAPSHOT-sources.jar
jboss-metadata-1.0.0-SNAPSHOT.jar
Should have been:
carlo@alien:~/work/repository.jboss.org/jboss$ ls jboss-metadata/1.0.0-SNAPSHOT/lib/
jboss-metadata-sources.jar
jboss-metadata.jar
--
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
17 years
[JBoss JIRA] Created: (JBAS-5034) LoginContext exception crashes application
by Christos Nicolaou (JIRA)
LoginContext exception crashes application
------------------------------------------
Key: JBAS-5034
URL: http://jira.jboss.com/jira/browse/JBAS-5034
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Security
Affects Versions: JBossAS-4.0.4.GA
Environment: Linux. I have two linux servers with JBoss installed running in clustered mode and two servers with Tomcat 5.23 running in load-balancing mode(not clustered).
I have replicated the problem on windows with a jboss and tomcat running independently.
Reporter: Christos Nicolaou
Assigned To: Scott M Stark
The problem occurs when I the LoginContext is initialized and logged in, and I try to call the server. At this point the call fails(wrong credentials) and I do not logout the context. After this any call coming to the tomcat server from any browser running on other machines gives a security exception in JBoss. In the JBoss log it I can see the JBoss ServerLoginModule saying "Bad Password given for username=a" where 'a' is the user with the invalid credentials from the previous call.
In case the LoginContext is logged out in case of an exception everything works out fine. However, since what I described above means that the web-server picks up a LoginContext belonging to a different session this worries me a lot.
--
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
17 years
[JBoss JIRA] Created: (JBAS-3509) org.jboss.test.cache.bean.MBeanUnitTestCase because "ejb" is not bound
by Jaroslaw Kijanowski (JIRA)
org.jboss.test.cache.bean.MBeanUnitTestCase because "ejb" is not bound
----------------------------------------------------------------------
Key: JBAS-3509
URL: http://jira.jboss.com/jira/browse/JBAS-3509
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Test Suite
Affects Versions: JBossAS-5.0.0.Beta
Environment: win xp
Reporter: Jaroslaw Kijanowski
org.jboss.test.cache.bean.MBeanUnitTestCase because "ejb" is not bound because of missing xml files.
Resolve:
Copy following xml files to testsuite\src\resources\cache\META-INF
************
ejb-jar.xml:
************
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar >
<description><![CDATA[No Description.]]></description>
<display-name>Generated by XDoclet</display-name>
<enterprise-beans>
<!-- Session Beans -->
<session >
<description><![CDATA[]]></description>
<ejb-name>CacheObjectMeanTester</ejb-name>
<home>org.jboss.test.cache.bean.CacheObjectMeanTesterHome</home>
<remote>org.jboss.test.cache.bean.CacheObjectMeanTester</remote>
<ejb-class>org.jboss.test.cache.bean.CacheObjectMeanTesterBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
<session >
<description><![CDATA[Proxy to the TreeCache MBean.]]></description>
<ejb-name>test/TreeCacheTester</ejb-name>
<home>org.jboss.test.cache.bean.TreeCacheTesterHome</home>
<remote>org.jboss.test.cache.bean.TreeCacheTester</remote>
<ejb-class>org.jboss.test.cache.bean.TreeCacheTesterBean</ejb-class>
<session-type>Stateful</session-type>
<transaction-type>Container</transaction-type>
</session>
<session >
<description><![CDATA[Proxy to the TreeCacheAop MBean.]]></description>
<ejb-name>test/TreeCacheAopTester</ejb-name>
<home>org.jboss.test.cache.bean.TreeCacheAopTesterHome</home>
<remote>org.jboss.test.cache.bean.TreeCacheAopTester</remote>
<ejb-class>org.jboss.test.cache.bean.TreeCacheAopTesterBean</ejb-class>
<session-type>Stateful</session-type>
<transaction-type>Container</transaction-type>
</session>
<session >
<description><![CDATA[EJB proxy to the TreeCache MBean service.]]></description>
<ejb-name>test/TreeCacheMBeanTester</ejb-name>
<home>org.jboss.test.cache.bean.TreeCacheMBeanTesterHome</home>
<remote>org.jboss.test.cache.bean.TreeCacheMBeanTester</remote>
<ejb-class>org.jboss.test.cache.bean.TreeCacheMBeanTesterBean</ejb-class>
<session-type>Stateful</session-type>
<transaction-type>Container</transaction-type>
</session>
<session >
<description><![CDATA[Proxy to the TreeCacheAop MBean.]]></description>
<ejb-name>test/TreeCacheAopMBeanTester</ejb-name>
<home>org.jboss.test.cache.bean.TreeCacheAopMBeanTesterHome</home>
<remote>org.jboss.test.cache.bean.TreeCacheAopMBeanTester</remote>
<ejb-class>org.jboss.test.cache.bean.TreeCacheAopMBeanTesterBean</ejb-class>
<session-type>Stateful</session-type>
<transaction-type>Container</transaction-type>
</session>
<!--
To add session beans that you have deployment descriptor info for, add
a file to your XDoclet merge directory called session-beans.xml that contains
the <session></session> markup for those beans.
-->
<!-- Entity Beans -->
<!--
To add entity beans that you have deployment descriptor info for, add
a file to your XDoclet merge directory called entity-beans.xml that contains
the <entity></entity> markup for those beans.
-->
<!-- Message Driven Beans -->
<!--
To add message driven beans that you have deployment descriptor info for, add
a file to your XDoclet merge directory called message-driven-beans.xml that contains
the <message-driven></message-driven> markup for those beans.
-->
</enterprise-beans>
<!-- Relationships -->
<!-- Assembly Descriptor -->
<assembly-descriptor >
<!--
To add additional assembly descriptor info here, add a file to your
XDoclet merge directory called assembly-descriptor.xml that contains
the <assembly-descriptor></assembly-descriptor> markup.
-->
<!-- finder permissions -->
<!-- finder permissions -->
<!-- finder permissions -->
<!-- finder permissions -->
<!-- finder permissions -->
<!-- transactions -->
<container-transaction >
<method >
<ejb-name>test/TreeCacheTester</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Supports</trans-attribute>
</container-transaction>
<container-transaction >
<method >
<ejb-name>test/TreeCacheAopTester</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Supports</trans-attribute>
</container-transaction>
<container-transaction >
<method >
<ejb-name>test/TreeCacheMBeanTester</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Supports</trans-attribute>
</container-transaction>
<container-transaction >
<method >
<ejb-name>test/TreeCacheAopMBeanTester</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Supports</trans-attribute>
</container-transaction>
<!-- finder transactions -->
</assembly-descriptor>
</ejb-jar>
************
************
jboss.xml
************
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 3.0//EN" "http://www.jboss.org/j2ee/dtd/jboss_3_0.dtd">
<jboss>
<enterprise-beans>
<!--
To add beans that you have deployment descriptor info for, add
a file to your XDoclet merge directory called jboss-beans.xml that contains
the <session></session>, <entity></entity> and <message-driven></message-driven>
markup for those beans.
-->
<session>
<ejb-name>CacheObjectMeanTester</ejb-name>
<jndi-name>test/CacheObjectMeanTester</jndi-name>
</session>
<session>
<ejb-name>test/TreeCacheTester</ejb-name>
<jndi-name>ejb/test/TreeCacheTester</jndi-name>
</session>
<session>
<ejb-name>test/TreeCacheAopTester</ejb-name>
<jndi-name>test/TreeCacheAopTester</jndi-name>
</session>
<session>
<ejb-name>test/TreeCacheMBeanTester</ejb-name>
<jndi-name>ejb/test/TreeCacheMBeanTester</jndi-name>
</session>
<session>
<ejb-name>test/TreeCacheAopMBeanTester</ejb-name>
<jndi-name>ejb/test/TreeCacheAopMBeanTester</jndi-name>
</session>
</enterprise-beans>
<resource-managers>
</resource-managers>
</jboss>
***************
--
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
17 years