December 2006 - jboss-user - Jboss List Archives

[Installation, Configuration & Deployment] - Re: Shared classpath within an EAR?

by weston.price＠jboss.com

You really should not use the java module approach. There are other alternatives. EE5 includes mechanism to load thirdparty jars from a centralized location. In J2EE 1.4 you can declare a libs directory, place your 3rd party jars in them and list each one explicitly in the MANIFEST.MF file of your application components anonymous wrote : | EAR | -->lib | -->jar1 | -->jar2 | ejb-module.jar | -->META-INF | -->MANIFEST.MF | (Class-Path: lib/jar1.jar, lib/jar2.jar | | Note, regular scoping rules apply in that if you are using an isolated CL with Java2ParentDelegation turned off, this will force the load from the lib directory. If not, and a class exists in a higher class loader, this one will be chosen. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991791#3991791 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991791

19 years, 4 months

1
0
0 / 0

[Installation, Configuration & Deployment] - Re: Shared classpath within an EAR?

by lightbulb432

Also, while one of the options is to place it directly underneath the EAR and declare it in application.xml as a java module, that could get really messy really quickly if you have many JAR libs... Is there a way to declare a directory containing libs as being visible to the entire EAR's classpath? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991790#3991790 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991790

19 years, 4 months

1
0
0 / 0

[JCA/JBoss] - Re: DB2 XA connection problem - Non XA works

by weston.price＠jboss.com

I was able to get this to run on an AMD64 system with no issues. Note, DB2 seems to want it's libraries first in the LD_LIBRARY_PATH. Also, use of the db2profile script seems to be required. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991788#3991788 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991788

19 years, 4 months

1
0
0 / 0

[JBoss Portal] - Re: Login.jsp

by mmontoni

Thanks guys, I followed a wiki I found for JBoss Portal 2.0 and changed in jboss-portal.sar/portal-server.war/web-inf/web.xml. It worked but did I do it right? I am trying to integrate Acegi on it...I did it on portal-server.war but I can't get the login.jsp to show up anymore....I wonder if I should redo everything under jboss-portal.sar. Thanks! Mariella. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991786#3991786 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991786

19 years, 4 months

1
0
0 / 0

[EJB 3.0] - Embedded EJB3 doesn't work when Transaction Isolation is set

by dangelo1

If you add the following in the datasource configuration of the Embeddable EJB3 TRANSACTION_REPEATABLE_READ of any other transaction isolation level It doesn't work! i.e. in SQL server my database inserts just hangs and doesn't seem to get committed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991785#3991785 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991785

19 years, 4 months

1
0
0 / 0

[JBoss Portal] - UserPortlet

by mmontoni

Hi, I was wondering where the UserPortlet is inside of the JBoss Portal? I am trying to see the code and I just can't find where this portlet is....I thought it was inside of the jboss-portal.sar. Where should I be looking? Thanks! Mariella. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991783#3991783 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991783

19 years, 4 months

1
0
0 / 0

[Installation, Configuration & Deployment] - Re: strange! halt of jboss + DB2(XA)

by weston.price＠jboss.com

I did some tests and the following is going to be required in your *-ds.xml file. <isSameRM-override-value>false</isSameRM-override-value> IBM DB2 XA seems to suffer from the same Oracle issue wherein enlisting two managed connections within the same XA transaction will not work if the underlying resource manager is the same. Add this to your *-ds.xml file(s) and you should be all set. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991781#3991781 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991781

19 years, 4 months

1
0
0 / 0

[News & Announcements] - JBoss Messaging 1.0.1.SP2 Released

by ovidiu.feodorov＠jboss.com

JBoss Messaging 1.0.1.SP2 has been released and it is available for download on jboss.org (http://labs.jboss.com/portal/jbossmessaging/downloads) and sourceforge (http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=15...). The SP2 release fixes a major concurrency bug (http://jira.jboss.com/jira/browse/JBMESSAGING-660 - a race condition that used to occur while closing sessions), a remoting bug (http://jira.jboss.com/jira/browse/JBMESSAGING-644) and also introduced changes in how redeliveries and sending messages to the Dead Letter Queue are handled. WARNING! Due to the fact that the redelivery count per message is now maintained in the database, the database schema has changed, so the database tables need to be dropped and recreated upon restart. The complete list of changes introduced by this release is available at http://jira.jboss.org/jira/secure/ReleaseNote.jspa?version=12311073&style... The JBoss Messaging project roadmap is available here: http://jira.jboss.org/jira/browse/JBMESSAGING?report=com.atlassian.jira.p... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991780#3991780 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991780

19 years, 4 months

1
0
0 / 0

[JBoss Messaging] - JBoss Messaging 1.0.1.SP2 Released

by ovidiu.feodorov＠jboss.com

JBoss Messaging 1.0.1.SP2 has been released and it is available for download on jboss.org (http://labs.jboss.com/portal/jbossmessaging/downloads) and sourceforge (http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=15...). The SP2 release fixes a major concurrency bug (http://jira.jboss.com/jira/browse/JBMESSAGING-660 - a race condition that used to occur while closing sessions), a remoting bug (http://jira.jboss.com/jira/browse/JBMESSAGING-644) and also introduced changes in how redeliveries and sending messages to the Dead Letter Queue are handled. The configuration changes required by this new release are extensively described below. WARNING! Due to the fact that the redelivery count per message is now maintained in the database, the database schema has changed, so the database tables need to be dropped and recreated upon restart. The complete list of changes introduced by this release is available at http://jira.jboss.org/jira/secure/ReleaseNote.jspa?version=12311073&style... The JBoss Messaging project roadmap is available here: http://jira.jboss.org/jira/browse/JBMESSAGING?report=com.atlassian.jira.p... Configuration changes introduced by JBoss Messaging 1.0.1.SP2 1. Configurable DLQ name and maximum delivery attempt count The latest server version allows you to configure an arbitrary DLQ where messages will sent after a number of failed delivery attempts. The queue name can be specified using ServerPeer's DLQName attribute. The number of delivery attempts can be specified using ServerPeer's MaxDeliveryAttempts attribute. Both attributes are part of ServerPeer service configuration, located in messaging-service.xml: <mbean code="org.jboss.jms.server.ServerPeer" | name="jboss.messaging:service=ServerPeer" | xmbean-dd="xmdesc/ServerPeer-xmbean.xml"> | | ... | | <attribute name="MaxDeliveryAttempts">10</attribute> | <attribute name="DLQName">DLQ</attribute> | | </mbean> | The queue to be used as DLQ must be declared in destinations-service.xml, so it will be deployed at boot. 2. Maximum redelivery attempts for EJB3 Message Driven Beans For a JBoss 4.0.5 EJB3 MDB container, the maximum redelivery attempts attribute is set by default to 0, so the messages are sent straight to DLQ (http://jira.jboss.org/jira/browse/JBAS-3917). To work around this, change the maximum delivery attempts counter in your EJB3 MDB configuration: | @MessageDriven(activationConfig = | | { | | ... | | @ActivationConfigProperty(propertyName="DLQMaxResent", propertyValue="10") | | }) 3. Remoting configuration changes The remoting-service.xml needs to be changed, by adding the following two new attributes (as result of http://jira.jboss.org/jira/browse/JBMESSAGING-644) to the Connector's configuration: | <attribute name="clientSocketClass" isParam="true">org.jboss.jms.client.remoting.ClientSocketWrapper</attribute><br> | <attribute name="serverSocketClass">org.jboss.jms.server.remoting.ServerSocketWrapper</attribute><br> | Example: | <mbean code="org.jboss.remoting.transport.Connector" name="jboss.messaging:service=Connector,transport=socket" display-name="Socket transport Connector"> | <attribute name="Configuration"> | <config> | | <invoker transport="socket"> | ... | <attribute name="clientSocketClass" isParam="true">org.jboss.jms.client.remoting.ClientSocketWrapper</attribute> | <attribute name="serverSocketClass">org.jboss.jms.server.remoting.ServerSocketWrapper</attribute> | ... | </invoker> | </config> | | </attribute> | </mbean> | In case you use an SSL connector, the same attributes must be added to the SSL Connector's configuration. 4. Database schema changes The number of delivery attempts is now recorded in the database. For this reason, the current server version requires a database schema change. 1.0.1.GA-created tables are incompatible with 1.0.1.SP2, so in order to use SP2, you need to drop the old tables and recreate them. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991779#3991779 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991779

19 years, 4 months

1
0
0 / 0

[JBoss jBPM] - HOW to create new node types ???

by juangiovanolli

what 's the best way to create new node types that extends from org.jbpm.graph.def.node, inheriting all the capabilities of this?? Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991778#3991778 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991778

19 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user December 2006