[JBoss AOP] - Re: jboss aop with activebpel
by flavia.rainone＠jboss.com
I think that using the JBoss AS can make things simpler because of the AOP Deployer (basically, this component will allow you to use JBoss AOP without setting aoppath and other environment variables, and it will be easier to run the server with JBoss AOP enabled). Besides, dynamic AOP is available through deployment and undeployment of .aop components, which means that you don't have to perform any Java calls to enable and disable aspects.
Regarding running things from inside Eclipse, I don't think it would bring you any advantages or disadvantages.
As a reminder, the JBoss AOP plugin for Eclipse is outdated and is not going to work. We have plans to fix this in the future.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4148842#4148842
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4148842
17 years, 11 months
[JBossWS] - Using the same Remote Interface for different services????
by felle82
Hi all,
Is it possible to use the same remote interface for different services within one application. I have two services with the same interface using JAX-WS. They are in two different jars but in one EAR. Of course there are different implementations for the beans. One is a publish-subscribe component and the other is a subscriber but they both should implement the same consumer interface.
I use different namespaces and service names and when I deploy them, I get different endpoints.
@WebService(name="ConsumerTest", targetNamespace="http://xyz.com/sii/testconsumer")
| @Remote
| public interface ConsumerRemote {
|
| @WebMethod(operationName="notify")
| @WebResult(name = "result")
| public String notify(@WebParam(name="topic")
| String topic,@WebParam(name="message")
| Object message);
|
| }
@WebService(name="ConsumerService", targetNamespace="http://xyz.com/sii/pubsub/consumer")
| @Remote
| public interface ConsumerRemote {
|
| @WebMethod(operationName="notify")
| @WebResult(name = "result")
| public String notify(@WebParam(name="topic")
| String topic,@WebParam(name="message")
| Object message);
|
| }
But behind that endpoint the wsdls for both are the same with the same namespace and service name. Hence the service invocation is done by the same bean implementation. I have to change the package or class name of one interface (and bean) to get different wsdls.
Any solutions for that?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4148837#4148837
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4148837
17 years, 11 months
[Messaging, JMS & JBossMQ] - Re: How to access JBOSS by providing IP address
by priyarao234
dis s my complete server.xml
<!--APR library loader. Documentation at /docs/apr.html -->
<!--Initialize Jasper prior to webapps are loaded. Documentation at /docs/jasper-howto.html -->
<!-- Use a custom version of StandardService that allows the
connectors to be started independent of the normal lifecycle
start to allow web apps to be deployed before starting the
connectors.
-->
<!-- A "Connector" represents an endpoint by which requests are received
and responses are returned. Documentation at :
Java HTTP Connector: /docs/config/http.html (blocking & non-blocking)
Java AJP Connector: /docs/config/ajp.html
APR (HTTP/AJP) Connector: /docs/apr.html
Define a non-SSL HTTP/1.1 Connector on port 8080
-->
<!-- Define a SSL HTTP/1.1 Connector on port 8443
This connector uses the JSSE configuration, when using APR, the
connector should be using the OpenSSL style configuration
described in the APR documentation -->
<!--
-->
<!-- Define an AJP 1.3 Connector on port 8009 -->
<!-- The JAAS based authentication and authorization realm implementation
that is compatible with the jboss 3.2.x realm implementation.
- certificatePrincipal : the class name of the
org.jboss.security.auth.certs.CertificatePrincipal impl
used for mapping X509[] cert chains to a Princpal.
- allRolesMode : how to handle an auth-constraint with a role-name=*,
one of strict, authOnly, strictAuthOnly
+ strict = Use the strict servlet spec interpretation which requires
that the user have one of the web-app/security-role/role-name
+ authOnly = Allow any authenticated user
+ strictAuthOnly = Allow any authenticated user only if there are no
web-app/security-roles
-->
<!-- A subclass of JBossSecurityMgrRealm that uses the authentication
behavior of JBossSecurityMgrRealm, but overrides the authorization
checks to use JACC permissions with the current java.security.Policy
to determine authorized access.
- allRolesMode : how to handle an auth-constraint with a role-name=*,
one of strict, authOnly, strictAuthOnly
+ strict = Use the strict servlet spec interpretation which requires
that the user have one of the web-app/security-role/role-name
+ authOnly = Allow any authenticated user
+ strictAuthOnly = Allow any authenticated user only if there are no
web-app/security-roles
-->
<!-- Uncomment to enable request dumper. This Valve "logs interesting
contents from the specified Request (before processing) and the
corresponding Response (after processing). It is especially useful
in debugging problems related to headers and cookies."
-->
<!--
-->
<!-- Access logger -->
<!--
-->
<!-- Uncomment to enable single sign-on across web apps
deployed to this host. Does not provide SSO across a cluster.
If this valve is used, do not use the JBoss ClusteredSingleSignOn
valve shown below.
A new configuration attribute is available beginning with
release 4.0.4:
cookieDomain configures the domain to which the SSO cookie
will be scoped (i.e. the set of hosts to
which the cookie will be presented). By default
the cookie is scoped to "/", meaning the host
that presented it. Set cookieDomain to a
wider domain (e.g. "xyz.com") to allow an SSO
to span more than one hostname.
-->
<!--
-->
<!-- Uncomment to enable single sign-on across web apps
deployed to this host AND to all other hosts in the cluster.
If this valve is used, do not use the standard Tomcat SingleSignOn
valve shown above.
Valve uses a JBossCache instance to support SSO credential
caching and replication across the cluster. The JBossCache
instance must be configured separately. By default, the valve
shares a JBossCache with the service that supports HttpSession
replication. See the "jboss-web-cluster-service.xml" file in the
server/all/deploy directory for cache configuration details.
Besides the attributes supported by the standard Tomcat
SingleSignOn valve (see the Tomcat docs), this version also
supports the following attributes:
cookieDomain see above
treeCacheName JMX ObjectName of the JBossCache MBean used to
support credential caching and replication across
the cluster. If not set, the default value is
"jboss.cache:service=TomcatClusteringCache", the
standard ObjectName of the JBossCache MBean used
to support session replication.
-->
<!--
-->
<!-- Check for unclosed connections and transaction terminated checks
in servlets/jsps.
Important: The dependency on the CachedConnectionManager
in META-INF/jboss-service.xml must be uncommented, too
-->
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4148834#4148834
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4148834
17 years, 11 months
[Messaging, JMS & JBossMQ] - Re: How to access JBOSS by providing IP address
by priyarao234
hi Aneesh, Thanks 4 Reply..... I didn't made any changes in my server.xml which is avaolable at
C:\jboss-4.2.2.GA\server\default\deploy\jboss-web.deployer\server.xml
my server.xml file is like this only..... Plz specify where i have to do modifications....
<!--APR library loader. Documentation at /docs/apr.html -->
<!--Initialize Jasper prior to webapps are loaded. Documentation at /docs/jasper-howto.html -->
<!-- Use a custom version of StandardService that allows the
connectors to be started independent of the normal lifecycle
start to allow web apps to be deployed before starting the
connectors.
-->
<!-- A "Connector" represents an endpoint by which requests are received
and responses are returned. Documentation at :
Java HTTP Connector: /docs/config/http.html (blocking & non-blocking)
Java AJP Connector: /docs/config/ajp.html
APR (HTTP/AJP) Connector: /docs/apr.html
Define a non-SSL HTTP/1.1 Connector on port 8080
-->
<!-- Define a SSL HTTP/1.1 Connector on port 8443
This connector uses the JSSE configuration, when using APR, the
connector should be using the OpenSSL style configuration
described in the APR documentation -->
<!--
-->
<!-- Define an AJP 1.3 Connector on port 8009 -->
<!-- The JAAS based authentication and authorization realm implementation
that is compatible with the jboss 3.2.x realm implementation.
- certificatePrincipal : the class name of the
org.jboss.security.auth.certs.CertificatePrincipal impl
used for mapping X509[] cert chains to a Princpal.
- allRolesMode : how to handle an auth-constraint with a role-name=*,
one of strict, authOnly, strictAuthOnly
+ strict = Use the strict servlet spec interpretation which requires
that the user have one of the web-app/security-role/role-name
+ authOnly = Allow any authenticated user
+ strictAuthOnly = Allow any authenticated user only if there are no
web-app/security-roles
-->
<!-- A subclass of JBossSecurityMgrRealm that uses the authentication
behavior of JBossSecurityMgrRealm, but overrides the authorization
checks to use JACC permissions with the current java.security.Policy
to determine authorized access.
- allRolesMode : how to handle an auth-constraint with a role-name=*,
one of strict, authOnly, strictAuthOnly
+ strict = Use the strict servlet spec interpretation which requires
that the user have one of the web-app/security-role/role-name
+ authOnly = Allow any authenticated user
+ strictAuthOnly = Allow any authenticated user only if there are no
web-app/security-roles
-->
<!-- Uncomment to enable request dumper. This Valve "logs interesting
contents from the specified Request (before processing) and the
corresponding Response (after processing). It is especially useful
in debugging problems related to headers and cookies."
-->
<!--
-->
<!-- Access logger -->
<!--
-->
<!-- Uncomment to enable single sign-on across web apps
deployed to this host. Does not provide SSO across a cluster.
If this valve is used, do not use the JBoss ClusteredSingleSignOn
valve shown below.
A new configuration attribute is available beginning with
release 4.0.4:
cookieDomain configures the domain to which the SSO cookie
will be scoped (i.e. the set of hosts to
which the cookie will be presented). By default
the cookie is scoped to "/", meaning the host
that presented it. Set cookieDomain to a
wider domain (e.g. "xyz.com") to allow an SSO
to span more than one hostname.
-->
<!--
-->
<!-- Uncomment to enable single sign-on across web apps
deployed to this host AND to all other hosts in the cluster.
If this valve is used, do not use the standard Tomcat SingleSignOn
valve shown above.
Valve uses a JBossCache instance to support SSO credential
caching and replication across the cluster. The JBossCache
instance must be configured separately. By default, the valve
shares a JBossCache with the service that supports HttpSession
replication. See the "jboss-web-cluster-service.xml" file in the
server/all/deploy directory for cache configuration details.
Besides the attributes supported by the standard Tomcat
SingleSignOn valve (see the Tomcat docs), this version also
supports the following attributes:
cookieDomain see above
treeCacheName JMX ObjectName of the JBossCache MBean used to
support credential caching and replication across
the cluster. If not set, the default value is
"jboss.cache:service=TomcatClusteringCache", the
standard ObjectName of the JBossCache MBean used
to support session replication.
-->
<!--
-->
<!-- Check for unclosed connections and transaction terminated checks
in servlets/jsps.
Important: The dependency on the CachedConnectionManager
in META-INF/jboss-service.xml must be uncommented, too
-->
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4148833#4148833
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4148833
17 years, 11 months