Thanks for sharing your project. I've done outbound connection pools before
but never inbound, so it's great to have a sample.
--
View this message in context:
http://tomee-openejb.979440.n4.nabble.com/Strange-resource-adapter-error-message-tp4674170p4674177.html
Sent from the TomEE Users
Jean-Louis MONTEIRO wrote
JCA (outbound connection pool with transaction support)
Very cool part of Java EE but not well known.
So true. I've actually never met anyone in person that has built a JCA
adapter. Most people try to solve the problem JCA solves by re-inventing
the wheel and
EJB3 (singletons, transactions and asynchronous)
JMS
JAX-WS (client and server)
JAX-RS (client and server)
JSF (only for html rendering of JAX-RS responses)
CDI (how can you not use it?)
JTA
JPA
Servlets
Filters
JCA (outbound connection pool with transaction support)
--
View this message in
Any change of getting a cxf upgrade with this release? If not to cxf3, then
at least cxf2.7.x? Just thought i'd ask since i really want the nio client
capability :)
--
View this message in context:
http://tomee-openejb.979440.n4.nabble.com/Tomee-1-7-2-Release-Date-tp4673133p4673148.html
Sent
Thanks brilliant. I thought i'd have to wait for 2.0 for it.
--
View this message in context:
http://tomee-openejb.979440.n4.nabble.com/Tomee-1-7-2-Release-Date-tp4673133p4673150.html
Sent from the TomEE Users mailing list archive at Nabble.com.
Ok i think i misunderstood. I was assuming 1.7.2 would be released before
2.0 and if so, it would be nice to get cfx 2.7 or higher in that release. I
just checked the 1.7.x branch and see cxf.version is 2.6.14 in the pom.xml
so guess it's not in scope to upgrade it for 1.7.2?
--
View this
I just tested this again because I remember at the time i used
classpath:... in the wsdlLocation i saw error messages in the log file
when booting up tomee. I have confirmed this just now but I have been
ignoring this error message because it doesn't seem to stop my application
from working
Actually looks like i do still get the error message in the log file when
using the relative path form of wsdlLocation...
Dec 01, 2014 10:48:27 AM org.apache.openejb.config.WsDeployer getWsdl
SEVERE: Unable to read wsdl file
META-INF/wsdl/AcceptPaymentForAncillaries.wsdl
Just missed it before
rherschke wrote
The problem isn't regarding the development of a JCA Resource Adapter, but
about configuring and referencing it in Tomee.
...
I see, that there is an undocumented way to create Per-App-Instances of a
Resource via
Resource ... class=...
(rather than type=..., as
This is interesting because I found i had to use classpath:... in
wsdlLocation when i was setting up tomee to reuse a single JAXBContext like
follows...
@Stateless
@Local(AcceptPaymentForAncillariesPortType.class)
@WebService(
portName=AcceptPaymentForAncillariesPortType,
I worked on a JCA adapter recently in tomee so know what you're going
through.
I created a very basic JCA skeleton project that contains a very simple jca
adapter and a single test case that loads the resource adapter in tomee and
injects the connection factory. You can see this project here...
I have been trying to use moxy as the JAXBContext implementation in tomee and
have had some issues. I had the following war file...
moxy-test.war
|-WEB-INF
|-lib
|-config-moxy.jar
|- META-INF
|- services
|-javax.xml.bind.JAXBContext
The content of the
I'm creating a jaxws client and want to use the same jaxbcontexts used to
marshal the jaxb objects to xml to also marshal to json in a Handler for
indexing the web service requests and responses in elastic search. The
default JAXBContext can't marshal to json, so i need to use moxy. I tried
I'm have been trying out using cxf3 with apache-tomee-webprofile-1.7.0 and
testing to see if i can create some jaxrs services. I've hit a problem when
i use a jax-rs annotation.
In my pom.xml i have this...
dependency
groupIdorg.apache.cxf/groupId
artifactIdcxf-integration-cdi/artifactId
great work!
--
View this message in context:
http://tomee-openejb.979440.n4.nabble.com/Apache-TomEE-1-7-0-Release-tp4671162p4671201.html
Sent from the TomEE Users mailing list archive at Nabble.com.
MarkusFrisch wrote
If so - what would you recommend as a replacement?
You could always use apache cxf which is bundled with tomee.
--
View this message in context:
http://tomee-openejb.979440.n4.nabble.com/Application-that-contains-jersey-fails-to-start-tp4671125p4671129.html
Sent from the
Are you using contract first (ie. you have the WSDL already and need to
create the web service implementation for it), or code first (you have no
WSDL and just want to write the code and generate the WSDL)?
--
View this message in context:
Alexander Wagner wrote
At this point our big question is the IDE Support. The Eclipse Support
for Tomcat/TomEE over the WTP-Connector is excellent, but it covers only
War-Projects. So I tried the OpenEJB Eclipse Plugin
(https://openejb.apache.org/openejb-eclipse-plugin.html). First of all,
Using the 2.7.X conduit from tomee-plus-1.6.0 is proving to be difficult. It
seems ok if i'm not hosting any web services, but when i try it from a web
service (ie. call an external web service from my own web service), then it
throws lots of different types of exceptions (ClassNotFound etc). It
Romain Manni-Bucau wrote
I'd like to
get 2.0.x-alpha where we are neither javaee 7 nor certified but in between
ee6 and 7 where we could have cxf 3
Sounds good. Lack of certification isn't a big issue for me compared to
getting NIO capability for calling web services. After playing with
Romain Manni-Bucau wrote
Wonder if you can't
simply use cxf 3/2.7 async conduit with cxf 2. It is theorytically
possible, would need to check the modularity of cxf for it.
I'll try this approach.
I have another question related to this. I'm performing the webservice
invokeAsync calls from
I have a project running in tomee and i've just implemented using jax-ws
asynchronous web service calls.
Do jax-ws async calls use a different async thread pool to the pool
configured using AsynchronousPool.CorePoolSize?
Does cxf use nio by default for async web service calls?
Thanks,
I might wait for tomee 1.7. That's coming soon right? :)
--
View this message in context:
http://tomee-openejb.979440.n4.nabble.com/Is-there-a-CXF-Async-thread-pool-tp4670492p4670501.html
Sent from the TomEE Users mailing list archive at Nabble.com.
How do i configure the cxf async pool in tomee 1.6? I'm looking for the name
of property similar to the AsynchronousPool.CorePoolSize that i can put in
system.properties?
--
View this message in context:
Sorry to ask but is there an expected release date for tomee 2.0? I can't
use snapshot versions, so have to wait for the release. Also i'm using
apache-tomee-plus so don't feel comfortable replacing the cxf version of the
libs.
--
View this message in context:
I implemented using the ResourceAsService wrapper as you suggested and it
works. I think that ResourceAsService could be useful enough to be included
in tomee.
My ResourceAsService class is
public class ResourceAsService {
private String resourceId;
public String
Using @resourceId would be even better. I was wishing for that the last
few days.
Cheers,
Anthony
--
View this message in context:
http://openejb.979440.n4.nabble.com/Use-single-JAXBContext-for-multiple-web-services-tp4670019p4670026.html
Sent from the OpenEJB User mailing list archive at
I've managed (after lots of pain and suffering) to get my web services using
the same JAXBContext. The great thing is this significantly speeds up my
tomee boot time. Before, tomee was taking 37594 ms to boot and now it is
taking 10150 ms, so the performance gain is massive. The steps i went
Is it possible to configure a single JAXBContext to be reused by multiple
JAX-WS web services? I want to test this to see if it speeds up my boot
time and uses less memory.
Searching on the web, i've found this link...
https://www.mail-archive.com/users@cxf.apache.org/msg35563.html
This
I was hoping there was more to it than that. Like being able to inject
interceptors and do away with config in resources.xml and openejb-jar.xml.
--
View this message in context:
http://openejb.979440.n4.nabble.com/cxf-advanced-examples-tp4669927p4669937.html
Sent from the OpenEJB User
I know you're right and usually at some point we have to configure something
that is specific to an implementation.
--
View this message in context:
http://openejb.979440.n4.nabble.com/cxf-advanced-examples-tp4669927p4669942.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
Hwaastad, just interested to know where you are? I used to live in
Switerland and going snowboarding in the swiss and french alps. Your pic
looks like that. Am i close?
--
View this message in context:
http://openejb.979440.n4.nabble.com/cxf-advanced-examples-tp4669927p4669947.html
Sent
I have a simple cxf interceptor in a project that just forces the text of an
xml element in a web service response to be wrapped in a CDATA element. It
would probably make for a good example.
There's 2 classes I have to implement the interceptor...
public class CDataContentWriter extends
It might be related to jaxb context initialization since i have 274 jaxb
classes.
--
View this message in context:
http://openejb.979440.n4.nabble.com/Web-Services-slow-down-boot-time-tp4669495p4669574.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
I just thought i would mention that i have noticed when booting tomEE,
initialization of EJBs is really quick, but when my web services initialize
in the container, they take about 1 second each. I have a project with
about 17 web services and now i'm really noticing the web service
It's JAXWS
--
View this message in context:
http://openejb.979440.n4.nabble.com/Web-Services-slow-down-boot-time-tp4669495p4669534.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
I don't have a post construct.
Here's some of the console log output showing the webservices being
deployed. From the timestamp, you can see the StartEjbs is really quick
(all ejbs start in about 1 second) and then the
org.apache.openejb.server.webservices.WsService deployApp is noticably
slower
I think Java Application Servers left a bad impression on alot of people back
in the early ejb2/jsf1 days. It wasn't only the specs that were not great
(ie. ejb2 entity beans) but also the containers that were implemented were
incredibly resource hungry memory pigs that took an eternity to boot
Hi Ivan,
I duplicated your results using the test case you uploaded and saw a steady
performance degredation. I was wondering if this was related to jpa, or the
fact you're using ejb2, so i created a similar test case using ejb 3 entity
beans, based on the injection-of-entitymanager test case.
You can create a persistence.xml in your WEB-INF folder and reference jar
files in your WEB-INF/lib using the jar-files element. I normally put jar
files into WEB-INF/lib and put persistence.xml in /META-INF of those jar
files.
You could create a remote ejb interface and pass your entity classes
This might help...
http://openejb.979440.n4.nabble.com/TomEE-CXF-Configuration-td4631682.html#a4651270
--
View this message in context:
http://openejb.979440.n4.nabble.com/Changing-the-URL-for-SOAP-WebService-tp4667258p4667260.html
Sent from the OpenEJB User mailing list archive at
+1
Stateless views will be nice.
--
View this message in context:
http://openejb.979440.n4.nabble.com/When-will-MyFaces-2-2-x-be-bundled-with-TomEE-1-6-x-tp4667185p4667194.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
So there's a sync thread pool (ie. when called by a HttpServletRequest) and
if that thread calls a stateless session EJB method synchronously, it uses
that same thread and is only limited by the stateless session pool size. If
an async call is made, then is uses the async thread pool (default
Interesting to know that there are separate sync and async pools. I would
have assumed that you would configure a pool for stateless session beans
that would be used for both sync and async. But i can see that could cause
potential thread deadlocks so you need a dedicated async thread pool. But
Could it be because you're using JSF managed beans instead of CDI?
--
View this message in context:
http://openejb.979440.n4.nabble.com/doubt-about-scopes-tp4666709p4666726.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
Maybe move your jms consumers into a different app from your webapp?
--
View this message in context:
http://openejb.979440.n4.nabble.com/Looking-for-some-advice-about-EJB-JMS-and-Quartz-with-TomEE-1-6-0-tp4666342p4666359.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
Leonardo K. Shikida wrote
Last but not least, I've experiencing some strange problems probably
related to the classloader, and I've removed xerces-impl-2.11.0.jar from
eclipse factory path (java compiler - annotation processing - factory
path, to generate openJPA metamodel classes for Criteria
I've just deployed an application that i had running in tomee1.5.2 into tomee
1.6.0. When the application starts up, i get the following error printed
out to the console that i didn't get when deploying to tomee 1.5.2. Any
ideas what might be causing this?
25/11/2013 3:28:13 PM
I think it is because TransactionAttributeType.REQUIRED is the default used
if you don't specify anything.
--
View this message in context:
http://openejb.979440.n4.nabble.com/TransactionAttribute-tp4665000p4665001.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
I was wondering if it is possible to inject a cxf jax-ws client using the
@WebServiceRef annotation? My scenario is that there is a web service that
is running in an external system that i want to call from a stateless ejb.
I have run wsimport over the WSDL to generate the service
It may be that I don't understand @WebServiceRef very well, but I don't see
much value in using it in my case. If I still have to programmatically
configure endpoint address and security headers I think I might be better
off using @Produces method to return a configured SEI. Am I missing
I worked on a JCA adapter recently and got it running in weblogic and tomee.
some links that might help...
http://openejb.979440.n4.nabble.com/openejb-not-destroying-ManagedConnections-on-shutdown-td4658799.html#a4658979
Leonardo K. Shikida wrote
that's probably because I am running tomEE from inside eclipse, and its
configuration is messing the class loading process
Running tomee inside eclipse should work exactly the same as outside
eclipse but you may need the right plugins depending on how you build
things.
Maybe try the autoReconnect=true option at the end of the JdbcUrl
eg.
Resource id=MySQL Database type=DataSource
JdbcDriver com.mysql.jdbc.Driver
JdbcUrl
jdbc:mysql://localhost:3306/lemonadeStand?autoReconnect=true
UserName lc
You should be able to inject the mail session directly into your unit test.
I have a unit test that accesses the mail session through injection. It
looks like this...
public class EmailServiceEJBTest {
final static Logger logger =
LoggerFactory.getLogger(EmailServiceEJBTest.class);
forgot to post the @Before method, which is important...
@Before
public void before() throws NamingException, LiquibaseException,
SQLException {
ejbContainer.getContext().bind(inject, this);
}
--
View this message in context:
Can't wait for JSR 352 Batch Applications for the Java Platform. Looks very
much like spring batch which i have used and thought was one of the best
spring modules that had no equivalent in jee.
--
View this message in context:
It would be nice to know how you have ActiveMQ configured when you get these
sorts of issues. Are you using in-memory, file or rdbms persistence store?
--
View this message in context:
http://openejb.979440.n4.nabble.com/Question-on-MDB-processing-tp4661685p4661742.html
Sent from the OpenEJB
Thanks for fixing this in 1.6.0. Any idea when that version will be
released?
For version 1.5.1, i have tried setting the openejb.provider.default
property as you suggested but it hasn't fixed the problem. My
arquillian.xml file is...
arquillian
I found this link which describes a similar configuration of a
JacksonJsonProvider but using spring...
http://wolfe.id.au/2011/05/22/using-jackson-with-apache-cxf/
--
View this message in context:
I have a test case using tomee-embedded and have some jaxrs services
configured to have basic authentication in web.xml. When i try to logon in
my test case, I get the following exception...
java.lang.ClassCastException:
org.apache.openejb.core.security.SecurityServiceImpl cannot be cast to
61 matches
Mail list logo