November 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4985) Mac OS X 10.5 - How to add as a Web Service

by Cesar Quebral (JIRA)

Mac OS X 10.5 - How to add as a Web Service ------------------------------------------- Key: JBAS-4985 URL: http://jira.jboss.com/jira/browse/JBAS-4985 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.2.GA Environment: Mac OS X Server 10.5 running JBoss 4.2.2 Reporter: Cesar Quebral http://localhost:8080 works when run on the same server. However, http://<ip_address>:8080 does not work from other computers on the network. I called Apple and they don't support JBoss. Apparently, I need to add the site in Server Admin console under Web. The problem is it's asking for the 'web folder' location and the name of the default 'index' file. Has anyone successfully run JBoss 4.2.2 on Mac OS X Server 10.5? Thanks for your help. -- 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, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1794) new italian updates

by Luca Stancapiano (JIRA)

new italian updates ------------------- Key: JBPORTAL-1794 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1794 Project: JBoss Portal Issue Type: Patch Security Level: Public (Everyone can see) Components: Portal CMS, Portal Core, Portal Core Admin, Portal Identity, Portal Migration, Portal Samples, Portal Search Affects Versions: 2.6.2 Final Environment: not important Reporter: Luca Stancapiano Assigned To: Sohil Shah Fix For: 2.6.3 Final hi ... I created new updates about italian language for portal . I send it here -- 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, 1 month

2
8
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1153) Optimisation for message sucking

by Tim Fox (JIRA)

Optimisation for message sucking -------------------------------- Key: JBMESSAGING-1153 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1153 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.4.0.SP2 Currently JBM uses a single shared database for all nodes so when sucking messages we can do a simple optimisation to move the message from one channel to another using a SQL UPDATE. This should improve performance for message redistribution, especially for larger messages. -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1713) add proxy capabilities to the portal build

by Andrew Oliver (JIRA)

add proxy capabilities to the portal build ------------------------------------------ Key: JBPORTAL-1713 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1713 Project: JBoss Portal Issue Type: Patch Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.3 Final Reporter: Andrew Oliver Assigned To: Julien Viet This patch will add proxy settings to the build i.e. C:\Users\oliveran\portal\JBoss_Portal_Branch_2_6\build>build.bat -Dproxy.host=localhost -Dproxy.port=5865 -Dproxy.username=xxx -Dproxy.password=xxx -- 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, 1 month

3
13
0 / 0

[JBoss JIRA] Created: (JBAS-4949) NPE in ProxyFactoryHelper

by Thomas Diesler (JIRA)

NPE in ProxyFactoryHelper ------------------------- Key: JBAS-4949 URL: http://jira.jboss.com/jira/browse/JBAS-4949 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler -- 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, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-4987) JBOSS WS:Cannot obtain endpoint meta data

by cai jc (JIRA)

JBOSS WS:Cannot obtain endpoint meta data ------------------------------------------ Key: JBAS-4987 URL: http://jira.jboss.com/jira/browse/JBAS-4987 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: JBossAS-4.2.2.GA Environment: JBOSS 4.2.2 GA, JDK1.6 Reporter: cai jc Assigned To: Thomas Diesler I created a web service endpoint using JWS: /* * BookWS.java * * * To change this template, choose Tools | Template Manager * and open the template in the editor. */ package net.cjc.ws; import java.util.List; import javax.ejb.*; import javax.jws.*; import javax.jws.soap.SOAPBinding; import net.cjc.beans.AuthorManager; import net.cjc.entity.Book; @WebService(name="BookWS",targetNamespace="http://net.cjc.ws",serviceName="BookWSService") @SOAPBinding(style= SOAPBinding.Style.RPC) @Stateless public class BookWS { /* @EJB private AuthorManager am; @WebMethod public List<Book> getMyBook(String me) { return am.queryBooks(me); }*/ @WebMethod public String getMyBook(String me) { return "you have nothing!"; } } And modified web.xml to configure this endpoint as a servlet. At deploy time,the app server throws an exception: 06:13:45,593 ERROR [MainDeployer] Could not start deployment: file:/D:/jboss-4.2.2.GA/server/default/tmp/deploy/tmp7551cjc.ear-contents/cjc-war.war java.lang.NoClassDefFoundError: Could not initialize class com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:422) at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:286) at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:139) at com.sun.xml.bind.api.JAXBRIContext.newInstance(JAXBRIContext.java:105) at com.sun.xml.bind.api.JAXBRIContext.newInstance(JAXBRIContext.java:116) ... But I still can see this web service from http://localhost:8080/jbossws/services.While I click it to retrieve WSDL,another exception is thrown: 06:25:15,796 ERROR [RequestHandlerImpl] Error processing web service request java.lang.IllegalStateException: Cannot obtain endpoint meta data at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleWSDLRequest(RequestHandlerImpl.java:520) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doGet(RequestHandlerImpl.java:144) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:126) at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84) .... Is this a bug? or my fault? -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4851) TECH REVIEW: Server Configuration Guide - Chapter1 - Enterprise Applications with EJB3 Services

by samson kittoli (JIRA)

TECH REVIEW: Server Configuration Guide - Chapter1 - Enterprise Applications with EJB3 Services ----------------------------------------------------------------------------------------------- Key: JBAS-4851 URL: http://jira.jboss.com/jira/browse/JBAS-4851 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Server Configuration Guide Affects Versions: JBossAS-4.2.2.GA Reporter: samson kittoli Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide 1. Open document in Open Office 2. Edit -> Changes -> Record 3. Edit the document 4. Save changes and reattach to this Jira It is important for track changes to be enabled so the re-write can be easily performed. http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/ -- 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, 1 month

3
8
0 / 0

[JBoss JIRA] Created: (JBAS-4433) Row-locking enhancement for loading bean outside of a transaction

by Scott Marlow (JIRA)

Row-locking enhancement for loading bean outside of a transaction ----------------------------------------------------------------- Key: JBAS-4433 URL: http://jira.jboss.com/jira/browse/JBAS-4433 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: EJB2 Affects Versions: JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta1, JBossAS-4.0.4.GA Reporter: Scott Marlow Assigned To: Scott Marlow Fix For: JBossAS-5.0.0.GA, JBossAS-4.2.1.CR1 JBoss recommends that applications should use transactions (see user forum reference). However, there are certain types of applications that use "transaction-type=NotSupported" and load data without a transaction. If the bean is being loaded without a transaction, treat the operation as if row-locking==false. -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-1083) Augment Assignable interface

by s b (JIRA)

Augment Assignable interface ---------------------------- Key: JBPM-1083 URL: http://jira.jboss.com/jira/browse/JBPM-1083 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Environment: All Reporter: s b Assigned To: Tom Baeyens The Assignable interface needs additional methods defined for efficient code development: getName() getId() getActorId() getPooledActors() Without these methods, casting and "instanceof" cases are required and much duplicate code for processing of assignments to both SwimlaneInstance and TaskInstance. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4719) Implementations of Invoker should implement equals as an equality check rather than relying on Object.equals, this is important for cluster fail-over support

by Scott Marlow (JIRA)

Implementations of Invoker should implement equals as an equality check rather than relying on Object.equals, this is important for cluster fail-over support ------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-4719 URL: http://jira.jboss.com/jira/browse/JBAS-4719 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta2, JBossAS-4.0.5.GA, JBossAS-4.0.4.GA Reporter: Scott Marlow Assigned To: Scott Marlow Fix For: JBossAS-4.2.2.GA, JBossAS-5.0.0.CR1, JBossAS-4.0.5.SP1 , JBossAS-4.2.3.GA Part of how JRMPInvokerProxyHA handles fail-over includes removing the reference to the node that left the cluster. However, the dead node is not removed as an equality check is not implemented by certain Invoker implementations. The relevant code in JRMPInvokerProxyHA is protected void removeDeadTarget(Object target) { if (this.familyClusterInfo != null) this.familyClusterInfo.removeDeadTarget (target); } The code in familyClusterInfo is: public ArrayList removeDeadTarget(Object target) { synchronized (this) { ArrayList tmp = (ArrayList) targets.clone(); tmp.remove (target); this.targets = tmp; this.isViewMembersInSyncWithViewId = false; } return this.targets; } Since, we didn't include an equals test in many of the different Invoker implementations, the above "tmp.remove(target)" operation fails. The reason for the failure is due to the "targets" ArrayList changing on every invocation (to reflect the current cluster server membership list), a new "targets" is created (so of course comparing references later will not work.) A similar problem occurs with the EJB2 load balancers after a cluster membership changes. I think that these issues will be solved by implementing an equals test in the different invokers that can handle equality testing. PooledInvokerProxy should implement equals based on ServerAddress. -- 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, 1 month

4
11
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2007