[JBoss-user] Deployment sequence of multiple .SARs in .EAR (jboss--3.0.6)
Title: Deployment sequence of multiple .SARs in .EAR (jboss--3.0.6) Hi, What exactly is the ordering rule when an .ear, containing multiple .sar files, is deployed? We have the following jboss-app.xml: module servicefirstservices.sar/service /module module servicesecondservices.sar/service /module Important detail: the first .sar has to be initialized BEFORE the second one. When we deployed the .ear on JBoss3.0.3, the deployment occured in the right sequence. But when we try JBoss3.0.6 the first .sar is always deployed AFTER the second one, regardless of the order wherein the modules are described in the deployment descriptor. How can we force the right deployment order of these .sar files? What are the rules here? Thanks in advance, Wonne Keysers
[JBoss-user] Shutdown problems in JBoss-IDE alpha_05
The shutdown mechanism has changed for JBoss = 3.2. To make shutdown work for this servers with the current JBoss-IDE alpha_05 go to the launch configuration and choose the shutdown tab. There you must enter -S as program argument. Now shutdown should work. Hans --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] How to throw AxisFault in JBoss.net?
Thanks for your reply but AxisFault is a checked exception. It inherits from java.rmi.RemoteException. The point is that JBoss.net should be able to report faults from the EJB-tier to the client-side and to wrap the fault inside another fault doesn't make any sense. Jonas On Wed, 2003-01-29 at 22:54, JD Brennan wrote: AxisFault is probably unchecked so it gets wrapped. I bet the spec says that only checked exceptions have to get passed back intact. You could wrap AxisFault in a checked exception, maybe... JD -Original Message- From: Jonas Engman [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 29, 2003 1:21 PM To: [EMAIL PROTECTED] Subject: [JBoss-user] How to throw AxisFault in JBoss.net? I'm using JBoss 3.2beta1/JBoss.net and I'm trying to throw an AxisFault from a SessionBean but the exception seems somehow be wrapped inside a javax.ejb.EJBException. I'm throwing the fault using throw new AxisFault(a fault has occurred); but the faultString that appears on the client-side is javax.ejb.EJBException: null; CausedByException is: a fault has occurred. A closer look at the detail-body using TCPMon shows that the it contains the full stacktrace followed by the original faultString but it's all wrapped inside the detail-tag. The same thing goes for the original faultCode, faultActor and faultDetail. Is it somehow possible to throw an AxisFault that doesn't get wrapped inside a SOAPFault that contains the javax.ejb.EJBException? Without the ability to throw a user-defined AxisFault I don't see how a fault should be reported to the client-side. Thanks Jonas --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Deployment sequence of multiple .SARs in .EAR (jboss--3.0.6)
Well, the good solution is only in jboss 4: you can put a depends> tag at the top level of jboss-service.xml with the object name the deploymentInfo for your first .sar is deployed to. This is not easily portable to 3.0.x unfortunately. The easy solution for 3.0.x is probably to put firstervices.sar inside secondservices.sar. david jencks On Thursday, January 30, 2003, at 03:29 AM, Keysers, Wonne wrote: Hi, What exactly is the ordering rule when an .ear, containing multiple .sar files, is deployed? We have the following jboss-app.xml: module> service>firstservices.sar/service> /module> module> service>secondservices.sar/service> /module> Important detail: the first .sar has to be initialized BEFORE the second one. When we deployed the .ear on JBoss3.0.3, the deployment occured in the right sequence. But when we try JBoss3.0.6 the first .sar is always deployed AFTER the second one, regardless of the order wherein the modules are described in the deployment descriptor. How can we force the right deployment order of these .sar files? What are the rules here? Thanks in advance, Wonne Keysers
AW: [JBoss-user] How to throw AxisFault in JBoss.net?
The custom exception that you throw should be ideally mapped by axis/jboss.net into the soapfault. (Your bean should not know whether it is published as a web-service). What if you declare and throw a CustomApplicationException? How does the returned soap-message look like? If I remember right, axis will include the stack trace into the detail section of a soap-fault ... AxisFault is the axis-internal exception if something goes wrong in the web service engine (not the application), therefore it has the same status as a java.rmi.ServerException, java.rmi.RemoteException ... But that is used only outside the application in the container. CGJ -Ursprüngliche Nachricht- Von: Jonas Engman [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 30. Januar 2003 11:44 An: '[EMAIL PROTECTED]' Betreff: RE: [JBoss-user] How to throw AxisFault in JBoss.net? Thanks for your reply but AxisFault is a checked exception. It inherits from java.rmi.RemoteException. The point is that JBoss.net should be able to report faults from the EJB-tier to the client-side and to wrap the fault inside another fault doesn't make any sense. Jonas On Wed, 2003-01-29 at 22:54, JD Brennan wrote: AxisFault is probably unchecked so it gets wrapped. I bet the spec says that only checked exceptions have to get passed back intact. You could wrap AxisFault in a checked exception, maybe... JD -Original Message- From: Jonas Engman [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 29, 2003 1:21 PM To: [EMAIL PROTECTED] Subject: [JBoss-user] How to throw AxisFault in JBoss.net? I'm using JBoss 3.2beta1/JBoss.net and I'm trying to throw an AxisFault from a SessionBean but the exception seems somehow be wrapped inside a javax.ejb.EJBException. I'm throwing the fault using throw new AxisFault(a fault has occurred); but the faultString that appears on the client-side is javax.ejb.EJBException: null; CausedByException is: a fault has occurred. A closer look at the detail-body using TCPMon shows that the it contains the full stacktrace followed by the original faultString but it's all wrapped inside the detail-tag. The same thing goes for the original faultCode, faultActor and faultDetail. Is it somehow possible to throw an AxisFault that doesn't get wrapped inside a SOAPFault that contains the javax.ejb.EJBException? Without the ability to throw a user-defined AxisFault I don't see how a fault should be reported to the client-side. Thanks Jonas --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] basic clustering question
Hi all, I've never tried clustering jboss, so I have some basic theory questions. Assume that we have two boxes each running jboss with embedded tomcat/jetty say, and each running my application. 1) I assume that we would have a simple router infront of each of the boxes to handle load balancing and just picking one of the boxes at random to send requests to. Is this how it's normally done? 2) do they both have to use one instance of a database eg on box 3, if so, isn't this a single point of failure anyway? How is this normally done? 3) in order to cluster, do all the beans have to be remote to keep the other nodes updated, or can the entity beans be local? thank you, Brian
[JBoss-user] JBoss Version [Which One ?]
I was just reviewing the list of JBoss packages on SourceForge. I am currently using 3.0.4 and I am wondering when I should venture into a new version. Is the following basically applicable ? 3.0.6: Bug Fixes For 3.0.4 3.2: New Features Over 3.0.4 as well as bug fixes 4.0 [Alpha]: New Architecture (this one's out) //Nicholas = Nicholas Whitehead Home: (973) 377 9335 Cell: (201) 615 2716 Work: (212) 622 5639 [EMAIL PROTECTED] --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] basic clustering question
From: Brian McSweeney [mailto:[EMAIL PROTECTED]] 2) do they both have to use one instance of a database eg on box 3, if so, isn't this a single point of failure anyway? How is this normally done? Usually the database is on a cluster itself with the disks attached over a storage area network iff you have the money. But databases run usually reliably even on a single system. -- Bancotec GmbH EMail: [EMAIL PROTECTED] Calwer Str. 33 Telefon: +49 711 222 992 900 D-70173 Stuttgart Telefax: +49 711 222 992 999 Ein Unternehmen der Cellent AG http://www.cellent.de/ --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] JBoss 3.0.4 CMP 2- DB Error Retrieving Values
Simple entity bean. I do a loookup, it finds the record but when it retrieves the row, it throws a SQL exception saying invalid column name. I cannnot figure out why because when I take the SQL from the console and paste into my SQLEditor, it executes fine. Here is the error: 09:22:36,843 DEBUG [ClientManagerBean] getClient(1) 09:22:36,921 DEBUG [findByPrimaryKey] Executing SQL: SELECT CLIENT_ID FROM CLIENT WHERE CLIENT_ID=? 09:22:37,171 DEBUG [Client] Executing SQL: SELECT MASTER_COMBO_ID, CLIENT_CODE, ORGANIZATION_ID, FEIN, TIPPED_CLIENT, COMPANY_NAME, ADDRESS1, ADDRESS2 , CITY, STATE, ZIP, ZIP4, TEL, PAYROLLCONTACT_NAME, PAYROLLCONTACT_TEL, PAYROLL_SETUP_DATE, PAYROLL_START_DATE, FEATURE_TERMINATION_DATE, ACC_NAME, ACSR_NAME, FICA_LIABILITY_SPLIT, COMBO_CLIENT, WINBACK_CLIENT, CLIENT_START_DATE, FLT_EMAIL, USER_ID, SERVICE_CENTER_ID FROM CLIENT WHERE (CLIENT_ID=?) 09:22:37,453 ERROR [LogInterceptor] TransactionRolledbackLocalException, causedBy: java.sql.SQLException: ORA-00904: invalid column name The full stack trace is attached. = Nicholas Whitehead Home: (973) 377 9335 Cell: (201) 615 2716 Work: (212) 622 5639 [EMAIL PROTECTED] 09:22:37,171 DEBUG [Client] Executing SQL: SELECT MASTER_COMBO_ID, CLIENT_CODE, ORGANIZATION_ID, FEIN, TIPPED_CLIENT, COMPANY_NAME, ADDRESS1, ADDRESS2 , CITY, STATE, ZIP, ZIP4, TEL, PAYROLLCONTACT_NAME, PAYROLLCONTACT_TEL, PAYROLL_SETUP_DATE, PAYROLL_START_DATE, FEATURE_TERMINATION_DATE, ACC_NAME, AC SR_NAME, FICA_LIABILITY_SPLIT, COMBO_CLIENT, WINBACK_CLIENT, CLIENT_START_DATE, FLT_EMAIL, USER_ID, SERVICE_CENTER_ID FROM CLIENT WHERE (CLIENT_ID=?) 09:22:37,453 ERROR [LogInterceptor] TransactionRolledbackLocalException, causedBy: java.sql.SQLException: ORA-00904: invalid column name at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134) at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:289) at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:573) at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1891) at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteDescribe(TTC7Protocol.java:830) at oracle.jdbc.driver.OracleStatement.doExecuteQuery(OracleStatement.java:2391) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2672) at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:589) at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:527) at org.jboss.resource.adapter.jdbc.local.LocalPreparedStatement.executeQuery(LocalPreparedStatement.java:289) at org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadEntityCommand.execute(JDBCLoadEntityCommand.java:122) at org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadEntityCommand.execute(JDBCLoadEntityCommand.java:62) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.loadEntity(JDBCStoreManager.java:572) at org.jboss.ejb.plugins.CMPPersistenceManager.loadEntity(CMPPersistenceManager.java:410) at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.loadEntity(CachedConnectionInterceptor.java:353) at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invoke(EntitySynchronizationInterceptor.java:251) at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:186) at org.jboss.ejb.plugins.EntityReentranceInterceptor.invoke(EntityReentranceInterceptor.java:90) at org.jboss.ejb.plugins.EntityInstanceInterceptor.invoke(EntityInstanceInterceptor.java:163) at org.jboss.ejb.plugins.EntityLockInterceptor.invoke(EntityLockInterceptor.java:107) at org.jboss.ejb.plugins.EntityCreationInterceptor.invoke(EntityCreationInterceptor.java:69) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:107) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:178) at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:60) at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:130) at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:204) at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:493) at org.jboss.ejb.plugins.local.BaseLocalContainerInvoker.invoke(BaseLocalContainerInvoker.java:301) at org.jboss.ejb.plugins.local.EntityProxy.invoke(EntityProxy.java:38) at $Proxy166.getClientId(Unknown Source) at com.adp.ebs.flt.DO.ClientDO.init(Unknown Source) at com.adp.ebs.flt.ejb.ClientManagerBean.getClient(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at
Re: AW: [JBoss-user] How to throw AxisFault in JBoss.net?
Thank you for answer and it's probably best not to throw any custom
AxisFault inside a bean. If I create a CustomApplicationException that
inherits from for example java.lang.Exception and throw that from the
session bean it's all being wrapped up inside a AxisFault that contains
the full classname of the exception followed by the error-message as the
faultMessage. The errorCode of the message is:
xmlns:ns1=http://xml.apache.org/axis/;ns1:Server.userException
The problem, as I see it, is that is should somehow be examine the
exception/fault on the client-side. If a do a try/catch statement like
try {
} catch (AxisFault af) {
}
it's possible to catch the exception but how am I supposed to tell
different server-exceptions apart? The only unique identifier I have is
the faultMessage and I don't think parsing that string is convenient.
Shouldn't I be able to somehow set the faultCode? Or how should the
client handle different faults?
Thanks again
/Jonas
On Thu, 2003-01-30 at 14:05, Jung , Dr. Christoph wrote:
The custom exception that you throw should be ideally mapped by
axis/jboss.net into
the soapfault. (Your bean should not know whether it is published as a
web-service).
What if you declare and throw a CustomApplicationException? How does the
returned soap-message look like?
If I remember right, axis will include the stack trace into the detail
section of a soap-fault ...
AxisFault is the axis-internal exception if something goes wrong in the web
service engine (not the application), therefore it has the same status as a
java.rmi.ServerException, java.rmi.RemoteException ... But that is used only
outside the application in the container.
CGJ
-Ursprüngliche Nachricht-
Von: Jonas Engman [mailto:[EMAIL PROTECTED]]
Gesendet: Donnerstag, 30. Januar 2003 11:44
An: '[EMAIL PROTECTED]'
Betreff: RE: [JBoss-user] How to throw AxisFault in JBoss.net?
Thanks for your reply but AxisFault is a checked exception. It inherits from
java.rmi.RemoteException. The point is that JBoss.net should be able to
report faults from the EJB-tier to the client-side and to wrap the fault
inside another fault doesn't make any sense.
Jonas
On Wed, 2003-01-29 at 22:54, JD Brennan wrote:
AxisFault is probably unchecked so it gets
wrapped. I bet the spec says that only
checked exceptions have to get passed back
intact.
You could wrap AxisFault in a checked exception,
maybe...
JD
-Original Message-
From: Jonas Engman [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 29, 2003 1:21 PM
To: [EMAIL PROTECTED]
Subject: [JBoss-user] How to throw AxisFault in JBoss.net?
I'm using JBoss 3.2beta1/JBoss.net and I'm trying to throw an
AxisFault from a SessionBean but the exception seems somehow be
wrapped inside a javax.ejb.EJBException.
I'm throwing the fault using
throw new AxisFault(a fault has occurred);
but the faultString that appears on the client-side is
javax.ejb.EJBException: null; CausedByException is: a fault has
occurred.
A closer look at the detail-body using TCPMon shows that the it
contains the full stacktrace followed by the original faultString but
it's all wrapped inside the detail-tag.
The same thing goes for the original faultCode, faultActor and
faultDetail.
Is it somehow possible to throw an AxisFault that doesn't get wrapped
inside a SOAPFault that contains the javax.ejb.EJBException?
Without the ability to throw a user-defined AxisFault I don't see how
a fault should be reported to the client-side.
Thanks
Jonas
---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com ___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
###
This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.F-Secure.com/
---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld http://www.vasoftware.com
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
--
Jonas Engman [EMAIL PROTECTED]
---
This SF.NET email is sponsored by:
RE: [JBoss-user] EAR works in 2.4.10 but not in 3.0.6
Let me add more information. - Win XP Pro SP1 + hotfixes - Java 2 SDK 1.4.1_01 - created custom server config from default I tried 3.2RC1 and received the same errors as in my original post. I plan to try 3.0.5 as soon as I can. Also, I seek to know the *correct* way to deploy the EAR that I described; while temporary fixes are good to know, I'm not in a hurry such that I need them. I can continue to run on 2.4.10 or the 2.4.x branch as long as I need to do so. By all means, though, I welcome very much all ideas. Thanks for your help, Craig --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] EAR works in 2.4.10 but not in 3.0.6
3.0.5 failed in the same way that 3.0.6 and 3.2RC1 have failed. Please share any thoughts that you may have. Thanks, Craig --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] JBoss IDE VM Argument Problem
I am setting these VM arguments in the start box of the server configuration: -DTURBO -Xms512m -Xmx512 These values are not getting through because the TURBO property does not exist. Works fine when setting these value in JAVA_OPTS and using run.bat. --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] JBoss MQ durable subscribers
Using JBoss 3.0.4 and JBossMQ. We have a problem if the durable subscriber client attempts to reconnect after an abnormal connection using the same Client ID, the exception is raised: javax.jms.InvalidClientIDException: This loggedOnClientIds is already registered ! at org.jboss.mq.sm.AbstractStateManager.addLoggedOnClientId(AbstractStateManager.java:237) How do we tell JBossMQ that the Client ID is no longer connected? In searching through the forums, I saw the suggestion to use a different Client ID on reconnect, but that does not make sense as the client will miss any messages that published during the time it is down. Thanks, Ken Whitaker __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] RE: question about jboss cmp
On Wednesday, January 29, 2003, at 08:15 AM, Eric J Kaplan wrote: No (I wasn't implying it was easy) but without it, for a lot of applications going through the entity beans isn't practical. More often than not, the applications we work on do NOT simply findByPrimaryKey, but instead need to load based upon a query. I take what Mark Fleury says in his paper to heart about taking advantage of the cacheing capabilities of the container, but not if I have to go to the database anyway to find all the primary keys every time... Yes cache is king. There are two solutions here: all data is in memory, or we cache query results. I have been told the first is fairly easy, and all we would have to do is expose the data to a hypersonic query engine and generate some queries. The second is also fairly easy. We cache results keyed on the ejb-ql and parameters. When when we find a match we, return the results from the cache. When the data changes in any of the query domain we flush the cache. This assumes that the cache can be notified of any changes, which means commit option A until we have a physical store notifications. We've found anytime we've had slowness in our application, it's a session bean going through an entity bean's home interface to find a bunch of beans, and we have to change to direct jdbc, thereby bypassing the container. This is not JBoss specific, it's a general problem. Bottom line is, for mostly read-only apps with limited write, entity beans can be overkill. Yes, there is a speedup if the beans are already in memory of just going to the db to find the primary keys and then pulling the data from the beans already in memory, but the penalty one has to pay if the beans are NOT in memory is severe (one by one, the container goes back to the db to grab each row). This is an only problem. I am surprised you have not already heard of the read-ahead patches around this. As for the in-memory query resolver, I thought this was what jdo and jdo-ql were all about? We have to do similar things in our application on the client side for holding onto local copies of objects and limiting unnecessary calls back out to the app server to get new objects. JDO is simply an interface to a persistence system. In the end it is all about implementation. We plan on adding support to all of this in JBoss, and transparently to you. -dain --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] RE: question about jboss cmp
On Wednesday, January 29, 2003, at 09:30 AM, Eric J Kaplan wrote: Thanks David. You've answered my question. Is this read-ahead capability a specific feature of jboss or in the spec? One issue we have is that as much as we push jboss, we have installs where they for whatever reason aren't using jboss. All tuning options are vendor specific. You should really read the EJB specification. Specifically pay attention to what they don't address. For example, all physical store mappings and tuning are out of the spec. About read-ahead. If I enable it, and I execute an initial finder that reads ahead and caches, and then someone else comes, my understanding is they still have to go back to the db to find primary keys. Will they also read ahead as well? If so, aren't they grabbing extra data that's already in memory? Currently JBoss always goes back to the Database for the primary keys. A query cache is on the todo list for 4.0 and an in-memory query engine may also make it. As for caching between transactions it depends on the commit option. I have code in 4.0 (just haven't gotten to the back port yet) that merges the transaction cache in the main cache after the tx commits, but this only works with commit option A, as B and C always throw out the cache data when the new transaction starts. We hope to address that with Optimistic locking in 4.0. -dain --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
AW: AW: [JBoss-user] How to throw AxisFault in JBoss.net?
Jonas,
I´m not sure what I did there, but there should be some (hmm, outdated) code
in jboss.net that implements
a client-side java.lang.reflect.InvocationHandler for transparently calling
remote web services through
ordinary remote interfaces/dynamic proxies.
It may as well be that I left exception handling out of the game.
This approach is outdated, because the best way, IMHO, is to take the
server-generated wsdl and pre-generate client stubs using the wsdl2java
toolkit. They should have some exception support there ready to remap the
AxisFault to
ordinary java exceptions, shouldn´t they? Classname is there, message is
there, maybe not the stack trace.
If they do not do that, parsing the AxisFault string is still ok, IMHO,
inside the generic proxy or the generated client stub, because then your
application still is clean from those dirty hacks and you can change that
code whenever axis changes just by tweaking the proxy code or the code
generator. In that case, would you volunteer implementing that when I
support you in finding the right place in jboss.net to place it?
Best,
CGJ
-Ursprüngliche Nachricht-
Von: Jonas Engman [mailto:[EMAIL PROTECTED]]
Gesendet: Donnerstag, 30. Januar 2003 15:55
An: '[EMAIL PROTECTED]'
Betreff: Re: AW: [JBoss-user] How to throw AxisFault in JBoss.net?
Thank you for answer and it's probably best not to throw any custom
AxisFault inside a bean. If I create a CustomApplicationException that
inherits from for example java.lang.Exception and throw that from the
session bean it's all being wrapped up inside a AxisFault that contains the
full classname of the exception followed by the error-message as the
faultMessage. The errorCode of the message is:
xmlns:ns1=http://xml.apache.org/axis/;ns1:Server.userException
The problem, as I see it, is that is should somehow be examine the
exception/fault on the client-side. If a do a try/catch statement like
try {
} catch (AxisFault af) {
}
it's possible to catch the exception but how am I supposed to tell different
server-exceptions apart? The only unique identifier I have is the
faultMessage and I don't think parsing that string is convenient. Shouldn't
I be able to somehow set the faultCode? Or how should the client handle
different faults?
Thanks again
/Jonas
On Thu, 2003-01-30 at 14:05, Jung , Dr. Christoph wrote:
The custom exception that you throw should be ideally mapped by
axis/jboss.net into the soapfault. (Your bean should not know whether
it is published as a web-service).
What if you declare and throw a CustomApplicationException? How does
the returned soap-message look like?
If I remember right, axis will include the stack trace into the detail
section of a soap-fault ...
AxisFault is the axis-internal exception if something goes wrong in
the web service engine (not the application), therefore it has the
same status as a java.rmi.ServerException, java.rmi.RemoteException
... But that is used only outside the application in the container.
CGJ
-Ursprüngliche Nachricht-
Von: Jonas Engman [mailto:[EMAIL PROTECTED]]
Gesendet: Donnerstag, 30. Januar 2003 11:44
An: '[EMAIL PROTECTED]'
Betreff: RE: [JBoss-user] How to throw AxisFault in JBoss.net?
Thanks for your reply but AxisFault is a checked exception. It
inherits from java.rmi.RemoteException. The point is that JBoss.net
should be able to report faults from the EJB-tier to the client-side
and to wrap the fault inside another fault doesn't make any sense.
Jonas
On Wed, 2003-01-29 at 22:54, JD Brennan wrote:
AxisFault is probably unchecked so it gets
wrapped. I bet the spec says that only
checked exceptions have to get passed back
intact.
You could wrap AxisFault in a checked exception,
maybe...
JD
-Original Message-
From: Jonas Engman [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 29, 2003 1:21 PM
To: [EMAIL PROTECTED]
Subject: [JBoss-user] How to throw AxisFault in JBoss.net?
I'm using JBoss 3.2beta1/JBoss.net and I'm trying to throw an
AxisFault from a SessionBean but the exception seems somehow be
wrapped inside a javax.ejb.EJBException.
I'm throwing the fault using
throw new AxisFault(a fault has occurred);
but the faultString that appears on the client-side is
javax.ejb.EJBException: null; CausedByException is: a fault has
occurred.
A closer look at the detail-body using TCPMon shows that the it
contains the full stacktrace followed by the original faultString but
it's all wrapped inside the detail-tag.
The same thing goes for the original faultCode, faultActor and
faultDetail.
Is it somehow possible to throw an AxisFault that doesn't get
wrapped
inside a SOAPFault that contains the javax.ejb.EJBException?
Without the ability to throw a user-defined AxisFault I don't see
how
a fault should be reported to the client-side.
Thanks
Jonas
Re: [JBoss-user] help clearing a single user from authentication cache
I have added an RFE to SourceForge: https://sourceforge.net/tracker/index.php?func=detailaid=677614group_id=22866atid=376688 On a side note, does anyone know if Scott Stark is on vacation? I haven't noticed any emails from him on the list for a few days. Thanks again, David -- Meyer-Willner, Bernhard escribió:: RFE in sourceforge sounds good to me. The methods you mention have been there since 3.0.5. -Ursprüngliche Nachricht- Von: David Ward [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 29. Januar 2003 16:33 An: [EMAIL PROTECTED] Betreff: Re: [JBoss-user] help clearing a single user from authentication cache I just upgraded from jboss-3.0.4_tomcat-4.1.12 to jboss-3.0.6_tomcat-4.1.18. I noticed a LOT more methods in the JaasSecurityManagerService. The methods are now: getPrincipal() registerSecurityDomain() isValid() start() create() doesUserHaveRole() getAuthenticationCachePrincipals() stop() getUserRoles() flushAuthenticationCache() destroy() Oh, how I wish there was a removeAuthenticationCachePrincipal() that took a String username or Principal! Should I submit an RFE at sourceforge, or can I beg the powers-that-be (Scott?) to add it to a 3.0.7? Or maybe there's a way to accomplish what I want in 3.0.6 that I don't know about? Thanks, David -- Meyer-Willner, Bernhard escribió:: Very interesting! I would like to do the same. I'm already using the method java.util.List getAuthenticationCachePrincipals() which I believe is available only since 3.0.5 to get a List of the principals currently in the authentication cache. I looked up the JaasSecurityManager directly from the MBeanServer since also my lookup of java:/timedCacheFactory failed. I don't see a method to evict a single user from the cache, just all by calling flushAuthenticationCache. Is there a method like this? Besides...something else...would it be possible to show the meanings of the parameters of MBean operations in JMX Console. Sometimes it's kind of hard to guess what they mean and it's kind of cumbersome to look it up in the Javadocs. Thanks, Bernhard -Ursprüngliche Nachricht- Von: David Ward [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 28. Januar 2003 21:12 An: [EMAIL PROTECTED] Betreff: [JBoss-user] help clearing a single user from authentication cache Using JDK 1.4.1_01, jboss-3.0.4_tomca-tomcat-4.1.2 on Linux. I'm trying to clear from the authentication cache JUST a single user. Invoking flushAuthenticationCache(String) on the mbean works fine, but it flushes *all* users' security infos. I want to call the CachePolicy's remove(Principal) method, so I tried looking up the CachePolicy in JNDI and calling it. Though I found a TimedCachePolicy in jndi under java:/timedCacheFactory/docs (docs is our app's security name), and called the remove(Principal) method successfully, it doesn't seem to do anything. Then, I tried extending JaasSecurityManagerService, configuring the use of my class in jboss-service.xml. I see it in the JMX-Console, but for some reason my added method isn't showing up there (under list mbean operations), and I don't know how to register an MBean interface to expose it. Please help. Again, my end goal is to flush the authentication cache for just a single user. Unfortunately, there's not a public, exposed method in the JaasSecurityManagerService that does this. Also, below is some output from the jmx console JNDIView. - What's up with the Failed to lookup: timedCacheFactory? - When I looked up the timedCacheFactory, it's actually a $Proxy class (EJB?) - java:jaas/docs says it's a SecurityDomainContext below, but when I look it up in code, I get a ClassCastException saying it's *really* a JaasSecurityManager! Why the descrepency? If it *was* actually a SecurityDomainContext, I could call sdc.getAuthenticationCache().remove(new SimplePrincipal(username))! Thanks again, David java: Namespace +- DefaultDS (class: org.jboss.resource.adapter.jdbc.local.LocalDataSource) +- XAConnectionFactory (class: org.jboss.mq.SpyXAConnectionFactory) +- SecurityProxyFactory (class: org.jboss.security.SubjectSecurityProxyFactory) +- DefaultJMSProvider (class: org.jboss.jms.jndi.JBossMQProvider) +- CounterService (class: org.jboss.varia.counter.CounterService) +- comp (class: javax.naming.Context) +- JmsXA (class: org.jboss.resource.adapter.jms.JmsConnectionFactoryImpl) +- ConnectionFactory (class: org.jboss.mq.SpyConnectionFactory) +- jaas (class: javax.naming.Context) | +- JmsXARealm (class: org.jboss.security.plugins.SecurityDomainContext) | +- jbossmq (class: org.jboss.security.plugins.SecurityDomainContext) | +- docs (class: org.jboss.security.plugins.SecurityDomainContext) +- timedCacheFactory (class: javax.naming.Context) Failed to lookup: timedCacheFactory, errmsg=null +- TransactionPropagationContextExporter (class: org.jboss.tm.TransactionPropagationContextFactory) +- Mail (class:
[JBoss-user] Jboss - Tomcat help !!
I'm getting some errors sometimes when I try to access my application. Does anyone know what is it ? Thanks Gabriel Error: Apache Tomcat/4.0.6 - HTTP Status 500 - Internal Server Error type Exception report message Internal Server Error description The server encountered an internal error (Internal Server Error) that prevented it from fulfilling this request. exception javax.servlet.ServletException: loader constraints violated when linking javax/servlet/jsp/JspWriter class at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:471) at org.apache.jsp.login$jsp._jspService(login$jsp.java:67) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:201) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:381) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:473) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:475) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1027) at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1125) at java.lang.Thread.run(Thread.java:536) root cause java.lang.LinkageError: loader constraints violated when linking javax/servlet/jsp/JspWriter class at org.apache.jsp.login$jsp._jspService(login$jsp.java:51) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:201) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:381) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:473) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) at
Re: [JBoss-user] Jboss - Tomcat help !!
Smells like a duplicate package (javax.servlet.jsp) in the classpath. - Original Message - From: Gabriel Pinto [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, January 30, 2003 10:55 AM Subject: [JBoss-user] Jboss - Tomcat help !! I'm getting some errors sometimes when I try to access my application. Does anyone know what is it ? Thanks Gabriel Error: Apache Tomcat/4.0.6 - HTTP Status 500 - Internal Server Error type Exception report message Internal Server Error description The server encountered an internal error (Internal Server Error) that prevented it from fulfilling this request. exception javax.servlet.ServletException: loader constraints violated when linking javax/servlet/jsp/JspWriter class at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImp l.java:471) at org.apache.jsp.login$jsp._jspService(login$jsp.java:67) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.ja va:201) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:381) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:473) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application FilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh ain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:243) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 66) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja va:190) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 66) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase .java:475) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 64) at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:2 46) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 64) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180 ) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 66) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve. java:170) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 64) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170 ) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 64) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 64) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java :174) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 66) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java: 1027) at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1125 ) at java.lang.Thread.run(Thread.java:536) root cause java.lang.LinkageError: loader constraints violated when linking javax/servlet/jsp/JspWriter class at org.apache.jsp.login$jsp._jspService(login$jsp.java:51) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.ja va:201) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:381) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:473) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application FilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh ain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:243) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 66) at
Re: [JBoss-user] JBoss MQ durable subscribers
--- Ken Whitaker [EMAIL PROTECTED] wrote: Using JBoss 3.0.4 and JBossMQ. We have a problem if the durable subscriber client attempts to reconnect after an abnormal connection using the same Client ID, the exception is raised: javax.jms.InvalidClientIDException: This loggedOnClientIds is already registered ! Is it safe to call: public void removeLoggedOnClientId(String ID) on the StateManager instance for a client that has abnormally exited? __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] RE: question about jboss cmp
onsdagen den 29 januari 2003 kl 21.55 skrev Pete Beck: On a side note, I wonder if the SQL parser in the hypersonic codebase could be modified to work on EJBs? :-) Using Hypersonic as a sql-cache front-end to Your DB is possible today with additional trigger classes. torsdagen den 30 januari 2003 kl 17.57 skrev Dain Sundstrom: There are two solutions here: all data is in memory, or we cache query results. Depending on application both scenarios can be done with the above mentioned Hypersonic trigger classes. As Dain points out synchronising the sql-cache front-end and the DB back-end is dependent on the application. 1) one way would be to let all traffic to the DB back-end pass through the sql-cache front-end. 2) another would be to build native notifications from the DB back-end to update the sql-cache front-end. With the current Hypersonic version 1.7.1 it is only recommended for non tx style apps. Then again using 2) one would let the DB back-end with or without JBoss managed tx update the sql-cache front-end ... from the tx able DB back-end. --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] 15.3 MILLION OPT-IN EMAIL ADDRESSES...PLUS $2,000 IN FREE EMAIL MARKETING SOFTWARE!
WOULD YOU LIKE TO HAVE YOUR MESSAGE SEEN BY OVER 15.3 MILLION OPT-IN, TARGETED PROSPECTS DAILY? Below contains all the information you will ever need to market your product or service on the Internet. If you have a product, service, or message that you would like to get out to Thousands, Hundreds of Thousands, or even Millions of people, you have several options. Traditional methods include print advertising, direct mail, radio, and television advertising. They are all effective, but they all have two catches: They're EXPENSIVE and TIME CONSUMING. Not only that, you only get ONE SHOT at making your message heard by the right people. Also, Internet Search Engine Submissions, Classified Ads, Newsgroup Postings simply DO NOT WORK effectively. Now this has all changed! Thanks to the top programmers in the world and their NEW EMAIL TECHNOLOGY, You can send millions of email messages daily for FREE...Without getting terminated from your current Internet connection! It's very simple to do and you can be increasing your sales within minutes of installing this new extraordinary software! Besides...It's the only real way to advertise on the Internet that works...Period! WE WILL SUPPLY YOU WITH OVER 15.3 MILLION OPT-IN EMAIL ADDRESSES TO GET YOU STARTED RIGHT AWAY! PLUS FREE EMAIL ADDRESS DOWNLOADS FOR LIFE! ALSO, YOU WILL RECEIVE $2,000 WORTH OF EMAIL MARKETING SOFTWARE FREE! Including.. BROADCAST EMAIL SENDING SOFTWARE...(send millions of email advertisements daily with a few clicks of your mouse, without getting your ISP trerminated. We used the same software to send you this email) EMAIL EXTRACTION SOFTWARE...(retrieve new targeted email addresses daily. Hundreds of thousands of them) LIST MANAGEMENT SOFTWARE...(keep your lists clean, opt-in and manage all your remove requests, leads, sales etc...) and much...much more! Hurry...This extraordinary offer ends at midnight tonight! To find out more information, Do not respond by email. Instead, click on the link below or copy and paste the exact web site address below into your web browser. http://www.vvorldvvideventures.com/504305/addresses.htm __ Want to be removed from our email list? You were sent this email because you used our Opt-in service. We hope you enjoy reading our messages. However, if you'd rather not receive future e-mails from us, Click on the link below http://www.vvorldvvideventures.com/504305/romove.htm Thank you for your cooperation ___ --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [Xdoclet-user] AW: [JBoss-user] Re: FW: New file structure for xpetstore-3.0 (ba nk ws)
Hi Chris, excellent! It would be great if we could work together on this. I'm sure if JBoss already provides the basic functionality through Axis etc then it should be easy enough to just wrap that behind the 1.4 spec. Wonderful if we could provide the xdoclet tags for it too. I'll take a look at JBoss.net and maybe we can come up with a plan. Brian - Original Message - From: Jung , Dr. Christoph [EMAIL PROTECTED] To: [EMAIL PROTECTED]; James Cooley [EMAIL PROTECTED]; Herve Tchepannou [EMAIL PROTECTED] Cc: xdoclet [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, January 30, 2003 1:41 PM Subject: [Xdoclet-user] AW: [JBoss-user] Re: FW: New file structure for xpetstore-3.0 (ba nk ws) The integration code that puts Axis as a web service deployer into jboss is called jboss.net Currently it uses a proprietary deployment model (web service archive - ..wsr - containing serialisation code and the native Axis wsdd deployment descriptors as meta-data) that is however quite along the lines of rest-J2EE. We have a special xdoclet module for generating wsdd from annotated EJB´s and POJO´s. It is planned to support the J2EE1.4 deployment model until June, I cannot give you any guarantuee on earlier deadlines (since as it looks, I will be the one to implement it and my schedule is quite full). I would be happy to contribute to any 1.4 web service xdoclet module on that way. I would also be happy if we could work together on that issue, since you seem to have the Weblogic experience as well and we would like to be at least as good ;-) Maybe you could already have a look at what is already in jboss.net and maybe start with our proprietary xdoclet/deployment model. Deriving a 1.4 web service annotation and migrating the xpetstore may result in a very simple task, then? CGJ -Ursprüngliche Nachricht- Von: Brian McSweeney [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 30. Januar 2003 13:56 An: James Cooley; Herve Tchepannou Cc: xdoclet; [EMAIL PROTECTED]; [EMAIL PROTECTED] Betreff: [JBoss-user] Re: FW: New file structure for xpetstore-3.0 (bank ws) Hi all, I'm sending this mail to both the jboss-user and xdoclet users lists because although it's with regard to the xpetstore application some questions are based on xdoclet and some on JBoss. Ok, for the next version of xpetstore we're looking at giving an example implementation of a web service. The web service example that Herve has suggested is one to process credit card information. This will be called internally within the xpetstore application. The whole idea of xpetstore is to show how to write container independent apps with xdoclet. It currently supports weblogic and jboss, so while it was suggested that we could write the web service with JBoss' web service (is this called JBoss.net?) it would be really good if we could write it based on J2EE 1.4 and thus try to make it container independent. I know that JBoss 4 will be complient with the J2EE 1.4 spec. and this is meant to be released by June, but are there going to be earlier beta versions that will support this functionality so we can test against it? If so is a time estimate possible? Which leads me to the xdoclet part of the question. We're promoting xdoclet so does it plan to add this 1.4 functionality? If so, at what stage? anyway, thanks very much for your time and any replies. Our previous discussion on this is attached below. Brian PS - As an aside is this how online sites actually do process credit card info? I'm not so sure. Are they moving towards processing via web services? Most people who run online sites I know, store the data and batch process the info via a standard visa machine etc. If however the credit card companies are moving towards web services then I think it's a wonderful idea. Anyone know about this? - Original Message - From: James Cooley [EMAIL PROTECTED] To: Brian McSweeney [EMAIL PROTECTED] Cc: Herve Tchepannou [EMAIL PROTECTED] Sent: Thursday, January 30, 2003 11:52 AM Subject: Re: FW: New file structure for xpetstore-3.0 (bank ws) I think we're reaching a point were it might be better to have these discussions on the dev list - there are probably some lurkers with experience of this out there. Brian McSweeney wrote: I like the structure beneath. It's clear. I have two questions about the bank web service idea. Just on the bank ws - would it not be easier to do a WS to the petstore before getting started on the bank? The petstore has a much richer interface than a cc processing app. Q1: Is there no way to make the session facade itself a web service? Does it have to be via a servlet? If we are going to write the bank app as an ejb, I think it would be nicer to just be able to say - these methods on the session facade are web service enabled. I know that JBoss has JBoss.net which is meant to provide like web services.
[JBoss-user] Re: FW: New file structure for xpetstore-3.0 (bank ws)
Hi all, I'm sending this mail to both the jboss-user and xdoclet users lists because although it's with regard to the xpetstore application some questions are based on xdoclet and some on JBoss. Ok, for the next version of xpetstore we're looking at giving an example implementation of a web service. The web service example that Herve has suggested is one to process credit card information. This will be called internally within the xpetstore application. The whole idea of xpetstore is to show how to write container independent apps with xdoclet. It currently supports weblogic and jboss, so while it was suggested that we could write the web service with JBoss' web service (is this called JBoss.net?) it would be really good if we could write it based on J2EE 1.4 and thus try to make it container independent. I know that JBoss 4 will be complient with the J2EE 1.4 spec. and this is meant to be released by June, but are there going to be earlier beta versions that will support this functionality so we can test against it? If so is a time estimate possible? Which leads me to the xdoclet part of the question. We're promoting xdoclet so does it plan to add this 1.4 functionality? If so, at what stage? anyway, thanks very much for your time and any replies. Our previous discussion on this is attached below. Brian PS - As an aside is this how online sites actually do process credit card info? I'm not so sure. Are they moving towards processing via web services? Most people who run online sites I know, store the data and batch process the info via a standard visa machine etc. If however the credit card companies are moving towards web services then I think it's a wonderful idea. Anyone know about this? - Original Message - From: James Cooley [EMAIL PROTECTED] To: Brian McSweeney [EMAIL PROTECTED] Cc: Herve Tchepannou [EMAIL PROTECTED] Sent: Thursday, January 30, 2003 11:52 AM Subject: Re: FW: New file structure for xpetstore-3.0 (bank ws) I think we're reaching a point were it might be better to have these discussions on the dev list - there are probably some lurkers with experience of this out there. Brian McSweeney wrote: I like the structure beneath. It's clear. I have two questions about the bank web service idea. Just on the bank ws - would it not be easier to do a WS to the petstore before getting started on the bank? The petstore has a much richer interface than a cc processing app. Q1: Is there no way to make the session facade itself a web service? Does it have to be via a servlet? If we are going to write the bank app as an ejb, I think it would be nicer to just be able to say - these methods on the session facade are web service enabled. I know that JBoss has JBoss.net which is meant to provide like web services. I'm not sure how this works but we could check it out. I played around with Axis and it's trivial to create a WS using it - there are some sample apps with it. It can create all the descriptors for you. JBoss uses Axis so I guess it should be easy. Also, I know that the new version of the J2EE 1.4 spec is supposed to support web services. If you read the tutorial on the new web service technology introduced in j2ee 1.4 there are two ways to create web services - via servlets and via stateless session beans: http://java.sun.com/j2ee/1.4/docs/tutorial/doc/NewEJB3.html#80672 A Web service client can access J2EE applications in two ways. First, the client can access a Web service created with JAX-RPC. Behind the scenes, JAX-RPC uses a servlet to implement the Web service. Second, a Web service client can access a stateless session bean through its Web service endpoint interface. Other types of enterprise beans cannot be accessed by Web service clients. I think coding to this spec would be excellent. We could be one of the first groups to provide an example implementation of an app using the new new spec. Opinions? Sounds good. Do any of the containers support 1.4 yet? I suppose we're promoting xdoclet so does it plan to add this 1.4 functionality? Q2: Not as important, is this how online sites actually do process credit card info? I'm not so sure. Are they moving towards processing via web services? Most people who run online sites I know, store the data and batch process the info via a standard visa machine etc. If however the credit card companies are moving towards web services then I think it's a wonderful idea. I don't know but Struts form validation has an algorithm to check if a cc is valid which is probably as far so most retailers go on-line. The batch idea sounds about right. Brian Herve wrote: For simplification purpose, we can change the structure like this: xpetstore | +--DIR doc +--DIR lib +--DIR src | +--DIRant | | | +-- build.xml | +--
AW: [JBoss-user] Re: FW: New file structure for xpetstore-3.0 (bank ws)
The integration code that puts Axis as a web service deployer into jboss is called jboss.net Currently it uses a proprietary deployment model (web service archive - ..wsr - containing serialisation code and the native Axis wsdd deployment descriptors as meta-data) that is however quite along the lines of rest-J2EE. We have a special xdoclet module for generating wsdd from annotated EJB´s and POJO´s. It is planned to support the J2EE1.4 deployment model until June, I cannot give you any guarantuee on earlier deadlines (since as it looks, I will be the one to implement it and my schedule is quite full). I would be happy to contribute to any 1.4 web service xdoclet module on that way. I would also be happy if we could work together on that issue, since you seem to have the Weblogic experience as well and we would like to be at least as good ;-) Maybe you could already have a look at what is already in jboss.net and maybe start with our proprietary xdoclet/deployment model. Deriving a 1.4 web service annotation and migrating the xpetstore may result in a very simple task, then? CGJ -Ursprüngliche Nachricht- Von: Brian McSweeney [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 30. Januar 2003 13:56 An: James Cooley; Herve Tchepannou Cc: xdoclet; [EMAIL PROTECTED]; [EMAIL PROTECTED] Betreff: [JBoss-user] Re: FW: New file structure for xpetstore-3.0 (bank ws) Hi all, I'm sending this mail to both the jboss-user and xdoclet users lists because although it's with regard to the xpetstore application some questions are based on xdoclet and some on JBoss. Ok, for the next version of xpetstore we're looking at giving an example implementation of a web service. The web service example that Herve has suggested is one to process credit card information. This will be called internally within the xpetstore application. The whole idea of xpetstore is to show how to write container independent apps with xdoclet. It currently supports weblogic and jboss, so while it was suggested that we could write the web service with JBoss' web service (is this called JBoss.net?) it would be really good if we could write it based on J2EE 1.4 and thus try to make it container independent. I know that JBoss 4 will be complient with the J2EE 1.4 spec. and this is meant to be released by June, but are there going to be earlier beta versions that will support this functionality so we can test against it? If so is a time estimate possible? Which leads me to the xdoclet part of the question. We're promoting xdoclet so does it plan to add this 1.4 functionality? If so, at what stage? anyway, thanks very much for your time and any replies. Our previous discussion on this is attached below. Brian PS - As an aside is this how online sites actually do process credit card info? I'm not so sure. Are they moving towards processing via web services? Most people who run online sites I know, store the data and batch process the info via a standard visa machine etc. If however the credit card companies are moving towards web services then I think it's a wonderful idea. Anyone know about this? - Original Message - From: James Cooley [EMAIL PROTECTED] To: Brian McSweeney [EMAIL PROTECTED] Cc: Herve Tchepannou [EMAIL PROTECTED] Sent: Thursday, January 30, 2003 11:52 AM Subject: Re: FW: New file structure for xpetstore-3.0 (bank ws) I think we're reaching a point were it might be better to have these discussions on the dev list - there are probably some lurkers with experience of this out there. Brian McSweeney wrote: I like the structure beneath. It's clear. I have two questions about the bank web service idea. Just on the bank ws - would it not be easier to do a WS to the petstore before getting started on the bank? The petstore has a much richer interface than a cc processing app. Q1: Is there no way to make the session facade itself a web service? Does it have to be via a servlet? If we are going to write the bank app as an ejb, I think it would be nicer to just be able to say - these methods on the session facade are web service enabled. I know that JBoss has JBoss.net which is meant to provide like web services. I'm not sure how this works but we could check it out. I played around with Axis and it's trivial to create a WS using it - there are some sample apps with it. It can create all the descriptors for you. JBoss uses Axis so I guess it should be easy. Also, I know that the new version of the J2EE 1.4 spec is supposed to support web services. If you read the tutorial on the new web service technology introduced in j2ee 1.4 there are two ways to create web services - via servlets and via stateless session beans: http://java.sun.com/j2ee/1.4/docs/tutorial/doc/NewEJB3.html#80672 A Web service client can access J2EE applications in two ways. First, the client can access a Web service created with JAX-RPC. Behind the scenes, JAX-RPC uses a servlet
