March 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBJCA-54) Google Collect 20080321

by Jesper Pedersen (JIRA)

Google Collect 20080321 ----------------------- Key: JBJCA-54 URL: https://jira.jboss.org/jira/browse/JBJCA-54 Project: JBoss JCA Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0 Alpha1 QE -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBJCA-53) Apache Common CLI 1.1

by Jesper Pedersen (JIRA)

Apache Common CLI 1.1 --------------------- Key: JBJCA-53 URL: https://jira.jboss.org/jira/browse/JBJCA-53 Project: JBoss JCA Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0 Alpha1 QE -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBJCA-52) Apache Common Beanutils 1..7.0

by Jesper Pedersen (JIRA)

Apache Common Beanutils 1..7.0 ------------------------------ Key: JBJCA-52 URL: https://jira.jboss.org/jira/browse/JBJCA-52 Project: JBoss JCA Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0 Alpha1 QE -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBJCA-50) Apache Common Logging 1.1.0.jboss

by Jesper Pedersen (JIRA)

Apache Common Logging 1.1.0.jboss --------------------------------- Key: JBJCA-50 URL: https://jira.jboss.org/jira/browse/JBJCA-50 Project: JBoss JCA Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0 Alpha1 Standalone + Test + QE -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBJCA-48) ANTLR 2.7.6

by Jesper Pedersen (JIRA)

ANTLR 2.7.6 ----------- Key: JBJCA-48 URL: https://jira.jboss.org/jira/browse/JBJCA-48 Project: JBoss JCA Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0 Alpha1 QE -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBJCA-49) Apache Log4J 1.2.14

by Jesper Pedersen (JIRA)

Apache Log4J 1.2.14 ------------------- Key: JBJCA-49 URL: https://jira.jboss.org/jira/browse/JBJCA-49 Project: JBoss JCA Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0 Alpha1 Standalone + Test -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (EJBTHREE-508) @GeneratedValue does not work with composite primary key

by Xiaolong Hao (JIRA)

[ https://jira.jboss.org/jira/browse/EJBTHREE-508?page=com.atlassian.jira.p... ] Xiaolong Hao commented on EJBTHREE-508: --------------------------------------- if possible can we re-visit this issue? We do have a case that we need a composite key with one surrogate field and one for db schema so that we can access same functional table in different schema. Plus, hibernate is handling it in xml configuration. HHH-2060. > @GeneratedValue does not work with composite primary key > -------------------------------------------------------- > > Key: EJBTHREE-508 > URL: https://jira.jboss.org/jira/browse/EJBTHREE-508 > Project: EJB 3.0 > Issue Type: Bug > Affects Versions: EJB 3.0 RC6 - PFD > Reporter: Holger Johanndeiter > Assignee: Emmanuel Bernard > Attachments: User.java, UserPK.java > > > I have an entity with a primary key class (@IdClass annotation) where i want the id to be auto-generated. (see forum post) > That does not happen though, no ids are generated, the only id i get is 0. (leads to one database entry where the id is 0, after that errors of course). > Database is Hypersonic SQL. > The entity works perfectly fine without @IdClass annotation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-6614) Client received com.sun.xml.ws.streaming.XMLStreamReaderException when invoking WebService annotated with OneWay

by Mosse Franck (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-6614?page=com.atlassian.jira.plug... ] Mosse Franck updated JBAS-6614: ------------------------------- Security: Public (was: JBoss Internal) > Client received com.sun.xml.ws.streaming.XMLStreamReaderException when invoking WebService annotated with OneWay > ---------------------------------------------------------------------------------------------------------------- > > Key: JBAS-6614 > URL: https://jira.jboss.org/jira/browse/JBAS-6614 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web Services > Affects Versions: JBossAS-5.0.0.GA > Environment: JBoss 5.0.0 under Windows XP > wsdl and stub generated using jax-ws tools > Reporter: Mosse Franck > Assignee: Alessio Soldano > > A standalone client receives an exception when it tries to invoke a web service annotated with @OneWay. > The exception received on the client side is : > com.sun.xml.ws.streaming.XMLStreamReaderException: XML reader error: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog > at [row,col {unknown-source}]: [1,0] > at com.sun.xml.ws.streaming.XMLStreamReaderUtil.wrapException(XMLStreamReaderUtil.java:242) > at com.sun.xml.ws.streaming.XMLStreamReaderUtil.next(XMLStreamReaderUtil.java:70) > at com.sun.xml.ws.streaming.XMLStreamReaderUtil.nextContent(XMLStreamReaderUtil.java:85) > at com.sun.xml.ws.streaming.XMLStreamReaderUtil.nextElementContent(XMLStreamReaderUtil.java:75) > at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:167) > at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:149) > at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:121) > at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:280) > at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:158) > at com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:74) > at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:559) > at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:518) > at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:503) > at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:400) > at com.sun.xml.ws.client.Stub.process(Stub.java:235) > at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:120) > at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:230) > at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:210) > at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:103) > at $Proxy30.createPerson(Unknown Source) > at test.example1.TestPeopleManager.testCreatePerson(TestPeopleManager.java:41) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99) > at org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81) > at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) > at org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75) > at org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45) > at org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:66) > at org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:35) > at org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42) > at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) > at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:45) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) > Caused by: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog > at [row,col {unknown-source}]: [1,0] > at com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOF(StreamScanner.java:686) > at com.ctc.wstx.sr.BasicStreamReader.handleEOF(BasicStreamReader.java:2134) > at com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2040) > at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1069) > at com.sun.xml.ws.util.xml.XMLStreamReaderFilter.next(XMLStreamReaderFilter.java:56) > at com.sun.xml.ws.streaming.XMLStreamReaderUtil.next(XMLStreamReaderUtil.java:51) > ... 39 more > The code of the web service is : > package test.example1; > import javax.ejb.Stateless; > import javax.jws.Oneway; > import javax.jws.WebMethod; > import javax.jws.WebParam; > import javax.jws.WebService; > @WebService( name="PeopleManager", serviceName="PeopleManager", targetNamespace="http://techtip.com/samples/example1") > @Stateless > public class PeopleManager { > @WebMethod( operationName="createPerson") > @Oneway > public void createPerson ( @WebParam(name="firstName") String firstName, @WebParam(name="lastName")String lastName, @WebParam(name="age") int age) > { > System.out.println ("Creating person [firstName=" + firstName + "; lastName=" + lastName + ";age=" + age + "]"); > } > } > Remark : If the @OneWay annotation is removed, the invocation from the client is successful. > The code of the client is : > package test.example1; > import java.net.MalformedURLException; > import java.net.URL; > import javax.xml.namespace.QName; > import org.junit.BeforeClass; > import org.junit.Test; > import test.example1.generated.*; > public class TestPeopleManager { > > private static PeopleManager peopleManager; > private static final String HOST_NAME = "localhost"; > private static final String PORT_NUMBER = "8080"; > private static final String TARGET_NAMESPACE = "http://techtip.com/samples/example1"; > > @BeforeClass > public static void beforeClass () throws MalformedURLException > { > String wsdlUrl = "http://" + HOST_NAME + ":" + PORT_NUMBER + "/TestWebService/PeopleManager?wsdl"; > URL wsdlLocation = new URL( wsdlUrl); > QName serviceName = new QName( > TARGET_NAMESPACE, > "PeopleManager" > ); > > PeopleManager_Service service = new PeopleManager_Service( > wsdlLocation, serviceName > ); > > peopleManager = service.getPeopleManagerPort (); > > } > @Test > public void testCreatePerson() throws Exception { > peopleManager.createPerson ( "Franck", "Mosse", 40); > } > > } > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2595) JMX Resolver for JSF

by Dimitris Andreadis (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-2595?page=com.atlassian.jira.plug... ] Dimitris Andreadis updated JBAS-2595: ------------------------------------- Comment: was deleted > JMX Resolver for JSF > -------------------- > > Key: JBAS-2595 > URL: https://jira.jboss.org/jira/browse/JBAS-2595 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service > Affects Versions: JBossAS-4.0.4RC1 > Reporter: Stan Silvert > Assignee: Stan Silvert > Priority: Optional > Fix For: JBossAS-5.1.0.CR1 > > > The JMX resolver does for JMX what Seam is doing for EJB. That is, it provides a ?seam? for JMX and JSF. It allows you to map an MBean as a JSF managed bean. Then you can use attributes from JMX in any JSF component. > The obvious use case for this is where you want to create a custom JMX console that only contains the attributes you are interested in. For example, I might want to monitor/modify the attributes for some DataSources and Tomcat threads all on a single JSP page. I would create a faces-config-jmx.xml file like this and place it in the WEB-INF directory: > <faces-config-jmx> > <managed-bean> > <managed-bean-name>defaultDS</managed-bean-name> > <jmx-object-name>jboss.jca:name=DefaultDS,service=ManagedConnectionPool</jmx-object-name> > </managed-bean> > <managed-bean> > <managed-bean-name>foo</managed-bean-name> > <jmx-object-name>Foo:name=Foo,type=XMBean</jmx-object-name> > </managed-bean> > </faces-config-jmx> > To use this in a JSP page, I just use the managed bean name in my JSF component as usual: > <h:form> > > <h:outputText value="New DefaultDS maxSize: "/> > <h:inputText value="#{defaultDS.MaxSize}" converter="javax.faces.Integer" /> > > <h:outputText value="New DefaultDS AvailableConnectionCount: "/> > <h:outputText value="#{defaultDS.AvailableConnectionCount}" /> > > <h:outputText value="Array access test for foo.myArray[2]: "/> > > <h:outputText value="Current value is: #{foo.myArray[2]}" /> > <h:commandButton value="Submit"/> > > </h:form> > The mechanism to do JMX to JSF resolution will be installed automatically using the new JSF initialization specified here: http://jira.jboss.com/jira/browse/JBAS-2593 > The application developer is only required to provide a faces-config-jmx.xml containing the mappings from managed bean names to JMX ObjectNames. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-3202) Extend the xpath test coverage

by Dimitris Andreadis (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-3202?page=com.atlassian.jira.plug... ] Dimitris Andreadis closed JBAS-3202. ------------------------------------ Fix Version/s: (was: JBossAS-5.1.0.CR1) Resolution: Won't Fix Aaron not available - wont' fix. > Extend the xpath test coverage > ------------------------------ > > Key: JBAS-3202 > URL: https://jira.jboss.org/jira/browse/JBAS-3202 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Test Suite, XML services > Reporter: Dimitris Andreadis > Assignee: Aaron Walker > > Extend the jaxp XPath API test coverage after the inital tests introduced by JBAS-2411 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 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-jira March 2009