February 2007 - jboss-user - Jboss List Archives

[JBoss Seam] - Re: deploy jboss seam application on oc4j server

by merajcal

Hi recycle_bin01, Same problem I have been facing for long time, and I had logged the problem but did not get any response, so I dont know what to do, I have to start my project also, The concept provided by the seam is excellent but I am sorry to say that the support provided by the forum is not very good, so I have to look for some other option like shale etc. Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4014479#4014479 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4014479

19 years, 2 months

1
0
0 / 0

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

by ovidiu.feodorov＠jboss.com

JBoss Messaging 1.0.1.SP4 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...). This service pack fixes several major bugs present in 1.0.1.SP2 and previous releases. The most serious bug is http://jira.jboss.org/jira/browse/JBMESSAGING-721, which was causing message redelivery not to function properly. This bug fix alone should justify an upgrade to 1.0.1.SP4, especially if you use Message Driven Beans and Container Managed Transactions. Another critical bug is http://jira.jboss.org/jira/browse/JBMESSAGING-787, which was causing long-running invocations (such as sending a large transaction to the server) to time out inadvertently. The root cause was identified to be http://jira.jboss.org/jira/browse/JBREM-691. The new Remoting library incorporated by 1.0.1.SP4 contains the fix for this bug. Other bugs fixes address the following 1.0.1.SP2 problems: * Broken QueueBrowser behavior (http://jira.jboss.org/jira/browse/JBMESSAGING-803) * Non-compliant client ID behavior - the previous version allowed simultaneous clients with same client ID (http://jira.jboss.org/jira/browse/JBMESSAGING-791) * Incorrect handling of the replyTo property for persistent messages in some situations (http://jira.jboss.org/jira/browse/JBMESSAGING-757) * Corruption of the security context in managed environment (http://jira.jboss.org/jira/browse/JBMESSAGING-807) * Potential deadlock during the client initialization (http://jira.jboss.org/jira/browse/JBMESSAGING-800) * Memory leaks (http://jira.jboss.org/jira/browse/JBMESSAGING-638) The complete list of changes introduced by this release is available at http://jira.jboss.org/jira/secure/ReleaseNote.jspa?version=12311164&style... The JBoss Messaging project roadmap is available here: http://jira.jboss.org/jira/browse/JBMESSAGING?report=com.atlassian.jira.p... We would like to use this opportunity to thank Andrea Di Cesare, Ilya Bochkov and our colleague Amit Bhayani for identifying some of the previously mentioned bugs, taking the trouble to report them, provide test cases, workarounds and fix suggestions. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4014461#4014461 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4014461

19 years, 2 months

1
0
0 / 0

[JBoss Messaging] - JBoss Messaging 1.0.1.SP4 Released

by ovidiu.feodorov＠jboss.com

JBoss Messaging 1.0.1.SP4 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...). This service pack fixes several major bugs present in 1.0.1.SP2 and previous releases. The most serious bug is http://jira.jboss.org/jira/browse/JBMESSAGING-721, which was causing message redelivery not to function properly. This bug fix alone should justify an upgrade to 1.0.1.SP4, especially if you use Message Driven Beans and Container Managed Transactions. Another critical bug is http://jira.jboss.org/jira/browse/JBMESSAGING-787, which was causing long-running invocations (such as sending a large transaction to the server) to time out inadvertently. The root cause was identified to be http://jira.jboss.org/jira/browse/JBREM-691. The new Remoting library incorporated by 1.0.1.SP4 contains the fix for this bug. Other bugs fixes address the following 1.0.1.SP2 problems: * Broken QueueBrowser behavior (http://jira.jboss.org/jira/browse/JBMESSAGING-803) * Non-compliant client ID behavior - the previous version allowed simultaneous clients with same client ID (http://jira.jboss.org/jira/browse/JBMESSAGING-791) * Incorrect handling of the replyTo property for persistent messages in some situations (http://jira.jboss.org/jira/browse/JBMESSAGING-757) * Corruption of the security context in managed environment (http://jira.jboss.org/jira/browse/JBMESSAGING-807) * Potential deadlock during the client initialization (http://jira.jboss.org/jira/browse/JBMESSAGING-800) * Memory leaks (http://jira.jboss.org/jira/browse/JBMESSAGING-638) The complete list of changes introduced by this release is available at http://jira.jboss.org/jira/secure/ReleaseNote.jspa?version=12311164&style... The JBoss Messaging project roadmap is available here: http://jira.jboss.org/jira/browse/JBMESSAGING?report=com.atlassian.jira.p... We would like to use this opportunity to thank Andrea Di Cesare, Ilya Bochkov and our colleague Amit Bhayani for identifying some of the previously mentioned bugs, taking the trouble to report them, provide test cases, workarounds and fix suggestions. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4014460#4014460 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4014460

19 years, 2 months

1
0
0 / 0

[JBoss Seam] - Re: Seam & Maven2

by fers

Hello, I have updated the integration (http://software.softeu.cz/seam/). I have integrated new features from seamgen 1.1.6.GA (security, ...) and added support for container profiles: modify jdbc.properties and profiles.xml to reflect your database / container configuration. What is still missing: fix support for embedded-ejb (missing jar dependency) * fix problems for deploying to jboss * add support for testng + embedded EJB (some support is already there) * test support for weblogic, websphere and flassfish containers * add support for multiproject (separate ear, jar and war) * I will be very thankfull for testing/feedback. Petr Ferschmann View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4014452#4014452 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4014452

19 years, 2 months

1
0
0 / 0

[Installation, Configuration & Deployment] - different hostnames to different applications?

by Linuso

I'm pretty new to Jboss and I hope you can help me whit my problem.. I's it possible to bind different hostnames to different applications?? I runnig Jboss AS 4.0.5 on a Linux server that are configured whit 3 different ip's / hostnames eth0 server.test.net 192.168.0.10 eth0:1 app1.test.net 192.168.0.11 eth0:2 app2.test.net 192.168.0.12 the applications is placed in /home/jboss/jboss/server/edfault/deploy/app1.war /home/jboss/jboss/server/edfault/deploy/app2.war If I use my webbrowser and go to any of those url's the applications works fine! server.test.net/app1 or app2 app1.test.net/app1 or app2 app2.test.net/app1 or app2 The problem is that I want to point the app-hostnames to the applications they belong to.. app1.test.net to app1 and app2.test.net to app2 I's it possible? How can I do this?? I have tried to google for an solution but I did not find anything good :( Please help me.. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4014449#4014449 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4014449

19 years, 2 months

1
0
0 / 0

[JBoss Portal] - Re: Deploy new portal using existing portlets

by MLipp

Thanks Peter. You write "you should be able to reference existing portlets ...", well, I tried this already, but all I get is Failed to create instance WfDemoPortalIntroInstance of portlet /de.danet.an.jbportal.war.local.portal.CMSPortlet because portlet /de.danet.an.jbportal.war.local.portal.CMSPortlet is not available so the portal effectively prepends the name of the WAR with the portal definition (de.danet.an.jbportal.war) to the full portlet name. It does not recognize this as a "fully qualified" (not-to-be-modified) portlet name. Maybe I'll head for the programmatic approach described in the referenced thread. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4014448#4014448 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4014448

19 years, 2 months

1
0
0 / 0

[Security & JAAS/JBoss] - standard extension of JAAS for instance based authorization?

by zetzioni

I'm wondering what is the best to do the following: I would like to extend the standard role based access control check which is done by JAAS (based on the role needed to run the method and the role the user has), with a test that will check if the user is allowed to run the method on the given params. What I have in mind is something like this: for each EJB I will have permission class (possibly most of them will share the same), and an interceptor that would call something like SecurityManager (or AccessController) checkPermission. I'm missing quite a lot of the picture though. Not enough that I'm not sure this is the right thing, I'm also not sure on the details of how to do it. For example, how would I map Permission class to a method in an EJB? Has anyone done this kinda thing? any recommendation on the right way? Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4014446#4014446 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4014446

19 years, 2 months

1
0
0 / 0

[JBoss Seam] - Re: Booking example allows check in date > check out

by saeediqbal1

This is interesting. Here is the confirm hotel booking page content. negative pricing. hmmm Name: W Hotel Address: Union Square, Manhattan City, State: NY, NY Zip: 10011 Country: USA Total payment: -$4,050.00 Check In Date: Feb 11, 2007 Check Out Date: Feb 2, 2007 Credit Card #: 3332333233323332 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4014441#4014441 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4014441

19 years, 2 months

1
0
0 / 0

[JBoss Seam] - Booking example allows check in date > check out

by saeediqbal1

Is this bug intentional in the booking example? Currently we can have check out date to be earlier than check in date even though the logic in the HotelBookingAction.java checks for it and documentation has a slightly different code. Or is something else broken? Please advise. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4014440#4014440 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4014440

19 years, 2 months

1
0
0 / 0

[JBossCache] - Re: problem when using new Fqn with Integer

by emailmsgbox

its is not a "bit poor" , inconsistent cache behavior is a big bug. you can start by removing the use of Integer object from the document. this pitfall is confusing at best also , what about performance? When I put my user hat(not design hat) I think IMHO that the FQN API should be String only until this design issue is resolved View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4014438#4014438 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4014438

19 years, 2 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 February 2007