[JBoss-dev] [Design of JBoss Internal Benchmarking] - Re: Internal errors in JBoss 3.2.6 with SpecjAppServer 2002
Change type mapping for java.lang.Short in Oracle9i mapping to the commented one. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3858988#3858988 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3858988 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] What are these XniJBossXBParser warnings?
I should have fixed this yesterday by logging this in TRACE. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott M Stark Sent: Monday, December 13, 2004 8:06 PM To: [EMAIL PROTECTED] Subject: [JBoss-dev] What are these XniJBossXBParser warnings? An update of my jboss-head workspace has started producing a flood of warning messages when parsing the rar metadata. Why is this? 11:02:00,375 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/C:/cvs/JBossHead/jboss-head/build/output/jboss-5.0.0alph a/server/d efault/deploy/jboss-local-jdbc.rar 11:02:00,156 WARN [XniJBossXBParser] Type is not available for connector 11:02:00,187 WARN [XniJBossXBParser] Type is not available for description 11:02:00,203 WARN [XniJBossXBParser] Type is not available for display-name 11:02:00,203 WARN [XniJBossXBParser] Type is not available for vendor-name 11:02:00,203 WARN [XniJBossXBParser] Type is not available for eis-type 11:02:00,203 WARN [XniJBossXBParser] Type is not available for resourceadapter-version 11:02:00,218 WARN [XniJBossXBParser] Type is not available for license 11:02:00,218 WARN [XniJBossXBParser] Type is not available for description 11:02:00,218 WARN [XniJBossXBParser] Type is not available for license-required 11:02:00,218 WARN [XniJBossXBParser] Type is not available for resourceadapter 11:02:00,218 WARN [XniJBossXBParser] Type is not available for resourceadapter-class 11:02:00,218 WARN [XniJBossXBParser] Type is not available for outbound-resourceadapter 11:02:00,218 WARN [XniJBossXBParser] Type is not available for connection-definition 11:02:00,234 WARN [XniJBossXBParser] Type is not available for managedconnectionfactory-class 11:02:00,234 WARN [XniJBossXBParser] Type is not available for config-property 11:02:00,234 WARN [XniJBossXBParser] Type is not available for description 11:02:00,234 WARN [XniJBossXBParser] Type is not available for config-property-name 11:02:00,234 WARN [XniJBossXBParser] Type is not available for config-property-type 11:02:00,234 WARN [XniJBossXBParser] Type is not available for config-property 11:02:00,234 WARN [XniJBossXBParser] Type is not available for description Scott Stark Chief Technology Officer JBoss Inc. --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss's Web Services Implementation] - Re: JBossWS getting involved
Yes, thats the way to do it. I'll look into it and do the delegation from the TypeMapping associated JAXRPC Serializers/Deserializers. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3858991#3858991 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3858991 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JMS on JBoss (JMS/JBoss)] - Configuration of JMS on JBoss
Hi,
We are having the following error when we try to communicate to Jboss 4.0 via
JNDI. Here is my code. Can anybody help me out with this ?
public SimpleSender() {
try {
QueueConnectionFactory myQConnFactory;
Queue myQueue;
Properties properties = new Properties();
properties.put(Context.INITIAL_CONTEXT_FACTORY,org.jnp.interfaces.NamingContextFactory);
properties.put(Context.URL_PKG_PREFIXES,org.jboss.naming:org.jnp.interfaces);
properties.put(Context.PROVIDER_URL,jnp://localhost:1099);
Context ctx = new InitialContext(properties);
myQConnFactory = (QueueConnectionFactory)
ctx.lookup(java:/ConnectionFactory);
myQueue = (Queue) ctx.lookup(queue/testQueue);
ctx.bind(SimpleSender,myQueue);
QueueConnection con =
myQConnFactory.createQueueConnection();
QueueSession session =
con.createQueueSession(false,Session.AUTO_ACKNOWLEDGE);
TextMessage textMessage = session.createTextMessage();
QueueSender sender = session.createSender(myQueue);
con.start();
for(int i=0;i10;i++){
textMessage.setText(Hello World + i );
sender.send(textMessage);
}
con.close();
ctx.close();
} catch(Exception ex) {
ex.printStackTrace() ;
}
}
Is there anything that I missing out.
Jagdish
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3858992#3858992
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3858992
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JMS on JBoss (JMS/JBoss)] - Re: Configuration of JMS on JBoss
Hi, The error that I am getting is as follows javax.naming.NameNotFoundException: ConnectionFactory not bound at org.jnp.server.NamingServer.getBinding(NamingServer.java:495) at org.jnp.server.NamingServer.getBinding(NamingServer.java:503) at org.jnp.server.NamingServer.getObject(NamingServer.java:509) at org.jnp.server.NamingServer.lookup(NamingServer.java:282) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:529) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:508) at javax.naming.InitialContext.lookup(InitialContext.java:347) at SimpleSender.(SimpleSender.java:49) at SimpleSender.main(SimpleSender.java:24) View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3858993#3858993 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3858993 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - Re: jboss aop on websphere
There are two parts to this, getting the classloader to intercept the calls to defineClass0 and getting AOP to work with any classloader setup. The first one is easy, just a simple modification to the code that instruments the classloader should do it. The second one involves a change to the way that the AOP code uses javassist, requiring recursive calls to the classloader (and therefore instrumentation). This will not work with the 1.5 instrumentation as it filters out recursive calls, a very restrictive decision on Sun's part (IMHO). The AOP code actually has a thread local flag added so that the instrumented classloader works the same way as the 1.5 instrumentation, preventing recursive calls. The following is based on my current understanding and could be wrong! The code currently works by intercepting a classloader call to instrument a class and, from that point on, the instrumentation classloading hierarchy is driven by javassist. The AOP code uses javassist to load the class information for superclasses, interfaces etc. based on what javassist believes the hierarchy to be. A mismatch in this and things could possibly go wrong. What I would like to do is throw this back to the calling classloader and allow it to dictate the hierarchy, obviously involving a recursive call to the classloader :-(. I will make the classloader instrumentation change to allow you to use it with the IBM VM, you could try and see if it is sufficient to let you get something working. Which java version are you using? Kev View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3858997#3858997 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3858997 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of Clustering on JBoss (Clusters/JBoss)] - XAConnectionFactory not bound
Hi, I know this is not quite the place to post this, but helping me wil certainly benefit jboss. Currently I am working on aproject for comparing the paerformance of JBoss compared to a major commercial appserver and another freshly developed commercial appserver in a clustered environment of about 8 Nodes a load balancer and a database-server. I have to say that I'm impressed wit JBoss' single-node results and am planing to add a SPECjAppServer2004 wiki-page presenting my results (anonymized). When trying to setup the Jboss cluster I dont seem to get the JMS using Oracle-XA datasource working. All nodes in my cluster are identical. When I start the first node everything is fine. When I start the second everything is fine. After that, every node (except the current master JMS server) started before the new node shows XAConnectionFactory not bound exceptions. Only the first two nodes can operate correctly. Any hints? I'm sort of desperate, since my deadline is coming nearer and I haven't started doing real cluster benchmarking yet. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3858998#3858998 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3858998 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of Mail Services] - What is the current status of the JBossMail server?
Hello, I like the idea of the JBossMail server. What is the current status of the JBossMail server? Is it already possible to use SMTP and IMAP? Regards, Roland Beuker View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3859013#3859013 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859013 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss's Web Services Implementation] - Re: JBossWS Streaming Implementation Proposal
Are you talking about JAXB2 here? Where can I find the info about JAXBContext using XMLStreamingReader? Thanks. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3859016#3859016 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859016 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-3.2 build.223 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2?log=log20041217055249Lbuild.223 BUILD COMPLETE-build.223Date of build:12/17/2004 05:52:49Time to build:23 minutes 44 secondsLast changed:12/17/2004 05:41:21Last log entry:Remove dependency of one-test on maybejars Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(1)1.165.2.174modifiedtdieslertestsuite/build.xmlRemove dependency of one-test on maybejars
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - Re: Methods via Reflection and MBean interception
From: http://docs.jboss.org/aop/aspect-framework/reference/en/html/reflection.html#reflection-attach-chains anonymous wrote : Intereptors/aspects bound to exexcution pointcuts for fields and constructors don't get invoked. Could you please let us know where the discrepancies are? Anyway this is correct : anonymous wrote : | To my mind, the method interception was the only that wouldn't cause bytecode transformation on the caller classes, due to the called class could have the original method renamed and replaced by a new one, that would fire the interceptions, so methods executed via Reflection would be intercepted if set up so. Regarding interceptions of field reads in MBeans, I have not yet tried. I will try to take a look over the next week or so. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3859018#3859018 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859018 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] [Web Services] - JBossWS / JAXB integration
Since the link to the post is broken in the forums I am emailing my comments. Thomas, you seem to go back to the design you had before our discussion in Neuchatel. Why? What JAXB version are you going to use? JAXB2 is not yet released and API is not available yet, AFAIK. JAXB1 seems to complicate your design. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, December 14, 2004 8:28 PM To: [EMAIL PROTECTED] Subject: [JBoss-dev] [Web Services] - JBossWS / JAXB integration JBossWS / JAXB integration -- A SOAP envelope targeted to JBossWS or emitted from JBossWS can either be of RPC or DOCUMENT style. The encoding is always literal. DOCUMENT style -- | soap:Envelope | soap:Header + | header-element * | /soap:Header | soap:Body | single-document-element | /soap:Body | /soap:Envelope | The body contains a single complex element, which is completely defined in XML schema. The optional header elements may be simple or complex types. In case of a complex type, it must be defined in schema. Here is an example | soap:Envelope | soap:Header | tns:SimpleHeader123456/tns:SimpleHeader | tns:ComplexHeader | nameTom/name | age3/age | /tns:ComplexHeader | /soap:Header | soap:Body | tns:PurchaseOrder | itemFerrari/item | address | streetWall Street 102/street | cityNew York/city | /address | /tns:PurchaseOrder | /soap:Body | /soap:Envelope | The corresponding schema may look as follows | schema | complexType name=ComplexHeaderType | sequence | element name=name type=xsd:string/ | element name=age type=xsd:int/ | /sequence | /complexType | element name=ComplexHeader type=tns:ComplexHeaderType | | complexType name=PurchaseOrderType | sequence | element name=item type=xsd:string/ | element name=address | complexType | sequence | element name=street type=xsd:string/ | element name=city type=xsd:string/ | /sequence | /complexType | /element | /sequence | /complexType | element name=PurchaseOrder type=tns:PurchaseOrderType | schema | Note, the schema does not contain a definition for tns:SimpleHeader/ which would be defined in the WSDL. The JAXB marshalling layer can only unmarshall the xml fragments that are defined in schema. The other fragments must be handled in the JBossWS layer, which is WSDL aware. RPC style - | soap:Envelope | soap:Header + | header-element * | /soap:Header | soap:Body | rpc-wrapper-element | rpc-parameter * | /rpc-wrapper-element | /soap:Body | /soap:Envelope | The body contains a RPC wrapper element, which indentifies the RPC operation. Optional child elements of the rpc-wrapper-element may be simple or complex types. In case of a complex type, it must be defined in schema. The optional header elements may be simple or complex types. In case of a complex type, it must be defined in schema. Here is an example | soap:Envelope | soap:Header | tns:SimpleHeader123456/tns:SimpleHeader | tns:ComplexHeader | nameTom/name | age3/age | /tns:ComplexHeader | /soap:Header | soap:Body | tns:PurchaseOrder | tns:itemFerrari/tns:item | tns:address | streetWall Street 102/street | cityNew York/city | /tns:address | /tns:PurchaseOrder | /soap:Body | /soap:Envelope | The corresponding schema may look as follows | schema | complexType name=ComplexHeaderType | sequence | element name=name type=xsd:string/ | element name=age type=xsd:int/ | /sequence | /complexType | element name=ComplexHeader type=tns:ComplexHeaderType | | complexType name=AddressType | sequence | element name=street type=xsd:string/ |element name=city type=xsd:string/ | /sequence | /complexType | element name=address type=tns:AddressType | schema | Note, the schema does not contain a definition for tns:SimpleHeader/ nor tns:PurchaseOrder/ nor tns:item These would be defined in the WSDL. The JAXB marshalling layer can only unmarshall the xml fragments that are defined in schema. The other fragments must be handled in the JBossWS layer, which is WSDL aware. SOAPContentElement -- The SAAJ API offers a DOM based object view of the SOAP envelope. For this dicussion we look at the following interfaces SOAPEnvelope, SOAPHeader,
[JBoss-dev] [JBossWS] - Re: document/literal wrapped and jbossws / jbossDotNet
Hi, I have been investigating using jboss-saaj and am fairly happy with this. I notice that with JAXM, there is a JAXMServlet and ReqRespListener class. Can you confirm whether it would be wise to use JAXM with JBoss and whether I can simply drop the two JAXM jar files into the jboss server/lib? I can just use saaj within an ordinary servlet, but I like the idea of JAXM albeit that I heard it was not favoured by IBM and others. Also, I am aiming to use jdom for XML processing - is this good practice for jboss or is it preferred to use dom4j, which ships with jboss? One final question, does jboss 4.0.0 allow you to add jdom.jar etc to the ear file? I have tried using a manifest with Class-Path, but the Classloader cannot find it. Thanks in advance, Peter View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3859022#3859022 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859022 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-14) CompleteUnitTestCase fails under java5
[ http://jira.jboss.com/jira/browse/JBAS-14?page=comments#action_12310868 ] Alex Loubyansky commented on JBAS-14: - These tests are bad as they report failures when generated queries are in fact correct from the data fetching point of view. The problem is that you can't predict the exact order of a sequence of conjunctions/disjunctions in the WHERE clause, tables in the FROM clause, etc. So, in general, if these tests pass it's a luck. CompleteUnitTestCase fails under java5 -- Key: JBAS-14 URL: http://jira.jboss.com/jira/browse/JBAS-14 Project: JBoss Application Server Type: Bug Versions: JBossAS-4.0.1 Final Environment: 13:35:08,406 INFO [Server] Starting JBoss (MX MicroKernel)... 13:35:08,406 INFO [Server] Release ID: JBoss [Zion] 4.0.1RC2 (build: CVSTag=Branch_4_0 date=200411271821) 13:35:08,406 INFO [Server] Home Dir: C:\cvs\JBoss4.0\jboss-4.0\build\output\jboss-4.0.1RC2 13:35:08,406 INFO [Server] Home URL: file:/C:/cvs/JBoss4.0/jboss-4.0/build/output/jboss-4.0.1RC2/ 13:35:08,406 INFO [Server] Library URL: file:/C:/cvs/JBoss4.0/jboss-4.0/build/output/jboss-4.0.1RC2/lib/ 13:35:08,406 INFO [Server] Patch URL: null 13:35:08,406 INFO [Server] Server Name: all 13:35:08,406 INFO [Server] Server Home Dir: C:\cvs\JBoss4.0\jboss-4.0\build\output\jboss-4.0.1RC2\server\all 13:35:08,421 INFO [Server] Server Home URL: file:/C:/cvs/JBoss4.0/jboss-4.0/build/output/jboss-4.0.1RC2/server/all/ 13:35:08,421 INFO [Server] Server Data Dir: C:\cvs\JBoss4.0\jboss-4.0\build\output\jboss-4.0.1RC2\server\all\data 13:35:08,421 INFO [Server] Server Temp Dir: C:\cvs\JBoss4.0\jboss-4.0\build\output\jboss-4.0.1RC2\server\all\tmp 13:35:08,421 INFO [Server] Server Config URL: file:/C:/cvs/JBoss4.0/jboss-4.0/build/output/jboss-4.0.1RC2/server/all/conf/ 13:35:08,421 INFO [Server] Server Library URL: file:/C:/cvs/JBoss4.0/jboss-4.0/build/output/jboss-4.0.1RC2/server/all/lib/ 13:35:08,421 INFO [Server] Root Deployment Filename: jboss-service.xml 13:35:08,421 INFO [Server] Starting General Purpose Architecture (GPA)... 13:35:08,937 INFO [ServerInfo] Java version: 1.5.0,Sun Microsystems Inc. 13:35:08,937 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0-b64,Sun Microsystems Inc. 13:35:08,937 INFO [ServerInfo] OS-System: Windows XP 5.1,x86 Reporter: Scott M Stark Assignee: Alex Loubyansky When running the org.jboss.test.cmp2.commerce.CompleteUnitTestCase test under java5 there are two failures related to query expecation failures: Suite: org.jboss.test.cmp2.commerce.CompleteUnitTestCase Test:testJBossQL Type:failure Exception: net.sourceforge.junitejb.RemoteAssertionFailedError Message: Expected: SELECT t0_o1.ORDER_NUMBER FROM ORDER_DATA t0_o1, ORDER_DATA t3_o2, CUSTOMEREJB t1_o1_customer, CUSTOMEREJB t2_o2_customer WHERE (( NOT (t1_o1_customer.id=t2_o2_customer.id)) AND (t0_o1.CC_TYPE=t3_o2.CC_TYPE AND t0_o1.CC_FIRST_NAME=t3_o2.CC_FIRST_NAME AND t0_o1.CC_MI=t3_o2.CC_MI AND t0_o1.CC_LAST_NAME=t3_o2.CC_LAST_NAME AND t0_o1.CC_BILLING_ZIP=t3_o2.CC_BILLING_ZIP AND t0_o1.CC_CARD_NUMBER=t3_o2.CC_CARD_NUMBER) AND t0_o1.customer=t1_o1_customer.id AND t3_o2.customer=t2_o2_customer.id) but got: SELECT t0_o1.ORDER_NUMBER FROM ORDER_DATA t0_o1, ORDER_DATA t3_o2, CUSTOMEREJB t2_o2_customer, CUSTOMEREJB t1_o1_customer WHERE (( NOT (t1_o1_customer.id=t2_o2_customer.id)) AND (t0_o1.CC_TYPE=t3_o2.CC_TYPE AND t0_o1.CC_FIRST_NAME=t3_o2.CC_FIRST_NAME AND t0_o1.CC_MI=t3_o2.CC_MI AND t0_o1.CC_LAST_NAME=t3_o2.CC_LAST_NAME AND t0_o1.CC_BILLING_ZIP=t3_o2.CC_BILLING_ZIP AND t0_o1.CC_CARD_NUMBER=t3_o2.CC_CARD_NUMBER) AND t3_o2.customer=t2_o2_customer.id AND t0_o1.customer=t1_o1_customer.id) - Suite: org.jboss.test.cmp2.commerce.CompleteUnitTestCase Test:testEJBQL Type:failure Exception: net.sourceforge.junitejb.RemoteAssertionFailedError Message: expected:...0_o.ORDER_NUMBER=t4_l.ORDER_NUMBER AND t6_l_product.id=t5_l_product_productCategories_R.PRODUCT_ID AND t1_pc.id=t5_l_product_productCategories_R.PRODUCT_CATEGORY_ID AND t1_pc.subId=t5_l_product_productCategories_R.PRODUCT_CATEGORY_SUBID AND t4_l.product=t6_l_product.id but was:...6_l_product.id=t5_l_product_productCategories_R.PRODUCT_ID AND t1_pc.id=t5_l_product_productCategories_R.PRODUCT_CATEGORY_ID AND t1_pc.subId=t5_l_product_productCategories_R.PRODUCT_CATEGORY_SUBID AND t4_l.product=t6_l_product.id AND t0_o.ORDER_NUMBER=t4_l.ORDER_NUMBER - -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - Re: Methods via Reflection and MBean interception
Now, I'm intruding here from another forum :) You can apply interceptors to MBeans (either statically or dynamically) by wrapping the MBean with an XMBean descriptor. Those interceptors come from the JBossMX framework (nothing to do with the AOP framework), so they are old style ones (no bytecode magic whatsoever), and they let you intercept JMX operations and attribute get/sets. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3859025#3859025 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859025 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossWS] - jboss-saaj attachmentpart problem
Hi, I'm using jboss 4.0.0. and am having problems with attachments when using saaj. The only success I have is if I attach using MIME type text/plain and set content to a String. If I try to set MIME type to application/xml or text/xml and set content to be JDOMSource then I get IllegalArgument exception: If I try to set MIME type to application/xml or text/xml and set content to javax.xml.transform.stream.StreamSource then I get null pointer exception : anonymous wrote : 13:40:03,032 ERROR [EBXMLTransportActivatorBean] java.lang.NullPointerException | 13:40:03,032 INFO [STDOUT] java.lang.NullPointerException | 13:40:03,042 INFO [STDOUT] at org.apache.axis.attachments.ManagedMemoryData | Source.(ManagedMemoryDataSource.java:202) | 13:40:03,042 INFO [STDOUT] at org.apache.axis.attachments.AttachmentPartImp | l.setContent(AttachmentPartImpl.java:491) anonymous wrote : 13:47:57,683 ERROR [EBXMLTransportActivatorBean] java.lang.IllegalArgumentExcep | ion: Cannot content type 'text/xml' for: [EMAIL PROTECTED] | 13:47:57,723 INFO [STDOUT] java.lang.IllegalArgumentException: Cannot content | ype 'text/xml' for: [EMAIL PROTECTED] | 13:47:57,763 INFO [STDOUT] at org.apache.axis.attachments.AttachmentPartIm | l.setContent(AttachmentPartImpl.java:486) I would gratefully appreciate it if someone has some experience to offer on adding a StreamSource as an attachment with jboss-saaj. Thanks. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3859030#3859030 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859030 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossWS] - Re: jboss-saaj attachmentpart problem
Does this relate to https://sourceforge.net/tracker/?func=detailatid=376685aid=1039881group_id=22866? If so, is when will able stable version of 4.0.1 be available? Thanks View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3859033#3859033 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859033 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss Portal Development] - Re: Deploy Jetspeed2 on JBoss problem
Maybe you should try the jetspeed mailing list? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3859035#3859035 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859035 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossWS] - Re: jboss-saaj attachmentpart problem
Okay, I have a solution. I was using: | AttachmentPart attachmentPart = message.createAttachmentPart(); | attachmentPart.setContentId(payload-1); | attachmentPart.setMimeHeader(Content-Type, text/xml); | attachmentPart.setContent(new JDOMSource(document), text/xml); | message.addAttachmentPart(attachmentPart); Now I am successfully using: | org.jdom.Document document = new Document(); | document.setRootElement(new org.jdom.Element(PayloadTest)); | javax.activation.DataHandler handler = new javax.activation.DataHandler(new JDOMSource(document), text/xml); | AttachmentPart attachmentPart = message.createAttachmentPart(handler); | attachmentPart.setContentId(payload-1); | attachmentPart.setMimeHeader(Content-Type, text/xml); | I guess it must be the DataHandlers in use by Axis? If anyone has an explanation, I would like to know! View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3859041#3859041 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859041 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss's Web Services Implementation] - Re: JBossWS Streaming Implementation Proposal
[EMAIL PROTECTED] wrote : Are you talking about JAXB2 here? Where can I find the info about JAXBContext using XMLStreamingReader? | Thanks. Yes JAXB2. If you look at the EDR javadoc, the Marshaller/Unmarshaller interfaces which are pulled from the JAXBContext, have overloaded marshall, and unmarshall methods which support both XMLStreamReader/XMLStreamWriter and XMLEvenetReader/XMLEventWriter. Here is an unmarshalling example using the stream reader | XMLStreamReader xmlStreamReader = | XMLInputFactory().newInstance().createXMLStreamReader( ... ); | JAXBContext jc = JAXBContext.newInstance( com.acme.foo ); | Unmarshaller u = jc.createUnmarshaller(); | Object o = u.unmarshal( xmlStreamReader ); | And here is a marshalling example | ComplexObject obj = ...; | XMLStreamWriter xmlStreamWriter = |XMLOutputFactory.newInstance().createXMLStreamWriter( ... ); | JAXBContext jc = JAXBContext.newInstance( com.acme.foo ); | Marshaller m = jc.createMarshaller(); | m.marshal( obj, xmlStreamWriter ); | Thanks, -Jason View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3859042#3859042 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859042 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss's Web Services Implementation] - Re: JBossWS Streaming Implementation Proposal
Also, they claify the pulling/pushing behavior in the javadoc, which correpsonds with my design proposal. From the javadoc: | unmarshal | | java.lang.Object unmarshal(javax.xml.stream.XMLStreamReader reader) |throws JAXBException | | Unmarshal XML data from the specified pull parser and return the resulting content tree. | | This method assumes that the parser is at a start element event, and the unmarshalling will be done from this start element to the corresponding end element. If this method returns successfully, the reader will be pointing at the token right after the end element. | Thanks, -Jason View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3859044#3859044 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859044 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss's Web Services Implementation] - Re: JBossWS Streaming Implementation Proposal
Hi Jason, What you describe here is the transition from | InputStream - StAX - JAXRPC Deserializer - Java Object | Let me rehears what we've currently got: Fragment incomming XML message (done in MessageFactory.createMessage()) and create a flat SAAJ view Document Style -- SOAPEnvelope SOAPHeader SOAPHeaderElement (SOAPContentElement that holds a fragment) SOAPBody SOAPBodyElement (SOAPContentElement that holds a fragment) RPC Style - SOAPEnvelope SOAPHeader SOAPHeaderElement (SOAPContentElement that holds a fragment) SOAPBody SOAPBodyElement (RPC element) SOAPElement (SOAPContentElement that holds a fragment) SAAJ at this level is perfect to describe the structure of the SOAP message. It starts to be less perfect the deeper you go down the tree forcing the DOM view onto the user. The important bit is, to allow to go forth and back between the XML and Java Object representation at the SOAPContentElement level using the JAXRPC serializer/deserializers. Whether to hold the XML representation as String or StAX events is an (important) implementation detail. So how about this: MessageFactory.createMessage builds the SAAJ view as above with SOAPContentElement(s). Upon END_ELEMENT the SOAPContentElement passes the event stream to the deserializer which constructs the java objects and assigns it to the SOAPContentElement. If we don't have handlers the java object passes unmodified the endpoint. In case we have handlers that modify the content we can alway go back to the DOM view of the content using the corresponding serializer. That should account for the majority of use cases and we don't hold a second (xmlFragment) copy of the content. As you point out correctly, we take the hit if the handler (or endpoint) is stupid enough to require a DOM view of the content. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3859051#3859051 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859051 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss's Web Services Implementation] - Re: JBossWS Streaming Implementation Proposal
Jason, this all makes sence. I think you should go ahead and change the
signature of
| public abstract class DeserializerBase implements Deserializer
| {
|public abstract Object deserialize(QName xmlName, QName xmlType, String
xmlFragment, SerializationContextImpl serContext)
| }
|
with
| public abstract class DeserializerBase implements Deserializer
| {
|public abstract Object deserialize(QName xmlName, QName xmlType,
XMLStreamReader reader, SerializationContextImpl serContext)
| }
|
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3859055#3859055
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859055
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBAS-14) CompleteUnitTestCase fails under java5
[ http://jira.jboss.com/jira/browse/JBAS-14?page=history ] Scott M Stark resolved JBAS-14: --- Resolution: Done Fix Version: JBossAS-4.0.1 Final Ok, I just disabled the exact string assertions and log a message to stderr if the match does not exist. CompleteUnitTestCase fails under java5 -- Key: JBAS-14 URL: http://jira.jboss.com/jira/browse/JBAS-14 Project: JBoss Application Server Type: Bug Versions: JBossAS-4.0.1 Final Environment: 13:35:08,406 INFO [Server] Starting JBoss (MX MicroKernel)... 13:35:08,406 INFO [Server] Release ID: JBoss [Zion] 4.0.1RC2 (build: CVSTag=Branch_4_0 date=200411271821) 13:35:08,406 INFO [Server] Home Dir: C:\cvs\JBoss4.0\jboss-4.0\build\output\jboss-4.0.1RC2 13:35:08,406 INFO [Server] Home URL: file:/C:/cvs/JBoss4.0/jboss-4.0/build/output/jboss-4.0.1RC2/ 13:35:08,406 INFO [Server] Library URL: file:/C:/cvs/JBoss4.0/jboss-4.0/build/output/jboss-4.0.1RC2/lib/ 13:35:08,406 INFO [Server] Patch URL: null 13:35:08,406 INFO [Server] Server Name: all 13:35:08,406 INFO [Server] Server Home Dir: C:\cvs\JBoss4.0\jboss-4.0\build\output\jboss-4.0.1RC2\server\all 13:35:08,421 INFO [Server] Server Home URL: file:/C:/cvs/JBoss4.0/jboss-4.0/build/output/jboss-4.0.1RC2/server/all/ 13:35:08,421 INFO [Server] Server Data Dir: C:\cvs\JBoss4.0\jboss-4.0\build\output\jboss-4.0.1RC2\server\all\data 13:35:08,421 INFO [Server] Server Temp Dir: C:\cvs\JBoss4.0\jboss-4.0\build\output\jboss-4.0.1RC2\server\all\tmp 13:35:08,421 INFO [Server] Server Config URL: file:/C:/cvs/JBoss4.0/jboss-4.0/build/output/jboss-4.0.1RC2/server/all/conf/ 13:35:08,421 INFO [Server] Server Library URL: file:/C:/cvs/JBoss4.0/jboss-4.0/build/output/jboss-4.0.1RC2/server/all/lib/ 13:35:08,421 INFO [Server] Root Deployment Filename: jboss-service.xml 13:35:08,421 INFO [Server] Starting General Purpose Architecture (GPA)... 13:35:08,937 INFO [ServerInfo] Java version: 1.5.0,Sun Microsystems Inc. 13:35:08,937 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0-b64,Sun Microsystems Inc. 13:35:08,937 INFO [ServerInfo] OS-System: Windows XP 5.1,x86 Reporter: Scott M Stark Assignee: Alex Loubyansky Fix For: JBossAS-4.0.1 Final When running the org.jboss.test.cmp2.commerce.CompleteUnitTestCase test under java5 there are two failures related to query expecation failures: Suite: org.jboss.test.cmp2.commerce.CompleteUnitTestCase Test:testJBossQL Type:failure Exception: net.sourceforge.junitejb.RemoteAssertionFailedError Message: Expected: SELECT t0_o1.ORDER_NUMBER FROM ORDER_DATA t0_o1, ORDER_DATA t3_o2, CUSTOMEREJB t1_o1_customer, CUSTOMEREJB t2_o2_customer WHERE (( NOT (t1_o1_customer.id=t2_o2_customer.id)) AND (t0_o1.CC_TYPE=t3_o2.CC_TYPE AND t0_o1.CC_FIRST_NAME=t3_o2.CC_FIRST_NAME AND t0_o1.CC_MI=t3_o2.CC_MI AND t0_o1.CC_LAST_NAME=t3_o2.CC_LAST_NAME AND t0_o1.CC_BILLING_ZIP=t3_o2.CC_BILLING_ZIP AND t0_o1.CC_CARD_NUMBER=t3_o2.CC_CARD_NUMBER) AND t0_o1.customer=t1_o1_customer.id AND t3_o2.customer=t2_o2_customer.id) but got: SELECT t0_o1.ORDER_NUMBER FROM ORDER_DATA t0_o1, ORDER_DATA t3_o2, CUSTOMEREJB t2_o2_customer, CUSTOMEREJB t1_o1_customer WHERE (( NOT (t1_o1_customer.id=t2_o2_customer.id)) AND (t0_o1.CC_TYPE=t3_o2.CC_TYPE AND t0_o1.CC_FIRST_NAME=t3_o2.CC_FIRST_NAME AND t0_o1.CC_MI=t3_o2.CC_MI AND t0_o1.CC_LAST_NAME=t3_o2.CC_LAST_NAME AND t0_o1.CC_BILLING_ZIP=t3_o2.CC_BILLING_ZIP AND t0_o1.CC_CARD_NUMBER=t3_o2.CC_CARD_NUMBER) AND t3_o2.customer=t2_o2_customer.id AND t0_o1.customer=t1_o1_customer.id) - Suite: org.jboss.test.cmp2.commerce.CompleteUnitTestCase Test:testEJBQL Type:failure Exception: net.sourceforge.junitejb.RemoteAssertionFailedError Message: expected:...0_o.ORDER_NUMBER=t4_l.ORDER_NUMBER AND t6_l_product.id=t5_l_product_productCategories_R.PRODUCT_ID AND t1_pc.id=t5_l_product_productCategories_R.PRODUCT_CATEGORY_ID AND t1_pc.subId=t5_l_product_productCategories_R.PRODUCT_CATEGORY_SUBID AND t4_l.product=t6_l_product.id but was:...6_l_product.id=t5_l_product_productCategories_R.PRODUCT_ID AND t1_pc.id=t5_l_product_productCategories_R.PRODUCT_CATEGORY_ID AND t1_pc.subId=t5_l_product_productCategories_R.PRODUCT_CATEGORY_SUBID AND t4_l.product=t6_l_product.id AND t0_o.ORDER_NUMBER=t4_l.ORDER_NUMBER - -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products
[JBoss-dev] [JBoss JIRA] Created: (JBAS-68) Added missing MdbEjb.jsp in web-console
Added missing MdbEjb.jsp in web-console --- Key: JBAS-68 URL: http://jira.jboss.com/jira/browse/JBAS-68 Project: JBoss Application Server Type: Task Versions: JBossAS-3.2.6 Final, JBossAS-4.0.1RC1 Reporter: Dimitris Andreadis Assigned to: Dimitris Andreadis Priority: Minor Fix For: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-5.0 Alpha added missing MDB page, contributed by [EMAIL PROTECTED] -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-68) Added missing MdbEjb.jsp in web-console
[ http://jira.jboss.com/jira/browse/JBAS-68?page=history ] Dimitris Andreadis updated JBAS-68: --- Attachment: screenshot-1.jpg Added missing MdbEjb.jsp in web-console --- Key: JBAS-68 URL: http://jira.jboss.com/jira/browse/JBAS-68 Project: JBoss Application Server Type: Task Versions: JBossAS-3.2.6 Final, JBossAS-4.0.1RC1 Reporter: Dimitris Andreadis Assignee: Dimitris Andreadis Priority: Minor Fix For: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-5.0 Alpha Attachments: screenshot-1.jpg added missing MDB page, contributed by [EMAIL PROTECTED] -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-68) Added missing MdbEjb.jsp in web-console
[ http://jira.jboss.com/jira/browse/JBAS-68?page=history ] Dimitris Andreadis closed JBAS-68: -- Resolution: Done Added missing MdbEjb.jsp in web-console --- Key: JBAS-68 URL: http://jira.jboss.com/jira/browse/JBAS-68 Project: JBoss Application Server Type: Task Versions: JBossAS-3.2.6 Final, JBossAS-4.0.1RC1 Reporter: Dimitris Andreadis Assignee: Dimitris Andreadis Priority: Minor Fix For: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-5.0 Alpha Attachments: screenshot-1.jpg added missing MDB page, contributed by [EMAIL PROTECTED] -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossWS] - Paths and Getting Started Guide
I am using the Getting Started guide to develop my own web service. One of the
questions I came up with that I do not see discussed in the guide is the
classpath of the Axis files. I created a sub-directory on my server that I
copy the Axis JAR files in to, but I have to believe this is not the best
solution.
Are the JAR files on the server somewhere that I can add to my classpath? I am
doing all of this in an Ant script and it works, but I don't feel like I should
have to copy the Axis files to the server.
I have the service deployed and I can access it via the URL, but I am getting
the following exception when I try to run my client.
| [java] java.lang.IllegalAccessError: tried to access field
org.apache.axis.
| client.Service.engine from class org.jboss.webservice.client.ServiceImpl
| [java] at
org.jboss.webservice.client.ServiceImpl.getAxisClient(Service
| Impl.java:255)
| [java] at org.apache.axis.client.Service.init(Service.java:185)
| [java] at
org.jboss.webservice.client.ServiceImpl.init(ServiceImpl.ja
| va:99)
| [java] at
org.jboss.webservice.client.ServiceFactoryImpl.createService(
| ServiceFactoryImpl.java:112)
| [java] at com.hott.client.WSClient.main(Unknown Source)
| [java] Exception in thread main
|
I am using the exact code that comes from the Getting started guides files.
Here is my client code:
| package com.hott.client;
|
| import javax.xml.rpc.Call;
| import javax.xml.rpc.Service;
| import javax.xml.rpc.JAXRPCException;
| import javax.xml.rpc.ServiceFactory;
| import javax.xml.rpc.ParameterMode;
|
| import javax.xml.namespace.QName;
| import java.net.URL;
|
| import com.hott.service.BookSessionEndpoint;
| /**
| *
| * @author HOTT Instructor
| */
| public class WSClient {
|
| /**
| * @param args the command line arguments
| */
| public static void main(String[] args) throws Exception{
| URL url = new
URL(http://localhost:8080/ws4ee/services/BookSessionService?wsdl;);
|
| QName qname = new QName(http://service.hott.com;,
| BookSessionService);
|
| ServiceFactory factory = ServiceFactory.newInstance();
| Service service = factory.createService(url,qname);
|
| BookSessionEndpoint endpoint = (BookSessionEndpoint)
| service.getPort(BookSessionEndpoint.class);
|
| String byISBN = endpoint.findByISBN(99415);
| String byTitle = endpoint.findByTitle(Little Women);
| String byPrice = endpoint.findByPriceRange(0,100);
|
| System.out.println(By ISBN: + byISBN);
| System.out.println(By Title: + byTitle);
| System.out.println(By Price: + byPrice);
| }
|
| }
|
|
Thanks
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3859078#3859078
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859078
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-69) EJB Timer Service broken when used with security domain
EJB Timer Service broken when used with security domain --- Key: JBAS-69 URL: http://jira.jboss.com/jira/browse/JBAS-69 Project: JBoss Application Server Type: Bug Components: EJBs Versions: JBossAS-4.0.0 Final Reporter: Scott M Stark Assigned to: Scott M Stark Priority: Critical Fix For: JBossAS-4.0.1 Final -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-69) EJB Timer Service broken when used with security domain
[ http://jira.jboss.com/jira/browse/JBAS-69?page=history ] Scott M Stark updated JBAS-69: -- Description: When an EJB (an entity bean in my case) has a security domain associated with it, calls to the ejbTimeout method fail with a SecurityException (insufficient method permissions). It appears the principal is being hardcoded to null in the TimedObjectInvoker, causing the security check to fail in the SecurityInterceptor. I have tried setting the method permissions for ejbTimeout to unchecked, but these aren't picked up, possibly because ejbTimeout is not a member of the bean's local interface. was: EJB Timer Service broken when used with security domain --- Key: JBAS-69 URL: http://jira.jboss.com/jira/browse/JBAS-69 Project: JBoss Application Server Type: Bug Components: EJBs Versions: JBossAS-4.0.0 Final Reporter: Scott M Stark Assignee: Scott M Stark Priority: Critical Fix For: JBossAS-4.0.1 Final Original Estimate: 2 hours Remaining: 2 hours When an EJB (an entity bean in my case) has a security domain associated with it, calls to the ejbTimeout method fail with a SecurityException (insufficient method permissions). It appears the principal is being hardcoded to null in the TimedObjectInvoker, causing the security check to fail in the SecurityInterceptor. I have tried setting the method permissions for ejbTimeout to unchecked, but these aren't picked up, possibly because ejbTimeout is not a member of the bean's local interface. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-1081791 ] EJB Timer Service broken when used with security domain
Bugs item #1081791, was opened at 2004-12-08 17:17 Message generated for change (Comment added) made by starksm You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=1081791group_id=22866 Category: JBossServer Group: v4.0 Status: Closed Resolution: Duplicate Priority: 5 Submitted By: mpoindexter (mpoindexter) Assigned to: Scott M Stark (starksm) Summary: EJB Timer Service broken when used with security domain Initial Comment: When an EJB (an entity bean in my case) has a security domain associated with it, calls to the ejbTimeout method fail with a SecurityException (insufficient method permissions). It appears the principal is being hardcoded to null in the TimedObjectInvoker, causing the security check to fail in the SecurityInterceptor. I have tried setting the method permissions for ejbTimeout to unchecked, but these aren't picked up, possibly because ejbTimeout is not a member of the bean's local interface. I think there are two possible fixes: 1) Skip security checking for ejbTimeout in the SecurityInterceptor (don't think this is much of a solution since calls made to other beans in the ejbtimeout method will have no principal associated with them) 2) Store the current principal with the timer when the timer is created. When the timer triggers, recall this principal and set the current principal to the creator of the timer. I think this seems like the correct solution -- Comment By: Scott M Stark (starksm) Date: 2004-12-17 09:34 Message: Logged In: YES user_id=175228 This is being tracked in jira: http://jira.jboss.com/jira/browse/JBAS-69 -- Comment By: mpoindexter (mpoindexter) Date: 2004-12-09 13:23 Message: Logged In: YES user_id=1174627 Here's a version of SecurityInterceptor with a workaround, but it's not what I'd call an elegant solution. Just in case anyone else needs a fix quick. -- Comment By: Scott M Stark (starksm) Date: 2004-12-08 18:21 Message: Logged In: YES user_id=175228 No 2) is not correct as there is no security context associated with ejb timer calls. The container has to setup the permissions to deal with this correctly. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=1081791group_id=22866 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-1053625 ] Not JSR-77 Spec compliant
Bugs item #1053625, was opened at 2004-10-25 03:04 Message generated for change (Comment added) made by starksm You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=1053625group_id=22866 Category: JBossMX Group: v4.0 Status: Closed Resolution: Postponed Priority: 5 Submitted By: Marcus Redeker (mredeker) Assigned to: Scott M Stark (starksm) Summary: Not JSR-77 Spec compliant Initial Comment: We are currently developing a JSR-77 Management Console and found that JBoss's class org.jboss.management.j2ee.ResourceAdapter which represents the JSR-77 j2eeType ResourceAdapter is not spec complient. It must have an attribute jcaResource but JBoss has named the attribute JcaResource with a capital letter. Als we found that self deployed DataSources are not accessibale through JSR-77 because they have the JBoss LocalTransaction JDBC Wrapper as parent. But the spec allows only on object name to be returned by jcaResource. This means that each self deployed DataSource should get it's own JBoss LocalTransaction JDBC Wrapper which is accessible through JSR-77. -- Comment By: Scott M Stark (starksm) Date: 2004-12-17 09:36 Message: Logged In: YES user_id=175228 Reopen with a definition/example of a 'self deployed DataSource'. -- Comment By: Scott M Stark (starksm) Date: 2004-11-07 10:22 Message: Logged In: YES user_id=175228 A duplicate jcaResource has been added to conform to the expected name. I'll look into the DataSource naming issue, but define what you mean by 'self deployed DataSource'. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=1053625group_id=22866 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss's Web Services Implementation] - Re: JBossWS Streaming Implementation Proposal
[EMAIL PROTECTED] wrote : Hi Jason, | | The important bit is, to allow to go forth and back between the XML and Java Object representation at the SOAPContentElement level | using the JAXRPC serializer/deserializers. | | Whether to hold the XML representation as String or StAX events is an (important) implementation detail. | So how about this: | | MessageFactory.createMessage builds the SAAJ view as above with SOAPContentElement(s). | Upon END_ELEMENT the SOAPContentElement passes the event stream to the deserializer which constructs the java objects | and assigns it to the SOAPContentElement. If we don't have handlers the java object passes unmodified the endpoint. | I had thought about adapting SAAJ in some way that would internally use StAX, but there are a couple of problems. 1) you have to scan through the whole message to build the outer SAAJ tree 2) Since the parser is forward only, you can't backtrack if you need to, which makes lazy loading difficult. Now its possible to cache the event objects for a block, which is more efficiant than a DOM tree, but it still requires you to effectivelly allocate a list of objects that is the size of the entire message. XML fragments have the same problem because you are still allocating a block of memory that is the size of the message. This prompted me to consider an alternative to using SAAJ, though I was not sure if there was a problem with this, since so much of the current design is built around SAAJ. I assumed that the reason for using it, was just to simplify passing elements to handlers. I was also working under the idea of trying to come up with a solution that allowed for parsing an indefinitely large message, with as minimal copies as possible. By not maintaining that SAAJ tree, we no longer have a need to hold on to any of the XML after we process it. So a SOAP message could be 1 TB for all we care, and we would only allocate a few K. This is just refering to space allocated for processing, I realize that if every single element in the SOAP message is actually deserialized into an object of equivalent size, the memory usage would be the same if not larger than the SOAP message. If however only a few elements are mapped to the message, the memory allocation would be quite small. So I guess the questions I have are: Is trying to optimze for a tiny memory footprint unnesessary or unrealistic? Are there other reasons to have an SAAJ tree that I didn't think of? -Jason View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3859084#3859084 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859084 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAOP-1) VersionedObjectUnitTestCase fails under java5
[ http://jira.jboss.com/jira/browse/JBAOP-1?page=history ] Bill Burke closed JBAOP-1: -- Resolution: Done org.jboss.util.id.GUID was not Comparable and Versioned aspect was sorting a list of them. Not sure how this EVER worked. VersionedObjectUnitTestCase fails under java5 - Key: JBAOP-1 URL: http://jira.jboss.com/jira/browse/JBAOP-1 Project: JBoss AOP Type: Bug Environment: 13:35:08,406 INFO [Server] Starting JBoss (MX MicroKernel)... 13:35:08,406 INFO [Server] Release ID: JBoss [Zion] 4.0.1RC2 (build: CVSTag=Branch_4_0 date=200411271821) 13:35:08,406 INFO [Server] Home Dir: C:\cvs\JBoss4.0\jboss-4.0\build\output\jboss-4.0.1RC2 13:35:08,406 INFO [Server] Home URL: file:/C:/cvs/JBoss4.0/jboss-4.0/build/output/jboss-4.0.1RC2/ 13:35:08,406 INFO [Server] Library URL: file:/C:/cvs/JBoss4.0/jboss-4.0/build/output/jboss-4.0.1RC2/lib/ 13:35:08,406 INFO [Server] Patch URL: null 13:35:08,406 INFO [Server] Server Name: all 13:35:08,406 INFO [Server] Server Home Dir: C:\cvs\JBoss4.0\jboss-4.0\build\output\jboss-4.0.1RC2\server\all 13:35:08,421 INFO [Server] Server Home URL: file:/C:/cvs/JBoss4.0/jboss-4.0/build/output/jboss-4.0.1RC2/server/all/ 13:35:08,421 INFO [Server] Server Data Dir: C:\cvs\JBoss4.0\jboss-4.0\build\output\jboss-4.0.1RC2\server\all\data 13:35:08,421 INFO [Server] Server Temp Dir: C:\cvs\JBoss4.0\jboss-4.0\build\output\jboss-4.0.1RC2\server\all\tmp 13:35:08,421 INFO [Server] Server Config URL: file:/C:/cvs/JBoss4.0/jboss-4.0/build/output/jboss-4.0.1RC2/server/all/conf/ 13:35:08,421 INFO [Server] Server Library URL: file:/C:/cvs/JBoss4.0/jboss-4.0/build/output/jboss-4.0.1RC2/server/all/lib/ 13:35:08,421 INFO [Server] Root Deployment Filename: jboss-service.xml 13:35:08,421 INFO [Server] Starting General Purpose Architecture (GPA)... 13:35:08,937 INFO [ServerInfo] Java version: 1.5.0,Sun Microsystems Inc. 13:35:08,937 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0-b64,Sun Microsystems Inc. 13:35:08,937 INFO [ServerInfo] OS-System: Windows XP 5.1,x86 Reporter: Scott M Stark Assignee: Bill Burke The org.jboss.test.aop.test.VersionedObjectUnitTestCase is failing with the following exception when jboss is running under java5. The same test runs fine when running under jdk1.4.2_05. 13:36:14,531 INFO [VersionedObjectTester] test optimistic lock 13:36:14,578 INFO [VersionedObjectTester] caught exception correctly: Unable to commit, tx=TransactionImpl:XidImpl[FormatId=257, GlobalId=banshee9100/94, Branc hQual=, localId=94] status=STATUS_NO_TRANSACTION; - nested throwable: (java.lang.ClassCastException: org.jboss.util.id.GUID) exception type: javax.transaction.T ransactionRolledbackException 13:36:14,578 ERROR [VersionedObjectTester] failed java.lang.Exception: optimistic lock failed, field was changed at org.jboss.test.aop.bean.VersionedObjectTester.org$jboss$test$aop$bean$VersionedObjectTester$testPerField$aop(VersionedObjectTester.java:85) at org.jboss.test.aop.bean.VersionedObjectTester.testPerField(VersionedObjectTester.java) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:257) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:122)
[JBoss-dev] [Design of JBossCache] - Re: I can' t run the example from the downloaded zip file.
after download, do I have to change some configuration file? thanks View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3859086#3859086 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859086 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossWS] - Second WS parameter set to null
I have a webservice that takes two string parameters. I am calling the
webservice from a DII client and the second parameter seems to be getting lost.
I have set the org.apache.axis is DEBUG level reporting and this is part of
what I get:
| 2004-12-17 17:27:46,978 DEBUG [org.apache.axis.message.BodyBuilder] Exit:
BodyBuilder::onStartChild()
| 2004-12-17 17:27:46,978 DEBUG [org.apache.axis.i18n.ProjectResourceBundle]
org.apache.axis.i18n.resource::handleGetObject(pushHandler00)
| 2004-12-17 17:27:46,978 DEBUG
[org.apache.axis.encoding.DeserializationContextImpl] Pushing handler [EMAIL
PROTECTED]
| 2004-12-17 17:27:46,978 DEBUG
[org.apache.axis.encoding.DeserializationContextImpl] Pushing element in0
| 2004-12-17 17:27:46,978 DEBUG [org.apache.axis.message.SOAPElementAxisImpl]
Adding child: ns1:in0
| 2004-12-17 17:27:46,978 DEBUG
[org.apache.axis.message.SOAPEnvelopeAxisImpl] setModifiedAfterSerialization:
true
| 2004-12-17 17:27:46,978 DEBUG
[org.apache.axis.encoding.DeserializationContextImpl] Exit:
DeserializationContextImpl::startElement()
| 2004-12-17 17:27:46,978 DEBUG
[org.apache.axis.encoding.DeserializationContextImpl] addTextNode: 'isabored'
| 2004-12-17 17:27:46,978 DEBUG [org.apache.axis.message.SOAPElementAxisImpl]
Adding child: #text [isabored]
| 2004-12-17 17:27:46,978 DEBUG
[org.apache.axis.message.SOAPEnvelopeAxisImpl] setModifiedAfterSerialization:
true
| 2004-12-17 17:27:46,978 DEBUG
[org.apache.axis.encoding.DeserializationContextImpl] Enter:
DeserializationContextImpl::endElement(http://4testApp.dyndns.org/ws4ee, in0)
| 2004-12-17 17:27:46,978 DEBUG [org.apache.axis.i18n.ProjectResourceBundle]
org.apache.axis.i18n.resource::handleGetObject(popHandler00)
| 2004-12-17 17:27:46,978 DEBUG
[org.apache.axis.encoding.DeserializationContextImpl] Popping handler [EMAIL
PROTECTED]
| 2004-12-17 17:27:46,978 DEBUG
[org.apache.axis.encoding.DeserializationContextImpl] Popped element stack to
org.apache.axis.message.SOAPBodyAxisImpl:Body
| 2004-12-17 17:27:46,978 DEBUG
[org.apache.axis.encoding.DeserializationContextImpl] Exit:
DeserializationContextImpl::endElement()
| 2004-12-17 17:27:46,978 DEBUG
[org.apache.axis.encoding.DeserializationContextImpl] Enter:
DeserializationContextImpl::endPrefixMapping(ns1)
| 2004-12-17 17:27:46,978 DEBUG
[org.apache.axis.encoding.DeserializationContextImpl] Exit:
DeserializationContextImpl::endPrefixMapping()
| 2004-12-17 17:27:46,978 DEBUG
[org.apache.axis.encoding.DeserializationContextImpl] Enter:
DeserializationContextImpl::startPrefixMapping(ns2,
http://4testApp.dyndns.org/ws4ee)
| 2004-12-17 17:27:46,978 DEBUG
[org.apache.axis.encoding.DeserializationContextImpl] Exit:
DeserializationContextImpl::startPrefixMapping()
| 2004-12-17 17:27:46,978 DEBUG
[org.apache.axis.encoding.DeserializationContextImpl] Enter:
DeserializationContextImpl::startElement(http://4testApp.dyndns.org/ws4ee, in1)
| 2004-12-17 17:27:46,978 DEBUG [org.apache.axis.message.BodyBuilder] Enter:
BodyBuilder::onStartChild()
| 2004-12-17 17:27:46,978 DEBUG [org.apache.axis.utils.DOM2Utils]
createElement {http://4testApp.dyndns.org/ws4ee}ns2:in1
| 2004-12-17 17:27:46,978 DEBUG [org.apache.axis.i18n.ProjectResourceBundle]
org.apache.axis.i18n.resource::handleGetObject(newElem00)
| 2004-12-17 17:27:46,978 DEBUG [org.apache.axis.message.SOAPElementAxisImpl]
New MessageElement ([EMAIL PROTECTED]:in1: null]]) named {ns2}in1
| 2004-12-17 17:27:46,978 DEBUG [org.apache.axis.message.BodyBuilder] Exit:
BodyBuilder::onStartChild()
| 2004-12-17 17:27:46,978 DEBUG [org.apache.axis.i18n.ProjectResourceBundle]
org.apache.axis.i18n.resource::handleGetObject(pushHandler00)
| 2004-12-17 17:27:46,978 DEBUG
[org.apache.axis.encoding.DeserializationContextImpl] Pushing handler [EMAIL
PROTECTED]
| 2004-12-17 17:27:46,978 DEBUG
[org.apache.axis.encoding.DeserializationContextImpl] Pushing element in1
| 2004-12-17 17:27:46,978 DEBUG [org.apache.axis.message.SOAPElementAxisImpl]
Adding child: ns2:in1
| 2004-12-17 17:27:46,978 DEBUG
[org.apache.axis.message.SOAPEnvelopeAxisImpl] setModifiedAfterSerialization:
true
| 2004-12-17 17:27:46,978 DEBUG
[org.apache.axis.encoding.DeserializationContextImpl] Exit:
DeserializationContextImpl::startElement()
| 2004-12-17 17:27:46,978 DEBUG
[org.apache.axis.encoding.DeserializationContextImpl] addTextNode: 'testField'
| 2004-12-17 17:27:46,978 DEBUG [org.apache.axis.message.SOAPElementAxisImpl]
Adding child: #text [testField]
| 2004-12-17 17:27:46,978 DEBUG
[org.apache.axis.message.SOAPEnvelopeAxisImpl] setModifiedAfterSerialization:
true
| 2004-12-17 17:27:46,978 DEBUG
[org.apache.axis.encoding.DeserializationContextImpl] Enter:
DeserializationContextImpl::endElement(http://4testApp.dyndns.org/ws4ee, in1)
| 2004-12-17 17:27:46,978 DEBUG [org.apache.axis.i18n.ProjectResourceBundle]
org.apache.axis.i18n.resource::handleGetObject(popHandler00)
|
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-65) MDB Deployment ignores activation-config
[ http://jira.jboss.com/jira/browse/JBAS-65?page=history ] Adrian Brock closed JBAS-65: Resolution: Done Fixed for 4.0.1 MDB Deployment ignores activation-config Key: JBAS-65 URL: http://jira.jboss.com/jira/browse/JBAS-65 Project: JBoss Application Server Type: Bug Components: EJBs Versions: JBossAS-4.0.0 Final Environment: Sun JVM 5 JBOSS: 4.0.1 RC1 Reporter: Michael Kopp Assignee: Adrian Brock Fix For: JBossAS-4.0.1 Final I use ejb-jar.xml with EJB spec 2.1. Jboss ignores the message-selector on the following MDB: message-driven description![CDATA[]]/description ejb-nameTransactionWriterBean/ejb-name ejb-classcom.ftisoft.streetlamp.ejb.TransactionWriter/ejb-class messaging-typejavax.jms.MessageListener/messaging-type transaction-typeContainer/transaction-type message-destination-typejavax.jms.Topic/message-destination-type activation-config activation-config-property activation-config-property-namedestinationType/activation-config-property-name activation-config-property-valuejavax.jms.Topic/activation-config-property-value /activation-config-property activation-config-property activation-config-property-namemessageSelector/activation-config-property-name activation-config-property-valuestreetlampWritten lt; true/activation-config-property-value /activation-config-property /activation-config resource-ref res-ref-namejdbc/HibernateFactory/res-ref-name res-typenet.sf.hibernate.SessionFactory/res-type res-authContainer/res-auth /resource-ref /message-driven Furthermore I see the following Warnings during deployment: 11:14:34,971 WARN [JMSContainerInvoker] No message-driven-destination given; using; guessing type 11:14:35,142 WARN [JMSContainerInvoker] No message-driven-destination given; using; guessing type 11:14:35,365 WARN [JMSContainerInvoker] Could not determine destination type, defaults to: javax.jms.Topic 11:14:35,691 WARN [JMSContainerInvoker] No message-driven-destination given; using; guessing type 11:14:35,717 WARN [JMSContainerInvoker] No message-driven-destination given; using; guessing type -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - Re: jboss aop on websphere
I'm using 1.4.1 of the IBM VM. We're pretty much tied to WebSphere on this project, so even if we did upgrade to 6.0 in the near term (which we won't) we'd still only be on 1.4.2. I tried altering the following part of the replace call in AspectManager.getInstrumentedClassLoader(): + $_ = $proceed($1, newBytes, 0, newBytes.length, $5) ; with + $_ = $proceed($1, newBytes, 0, newBytes.length, $5, $6, $7) ; Just like before when I set jboss.aop.verbose to true it chatters on about trying to transform certain objects and determining what methods should be aspectized. That seems to indicate that the AspectManager is being called at the correct time before the defineClass0 method is called, and that classes are successfully being loaded to some degree. Ultimately it dies at the same place as before. It still throws the same exception, stating that it is unable to aspectize a class because it is unable to find another class that it references. Not sure if the above fix is the fix you were envisioning or not, but I thought I'd give it a try from what I understand about the code. As far as the recursive classloading techniques, I'd be interested in trying that out, would I need to dig into javassist? I'll start there and see what I can find, but please feel free to give any directions you might find helpful (I understand that you're pretty strapped for time). Thanks for the help, Tom View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3859092#3859092 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859092 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBWEB-6) Release JK-1.2.8
[ http://jira.jboss.com/jira/browse/JBWEB-6?page=comments#action_12310873 ] Mladen Turk commented on JBWEB-6: - Released JK-1.2.8-RC-1 This is the last release before 1.2.8 final. The same release will be marked as stable as no more bugs found. Release JK-1.2.8 Key: JBWEB-6 URL: http://jira.jboss.com/jira/browse/JBWEB-6 Project: JBoss Web Type: Task Components: mod_jk Versions: mod_jk 1.2.8 Reporter: Mladen Turk Assignee: Mladen Turk Fix For: mod_jk 1.2.8 Original Estimate: 2 days Remaining: 2 days Release new stable 1.2.8 release for mod_jk. My plan is to use and enforce an even number notation for stable releases. All bug fixes and IIS installer will be finished by that time. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-70) Security event listener that could be plugged in to listen to authentication and authorization events.
Security event listener that could be plugged in to listen to authentication and authorization events. -- Key: JBAS-70 URL: http://jira.jboss.com/jira/browse/JBAS-70 Project: JBoss Application Server Type: Feature Request Components: Security Versions: JBossAS-4.0.0 Final Reporter: Jagannath Bodapatla Assigned to: Scott M Stark Priority: Critical I would like to capture/trace user login (user-id/role, success or failure) every time user access server, so that we can know who is using our system and what is doing. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAOP-55) Allow use of annotations for parameters in pointcuts
Allow use of annotations for parameters in pointcuts Key: JBAOP-55 URL: http://jira.jboss.com/jira/browse/JBAOP-55 Project: JBoss AOP Type: Bug Reporter: Kabir Khan Assigned to: Kabir Khan Fix For: 1.1 Should be possible to do: execution(* POJO-method(@Ann)) and execution(POJO-new(@Ann)) etc. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - Re: jboss aop on websphere
Tom, thanks for all your patience here... Did you ever try just using the precompiler? (AOPC) View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3859096#3859096 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859096 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of Clustering on JBoss (Clusters/JBoss)] - Colocation and local optimization - JBAS-57
This relates to the following JIRA task: http://jira.jboss.com/jira/browse/JBAS-57 Since the colocation check in HAJRMP isn't redudant, this needs fixing in two ways: a) It needs applying to the other HA invokers b) It needs moving the interceptor chain where the policy can be overridden when required. Design: 1) Move the colocation hashmap into a separate static maintained by ProxyFactoryHA 2) Rather than creating a whole new set of InvokerInterceptors that understand the colocation map, I propose to update the default InvokerInterceptor.isLocal() to also check the colocation map, not just the GUID. This will be done in a protected method so that subclasses may override the behaviour as required. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3859101#3859101 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859101 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBMICROCONT-4) Virtual File System service
Virtual File System service --- Key: JBMICROCONT-4 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-4 Project: JBoss MicroContainer Type: Feature Request Reporter: Ivelin Ivanov Assigned to: Dimitris Andreadis Priority: Critical Fix For: JBossMC_1_0_0M2 [Adrian] Ok, here is the design I have in mind for the new deployer aspects. This will be part of JBoss Kernel M2 release due by end of January. Deploying Deployers: First you have to be able to deploy a deployer. Not an easy task as I imagine the deployer will have dependencies on other services. The aim will be to minimize these dependencies to ease the problem. Basic Architecture: The basic architecture of the aspectized deployer is that the deployments work with a tree of DeploymentInfo objects just like the deployers do now. There are two major differences: 1) The deployers do not deal with urls, they deal with VFS contexts 2) The deployers do not create objects directly, instead they create kernel MetaData objects and submit them to the kernel for instantiation/configuration to obtain correct ordering of startup/shutdown Deployment Mode: The deployers work in two different modes 1) The first step is to ask who recognises the VFS context. This is so the responsible deployer can correctly decide which part of the context takes part in the classloading and where the metadata is located. Additionally, this may introduce subdeployments (VFS contexts) if the deployment allows/contains them. 2) The second step (the main chain) allows each deployer to augment the kernel metadata with its own config. Deployer Ordering: Since the deployers are working on a metadata model rather than constructing objects directly, there should be less problem with ordering. Most ordering will be in the classloader/instantiation/config stage, the deployer should insert that ordering in the form of dependencies in the metadata. The only ordering required of the deployer chain is where one deployer needs to work on the kernel metadata output of another deployer. Killing two birds with one stone: The problems mentioned with the deployer requiring other services and the first tasks performed by package specific deployers, i.e. identifying the deployment and its structure can be easily solved by splitting the deployers into two classes 1) A structural component that says I recognise this deployment and this is how it is structured 2) An interpretive component that creates the kernel metadata from the package. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBMICROCONT-4) Virtual File System service
[ http://jira.jboss.com/jira/browse/JBMICROCONT-4?page=comments#action_12310874 ] Ivelin Ivanov commented on JBMICROCONT-4: - From Dimitris: http://www.jboss.org/index.html?module=bbop=viewtopict=57790 Virtual File System service --- Key: JBMICROCONT-4 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-4 Project: JBoss MicroContainer Type: Feature Request Reporter: Ivelin Ivanov Assignee: Dimitris Andreadis Priority: Critical Fix For: JBossMC_1_0_0M2 [Adrian] Ok, here is the design I have in mind for the new deployer aspects. This will be part of JBoss Kernel M2 release due by end of January. Deploying Deployers: First you have to be able to deploy a deployer. Not an easy task as I imagine the deployer will have dependencies on other services. The aim will be to minimize these dependencies to ease the problem. Basic Architecture: The basic architecture of the aspectized deployer is that the deployments work with a tree of DeploymentInfo objects just like the deployers do now. There are two major differences: 1) The deployers do not deal with urls, they deal with VFS contexts 2) The deployers do not create objects directly, instead they create kernel MetaData objects and submit them to the kernel for instantiation/configuration to obtain correct ordering of startup/shutdown Deployment Mode: The deployers work in two different modes 1) The first step is to ask who recognises the VFS context. This is so the responsible deployer can correctly decide which part of the context takes part in the classloading and where the metadata is located. Additionally, this may introduce subdeployments (VFS contexts) if the deployment allows/contains them. 2) The second step (the main chain) allows each deployer to augment the kernel metadata with its own config. Deployer Ordering: Since the deployers are working on a metadata model rather than constructing objects directly, there should be less problem with ordering. Most ordering will be in the classloader/instantiation/config stage, the deployer should insert that ordering in the form of dependencies in the metadata. The only ordering required of the deployer chain is where one deployer needs to work on the kernel metadata output of another deployer. Killing two birds with one stone: The problems mentioned with the deployer requiring other services and the first tasks performed by package specific deployers, i.e. identifying the deployment and its structure can be easily solved by splitting the deployers into two classes 1) A structural component that says I recognise this deployment and this is how it is structured 2) An interpretive component that creates the kernel metadata from the package. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-57) Need the ability to disable ha invoker local optimization path
[ http://jira.jboss.com/jira/browse/JBAS-57?page=comments#action_12310875 ] Adrian Brock commented on JBAS-57: -- Since we've decided the colocation check is not redundant. I've put the proposed solution in the forums for discussion. Need the ability to disable ha invoker local optimization path -- Key: JBAS-57 URL: http://jira.jboss.com/jira/browse/JBAS-57 Project: JBoss Application Server Type: Feature Request Components: Clustering Versions: JBossAS-3.2.6 Final, JBossAS-4.0.0 Final Reporter: Scott M Stark Assignee: Adrian Brock Fix For: JBossAS-3.2.7 Final, JBossAS-4.0.1 Final The ha invoker proxies currently perform a check for a collocated call, and if this check is statisfied, the ha invoker channel is ignored. A frequent request is to disable this. Because this logic is embedded in the ha invoker proxy instead of the InvokerInterceptor, this cannot be easily done. In lieu of a refactoring of the ha proxy, there should be a flag which simply disables the optimization done within the proxy. One might even argue that this check should be removed altogether since it does already exist at the InvokerInterceptor level. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-57) Need the ability to disable ha invoker local optimization path
[ http://jira.jboss.com/jira/browse/JBAS-57?page=history ] Adrian Brock updated JBAS-57: - JBoss Forum Reference: http://www.jboss.org/index.html?module=bbop=viewtopict=57830 Need the ability to disable ha invoker local optimization path -- Key: JBAS-57 URL: http://jira.jboss.com/jira/browse/JBAS-57 Project: JBoss Application Server Type: Feature Request Components: Clustering Versions: JBossAS-3.2.6 Final, JBossAS-4.0.0 Final Reporter: Scott M Stark Assignee: Adrian Brock Fix For: JBossAS-3.2.7 Final, JBossAS-4.0.1 Final The ha invoker proxies currently perform a check for a collocated call, and if this check is statisfied, the ha invoker channel is ignored. A frequent request is to disable this. Because this logic is embedded in the ha invoker proxy instead of the InvokerInterceptor, this cannot be easily done. In lieu of a refactoring of the ha proxy, there should be a flag which simply disables the optimization done within the proxy. One might even argue that this check should be removed altogether since it does already exist at the InvokerInterceptor level. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - Re: jboss aop on websphere
I'm not sure whether aopc would work for my situation. I'm using IBM's web services implementation for WebSphere, which include a bunch of closed source classes. Those classes are the ones I want to do the instrumentation on. I didn't try it with jboss-aop, but I tried to instrument the classes with aspectj and it seemed to have some issues getting at those classes or at least it being difficult to get it to do so. With aopc would it recompile the appropriate classes in those jar files to something new? I'd need to then determine what changed and make sure pathing is correct for the classloaders involved. Sorry my understanding is just starting to grow about the innerworkings of classloaders, compilers and the other tools used internally to AOP implementations. Now that I understand javassist's role with jboss-aop a little better and how it is able to alter the actual bytecode, I'm wondering if aopc would be a possibility. The loadtime transformations would be handy though. I'm in early phases of using aop, mostly for debugging and logging while I'm developing and just making a quick change to an xml file for some reason seems much more appealing than having to recompile all of the classes everytime I want to change a pointcut. Like I said before I'd be happy to do what I can to get this working. Thanks, Tom View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3859102#3859102 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859102 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossWS] - Re: Paths and Getting Started Guide
I wanted to add another question to this message.
I have gotten the service deployed and I am trying to access the service from a
servlet. Here is the code in the doGet method of my servlet:
| try{
| URL url = new
URL(http://localhost:8080/ws4ee/services/BookSessionService?wsdl;);
| QName qname = new
QName(http://service.hott.com,BookSessionService;);
| ServiceFactory factory = ServiceFactory.newInstance();
| Service service = factory.createService(url,qname);
|
| BookSessionEndpoint endpoint = (BookSessionEndpoint)
| service.getPort(BookSessionEndpoint.class);
| System.out.println(It works to here);
| String byISBN = endpoint.findByISBN(99415);
| out.println(By ISBN: + byISBN);
| System.out.println(Here I am 5);
| String byTitle = endpoint.findByTitle(Little Women);
| out.println(By Title: + byTitle);
| System.out.println(Here I am 6);
| String byPrice = endpoint.findByPriceRange(0,100);
| out.println(By Price: + byPrice);
| System.out.println(Here I am 7);
|
The code works up to the System.out.println(It works to here). When the code
encounters the call to findByISBN(99415) it returns a SOAP fault. Reading the
SOAP fault it is telling me that the Service is unavailable and I get back a
404 from the server.
I can access the WSDL file using the URL. Can anyone give me some thoughts on
what's going on? If there are any other deployment descriptors you would like
to see please let me know.
Thanks again.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3859103#3859103
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859103
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBPM-35) expose link status to expressions in join conditions (9.1, 12.5.1)
[ http://jira.jboss.com/jira/browse/JBPM-35?page=history ] Juan Cantu resolved JBPM-35: Resolution: Done expose link status to expressions in join conditions (9.1, 12.5.1) --- Key: JBPM-35 URL: http://jira.jboss.com/jira/browse/JBPM-35 Project: JBoss jBPM Type: Sub-task Components: BPEL Versions: 3.0 DR 1 Environment: dom4j, jaxen Reporter: Alejandro Guzar Assignee: Juan Cantu Fix For: 3.0 DR 1 Original Estimate: 1 day Time Spent: 1 day Remaining: 0 minutes Mantain link status in the context instance. Expose status of an activity's incoming links to the join condition associated with that activity. Implement the bpws:getLinkStatus() extension function. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBMICROCONT-4) Virtual File System service
[ http://jira.jboss.com/jira/browse/JBMICROCONT-4?page=comments#action_12310877 ] Ivelin Ivanov commented on JBMICROCONT-4: - Mladen also proposed gnome and http://apvfs.sourceforge.net/ (his vfs module for httpd). Virtual File System service --- Key: JBMICROCONT-4 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-4 Project: JBoss MicroContainer Type: Feature Request Reporter: Ivelin Ivanov Assignee: Dimitris Andreadis Priority: Critical Fix For: JBossMC_1_0_0M2 [Adrian] Ok, here is the design I have in mind for the new deployer aspects. This will be part of JBoss Kernel M2 release due by end of January. Deploying Deployers: First you have to be able to deploy a deployer. Not an easy task as I imagine the deployer will have dependencies on other services. The aim will be to minimize these dependencies to ease the problem. Basic Architecture: The basic architecture of the aspectized deployer is that the deployments work with a tree of DeploymentInfo objects just like the deployers do now. There are two major differences: 1) The deployers do not deal with urls, they deal with VFS contexts 2) The deployers do not create objects directly, instead they create kernel MetaData objects and submit them to the kernel for instantiation/configuration to obtain correct ordering of startup/shutdown Deployment Mode: The deployers work in two different modes 1) The first step is to ask who recognises the VFS context. This is so the responsible deployer can correctly decide which part of the context takes part in the classloading and where the metadata is located. Additionally, this may introduce subdeployments (VFS contexts) if the deployment allows/contains them. 2) The second step (the main chain) allows each deployer to augment the kernel metadata with its own config. Deployer Ordering: Since the deployers are working on a metadata model rather than constructing objects directly, there should be less problem with ordering. Most ordering will be in the classloader/instantiation/config stage, the deployer should insert that ordering in the form of dependencies in the metadata. The only ordering required of the deployer chain is where one deployer needs to work on the kernel metadata output of another deployer. Killing two birds with one stone: The problems mentioned with the deployer requiring other services and the first tasks performed by package specific deployers, i.e. identifying the deployment and its structure can be easily solved by splitting the deployers into two classes 1) A structural component that says I recognise this deployment and this is how it is structured 2) An interpretive component that creates the kernel metadata from the package. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBPM-28) Link Semantics (12.5.1) and Death Path elimination (12.5.2)
[ http://jira.jboss.com/jira/browse/JBPM-28?page=history ] Juan Cantu resolved JBPM-28: Resolution: Done Link Semantics (12.5.1) and Death Path elimination (12.5.2) --- Key: JBPM-28 URL: http://jira.jboss.com/jira/browse/JBPM-28 Project: JBoss jBPM Type: Sub-task Components: BPEL Versions: 3.0 DR 1 Reporter: Juan Cantu Assignee: Juan Cantu Fix For: 3.0 DR 1 Original Estimate: 1 week, 2 days Time Spent: 4 days Remaining: 3 days Implement the routing constraints enforced by source and target links of bpel activities. This mechanism is defined in chapter 12.5.1 and 12.5.2 of the bpel spec. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0 build.276 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20041217111905Lbuild.276 BUILD COMPLETE-build.276Date of build:12/17/2004 11:19:05Time to build:91 minutes 6 secondsLast changed:12/17/2004 10:17:43Last log entry:added missing MDB page, contributed by [EMAIL PROTECTED] Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(1)1.1.2.1modifiedanddconsole/src/resources/webconsole.war/MdbEjb.jspadded missing MDB page, contributed by [EMAIL PROTECTED]
[JBoss-dev] [JBoss JIRA] Commented: (JBMICROCONT-4) Virtual File System service
[ http://jira.jboss.com/jira/browse/JBMICROCONT-4?page=comments#action_12310879 ] Adrian Brock commented on JBMICROCONT-4: Guys, maybe we shouldn't call it a VFS. Perhaps (VDF) Virtual Deployment Framework is a better name. The purpose of the coponent isn't to abstract away the protocol (though that will be a part of it). In fact for the osgi facade there will be a requirement for a component to get URLHandlers. The purpose of the VDF is to abstract away: 1) The meta data location 2) The real urls that make up the classpath 3) Identifying subdeployments 4) The unpacking of the subdeployments into a temporary location 5) The downloading of remote deployments to the temporary location 6) Unpacked/packed deployments 7) The logical urls that make up the codebase for security checks Virtual File System service --- Key: JBMICROCONT-4 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-4 Project: JBoss MicroContainer Type: Feature Request Reporter: Ivelin Ivanov Assignee: Dimitris Andreadis Priority: Critical Fix For: JBossMC_1_0_0M2 [Adrian] Ok, here is the design I have in mind for the new deployer aspects. This will be part of JBoss Kernel M2 release due by end of January. Deploying Deployers: First you have to be able to deploy a deployer. Not an easy task as I imagine the deployer will have dependencies on other services. The aim will be to minimize these dependencies to ease the problem. Basic Architecture: The basic architecture of the aspectized deployer is that the deployments work with a tree of DeploymentInfo objects just like the deployers do now. There are two major differences: 1) The deployers do not deal with urls, they deal with VFS contexts 2) The deployers do not create objects directly, instead they create kernel MetaData objects and submit them to the kernel for instantiation/configuration to obtain correct ordering of startup/shutdown Deployment Mode: The deployers work in two different modes 1) The first step is to ask who recognises the VFS context. This is so the responsible deployer can correctly decide which part of the context takes part in the classloading and where the metadata is located. Additionally, this may introduce subdeployments (VFS contexts) if the deployment allows/contains them. 2) The second step (the main chain) allows each deployer to augment the kernel metadata with its own config. Deployer Ordering: Since the deployers are working on a metadata model rather than constructing objects directly, there should be less problem with ordering. Most ordering will be in the classloader/instantiation/config stage, the deployer should insert that ordering in the form of dependencies in the metadata. The only ordering required of the deployer chain is where one deployer needs to work on the kernel metadata output of another deployer. Killing two birds with one stone: The problems mentioned with the deployer requiring other services and the first tasks performed by package specific deployers, i.e. identifying the deployment and its structure can be easily solved by splitting the deployers into two classes 1) A structural component that says I recognise this deployment and this is how it is structured 2) An interpretive component that creates the kernel metadata from the package. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBMICROCONT-4) Virtual File System service
[ http://jira.jboss.com/jira/browse/JBMICROCONT-4?page=comments#action_12310880 ] Scott M Stark commented on JBMICROCONT-4: - Agreed. At one point it was mentioned that class loading and scoping/directionality of loading of classes/resources was also part of this, and certainly this is a concept completely foreign to a traditional file system abstraction. Virtual File System service --- Key: JBMICROCONT-4 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-4 Project: JBoss MicroContainer Type: Feature Request Reporter: Ivelin Ivanov Assignee: Dimitris Andreadis Priority: Critical Fix For: JBossMC_1_0_0M2 [Adrian] Ok, here is the design I have in mind for the new deployer aspects. This will be part of JBoss Kernel M2 release due by end of January. Deploying Deployers: First you have to be able to deploy a deployer. Not an easy task as I imagine the deployer will have dependencies on other services. The aim will be to minimize these dependencies to ease the problem. Basic Architecture: The basic architecture of the aspectized deployer is that the deployments work with a tree of DeploymentInfo objects just like the deployers do now. There are two major differences: 1) The deployers do not deal with urls, they deal with VFS contexts 2) The deployers do not create objects directly, instead they create kernel MetaData objects and submit them to the kernel for instantiation/configuration to obtain correct ordering of startup/shutdown Deployment Mode: The deployers work in two different modes 1) The first step is to ask who recognises the VFS context. This is so the responsible deployer can correctly decide which part of the context takes part in the classloading and where the metadata is located. Additionally, this may introduce subdeployments (VFS contexts) if the deployment allows/contains them. 2) The second step (the main chain) allows each deployer to augment the kernel metadata with its own config. Deployer Ordering: Since the deployers are working on a metadata model rather than constructing objects directly, there should be less problem with ordering. Most ordering will be in the classloader/instantiation/config stage, the deployer should insert that ordering in the form of dependencies in the metadata. The only ordering required of the deployer chain is where one deployer needs to work on the kernel metadata output of another deployer. Killing two birds with one stone: The problems mentioned with the deployer requiring other services and the first tasks performed by package specific deployers, i.e. identifying the deployment and its structure can be easily solved by splitting the deployers into two classes 1) A structural component that says I recognise this deployment and this is how it is structured 2) An interpretive component that creates the kernel metadata from the package. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of Clustering on JBoss (Clusters/JBoss)] - Re: Colocation and local optimization - JBAS-57
If there is going to be a check for an entry in the collocation map, then effectively the GUID becomes irrelevant. Other cleanup than could be done is removal of the unused remoteInvoker instance variable. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3859105#3859105 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859105 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBMICROCONT-4) Virtual File System service
[ http://jira.jboss.com/jira/browse/JBMICROCONT-4?page=comments#action_12310881 ] Ivelin Ivanov commented on JBMICROCONT-4: - [From Mladen] I don't like it. It has one major design flow and that is not allowing protocol stacking. As mater affect my humble apvfs is IMO the only virtual file system on the planet that allows that. For example I can use database-zip-memory, so you can have a zip file inside a database that will be managed on-the-fly. With jakarta vfs or even gnome vfs you will have to save that on the disk first and the do a second vfs open. Regards, Mladen. Virtual File System service --- Key: JBMICROCONT-4 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-4 Project: JBoss MicroContainer Type: Feature Request Reporter: Ivelin Ivanov Assignee: Dimitris Andreadis Priority: Critical Fix For: JBossMC_1_0_0M2 [Adrian] Ok, here is the design I have in mind for the new deployer aspects. This will be part of JBoss Kernel M2 release due by end of January. Deploying Deployers: First you have to be able to deploy a deployer. Not an easy task as I imagine the deployer will have dependencies on other services. The aim will be to minimize these dependencies to ease the problem. Basic Architecture: The basic architecture of the aspectized deployer is that the deployments work with a tree of DeploymentInfo objects just like the deployers do now. There are two major differences: 1) The deployers do not deal with urls, they deal with VFS contexts 2) The deployers do not create objects directly, instead they create kernel MetaData objects and submit them to the kernel for instantiation/configuration to obtain correct ordering of startup/shutdown Deployment Mode: The deployers work in two different modes 1) The first step is to ask who recognises the VFS context. This is so the responsible deployer can correctly decide which part of the context takes part in the classloading and where the metadata is located. Additionally, this may introduce subdeployments (VFS contexts) if the deployment allows/contains them. 2) The second step (the main chain) allows each deployer to augment the kernel metadata with its own config. Deployer Ordering: Since the deployers are working on a metadata model rather than constructing objects directly, there should be less problem with ordering. Most ordering will be in the classloader/instantiation/config stage, the deployer should insert that ordering in the form of dependencies in the metadata. The only ordering required of the deployer chain is where one deployer needs to work on the kernel metadata output of another deployer. Killing two birds with one stone: The problems mentioned with the deployer requiring other services and the first tasks performed by package specific deployers, i.e. identifying the deployment and its structure can be easily solved by splitting the deployers into two classes 1) A structural component that says I recognise this deployment and this is how it is structured 2) An interpretive component that creates the kernel metadata from the package. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of Clustering on JBoss (Clusters/JBoss)] - Re: Colocation and local optimization - JBAS-57
Only if the non HA invoker deployment also maintained the colocation info. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3859108#3859108 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859108 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of Clustering on JBoss (Clusters/JBoss)] - Re: Colocation and local optimization - JBAS-57
Ok, I thought you were indicating that the base InvokerInterceptor was going to be checking for existence in the collocation map which would require the non-ha proxy factories to maintain this info. Its a less intrusive change if the GUID continues to be a marker for non-ha collocation and only ha proxy factories maintain the explicit collocation mapping. This would require one new HAInvokerInterceptor as far as I can see. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3859110#3859110 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859110 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-3.2 build.224 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2?log=log20041217150400Lbuild.224 BUILD COMPLETE-build.224Date of build:12/17/2004 15:04:00Time to build:25 minutes 38 secondsLast changed:12/17/2004 10:18:39Last log entry:added missing MDB page, contributed by [EMAIL PROTECTED] Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(1)1.1.4.1modifiedanddconsole/src/resources/webconsole.war/MdbEjb.jspadded missing MDB page, contributed by [EMAIL PROTECTED]
[JBoss-dev] [Design of JBossCache] - Re: Problem in running the plain.bsh example
I am sure I am using jbosscache 1.2 as well, I download it from here: http://sourceforge.net/project/showfiles.php?group_id=22866package_id=102339 So what are the steps to fix the example? I am using Windows XP with jdk 1.4.2 Thank you. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3859112#3859112 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859112 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head build.594 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20041217160602Lbuild.594 BUILD COMPLETE-build.594Date of build:12/17/2004 16:06:02Time to build:34 minutes 31 secondsLast changed:12/17/2004 15:49:24Last log entry:Modified pointcut language to allow annotations as parameters and return types, i.e.:execution(@org.blah.Ann POJO-method(@org.blah.Ann) Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(9)1.21modifiedkabkhanaop/src/main/org/jboss/aop/pointcut/ast/pointcut.jjtModified pointcut language to allow annotations as parameters and return types, i.e.:execution(@org.blah.Ann POJO-method(@org.blah.Ann)1.24modifiedkabkhanaop/src/main/org/jboss/aop/pointcut/ast/PointcutExpressionParserTokenManager.javaModified pointcut language to allow annotations as parameters and return types, i.e.:execution(@org.blah.Ann POJO-method(@org.blah.Ann)1.18modifiedkabkhanaop/src/main/org/jboss/aop/pointcut/Util.javaModified pointcut language to allow annotations as parameters and return types, i.e.:execution(@org.blah.Ann POJO-method(@org.blah.Ann)1.7modifiedkabkhanaop/src/main/org/jboss/aop/annotation/PortableAnnotationElement.javaModified pointcut language to allow annotations as parameters and return types, i.e.:execution(@org.blah.Ann POJO-method(@org.blah.Ann)1.49modifiedkabkhanaop/src/main/org/jboss/aop/Advisor.javaModified pointcut language to allow annotations as parameters and return types, i.e.:execution(@org.blah.Ann POJO-method(@org.blah.Ann)1.63modifiedkabkhanaop/build.xmlModified pointcut language to allow annotations as parameters and return types, i.e.:execution(@org.blah.Ann POJO-method(@org.blah.Ann)1.27modifiedpatriot1burkeaspects/build.xmladd pluggable-instrumentor to dist1.6modifiedpatriot1burkecommon/src/main/org/jboss/util/id/GUID.javaGUID needs tob e Comparable1.1addedanddconsole/src/resources/webconsole.war/MdbEjb.jspbranches: 1.1.2; 1.1.4;added missing MDB page, contributed by [EMAIL PROTECTED]
[JBoss-dev] [Design of JBossCache] - Re: Problem in running the plain.bsh example
just do what I said. and run the demo see what happen. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3859119#3859119 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859119 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBossCache] - Re: I can' t run the example from the downloaded zip file.
I just downloaded the Standalone Beta 2, the jboss-cache-dist.zip. and it is working. so does it mean that JBossCache1.2 doesn't support standalone? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3859120#3859120 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859120 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAOP-55) Allow use of annotations for parameters in pointcuts
[ http://jira.jboss.com/jira/browse/JBAOP-55?page=history ] Kabir Khan closed JBAOP-55: --- Resolution: Done Allow use of annotations for parameters in pointcuts Key: JBAOP-55 URL: http://jira.jboss.com/jira/browse/JBAOP-55 Project: JBoss AOP Type: Bug Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 1.1 Should be possible to do: execution(* POJO-method(@Ann)) and execution(POJO-new(@Ann)) etc. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBossCache] - jbosscache and hibernate example
Hi, Can anyone please tell me where I can find example of how jbosscache uses with hibernate? thanks in advance for any pointer. thanks. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3859121#3859121 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859121 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossWS] - JBoss 4 and JbossWS - Xdoclet tags
Dear community,
I have a SessionBean that i have implemented as a WebService 1.1 compliant,
using the new wsee xdoclet tags in the new JBoss 4. I also have another class (
Calculadora) in my project that i use in the SessionBean, so that classe needs
to be serialized, because the sessionBean returns an object of the class's type
(see below).
public abstract class TestSessionBean implements TestSessionEndpoint,
SessionBean {
/**
* @ejb.interface-method
* view-type=service-endpoint
**/
public Calculadora Calc (int x, int y){
Calculadora tmp = new Calculadora();
tmp.setX(x);
tmp.setY(y);
tmp.multiplicacao();
return tmp ;
// and continues
}
I need to know what tags do i need to use (using JBoss 4.0.0), so that xdoclet
knows that class Calculadora, needs to be serialized and i could use then the
code above, to return an object in the Calc method. As it is now, compiles OK
but it doesnt deploy, JBoss 4 complains that it doesnt know
Calculadora.class
Thanks Herlander
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3859123#3859123
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859123
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of XDoclet Tags on JBoss (XDoclet/JBoss)] - JBoss 4 and JbossWS - Xdoclet tags
Dear community,
I have a SessionBean that i have implemented as a WebService 1.1 compliant,
using the new wsee xdoclet tags in the new JBoss 4. I also have another class (
Calculadora) in my project that i use in the SessionBean, so that classe needs
to be serialized, because the sessionBean returns an object of the class's type
(see below).
public abstract class TestSessionBean implements TestSessionEndpoint,
SessionBean {
/**
* @ejb.interface-method
* view-type=service-endpoint
**/
public Calculadora Calc (int x, int y){
Calculadora tmp = new Calculadora();
tmp.setX(x);
tmp.setY(y);
tmp.multiplicacao();
return tmp ;
// and continues
}
I need to know what tags do i need to use (using JBoss 4.0.0), so that xdoclet
knows that class Calculadora, needs to be serialized and i could use then the
code above, to return an object in the Calc method. As it is now, compiles OK
but it doesnt deploy, JBoss 4 complains that it doesnt know
Calculadora.class
Thanks Herlander
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3859124#3859124
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859124
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head-jdk-matrix build.36 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20041217224106Lbuild.36 BUILD COMPLETE-build.36Date of build:12/17/2004 22:41:06Time to build:24 minutes 44 secondsLast changed:12/17/2004 15:49:26Last log entry:Modified pointcut language to allow annotations as parameters and return types, i.e.:execution(@org.blah.Ann POJO-method(@org.blah.Ann) Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(98)1.1addedkabkhanaop/src/test/org/jboss/test/aop/annotatedparams/AnnotatedParamsTester.javaModified pointcut language to allow annotations as parameters and return types, i.e.:execution(@org.blah.Ann POJO-method(@org.blah.Ann)1.1addedkabkhanaop/src/test/org/jboss/test/aop/annotatedparams/POJO.javaModified pointcut language to allow annotations as parameters and return types, i.e.:execution(@org.blah.Ann POJO-method(@org.blah.Ann)1.1addedkabkhanaop/src/test/org/jboss/test/aop/annotatedparams/Param.javaModified pointcut language to allow annotations as parameters and return types, i.e.:execution(@org.blah.Ann POJO-method(@org.blah.Ann)1.1addedkabkhanaop/src/test/org/jboss/test/aop/annotatedparams/ParamType.javaModified pointcut language to allow annotations as parameters and return types, i.e.:execution(@org.blah.Ann POJO-method(@org.blah.Ann)1.1addedkabkhanaop/src/test/org/jboss/test/aop/annotatedparams/Return.javaModified pointcut language to allow annotations as parameters and return types, i.e.:execution(@org.blah.Ann POJO-method(@org.blah.Ann)1.1addedkabkhanaop/src/test/org/jboss/test/aop/annotatedparams/ReturnType.javaModified pointcut language to allow annotations as parameters and return types, i.e.:execution(@org.blah.Ann POJO-method(@org.blah.Ann)1.1addedkabkhanaop/src/test/org/jboss/test/aop/annotatedparams/SimpleInterceptor.javaModified pointcut language to allow annotations as parameters and return types, i.e.:execution(@org.blah.Ann POJO-method(@org.blah.Ann)1.1addedkabkhanaop/src/resources/test/annotatedparams/jboss-aop.xmlModified pointcut language to allow annotations as parameters and return types, i.e.:execution(@org.blah.Ann POJO-method(@org.blah.Ann)1.21modifiedkabkhanaop/src/main/org/jboss/aop/pointcut/ast/pointcut.jjtModified pointcut language to allow annotations as parameters and return types, i.e.:execution(@org.blah.Ann POJO-method(@org.blah.Ann)1.24modifiedkabkhanaop/src/main/org/jboss/aop/pointcut/ast/PointcutExpressionParserTokenManager.javaModified pointcut language to allow annotations as parameters and return types, i.e.:execution(@org.blah.Ann POJO-method(@org.blah.Ann)1.18modifiedkabkhanaop/src/main/org/jboss/aop/pointcut/Util.javaModified pointcut language to allow annotations as parameters and return types, i.e.:execution(@org.blah.Ann POJO-method(@org.blah.Ann)1.7modifiedkabkhanaop/src/main/org/jboss/aop/annotation/PortableAnnotationElement.javaModified pointcut language to allow annotations as parameters and return types, i.e.:execution(@org.blah.Ann POJO-method(@org.blah.Ann)1.49modifiedkabkhanaop/src/main/org/jboss/aop/Advisor.javaModified pointcut language to allow annotations as parameters and return types, i.e.:execution(@org.blah.Ann POJO-method(@org.blah.Ann)1.63modifiedkabkhanaop/build.xmlModified pointcut language to allow annotations as parameters and return types, i.e.:execution(@org.blah.Ann POJO-method(@org.blah.Ann)1.27modifiedpatriot1burkeaspects/build.xmladd pluggable-instrumentor to dist1.6modifiedpatriot1burkecommon/src/main/org/jboss/util/id/GUID.javaGUID needs tob e Comparable1.1addedanddconsole/src/resources/webconsole.war/MdbEjb.jspbranches: 1.1.2; 1.1.4;added missing MDB page, contributed by [EMAIL PROTECTED]1.4modifiedstarksmtestsuite/src/main/org/jboss/test/security/ejb/CallerBean.javaAdd the mising callEcho method implementation needed by the deepRunAs test1.22modifiedstarksmserver/src/main/org/jboss/security/SecurityAssociation.javaThere was an off by one error in the run-as identity stack calculation. This really fixes [ 1041273 ] Run-as Identity not propagated.1.29modifiedstarksmtestsuite/imports/test-jars.xmlComment out the ejb-timer.* stuff for now.1.28modifiedanddtestsuite/imports/test-jars.xmlEJBDeployer is xmbean-ized and so can be configured with deployment interceptorsSubDeployerInterceptor is an abstract base class for deployment interceptorsLoginConfigInterceptor handles automatic security domain creation/destruction upon deployment/undeployment1.1addedanddtestsuite/src/main/org/jboss/test/security/test/LoginConfigInterceptorUnitTestCase.javaEJBDeployer is xmbean-ized and so can be configured with deployment interceptorsSubDeployerInterceptor is an abstract base class for deployment interceptorsLoginConfigInterceptor handles automatic security domain creation/destruction upon
[JBoss-dev] [JBoss JIRA] Created: (JBREM-24) Allow for specific network interface bindings
Allow for specific network interface bindings - Key: JBREM-24 URL: http://jira.jboss.com/jira/browse/JBREM-24 Project: JBoss Remoting Type: Feature Request Components: transport Versions: 1.0.1 alpha Reporter: Tom Elrod Assigned to: Tom Elrod Need ability for address bindings for particular network interfaces. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0-testsuite build.21 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20041217232106Lbuild.21 BUILD COMPLETE-build.21Date of build:12/17/2004 23:21:06Time to build:91 minutes 0 secondsLast changed:12/17/2004 13:14:35Last log entry:[JBAS-65] - Parse the standard JMS activation configuration from JCA1.5 appendix BThis allows EJB2.1 style JMS MDB deployments to be processed through the currently more stable JMSContainerInvoker Unit Tests: (2177) Total Errors and Failures: (41)testEjbInterceptionorg.jboss.test.hibernate.test.HibernateIntgUnitTestCaseunknownorg.jboss.test.jbossmq.test.LargeMessageUnitTestCaseunknownorg.jboss.test.jbossmq.test.OILConnectionUnitTestCaseunknownorg.jboss.test.security.test.SRPUnitTestCasetestEjbFinderorg.jboss.test.securitymgr.test.BMPUnitTestCasetestEjbRemoveorg.jboss.test.securitymgr.test.BMPUnitTestCasetestEjbLifeCycleorg.jboss.test.securitymgr.test.BMPUnitTestCasetestPrimaryKeyObjectIdentityorg.jboss.test.securitymgr.test.BMPUnitTestCasetestEjbRemoteIForg.jboss.test.securitymgr.test.BMPUnitTestCasetestEntityHandleorg.jboss.test.securitymgr.test.BMPUnitTestCasetestSessionHandleNoDefaultJNDIorg.jboss.test.securitymgr.test.BMPUnitTestCasetestProbeContainerCallbacksorg.jboss.test.securitymgr.test.BMPUnitTestCasetestContainerObjectsorg.jboss.test.securitymgr.test.BMPUnitTestCasetestUserTransactionorg.jboss.test.securitymgr.test.BMPUnitTestCasetestServerFoundorg.jboss.test.securitymgr.test.BMPUnitTestCaseunknownorg.jboss.test.securitymgr.test.BMPUnitTestCasetestConcurrentPutAndEvictorg.jboss.test.cache.test.eviction.LRUPolicyUnitTestCasetestEvictionorg.jboss.test.cache.test.eviction.ReplicatedLRUPolicyUnitTestCasetestEvictionReplicationorg.jboss.test.cache.test.eviction.ReplicatedLRUPolicyUnitTestCasetestThreadedAccess_RWLockorg.jboss.test.cache.test.generic.IdentityLockUnitTestCasetestThreadedAccess_SimpleLockorg.jboss.test.cache.test.generic.IdentityLockUnitTestCasetestStateTransferorg.jboss.test.cache.test.replicated.AsyncUnitTestCasetestSyncReplorg.jboss.test.cache.test.replicated.AsyncUnitTestCasetestSyncReplorg.jboss.test.cache.test.replicated.SyncTxUnitTestCasetestASyncReplorg.jboss.test.cache.test.replicated.SyncTxUnitTestCasetestPutorg.jboss.test.cache.test.replicated.SyncTxUnitTestCasetestStateReplicationorg.jboss.test.cluster.test.DRMTestCasetestCreateOrganizationorg.jboss.test.jaxr.create.CreateOrganizationTestCasetestJaxrDeleteorg.jboss.test.jaxr.delete.JaxrDeleteTestCasetestJaxrReadorg.jboss.test.jaxr.read.JaxrReadTestCasetestEjbCreateorg.jboss.test.securitymgr.test.BMPUnitTestCasetestRestoreToEntityorg.jboss.test.txtimer.test.PersistenceTestCasetestRestoreToSessionorg.jboss.test.txtimer.test.PersistenceTestCasetestPersistenceEqualityorg.jboss.test.txtimer.test.PersistenceTestCase Modifications since last build:(46)1.64.2.2modifiedejortserver/src/main/org/jboss/ejb/plugins/jms/JMSContainerInvoker.java[JBAS-65] - Parse the standard JMS activation configuration from JCA1.5 appendix BThis allows EJB2.1 style JMS MDB deployments to be processed through the currently more stable JMSContainerInvoker1.9.2.33modifiedejorttestsuite/imports/test-jars.xmlAdd a test for EJB2.1 MDB style deployment deployed through the JMSContainerInvoker1.1.2.1modifiedejorttestsuite/src/main/org/jboss/test/messagedriven/support/JMSContainerInvokerTest.javaAdd a test for EJB2.1 MDB style deployment deployed through the JMSContainerInvoker1.1.2.1modifiedejorttestsuite/src/main/org/jboss/test/messagedriven/test/JMSContainerInvokerMessageDrivenUnitTestCase.javaAdd a test for EJB2.1 MDB style deployment deployed through the JMSContainerInvoker1.5.6.1modifiedpatriot1burkecommon/src/main/org/jboss/util/id/GUID.javaMake GUID Comparable1.12.4.1modifiedejortcache/.classpathFix the eclipse build1.18.2.1modifiedstarksmtestsuite/src/main/org/jboss/test/cmp2/commerce/QueryTest.javaDisable two of the exact string match tests as the order query elements cannot really be guarenteed. These tests should be validating the parse tree.1.1.2.1modifiedanddconsole/src/resources/webconsole.war/MdbEjb.jspadded missing MDB page, contributed by [EMAIL PROTECTED]1.19.2.3modifiedstarksmserver/src/main/org/jboss/security/SecurityAssociation.javaThere was an off by one error in the run-as identity stack calculation. This really fixes [ 1041273 ] Run-as Identity not propagated.1.2.16.2modifiedstarksmtestsuite/src/main/org/jboss/test/security/ejb/CallerBean.javaAdd the mising callEcho method implementation needed by the deepRunAs test1.6.6.1modifiedstarksmtestsuite/src/main/org/jboss/test/jbossmx/implementation/server/ContextCLTestCase.javaIf this is running under java5 run no tests as there is no guarentee of what the class loader of the mbean is.1.2.6.1modifiedejortmessaging/src/etc/server/examples/deploy/standalone/build.xmlUpdate the standalone JBossMQ build for the
[JBoss-dev] jboss-4.0-jdk-matrix build.41 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-jdk-matrix?log=log20041218010425Lbuild.41
BUILD COMPLETE-build.41Date of build:12/18/2004 01:04:25Time to build:25 minutes 52 secondsLast changed:12/17/2004 13:14:35Last log entry:[JBAS-65] - Parse the standard JMS activation configuration from JCA1.5 appendix BThis allows EJB2.1 style JMS MDB deployments to be processed through the currently more stable JMSContainerInvoker
Unit Tests: (0) Total Errors and Failures: (0)
Modifications since last build:(47)1.64.2.2modifiedejortserver/src/main/org/jboss/ejb/plugins/jms/JMSContainerInvoker.java[JBAS-65] - Parse the standard JMS activation configuration from JCA1.5 appendix BThis allows EJB2.1 style JMS MDB deployments to be processed through the currently more stable JMSContainerInvoker1.1.2.1modifiedejorttestsuite/src/resources/messagedriven/jmscontainerinvoker/META-INF/ejb-jar.xmlAdd a test for EJB2.1 MDB style deployment deployed through the JMSContainerInvoker1.9.2.33modifiedejorttestsuite/imports/test-jars.xmlAdd a test for EJB2.1 MDB style deployment deployed through the JMSContainerInvoker1.1.2.1modifiedejorttestsuite/src/main/org/jboss/test/messagedriven/support/JMSContainerInvokerTest.javaAdd a test for EJB2.1 MDB style deployment deployed through the JMSContainerInvoker1.1.2.1modifiedejorttestsuite/src/main/org/jboss/test/messagedriven/test/JMSContainerInvokerMessageDrivenUnitTestCase.javaAdd a test for EJB2.1 MDB style deployment deployed through the JMSContainerInvoker1.5.6.1modifiedpatriot1burkecommon/src/main/org/jboss/util/id/GUID.javaMake GUID Comparable1.12.4.1modifiedejortcache/.classpathFix the eclipse build1.18.2.1modifiedstarksmtestsuite/src/main/org/jboss/test/cmp2/commerce/QueryTest.javaDisable two of the exact string match tests as the order query elements cannot really be guarenteed. These tests should be validating the parse tree.1.1.2.1modifiedanddconsole/src/resources/webconsole.war/MdbEjb.jspadded missing MDB page, contributed by [EMAIL PROTECTED]1.19.2.3modifiedstarksmserver/src/main/org/jboss/security/SecurityAssociation.javaThere was an off by one error in the run-as identity stack calculation. This really fixes [ 1041273 ] Run-as Identity not propagated.1.2.16.2modifiedstarksmtestsuite/src/main/org/jboss/test/security/ejb/CallerBean.javaAdd the mising callEcho method implementation needed by the deepRunAs test1.6.6.1modifiedstarksmtestsuite/src/main/org/jboss/test/jbossmx/implementation/server/ContextCLTestCase.javaIf this is running under java5 run no tests as there is no guarentee of what the class loader of the mbean is.1.2.6.1modifiedejortmessaging/src/etc/server/examples/deploy/standalone/build.xmlUpdate the standalone JBossMQ build for the JBoss4 changes.1.2.6.1modifiedejortmessaging/src/etc/server/examples/deploy/standalone/jboss-service.xmlUpdate the standalone JBossMQ build for the JBoss4 changes.1.9.2.32modifiedstarksmtestsuite/imports/test-jars.xmlUpdate the exception.jar to use the jboss EJBTestCase1.5.6.1modifiedstarksmtestsuite/src/resources/exception/META-INF/ejb-jar.xmlUpdate to test remote and local security exception propagation1.5.6.1modifiedstarksmtestsuite/src/resources/exception/META-INF/jboss.xmlUpdate to test remote and local security exception propagation1.2.6.1modifiedstarksmtestsuite/src/main/org/jboss/test/exception/EntityExceptionTesterLocal.javaUpdate to test remote and local security exception propagation1.3.4.1modifiedstarksmtestsuite/src/main/org/jboss/test/exception/EntityExceptionUnitTestCase.javaUpdate to test remote and local security exception propagation1.4.6.1modifiedstarksmtestsuite/src/main/org/jboss/test/exception/ExceptionTester.javaUpdate to test remote and local security exception propagation1.6.6.1modifiedstarksmtestsuite/src/main/org/jboss/test/exception/ExceptionTesterBean.javaUpdate to test remote and local security exception propagation1.7.6.1modifiedstarksmtestsuite/src/main/org/jboss/test/exception/ExceptionTesterLocal.javaUpdate to test remote and local security exception propagation1.7.6.1modifiedstarksmtestsuite/src/main/org/jboss/test/exception/ExceptionUnitTestCase.javaUpdate to test remote and local security exception propagation1.2.4.4modifiedstarksmserver/src/main/org/jboss/ejb/plugins/JaasAuthenticationInterceptor.javaLook to the SecurityAssociation context exception on authentication failure and throw that exception if not null. If there is no SecurityAssociation context exception, throw the current SecurityException("Authentication ..."). Fixes [JBAS-47] Support for jaas CredentialExpiredException and AccountExpiredException.1.46.4.4modifiedstarksmserver/src/main/org/jboss/ejb/plugins/SecurityInterceptor.javaLook to the SecurityAssociation context exception on authentication failure and throw that exception if not null. If there is no SecurityAssociation
