April 2008 - jboss-dev-forums - Jboss List Archives

[Design of EJB 3.0] - Re: JBMETA-6, JBMETA-25 resolved jndi name

by alex.loubyansky＠jboss.com

I guess current determineJndiName logic should be the default one? How is this going to work if the JndiBindingPolicy doesn't have access to the metadata? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146520#4146520 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146520

16 years, 5 months

1
0
0 / 0

[Design of JBoss IIOP on JBoss] - Re: CORBA_BAD_INV_ORDER running AS 5 IIOP tests with JDK 6

by smcgowan＠redhat.com

This was interesting - http://bugs.sun.com/bugdatabase/view_bug.do;jsessionid=fd40a0e2c4c9b79ada... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146494#4146494 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146494

16 years, 5 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Publish ESB services to web services

by mark.little＠jboss.com

"jim.ma" wrote : | So far ,what I have in mind is building the SOAPFault message using ActionProcessingException. | We already do that for ESB fault messages so I think it makes sense. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146486#4146486 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146486

16 years, 5 months

1
0
0 / 0

[Design of EJB 3.0] - Re: EJB3 container for EJB2 beans

by alex.loubyansky＠jboss.com

http://jira.jboss.com/jira/browse/EJBTHREE-1307 fixed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146483#4146483 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146483

16 years, 5 months

1
0
0 / 0

[Design of EJB 3.0] - Re: JBMETA-6, JBMETA-25 resolved jndi name

by scott.stark＠jboss.org

What I'm testing right now is addition of EjbDeploymentSummary, DefaultJndiBindingPolicy to metadata under the org.jboss.metadata.ejb.jboss.jndipolicy.spi and the addition of a determineJndiName(EjbDeploymentSummary) method on JBossEnterpriseBeanMetaData that will load the policy if the default is needed. If there is no policy it will use an org.jboss.metadata.ejb.jboss.jndipolicy.plugins.EjbNameJndiBindingPolicy to derive the jndi names from the ejb-name. The ejb3 variations of these api can be noop subclasses for backward compatibility if needed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146482#4146482 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146482

16 years, 5 months

1
0
0 / 0

[Design of EJB 3.0] - Re: JBMETA-6, JBMETA-25 resolved jndi name

by alex.loubyansky＠jboss.com

Yes, I agree. Looking at the interface I don't see how an implementation can get access to the metadata. I'd think there should be a way. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146481#4146481 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146481

16 years, 5 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Failed to connect to server localhost:1099 and class files m

by spandey1982

Hi, We are trying to upgrade our Jboss messaging service from 1.0.1 to 1.4. We are using JBoss 4.2.2 GA and JDK 1.5. I am getting below mentioned exception. I can start the "messaging" application successfully with my queues and topics. But, while running my mdbs along with messaging, I am getting the exception. ... javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:1099 and discovery failed with error: javax.naming.CommunicationException: Failed to retrieve stub from server 192.168.209.195:1100 [Root exception is java.io.StreamCorruptedException: unexpected block data] [Root exception is javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]] ... >From net I got suggestion to replace old (1.1) jboss-messaging-client.jar with new one(1.4). I simply replaced the file without building the code with new jar and problem still persisted. Then I tried compiling my code with new jar but got following compilation time symbol not found error for following classes: javax.ejb.MessageDrivenBean, javax.ejb.MessageDrivenContext, etc. I check and found that these classes are present in old jar but not in the new one. Any idea how is it possible. Regards, Sudhakar View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146478#4146478 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146478

16 years, 5 months

1
0
0 / 0

[Design of JBoss ESB] - Schedule for ESB 4.4. release

by Kevin.Conner＠jboss.com

We have now finalised the schedule for the 4.4 release of the ESB project. 19th May - 30th May (2 weeks) JIRA issues will be assigned to the 4.4 release of the project. At this stage we will consider requests for new functionality. 2nd June - 18th July (7 weeks) Development work continues through this period. We will only consider additional JIRA tasks if they are definitely bug fixes, new functionality will be assigned to the next release 21st July - 31st July (2 weeks) This period covers the final testing of the project, in readiness for the release. If there is anything you wish to see in this version of the project then please let us know *before* May 30th. Thanks, Kev View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146471#4146471 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146471

16 years, 5 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Filters in ESB

by mark.little＠jboss.com

The property file is for the ESB instance. If you think saying "JBossESB instance" is better then fine. Create a JIRA and we'll update the docs. We have no concept of per-service filters at the moment (think CORBA POI). That should come in the 5.0 release eventually. At the moment the filter approach, via the property file, seems to be sufficient for all (majority) of the use cases we have. As to how the filter code is loaded into the ESB deployment, it should be possible to add it to your normal classpath resolution and not have to put it within the jbossesb.sar. Do you find that is not the case? If so can you produce a stand-alone test case and we'll investigate. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146470#4146470 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146470

16 years, 5 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Timeboxed development schedule

by Kevin.Conner＠jboss.com

Update: We will be moving the end date of the development work and, therefore, the end date of the release back by one week. The main reason for this decision is to include the work which is currently taking place on the FP branch and verify the integration with AS 4.2.2. The new dates are: 17th March - 2nd May (7 weeks) Development work continues through this period. We will only consider additional JIRA tasks if they are definitely bug fixes, new functionality will be assigned to the next release 5th May - 16th May (2 weeks) This period covers the final testing of the project, in readiness for the release. Apologies for this. Kev View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146466#4146466 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146466

16 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums April 2008